Loading editions into generated product

Editions contain the product model properties and subclause (parent-child clause) relationships. After generating the product, you can load editions into the product running in PolicyCenter.

  • You create editions in the visualized product line.
  • The product template contains the editions.
  • The editions are stored in the PolicyCenter database after loading the template for the generated product.
  • Subclause relationships are in the base edition.
Note: Generating the product creates the artifacts needed for PolicyCenter including PCF files, the product model, and entity model. But generating the product does not include editions.

After loading editions, you activate the editions to make them active in the generated product. The rules take effect immediately after activation. Rules in the new editions may cause validation issues to appear or disappear from open policy transactions. Validation issues can even appear or disappear from quoted policy transactions.

See also

Editions are deployed into a running PolicyCenter instance

You load editions into a running PolicyCenter instance.

If you make product changes that are completely contained within editions, the changes are not to the generated product. Therefore, you can load the editions into the product without first regenerating and redeploying it.

Changes that are completely contained within editions include:

  • Changes to product model properties
    • Field usage
    • Clause availability and existence
    • Default, minimum, or maximum values
  • Changes to subclause relationships that do not include structural changes
    • For example, you add or remove subclause relationships, but you do not add or remove any clauses or clause terms.

Structural changes require regenerating the product

Modifying editions can introduce structural changes to the product line.

These kinds of changes include but are not limited to:
  • Adding a new risk object, clause, attribute, or other structural element.
  • Adding a new clause, such as a coverage, and making it available starting on September 1st for all policies.
  • Changing the label of an attribute or a clause. For example, changing the wording of a question attribute.
  • Changing the name of a risk object or clause.

Adding or removing subclause relationships, without adding or removing clauses or clause terms, is not a structural change.

Before loading editions with structural changes, you must regenerate and redeploy the product in PolicyCenter.