RolesExist

This business rule, when attached to a transaction, allows for configuration of multiple validations. Specifically, the ability to identify which roles cannot be assigned to the same person (i.e.Client) age validations, and identification of role fields that must be populated. This rule must be listed in TransactionBusinessRulePacket.

RolesExist: Elements and Attributes
Element/Tag Attributes Parent Element Description Element/Attribute Values

<RolesExist>

 

  

The opening and closing tag for the business rule.

  

<Role>

 

 <RolesExist>

Required, repeatable:

Opening tag of the role section.

 

<RoleCode>

 

 <Role>

Required :
Defines the role codes that must exist on the policy.

 

Required value:
Code: RoleCode (As defined in AsCode table=>AsCodeRole).

  

<FieldsExist>

 

 <Role>

Optional:
The element tag listsfields that must exist on the role and have a value other than null.

 

<Field>

 

 <FieldsExist>

Required, repeatable:

<FieldsExist> tag is used to ensure that certain required fields are filled in, at the time of running the transaction.

 

Required value:
String: Field name from the GROUP attribute.

  

GROUP

  

Required attribute:
String: Client, Role, Person, Organization  

Indicates the table/screen that stores the field being referenced.

  

DISPLAY

  

Required attribute:
String: Provides a user friendly name that is inserted into the error message when the field does not pass validation.

  

<FieldsDoNotExist>

 

 <Role>

Optional:
<FieldsDoNotExist> tag is used to ensure that certain required fields are empty, at the time of running the transaction.

 

<Field>

 

 <FieldsDoNotExist>

Required, repeatable:
Defines the field to verify if the field value does not exist on the Client screen of the client which is assigned to the specified role code.

 

Required value:
String: Field name from the GROUP attribute.

  

GROUP

  

Required attribute:
String: Client, Role. Indicates the table/screen that stores the field being referenced. Available groups are limited to CLIENT and ROLE.

  

DISPLAY

  

Required attribute:
String: Provides a user friendly name that is inserted into the error message when the field does not pass validation.

  

<InterRoleRules>

   <RolesExist>

Optional:

<InterRoleRules> applies dependencies between roles.

  

<MustBeDifferent>

   <InterRoleRules>

Required, Repeatable::


This element lists the roles whose clients must not be the same.

  

ROLE1

  

Required:

Code:

RoleCode(As defined in AsCodetable=> AsCodeRole)

  

ROLE2

  

Required:

Code:

RoleCode(As defined in AsCodetable=> AsCodeRole)

  

<Validations>

   <RolesExist>

Optional:

This element defines age related validations.

  

<AgeValidation>

   <Validations>

Required, repeatable:

Defines the age validation for each role.

  

ROLE

  

Required:

Code:

RoleCode (As defined in AsCode table=>AsCodeRole)

  

DISPLAY

  

Required:

Provides a user friendly name that is inserted into the error message when the age does not pass validation.

  
MINIMUM   Required:

Minimum age.

Defines the minimum age for the role.

  

MAXIMUM

  

Required:

Maximum age.

Defines the maximum age for the role.

  

<Events>

   

See Actions/Events.

 

<ScreenMath>

    

See ScreenMath Element.

  

<Actions>

    

See Actions/Events.

 

<Segments>

   <RolesExist>

Optional:

 

<Segment>

 

   <Segments>

Required, repeatable:

Identifies the segment by its name on which roles are validated. Although the element is repeatable, the segment name cannot be repeated.

  
SEGMENTNAME  

Required:

SegmentName

  

<Role>

   <Segment>

Required, Repeatable:

Opening tag for the role section.

  

<RoleCode>

   <Role>

Required:

Defines the role codes that must exist on the segment.

  

<FieldsExist>

   <Role>

Optional:

The element lists fields that must exist on the role and have a value other than null.

  

<Field>

   <FieldsExist>

Required, repeatable:

Defines a field name that must exist.

  

GROUP

  

Required:

String: Client, Role

Indicates the table/screen that stores the field being referenced.

  

DISPLAY

  

Required:

String: Provides a user friendly name that is inserted into the error message when the field does not pass validation.

  

<FieldsDoNotExist>

 

 <Role>

Optional:
<FieldsDoNotExist> tag is used to ensure that certain required fields are empty, at the time of running the transaction.

 

<Field>

 

 <FieldsDoNotExist>

Required, repeatable:
Defines the field to verify if the field value does not exist on the Client screen of the client which is assigned to the specified role code.

 

Required value:
String: Field name from the GROUP attribute.

  

GROUP

  

Required attribute:
String: Client, Role. Indicates the table/screen that stores the field being referenced. Available groups are limited to CLIENT and ROLE.

  

DISPLAY

  

Required attribute:
String: Provides a user friendly name that is inserted into the error message when the field does not pass validation.

  

<InterRoleRules>

   <Segment>

Optional:   

