Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 5 Next »

What is a Gateway Action?

The  Gateway action acts as a decision point and controls the path that records take as they flow through an Actionflow. Data flow is controlled by the expressions on each output connection points and these provide the logic for which path the data flows. Several output connection points can be added, with decision logic on each one.

Exclusive vs Inclusive

Control whether or not a record can go through more than one output. 

 Exclusive Gateway (Single path)

 to make a record go through the first connection point where the condition is met. 

 Inclusive Gateway (Multiple Paths)

 to make a record go through all connection points where the condition is met. 

Rules

For each output connection point, rules (expressions) can be defined to be evaluated. If the condition is met, the record will go through the connection point or points (depending on if the gateway is exclusive or inclusive, see above).

Example Setup

This is an example of a simple gateway Actionflow that receives an order status. Where the order status is Complete, the data is saved but where the order status is Open, an email is sent.

Creating Gateway Actions

  1. Click and drag the  Gateway icon in the toolbar onto the canvas
  2. Enter a name for the Gateway action, then select Create Action
  3. In the Gateway action  Properties on the right:

    1.  or Exclusive

    2. Define Rules for each output connection point clicking the  icon 

    3.  Apply and Close all settings
  4. Hover over the  Gateway action on the canvas to see the output connection points
    1. Click on each connection point to connect it to another action node
    2. Once connected, the rules can be changed directly on the connector by right-clicking and choosing 

Worked Example

Here's a worked example using the Shop Data (available from the Learning Centre).

In this example, we are using:  

  • A Shop Stock screen containing a grid of the Shop Stock data, a pie chart of the Shop Stock data and a grid of the Shop Departments data  - this screen was created using the Multi-Tile template

If you are completing this chapter as part of the Actionflow course and using a training instance, the data and screens have already been pre-loaded into the Actionflow Intermediate Application. For this example, we'll be working on the grid on the Shop Stock screen.

GIF/SCREENSHOT OF FINISHED RESULT

 Configuring a View to Read Only and Auto Save

Error rendering macro 'excerpt-include' : No link could be created for '2.02 In-Grid Editing Actionflows'.


  1. For the Auto Save Action Method, choose  Actionflow
  2. For the Auto Save Actionflow, click the  icon to create a new Actionflow 
    1. Name: NumberCheck

1.02 Actionflow Principles

  • No labels