Role Shading and RoleScreen Access to Plan, Policy, Client and Address Fields Prototype
RoleScreen is an existing business rule, with all the existing functionality and the same is explained in earlier prototypes. The current Role Shading and RoleScreen Access to Plan, Policy, Client and Address Fields Prototype explains the features in OIPAthat enable role shading to be performed basis role status and detailed action/events using PLANFIELD, POLICYFIELD, Client and Address details for the role player in the action/events configuration.
Scenario 1
For a specific plan, the Max Issue Age for the plan is 70. In a given instance, the insured DOBis entered as 01/01/1940, a validation is carried out using the client details to find if the Client is within the age of 70 at IssueDate and hence Error is thrown “Max Issue Age for insured is 70 years” and does not allows the Role to get added.
Scenario 2
For an Insured role, the First Name is a required field. In a given instance, the insured Last Name is entered as "Harry" but no First Name is entered. By accessing the First and Last Name, the same is validated and an error message "First Name is required for the last name $$$Client:LastName$$$" is displayed and the role details are not recorded.
Scenario 3
For an Insured role, the gender value Unisex is allowed only in the USstate of Montana. In a given instance, the user selects an insured with gender 'Unisex' residing in a state other than Montana. An error message “For an Unisex Insured residence State needs to be Montana” and the Role is not added.
Scenario 4
For an Insured role, there is more than one role that is in deleted/Inactive status after some role changes are performed in the policy. For the Deleted/Inactive roles, the roles fields should not be available for edit and the role should be shaded differently to ensure the deleted/inactive roles are visible differently.
Prototype Configuration
- The existing transaction ‘RoleScreen’ BR in the Functional Prototype Plan is used for demonstrating the functionality associated with this feature. The following features are configured to demonstrate the same functionality:
For Scenario 1, two fields, MaxIssueAge from Plan Field with TYPE=”PLANFIELD” and PolicyEffectiveDate (treated as Issue Date) from Policy Field, TYPE=”POLICYFIELD”are configured in Role Screen Math. At the same time, Client:DateOfBirth is used as an EXPRESSION for fetching client’s date of birth, which acts as a parameter to ANBAgeOf(“ClientDOBMV”,”IssueDateMV) to calculate the Age on Issue Date of a client. Alternatively, Plan Date is also used as Issue date when user does not enters Policy Effective date which is an user enterable field, whereas Plan Date is always available, with a system defaulted date. Basis the Issue Age, appropriate error message is displayed, if necessary.
For Scenario 2, Client context variable, Client: FirstName is accessed in the validation to ensure the first name is available. If it is not entered, an error message is shown and the value for context variable Client:LastName is used in substitution.
For Scenario 3, Client’s gender is fetched configuring Client: Sex and Client state details by using the Address: StateCode in the actions and depending on the values for Sex and residence state code, an error message is displayed if Unisex is used with any state other than Montana.
- For Scenario 4, the role shading feature is enabled in the Prototype Company at the company level by using the CompanyCosmetics BR. This ensures the roles are shaded basis the role status. Please see section on RoleShading feature for details.
View Prototype in OIPA
- Log in OIPA using the Prototype Company user ID and password.
- Click Policy | New from the Main menu.
- Add a shell policy for the Functional Prototype Plan to test the prototype.
- Navigate to the Role Screen and enter input details as explained in each of the scenario to view the prototype functionality.
- Make one or more Roles Deleted/Inactive by using appropriate activities to see the Role Shading functionality.
-
Make changes to the various fields and check action/events as explained above to view the functionality.