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.
-
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:
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
icon, and choosing Open Data Association.
- By selecting an activity in a structured process, and then clicking the Data Association
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
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.
- By clicking an activity in a structured process, clicking the More
-
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.
Define Conditions for Data Associations
There may be a business scenario where you want a data association to execute in runtime only when a particular condition fulfills. Control the execution of data associations in runtime by adding conditions to them in the Data Association editor.
A data association that has been configured with conditional mapping executes in runtime only when the defined condition fulfills. Otherwise, it fails to execute. All other data associations that do not have conditional mapping defined execute normally in runtime.
To define a new condition: