You are here: Main Explorer Folders > Prototypes > New Prototype Samples For This Release > Segment Roles

Segment Roles

Segment functionality was enhanced to allow a user to assign and view roles assigned to a segment.

The SegmentRoleScreen business rule is a new rule that allows the user to configure the Segment Role screen and define the dynamic fields that can be displayed and updated on the specific role detail window.

When the segment is configured, the role characteristics are defined, such as the minimum/maximum number of roles allowed and cloning data from existing roles. The role detail can vary by segment and role combination.

Each segment will have distinct roles assigned to it, while the same client(s) may be assigned to multiple segments in the same role or in different roles.

The CopyToRoleFields business rule is used to update fields for multiple roles. Roles assigned to the Segment may also be created by transactions.

Segment Configuration Requirements

Create the Segment and configure it to establish and maintain roles as well as supply role views. Segments behave much like the PolicyScreen business rule in terms of Role creation, editing information provided at the detail level (minimum/maximum number of roles, percentages, disabling role fields), and client type designation. Segment fields, for example, DisableStatus and DisableRoleFields can be locked down and disabled based on the configuration pointing to the overall policy status. When the entire segment is locked down, disabled, no role deletions, additions, or changes are allowed. When the role fields are disabled Find Client and New Client are also disabled. Role Views are provided on the Segment to allow for the update of a field on multiple roles. Navigate to Global Explorer | Segments. The three segments used to demonstrate this functionality are RiderWithRoles, RiderWithClientAssignmentII, and RiderWithoutClientAssignmentII.
- RiderWithRoles: This segment demonstrates the use of Role Views associated with the display of information on the Role grid in OIPA. The Roles to be included in the view are configurable and roles can be repeated among different views. An optional attribute ALLROLES allows for view of all roles, otherwise, the default is displayed. The default view houses the following information for display on the role grid: Client Name, Role, Tax ID, Action, and Percent. In terms of the Percent, AllowZeroPercent or AllowPercent will be based on the element configured within the role for the particular Segment.
- RiderWithClientAssignmentII: This segment demonstrates the use of Client Assignment configuration. Client Assignment configuration was developed to satisfy the business need to clone existing roles from existing segments or to exclude specific clients already associated with a role on an existing segment. ClientAssignment, when checked, will limit the search result set during a 'Find Client' request to those clients defined by the role's ClientAssignment. ClientAssignment specifies information about cloning role detail and excluding assigned clients. CLONEROLEDETAIL stipulates whether the common role detail is cloned/copied to the new role. EXCLUDEASSIGNED generates a list of available clients not already assigned in previous acts of role designation to the same role code on the same segment. When assigned Yes, clients already assigned are removed from the list. The Source Segment provides the information for Client Assignment in terms of the Segment to use for copying of role detail and which roles to include/exclude. When cloning Role Detail, there must be a match in the field name between the source and destination segment.
- RiderWithhoutClientAssignmentII: This segment demonstrates no Segment Role Views or the presentation of default views when configuration depicting another view is absent.
The SegmentRoleScreen business rule is used to define the role detail at the field level. There is specific syntax within the SegmentRoleScreen business rule that allows dynamic role fields to be shared across multiple roles for segments.
There are eight transactions configured to demonstrate the segment role functionality. The purpose of each transaction is provided below.
- CopyToWithALLROLES: This transaction demonstrates the use of the attribute ALLROLES associated with the element SegmentRoles used in the CopyToRoleFields rule configuration. It demonstrates the use of Test elements in the CopyToRoleFields rule. Configuration stipulates that the RoleRelationship field will be updated only for those segments whose type code is not 72 (72 is Rider Without Client Assignment). Navigate to Global Explorer | Transactions | CopyToWithALLROLES (Functional Prototype Plan).
- CopyToWithoutALLROLES: This transaction demonstrates the use of a Role Code in the CopyToRoleFields business rule to determine which role is updated. The transaction allows the user to select a segment and limits the list of available roles in the drop down based on the roles added to the segment selected. CopyToRoleFields in terms of Segments, provides the capability to update field level information to all of the Segment's roles (with the exception of the CSR) by using the ALLROLE attribute. An Individual/single role may be updated specifically, by using the ROLECODE attribute. And From and To and (FromCollection) elements provide a method for passing the applicable data to the role specified. Conditions, Statements, and Tests serve as qualifiers in the configuration to determine if the role should be updated or not. ROLEPERCENT and ROLEAMOUNT can be updated. Activity Field level values can be updated. Undo/Redo or Reversal processing reverts the values back prior to when activity processing was executed to copy to the role field(s). Navigate to Global Explorer | Transactions | CopyToWithoutALLROLES (Functional Prototype Plan).
- CopyToFromCollection:This transaction demonstrates the use of the CopyToRoleFields rule using Collection configuration in the transaction. Navigate to Global Explorer | Transactions | CopyToFromCollection (Functional Prototype Plan).
- SegmentRolesRolesExist: This transaction demonstrates the use of the RolesExist business rule with Segment roles. Configuration within the rule demonstrates the use of Validations and InterRoleRules. The RolesExist business rule allows for the validation of Roles within the segments including InterRoleRules and AgeValidation. For example, InterRoleRules will validate that two roles are served by two separate and distinct clients as in the case where the insured and the beneficiary cannot be the same client. AgeValidation will ensure the client's age is appropriate for the designation to the role. For example, the client who occupies the Insured's role, must meet the age range requirement set forth under the plan guidelines. Navigate to Global Explorer | Transactions | SegmentRolesRolesExist (Functional Prototype Plan).
- SegmentRolesAddRoles: This transaction demonstrates the use of the AddRoles business rule with Segment roles. The AddRolesbusiness rule allows the user to select the client designation, the role designation and the segment to update using the configuration elements for this business rule. The AddRoles business rule allows for the creation of new roles on a particular segment (via the SegmentGUID attribute) when the attached rule is executed on the transaction processed. Navigate to Global Explorer | Transactions | SegmentRolesAddRoles (Functional Prototype Plan).
- SegmentRolesCreatePolicy: This transaction demonstrates the use of the CreatePolicy business rule with Segment roles. The CreatePolicy business rule allows for creation of roles at the policy level and segment level. The Roles from the existing source segment as defined by the SEGMENTNAME attribute can be copied and created as the new segment on the new policy. If the attribute(COPYSOURCE) value is set to No, then the role's section will be generated without the use of copying from the source. From and To elements will provide a vehicle (if copying) for passing the information from the source segment roles to the new segment's roles. Navigate to Global Explorer | Transactions | SegmentRolesCreatePolicy (Functional Prototype Plan).
- SegmentRolesCOPYALLROLES: This transaction demonstrates the use of CreatePolicy business rule using the attribute of COPYALLROLES. COPYALLROLES is an indicator (Yes|No) that determines whether or not to copy all of the segment roles from the source policy segment to the new policy's segment. Navigate to Global Explorer | Transactions | SegmentRolesCOPYALLROLES (Functional Prototype Plan).
- SegmentRolesCreateSegments: This transaction demonstrates the use of the CreateSegments business rule with Segment roles. The CreateSegments business rule allows for the creation of multiple Roles and Role Detail fields on a specified segment. The RoleCode, SegmentName, and StatusCode all apply during the configuration of the business rule. In addition, the From and To sections allow for passing along field level information to the newly created segment. Navigate to Global Explorer | Transactions | SegmentRolesCreateSegments (Functional Prototype Plan).