MultiFields Element

A set of configurable fields that can be repeated on a screen is called MultiFields. Multifields are allowed in Screen and Transaction configuration and add multiple sets of dynamic fields. To use MultiFields in a business rule or transaction, a MultiField business rule must first be defined. It can then be used on a screen by configuring the <MultiFields> element and providing the full business rule name. For detailed information about configuring MultiFields, refer to "MultiField Configuration" in the Rules Palette Help.

Note: In any one Screen or Transaction, only one MultiField business rule can be referenced by a <MultiFields> element and only one <MultiFields> element can be configured on the Screen or Transaction. In case multiple sets of MultiFields are required, multiple sets can be configured in a single MultiField business rule. If more than one <MultiFields> element is configured in a Screen or Transaction, only the first will take effect.

MultiFields: Elements and Attributes
Element Attribute Parent Element Description / Value
<MultiFields>    

Optional:

This element triggers the inclusion of a MultiFields business rule into the containing rule's field presentation.  This is applicable for a screen or transaction where the user is allowed to enter or display information.  This element is optional and only required when the MultiFields presentation is desired.

Values:

  • No

    • default

    • The multifield rule's definition will not be incorporated into the containing rule's field presentation.

  • Yes

    • The multifield rule's definition will be incorporated into the containing rule's field presentation.
  RULE <MultiFields>

Required:

The attribute provides the exact name of a MultiFields business rule that is incorporated in the containing rule's field presentation.  The first (root) element in the rule must be <MultiFields>.

Values:

  • literal

    • Business rule name that defines at least one multifield structure.

XML Schema

<[rule_name]>
    <!--screen rule or transaction configuration-->
    ...
    <MultiFields RULE="[literal]">[No | Yes]</MultiFields>
    ...
</[rule_name]>

XML Schema

<Client TYPECODE="02" ACTIVITYPLAN="Client Plan">
    ...
    <MultiFields RULE="MultiField-IndividualClient">Yes</MultiFields>
    ...
</Client>
 
OR
 
<Transaction>
    ...
    <MultiFields RULE="MultiField-PrototypePolicyScreen">Yes</MultiFields>
    ...
</Transaction>