You’ve registered and joined the OPA Hub Website, where our goal is to be the best Community website about Oracle Policy Automation. You are already one of 572 people here who have a shared interest in Oracle Policy Automation. Welcome aboard! Ask a question, make a comment, get involved!
Win! Win! Win!
Now, take a moment to answer this question : you can enter as many times as you like AND the first 5 winners will win the new OPA Hub T-shirt. If you are not interested of course, please feel free to browse the site.
Below is a project written in Oracle Policy Automation 12 (this was actually in 12.18B but it has no bearing on the example). It has only one attribute : the date of the next visit. This is written as follows:
The date of the next visit= YearEnd (AddYears(the current date;1))
The date you are running the Debugger, the current date is November 19, 2018. The rule should perform a simple assignment, taking the current date, adding a year and then using that as the input for the YearEnd function. So :
YearEnd(November 19, 2019)
But the Debugger session of the Oracle Policy Automation Interview displays the following:
The date is incorrectly showing 12/31/20. So what is happening here? Even more strange, the Data tab of the Debugger shows the following:
The value is correct on the right, incorrect on the left.
So what has happened to the Oracle Policy Automation project in this example? What has the Project author done wrong?
Hints to Help You
- It’s not a product bug
- It’s not the separator “,” or “;” – these are based on your Region settings and I use English language but in Swiss region. Use your own separator if you are building it.
- It’s not a bug with the function
- It’s not a problem with years using 2 digits or 4