Incremental Propagation

During normal running of the application, the system detects changes to data which may have been used to populate CER rule objects, by listening for these internal events:

• changes to evidence, such as the activation of in-edit evidence changes; and
• changes to entity rows, for entities which are mapped in data configurations for the Entity Rule Object Converter.

The processing of these internal events as they occur is known as "incremental propagation". Incremental propagation is used to inform the Dependency Manager of changes to precedent data, so that the Dependency Manager can take care of identifying dependents to recalculation.

There are situations where incremental propagation cannot automatically detect changes to precedent data, namely:

• a non-propagatable data write operation is executed (see Propagation Processing); and/or
• data is written to the database outside the control of standard modeled entity operations, e.g. via an SQL script or another system connected to the application's database.

If either of these occur you must take manual steps to identify and reassess cases which may be potentially affected.