You are here: Transaction Rules > Transaction Elements > Math Element > ACTIVITY

Oracle® Insurance XML Configuration Guide Release 9.4.1.0 E23637_01

# ACTIVITY

## Description

Activity, ActivityField, and ActivityArray are used to support functionality equivalent to Spawncode 08 where the system would spawn multiples of the same transaction from a single activity.

Activity math objects will hold all the field instructions for a given transaction rule while ActivityArray will hold multiples of the activity math record. ActivityField will allow the system to extract the value of a specified field within the Activity math object. By allowing each spawned transaction to reference unique data sets, any number of transactions may be spawned any number of times on the policy for a single parent transaction.

Activity represents a collection of activity fields. The ACTIVITY math variable is similar to COLLECTION with the exception that ACTIVITY will create a 'virtual' math object set by using the default value or within the configuration replacing any of the default calculated values using a "SetValue" operation.

Before values can be assigned to the fields of the activity math object, it must first be instantiated in the transaction math using the "Create" operation. The value of the math variable is either a literal transaction name, transaction GUID, or a reference to a previously defined math variable containing either of these two values.

## ACTIVITY Element/Attribute Table

TYPE=ACTIVITY

Element | Attributes | Attribute Value | Element Value | Definition
--- | --- | --- | --- | ---
<MathVariable> | TYPE | ACTIVITY |  |
| OPERATION | CREATE | A variable whose value is the transaction name or GUID (can be contained in a previously defined math variable). | When using the CREATE operation, the value of the math variable cannot be blank and must be equal to a valid Transaction Name or Transaction GUID. If only a transaction name is specified, the system will resolve the transaction rule in the current activity plan. If a GUID is specified, the transaction rule will be that of the specified GUID but that GUID must be for the current plan.
|  | SETVALUE | A variable or literal whose value is used to replace the current default value of an activity field. | Field Name to update the objectname. Value is the name of the math variable or literal value used. SetValue is taking the value and replacing the FieldName default value with the value entered in the Value property. Note: Some fields of the Activity math object cannot be replaced using SetValue operation. If they are configured, the system will ignore instructions to change/set value for the following fields: ACTIVITYGUID, TRANSACTIONGUID, TYPECODE, STATUSCODE, ACTIVEFROMDATE, ACTIVETODATE, CLIENTNUMBER, RELATEDGUID, XMLDATA, PROCESSINGORDER, ERRORSTATUSCODE, SUSPENSESTATUSCODE, ACTIVITYGMT, ENTRYGMT, CREATIONGMT, and SCHEDULEGUID. Aside from the dynamic fields, the following "Fixed" fields should accept new values: POLICYGUID, EFFECTIVEDATE. Note:POLICYGUID should be available for cross policy spawning. The POLICYGUID will default to that of the current policy and may be replaced by a set value operation. If Set Value requires a calculation, the calculation must first be done with another math variable which will be referenced by the Set Value operation. Example: Adding 15 days to the Effective Date must be handled by another math variable that the Set Value operation will be used populate the object field.

## XML Example

    <MathVariable VARIABLENAME="ObjectName" TYPE="ACTIVITY" OPERATION="SETVALUE" FIELDNAME="EffectiveDate" DATATYPE="DATE">Activity:EffectiveDate</MathVariabl

    <MathVariable VARIABLENAME="ObjectName" TYPE="ACTIVITY" OPERATION="CREATE" DATATYPE="ACTIVITY">Disbursement</MathVariable>

Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Open table of contents