Applies dependencies between roles.

  

<MustBeDifferent>

   <InterRoleRules>

Required, Repeatable:

This element lists the roles whose clients must not be the same.

  

ROLE1

  

Code:

RoleCode(As defined in AsCodetable=> AsCodeRole)

  

ROLE2

  

Code:

RoleCode(As defined in AsCodetable=> AsCodeRole)

  

<Validations>

   <Segment>

<Validations> is used to perform certain age related validations.

  

<AgeValidation>

   <Validations>

Required, repeatable:

Defines the age validation for each role.

  

ROLE

  

Required:

Code:

RoleCode (As defined in AsCode table=>AsCodeRole)

  

DISPLAY

  

Required:

Provides a user friendly name that is inserted into the error message when the age does not pass validation.

  

<Minimum>

   <AgeValidation>

Required  

Minimum age for the specified role.

  

<Maximum>

   <AgeValidation>

Required  

Maximum age for the specified role.

  

 XML Schema

<RolesExist>

<Role>

<RoleCode>role code</RoleCode>

<FieldsExist>

<Field GROUP="object name" DISPLAY="string">FieldName</Field>

<Field GROUP="[Client|Organization|Person]" DISPLAY="string">FieldName</Field>
</FieldsExist>

<FieldsDoNotExist>

<Field GROUP="object name" DISPLAY="string">FieldName</Field>

</FieldsDoNotExist>

</Role>

<Role>

<RoleCode>role code</RoleCode>

</Role>

<InterRoleRules>

<MustBeDifferent ROLE1="" ROLE2=""/>

</InterRoleRules>

<Validations>

<AgeValidation ROLE="" DISPLAY="" MINIMUM="" MAXIMUM="">

<Minimim></Minimum>

<Maximum></Maximum>

</AgeValidation>

</Validations>

<Segments>

<Segment SEGMENTNAME="">

<Role>

<RoleCode>role code</RoleCode>

<FieldsExist>

<Field GROUP="object name"
DISPLAY="string">FieldName</Field>

</FieldsExist>

<FieldsDoNotExist>

<Field GROUP="object name" DISPLAY="string">FieldName</Field>

</FieldsDoNotExist>

</Role>

<InterRoleRules>

<MustBeDifferent ROLE1="" ROLE2=""/>

</InterRoleRules>

<Validations>

<AgeValidation ROLE="" DISPLAY="">

<Minimum></Minimum>

<Maximum></Maximum>
</AgeValidation>

</Validations>

</Segment>

</Segments>

</RolesExist>

XML Example

<RolesExist>

<Role>

<RoleCode>01</RoleCode>

<FieldsExist>

<Field GROUP="Client" DISPLAY="SSN/TIN">TaxID</Field>

<Field GROUP="Client" DISPLAY="DOB">DateOfBirth</Field>
<Field GROUP="Organization" DISPLAY="Organization Name">OrganizationName</Field>
<Field GROUP="Person" DISPLAY="FirstName">FirstName</Field>

</FieldsExist>

</Role>

<Role>

<RoleCode>23</RoleCode>

</Role>

<Role>

<RoleCode>37</RoleCode>

</Role>

<Role>

<RoleCode>82</RoleCode>

</Role>

<Segments>

<Segment SEGMENTNAME="RiderWithRoles">

<Role>

<RoleCode>37</RoleCode>

<FieldsExist>

<Field GROUP="RoleField" DISPLAY="Common Role Field">CommonRoleField</Field>

</FieldsExist>

<FieldsDoNotExist>
<Field GROUP="Client" DISPLAY="Date Of Death">DateOfDeath</Field>
</FieldsDoNotExist>
</Role>

<Role>

<RoleCode>49</RoleCode>

<FieldsExist>

<Field GROUP="RoleField" DISPLAY="Common Role
Field">CommonRoleField</Field>

</FieldsExist>

</Role>

<InterRoleRules>

<MustBeDifferent ROLE1="37" ROLE2="49"></MustBeDifferent>

</InterRoleRules>

<Validations>

<AgeValidation ROLE="49" DISPLAY="Payer age less than 20 or greater than 60">

<Minimum>20</Minimum>

<Maximum>60</Maximum>

</AgeValidation>

</Validations>

</Segment>

<Segment SEGMENTNAME="RiderWithClientAssignmentII">

<Role>

<RoleCode>37</RoleCode>

<FieldsExist>

<Field GROUP="RoleField" DISPLAY="Common Role
Field">CommonRoleField</Field>

</FieldsExist>

<FieldsDoNotExist>
<Field GROUP="Client" DISPLAY="Date Of Death">DateOfDeath</Field>
</FieldsDoNotExist>
</Role>

</Segment>

<Segment SEGMENTNAME="RiderWithoutClientAssignmentII">

<Role>

<RoleCode>37</RoleCode>

</Role>

</Segment>

</Segments>

</RolesExist>