Creating the Human Task Using the User Task Properties Dialog

• Create a BPMN process

• Add a user task

• From the user task implementation properties dialog box, create a Human Task

  For more information see Creating a Human Task from Oracle BPM Studio.

• Create the corresponding taskflows using SOA Suite

Creating the Human Task Using the Human Task Editor:

• Create a Human Task from the SOA Composite Editor

  For more information see Creating a Human Task from the SOA Composite Editor.

• Create the corresponding taskflow using SOA Suite

• Create a BPMN process with user tasks

• Implement the user tasks in the BPMN process using the defined Human Tasks

  For more information see Implementing a User Task with an Existing Human Task .

Using an existing Human Task:

• Create a BPMN process

• Add a user task.

• In the user task implementation properties dialog box, select the existing Human Task.

  For more information, see How to Implement a User Task With an Existing Human Task .

You can create a Human Task from the User Task Properties dialog box in Oracle BPM Studio.

To create a Human Task from Oracle BPM Studio:

When you create a Human Task from Oracle BPM Studio you can configure the outcome of the Human Task. The outcome values you configure appear as the available actions of the Human Task in Oracle BPM Worklist.

To configure the outcome of a Human Task:

You can add multiple parameters to a Human Task to build the Human Task payload. Oracle BPM Studio uses this parameters to create the data association of the user task that uses the Human Task.

To add a parameter to a Human Task:

When you create a Human Task you must define an outcome target. The outcome target maps the result of the Human Task to a String data object in your BPM project.You can base the flow of your process on the value of the outcome target using an exclusive gateway.

To configure the outcome target of a Human Task

The Human Task automatically appears in the HumanTasks predefined module in the business catalog. You can use the Human Task to implement the user task you are editing or other user tasks in the BPM project.

You can edit the created Human Task using the Human Task editor to configure implementation details.

To edit a Human Task using the User Task Properties dialog box:

You can add a user task to a BPM project using the SOA Composite editor.

To create a Human Task from the SOA Composite Editor:

When you create a Human Task from the SOA Composite Editor, the Human Task you created is available to implement the user tasks in your BPM project. For more information on how to do this, see Implementing a User Task with an Existing Human Task .

You can implement a user task using an existing Human Task that you created for another user task or using the Human Task editor.

To implement a user task with an existing Human 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.

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.

   1. Right-click a module.

   2. Select New and then select Business Object.

   3. Select Based on External Schema.

   4. Click the Browse button.

   5. Select Copy to Project.

   6. Click Browse Resources.

      The Type Chooser dialog box opens.

   7. 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 box.

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.

You can edit a Human Task used in your BPM project using the Human Task editor. Generally you use the Human Task editor to edit complex human tasks.

To edit a Human Task using the Human Task Editor:

When using the Human Task editor in a BPM Suite installation, you can specify an email address for the recipient of a Notification.

To specify an email address for the recipient of a notification:

To configure Oracle UCM Repository for task attachments:

1. In the Project Navigator tree, expand the Business Catalog node.

2. Expand the Human Tasks node.

3. Double-click the Human Task you want to configure.

   The Human Task Editor appears.

4. Click the Documents tab.

5. Select Use Document Package.

   A section to configure metadata properties appears. The table already contains the mandatory standard metadata: Security Group and Document Type.

6. Optionally add new standard or custom metadata properties:

   1. Click the Add button.

   2. Click the Name column to select a standard property from the list or to enter a custom name.

   3. Click the Value column to assign a value to the property. Select By Name to provide the text to assign the value to the property, or By Expression to provide an expression.

   4. Click the Display column to select a display mode:

      Editable: the user can provide a value in the task form when uploading the attachment.

      Hidden: the value does not appear in the task form

      Read-Only: the value appears in the task form but the user cannot modify it

   Note:

   Custom metadata does not appear in the task form, so you must map the value to a task payload or provide a static value.