You are here: Business Rules > Attached Rules > DoSegmentRecalculations

Oracle® Insurance Rules Palette Release 9.3.1.0 E21044_01

# DoSegmentRecalculations

## Description

This business rule can be attached to a transaction that specifies the names and execution orders of segments attached to a policy. When the rule is processed, the segments for the current policy will be loaded and calculated in the order specified.

DoSegmentRecalculation Element/Attribute Table
Element/Tag | Definition | Attribute | Element/Attribute Value and Description
--- | --- | --- | ---
<DoSegmentRecalculations> | The required opening and closing elements of this business rule. |  |
<CalculationOrder> | Required element; Used to specify the order in which the segments have to be recalculated. Note: Only those segments that are mentioned here will be recalculated. If a segment is part of a policy but not mentioned here it will not be processed. | IF | Optional attribute; ="Expression" If this attribute is present and if the condition returns True, only those segments that are specified in the <SegmentGUID> tag are processed. All other segments are ignored. If this attribute is present but the condition returns False, then the IF condition in <CalculationOrder> is evaluated.
<SegmentName> | Required / Repeatable element; This element is used to specify the name of the segments. The order in which the segments will be processed depends on the order in which they are mentioned in this element. |  | Required element value; String: Name of the segment.
<WriteActivitySource> | Optional element; Indicates the source activity is stored to the BenefitSplit record. Note: ActivityGUID in AsBenefitSplit table: If the BenefitSplit is created by normal activity processing, then the Activity's GUID should be put in the ActivityGUID column. ShadowActivityGUID in AsBenefitSplit table: If the existing BenefitSplit records are affected by any of the activities, then that Activity's GUID should be put in ShadowActivityGUID |  | Required element value; Yes/No Yes - Indicates that the source activity that caused the BenefitSplit is captured in the AsBenefitSplit table. No - Indicates that the source activity that caused the BenefitSplit is not captured in the AsBenefitSplit table.

## XML Example

    <DoSegmentRecalculations>

    <CalculationOrder>

    <SegmentName>Base Coverage - Term</SegmentName>

    <SegmentName>Flat Extra - Temporary</SegmentName>

    <SegmentName>Flat Extra - Permanent</SegmentName>

    <SegmentName>Term - Disability Benefit Option</SegmentName>

    </CalculationOrder>

    </DoSegmentRecalculations>

## Schema Example

    <DoSegmentRecalculations>

    <CalculationOrder IF="[Expression]">

    <SegmentName>[String]</SegmentName>

    <SegmentName>[String]</SegmentName>

    </CalculationOrder>

    </DoSegmentRecalculations>

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

Open table of contents