Minimizing performance issues with the Policy Exception rules

It is extremely easy to configure the exception rules so as to create performance issues, because the rules run on all PolicyPeriod entities of a given type. To minimize performance issues, Guidewire recommends the following:

• Put as little expensive logic into the exception rules as possible. The suggested approach is to check for a condition (which is relatively cheap to inspect). Then, if the condition is true, perform a relatively low-cost action (such as creating an Activity).
• Only enable an exception process (OpenPolicyException, ClosedPolicyException, or BoundPolicyException) in scheduler-config.xml if you have Policy Exception rules for that particular policy exception type. For example, if you have bound policy exception rules, then only enable the BoundPolicyException process.
• Schedule the processes to run as rarely as possible, and use the highest values possible for a XXPolicyThresholdDays configuration parameter.