Editions high-level workflow
These high-level steps show how editions move from a non-production PolicyCenter development environment to PolicyCenter in production mode.
About this task
Editions are created on the product line. You create editions in the visualized product in
a non-production environment. Editions, including the Base edition
that defines the base product line, contain the product model properties and subclause
relationships.

Procedure
-
In a non-production environment of PolicyCenter, develop the
product structure and editions.
The editions group product model properties by effective date. The Base edition contains product model properties and subclause (parent-child clause) relationships without an effective date.
-
If necessary, generate the product code in the non-production environment.
Generating the product code is necessary the very first time a product is created. After that, you need to generate when you make structural changes. For more information, see Structural changes apply to all editions.PolicyCenter artifacts, such as PCF files, the entity model, and the product model, are created. Use Guidewire development tools, such as Studio, to work with these files.
Editions are not included in the generated product.
- If you generated the product code in the previous step, recompile and restart PolicyCenter.
-
For testing, load editions into the generated product in the non-production
environment.
- Export the template from the visualized product.
-
Load the editions from the template into the generated product.
The editions are stored in the PolicyCenter database.
-
In a production environment of PolicyCenter, deploy the product code.
This step is necessary if you made structural changes to the product.
This step requires recompiling PolicyCenter.
-
Load editions to production PolicyCenter.
- Export the template containing editions from non-production PolicyCenter.
-
Load the editions from the template into production PolicyCenter.
The editions are stored in the PolicyCenter database.
