Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Business Process Framework: Workflow Guide > Administering a Workflow Process > Recovering a Workflow Process > Recovering Workflow Process InstancesIf the Workflow Process Manager server component fails, then the Siebel Server resumes the interrupted workflow process instances when it restarts. The Workflow Recovery Manager recovers these instances according to the state information that the Workflow Engine saves for each instance. Automatically Recovering a Workflow Process InstanceIf the Workflow Process Manager server component fails due to an event that occurs outside of the Workflow Process Manager server component, such as a server failure, then Siebel Workflow resumes the interrupted workflow process instances when the Siebel Server restarts. You can manually recover instances that Siebel Workflow cannot automatically recover. For example, if the Siebel Server fails while a Siebel operation updates a record, then the workflow process cannot determine if the Siebel operation finished. It might be necessary for you to manually make sure the workflow process finished this update before resuming the workflow process. Siebel CRM can automatically recover a workflow process that runs in the server component. It cannot automatically recover a workflow process that runs on a local database. Manually Recovering a Workflow Process InstanceYou can correct and resume a workflow process instance that encounters errors. For example, if the Communications Server is not available, and if a workflow process uses email to send a notice, then Siebel CRM sets the status for this workflow process to In Error. You can activate the Communications Server, and then resume the workflow process. To manually recover a workflow process instance
How Call Depth Affects Resuming a Workflow ProcessSiebel CRM can resume a workflow process instance only if the Call Depth setting of this instance is the highest among the related instances. If the instance is part of a set of related instances, and if one or more of these instances includes a higher Call Depth level, then Siebel CRM disables Resume Instance-Next Step and Resume Instance-Current Step. For example, assume multiple related instances exist, and that these instances include Call Depth settings of 0,1,2,3, and 4. Assume you choose the record with level 3. In this situation, Siebel CRM disables these Resume controls because level 3 is not the highest Call Depth level that it set among the related instances. |
![]() ![]() |
Siebel Business Process Framework: Workflow Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |