Flow Step Trigger (After,Before,Error) Flow Behavior
  • Updated on 14 Apr 2017
  • 3 minutes to read
  • Print
  • Dark
    Light

Flow Step Trigger (After,Before,Error) Flow Behavior

  • Print
  • Dark
    Light

This tutorial demonstrates how to use Flow Step Trigger Flow Behavior in Decisions . This Flow Behavior may be used for Flow debugging purposes. There are 3 types of such Flow Behavior : After, Before , and Error . The Flow with one of these behaviors is applied to the step in another Flow and can be triggered Before/After step execution or if step throws an Error .
Example:
In this example we are going to build a simple Flow Step Trigger Flow and use it on a step in different Flow .
We begin in the Designer Folder with clicking Create Flow on the Actions Panel. In the resulting pop-up window we Name the Flow.
2018-06-27_133340-1.png

2018-06-28_162553.png

Then, from the Properties panel under Settings > Behavior Type drop-down list we pick one of Flow Step Trigger types:

  • After : Flow triggered after Step execution
  • Before : Flow triggered before Step execution
  • Error : Flow triggered if Step throws an Error

In this example we pickFlow Step Trigger (After) .
2018-06-28_162701.png

In Flow Designer we add Log (Fast) step from All Steps [Catalog] > Flow Management category.
2018-06-28_162920.png

Then, we connect outcome from Log (Fast) step to the End Step in our Flow , and select Log (Fast) step to configure data mapping.
In this example we are going to configure Constant Debug level Input . Next, we Ignore all logs except log 01 . For log 01 Input we set Text Merge.Plain Mapping Type and click Show Editor.
InMerge Text Editor we use Step Run Data to compose our log message. Mention, Step Run Data is available in all Flow Step Trigger Flow types and contain information about the Step execution. When finished, we can click Ok to save and continue.
2018-06-29_104904.png

InMerge Text Editor we use Step Run Data to compose our log message. Mention, Step Run Data is available in all Flow Step Trigger Flow types and contain information about the Step execution. When finished, we can click Ok to save and continue.
Next, we locate log Category Input , set Text Merge.Plain Mapping Type , and click Show Editor.
2018-06-29_104431.png

In the Merge Text Editor we use data from Step Run Data to compose ourlog Category . Then, click Ok to save and continue.
2018-06-29_130449.png

This completes our Flow . We save the Flow and close Flow Designer.
Back in the Designer Folder we click Create Flow on the Folder Actions Panel. Then, we Name the Flow and click CREATE to proceed to the Flow Designer.
2018-06-29_135129.png

In the Flow Designer we add Create Data step from the Favorite Steps category.
2018-06-29_135159.png

Next, we click Show Editor under Data Definitions for Create Data step.
2018-06-29_135241.png

In the Data Definitions we add some simple data and click Close to save and continue.
2018-06-29_135336.png

Then, we locate Testing and Simulation options for Create Data step. Under Triggers options we can see Before Trigger Type, After Trigger Type and Error Type . Here we can add our Flow Step Trigger Flows . Also, for each type we have 3 options:

  • None : do nothing
  • Store : save step execution details
  • Run Flow : use Flow Step Trigger Flow to do what we need

We pick Run Flow under After Trigger Type.
2018-06-29_142323.png

Next, using Flow Picker we pick our Trigger Flow and click PICK to continue.
2018-06-29_155248.png

This completes our Main Flow . We click Debug Flow on the top panel of the Flow Designer.
2018-01-08_114430.png

If we navigate to System > Administration > System Tools > Logging Folder in the Portal we should  see that our Log about Create Data Step execution in Main Flow is saved under Debug level.
2018-06-29_161400.png

Was this article helpful?