Client Screen Errors Are Persisting In Activity Client Fields After Closing The Window

(Doc ID 2422948.1)

Last updated on JULY 13, 2018

Applies to:

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

Symptoms

On : 11.1.0.2 version, General

ACTUAL BEHAVIOR
---------------
Client Screen Errors Are Persisting in Activity Client Fields after closing the window. We have OnSubmit validations for fields on the client screen and when we go to create a client using a ClientField inside of an activity and trigger the error if the user closes the screen and re-opens it the error message is still present on the screen. To trigger this issue you need to have a client where one of it's fields has an OnSubmit validation around it that throws an error, after this is configured you need to create an activity with a ClientField. Once that has been done create this activity and click on the client button to create a new client, fill in enough information to trigger the OnSubmit error once this is triggered close the window by hitting cancel or the 'X' button once this is done click the client icon again to create a new client and notice the Error Message Will still be displayed.

EXPECTED BEHAVIOR
-----------------------
When a user returns to the screen after trigger an OnSubmit error after canceling or closing the window the error would no longer be displayed.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) login
2) Navigate to policy
3) Add activity
4) Click on the client button and navigate to New Client
5) Switch type to Corporate and click save - note error message at the top
6) Close the client window or click cancel... Do not save it (Issue happens in both cases)
7) re-open the client window and notice error message will stil be displayed

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Business users will see error messages that are not relevant to their current context.

Cause

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