Undo Redo of Client Level Transaction

From Oracle Insurance Rules Palette

You are here: Main Explorer > Prototypes > Prototype Samples for Previous Releases > Undo Redo of Client Level Transaction

 

Undo Redo of Client Level Transaction

 

OIPA, adds a new feature for Undo/Redo functionality at the client and customer level. New transaction type is now added under Prototype Company for Client Plan named as "Client financial". This new transaction type will be a Reversible/Reversing type of transaction. Earlier the existing type was “Client-Financial” transaction type, now being "Client-Financial -Reversible-Reversing type. The following are available

 

  • Client-Financial (Client-Financial-Reversible-Reversing)
  • Client-Financial-Reversible-Non-Reversing

 

New Transaction Type System Codes are added in the palette to recognize new AsCode transaction types (mentioned above).

 

Configuration Overview

 

The new transactions ‘ClientFinancialReversibleReversing’ and ‘ClientFinancialReversibleNonReversing’ are added for the Client Plan in Prototype Company. These transactions are expected to get processed on the following way

 

  • On processing the ‘ClientFinancialReversibleReversing’ activity, the ‘ClientFinancialSpawn1’ activity gets spawned.
  • On recycling/reversing the ‘ClientFinancialReversibleReversing’ activity, will undo/redo all the active activities above it. As the spawned activity ‘ClientFinancialSpawn1’ is a reversible, non reversing type, it gets reversed as well.
  • On processing the ‘ClientFinancialReversibleNonReversing’ activity, the ‘ClientFinancialSpawn2’ activity gets spawned.
  • On reversing the ‘ClientFinancialReversibleNonReversing’ activity, the activities above will not get affected. The spawned activity ‘ClientFinancialSpawn2’ is not reversed on reversing

 

 

Pre-requisite

 

The OIPA user should have the access to both the transactions in the application and should have the necessary security in order to access the ‘Delete’ checkbox for the transaction ‘ClientFinancialReversibleReversing’.

 

Prototype Example

 

ClientFinancialReversibleReversing

 

  • This transaction has only the field ‘EffectiveDate’ configured.
  • On reversing this activity, all the activities above it, other than the non reversible type, will also get reversed, and a new instance of the current activity is not created.
  • On recycling this activity, all the activities above it, other than the non reversible type, will also get reversed, and a new instance of the current activity is created.
  • The spawned activity ‘ClientFinancialSpawn1’ which is of type ‘ReversibleNonReversing’, also gets reversed.

 

ClientFinancialReversibleNonReversing

 

  • This transaction also has only the field ‘EffectiveDate’ configured.
  • On reversing this activity, the other activities above will not get affected.
  • The spawned transaction ‘ClientFinancialSpawn2’ will also remain unchanged on reversing this activity.

 

ClientFinancialSpawn1

 

This transaction also has only the field ‘EffectiveDate’ configured. It is spawned by transaction ‘ClientFinancialReversibleReversing’.

 

ClientFinancialSpawn2

 

This transaction also has only the field ‘EffectiveDate’ configured. It is spawned by transaction ‘ClientFinancialReversibleNonReversing.

 

View Prototype in OIPA

  1. Login to OIPA with a Prototype company user credentials.
  2. Select a Client Plan
  3. Create a new Policy and process it
  4. Add new Activity and process the activity for the above transaction types
  5. View the result for the new functionality explained above