Broadway Flow - Stages

A Broadway flow is a graph / tree built of several Stages where each Stage is a step of the flow that can include one or more Actors. The flow's Stages are executed consecutively from left to right. When there are several Stages on the same level, the execution order is top down. The Actors within each Stage are also executed top down.

This article describes the following Stage features:

How Do I Add or Delete a Stage?

A Stage can be added anywhere in the flow.

  • To add a Stage to the end of the flow, click the big + in the empty Stage area.

  • To add a Stage in the middle of the flow, click image in the right corner of the Stage to open the Stage context menu and select either Insert After or Insert Before.

  • To delete a Stage, click Delete in the Stage context menu.

    • If the Stage has a dependent branch, it is also deleted.
    • Starting from Fabric 6.5.3, the dependent branch is marked with red color and the confirmation message is displayed on top of the flow window. This is in order to allow the user to verify whether the Delete result is what he/she expected.

    Flow-Plus Icon

How Do I Split or Merge the Stages?

Each Stage can be split into two (and so on) to create several stages on the same dependency level.

To split a Stage, click image in the right corner of the Stage to open the Stage context menu and select Split.

The Split's logic depends on the position of the Stage in the flow and includes the following rules:

  • The first Stage in the flow (root) cannot be split.
  • If the Stage before the current Stage is not split, the current Stage is split into two.
  • If the Stage before the current Stage is split (for example, there are four Stages on the same level), the current Stage is split into the same number of Stages.

What is a Stage Condition?

If a condition is required in the flow, the flow can be split and a Stage Condition Actor can be added to one or more Stages that have been created as a result of the split.

The condition Actor can have any number of output parameters; however a True / False check is always performed on the first output parameter. Note that this parameter does not need to be Boolean, since Broadway automatically casts its type to Boolean. For example, an empty string is considered to be false while a string that is not empty is considered to be true.

Click for more information about Broadway data types.

The else condition can be set on a Stage on the same level as the Stage Condition and is only executed if all conditions are false. Stages without a Stage condition are always executed and do not impact the else Stage.

The Stage's conditions impact all subsequent Stages in the same branch. Thus:

  • If a Stage condition is false, the execution of its branch stops.
  • A merged Stage will run after all its parent Stages have been executed.
  • If no parent Stages have been executed (all conditions are false), the merged Stage is not executed.

How Do I Define a Stage Condition?

To add a Stage condition to the flow, click image in the right corner of the Stage to open the Stage context menu and select Stage Condition to add an Actor to the Stage. The added Actor is green.

image

To mark a Stage as else, click image > Else.

image

Note that although any Actor can be used as a condition, a JavaScript Actor is a powerful actor for expressing complex conditions. The script returns the value of the last line and does not expect the return keyword.

Elseif Stage Condition

Starting from V8.0, you can define elseif conditions. When a Stage is split into several Stages on the same dependency level, you can define the elseif logic by adding a Stage Condition and marking the same stage as else. The conditions of all Stages of the same level will continue to be evaluated top -> down, by the following rules:

  • Start by evaluation of all Stages with a condition only (and without else).
  • If none of them is true, evaluate all Stages with else and a condition, in a top -> down order.
  • If none of them is true, execute the else Stage.

In the below example, the order of the Stage execution is: Stage 2 -> Stage 5 -> Stage 3 -> Stage 4.

image

Stage Conditions Example

The following example displays a split flow with a condition and an else Stage where each branch is then also split into a condition and an else Stage.

Depending on the flow's input, the execution can run via one of four alternatives on the third level.

image

Previous

Broadway Flow - Stages

A Broadway flow is a graph / tree built of several Stages where each Stage is a step of the flow that can include one or more Actors. The flow's Stages are executed consecutively from left to right. When there are several Stages on the same level, the execution order is top down. The Actors within each Stage are also executed top down.

This article describes the following Stage features:

How Do I Add or Delete a Stage?

A Stage can be added anywhere in the flow.

  • To add a Stage to the end of the flow, click the big + in the empty Stage area.

  • To add a Stage in the middle of the flow, click image in the right corner of the Stage to open the Stage context menu and select either Insert After or Insert Before.

  • To delete a Stage, click Delete in the Stage context menu.

    • If the Stage has a dependent branch, it is also deleted.
    • Starting from Fabric 6.5.3, the dependent branch is marked with red color and the confirmation message is displayed on top of the flow window. This is in order to allow the user to verify whether the Delete result is what he/she expected.

    Flow-Plus Icon

How Do I Split or Merge the Stages?

Each Stage can be split into two (and so on) to create several stages on the same dependency level.

To split a Stage, click image in the right corner of the Stage to open the Stage context menu and select Split.

The Split's logic depends on the position of the Stage in the flow and includes the following rules:

  • The first Stage in the flow (root) cannot be split.
  • If the Stage before the current Stage is not split, the current Stage is split into two.
  • If the Stage before the current Stage is split (for example, there are four Stages on the same level), the current Stage is split into the same number of Stages.

What is a Stage Condition?

If a condition is required in the flow, the flow can be split and a Stage Condition Actor can be added to one or more Stages that have been created as a result of the split.

The condition Actor can have any number of output parameters; however a True / False check is always performed on the first output parameter. Note that this parameter does not need to be Boolean, since Broadway automatically casts its type to Boolean. For example, an empty string is considered to be false while a string that is not empty is considered to be true.

Click for more information about Broadway data types.

The else condition can be set on a Stage on the same level as the Stage Condition and is only executed if all conditions are false. Stages without a Stage condition are always executed and do not impact the else Stage.

The Stage's conditions impact all subsequent Stages in the same branch. Thus:

  • If a Stage condition is false, the execution of its branch stops.
  • A merged Stage will run after all its parent Stages have been executed.
  • If no parent Stages have been executed (all conditions are false), the merged Stage is not executed.

How Do I Define a Stage Condition?

To add a Stage condition to the flow, click image in the right corner of the Stage to open the Stage context menu and select Stage Condition to add an Actor to the Stage. The added Actor is green.

image

To mark a Stage as else, click image > Else.

image

Note that although any Actor can be used as a condition, a JavaScript Actor is a powerful actor for expressing complex conditions. The script returns the value of the last line and does not expect the return keyword.

Elseif Stage Condition

Starting from V8.0, you can define elseif conditions. When a Stage is split into several Stages on the same dependency level, you can define the elseif logic by adding a Stage Condition and marking the same stage as else. The conditions of all Stages of the same level will continue to be evaluated top -> down, by the following rules:

  • Start by evaluation of all Stages with a condition only (and without else).
  • If none of them is true, evaluate all Stages with else and a condition, in a top -> down order.
  • If none of them is true, execute the else Stage.

In the below example, the order of the Stage execution is: Stage 2 -> Stage 5 -> Stage 3 -> Stage 4.

image

Stage Conditions Example

The following example displays a split flow with a condition and an else Stage where each branch is then also split into a condition and an else Stage.

Depending on the flow's input, the execution can run via one of four alternatives on the third level.

image

Previous