How PolicyCenter schedules the Policy Exception rules
Three separate batch processes control the time at which PolicyCenter runs the exception rules.
|
Runs on all |
|
Runs on all |
|
Runs on all |
All three processes invoke the same rule
set. Therefore, if you want the exception behavior to vary based on the
PolicyPeriod status, you
need to test that status within the rules.
In the base configuration, Guidewire disables these batch processes by default. To enable a batch process, remove the comments around its entry in scheduler-config.xml. If enabled, PolicyCenter runs the default entries at the following times:
OpenPolicyExceptionruns every night at 2 a.m.BoundPolicyExceptionruns on the first Saturday of each month at 12:00 noonClosedPolicyExceptionruns on the first Sunday of each month at 12:00 noon
You can use configuration parameters in config.xml to limit how often PolicyCenter runs the exception rules against a single PolicyPeriod entity. Use the following parameters:
Batch process |
Use parameter… |
Default (days) |
|---|---|---|
|
|
1 |
|
|
14 |
|
|
14 |
These parameters limit how many days must
pass before the exception rules run a second time on any given PolicyPeriod entity. For instance,
suppose that a given PolicyPeriod
has a withdrawn status and ClosedPolicyThresholdDays
is set to 30. After PolicyCenter
runs the exception rules on that PolicyPeriod,
the ClosedPolicyException
process does not run rules on that particular policy again until at least
30 days have passed. Thus, these configuration parameters are useful
as throttles for performance.
The following table summarizes this information:
Process |
Default Schedule |
Criteria |
|---|---|---|
|
Every night at 2 a.m. |
|
|
First Saturday noon |
|
|
First Sunday noon |
|
See also
