PlanSegment
The PlanSegment business rule dictates the data that is stored for each plan segment instance. Configuration of the rule is similar to screen rules but will enable to capture PlanSegmentName level fields based on the configuration of PlanSegmentName definition.
Element/Tag | Definition | Attribute | Element/Attribute Value and Description |
---|---|---|---|
<PlanSegment> |
The opening and closing tag for the rule. |
|
|
<Subsections>
|
Optional element: The fields configured inside subsections will be grouped together and the display can be collapsed or expanded. |
SECTIONNODES |
Optional attribute:Expanded/Collapsed Collapsed is the default value. |
<Subsection> |
Repeatable element: Required if <Subsections> element is configured. |
TITLE |
Optional attribute:String The title to be displayed on the subsection header. |
SECTIONNODES |
Optional attribute: Expanded/Collapsed Collapsed is the default value. |
||
<Fields>
|
Screen entry fields. Click the Fields link for configuration details. |
|
|
<Events> | The opening and closing elements of the Event Section | ||
<ScreenMath> | The opening and closing elements of the ScreenMath Section | ||
<Actions> |
The opening and closing elements of the Actions Section | ||
<MultiFields> | Required: The opening and closing tag of the MultiFields element. This element is used to turn on/off the multifields section. The statement can occur in any part of the Transaction/Screen XML. | Required element value: Yes | |
RULE | A literal value referencing the exact rule name of a MultiFields business rule (AsBusinessRules.RuleName). |
XML Example
<PlanSegment>
<Subsections>
<Subsection>
<Fields>
<Field> </Field>
</Fields>
</Subsection>
</Subsections>
<Events></Events>
<ScreeMath></ScreenMath>
<Actions></Actions>
</PlanSegment>