Flow Control

Overview

Flow control objects (also known as arrows or links) are devices that connect objects inside a workflow together to make it a cohesive unit and define the logical flow of the workflow, which is its progression from one element to the next as it runs. An arrow originating from one object and pointing at another signifies that control is being passed from the previous object to the ensuing object. A workflow executes along the path of any arrow containing the value equaling that of the previous object.

Arrows can behave differently depending on which object is their parent (that is, which object they stem from). They don't simply connect two objects together, but they have fundamental meaning as well. Arrows can diagram the logical progression through the course of a workflow dependent on specific events or conditions that may occur during execution of subsequent workflow objects.

To obtain a better understanding of flow control arrow behavior and view an assortment of examples, see Workflow Logic.

Related Topics

Arrow types

There are three types of flow control arrows, each possessing their own unique characteristics. The table below lists the available arrows along with a brief description. For more details about a specific arrow, click the associated link.

Icon Object Description
Success Arrow Color coded green and proceeds to the object it is linked to providing that the previous object it stems from ran successfully.  
Failure Arrow Color coded red and proceeds to the object it is linked to provided that the previous object failed or generated an error. Ideally used to link to an alternate task that corrects the issue encountered by the failed task.
Result Arrow Color coded blue and mainly used in conjunction with the Evaluation object to provide conditional branching during a workflow's execution. For more on the Evaluation object, see Evaluation Object.

Linking objects

For convenience, single-clicking an object in the workspace displays a small flow control arrow (also known as nub) on the upper right corner. This arrow can be dragged to another workflow object to link them both. To use a Failure (red) arrow, drag it from the Available Objects pane to the workspace then connect each end of the arrow to the desired objects.

NOTE: An arrow is connected to an object properly when a green dot appears between the arrow and the object. Also the word ‘Success’ will change from the color gray to the color black.

Additional notes

There are some basic practices to follow when using arrows to link from one object to another:

  • The Result arrow should only be used to link from an Evaluation Object to other objects because only the Evaluation object can provide an answer (that is, the result) to a question (that is, the evaluation).

  • Along with a Result Arrow, an Evaluation object can also be followed by a Success or Failure arrow. This is because Evaluation objects treat a True Result as a Success and a False Result as a Failure.

  • Do not use a Failure arrow to link from event objects (for example, Schedule and Key events). Only the Success arrow should be used to link from events to other objects because events are designed primarily to trigger workflow execution. Unlike conditions, events lack behavioral properties that allow it fail.

  • If a condition is used as a triggering object at the start of a workflow, it should only be linked to a Success arrow and not a Failure arrow. This is because the Behavior tab settings of a triggering condition is set to Wait for condition and Indefinitely. In other words, it will wait for the specified condition to occur indefinitely, therefore, has no possibility to fail.