Overriding validation triggers

In the base configuration, Guidewire sets validation to trigger on many top-level entities and on many of the arrays and foreign keys associated with them. You cannot modify the base metadata XML files in which these configurations are set. However, there can be occasions in which you want to override the default validation behavior. For example:

  • You want to trigger validation upon modification of an entity in the PolicyCenter base data model that does not currently trigger validation.
  • You do not want to trigger validation on entities on which PolicyCenter performs validation in the base configuration.

You can only override validation on certain objects associated with a base configuration entity. (It is not necessary to override your own extension entities as you simply set triggersValidation to the desired value as you define the entity.)

The following tables lists the data objects for which you can override validation, the XML override element to use, and the location of additional information.

Data field

Override element

More information

<array>

<array-override>

<array>

<foreignkey>

<foreignkey-override>

<foreignkey>

<onetoone>

<onetoone-override>

<onetoone>

See also

Validation trigger example

In the base configuration, PolicyCenter runs the validation rules on the Account object during database commit. Guidewire defines the Account entity in Account.eti. The PolicyCenter base configuration first defines the Account entity as validatable, then defines the RoleAssignments array as triggering validation.

<entity entity="Account" table="account" type="retireable" lockable="true">
    ...
  <implementsEntity name="Validatable"/>
  ...
  <array arrayentity="UserRoleAssignment"
         cascadeDelete="true"
         desc="Role Assignments for this account."
         exportable="false"
         name="RoleAssignments"
         triggersValidation="true"/>
  ...
</entity>