| Precedent Change Item
:
An item in a Precedent Change Set, i.e. details of a precedent which has changed (identified by its type and ID).
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 item of changed precedent data is stored as a row on this entity, linking to its owning Precedent Change Set.
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 Precedent Change Set row;
- stores a new row on this entity identifying the data that changed and ties to the precedent change set row stored above; and
- submits the precedent change set for deferred processing.
When the deferred processing request is later dequeued, the Dependency Manager uses the precedent change item stored in the precedent change set together with the Dependency rows to identify that Product Delivery 123 must be reassessed.
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. DMX files and/or database scripts must not be used to populate this entity.
Optimistic locking is not required as rows are never modified.
The Dependency Manager has no inherent understanding of the precedent referred to by a row on this entity. As such the precedentType and precedentID attributes on this entity are not constrained by foreign keys, since the Dependency Manager intentionally does not maintain any lists of known precedents in the system.
|
