Create Human Task Dialog

3.36 Create Human Task Dialog - Advanced Tab

Use to specify advanced features for the metadata task configuration file associated with the BPEL process, such as scope name, global task variable name, task owner, identification key, included task history, and callbacks.

When association is complete, a Task Service partner link is created. The Task Service exposes the operations required to act on a task.

Element	Description
Scope Name	Enter the name for the BPEL scope activity to be generated or accept the default value of `human_task_namenumber`. This BPEL scope encapsulates the entire interaction with the workflow service and BPEL variable manipulation.
Global Task Variable Name	Enter the global task variable name. This is the name of the BPEL task variable used for the workflow interaction.
Owner	Enter the owner of this task. 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 in the Create Human Task Dialog - General Tab, it defaults to the owner specified here. If an owner is not explicitly specified here or in the Human Task Editor, the service queries the identity provider and automatically selects a user with an `admin` privilege to be the owner. Enter the initiator manually (for example, `jcooper`). Click the XPath Expression Builder icon to display the Expression Builder dialog for dynamically specifying an owner.
Identification Key	Enter or click the XPath Expression Builder icon to specify an optional identification key value. 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.
Identity Context	Enter the identity realm name to be used for the task when multiple realms are configured.
Application Context	Enter the stripe name of the application that contains the application roles used in the task.
Include task history from	Use to extend a task prior to this one in the BPEL process by selecting to include task history, comments, and attachments from the previous task to get a complete end-to-end audit trail. For example, assume you have a computer purchase workflow that first gets manager approvals (for example, computer purchase approval). Some BPEL logic then calls external services to get price quotes. You then have another computer order task for the procurement department. The task for the procurement department may extend the previous computer purchase approval task to get approval history and comments from the approvers.
Clear old payload and recreate	Click if the extending task has a payload that is different from the other task.
Use existing payload	Click if the extending task has the same payload as the other task.