CER uses the Dependency Manager to store dependencies for CER-stored attribute values

For rule objects that are stored on CER's database tables, each attribute value on those rule objects may play a role as:

• a dependent - i.e. an attribute value which is derived by calculating its values from input data; and/or
• a precedent - i.e. an attribute value which is used as input data during the calculation of a dependent.

CER registers a dependent handler and a precedent handler with the Dependency Manager to allow its stored attribute values to be used as dependents and/or precedents in stored dependencies.

For example, if an attribute totalIncome is present on a Person rule object stored on CER's database tables, and the calculation of totalIncome involved the retrieval of Income.amount attribute values also stored on CER's database tables, then CER would request the Dependency Manager to store the fact that the Person.totalIncome attribute value depends on the Income.amount attribute values.