The ProcessRequirements Business Rule "NewStatus" Element Does Not Work As Expected/Defined
(Doc ID 2329649.1)
Last updated on MAY 05, 2021
Applies to:
Oracle Insurance Policy Administration J2EE - Version 11.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Requested Code Change
Add a specification that ProcessRequirements business rule would be able to update the status to the status specified in the business rule itself and not only trigger the requirement definition.
Expected Behavior
Update requirement fields as well as its status using an activity.
Expect the requirement definition to continue to be triggered based on the newly specified status.
The NewStatus’ element is defined as:
This is not the case. Instead, it just kicks off the Requirement Definition for the current status of the requirement.
The expectation is that the status would be changed to the status specified in NewStatus and that the definition be kicked off for this newly changed status.
Steps to Reproduce
1) Configure an activity to use the ProcessRequirement Attached Rule (AR)
2) Configure the AR to update the status of the requirement
3) Add and Process the activity - notice the requirement status will remain unchanged.
Business Impact
Due to this issue, users are unable to change the status of a requirement via an activity.
Cause
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
Symptoms |
Cause |
Solution |
References |