Rulebase Structure

The following Entity/Relationship diagram depicts the default rulebase structure for dynamic decision tables.

Note 1: Conceptually, the relationship between Domain and DIMember is many-to-many: a domain may contain many domain interface members and a domain interface member can belong to many domains. However, the relationship is implemented as a one-to-many relationship: the same domain interface member has multiple occurrences in the DIMember table for each domain to which it belongs.

Note 2: Conceptually, the relationship between DecTable and Condition and DecTable and Action is mandatory: a (valid) decision table must have at least Condition and at least one Action. These relationships are optional to allow partially completed decision tables to be saved in the rulebase.

Note 3: Conceptually, the relationships between Condition and RPValue and Action and RPValue are one-to-one. However, it is necessary for the rulebase to accommodate the possibility that the length of the string describing the Condition or Action value may exceed the length of the rulebase field. In this case, Aion will automatically parse the value string and create multiple RPValue entries for a single Condition or Action.