Split risk objects in a policy transaction

About this task

In a policy transaction, you split the risk object and can modify independently the values of the split fields. Any number of splits may be performed on risk objects. Different risk objects may have different numbers of splits or different split dates.
Note:

Because the Split button is on the risk objects tab, you can only split child risk objects of the product line and not the line itself.

Procedure

  1. In a policy transactions for a policy line that has risk objects that can be split, advance to Risk Details and select the risk objects tab.
  2. Add the risk object that can be split.
    For risk objects that can be split, Effective Date and Expiration Date appear in the list view and the Split button appears above the list.
  3. Select one or more of these risk objects to enable the Split button.
  4. Click Split.
    The Split Risks popup appears.
  5. Choose the Date on which to split the risks and click Split.
    An error appears if the date is outside the policy period range or if a split already exists on the given date.

    After a successful split, there are two versions of the risk object. You can click to view either version of the risk object but only fields that can be split are editable in the second version.

    Both versions initially have the same data, except for scalable fields which are prorated based on the split date. You can edit splittable fields independently in both versions. Fields that cannot be split are editable only in the first version. Upon save, changes made in the first version propagate to the second version.

    You can Remove or Split the first version of an risk object only. Removing a risk object removes all versions. There is no way to remove a single version. There is no way to undo the split to a risk object.
    Note:

    The risk object popup lets you edit other product elements besides fields, such as clauses, exposures and child coverables. In the base implementation, these elements are independently editable in both versions of the risk object.