Siebel Business Process Framework: Workflow Guide > Administering Workflow Policies > About Workflow Policy Administration >

Moving a Workflow Policy to a Different Group

In response to changes in the business environment or you configuration, you might find it necessary to change the workflow group for a given workflow policy.

Before you can move a workflow policy from one group to another group, requests associated with that workflow policy must finished. If a workflow policy's group is changed while associated requests are pending, Workflow Monitor Agent will fail with the error Rule Not Found. If this occurs, restore the workflow policy to the policy's original group, wait for the requests to finish, then proceed with the change.

When moving an existing workflow policy from one workflow group to another workflow group, the triggers must be updated. The Triggers will contain the RULE_ID and GROUP_ID for the Workflow Policy. So, if the triggers have not been re-generated, rows will exist in S_ESCL_REQ the reference the original RULE_ID and GROUP_ID.

To move a Workflow Policy to a different Group

1. Run a generate triggers task to drop database triggers, thus making sure no more rows are inserted for workflow policies in the group you need to change. Use the following parameters:

   EXEC=TRUE

   Remove=TRUE

   TIP:   Since triggers are being disabled you need to avoid having additional triggers being fired by workflow policies. Therefore, consider making these changes when either no users or only a minimal number of users are accessing the system.

   For more information, see Running Generate Triggers.

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

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

3. Query the S_ESCL_REQ table for the GROUP_ID to make sure no more rows are present for GROUP_ID.
4. If no monitor agent task is running for the group, start a task for the group with the proper group name.
5. Once the remaining rows in the S_ESCL_REQ table for the group have finished processing, stop the workflow monitor agent task for the group.
6. Reassign the workflow policy to the group by changing the workflow policy's group name field to the new group name.
7. Re-generate database triggers, using the following parameters:

   EXEC=TRUE

   Remove=FALSE

8. Re-start the Workflow Monitor Agent for the old group.
9. Start a new Workflow Monitor Agent for the new group.