Activity Array Population of Entities For Activity Processing

Currently when a transaction is spawned using the ActivityArray option, we can only pass data to Activity Fields but there is no option to pass on data relating to Allocations, MultiFields, Suspense, MultiSuspense, which could be required in transaction processing. This enhancement is to address this gap and provision for passing data into such auxiliary transaction data.

There are two other related items that are included in this enhancement

 ActivityArray now provides the option to “APPEND” or “SETVALUE” in the Post Assignment Math to an existing ActivityArray created in the Activity Math.

 When using GenerateSuspense BR, the Suspense Number generated from the GenerateSuspense BR is now available for access in the Post Assignment Math.

Prototype Configuration DetailOverview

This feature gives enhancement to the capability of Activity Array to support Multifields, Allocations and Suspense.

Prerequisites

User should be able to add the "ActivityArray" transaction in PAS application.After processing the "ActivityArray" transcation

User should also be able to see the "SuspensePAVE" Transaction

New Items

A new transaction 'ActivityArray' and 'SuspensePAVE' is created at 'Dynamic Plan' Level.

Transaction name: ActivityArray

Company name: Prototype Individual Child Company

Product Name: Individual Prototype Product

Plan Name :Dynamic Prototype Plan

Transaction name: SuspensePAVE

Company name: Prototype Individual Child Company

Product Name: Individual Prototype Product

Plan Name :Dynamic Prototype Plan

BusinessRules Attached :

PostAssignmentValidateExpressions

Generate Suspense

MultiField-PrototypePolicyScreen

Changes to Existing Items

None

Configuration Details

"Entity Level For Linking Allocation" field will have 'Plan','Policy','Activity' for user selection.

MultiFields details are passed via MathVariable.

SuspenseDetails should be entered into "SuspenseNumber1" and "SuspenseNumber2" fields along with the field "Amount" by the user.

Allocations details will be passed depending on the selection in the "Entity Level For Linking Allocation" field.

If the user adds and process the "AddActivity" transaction "SuspenseInPAVE" transaction will be autoprocssed since PROCESSIMMEDIATE="Yes"

in 'ActivitySequenceProcess' tag in the "AddActivity" transaction.

Scenario 1:If the user selection is Plan:

Along with the suspense and multifields values PlanLevel allocationdetails will be sent to "SuspenseInPAVE" transaction.

Result:

User should be able to see PlanLevel Allocation,Suspense Detail and Multifield details in ActivitySummary screen of "SuspenseInPAVE" transaction

Scenario 2:If the user selection is Policy:

Along with the suspense and multifields values PolicyLevel allocationdetails will be sent to "SuspenseInPAVE" transaction.

Result:

User should be able to see PolicyLevel Allocation,Suspense Detail and Multifield details in ActivitySummary screen of "SuspenseInPAVE" transaction.

Scenario 3:If the user selection is Activity:

Along with the suspense and multifields values user should add ActivityLevel allocationdetails also which will be sent to "SuspenseInPAVE" transaction.

Result:

User should be able to see ActivityLevel Allocation,Suspense Detail and Multifield details in ActivitySummary screen of "SuspenseInPAVE" transaction.

     
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us