You can create a compound rule using a single event map or multiple event maps. In either case, however, in order for the rule to instantiate, the KPIs upon which the rule is defined must have common dimensional hierarchies, starting with the top-most dimension. Dimension hierarchies must match in dimension, attribute, and hierarchy order. KPIs that use the same hierarchy will always match. The Rule Expression editor provides validation to ensure that matching KPIs are selected.

The following table describes the case of matching hierarchies.

The following two tables describe the case when hierarchies do not match.

The following examples provide additional information about how hierarchies work in compound rule expressions.

Resulting rule instances: Those with common values for customer used to instantiate both KPI#1 and KPI #2. A rule instance will not be created if customer Lucent exists for only one of the KPIs. Event data for customer Lucent must be sent in for both KPIs in order for a rule instance to be created.

Resulting rule instances: Those with common values for region used to instantiate both KPI#1 and KPI #2.

Resulting rule instances: None, because County and City do not match.

Resulting rule instances: None, because State does not match Region.