Go to Step or Anchor v3.0.0 Help ​

Redirects the Flow to any Step or Anchor.

How can I use the Step? ​

The Step lets you move between different parts of your Flow. You can use the Step to set a destination to a specified point, collect data from another branch, or iterate with various values.

How does the Step work? ​

The Step redirects the Flow to a specific Step or Anchor based on target settings. In addition, you can handle the limit of redirects and set an Anchor to the Step itself.

Target settings ​

To redirect the Flow to a specific target, follow these steps:

  1. For Target, select one of the following options:
    • Selected Step: Allows to pick the target from the list of Steps.
    • Step label: Allows to set the target Step using its label. The input is case-sensitive.
    • Anchor name: Allows to set the target anchor using its name. The input is case-sensitive. It can only include letters, numbers, $, or underscore characters and cannot start with a number.
    • Previous anchor: Sets the target to the previous anchor in the same branch.
  2. Specify the Step or Anchor to redirect the Flow to - the input option depends on the selected target.
  3. Optional: Turn on Handle invalid targets in a separate exit to enable an invalid exit for invalid targets. If turned off, the Step handles such cases along with other errors.

Anchor options ​

Using Anchor options, you can set an Anchor on the Step itself. The following setting is available:

  • Set an anchor on this Step: Enable to set an anchor name on this Step.
  • Ancor name: Enter the anchor name. The input is case-sensitive. It can only contain letters, numbers, $, and underscore characters. Any names with white spaces will be trimmed to camel case. If the anchor name begins with a number, the number will be replaced with $.

Note: Anchors are registered during Flow activation, but Merge field-based anchors are set up during Step execution. To avoid errors or unexpected behavior, create the Merge field value you intend to use as the anchor name before reaching the anchor Step and pass Flow through the anchor Step before redirecting to the anchor.

Loop handling ​

With Loop handling, you can limit the number of redirects to a specific Step and choose how to handle that limit using the limit exit. This way, you can prevent endless loops and ensure an efficient workflow.

The following settings are available:

  • Set the limit of redirects: Enable to set the limit of redirects to a specified number.
  • Limit of redirects: Enter the number of loops to perform.
  • Handle limit through limit exit: Enable the use of limit exit to manage the limit of redirects.
  • Reset limit on exit: Enable to reset the limit of redirects on the limit exit.

Error Handling ​

By default, the Handle error toggle is on, and the Step handles errors with a separate exit. If any error occurs during the Step execution, the Flow proceeds down the error exit.

If the Handle error toggle is disabled, the Step does not handle errors. In this case, if any error occurs during the Step execution, the Flow fails immediately after exceeding the Flow timeout. To prevent the Flow from being suspended and continue handling errors, you can place the Flow Error Handling Step before the main logic or your Flow.

Reporting ​

After the Step completes, it generates a report that includes its execution status and other details. You can customize the report by adjusting the Step's log level and adding tags.

Log level ​

By default, the Step's log level matches that of the Flow. You can change the Step's log level by selecting an appropriate option from the Log level dropdown.

Tags ​

Tags provide a way to classify and search for sessions based on their attributes. To create a new tag, specify its category, label, and value. You can then use tags to filter and group the sessions in the report.

Service dependencies ​

  • flow builder v3.42.0
  • event-manager v2.0.1
  • deployer v2.18.0

Release notes ​

v3.0.0

  • Initial release
  • Replace Go to Step in Current Flow v2.0.3