Design

Back Next

MDM human tasks

Informatica Intelligent Cloud Services

Business 360 Console uses the

Application Integration

processes as workflows for the user-triggered and system-generated business events. If you do not want to use any predefined approval workflows in Business 360 Console, define a process in

Application Integration

and use it to configure business events. These processes must contain at least one human task.

A human task indicates that the process requires user interaction as part of the workflow. The MDM human task supports the following user tasks:

Generic User Task. Defines actions for users included in the workflow.

Originator User Task. Defines actions for users who trigger a workflow with their actions.

You can use the predefined MDM Multi-Step Approval Template to design a process. For more information about the predefined template, see MDM Multi-Step Approval Template.

To configure an MDM human task in a Service step, select

MDM > HumanTask > Generic User Task

MDM > HumanTask > Originator User Task

as a system service action.

The options other than Generic User Task
and Originator User Task
under HumanTask
are reserved for future use.

The following image shows the MDM human task properties:

The image shows the input and output fields that you can configure for a General User Task.

Input Fields

Configure the following input fields in the Service step for an MDM human task:

Template: Required. The template field that you added to the
Input Fields
tab of the Start step.
TaskTypes: Required. The taskTypes field that you added to the
Input Fields
tab of the Start step.
Change List: Required. The input field that you added to the
Input Fields
tab of the Start step.
TaskName: Required. The unique name of the Service step that you specified on the
General
tab.
Task Actions: Required. The list of actions that the users can perform with this step. Use a semicolon as a delimiter. For example,
Send for Translation;Send Back to Originator;Release
. You can also use the action text to provide more information on the next process step. The output that returns from each task action must be handled within the process.

Output Fields

You can use the

LastAction

and

LastApprover

fields to define additional process steps, such as Assignment step or Decision step, to access data and services and to perform related orchestration activities. Each process step returns information about the last approver and the last action taken by the approver.

The following fields store the step values that the additional process steps return:

LastAction: The last task action, such as Send for Translation, Send Back to Originator, or Release.
LastApprover: The identifier of the user who took the last action.

For step-by-step instructions about creating a process with a human task, see Defining Cloud Application Integration processes for user-triggered business events.

System Service Actions

Download Guide

Watch

Comments

Cloud Application Integration Homepage