Product editions

Product editions define product model properties and subclause relationships for product lines. Each product line has a Base edition that defines product model properties and subclause relationships for the base product line. You can use product editions to introduce changes to the product after a product has gone into production. Typically, products start out with only the Base edition. Create additional editions if there is a filing or other business reason to change the product as of a certain effective date.

  • The Base edition defines product model properties for the product line.
  • Editions have an effective date.
  • Editions have an expiration date.
  • You can create different editions based on the values of certain dimensions, such as jurisdiction, brand, channel, partner, organization, and business type.
With product editions, you can:
  • Change an insurance product line after it has gone into production
  • Load product model properties into an installed product
In a policy transaction, either with installed or visualized product, PolicyCenter selects the edition based on the Effective Date, the Expiration Date, and the Segment Details.

Overlapping editions

Every edition has a date range bounded by its effective date and its expiration date. Overlapping editions are two or more editions that have identical values for jurisdiction and other segments and have overlapping date ranges. Workset Manager does not allow a workset to be promoted to production status if there are two or more editions in effect at the same time. However, for non-production worksets, it is possible to have overlapping editions. For example, when cloning or importing a product, you might have overlapping editions because all editions from all parent worksets are now stored in the draft workset. To resolve this issue, you must adjust the effective dates and expiration dates on the Editions tab to ensure that there are no overlapping editions.