Considerations and Limitations in Insurance Brokerage

Here are some considerations and limitations to keep in mind about Brokerage features.

Available in: Lightning Experience

Available in: Professional, Enterprise, and Unlimited Editions where Financial Service Cloud and Insurance Brokerage are enabled

Splits

The split arrangement search feature doesn't support special characters.
When using the Offset Duration in Producer Split Assignment, the end date for the first assignment and the effective date of second assignment is populated with a date that's one day later than it should be. The workaround is to update the date manually.
The dynamic enum values can’t be cleared once they're selected. The workaround is to delete thes row needs to be deleted.
In-bulk reassignment, only 50 records can be reassigned at once.

The Insurance Rate Plan ID and Type fields can't be selected from Visible columns in Rate Plan Type Configuration.
The dynamic enum values can’t be cleared once they're selected.
Deleting empty rows in data table.
The API names need to be manually entered for Context Definition, Expression Set Definition, and Batch Process Job Definition for Insurance Policy Lifecycle Configuration, Policy Management, and Commission Processing repsectively.
On saving commission statement line item type configuration, if required field is not set,the error shows API names of the respective fields instead of labels.
Localization is not complete for all labels.

The maximum number of entities in context definition is 50 and for the context persist API is 15 entities. Hence, customers can extend out-of-the-box context definition and add a maximum of 500 attributes, but can't add more than 15 entities.
The maximum number of records in the insurance policy hierarchy is 40,000.

The maximum number of batch jobs available is 5.
For the book of bsusiness split type, the Producer Allocation Amount field isn't visible as a related list.

Did this article solve your issue?

Let us know so we can improve!