Page configuration best practices

You can change the user interface of the PolicyCenter application by adding, changing, and removing PCF files from the configuration of your PolicyCenter instance. As a best practice, Guidewire recommends that you edit PCF files by using the Page Configuration (PCF) editor in Guidewire Studio.

See also

Modify base PCF files whenever possible

Modify the base configuration files wherever they can be modified. Create new files only when absolutely necessary.

Add a suffix to new PCF files to avoid name conflicts

Every page configuration file in your PolicyCenter instance must have a unique file name. The location of page configuration files within the folder structure of page configuration resources does not ensure uniqueness. To avoid future naming conflicts when Guidewire adds or changes base page configurations, Guidewire recommends that you append the suffix _Ext to the names of your page configuration files.

For example, name a new list view for contacts on a policy PolicyContacts_ExtLV.

Avoid using Gosu code in PCF files

Avoid including large blocks of Gosu code within the <Code> element in PCF files for the following reasons:
  • Code in a particular PCF file is not reusable.
  • You cannot debug code that is defined in a PCF file.
  • Large amounts of code can complicate merging of PCF files during an upgrade.