Define Business Events > Defining business events > Defining Cloud Application Integration processes for user-triggered business events
  

Defining Cloud Application Integration processes for user-triggered business events

If you do not want to use any predefined approval workflows, define workflows in Cloud Application Integration as processes. Processes contain sets of instructions that automate your business requirements.
To use Cloud Application Integration processes as workflows, add at least one Service step that's a generic user task or an originator user task. These user tasks indicate that the process requires user interaction as part of the workflow. Generic user tasks define actions for users included in the workflow. Originator user tasks define actions for users who trigger a workflow with their activity.
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 .
For example, you might want to define a process that has three approval steps where three approvers review the record.
To define a process with a Service step that is set to Generic User Task or Originator User Task, perform the following tasks in Application Integration:
  1. 1Create a process
  2. 2Define the input fields
  3. 3Define the output fields
  4. 4Define a Service step
  5. 5Define additional process steps

MDM Multi-Step Approval Template

The MDM Multi-Step Approval Template is a predefined template process that you can use to design your own processes.
The MDM Multi-Step Approval Template has example steps that demonstrate how to create an approval process with a Start step, Service steps, and additional process steps. The template includes examples of parallel and sequential steps. You can review the template process and then create a process based on your requirements.
You can find the template in the Business360 folder.
Important: Don't use the MDM Multi-Step Approval Template as your process. Copy the template and modify it to fit your business needs.

Create a process

Use Cloud Application Integration to create a process. For more information about creating a process, see the Cloud Application Integration help.
    1In Application Integration, select New.
    The New Asset dialog box appears.
    2Select Processes > Process, and then click Create.

Define the input fields

Define the required input fields for the process on the Start step.
    1In the Properties panel, on the General tab, type a unique name, and then click the Input Fields tab.
    2Add the following input fields with their types:
    Input Field
    Type
    input
    Text
    template
    Template. You can find Template when you click More types > Custom Types.
    taskTypes
    Task Types. You can find Task Types when you click More types > Custom Types.

Define the output fields

Define the required output fields for the process on the Start step. The output field values are set when the process executes and are then available in the steps that follow. These output fields don't appear in lists until the values are returned from a process. You define a name and type for the output fields for use in a process.
    1In the Properties panel, click the Output Fields tab.
    2Add the following output fields with their types:
    Output Field
    Type
    approved
    Text
    approvedBy
    Text

Define a Service step

Add a Service step and set the service action to Generic User Task or Originator User Task.
    1To add a Service step to the process, drag the Service step from the palette on the left to the canvas.
    2In the Properties panel, on the General tab, enter a unique name, and then click the Service tab.
    3Set the following properties for the service:
    Property
    Value
    Service Type
    System Service
    Action
    MDM > HumanTask > Generic User Task or MDM > HumanTask > Originator User Task.
    4Click the Input Fields tab.
    5Configure values for the following input fields:
    Input Field
    Value
    TaskName
    Unique name of the Service step that you specified in step 2. This name appears on the Workflow Inbox page for business users when a business event triggers a workflow that includes this task.
    Template
    template
    TaskTypes
    taskTypes
    Change List
    input
    Task Actions
    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.

Define additional process steps

Define additional process steps to access data, services, and perform related orchestration activities. Each process step completes and 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:
Field
Description
LastAction
The last task action, such as approve, reject, or send back.
LastApprover
The identifier of the user who took the last action.
For more information about adding process steps, see Adding Process Steps in the Cloud Application Integration help.
After you add all additional process steps, save and then publish the process.

Rules and guidelines for updating Application Integration processes defined within business events

Consider the following rules and guidelines when you update Application Integration processes defined within a business event: