Oracle® Insurance Rules Palette 10.1.2.0 E59346-01

Calculate Rules

Calculate rules are business rules that calculate various segment and/or policy values necessary for a policy. Calculate rules consist of an input math and calculation section, MathVariable validation and a mapping output section.

The math section pulls in any necessary input values and performs required calculations.

The output section of a Calculate General rule includes a mapping section that can write calculated values to AsPolicyField, AsSegmentField, AsClientField, and AsRoleField.    

• When calculating a segment the segment fields should be mapped to the segment being calculated.  

• Any field included in the output mapping must be defined in the destination screen rule such as the PolicyScreen or Segment business rule.  

A calculate button or a save button must be configured on the desired screen with the RULE attribute equaling the name of the Calculate rule to be invoked.   

Validations

Validations can be configured to validate any math variables right after they are processed. Error messages can be configured within the Validations section to provide the user with information in the event that a validation fails.

A math variable (from the MathVariables section) or Segment Field substitution may be made in the validation message. If an actual integer value from a math variable or segment field is needed, it must be surrounded by $$$. If a Segment field name is used in the Calculate Segment rule, the prefix ‘Segment:’ is required in the substitution.

The only supported data types are ‘TEXT’, ‘INTEGER’, ‘CURRENCY’, ‘DATE’ or ‘DECIMAL’. Therefore any other data types will need to be converted to TEXT, INTEGER or DECIMAL before being passed into the validation message. Special characters such as ‘$’ or ‘%’ need to be added in the validation message and will not be included in the substitution.

Validation Examples

The following example shows the error message configuration a user would see if the base issue age is greater than the maximum issue age on a policy.

<Expression TYPE="ErrorOnTrue" MESSAGE="Issue Age exceeds the maximum age of 65 (60 if in New York State). Segment will not calculate.">BaseIssueAge &gt; MaximumIssueAge</Expression>

If an actual integer value from a Segment Field or MathVariable name BaseIssueAge was needed for the validation message, then the configuration could be constructed as:

<Expression TYPE="ErrorOnTrue" MESSAGE="Issue Age of $$$Segment:BaseIssueAge$$$ exceeds the maximum age of 65 (60 if in New York State). Segment will not calculate.">BaseIssueAge &gt; MaximumIssueAge</Expression>