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 introduces the following nodes and how to connect them:childrenlinks to further details about the.
Child pages (Children Display) |
---|
For information about connecting actionflow nodes together, see Wiring Actionflows.
Adding Action Nodes
The toolbar includes the following action nodes that you can drag onto the actionflow canvas.
...
Everything in an actionflow is connected using connection points. They are blue when connected and grey when not connected. Find all the possible connection points below.
Excerpt |
---|
hidden | true |
---|
name | _actionflow_connection_points |
---|
|
| Connection Point | Relevant to | Description |
---|
Image Added | Interface Driving Connection Point | Input Interface Output Interface | - Defines the data attributes the actionflow is expecting as an input. This data is then used in the Actionflow using
Insert excerpt |
---|
| _driving_connection |
---|
| _driving_connection |
---|
nopanel | true |
---|
| s and remains constant. - Defines the data attributes the actionflow is expected to output. This data can then be mapped back onto components on the screen the action is being used.
- Each instance of the actionflow will map in its own set of data onto the expected data inputs/outputs of the connection point.
| Image Added | Interface Request Connection Point | Input Interface Output Interface | - Defines the data (and events) the actionflow is expecting as an requested input. This data is then used in the actionflow using
Insert excerpt |
---|
| _request_connection |
---|
| _request_connection |
---|
nopanel | true |
---|
| s and remains constant. - Each instance of the actionflow will map in its own set of data onto the expected data inputs.
| Image Added | Driving Output Connection Point | Input Data Components Insert excerpt |
---|
| _action_calculate |
---|
| _action_calculate |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_view_driving |
---|
| _action_view_driving |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _actionflow |
---|
| _actionflow |
---|
nopanel | true |
---|
|
| - A data source which drives the actionflow. Data is pushed through the actionflow using
Insert excerpt |
---|
| _driving_connection |
---|
| _driving_connection |
---|
nopanel | true |
---|
| 's. - Data flows from the
Insert excerpt |
---|
| _driving_output_connection_point |
---|
| _driving_output_connection_point |
---|
nopanel | true |
---|
| to the Insert excerpt |
---|
| _driving_input_connection_point |
---|
| _driving_input_connection_point |
---|
nopanel | true |
---|
| . - Has attributes which can be mapped to any
Insert excerpt |
---|
| _driving_input_connection_point |
---|
| _driving_input_connection_point |
---|
nopanel | true |
---|
| only.
| Image Added | Driving Input Connection Point | Output Data Components Insert excerpt |
---|
| _action_calculate |
---|
| _action_calculate |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_view_driving |
---|
| _action_view_driving |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_save |
---|
| _action_save |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_screen |
---|
| _action_screen |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_url |
---|
| _action_url |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_analysis |
---|
| _action_analysis |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
| - A data receiver. Data is received from
Insert excerpt |
---|
| _driving_connection |
---|
| _driving_connection |
---|
nopanel | true |
---|
| 's. - Has attributes which can be mapped to any
Insert excerpt |
---|
| _driving_output_connection_point |
---|
| _driving_output_connection_point |
---|
nopanel | true |
---|
| only.
| Image Added | Request Output Connection Point | Input Data Components Insert excerpt |
---|
| _action_view_request |
---|
| _action_view_request |
---|
nopanel | true |
---|
|
| - Provides lookup data to the actionflow using
Insert excerpt |
---|
| _request_connection |
---|
| _request_connection |
---|
nopanel | true |
---|
| 's. - Any node with a
Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
| can perform a lookup to a node with a Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| . - Has request attributes and data attributes
- Request attributes are used in filtering. They are mapped to request attributes on the node performing the lookup. Request attributes are referenced in the nodes filter using
req.[attributename] Data is flowing from the Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
| to the Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| . - Data attributes are mapped to data attributes on the node performing the lookup. These attributes are the actual data that is being returned from the lookup.
Data is flowing from the Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| to Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
|
| Image Added | Request Input Connection Point | Insert excerpt |
---|
| _action_calculate |
---|
| _action_calculate |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
| - Performs a lookup to
Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| 's. - Has request attributes and data attributes
- Request attributes are used in filtering. They are mapped to request attributes on the node being looked up to. Attributes that need to be sent to the node in order to filter the data must be added as request attributes.
Data is flowing from the Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
| to the Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| . - Data attributes are mapped to data attributes on the node being looked up to. These attributes are the actual data that is being received from the lookup.
Data is flowing from the Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| to Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
|
|
|
| Connection Point | Relevant to | Description |
---|
| Interface Driving Connection Point | Input Interface Output Interface | - Defines the data attributes the actionflow is expecting as an input. This data is then used in the Actionflow using
Insert excerpt |
---|
| _driving_connection |
---|
| _driving_connection |
---|
nopanel | true |
---|
| s and remains constant. - Defines the data attributes the actionflow is expected to output. This data can then be mapped back onto components on the screen the action is being used.
- Each instance of the actionflow will map in its own set of data onto the expected data inputs/outputs of the connection point.
|
| Interface Request Connection Point | Input Interface Output Interface | - Defines the data (and events) the actionflow is expecting as an requested input. This data is then used in the actionflow using
Insert excerpt |
---|
| _request_connection |
---|
| _request_connection |
---|
nopanel | true |
---|
| s and remains constant. - Each instance of the actionflow will map in its own set of data onto the expected data inputs.
|
| Driving Output Connection Point | Input Data Components Insert excerpt |
---|
| _action_calculate |
---|
| _action_calculate |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_view_driving |
---|
| _action_view_driving |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _actionflow |
---|
| _actionflow |
---|
nopanel | true |
---|
|
| - A data source which drives the actionflow. Data is pushed through the actionflow using
Insert excerpt |
---|
| _driving_connection |
---|
| _driving_connection |
---|
nopanel | true |
---|
| 's. - Data flows from the
Insert excerpt |
---|
| _driving_output_connection_point |
---|
| _driving_output_connection_point |
---|
nopanel | true |
---|
| to the Insert excerpt |
---|
| _driving_input_connection_point |
---|
| _driving_input_connection_point |
---|
nopanel | true |
---|
| . - Has attributes which can be mapped to any
Insert excerpt |
---|
| _driving_input_connection_point |
---|
| _driving_input_connection_point |
---|
nopanel | true |
---|
| only.
|
| Driving Input Connection Point | Output Data Components Insert excerpt |
---|
| _action_calculate |
---|
| _action_calculate |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_view_driving |
---|
| _action_view_driving |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_save |
---|
| _action_save |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_screen |
---|
| _action_screen |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_url |
---|
| _action_url |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_analysis |
---|
| _action_analysis |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
| - A data receiver. Data is received from
Insert excerpt |
---|
| _driving_connection |
---|
| _driving_connection |
---|
nopanel | true |
---|
| 's. - Has attributes which can be mapped to any
Insert excerpt |
---|
| _driving_output_connection_point |
---|
| _driving_output_connection_point |
---|
nopanel | true |
---|
| only.
|
| Request Output Connection Point | Input Data Components Insert excerpt |
---|
| _action_view_request |
---|
| _action_view_request |
---|
nopanel | true |
---|
|
| - Provides lookup data to the actionflow using
Insert excerpt |
---|
| _request_connection |
---|
| _request_connection |
---|
nopanel | true |
---|
| 's. - Any node with a
Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
| can perform a lookup to a node with a Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| . - Has request attributes and data attributes
- Request attributes are used in filtering. They are mapped to request attributes on the node performing the lookup. Request attributes are referenced in the nodes filter using
req.[attributename] Data is flowing from the Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
| to the Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| . - Data attributes are mapped to data attributes on the node performing the lookup. These attributes are the actual data that is being returned from the lookup.
Data is flowing from the Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| to Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
|
|
| Request Input Connection Point | Insert excerpt |
---|
| _action_calculate |
---|
| _action_calculate |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
| - Performs a lookup to
Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| 's. - Has request attributes and data attributes
- Request attributes are used in filtering. They are mapped to request attributes on the node being looked up to. Attributes that need to be sent to the node in order to filter the data must be added as request attributes.
Data is flowing from the Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
| to the Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| . - Data attributes are mapped to data attributes on the node being looked up to. These attributes are the actual data that is being received from the lookup.
Data is flowing from the Insert excerpt |
---|
| _request_output_connection_point |
---|
| _request_output_connection_point |
---|
nopanel | true |
---|
| to Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
|
|
...
HTML Comment |
---|
|
Properties HTML Comment |
---|
| The following icons are for post 9.0 action nodes Icon | Description | How to wire this action |
---|
Insert excerpt |
---|
| _action_file |
---|
| _action_file |
---|
nopanel | true |
---|
|
| Add an action to use a file in a specified location in the PhixFlow database. check restrictions on location |
| Insert excerpt |
---|
| _action_email |
---|
| _action_email |
---|
nopanel | true |
---|
|
| Add a node to generate an email. |
| Insert excerpt |
---|
| _action_write |
---|
| _action_write |
---|
nopanel | true |
---|
|
| Add a node to write data what does this do. |
|
|
Insert excerpt |
---|
| _parent |
---|
| _parent |
---|
nopanel | true |
---|
|
Basic SettingsTodo-Fiona - How do you specify the different types of gateway 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. Insert excerpt |
---|
| _check_box_tick |
---|
| _check_box_tick |
---|
nopanel | true |
---|
|
to display this action node in the repository. Insert excerpt |
---|
| _check_box_untick |
---|
| _check_box_untick |
---|
nopanel | true |
---|
|
to omit this action node 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: - Either: Todo-Fiona
- Insert: create a new stream-item in the stream.
- Update: change part of the stream-item in the stream.
- Delete: delete the stream-item from the stream. Todo-Fiona- check about delete node, Adam think sit may be going away.
Insert excerpt |
---|
| _terms_changing |
---|
| _terms_changing |
---|
nopanel | true |
---|
|
| 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. Insert excerpt |
---|
| _check_box_tick |
---|
| _check_box_tick |
---|
nopanel | true |
---|
| Todo-Fiona Insert excerpt |
---|
| _check_box_untick |
---|
| _check_box_untick |
---|
nopanel | true |
---|
| Todo-Fiona |
This section has a toolbar with standard buttons. The grid contains a list of the wires that pass data into the action. To edit an existing connection, double-click its name in the list. To add a new create a new attribute: click and set its properties. Todo-Fiona- why would this be usefulDrag add an existing attribute to this list Todo-Fiona- is this possible?? To remove attributes, select one and click Insert excerpt |
---|
| _delete_item |
---|
| _delete_item |
---|
nopanel | true |
---|
|
Output Connection PointsTodo-Fiona Insert excerpt |
---|
| _access |
---|
| _access |
---|
nopanel | true |
---|
|
Access Permissions section is available for gateway actions. Insert excerpt |
---|
| _description |
---|
| _description |
---|
nopanel | true |
---|
|
Todo-Fiona - Under what circumstances does the pop-up toolbar appear
- screenshot
Option | Description |
---|
Permanantly Delete with a Cross not a bin |
| Show Action Instance Details → Show properties |
|
|
|
|
...