Bookshelf Home | Contents | Index | PDF |
Siebel Business Process Framework: Workflow Guide > Options for Configuring a Workflow Process > Setting the Workflow Mode Property > Options for a Long-Running Workflow ProcessThis topic includes the following topics:
Defining a Sub Process that Assigns a Long-Running Workflow ProcessYou can define a workflow process that assigns an interactive subprocess to the user of a collaborative workflow process. An example of a collaborative workflow process is a workflow process that includes a requirement for approvals. It includes a logical path that runs across multiple users who work in collaboration to finish the work that the workflow process requires. To define a collaborative workflow process, you use the Recipients properties on a subprocess step. The login name determines assignment. The Position or User Id does not determine assignment. This login name can be one of the following items:
The Process Designer does not validate this login name. To define a sub process that assigns a long-running workflow process
Defining a Long-Running Workflow Process That Assigns a Task UI to a UserYou can use a long-running workflow process that assigns a task UI to a user, and then creates an item for the task UI in the user Inbox. To create a new instance of this task UI and run it, the user can click the inbox item. For example, the following work occurs in the Expense Report Approval long-running workflow process:
This situation requires a one-to-one assignment. To make this assignment, Siebel CRM can look up the Id for the manager from the business component that stores data about the user. Siebel CRM gets the manager Id, and then creates a new item in the manager Inbox. This item references the Review Expense Report task UI. To define a long-running workflow process that assigns a task UI to a user
|
Siebel Business Process Framework: Workflow Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |