You are here: Business Rules > Screen Rules > RoleScreen

Oracle® Insurance XML Configuration Guide Release 9.4.1.0 E23637_01

# RoleScreen

## Description

This business rule allows for the configuration of the Role screen and defines the dynamic fields that can be displayed and updated on the specified Role Detail(s) screens. The plan selected during the policy entry process dictates which role options are visible and available on the Role screen.

## RoleScreen Element/Attribute Table

Element/Tag | Definition | Attribute | Element/Attribute Value and Description
<RoleScreen> | The opening and closing tag for the business rule. |  |
<Role> | Required/Repeatable Element; Parent element that has sub- elements to hold required information or have available information for a specific role that is defined separately by this tag. | ROLECODE | Required Attribute; RoleCode The role code (as defined in AsCodeRole) that is to receive the definition described within the parent element.
|  | NAME | Provides a user-friendly description of the role affected by this definition.
<Fields> | Allows configuration of dynamic fields. . |  |
<SuccessorOnDelete> | Optional element; This element allows the system to replace one role with another upon deletion of the original role. |  | Required element value; RoleCode This is the role with which the original role should be replaced, upon its deletion. Note: The original role's RoleCode is specified in the <Role> tag. If the new role does not exist, then the user is warned with the same.
DELETEOLDROLE | Yes:Delete old role. No:Keep old role.
IGNOREONSTATUS | Optional Attribute; StatusCodes Indicates the case statuses where the role will not be replaced. The status codes are defined by the AsCodeStatus table.
<Events> | See Action/Events. |  |
<ScreenMath> | See Math Element. |  |
<Actions> | See Action/Events. |  |

## RoleScreen Image

## XML Example

<RoleScreen>

<Role ROLECODE=”13”>

<Fields>

<Field>

<Name>OverRideAddress1</Name>

<Display>Override Address</Display>

<DataType>Combo</DataType>

<Query TYPE=”SQL”>SELECT &ldots;. </Query>

</Field>

<Field>

<Name>Line</Name>

<Display></Display>

<DataType>Line</DataType>

</Field>

<Field>

<Name>Line</Name>

<Display></Display>

<DataType>Line</DataType>

<Field>

<Field>

<Name>AlternateCorrespondence</Name>

<Display>Correspondence to Alternate Address</Display>

<DataType>Text</DataType>

</Field>

<Field>

<Name>AlternateConfirmation</Name>

<Display>Confirmations to Alternate Address</Display>

<DataType>Text</DataType>

</Field>

<Field>

<Name>AlternateStatements</Name>

<Display>Statements to Alternate Address</Display>

<DataType>Text</DataType>

</Field>

</Fields>

</Role>

</RoleScreen>

## Schema Example

<RoleScreen>

<Role ROLECODE="[CodeString]">

<Fields> </Fields>

<SuccessorOnDelete DELETETOLDROLE="[Yes|No]" IGNOREONSTATUS="[StatusCode]">[RoleCode]</SuccessorOnDelete>

</Role>

</RoleScreen>

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

Open table of contents