Configure Data Association

Data association refers to the flow of data within a process. Use the data association editor to define input and output for activities that need them.

A data association involves a source and a target, where the source provides a value or an expression to be assigned to the target. An approval human task, for example, needs both input and output data association.

  • On the input side, it needs data input into the activity (referred to as its payload).

  • On the output side, after the activity has just finished, it needs output from the activity to data objects, to store results for use elsewhere in the process.

To configure data association:

  1. For a structured process, select an activity that needs data association, such as a human task or service task, click More iconand then select Open Data Association . (This option is active when the selected activity needs association.)
    The data association editor opens. Use its center pane as a canvas for mapping associations, by dragging and dropping elements from the left and right panes. Any data associations already configured display below Data Association. You use the empty pair of fields to create a new association.

    Note:

    Oracle Cloud Infrastructure Process Automation creates data associations for you in some cases, such as when you create a human task or start event with a form.
    1. Notice that the Input tab is selected. The left pane displays source objects (Data Objects) in an expandable tree. The right pane displays the payload, or entry parameters the activity needs to perform its function.
    2. Click the Output tab and notice how the left and right panes change. Now the left pane displays the task’s payload, and the right pane displays the variables available in the process.
  2. For a dynamic process, select a human task activity or a service activity. Click More icon, select Data Association and then select Input to configure input data association. (This option is active when the selected activity needs association.)
    You can configure output data association by selecting Output.
  3. In the Input tab begin creating a new association by dragging an input object from the Data Objects tree and dropping it in the input field titled New Association. You can also begin typing and select from auto-complete options that appear using the inline expression builder. To specify attributes within objects, enter a . (period) and select from the list that displays.

    See Work with Expressions.

    The input source provides the value or expression to assign to the target. You select variables related to the process (such as data objects) to map to the specific parameters the activity needs to perform its function (its entry parameters).

  4. Complete the association by dragging an output object from the payload tree and dropping it in the output field. You can also begin typing and select from auto-complete options that appear using the inline expression builder.

    Oracle Cloud Infrastructure Process Automation validates the new association and displays a green association icon if valid, or a red association icon and error if invalid:

    Valid data association icon Valid data association

    Data association invalid icon Invalid data association

  5. If needed, create additional associations and reorder them.
    Drag and drop an association to move it up or down in the associations list. Associations are executed in the order in which you position them. For example, if multiple associations assign a value to the same object, the last assigned value is used.
    As you edit, click the Undo or Redo buttons as needed.
  6. Click the Output tab, and create output data associations. You can think of the output as though the activity has just finished, and likely contains results that you'd like to store for use elsewhere in the process.
  7. Click Apply to save the data associations.
    You can save invalid associations and fix them later. Note that you can't deploy applications that contain validation errors.

Data Association Tips

Use the Data Association Editor to add, edit, delete, and reorder data associations.

Below are tips for configuring data associations.

  • The following activities need data association. Note that some activities have only output, such as a start form event, which captures the data end users enter into the form.

    • Human

    • System

    • Events, except timer catch and end events

  • You can access the data association editor:

    • By clicking an activity in a structured process, clicking the More More icon icon, and choosing Open Data Association.
    • By selecting an activity in a structured process, and then clicking the Data Association Data association icon icon that is present at the top right of the process editor.
    • By clicking a human or service activity in a dynamic process, clicking the More More icon icon, and then selecting Data Association. Choose Input to configure the activity's input data, and choose Output to configure the activity's output data.

  • In the Data Association Editor, click the Input tab to define data input into the activity, and the Output tab to define data output resulting from the activity.

  • Dropping an object into an association field that already contains a value replaces its value. If you drop an object into an input field that ends with an operator, the object name is appended to the field's contents.

  • You can use predefined variables in data associations for structured and dynamic processes. Predefined variables contain process execution information. They enable users to use process execution information such as instanceId, creatorName, createdDate and so on in data association. Note that predefined variables are read only, and their values can't be edited.

Human Task Exec Variables

The following human task exec variables are supported in output data associations:

Variable Description Type
taskExec.taskId Task number String
taskExec.title Title String
taskExec.approverDisplayName First name and last name of latest approver. String
taskExec.summary Summary String
taskOutcome Outcome of a task. For example, APPROVE or REJECT. String
taskExec.approvers Details of each approver. Use when multiple approvers act on a task. Array of objects, contained fields.
taskExec.approvedDate Date of task action. For example, date of approval. DateTime
taskExec.approver System identifier of latest approver. String
taskExec.createdDate Created Date DateTime
taskExec.approvedDate Date on which action is taken. For example, the date when approval is taken for a task. DateTime
taskExec.assignedDate Assigned Date DateTime
taskExec.priority Specify the priorities as:
  • 1 for high
  • 2 for medium
  • 3 for low
 int
taskExec.fromUser Creator or user who reassigned the task. Object (Identity Type). Contains the following fields:
  • id
  • name
  • display name
  • type
taskExec.approverName Username of the latest approver. String
taskExec.dueDate Due date DateTime

Process Variables

The following process variables are supported in output data associations:

Variable Description Type
businessKey Business key String
creatorid IDCS Id String
creatorType User applicant String
createdDate Date of creation DateTime
documents Document Document
processExec.title Process title String
processExec.instanceId Process Id String
processExec.creatorName Creator username String
processExec.creatorDisplayName Creator display name String