|Bookshelf Home | Contents | Index | PDF|
Interactive workflow processes that have been suspended can be resumed from within the user's Inbox. The user can navigate out of an interactive process, then navigate back to the process and pick up where the user left off.
Suspension and resumption of interactive workflow processes can be used in a situation such as the following: a transaction involving the user (an insurance agent) cannot be completed because of missing information, such as a spouse's social security number required for the entry of an insurance policy quote. In this example, when the insurance agent has been able to obtain the social security number after suspending the interactive workflow process, she can resume the process from within her Inbox and enter the number to complete the entry of the quote. Once the process is complete, the Workflow engine removes the interactive workflow process from her Inbox.
NOTE: With explicit resumption, when a user clicks on a workflow in the Inbox, the Inbox will invoke the Workflow engine or business service and pass it the row ID of the workflow instance for resumption.
Users often navigate out of structured interactive workflows because the workflows have been set up in this manner to address the specific needs of your business. When this happens, the interactive workflows remain in memory so that they can be resumed later in the same user session. As it is uncommon for users to have a large number of unfinished tasks at hand, there can be a maximum of eight suspended interactive workflows in the memory cache.
Upon receiving the user logout event, the Workflow engine goes through suspended interactive workflows in the in-memory cache. Workflows with the Auto Persist flag checked are saved as Inbox items. Other workflows are deleted.
|Siebel Business Process Designer Administration Guide|