Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Business Process Framework: Workflow Guide > Administering, Testing, and Migrating Workflow Policies > Administering Workflow Policies > Moving a Workflow Policy to a Different GroupTo 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
|
![]() ![]() |
Siebel Business Process Framework: Workflow Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |