This page is for application designers who want to define a process using a workflow diagram, and then connect elements of the diagram to PhixFlow dashboards and actions in an application. This page describes properties
...
An actionflow diagram is made up of a series of nodes. Each node represents a specific action. By configuring different actions and wiring them together you can create complex functionality. This section describes the properties of the different action nodes. This page has the properties for the following nodes:
- SaveDelete Todo-Fiona - check
- Gateway
- Open Screen
- Open URlURL
- Lookups
- Request Query Lookup
- Streaming Driving Query Lookup
For details of the calculate node, see Calculate Action Nodes
Adding Action Nodes
Connection Points
To add action nodes to the actionflow, drag the icons from the toolbar to the canvas. Everything in an actionflow is connection connected using connection points. They are blue when connected and grey when not connected. Find all the possible connection points below.
...
Icon | Description | Connection Points | How to wire this action | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Create | |||||||||||||||||||||||||||||||||||
| Add another complete actionflow as a node within this actionflow. This is useful to reuse existing actionflows, or to refactor a complex workflow by moving part of the logic to its own node. |
| The input and output connection points of the actionflow node must be wired into the rest of the actionflow. Need to test to add detail | ||||||||||||||||||||||||||||||||
| Add an action to open a specified dashboard (screen). Only use this action as the final node in an actionflow or branch of it. |
| Open screen nodes can be created with or without a screen attached. This is useful if the screen has not been created yet. Open screen nodes which do not have a screen attached appear with a warning symbol to remind users that this still needs to be configured.
Each open screen node has 1 primary input connection point by default called 'in'. Connecting to this connection point simply opens the screen and cannot pass any data to it. Do we still need this? Once a screen has been attached to the open dashboard node an input connection point for each form on the screen is created. Each input connection point automatically has any data fields on the form (dynamic text or form fields) added as attributes. These attributes can be mapped to and supplied with data. Each input connection point has the following properties:
Configure the purpose for the screen that will open
To set the actionflow to close the active dashboard on completion, on the top right of the canvas, tick Close Parent Dashboard. | ||||||||||||||||||||||||||||||||
| Add a node for a data view. The actionflow uses views to look-up additional data to use when processing stream-items. | Connect a view node to the action node that needs to look-up data via the lookup connection icon page. A look-up connection has 2 parameters:
| |||||||||||||||||||||||||||||||||
| Add an action to manipulate the data that is passed to the calculate action. In the calculate action, write an expression using one or more of the 115+ functions available in PhixFlow. | ||||||||||||||||||||||||||||||||||
| Add an action to deletes the specified stream-items passed to the node. | ||||||||||||||||||||||||||||||||||
| Add a node to specify decision logic. Gateways control the route that stream-items take as they flow through the actionflow. | ||||||||||||||||||||||||||||||||||
| Add a node to saves the specified stream-items to their stream. | ||||||||||||||||||||||||||||||||||
Tap | tbc | ||||||||||||||||||||||||||||||||||
Task | tbc | ||||||||||||||||||||||||||||||||||
List | |||||||||||||||||||||||||||||||||||
| List actionflows available to your application. | ||||||||||||||||||||||||||||||||||
| List dashboards available to your application. | ||||||||||||||||||||||||||||||||||
| List tables available to your application. |
...
Field | Description | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | Enter the name for the action node. | ||||||||||||||||
Show in the Explorer | An application can have many actionflows, and an individual actionflow can have many actions. This can lead to many items being listed in the repository. Use this option to omit the action from the repository.
| ||||||||||||||||
Stream Item Action | Todo-Fiona- find out if this can be renamed to something else unless it really relates to existing stream item actions. Available for save actions. Select the specific change to make to the stream-items:
| ||||||||||||||||
Stream Name | Select the stream Todo-Fiona why isn't this identified by the parent of the attribute/stream-item? | ||||||||||||||||
Exclusive | Available for gateway actions.
|
Input Connection Points
This section has a toolbar with standard buttons. The grid contains a list of the wires that pass data into the action.
...
Calculate actions process data using expressions; see pages in the topic Expressions and Scripts.
This section has a toolbar with standard buttons. The grid contains a list of the expressions that the calculate action will perform. To add a new expression:
...