When a client of the Dependency Manager identifies that data that may have been used in a calculation has changed, then that client can request that the Dependency Manager must identify and recalculate dependent values affected by the change.

If the Dependency Manager is configured to defer the identification/recalculation work to another transaction (e.g. by enqueuing a deferred process request or by waiting until the Dependency Manager batch suite is next run), then the Dependency Manager must record the changed precedent data in a precedent change set. Each precedent change set has a header record stored as a row on this entity.

By default, most rows on this entity relate to precedent change sets which are processed in deferred processing. However, at all times there is a single open precedent change set which records precedent change items to be processed in batch, as identified by the "open" record on the Precedent Change Set Batch Control entity.

Each precedent change set goes through this lifecycle as stored in the status attribute:

• Open. The state of a precedent change set when it is initially created. In this state new precedent change items can be added to the precedent change set.
• Submitted. The precedent change set has been submitted into dependent-identfication processing. No more precedent change items can be added to the precedent change set.
• Complete. The recalculation of all dependents affected by the precedent changes has been completed. The precedent change set is kept for historical purposes only.

Example

The Eligibility and Entitlement Engine identifies that a determination result for Product Delivery 123 depends on:

• data from the claimant's row on the Person entity;
• active evidence from the parent integrated case 122; and
• product configuration data stored on CREOLE Product.

Later, change of circumstances evidence is activated on integrated case 122, and the Eligibility and Entitlement Engine notifies the Dependency Manager that there has been a change to the precedent data of type "active evidence" for case 122. The Dependency Manager:

• stores a new row on this entity to open a new precedent change set;
• stores a Precedent Change Item identifying the data that changed and ties to the precedent change set row on this entity; and
• submits the precedent change set for deferred processing by enqueuing a deferred processing request and transitioning the status on the precedent change set from "Open" to "Submitted".

When the deferred processing request is later dequeued, the Dependency Manager uses the information in the precedent change set together with the Dependency rows to identify that Product Delivery 123 must be reassessed. After triggering reassessment for the case, the Dependency Manager closes the precedent change set by transitioning the status on the row from "Submitted" to "Closed".

Technical Notes

The data on this table may only be read or written using Dependency Manager APIs - no direct access to the underlying data is supported. Custom DMX files and/or database scripts must not be used to populate this entity. The DMX file for this entity included with the application MUST be used to create a row for the initial precedent change set required by the application.

It is perfectly possible for the Dependency Manager to be notified of changes in data, where that data has never been used in any calculation, and thus the data is not identified as a precedent in any Dependency row. In such circumstances the Dependency Manager will identify that no dependents are affected by the changes in data.