Siebel Business Process Framework: Workflow Guide > Administering, Testing, and Migrating Workflow Policies > Administering Workflow Policies >

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.

Locating Workflow Policies That Are Deleted or Expired

The examples in this topic can help you determine if rows in the S_ESCL_REQ table exist that are related to a deleted or expired workflow policy. For more information, see Tables That Workflow Monitor Agent Uses.

Locating Deleted Workflow Policies

You can enter a query that locates deleted workflow policies.

To locate deleted workflow policies

• Run the following query:

  select RULE_ID, count(RULE_ID)
  from S_ESCL_REQ a
  where not exists
  (select row_id
  from S_ESCL_RULE b
  where a.RULE_ID = b.ROW_ID)
  group by RULE_ID

Locating Expired Workflow Policies

You can enter a query that locates expired workflow policies.

To locate expired workflow policies

1. Run the following query:

   select a.RULE_ID, b.NAME, count (a.RULE_ID), b.EXPIRE_DT, b.SUB_TYPE_CD
   from S_ESCL_REQ a, S_ESCL_RULE b
   where a.RULE_ID = b.ROW_ID
   and b.EXPIRE_DT < sysdate
   group by a.RULE_ID, b.NAME, b.EXPIRE_DT, b.SUB_TYPE_CD

   where:

   • sysdate is the Oracle current date and time function.
2. Determine if the workflow policies unintentionally expired.

   An example of a workflow policy that unintentionally expires is someone forgetting to extend the dates but nobody changed the database triggers since the policy expired.

3. If you determine a workflow policy unintentionally expired, and if Siebel CRM must process the rows, then do the following:
   • If the Workflow Monitor is running, and if it is not necessary for you to shut it down, then reverse the expiration of the workflow policy. To do this, enter a new date and time in the Expiration Date field for policy. Make sure this date and time is greater than the current date and time.

     The workflow policy goes into effect after 10 minutes. This delay occurs because the default for the Reload Policy parameter of Workflow Monitor is 600 seconds.

   • If you require the workflow policy to go into effect immediately, then shut down Workflow Monitor if it is running, reverse expiration of the policy, and then start Workflow Monitor.

     You can also do this work with a workflow policy that includes a duration.