CREOLECaseDeterminationData

This table stores XML data for determinations.

The Engine can store two different types of XML data for each determination (and so for each row on CREOLECaseDetermination there are typically two related rows on CREOLECaseDeterminationData):

• Determination result

  An XML representation of a determination result, including the full eligibility/entitlement, key decision factor and decision details over the lifetime of the case, and also details of any errors encountered during calculation of the determination. This XML will be used when data from the determination result is subsequently displayed to a case worker; and

• Snapshot of Rule Objects

  An XML snapshot of the CER rule objects used in the calculation of the determination result. This snapshot provides a point-in-time view of the CER rule objects and is stored to provide a full technical audit of how the determination result was calculated. The CER rule objects include those for input data (such as evidence, personal details and rates) and also all intermediate calculation steps. The snapshot points to the versions of the rule sets that were in place when the time that the snapshot was taken, so that the subsequent publication of changes to those rule sets do not affect the ability to read the snapshot data. The snapshot can be read using CER's SnapshotDataStorage feature. A snapshot is stored for assessment and snapshot determinations, but is only stored for manual check determinations if the application has been configured to do so (using the curam.creole.manualeligibilitycheckdetermination.store.ruleobjectsnapshot environment variable).

In the unlikely event that the XML data is too long to fit onto a single CREOLECaseDeterminationData, the data will be truncated to fit and the extra data stored on an "overflow" CREOLECaseDeterminationData row (or chain of overflow rows).