Expiring a Workflow Policy

When you expire a Workflow Policy, you can remove rows that belong to the expired or Workflow Policy in the S_ESCL_REQ table, which is preferable to deleting the Workflow Policy.

To expire a Workflow Policy

Make a backup copy of the Siebel database or the effected tables.
If necessary, you can use this backup later to restore the tables to their state that existed before you deleted rows.
Use SQL to manually delete the rows that reference expired or deleted Workflow Policies. Delete these Workflow Policies according to RULE_ID, for example, as follows:
```
delete from table name where RULE_ID = 'rule_id'
```
Siebel CRM does not support direct delete or update statements on the Siebel database. Also, the following tables are the only tables that do not contain dependencies. Make sure you perform this procedure in accordance with Siebel Support guidelines:
- S_ESCL_REQ
- S_ESCL_ACTN_REQ
- S_ESCL_STATE
Expire the Workflow Policy:
1. Log in to the Siebel client and navigate to the Administration - Business Process screen.
2. Locate the Workflow Policy you want to expire in the Policies view.
3. Enter a date and time in the Expiration field that has already occurred.
To delete database triggers that reference expired Workflow Policies, run the Generate Triggers server task with the following parameters:
Drop Triggers:
```
EXEC = True
Remove = True 
```
Generate Triggers:
```
EXEC = True
Remove = False
```
If some Workflow Policies are expired, and if these policies did not drop and recreate database triggers, then the database triggers for these policies can still cause Siebel CRM to insert records in the tables for Siebel Workflow. Dropping these database triggers prevents Siebel CRM from creating rows in the S_ESCL_REQ table that are related to expired policies.
If necessary, recreate database triggers.
For more information, see Configuring Database Triggers.
If the errors continue, then contact Oracle Technical Support.
Include a description of the steps you performed to resolve the error, along with a copy of the Workflow Monitor Agent trace files with the following traces set:
```
Error Flags = 2
SQL Trace Flags = 2
```