ClientRequirementScreen

This business rule can be used to configure client's requirement summary table. If this rule is not configured, a default table displays the requirement summary with Requirement name, status, category and date updated along with actions as default columns. This screen rule overrides at Primary Company level.

ClientRequirementScreen: Elements and Attributes
Element/Tag Attributes Parent Element Description Element/Attribute Value

<ClientRequirementScreen>

   

The opening and closing tag of the business rule.

 

<Results>

 

<ClientRequirementScreen>

Required element:

This element defines the results of a requirement search.

 

<Hidden>

 

<Results>

Optional element: This element defines if results in the specified status should be hidden from view.

 

<StatusCode>

 

<Hidden>

A code defined for the AsCodeRequirementStatus code name.

Optional element: This element identifies the requirement's status.

 

<Table>

NAME

<Results>

Groups Supported shall be AsRequirement,AsRequirementDefinition,AsrequirementClient

Required element: This element controls the display of the requirement results table. See the Table Element page for more information on configuring this element.

 

<Column>

WIDTH

<Table>

Optional element: This element defines the width of columns in the results table, the alignment of the column's data and the format of the column's data.

Integer
 

ALIGN

<Table>

Left: The information in the column will be left-aligned.

Right: The information in the column will be right-aligned.

Center: The information in the column will be centered.

 
 

FORMAT

<Table>

Text: The information in the column will be formatted as simple text.

Currency: The information in the column will be formatted as currency.

Date: The information in the column will be formatted as a date.

 

<Group>

 

<Column>

The entity name that corresponds to the database table from which the requirement information should be extracted.

Optional element: This element identifies the database table from which the requirement information should be extracted.

Note: For example, <Group>Client</Group> indicates that the data should come from the AsClient database table.

 

 

XML Example

<ClientRequirementScreen>
<Results>
<Hidden>
<StatusCode>05</StatusCode>
<StatusCode>88</StatusCode>
</Hidden>
<Table>
<Column WIDTH="200" ALIGN="LEFT">
<Name>Message</Name>
<Display>Requirement Name</Display>
<DataType>Text</DataType>
<Group>Requirement</Group>
</Column>
<Column WIDTH="200" ALIGN="LEFT">
<Name>Name</Name>
<Display>Insured</Display>
<DataType>Text</DataType>
<Group>Client</Group>
</Column>
<Column WIDTH="50" ALIGN="LEFT">
<Name>TaxID</Name>
<Display>Tax ID</Display>
<DataType>Text</DataType>
<Group>Client</Group>
</Column>
<Column WIDTH="50" ALIGN="LEFT">
<Name>Status</Name>
<Display>Status</Display>
<DataType>Text</DataType>
</Column>
<Column WIDTH="200" ALIGN="LEFT">
<Name>UpdatedGMT</Name>
<Display>Updated</Display>
<DataType>Date</DataType>
<Group>Requirement</Group>
</Column>
</Table>
</Results>
</ClientRequirementScreen>