The data flow of a workflow is the manner in which the workflow element input and output parameters bind to workflow variables as each element of the workflow runs. You define the data flow of a workflow by using schema element bindings.

When an element in the workflow schema runs, it requires data in the form of input parameters. It takes the data for its input parameters by binding to a workflow variables that you set when you create the workflow, or by binding to an variable that a preceding element in the workflow set when it ran.

The element processes the data, possibly transforms it, and generates the results of its run in the form of output parameters. The element binds its resulting output parameters to new workflow variables that it creates. Other elements in the schema can bind to these new workflow variables as their input parameters. The workflow can generate the variables as its output parameters at the end of its run.

Element bindings

You must bind all workflow input and output parameters. Bindings set data in the elements, and define the output and exception behavior of the elements. Links define the logical flow of the workflow, whereas bindings define the data flow.

To set data in an element, generate output parameters from the element after processing, and handle any errors that might occur when the element runs, you must set the element binding.

Input binding
Set a schema element's incoming data. For most schema elements, you can do this from the Inputs/Outputs menu of the General tab.
Output binding
Define the output parameters used when an element finishes its run. For most schema elements, you can do this from the Inputs/Outputs menu of the General tab.
Output Exception bindings
Link to exception handlers if the element encounters an exception when it runs.

Output exception bindings write values into the bound source parameter.

If the element changes the values of the input parameters that it receives when it runs, you must bind them to a workflow variable by using an output exception binding. Binding the element's output parameters to workflow variables lets other elements that follow it in the workflow schema to take those output parameters as their input parameters.

A common mistake when creating workflows is not to bind output parameter values to reflect the changes that the element makes to the workflow variables.

Important: When you add an element that requires input and output parameters of a type that you have already defined in the workflow, Automation Orchestrator sets the bindings to these parameters. You must verify that the parameters that Automation Orchestrator binds are correct, in case the workflow defines different parameters of the same type to which the element can bind.

Define Element Bindings

After you link elements to create the logical flow of the workflow, you define element bindings to define how each element processes the data it receives and generates.

Prerequisites

Verify that you have a workflow schema in the Schema tab of the workflow editor, and that you have created links between the elements.

Procedure

  1. Log in to the Automation Orchestrator Client.
  2. Navigate to Library > Workflows, and select your workflow.
  3. Select the Schema tab.
  4. Select a workflow element.
  5. On the General tab of the element configuration window, expand the Inputs/Outputs option.
  6. Add the appropriate workflow input or output parameters from the list of existing parameters and variables.
  7. To save your changes to the workflow schema, click Save.

Results

You defined the input parameters that the element receives and the output parameters that it generates, and bound them to workflow variables and parameters.

What to do next

You can create forks in the path of the workflow by defining decisions.