Administrator Guide > Account and Role Types > Role Types |
This page is used to manage Role Types within the Lifecycle Management Suite. Role Codes provided by the host must be added to the Role Type list within the system. The following columns display on the Role Type Administration page:
Column Name | Description |
Role Code | Used to assign roles imported from the core to Role Types within the Lifecycle Management Suite. Role Codes can also be assigned to secondary roles in Role Mappings. Role Codes must match exactly the codes that are being provided in the file to be imported. |
Role Description | Denotes the full name of the Role Type. |
Liability Role | If selected, denotes that the Role Type is considered a liability role on an account. |
Last Modified | Denotes when the Role Type was last modified in the Lifecycle Management Suite. |
Modified By | Denotes what user made the last modification on the Role Type. |
By navigating to the System Management > Role Types page, administrators can create new role codes, edit existing role codes, set role mappings, delete existing role codes, copy existing role codes, refresh role codes, and print the role codes grid.
All role types share common attributes that are defined while creating, copying, or editing a role type.
Field | Description | ||
Role Code | Enter the role code provided by the host. This is a required field. | ||
Role Description | Denote the full name of the Role Type. This is a required field. | ||
Recovery ECOA Code |
Select the applicable Equal Credit Opportunity Act (ECOA) Code for the responsible individual on an account. The following options are available within the drop-down:
|
||
Liability Role | Select the check box to identify the Role Type as a liability role on an account. |
Located above the grid is the Role Mappings button. This feature allows administrators to map specific role types to secondary fields. Although the Lifecycle Management Suite imports all roles and people from the core, the system allows for up to eight secondary roles to be mapped to specific fields in the field list.
![]() |
If more than one role code is mapped to a specific role mapping and there is a person that holds each of the roles on the account, the system maps the first person that matches the role on the account. Also, if there are two people that hold the Joint Owner role, then the system imports the first person that has that role in the file. |
This feature is useful when building letters within the Lifecycle Management Suite. For example, when building a letter template in the letter template editor, secondary role fields are available to include in the letter template. If Joint Owner is mapped as Secondary 2 and Secondary 2 fields are included in the letter template and have a role on the account, the template populates the Joint Owner’s information. This allows for both the Primary and Joint Owner’s information to be populated in the same letter template.
![]() |
The primary role code within the database is imported into the Lifecycle Management Suite and automatically mapped to all letters upon completion of the first batch import. For more information, please see the connector guide for the applicable core interface. |