My Oracle Support Banner

Activity Reversal Does NOT Shadow Generated Requirements (Doc ID 2397372.1)

Last updated on MAY 10, 2018

Applies to:

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


On : version, General

Client/Policy level Requirements generated by processed Activity are not removed/shadowed by reversal of that Activity. This is inconsistent with treatment of other Activity impacts such as spawns, attached rule updates to policy/status, etc. which are rolled back via its reversal. Reprocessing of Activity creates new instances of existing Requirements which did not get removed by reversal causing clutter and confusion for the user.

Client/Policy level Requirements generated by processed Activity should be removed/shadowed when that Activity is reversed.

The issue can be reproduced at will with the following steps:
1. Process Activity that generates a NB/Policy requirement. Reverse the Activity and see that requirement remains listed for NB/Policy (i.e. not removed/shadowed by Activity reversal)

The issue has the following business impact:
Due to this issue, there is an accumulation of outdated and redundant data; confusing to user and requires extra/manual effort to remove bad/stale requirements which increases risk for error of deleting wrong requirement(s).


To view full details, 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 a vibrant support community of peers and Oracle experts.