Called Event and Call External Event Prototype

OIPA now allows Events in a transaction to generate an Action that results in triggering an event configured in a BRassociated with the transaction. This feature is provided to cater to a situation where the action to be performed in the target BRis to be triggered on an event defined in the transaction but the action to be performed is also dependent on the values in one or more fields in the target BR.

This functionality will be supported by defining an Action in the target BR (MultiField BRis used to demonstrate the capability in this case) as a CALLEDEVENT with an IDattribute. Such a called event defined in the target BRcan be triggered from the transaction through an Action of type CALLEXTERNALEVENT which is defined in the transaction with the same value in the IDattribute.

Currently this feature is supported in MultiFields BRand TransactionAllocationScreen BR. This may be extended to other associated BRs in future.

Scenario

In a specific transaction, a specific event to assign value or validate values in a Multifield in one or more instances of the multifield is required to be triggered on the basis of a specific event inside the transaction. The event is dependent on the values in both the transaction field and the multifield values.

Prototype Configuration

View Prototype in OIPA

  1. Log in OIPA using the Prototype Company user ID and password.
  2. Click Policy | New from the Main menu.
  3. Add a shell policy to test the prototype.
  4. Click Add Activity on the Secondary menu.
  5. Select the MultifieldEvents activity from the Activity drop down box.
  6. Make changes to the various fields view the action event triggered as explained above to view this functionality in action.
     
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us