Types of Change that Cause Bulk Reassessment

This section describes the types of change that the Engine treats as causing bulk reassessment, i.e. where the expected effect of the changes is not limited to a low number of cases (unlike case-level reassessment - see Case-level Reassessment).

The effects of any of these types of change are handled in batch processing, and so require the execution of batch jobs to be scheduled, either on a regular schedule provided by your third-party scheduling software, or on an ad hoc basic by being manually run by system operator staff.

The Engine treats any change to the following system-wide data as "bulk change" potentially affecting a large number of cases, and thus requiring bulk reassessment processing:

Product configuration;
CER Rules used by the Product;
Rule Object Data Configurations; and
Rate Tables.

The following sections describe these types of change in more detail, and explain the lifecycle of each type of change. In general terms, each type of change can be worked on by an administrator without causing any effects on the system, followed by a "publish" action where the completed changes start to take effect and are available for case processing.

Tip: When changes to any of these types of data are published, an informational message (advising that a system-wide change has occurred and that bulk reassessment processing is required) is shown on the publication screen and also written to the application logs.

It may be useful to monitor the application logs for this informational message if you choose to run bulk reassessment processing on an ad hoc basis (i.e. only when a bulk change has occurred).