Double-click the Human Task activity. From the Task Definition list of the General tab, select the human task, as shown

27-84 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

27.4.4 How to Define the Human Task Activity Advanced Features

Figure 27–76 shows the Advanced tab. Figure 27–76 Create Human Task — Advanced Tab The Advanced tab of the Human Task activity enables you to perform the tasks shown in Table 27–19 :

27.4.4.1 Specifying a Scope Name and a Global Task Variable Name

You are automatically provided with default scope and global task variable names during human task activity creation. However, you can specify custom names that are used to name the scope and global variable during human task activity creation. To specify a scope name and a global task variable name: 1. In the Scope Name field of the Advanced tab, enter the name for the BPEL scope to be generated. This BPEL scope encapsulates the entire interaction with the workflow service and BPEL variable manipulation. Table 27–19 Human Task - Advanced Tab For this Field... See... Scope Name Global Task Variable Name Section 27.4.4.1, Specifying a Scope Name and a Global Task Variable Name Owner Section 27.4.4.2, Specifying a Task Owner Identification Key Section 27.4.4.3, Specifying an Identification Key Identity Context Section 27.4.4.4, Specifying an Identity Context Application Context Section 27.4.4.5, Specifying an Application Context Include task history from Section 27.4.4.6, Including the Task History of Other Human Tasks Designing Human Tasks 27-85

2. In the Global Task Variable Name field of the Advanced tab, enter the global task

variable name. This is the name of the BPEL task variable used for the workflow interaction.

27.4.4.2 Specifying a Task Owner

The task owner can view tasks belonging to business processes they own and perform operations on behalf of any of the task assignees. Additionally, the owner can also reassign, withdraw, or escalate tasks. If you do not specify a task initiator on the General tab of the Human Task dialog, it defaults to the owner specified here. To specify a task owner: 1. In the Owner field of the Advanced tab, enter the task owner name or click the icon to the right to use the Expression Builder to dynamically specify the owner of this task.

27.4.4.3 Specifying an Identification Key

The identification key can be used as a user-defined ID for the task. For example, if the task is meant for approving a purchase order, the purchase order ID can be set as the identification key of the task. Tasks can be searched from Oracle BPM Worklist using the identification key. This attribute has no default value. To specify an identification key: 1. In the Identification Key field of the Advanced tab, enter an optional identification key value.

27.4.4.4 Specifying an Identity Context

The identity realm name is used for the task when multiple realms are configured. You cannot have assignees from multiple realms working on the same task. This field is required if you are using multiple realms. To specify an identity context 1. In the Identity Context field of the Advanced tab, enter a value.

27.4.4.5 Specifying an Application Context

The stripe name of the application contains the application roles used in the task. To specify an application context 1. In the Application Context field of the Advanced tab, enter a value.

27.4.4.6 Including the Task History of Other Human Tasks

This feature enables one human task to be continued with another human task. There are many scenarios in which you have related tasks in a single BPEL process. For example, assume you have the following: ■ A procurement process to obtain a manager’s approval for a computer ■ Several BPEL activities in between ■ Another task for the IT department to buy the computer