What are Custom Status Labels?
Custom Status Labels allow Carriers to override the default policy status labels within BriteCore with terminology that better fits their workflows or regulatory requirements. This feature provides flexibility for both agent and administrative users, but the settings below pertain to administrator functionality.
Setting 1: use-custom-status-labels-for-admin
Purpose:
This setting determines whether custom status labels should be displayed for admin users throughout the BriteCore admin interface.
How to Use:
Set this option to true (enabled) to have the system display custom status labels (as defined in the custom-status-labels setting) for admin users. Set this option to false (disabled) to continue displaying BriteCore’s default policy status labels.
How to Configure:
Access Advanced Settings: Navigate to the Advanced Settings in the BriteCore admin interface. Find use-custom-status-labels-for-admin: Locate the setting in the list. Enable or Disable: Set to true to enable custom labels for admins. Set to false to use default system labels. Save your changes.
Setting 2: custom-status-labels
Purpose:
Defines the actual custom labels for policy statuses to be used when the above setting is enabled. This is a mapping of system statuses to your chosen labels.
How to Use:
Specify a JSON object that maps each internal policy status (like “Unsubmitted”, “Active”, “Cancelled”, etc.) to your preferred label. When use-custom-status-labels-for-admin is enabled, these labels will appear for admin users throughout the admin interface.
How to Configure:
Access Advanced Settings: Go to the Advanced Settings section in the admin interface. Find custom-status-labels: Locate the setting and enter your custom label mappings as valid JSON.
Example Mapping:
{
"Unsubmitted": "Applications Not Sent",
"Submitted": "Applications Sent",
"Rejected": "Applications Denied",
"Active": "Policies In Force",
"Cancelled": "Policies Cancelled",
"Expired": "Policies Expired"
}Save your changes.
Note:
If a status is not mapped, the system will use the default label for that status. Improperly formatted JSON may result in the default labels being used. This mapping only affects the labels for users governed by the relevant enablement setting (admin or agent).