Decision steps

Decision steps allow conditional routing within a flow, for example where one incoming path gets split into two or more outgoing paths, based on pre-conditions. This is achieved using outcomes and business rules within a flow.

Overview

Decision steps can have multiple outcomes connected both into and out of them, and effectively act as a conduit to define the path that a flow should take. This is achieved by adding business rules to the outcomes. See Business rules.

For example, a page step could be set up so that when a user selects an item in a table, this value is passed into a decision step, and a business rule (or rules) assigned to any outcomes that then define which outcome/path in the flow the user is directed along.

Adding a decision step

To add and configure a decision step:

1. Add a decision step onto the canvas.

2. Link any outcomes into the decision step, passing any values that may be needed for the routing logic.

3. Link and edit any required outcomes from the step to define the various paths that can be taken:

   • Define the order in which the outcomes should be evaluated and processed using the Order field on the outcome. For example, setting an order to '1' will mean that outcome is checked before an outcome with an order set to '2'.

   • Add business rules for each outcome to define the routing logic by clicking Create Business Rules when setting up the outcome. See Business rules.

A worked example - using a decision step to route a flow

In this example, a flow is being used to present an interactive game to users.

1. A page step presents a user with the option to scan one of four different QR codes in order to select which type of game they wish to play.

2. Depending on which option is scanned, the user is then routed to the corresponding operator step, which sets a simple string value "[QR String]" to the name of the selected game. In this example, the user has scanned the "Geothermal" option, so the value is set to "Geothermal".

3. This value is then used by a decision step ("Which energy Type?") to route the user to the relevant outcome and instructions page using business rules configured against each outcome.

   Each of the outcomes has a business rule applied that handles the routing logic. It will cycle through each outcome in the order specified, and check whether the business rule criteria has been met, before moving onto the next outcome. For example, the "Geothermal" outcome business rule checks whether the value was set to "Geothermal", and if not it will move to the next outcome.

   

4. In this example, the user is routed to the 'Geothermal Instructions' page that provides information on how to play the game.

Adding an outcome

Outcomes can be added to a decision step.

• Adding Outcomes to a step

Adding comments to a step

Comments can be added to a decision step.

• Adding Comments to a step