A persistent image of all the rules (for all applications) that are currently loaded in the rule engine is maintained in the database for recovery purpose. Rules are synchronized through a specific transaction, independent from the synchronization transaction, as changes in the rule set-up is usually caused by external agents (for example, a BPM Events Admin command) and is infrequent. The rule changes that are notified to the database are: