This chapter includes the following sections:
For detailed information on how to create, edit, and configure human tasks, see Chapter 28, "Designing Human Tasks in Oracle BPM".
The implementation of user tasks requires you to define a Human Task. You can use an existing Human Task or define a new one.
If your project contains Human Tasks, then they automatically appear in the business catalog under the HumanTasks predefined module.
You can add new Human tasks to your project in the following ways:
Using the simplified interface Oracle BPM Studio provides
From the SOA New Gallery
From the SOA Composite Editor
When you double click a Human Task component in the business catalog, Oracle BPM Studio opens the SOA Human Task editor. You can edit the Human Task using this editor.
Figure 14-1 shows a Human Task component in the Sales Quote example.
At run time, when a token arrives at a user task control is passed from the BPMN process to the Oracle Human Workflow. Although both are part of Oracle BPM run time, control is not passed back to the BPMN process until the Human Tasks is completed.
After the workflow is complete, control is passed back the BPMN process, any required data objects are passed back to the user task, and the token moves to the next sequence flow of the process.
However human tasks are independent from BPMN processes. If you terminate a BPMN process while it runs a user task, the associated human tasks keeps running independently. For more information see Section 18.1.1, "Understanding the Relationship Between SOA Composites and SOA Components".
If the process instance leaves the user task before the human tasks is completed, the human task continues running and can you can still access it. This is because human tasks are independent from the BPMN process. Any changes you make to a human task after the process instance left the corresponding user task, do not appear in the audit trail.
When you define a human task in BPM the callback is implicitly defined.
Human task patterns allow you to use a predefined flow to create the Human Task. These predefined patterns contain standard process flows that are common to all business processes.
Oracle BPM supports the following Human Tasks patterns:
You can add a Human Tasks that uses patterns by selecting the specific user task in the Interactive Activities section in the Component Palette, or you can add a generic user task and when you create the Human Task select the pattern you want to use.
For more information about Human Task patterns, see Chapter 32, "Using Approval Management".
Update tasks enable you to update certain properties of specific user tasks in your process. You can choose to update a specific user task, all user tasks or to dynamically generate the ID of the user task to update using an expression. Update tasks do not require you to specify the taskId or the context.
You can use user tasks to perform the update operations based on the status of your process or the different paths the process instance takes. Update tasks enable you to model the updating sequence in your business process making the process flow easier to understand.
Update tasks enable you to change the value of some of the properties of the human task used to implement the user task. For a description of the properties involved in the different operations, see Section 28.2, "Creating a Human Task from Oracle BPM Studio".
Update tasks support the following operations:
Update Outcome: updates the outcome of the human task used to implement the specified user task. You must specify the new outcome using an expression. You can choose to write the expression using literals, simple expressions or XPath expressions.
Update Priority: updates the priority of the human task used to implement the specified user task. You must specify the new priority using an expression. You can choose to write the expression using literals, simple expressions or XPath expressions.
Withdraw: withdraws the task from the task list shown to other assignees.
Suspend: suspends the task.
Resume: resumes the task.
Escalate: escalates the task using the escalation hierarchy or escalation callbacks specified in the human task that implements the specified user task.
Reassign: reassigns the human task used to implement the specified user task, to a new user. You must specify the new user using an expression. You can choose to write the expression using literals, simple expressions or XPath expressions
Suspend Timers: suspends the timers that are running over the human tasks that implements the specified user task. Suspending the timers results in the suspension of the expiration policies defined for the human task.
You can update different parameters of user tasks from your business process using an update task.
Open the business process that contains the user task.
Add an update task.
Configure the update task. .
You can configure an update task to perform different operations over the user tasks you specify.
Right-click the update task.
Click the Implementation tab.
From the target list select how to specify the target user task.
The available options are:
Select a specific user task: The user tasks in your process appear in this list, you can select any of them and update it using this update task.
All User Tasks: This option enables you to update all the user tasks in the process.
Task Id: This option enables you to specify a task Id that identifies the user task, using an expression. When you select this option the Task Id field appears.
From the Operation list, select an operation.
For more information about the available operations, see Section 14.3.1, "Update Task Operations".