Compilation and Activation of Rule Bases

Whenever you make changes to a rule base, you must compile it to make sure that no errors exist. You must then activate it so that the changes take effect.

Compiling lets you examine the state transitions and function calls to ensure that the rule base correctly reflects your intentions. You can compile the rule base as many times as necessary to ensure that it functions as planned.

You can activate the rule base when the compiling process convinces you that it functions the way you intend it to. Activating the rule base archives the version of the rule base that existed before you began making changes and incorporates the changes into the current rule base. Until you activate the rules you have been editing, they will not process any records. To view the rules that are currently active, see How to View Rule Bases.

Note: Assume, for example, that you have updated the incident rule base to include a rule that applies an SLA instance to all incidents from a specific organization. Activating that rule base does nothing to change existing incidents from that organization because the rules engine is invoked only when incidents are added or updated, not when rule bases are activated.