...
When the user triggers an action with a mouse-click or keyboard-press, PhixFlow processes the actionflow. Actionflows can affect data, for example by making changes to recordsstream-items, such as update or delete.
...
- Check the input provided is appropriate
- Add the new customer record stream-item to the CRM database
- Provide a confirmation message.
...
- data interactions - save, delete, add
- data calls and calculations - connecting to data to look-up, use or process recordsprocess stream-items
- screen interactions - to open or close screens in the application
- another actionflow - this means you can represent a complex step as a single node
- gateways - decision points with logic to determine which path PhixFlow takes next.
...
You can resuse an actionflow throughout your application. This means you only need to create one actionflow for functionality that occurs on different screens or layouts, such as to save or update records stream-items. You can also include an actionflow as a node within another actionflow.
...
- 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 todo - check - driving and request?- 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 todo.
- 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 (table)
- related attirbutes
- sorting and filtering of recordsof 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.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|