Generated product files
Generating a product creates files in the PolicyCenter_installation/modules/configuration/config directory of PolicyCenter.
- XXX and xxx – The three character product abbreviation in upper and lower case
- YYY and yyy – The three character product line abbreviation in upper and lower case
- ProdId – Product identifier
- LineId – Line identifier
- Line – Short name of the product line
- Clause – Short name of the clause
- Typelist – Short name of the typelist
- Risk – Short name of the risk object
System files
Information about the product line appears at the end of the following files. Paths are relative to PolicyCenter_installation/modules/configuration/config.
When regenerating the product, you are not warned about modified files.
| Subdirectory | File name | Description |
|---|---|---|
| locale | display.properties | Display labels for screens. Generates labels for all languages defined by the
product. In Studio, if you add a display label that is not generated, the display key remains intact after regenerating the product. |
| productmodel.display.properties | Display labels for user interface fields for all languages defined by the product. | |
| typelist.properties |
For all languages defined by the product:
|
|
| lookuptables | lookuptables.xml | Lookup table for all product model patterns. |
Resources
Product generation adds files to the resources directory under PolicyCenter_installation/modules/configuration/config.
When regenerating the product, you are not warned about modified files. The files yyycostdef.xml, XXXDiffTree.xml, and YYYDiffTree.xml are exceptions.
| Subdirectory | Directory or File name | Description |
|---|---|---|
| systables.xml | Cost definition for the product
line: |
|
| diff | XXXDiffTree.xml |
Before regenerating the product, you will receive a warning about modified files that will be overwritten if you proceed. |
| productmodel | policylinepatterns/LineId | |
| products/ProdId | ||
| systables | costcode_ext.xml | |
| yyycostdef.xml |
Before regenerating the product, you will receive a warning about modified files that will be overwritten if you proceed. |
|
| underwriting_companies.xml |
For each
jurisdiction:
|
Product model
Product model files are in the resources/productmodel/products directory under PolicyCenter_installation/modules/configuration/config.
When regenerating the product, you are not warned about modified files.
| File name | Description |
|---|---|
| ProdId/ProdId.xml |
These files are generated once. You can make changes, and your changes will not be overwritten when you regenerate. |
| ProdId/ProdId-lookups.xml |
Update availability in Product Designer
If possible update availability in Advanced Product Designer. If Advanced Product Designer does not support a particular type of availability, you can make updates directly in Product Designer.
The first column of the table describes the update you make in Product Designer. The second column describes what happens in Studio when you commit the change in Product Designer. The third column describes what happens when you regenerate the product in Advanced Product Designer.| Product Designer | Studio | After regenerating product |
|---|---|---|
| Availability on Product | Availability criteria is updated in
ProdId/ProdId-lookups.xml. Availability criteria for a jurisdiction is updated in ProdId-lookups.xml in the ProdId/jurisdictions/XX/coveragepatterns directory, where XX is the jurisdiction. |
Updates in all ProdId-lookups.xml files remain intact. |
Update offerings in Product Designer
Advanced Product Designer does not support offerings. You can specify offerings for your product in Product Designer.| Product Designer | Studio | After regenerating product |
|---|---|---|
| Add offering | XXXOffering.xml and XXXOffering-lookups.xml created in the ProdId/offerings directory, where XXX is the name of the offering. |
XXXOffering.xml and XXXOffering-lookups.xml files remain intact. Overwritten – Offering disappears from productmodel.display.properties without warning. |
Update modifiers in Product Designer
Advanced Product Designer does not support modifiers. You can specify modifiers for your product in Product Designer.The first column of the table describes the update you make in Product Designer. The second column describes what happens in Studio when you commit the change in Product Designer. The third column describes what happens when you regenerate the product in Advanced Product Designer.
| Product Designer | Studio | After regenerating product |
|---|---|---|
| Add modifier | ProdId.xml and ProdId-lookups.xml created in the ProdId directory. |
Overwritten – Modifier disappears from both files without warning. Overwritten – Modifier disappears from productmodel.display.properties without warning. |
Update question sets in Product Designer
Advanced Product Designer does not support question sets. You can specify question sets for your product in Product Designer.The first column of the table describes the update you make in Product Designer. The second column describes what happens in Studio when you commit the change in Product Designer. The third column describes what happens when you regenerate the product in Advanced Product Designer.
| Product Designer | Studio | After regenerating product |
|---|---|---|
| Add question set with question |
Question set added to ProdId/ProdId.xml. QuestionSetName.xml and QuestionSetName-lookups.xml created in productmodel/questionsets. |
Files remain intact. |
Policy line patterns
Policy line patterns are in resources/productmodel/policylinepatterns/Line under PolicyCenter_installation/modules/configuration/config. The policy line corresponds to the product line in Advanced Product Designer.
When regenerating the product, you are not warned about modified files.
| File name | Description |
|---|---|
| Line.xml |
These files are generated once. You can make changes, and your changes will not be overwritten when you regenerate. |
| Line.properties | |
| Line-lookups.xml |
Update categories in Product Designer
Guidewire recommends that you update categories in Advanced Product Designer not Product Designer. In Advanced Product Designer, these are clause categories. This topic describes the consequences of updating categories in Product Designer.
| Product Designer | Studio | After regenerating product |
|---|---|---|
| Add new category | Category is added to line.xml in the
policylinepatterns directory. Display string for category is added to productmodel.display.properties. |
Overwritten – Category disappears from both files without warning. |
| Modify category | Category is modified in line.xml in
the policylinepatterns directory. Display string for category is modified in productmodel.display.properties. |
Overwritten – Your modifications to both files disappear without warning. |
| Remove category | Category is removed from line.xml in
the policylinepatterns directory. Display string for category is removed from productmodel.display.properties. |
Overwritten – The removed category reappears in both files without warning. |
Update clauses in Product Designer
Guidewire recommends that you update clauses in Advanced Product Designer not Product Designer. This topic describes the consequences of updating clauses in Product Designer.
Clause patterns are in resources/productmodel/policylinepatterns/Line/coveragepatterns. This directory includes patterns for coverages, conditions, and exclusions.
| File name |
|---|
| YYYClause.xml |
| YYYClause-lookups.xml |
| Product Designer | Studio | After regenerating product |
|---|---|---|
| Add clause | YYYClause.xml and
YYYClause-lookups.xml
files are added in the coveragepatterns directory. Display string for clause is added to productmodel.display.properties. |
YYYClause.xml and YYYClause-lookups.xml files remain intact. Overwritten – Clause disappears from productmodel.display.properties without warning. |
| Remove clause | YYYClause.xml and
YYYClause-lookups.xml
files are removed from the coveragepatterns
directory. Display string for clause is removed from productmodel.display.properties. |
Overwritten – YYYClause.xml and YYYClause-lookups.xml files reappear after generate without warning. Overwritten – Clause reappears in productmodel.display.properties without warning. |
| Add term to existing clause |
Term is added to YYYClause.xml and YYYClause-lookups.xml files in the coveragepatterns directory. Display string for term is added to productmodel.display.properties. |
Overwritten – Term disappears from
YYYClause.xml
without warning. Term remains in YYYClause-lookups.xml. Overwritten – Clause disappears from productmodel.display.properties without warning. |
| Remove term from clause |
Term is removed from YYYClause.xml and YYYClause-lookups.xml files in the coveragepatterns directory. Display string for term is removed from productmodel.display.properties. |
Overwritten – Term reappears in
YYYClause.xml and
YYYClause-lookups.xml
without warning. Overwritten – Term reappears in productmodel.display.properties without warning. |
Update availability in Product Designer
If possible, define availability for the product in Advanced Product Designer. If you have requirements for usage and availability that cannot be specified using Advanced Product Designer, you can use the availability features that Product Designer offers. For more information, see Specifying additional availability in Product Designer.
Availability scripts, lookup tables, and grandfathering are not supported in Advanced Product Designer. You can enter these for your product line in Product Designer.
The first column of the table describes the update you make in Product Designer. The second column describes what happens in Studio when you commit the change in Product Designer. The third column describes what happens when you regenerate the product in Advanced Product Designer.| Product Designer | Studio | After regenerating product |
|---|---|---|
|
Lookup table (availability criteria that you define at the top of the Availability screen). |
Availability criteria is updated in
YYYClause-lookups.xml
in the coveragepatterns directory. Availability criteria for a jurisdiction is updated in YYYClause-lookups.xml in the Line/jurisdictions/XX/coveragepatterns directory, where XX is the jurisdiction. |
Updates in all YYYClause-lookups.xml files remain intact. |
| Availability script | Script is updated in YYYClause.xml in the coveragepatterns directory. | For clauses, availability script updates remain in
YYYClause.xml. Overwritten – Availability script is overwritten in clause terms. You are warned before the file is overwritten. |
|
Grandfathering (randomly choose if covered object at line or risk) |
Grandfather criteria is updated in YYYClause-grandfathering.xml in the Line/jurisdictions/XX/coveragepatterns directory, where XX is the jurisdiction. | Updates in YYYClause-grandfathering.xml remains intact. |
Risk object entities
Entities for risk objects are in extensions/entity directory under PolicyCenter_installation/modules/configuration/config.
Before regenerating the product, you will receive a warning about modified files that will be overwritten if you proceed.
If you can, make all changes to the object in Advanced Product Designer. When you regenerate the product, you can accept the regenerated version of the object, and do not need to merge it with the older version. If that is not possible, you can make changes in an extension to the object. You have to add the extension manually in the file system. Although you cannot add the extension in Studio, you can edit it in Studio after creating it.
| File name | Description |
|---|---|
| YYYCost.eti | For each product line, there is a cost on the product line. These files are generated once. You can make changes, and your changes will not be overwritten when you regenerate. |
| YYYCostDefinition.eti | |
| YYYTransaction.eti |
These files are generated once. You can make changes, and your changes will not be overwritten when you regenerate. |
| YYYRisk.eti | An entity for each risk object, including the product line. These files are generated once. You can make changes, and your changes will not be overwritten when you regenerate. |
| YYYRiskCost.eti | A cost entity for each risk object. |
| YYYExposure.eti | An entity for each exposure. |
| YYYLineId.eti | An entity for the product line. |
Clause entities
Entities for clauses are in the extensions/entity directory under PolicyCenter_installation/modules/configuration/config. Clause types are coverages, conditions, and exclusions.
Before regenerating the product, you will receive a warning about modified files that will be overwritten if you proceed.
If you can, make all changes to the object in Advanced Product Designer. When you regenerate the product, you can accept the regenerated version of the object, and do not need to merge it with the older version. If that is not possible, you can make changes in an extension to the object. You have to add the extension manually in the file system. Although you cannot add the extension in Studio, you can edit it in Studio after creating it.
| File name | Description |
|---|---|
| YYYRiskCov.eti YYYRiskCond.eti YYYRiskExcl.eti |
An entity for each clause category on the risk object. |
| YYYRiskCovCost.eti | A cost entity for each clause type. |
| YYYRiskCovLookup.eti YYYRiskCondLookup.eti YYYRiskExclLookup.eti |
These files are generated once. You can make changes, and your changes will not be overwritten when you regenerate. |
| YYYRiskOptLookup.eti | |
| YYYRiskPackLookup.eti | |
| YYYRiskTermLookup.eti |
Schedule entities
Entities for schedules are in the extensions/entity directory under PolicyCenter_installation/modules/configuration/config.
Before regenerating the product, you will receive a warning about modified files that will be overwritten if you proceed.
If you can, make all changes to the object in Advanced Product Designer. When you regenerate the product, you can accept the regenerated version of the object, and do not need to merge it with the older version. If that is not possible, you can make changes in an extension to the object. You have to add the extension manually in the file system. Although you cannot add the extension in Studio, you can edit it in Studio after creating it.
| File name |
|---|
| YYYRiskSchCovItemCov.eti |
| YYYRiskScheduleCov.eti |
| YYYRiskScheduleCovItem.eti |
| YYYScheduledItem.eti |
Display names
- YYYEntity.lang-code
For example, PETDogCov.en or PETDogCov.fr.
Before regenerating the product, you will receive a warning about modified files that will be overwritten if you proceed.
Make all changes to display strings in Advanced Product Designer so that there is no need to merge changes when you regenerate.
In Studio, if you add a display name that is not generated, the display name remains intact after regenerating the product.
Costs and transactions
YYYCost.lang-codeYYYTransactionlang-code
Typelists
Typelists in the extensions/typelist directory under PolicyCenter_installation/modules/configuration/config.
Before regenerating the product, you will receive a warning about modified files that will be overwritten if you proceed.
For each typelist, maintain it either in a particular Advanced Product Designer product or in Studio. Do not modify the typelist in more than one place.
| File name | Description |
|---|---|
| Typelist.tti | Typelist for each drop-down list defined by the product line. |
| InstalledPolicyLine.YYY.ttx | Adds this policy line to the InstalledPolicyLine typelist. |
PCF files
Subdirectories for PCF files are in the web/pcf/line, xxx and yyy directories. Paths are relative to PolicyCenter_installation/modules/configuration/config.
Before regenerating the product, you will receive a warning about modified files that will be overwritten if you proceed.
PCF files that you add are not overwritten when you regenerate the product.
| Subdirectory | File name |
|---|---|
| policyfile | PolicyMenuItemSet.ProdId.pcf |
| Subdirectory | File name |
|---|---|
| job | LineWizardStepSet.ProdId.pcf |
| policy | YYYLineIdPanelSet.pcf |
| YYYLineIdScreen.pcf | |
| policyfile | PolicyFile_YYYLineId.pcf |
| LineIdLinks.pcf |
| Subdirectory | File name |
|---|---|
| policy | YYYRiskListPanelSet.pcf |
| YYYRiskPanelSet.pcf | |
| YYYRiskPopup.pcf | |
| YYYRiskScreen.pcf | |
| policyfile | PolicyFile_YYYRisk.pcf |
| PolicyFile_YYYRiskScreen.pcf |
| Subdirectory | File name |
|---|---|
| policy | YYYExposureListPanelSet.pcf |
Gosu classes
When you generate the product, Advanced Product Designer
creates a base class and an implementation class in the
PolicyCenter_installation/modules/configuration/gsrc
directory. The base class is created in the gw.lob package and has the
suffix Base. The implementation class is created in the package defined by
the APDProductLinesGosuPackage script parameter. The default is
ext.lob.
To avoid triggering warnings when you regenerate the product, make your changes in the implementation class, and do not modify the base class. You will receive warnings for changes to base classes, but no warnings for changes to implementation classes. When you regenerate, the implementation class is not affected; it is only generated if it does not exist.
For enhancement classes, YYYRiskEnhancement.gs and YYYExposureEnhancement.gs, make your changes directly in the enhancement and merge changes.
See also
