Making changes to entity metadata files in a rolling upgrade

Permitted changes to entity metadata files

Guidewire permits only the addition (not the modification) of a few select fields (XML elements) to an existing entity metadata file during a rolling upgrade. It is only possible to add the following XML elements along with the listed subtypes:
  • <column>
    • <columnParam>
    • <fulldescription>
    • <tag>
  • <monitaryamount>
    • <fulldescription>
    • <tag>
  • <typekey>
    • <fulldescription>
    • <keyfilters> (<keyfilter>)
    • <tag>
Fields (elements) in the entity metadata files become table columns in the database. Guidewire imposes the following constraints on these table columns:
  • The column can only support scalar data and it must be nullable (nullok=true).
  • The column cannot contain spatial data (spatialpoint, spatialpolygon).
  • The column cannot have a <localization> subelement.
  • The column cannot set the autoincrement attribute.
  • The column cannot contain a default value.

How to make changes to entity metadata files

Note: You cannot extend an entity for which the extendable attribute is set to false.

To make a make a supported change to an entity metadata file during a rolling upgrade, do the following, depending on the location of the file.

Studio folder File type Action to take
Metadata > Entity *.eti or *.eix Create a *.etx file for that entity in Extensions > Entity and add the supported change
Extensions > Entity *.eti or *.etx Modify the file in Extensions > Entity and add the supported change

Prohibited operations

Guidewire explicitly does not support the following changes to entity metadata files in a rolling upgrade:
  • Any attempt to add a new table.
  • Any attempt to add a new index.
  • Any attempt to modify the entity name.
  • Any attempt to add a localization element.
  • Any attempt to add the following elements:
    • <arrray>
    • <foreignkey>
    • <edgeForeignKey>
    • <onetoone>

Database writes during a rolling upgrade

Do not attempt to write to a new database column (one added during the rolling upgrade operation itself) during the rolling upgrade. If you do attempt such a database write, PolicyCenter blocks the transaction and then throws an exception.

In general, then, do not write to any new database column that you add during a rolling upgrade until after the rolling upgrade completes. The rolling upgrade is complete after you click Rolling Upgrade Complete on the (Server Tools) Upgrade and Versions screen. This action deletes the database flag associated with the rolling upgrade. Only then is the rolling upgrade complete.