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

Moving a Workflow Policy to a Different Group

To reply to changes in the business environment or to your configuration, it might be necessary to move a workflow policy to a different workflow group. Siebel CRM must finish requests that are associated with the workflow policy before you can move a workflow policy from one group to another group. If you move a workflow policy to a different workflow group while a request is pending, then Workflow Monitor Agent fails with a Rule Not Found error. In this situation, you must move the workflow policy back to the original group and wait for the request to finish.

If you move a workflow policy to a different workflow group, then you must also update database triggers. These triggers contain the RULE_ID and GROUP_ID for the workflow policy. If you do not update them, then rows in the S_ESCL_REQ table reference the original RULE_ID and GROUP_ID. For more information, see Tables That Workflow Monitor Agent Uses.

To move a workflow policy to a different group

1. To drop database triggers, run a Generate Triggers server task using the following parameters:

   EXEC=TRUE
   Remove=TRUE

   Dropping database triggers makes sure Siebel CRM does not insert any more rows for workflow policies in the group you must change. To avoid starting more database triggers, it is recommended that you make these changes only if no users or only a minimal number of users are currently using Siebel CRM. For more information, see Configuring Database Triggers.

2. If a Workflow Monitor Agent server task is already running, then allow the Siebel Server task to finish.

   This step makes sure the Siebel Server task processes the remaining rows in the S_ESCL_REQ table for the workflow policy group.

3. To make sure no more rows occur for GROUP_ID, query the S_ESCL_REQ table for the GROUP_ID.
4. If no server task for the monitor agent is running for the group, then start a server task for the group with the proper group name.
5. Wait for Siebel CRM to finish processing the remaining rows in the S_ESCL_REQ table for the group.
6. Stop the Siebel Server task of the Workflow Monitor Agent for the group.
7. To reassign the workflow policy to the group, change the field of the group name for the workflow policy to the new group name.
8. Generate database triggers again, using the following parameters:

   EXEC=TRUE
   Remove=FALSE

9. Restart the Workflow Monitor Agent for the old group.
10. Start a new Workflow Monitor Agent for the new group.
11. Restart the Workflow Monitor Agent for the old group.
12. Start a new Workflow Monitor Agent for the new group.