Actionflow Page Layout
The illustration shows the layout of an Actionflow:
1.Toolbar
- Action Nodes perform specific actions, e.g. enrich data using a calculate node or connect to an external API using a HTTP node
- Action nodes can be dragged onto the canvas to create a new action
- Certain action nodes can be clicked to see existing objects, e.g. click Open Screen to list existing screens, then drag from the Repository onto the canvas
- Canvas Properties relate to the canvas itself, e.g. aligning content and zooming out
2. Settings
Origin 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- Error rendering macro 'excerpt-include' : No link could be created for '_actionflow_event_location'.takes the user to the screen containing the instance of the Actionflow and highlight in the layers where the Actionflow is being triggered
Instances displays a list of the instances where the Actionflow is being reused, along with that instance's datasource, component and event type 
/ 
Close screen after action completes closes the screen where the Actionflow is being used, once it has finished- / 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
Nodes are the building blocks of Actionflows, they perform specific tasks and are wired together to make up the overall Actionflow.