How to Add a Business Object Attribute

14-4 Modeling and Implementation Guide for Oracle Business Process Management

8. Click OK.

14.2.2 What Happens When You Assign an Existing Human Task to a User Task

The user task uses the existing Human Task for its implementation. The SOA Composite displays the relationship between the BPMN process and the Human task by adding a wire between them. When the BPMN Service Engine runs the user task implementation it invokes the Human Workflow Service with the parameters defined in the data association of the user task. When the Human Workflow Service finishes running the Human Tasks it provides the result to the BPMN Service Engine using the defined data association.

14.2.3 How to Associate the Process Payload to the Human Task Payload

To associate the process payload to the Human Task payload you must configure the Human Task, the user task and start events in the BPMN process and create a business object based on the payload xsd file. To associate the process payload to the human task payload: 1. Create a business object using the Based on External Schema option. a. Right-click a module.

b. Select New and then select Business Object.

c. Select Based on External Schema.

d. Click the Browse button.

e. Select Copy to Project.

f. Click Browse Resources.

The Type Chooser dialog opens. g. Select the type of the business object from the payload xsd file. 2. Edit the start event in your BPMN process. 3. Define a custom argument using the business object you created as its type. 4. Add a process data object to your process using the business object you created as its type. 5. Define the data associations between the custom argument and data object.

6. In the Human Task editor, click the Data tab.

7. Select Add other payload from the list in the Add button. 8. Select the payload element in the Type Chooser dialog.

9. In the Process editor, right-click the user task and select Properties.

10. Define the data associations between the process data object and the task payload.

14.3 Creating a Human Task from Oracle BPM Studio

You can create a simple Human Task using Oracle BPM Studio. The simplified interface Oracle BPM Studio provides hides the complexity of the Human Task editor by exposing only those fields that are relevant to Oracle BPM. After you create the Using Human Tasks 14-5 Human Task using the simplified editor, you can edit it using the SOA Human Task editor if needed. The simplified Human Task editor Oracle BPM Studio provides, enables you to define the following properties: ■ Title Defines the name of the Human Task that is displayed to end-users in the Oracle BPM WorkSpace and WorkList applications. ■ Priority Specifies a priority for the Human Task. Valid values are between 1 highest priority and 5 lowest priority. The default value is 3. ■ Re-Initiate Restarts the approval process from the beginning ■ Outcomes Specifies the outcome possible outcome arguments of the Human Task. Oracle BPM Worklist displays the possible outcomes you select as the available tasks to perform at run time. ■ Parameters Define the Human Task payload. The Human Task data association is based on the parameters of the Human Task. The data association maps the data objects as input arguments. ■ Outcome Target Specifies a String data object to store the outcome argument of the Human Task. You can only select one data object. The Advanced User Task Properties enable you to define the following properties: ■ Initiator Specifies the user who initiates a task. The initiator can view their created tasks from Oracle BPM Worklist and perform specific tasks, such as withdrawing or suspending a task. ■ Owner Specifies the User ID of the task owner ■ Identification Key Defines 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 This field is required if you are using multiple realms. You cannot have assignees from multiple realms working on the same task. ■ Application Context Specifies the name of the application that contains the application roles used in the task. This indicates the context in which the application role operates.