Policy Exception rules

In the base configuration, Guidewire disables the Policy Exception rules by disabling the batch processes that run these Policy Exception rules.

If enabled, the rules looks for certain conditions on PolicyPeriod entities that possibly require further attention. You can then define follow-up actions for each exception found. First, PolicyCenter identifies PolicyPeriod entities that changed since the last inspection, or, that it has not inspected for a long time. PolicyCenter then runs these rules on each PolicyPeriod chosen.

This rule set is empty by default in the base configuration. Implementers are free to create rules in this rule set category as necessary. However, it is important to understand:

  • PolicyCenter persists any change made to the PolicyPeriod or its related objects through this rule set to the database.
  • PolicyCenter runs the rules in this rule set category—one at a time—over a potentially large number of PolicyPeriod entities. This can have an adverse impact on performance.

Validation and Policy Exception rules

The Policy Exception rules perform no implicit validation. Any validation that you want to perform you must execute explicitly by calling the appropriate validation method. Guidewire strongly recommends that you take care to validate only as needed, for performance reasons. For instance, if the only change to a PolicyPeriod entity is to raise an alert in the form of a Note, Activity, or email, do not validate.

Policy Exception rules and PolicyPeriod entities

PolicyCenter runs the Policy Exception rules over every PolicyPeriod entity in the database except for bound periods that are no longer the most recent model (PolicyPeriod.MostRecentModel == false). Thus, you can run exception rules on withdrawn, declined, and bound revisions.

Data model and the PolicyPeriod entity

To store the time at which it last ran the exception rules, PolicyCenter maintain a separate PolicyException entity with two fields of interest:

  • A non-nullable foreign key to PolicyPeriod
  • A datetime field named ExCheckTime indicating the time at which the exception rules last ran

A PolicyPeriod never has more than one associated PolicyException entity. If PolicyPeriod entity has no associated PolicyException entity, it means that the exception rules have not yet been run on that particular PolicyPeriod entity.