You are here: Business Rules > Attached Rules > CreateSegments

CreateSegments

Description

This business rule creates one or more new segments on a policy when attached to a transaction, when specific conditions are satisfied. This rule must be listed in TransactionBusinessRulePacket.

CreateSegment Element/Attribute Table
Element/Tab	Definition	Attribute	Element/Attribute Value and Description
<CreateSegments>	The opening and closing tag of the CreateSegments Business Rule.
<Tests>	Optional This element denotes a section containing one or more conditional expressions that when true will allow the rest of the rule to execute.
<Test>	Required/Repeatable Element This element allows the expression of a test condition. When more than one condition is provided, all conditions must evaluate to true in order for the containing <Tests> element to result in true.		A string representing an expression that can evaluate to true or false. Math variables may be used within the condition.
<CreateSegment>	Required, Repeatable: This element identifies a segment and the fields that are created and populated.
		SEGMENTNAME	Required: A literal value that matches the name of the segment exactly. This attribute identifies the segment to create using the segment’s segment name.
		STATUSCODE	Optional: A literal code value. “24”, the default value, means the default segment and allows the segment to be visible in OIPA. This element provides a value for the status code column on the new segment.
<Tests>	Optional: This element denotes a section containing one or more conditional expressions that when true will allow the containing element to execute.
<Test>	Required, Repeatable: This element allows the expression of a test condition. When more than one condition is provided, all conditions must evaluate to true in order for the containing <Tests> element to result in true..		A string representing an expression that can evaluate to true or false. Math variables may be used within the condition.
<Fields>	Required, Repeatable: Opening and closing elements to associate segment fields and their values. These values will apply to the specific Segment being created.
<Field>	Required, Repeatable: The opening and closing elements for a Segment field definition block.
<Name>	Required: Indicates the segment field the value of the <Value> element will be copied to.
<Value>	Required: Defines a source for the value being applied to the field indicated by <Name>.		A math variable or activity field from the transaction the rule is attached to.

XML Example

<CreateSegments>

<Tests>

<Test>AddBaseCoverageSegment = 1</Test>

</Tests>

<CreateSegment SEGMENTNAME="Base Coverage" STATUSCODE="24">

<Tests>

<Test>AddBaseCoverageSegment = 1</Test>

</Tests>

<Fields>

<Field>

<Name>SegmentAmount</Name>

<Value>SegmentAmountMV</Value>

<Currency>USD</Currency>-->

</Field>

</Fields>

</CreateSegment>

</CreateSegments>

Schema Example

<CreateSegments>

<Tests>

<Test>[conditional expression]</Test>

. . .

</Tests>

<CreateSegment SEGMENTNAME="[literal segment name]" STATUSCODE="[code value]">

<Tests>

<Test>[conditional expression]</Test>

. . .

</Tests>

<Fields>

<Field>

<Name>[segment field name]</Name>

<Value>[math variable|activity field]</Value>

</Field>

<Field>

. . .

</Field>

. . .

</Fields>

</CreateSegment>

<CreateSegment>

. . .

</CreateSegment>

. . .

</CreateSegments>