Loading...

XML

Word

Printable

Affects:

Release Notes
Fix Build:
CR1
Target Release:

7.9.0.GA
Steps to Reproduce:
Hide

Create a new process.

Create a timer event.

Set Fire multiple times or Fire at specific date property to the value:

"R5/2021-02-29T15:36:00Z/PT5S" or "2021-02-29T15:36:00Z"

Actual result

The expressions are evaluated as valid.

Expected result

The expressions are evaluated as invalid.
All expressions are evaluated as invalid in case such date really doesn't exist.
Show
Create a new process. Create a timer event. Set Fire multiple times or Fire at specific date property to the value: "R5/2021-02-29T15:36:00Z/PT5S" or "2021-02-29T15:36:00Z" Actual result The expressions are evaluated as valid. Expected result The expressions are evaluated as invalid. All expressions are evaluated as invalid in case such date really doesn't exist.

Sprint:
2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28)

The leap days are not being validated for both Fire multiple times and Fire at specific date properties:

366th day of the year
- some ISO-8601 formats are not supported in engine (see ~~RHPAM-2695~~ for more details), hence this is out of scope of the jira.
29th of February

As a result, the date can be set to the non existing time. For example:

Examples of valid expressions:

There is also the issue with leap second: 60th second.

It is not possible to set seconds to "60" value.
Since it is not predicable when exactly the leap second will be scheduled, it is out of scope of this jira.

is related to

RHPAM-2986 Stunner - Date validation for Fire multiple times property in Timer event is not correct

relates to

RHPAM-2695 Component timer expression contains errors