This topic is for application designers who want to understand the concepts of actionflows.
todo-anthony find this
| Note |
|---|
For applications created in PhixFlow versions 8.3 and earlier, use actions and stream item actions to configure user interaction with data; see Using Stream Actions. This page explains the concepts of the new actionflow feature, introduced in PhixFlow 9.0. |
...
As you add nodes to the actionflow, you wire the output connector of one node to the input connector on the next. In this way, you are create the logical steps needed to complete a specific piece of functionality. Todo UPDATE -Anthony Update picture
Reusing Actionflows
...
| Note |
|---|
When you reuse an actionflow, you do not create a copy of it. You are using the actionflow itself. An instance of an actionflow is the combination of the actionflow and its input connections. You can change an actionflow and the same change occurs in all the instances where it is used. The changes do not affect the input connections to the actionflow. todo Todo-Anthony - check this is true: However, if you remove or add nodes, you will need to wire the input/output connectors for all the instances of the actionflow. |
For each instance of an actionflow, you specify which data the actionflow takes by wiring to connectors. This means you can connect to attributes with any name.
todo Todo-Anthony - how do you select an actionflow to reuse it.
...
Dashboards have a section called unreachable actions - Todo-todo Anthony - what this means and how to use it.
...
- Toolbar
The toolbar contains icons that you drag onto the actionflow canvas to create the different nodes, such as a calculate action. - Source
If the source is empty, you are editing the actionflow.
If the source contains a name, you are editing an actionflow instance.
The source indicates what triggers the actionflow. This can be:- the name of the component, such as a button
- an event, such as a double-click If this is empty then the user is editing the Actionflow directly.
- Options
These options affect the entire workflow, such as hiding the loading spinner. - Inputs
Inputs to an actionflow- Event starts the actionflow. Events can be:
- either a user-triggered action, such as a mouse click on a button.
- or system-triggered action such as a task plan.
- View provides data to the actionflow. The event acts upon data in the same area, or nested within the area. A view is a combination of:
- a stream.
- related attributes.
- sorting and filtering of stream-items.
- data display, such as grid or form fields.
- Event starts the actionflow. Events can be:
- Connectors
These specify the data and events that the actionflow requires. All instances of the actionflow require appropriate inputs to be wired to these connectors.
Connectors collect data, pass data back to the calling object and perform lookups on data. todo - more detail - Action Nodes
The nodes on the diagram represent individual action that pass or process the data from the connectors. Nodes can also look-up data from other sources, for example to add parameters to a calculation.
...