Actionflow Page Layout

The illustration shows the layout of an Actionflow:

1.Toolbar

 .

2. Settings

• Insert excerpt
  _actionflow_origin _actionflow_origin nopanel true

   indicates the event that triggers the Actionflow instance. It displays its location in a hierarchy showing: name of the screen → component → event type, such as a double-click

• Insert excerpt
  _actionflow_event_location _actionflow_event_location nopanel true

   takes the user to the screen containing the instance of the Actionflow and highlight in the layers where the Actionflow is being triggered

• Insert excerpt
  _actionflow_instances _actionflow_instances nopanel true

   displays a list of the instances where the Actionflow is being reused, along with that instance's datasource, component and event type.

• Insert excerpt
  _toggle_off _toggle_off nopanel true

  / 

  Insert excerpt
  _toggle_on _toggle_on nopanel true

  Close screen after action completes closes the screen where the Actionflow is being used, once it has finished

• Insert excerpt
  _toggle_off _toggle_off nopanel true

  / 

  Insert excerpt
  _toggle_on _toggle_on nopanel true

  Hide loading spinner will hide the loading icon that appears after a set amount of time to indicate the Actionflow is running

3. Phases

Actionflows can be made up of multiple phases. The first phase will run automatically when the action is triggered. Any additional phases will run when prompted to by a Start Phase node. 

4. Inputs

Defines the input(s) that initiates the Actionflow. These are specific to the instance of the Actionflow being used. 

5. Connection Points

Define the data, or event(s), expected by the Actionflow and what it will return. All instances of the Actionflow use this Connection Point(s). 

6. Action Nodes

Action Nodes are the building blocks of Actionflows, they perform specific tasks and are joined using connectors to make up the overall Actionflow. 

7. Connectors

Connectors are used to connect Action Nodes together and facilitate the mapping of data through the Actionflow.

1.4 04 Connection Points