My Oracle Support Banner

The 'executeRequirementOnAllStateChanges=No' Properly Does Not Function As Expected (Doc ID 2873101.1)

Last updated on JUNE 02, 2022

Applies to:

Oracle Insurance Policy Administration J2EE - Version and later
Information in this document applies to any platform.


On : version, General

Since the release of OIPA v11.2.7.0 there is a new property: executeRequirementOnAllStateChanges.

The property description goes as follow:
Yes : This is the default if the system property is not provided. It will execute the Requirement's state configuration whenever the Requirement's field or status data have been modified.
No : It will prevent the Requirement's state configuration from executing when the Requirement's field data have been modified and will execute when the Requirement's status data has been modified.

Customers who desire the V10 behavior must add the New System Property with a Value of "No"

The Requirement's state configuration is executed when:
- The Requirement's Field or Status data have been modified.
- A Field with a OnChange Event is modified.

So the executeRequirementOnAllStateChanges=No is not actually working as designed.

The Requirement's state configuration to run ONLY when the Status is modified.

The issue can be reproduced at will with the following steps:
1. Open a Policy.
2. Navigate to Requirements.
3. Open a Requirement
4. Open one of the Requirement.
5. Update the value in one of the following fields: FollowUpDone,ServiceProvider,Insured.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.