Requirement Created With Fields Of Parent Requirement
(Doc ID 2687293.1)
Last updated on JULY 03, 2020
Applies to:Oracle Insurance Policy Administration J2EE - Version 220.127.116.11 and later
Information in this document applies to any platform.
On : 18.104.22.168 version, General
As 22.214.171.124 resolves some issues with requirements running in PRODUCTION mode, we are seeing new issues crop up as we are able to execute test scenarios more completely. This issue has presented itself now in production mode because in prior releases we have not been able to get as far as requirements executing the AddRequirements attached rule.
The scenario is this:
A policy requirement is configured to create another policy requirement when executing.
In DEVELOPMENT mode, this works as expected. However, in PRODUCTION mode, if the RequirementScreenDefinition rule has been cached (e.g. not the first execution of the scenario after a JVM restart, but subsequent executions) then the target requirement is created using the cached version of the parent requirement. This is due to the cache key for the screen rule not containing the unique ID of the requirement definition when created.
PRODUCTION mode should work in the same way as DEVELOPMENT mode in that the child requirement is created correctly.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document