You are here: Segment Rules > Segment

Segment

Description

Segment dictates the data that is stored for each policy instance. Segment is configured similar to screen rules but allows for additional validations and calculations by invoking CalculateGeneral business rules.  

Segment Element\Attribute Table

Element/Tag

Definition

Attribute

Element/Attribute Value and Description

<Segment>

The opening and closing tag.

 

 

<Fields>    

Screen entry fields. Click the Fields link for configuration details.

 

 

<Buttons>   

List of buttons that can be selected on the screen.

 

 

<Button>           

 

Name of the available button. If there are multiple buttons then they will be listed separately in individual <Button> tags.

RULE

String: Name of the Calculate rule that will be invoked by processing the Calculate button. Used in conjunction with the Calculate button. 

<Events>   

See Events.

 

 

<Validation>   

Opening and closing tags for a Validation section.

 

 

<Required>         

Allow the configuration to list the fields that must contain user entered data or selection.

 

 

<Field>               

Repeatable;

Name of the field that must have user input.

 

 

 

SegmentScreen Image 

OIPA Segment Screen

XML Example

<Segment>
        
<Fields>   
        
<Field>      
        
<Name>SegmentIssueDate</Name>
        
<Display>Effective Date</Display>
        
<DataType>Date</DataType>
        
<Calculated TYPE="SQL">SELECT AsNbCaseField.Datevalue 
 FROM AsNbCaseField WHERE AsNbCaseField.CaseID='[CaseID]' AND FieldName 
 = 'AppSignedDate'</Calculated>
        
</Field>      
        
<Field>      
        
<Name>SegmentIssueAge</Name>
        
<Display>Issue Age</Display>
        
<DataType>Integer</DataType>
        
<Disabled>Yes</Disabled>
        
</Field>      
        
<Field>      
        
<Name>RiderPremium</Name>
        
<Display>Rider Premium</Display>
        
<DataType>Money</DataType>
        
</Field>      
        
</Fields>      
        
<Buttons>   
        
<Button>Save</Button>      
        
</Buttons>   
        
<Events>   
        
<Event 
 TYPE="ONLOAD">      
        
<ActionSet ID="CheckForBaseCoverage"></ActionSet>
        
<ActionSet ID="CheckForInsuredRole"></ActionSet>
        
</Event>      
        
</Events>   
        
<ScreenMath>   
        
<Math ID="Math" GLOBAL="Yes">      
        
<MathVariables>         
        
<MathVariable VARIABLENAME="One" TYPE="VALUE" 
 DATATYPE="INTEGER">1</MathVariable>
        
<MathVariable VARIABLENAME="BaseSegmentCount" 
 TYPE="SQL" DATATYPE="INTEGER">SELECT COUNT(*) FROM 
 AsNbSegment JOIN AsSegmentName ON AsNbSegment.SegmentNameGUID = AsSegmentName.SegmentNameGUID 
 WHERE AsNbSegment.CaseID = '[CaseID]' AND AsSegmentName.TypeCode = '04'</MathVariable>
        
<MathVariable VARIABLENAME="InsuredCount" TYPE="SQL" 
 DATATYPE="INTEGER">SELECT COUNT(*) FROM AsNbRole JOIN AsNbCaseRole 
 ON AsNbCaseRole.RoleID = AsNbRole.RoleID WHERE AsNbCaseRole.CaseID = '[CaseID]' 
 AND AsNbRole.RoleCode = '03' AND AsNbRole.StatusCode = '01'</MathVariable>
        
</MathVariables>
        
</Math>      
        
</ScreenMath>   
        
<Actions>   
        
<ActionSet ID="CheckForBaseCoverage">      
        
<Condition IF="Math:BaseSegmentCount &lt; Math:One">
        
<Action ACTIONTYPE="ERROR">Base Coverage 
 must be added to case before adding Waiver Of premium coverage.</Action>
        
</Condition>
        
</ActionSet>      
        
<ActionSet ID="CheckForInsuredRole">      
        
<Condition IF="Math:InsuredCount &lt; Math:One">            
        
<Action ACTIONTYPE="ERROR">Insured must 
 be added to case before adding Waiver Of Premium coverage.</Action>
        
</Condition>            
        
</ActionSet>      
        
</Actions>   
        
</Segment>
        

 

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