- 24 Oct 2022
- 3 Minutes to read
- Updated on 24 Oct 2022
- 3 Minutes to read
Steps are defined as the building blocks of Flows; they act as a marker of individual points within a Flow's process. Steps are a visual representation of what the back-end code is accomplishing. Similar to a coding language, Inputs and Outputs are defined to and from steps so that data can be moved to the right places.
As the name suggests, steps operate sequentially. This means that the Output data of one step can be used to define the Input values of any step that comes after it.
Rather than manually program their function and data values, Decisions presents and compiles these configurations in a clean user-friendly interface. To help users locate and access these steps, the step Toolbox tab (located within the Flow Designer) contains multiple categories that house steps within the Decisions environment. This includes thousands of pre-built steps that represent common and complex functions in coding languages. Some features may include:
- Sending an Email or displaying a Popup message.
- Deserializing JSON and Converting File Data.
The following document discusses the Steps and the basics of using them within the Flow Designer.
The Toolbox houses all steps available in the Flow Designer; this tab can be controlled with Visibility Rules. Steps can also be added to the Toolbox via the SDK, Integration configuration, or Modules. Steps can be added to the workspace by dragging and dropping them from the Toolbox.
Add Step Dialog
The alternate method of adding a step to the Flow is through the use of the Add After window. The Add After window appears when the orange arrow at the end of a step outcome path is selected or if the arrow is dragged into some blank workspace. When a step is selected from this window, a text box is shown to rename the step icon label as it will appear in the Flow.
Flow Step Properties
Every step has a function that helps with accomplishing the goal in a workflow. The screenshot below depicts a Flow where the Start step connects to an Add step, which then connects to an End step. The Add step is able to take in two values of the Decimal datatype and add them together, then use that equated value to define the step output. Flows can contain several steps, all with different functions and moving values that would otherwise have to be configured in code.
When a step is placed into the Flow, the step can be selected so that the Properties tab populates with the available configurations for this step. Steps have inputs and outputs that specialize in moving data throughout the Flow. There are different sections of required and optional configuration settings that pertain to the steps function.
Multiple Outcome Flow Steps
Some steps in Decisions come with multiple outcome paths by default, meaning several different lines will stem from the step after it is placed. For example, Run Rule steps have two outcome paths, one for a True outcome and one for False. The data that is compared against the rule would follow the True or False path accordingly, either of which could lead to several other steps in the Flow.
All steps have the option to add additional outcomes from the Outcomes section of the corresponding step properties. These additional outcomes include a No Data Result path and an On Exception path. In a case where no data is reaching the step, the No Data Result path would be triggered, where Flow steps could follow to handle that occurrence. In a case where the step has an exception at runtime, the On Exception path would be triggered, leading to other Flow steps.
The Branch/Merge feature allows for a single outcome path to be split into several different paths, then connected again into a single path. If the Branch step is used to create paths, a Merge step must connect all of them.