Propagation Processing

Whenever the CaseHeader or ProductDelivery data changes for a CER-based product delivery, the propagator requests the ProductEligibilityEntitlementRuleSet.ProductDeliveryCase rule object for the case and manipulates it in memory.

For a product which has its reassessment strategy set to "Do not reassess closed cases", then:

• when a product delivery case for the product is closed, then the propagator removes the rule object in memory and also deletes all dependency records for the case's determination result, to prevent automatic reassessment of the case; and
• when a product delivery case for the product is re-opened and subsequently re-activated, then the Engine will calculate the case's determination result and will also build back up the dependency records for the case's determination result, to allow automatic reassessment of the case if data changes in the future.

For a product which has its reassessment strategy set to "Automatically reassess all cases", then no such processing occurs and the continuing presence of the dependency records in the Dependency Manager while a case is closed means that the case will continue to be reassessed due to data changes even if it is closed.

See Reassessment Strategy for details of the processing that occurs if an administrator chooses to change the reassessment strategy for an existing product that has product delivery cases created against it.