How to Use a Business Object in a Process What Happens When You Use a Business Object in a Process

Using Human Tasks 14-1 14 Using Human Tasks This chapter describes how to implement BPMN user tasks using Human Tasks. You can use an existing Human Task component created using the SOA Human Task editor, or you can create a new Human Task using the simplified interface Oracle BPM Studio provides. This chapter includes the following sections: ■ Section 14.1, Introduction to Human Tasks in BPM ■ Section 14.2, Assigning an Existing Human Task to a User Task ■ Section 14.3, Creating a Human Task from Oracle BPM Studio ■ Section 14.4, Creating a Human Task Using the SOA Human Task Editor ■ Section 14.5, Editing a Human Task from Oracle BPM Studio ■ Section 14.6, Using Human Task Patterns in Oracle BPM For detailed information about Human Tasks, see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

14.1 Introduction to Human Tasks in 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. For more information on how to define Human Tasks using Oracle SOA Suite, see the following chapters in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite: ■ Designing Human Tasks ■ Designing Task Forms for Human Tasks 14-2 Modeling and Implementation Guide for Oracle Business Process Management Figure 14–1 Human Task components in the Business Catalog This figure shows the Human Tasks components in the Sales Quote example. The business catalog stores all the Human Tasks components in the BPM project within the predefined module HumanTasks. 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 23.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.

14.1.1 Typical Design Workflow

There are two approaches to working with Human Tasks in Oracle BPM: ■ Creating the Human Task using the SOA Human Task editor ■ Creating the Human Task using the simplified interface Oracle BPM provides Note: When you define a human task in BPM the callback is implicitly defined.