Concurrency Issue On Client And Policy Level Activities When User Saves A Processed Activity
(Doc ID 2698138.1)
Last updated on AUGUST 07, 2020
Applies to:Oracle Insurance Policy Administration J2EE - Version 126.96.36.199 and later
Information in this document applies to any platform.
On : 188.8.131.52 version, General
Concurrency Issue on client and policy level activities when user saves a processed activity. System allows user to save an activity which has already been processed, causing the activity status to be changed back to pending while it has made all its commits.
An activity that is processed should not havae its status changed back to pending by saving its activity screen and a message should be displayed to the user attempting to make changes to an already processed activity. The activity should not be saved, or modified once it has been processed.
The issue can be reproduced at will with the following steps:
User A and B open same actvity's detail screen.
User A saves and processes activity. Activity is processed succesfully.
User B makes changes to the already processed activity and hits save. Activity is saved succefully and appears as pending.
Any user can now see the activity as pending and is able to process the activity.
However, the activity will almost always fail due to primary constraints.
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