Capture of Precedent Change Items

Clients must notify the Dependency Manager whenever the value of a precedent has changed. The Dependency Manager accumulates these changes into a Precedent Change Set for later processing.

The most prevalent example is the Eligibility and Entitlement Engine, which contains "rule object propagators" - these propagators are responsible for listening to changes in entities and evidence, and for notifying these changes to the Dependency Manager.

The Dependency Manager supports these modes for dealing with precedent changes:

• Queue for Deferred Processing (the default); and
• Queue for Batch Processing (for use by clients identifying precedent changes which are likely to lead to a large number of dependents being recalculated).

These modes are described in greater detail in the following sections.