Deleting an Obsolete Workflow Policy

You delete an obsolete Workflow Policy for the following reasons:

• To avoid the ESC-00054 error when you start Workflow Monitor.

• To avoid the unnecessary use of storage space. Normally, Workflow Monitor does not process rows that are associated with an obsolete Workflow Policy. The rows remain unused in the S_ESCL_REQ table.

Database triggers are still in effect when you expire or delete a Workflow Policy and shut down the Workflow Monitor. Database triggers that are related to an expired or deleted policy continue to work until you delete them from the Siebel database. Siebel CRM might continue to trigger rows in the S_ESCL_REQ table between the time you expire a Workflow Policy and the time you finish dropping and redefining database triggers.

You might encounter the ESC-00054 error when you start the Workflow Monitor because Workflow Monitor Agent finds Workflow Policies in the S_ESCL_REQ table that are not active or are not present. The workflow policies that Siebel CRM stores in the S_ESCL_RULE table must remain in the S_ESCL_REQ table and Siebel CRM must not process them.

If Use Action Agent is set to FALSE for the Workflow Monitor, then the Workflow Monitor Agent runs for the Action Agent, bypasses the S_ESCL_ACTN_REQ table, and uses only the S_ESCL_REQ table. If rows in the S_ESCL_REQ table exist for a Workflow Policy that is expired or deleted, then you must delete them before you start the Workflow Monitor. For more information, see Expiring a Workflow Policy.

For more information, see Tables That Workflow Monitor Agent Uses.