OnChange Does Not Commit Changes Correctly (Doc ID 2272497.1)

Last updated on MAY 31, 2017

Applies to:

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

Goal

 Using OnChange configuration provided by customer, the following behavior is observed:

1. Change the value of the first field which triggers an OnChange event.
2. The first field's OnChange events should trigger the 2nd field's event to trigger
3. Review the results, it appears that the 2nd field's OnChange events use the values from the initial load.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms