Defining a Long-Running Workflow Process That Assigns a Task to a User
You can use use a long-running Workflow Process to assign a task to a user and then create an item for the task in the user Inbox. To create a new instance of this task and to run the task, the user can clicks the inbox item. For example, the following occurs in the Expense Report Approval long-running Workflow Process:
An employee sends an expense report.
Siebel CRM creates a new task named Review Expense Report.
Siebel CRM assigns the Review Expense Report task to the employee’s manager.
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. When Siebel CRM gets the manager Id, it then creates a new item in the manager Inbox. This item references the Review Expense Report task.
To define a long-running Workflow Process that assigns a task to a user
Use the Process Designer to open the long-running Workflow Process.
At the point where Siebel CRM must call the task, determine the Id of the user to whom it must assign the new task instance.
Siebel CRM can use a business service that accesses Siebel Assignment Manager to apply an assignment rule. The input to this business service varies depending on the context that the assignment requires. The output from this business service is the Id of the user to whom Siebel CRM assigns the task.
This logic depends on your business requirements. If the Id:
Already exists in a business component, then you must use a Siebel operation.
Does not exist, then you must use a business service to get it.
In the Owner Id input argument, identify the task step that creates a new item in the user Inbox.
Add a task step to the Workflow Process.
If you add a task step to a Workflow Process, then it creates a new instance of the task and assigns it to the user. For more information, see Adding a Task Step.