FIELD
Pulls in a value from either the fields section of the transaction (AsActivity), the plan (AsPlan) or the policy (AsPolicy). In the value of this element you must list the name of the field you want to pull the value of, prefixed with the scope of where you are pulling it.
| TYPE = FIELD | ||||
|---|---|---|---|---|
| Element | Attributes | Parent Element | Description | Element/Attribute Value |
|
<MathVariable>
|
TYPE |
Prefix:FieldName Prefixes are: Activity, Policy*, Plan* and Valuation. *Best practice if you want a policy field to use a MATHVARIABLE TYPE=POLICYFIELD and if you want to use a plan field use a MATHVARIABLE TYPE=PLANFIELD
FIELD |
||
|
DATATYPE |
DATE TEXT INTEGER DECIMAL |
|||
|
ROUND |
="[Integer]" An optional attribute to be used when DATATYPE="DECIMAL" |
|||
|
DEFAULT |
="[String]" |
|||
|
LOG |
="Yes" |
|||
|
DECRYPT |
Yes: Field data is decrypted. No: Field data is not decrypted. |
|||
|
KEEPORIGINAL
|
Yes: The field data is stored in the encrypted format. No: The field data is stored in the decrypted/normal format. |
|||
|
CLEARVALUE |
Optional Element: Value: Yes / No Default Value: No Yes: The value of the math variable will be deleted after the execution of all the Attached Rules at the end of activity processing and will not be visible on the Math tab in the Activity details screen. No: The value of the math variable will be retained after activity processing and will be displayed in the Math tab in the Activity details screen. |
|||
XML Schema
<Field>
<Name></Name>
<Display></Display>
<DataType></DataType>
<Encrypt ERASE="Yes">Yes</Encrypt>
</Field>
XML Example
<MathVariable VARIABLENAME="Example" TYPE="FIELD" DATATYPE="INTEGER">Activity:TermFee</MathVariable>
