Actionflow Page Layout
The illustration shows the layout of an Actionflow:
If you are completing this chapter as part of the Actionflow course and using a training instance, load the Actionflow Foundation Application and navigate to the tab. Open the Actionflow, Save (TeacherForm) to view alongside this page.
1.Toolbar
.
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
- Location takes the user to the screen containing the instance of the Actionflow and highlights the component 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 data source, 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 these 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.