You are here: Business Rules > Screen Rules > RequirementsScreen

Oracle® Insurance XML Configuration Guide Release 9.4.1.0 E23637_01

# RequirementsScreen

## Description

This business rule is used to configure the applicable fixed fields for the Requirements screen. At this time, the only configuration needed for the Requirement screen is an empty opening and closing tag. Any additional configuration in the rule is not supported at this time.

## RequirementsScreen Element/Attribute Table

Element/Tag | Definition | Attribute | Element/Attribute Value and Description
--- | --- | --- | ---
<RequirementsScreen> | Required opening and closing tags of the business rule. |  |
<FixedFields> | Optional tag Allows configuration of 'above the line' fields. |  |
<Categories> | Optional Element; Allows configuration of categories from AsLinkrequirement table. Normally Requirements Screen loads all requirements from the AsLinkRequirement Table. This tag is used to control/filter the Requirements to be displayed on the Requirements Screen. When this tag is present in this rule then the Requirements screen will load the drop-down filtered by the Category list. Note: A column called CategoryCode should be present in the AsLinkRequirement table. The corresponding description for that category will be maintained in AsCode Table named as AsCodeRequirementCategory. |  |
<Category> | Required / Repeatable Element; This element is used to specify the Requirement Category. |  | Required Element Value; RequirementCategoryCode A valid CategoryCode form the AsLinkRequirement data base table. These codes are defined in AsCode => AsCodeRequirementCategory table Example:<Category>01</Category>
<Validation> | See Validation. |  |
<Events> | See Action/Events. |  |
<ScreenMath> | Refer to Math Element. |  |
<Actions> | See Action/Events. |  |

#### Additional Notes:

The global RequirementsScreen business rule should only consist of an empty opening and closing tag.

The Requirement screen contains two parts:

- the required documents needed for that Policy (what documents are required is defined in the GeneratePendingRequirement business rule) .
- the dates (The dates that must be updated are specified in theDeliveryRequirement business rule).

RequirementsScreen works together with GeneratePendingRequirement and DeliveryRequirement business rules.

- GeneratePendingRequirement is used to define the list of requirements that needs to be satisfied prior to processing certain activities.
- DeliveryRequirement specifies the dates that must be updated for these requirements (These dates are Date Received, Date Waived, Date Requested and Date Due ).

These two rules should be attached to the transaction along with the Transaction Business Rule Packet, and Transaction Cosmetics business rule to generate the requirements at the activity level.

## XML Example

    <RequirementsScreen>

    <Table>

    <Column WIDTH="260" ALIGN="CENTER" FORMAT="Text">

    <Name>RequirementDescription</Name>

    <Display>Description</Display>

    <Group>Requirement</Group>

    <DataType>Text</DataType>

    </Column>

    <Column WIDTH="100" ALIGN="CENTER" FORMAT="Text">

    <Name>RequirementStatusCode</Name>

    <Display>Status</Display>

    <Group>Requirement</Group>

    <DataType>Text</DataType>

    <Disabled>Yes</Disabled>

    </Column>

    <Column WIDTH="100" ALIGN="CENTER" FORMAT="Text">

    <Name>RequirementOpenDate</Name>

    <Display>Date Added</Display>

    <Group>Requirement</Group>

    <DataType>Date</DataType>

    <Disabled>Yes</Disabled>

    </Column>

    <Column WIDTH="100" ALIGN="CENTER" FORMAT="Text">

    <Name>RequirementCloseDate</Name>

    <Display>Date Accepted</Display>

    <Group>Requirement</Group>

    <DataType>Date</DataType>

    </Column>

    </Table>

    </RequirementsScreen>

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

Open table of contents