Action inputs and outputs
Understanding action inputs and outputs
When you create a workflow using the workflow editor you configure each action node to create an output (or perform an action such as sending an email). The output is dependent on the input from either the trigger node or a preceding action node.
The following example of a basic four node workflow using an event trigger, illustrates the principle of input and output for action nodes.
The workflow is triggered when a certain type of project is created and proceeds as follows:
- The project item is used by the relation action to determine the teams associated with the project.
- In this example there are two teams (Team 1 and Team 2), which are the output of the first relation operator node.
- This output becomes the input for the next relation action, which determines the list of team members in the two teams.
- In this example there are four team members, two in Team 1 and two in Team 2. This output becomes the input for the next create item action node.
- The create item action creates four items as the total number of members was four.
If you configure the create action to a single instance you will only get one item, see Create item.
Alloy allows you to configure workflows where the output of an action includes data based on the input of any stage within a branch. Each node is assigned a stage as you create a workflow.
The following example illustrates the output that occurs when you link the
Team attribute in the stage 4 action node to the
Team attribute of the input to the stage 3 action node, see Workflow link attributes. The
Team attribute displays the linked team name.
When creating workflows you can link multiple attributes between stages within the same branch to create complex workflows.
Alloy also provides you with Workflow Computations that can be used within workflows through the API, see Workflow Computations.