Online Help for Oracle SOA Suite

3.2 Human Task Editor - General Page

Use to specify the task title, task description, task outcomes, task priority, category, and task owner. How?

The Human Task Editor enables you to define the metadata for a human task. You can specify human task settings, such as task outcome, payload structure, task participants, assignment and routing policy, expiration and escalation policy, notification settings, and so on.

Element	Description
Task Title	Enter an optional task title. The title defaults to this value only if the initiated task does not have a title set in it. The title provides a visual identifier for the task. The task title displays in Oracle BPM Worklist. You can also search on titles in Oracle BPM Worklist. Select a method for specifying a task title: Plain Text: Manually enter a name (for example, `Vacation Request Approved`) Text and XPath: Enter a combination of manual text and a dynamic expression. After manually entering a portion of the title (for example, Approval Required for Order Id:), place the cursor one blank space to the right of the text and click the icon to the right of this field. This displays the Expression Builder for dynamically creating the remaining portion of the title. After completing the dynamic portion of the name, click OK to return to this field. The complete name is displayed. For example: `Approval Required for Order Id: <%/task:task/task:payload/task:orderId%>` The expression is resolved during runtime with the exact order ID value from the task payload.
Description	Enter an optional description of the task. The description enables you to provide additional details about a task. For example, if the task title is Computer Upgrade Request, you can provide additional details in this field, such as the model of the computer, amount of CPU, amount of RAM, and so on. The description does not display in Oracle BPM Worklist.
Outcomes	Accept the default values of APPROVE and REJECT or click the Search icon to perform the following: Select additional seeded task outcomes Create custom outcomes Task outcomes capture the possible outcomes of a task. Oracle BPM Worklist displays the outcomes you specify here as the possible task actions to perform during runtime. Note: Ensure that you do not specify a custom name that matches a name listed in the Actions tab of the Access page of the Human Task Editor (for example, do not specify Delete). Specifying the same name can cause problems at runtime.
Priority	Specify the priority of the tasks. Priority can be 1 through 5, with 1 being the highest. By default, the priority of a task is 3 (Normal). This priority value is overridden by any priority value you select in the General page of the Create Human Task dialog. You can filter tasks based on priority and create views on priorities in Oracle BPM Worklist.
Category	Specify an optional task category through one of the following methods: By name: Manually enter a name By expression: Click the icon to the right of this field to display the Expression Builder for dynamically creating a category This categorizes tasks created in a system. For example, in a help desk environment, you may categorize customer requests as either software-related or hardware-related. The category displays in Oracle BPM Worklist. You can filter tasks based on category and create views on categories in Oracle BPM Worklist.
Owner	Select a task owner: User: You can assign an individual user as the task owner. For example, you may assign user jlondon. Users are defined in an identity store configured with the SOA Infrastructure Group: You can assign groups as the task owner. Groups contain individual users. For example, users `jcooper` and `fkafka` may be members of the group `LoanAgentGroup` Application Role: You can assign users who are members of application roles to claim and act upon tasks Select a method for specifying the task owner: Statically through the identity service user directory or the list of application roles Dynamically through an XPath expression For example: If the task has a payload message attribute named po within which the owner is stored, you can specify an XPath expression such as: `/task:task/task:payload/po:purchaseOrder/po:owner` `ids:getManager('jstein', 'jazn.com')` The manager of `jstein` is the task owner. The task owner can view the tasks belonging to business processes they own and perform operations on behalf of any of the assigned task participant types. Additionally, the owner can also reassign, withdraw, or escalate tasks. The task owner can be considered the business administrator for a task. The task owner can also be specified in the Advanced tab of the Create Human Task dialog. The task owner specified in the Advanced tab overrides any task owner you enter in this field.
Application Context	Enter the name of the application that contains the application roles used in the task. This indicates the context in which the application role operates. If you do not explicitly create a task, but end up having one, you can set up the context.