Configure Data Associations

Data association refers to the flow of data within a workflow. Use the data association editor to define input and output for workflow elements 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. A user task, for example, needs both input and output data association.

  • On the input side, it needs data input into the user task (referred to as its payload).
  • On the output side, after the task has completed, it needs output from the task to data objects, to store results for use elsewhere.
  1. Open a workflow.
  2. Select the user task, click More icon and then click Open Data Association.
    The data association editor appears. 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 the center pane. Use the empty pair of fields to create a new association.
  3. In the data association editor, click the Input tab to define data input into the user task, and the Output tab to define data output resulting from the user task.
    • The Input tab is selected by default. 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.
    • Click the Output tab and notice how the left and right panes changes. Now the left pane displays the user task’s payload, and the right pane displays the variables available in the workflow.
  4. 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.

  5. 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.
    If the data association is valid, the data association icon turns green. The icon turns red for an invalid association.
  6. 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.
  7. 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 workflow.
  8. Click Apply to save the data associations.

Task Exec Variables

Task exec variables can be mapped in output data associations to store task execution details in your workflow.

When configuring output data associations for a user task, the following task exec variables are supported:

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