Changes to Coverable arrays

In previous releases, coverage, condition, and exclusion arrays for coverables in the base configuration were not marked as owner=true. This caused situations in which different users adding coverages to the same coverable were not correctly identified by PolicyCenter as concurrent data change exceptions. To remedy this, all Coverable entities in the base configuration have been modified to make their Coverage, Condition, and Exclusion arrays owner=true.

Guidewire recommends that you examine your configuration and make similar changes to any Coverable entities you have defined. Be aware that setting owner=true has side effects, such as causing copies of the Coverable to be deep copies (including its child Coverage, Condition, and Exclusion entity instances) as opposed to shallow copies. Examine any custom code you have that copies coverables and make sure that this code does not also copy coverages, conditions or exclusions (since these will be copied when owner=true).