Merging changes details

This section describes the rules PolicyCenter uses when merging changes for out-of-sequence jobs. In this topic, the phrase the same object means objects with the same fixed ID (matching FixedID property values). The fixed ID is discussed further in Policy revisioning.

General rules for merging changes are:

If an out-of-sequence job adds an object, later effective date slices include the addition.
If an out-of-sequence job removes an object, later effective date slices include the addition.
If an out-of-sequence job changes a property on an object, later effective date slices include the addition only if the later effective date slices do not change that property. When the same property on the same object is changed in both branches, if the values are different, this is an out-of-sequence conflict. The user must review changes in the out-of-sequence conflicts tab before binding the job. See Out-of-sequence jobs for details.
Note: Many types of changes in an out-of-sequence job are not out-of-sequence conflicts. All entity instance add or removals are not conflicts since they always override the later effective date slices. Even property changes are not conflicts if later slices do not modify that property.
If merging changes causes validation errors, users must choose new values for properties manually. See Validation issues and out-of-sequence jobs for related discussion.

The following table lists many examples of how PolicyCenter merges changes for out-of-sequence jobs. In the table, Merged Result means, If you look at the policy on the later effective date, this is the result after PolicyCenter merges changes.

Out-of-sequence change	Later effective date slice changes	Merged result
Car 3 is added to the policy	Car 2 is removed from the policy	Car 3 remains. Car 2 is removed. Car 3 is still numbered “3”.
Car 3 is added, garaged in CA	Auto Liability limit for CA is increased from 15/30/15 to 100/300/50 and the changes are applied (automatically) to Cars 1 and 2 (because it is a jurisdiction-level coverage).	Car 3 exists and has the new, higher limit.
Auto Liability limit for CA is increased from 15/30/15 to 100/300/50 and the changes are applied (automatically) to Cars 1 and 2 (because it is a jurisdiction-level coverage).	Car 3 is added, garaged in CA. It initially has the lower liability limit in effect as of the effective date for the earlier change.	Car 3 exists and has the new, higher limit for the jurisdiction-level coverage.
Car 3 is added with Collision deductible set to the then-standard 500.	The Collision coverage deductibles are changed from 500 to 250 for all the cars on the policy, which does not include Car 3 at this time.	Car 3’s deductible is not changed. The other cars have the lower deductible.
The Collision coverage deductibles are changed from 500 to 250 for all the cars on the policy (which does not include Car 3 at this time).	Car 3 is added with Collision deductible set to the then-standard 500.	Car 3’s deductible is not changed. The other cars have the lower deductible.
Car 1 is removed from the policy.	The Collision deductible for Car 1 is changed from 500 to 250.	Car 1 is removed from the policy. It is as if the limit change never occurred because those coverages were already gone by effective date of the later effective date change.
The CA car is removed, causing all jurisdiction-level coverages tied to Vehicles to be removed.	The Auto Liability limit for CA is changed from 15/30/15 to 100/300/50. The policy has only 1 car in CA.	The CA car and CA jurisdiction-level coverages are removed. It is as if the limit change never occurred because those coverages were already gone by effective date of the later effective date change.
The Basic PIP coverage limit for a vehicle is changed from 10k to 20k.	The vehicle is changed from type Private Passenger to Special because it is actually a dune buggy. PIP coverage no longer applies, so it is removed.	The car is type Special and PIP coverage is gone, so the limit change no longer applies.
The garage location for all the vehicles on the policy is changed from CA to the insured’s new address in AZ. This also requires switching the Collision deductible from 250 to 500 (because 250 is not available in AZ, for example).	A new car is added with deductible 250, like the others.	This actually depends on whether the garage location was edited or a new location added. If a new location is added, the new vehicle would still be listed at the old location. If a garage location was edited, the new car is now in a new jurisdiction and its deductible is no longer available. The user must select a valid choice. However, PolicyCenter does not support editing the Jurisdiction of a location. If the garaging location changes, instead add a new location for the new garaging location and remove the old one.
A WC class code (exposure) is added.	The Employer Liability Limit (line-level coverage) is increased.	The exposure is tied to the new, higher limit.
The Employer Liability Limit (a line-level coverage) is increased.	A WC class code (exposure) is added.	The exposure is tied to the new, higher limit.
A WC class code (exposure) is edited to increase the amount from 100k to 120k.	The class code description property on the same exposure is edited to adjust the description.	The exposure has the new description and amount is 120k.
The class code description property on a WC exposure is edited to adjust the description to “Description at Time A”.	The class code description property on a WC exposure is edited to adjust the description to “Description at Time B”.	This is a merge conflict, and the result could be either value. This is handled by the Change Conflicts tab.
A BOP policy was written with coverage form = Basic (property on `PolicyLine`). It is now changed to Broad.	Coverage form is changed to Special.	This is a merge conflict, and the result could be either value. This is handled by the Change Conflicts tab.
Building added to a property policy	Policy level discount added	Discount and new building on the policy.
A car (garaged in CA) is changed from “Special” to “Private Passenger”.	The car’s garage location is changed to KY, which is a PIP jurisdiction. As of time B, the car is Special, so PIP coverage does not apply.	The car is now Private Passenger, which means that new coverages would apply, such as Basic PIP. These new coverages must be added if they are available and standard. However, a user would need to select values for the coverage terms. If available but not standard, the user must elect where to accept the coverage.