A Calendar starts a/several years after the year where the "Start Date" of the Rules.
As a result, the simulation of the Rule in UVC gives inaccurate results as it uses the first year of the Calendar instead of the one mentioned on the Rule.
Example:
Release : 6.x
Component : DOLLAR UNIVERSE
Calculator forces date calculation to a valid date in calendar without informing the Interface (UVC).
Update to a fix version listed below or a newer version if available.
Fix version(s):
Component: Univiewer.Console and Application.Server
Dollar Universe 6.10.11 - Released 2nd October 2019
Details of the correction:
A new enhancement has been introduced to add a Popup Error in UVC when a year before the Calendar is used in the Start Date of the Rule.
It will now display "owls_rule_simulate error: 1503" when simulating the Rule with a date not present in the Calendar.
In universe.log of the impacted node, this error will be displayed:
|ERROR|X|IO|pid=p.t| buildDay |[][] - year is outside the bounds of calendar [2016-2036]: 2015. Force it to calendar period
In order to fix the above Errors, modify the "Valid from" Date of the Task's validity and the Rule's "Start date" so that both start in a year included in the Calendar (ie 2019).
This can be done via an export of the tasks with "uniexp" to xml, then modifying the dates in the xml file, and then importing again the modified xml file overwriting the existing tasks with the command "unimp".