In an actionflow, individual actions have connection points to receive data from the previous action.
...
For most action nodes, data flow is configured when you map attributes to the input connection points. For Gateway nodes, you can also control the data flow by mapping to output conenction points. This is because the expressions in a gateway provide the logic for which path the data flows, and different paths may require different data to pass through the gateway.
Overview
...
Connections can be
...
Everything in an actionflow is connected using connection points. They are blue when connected and grey when not connected. There are two types of connections:
Insert excerpt |
---|
| _driving_connection |
---|
| _driving_connection |
---|
nopanel | true |
---|
|
and Insert excerpt |
---|
| _request_connection |
---|
| _request_connection |
---|
nopanel | true |
---|
|
For information about the concepts related to wiring actionflows together using connection points, see Wiring Actionflows.
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 |
---|
| _action_view |
---|
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 |
---|
|
|
|
Input Connection Properties
Insert excerpt |
---|
| _parent |
---|
| _parent |
---|
nopanel | true |
---|
|
Basic Settings
Field | Description |
---|
Name | By default input connections are named in . Optionally, replace this with a descriptive name. |
Type | Select one of: Todo-Fiona - check definitons are correct - Driving: where data is being used by the action node
- Requested: when the input is coming back from a lookup
|
Data Attributes
This section has a toolbar with standard buttons. The grid contains a list of the attributes that will pass through the input wire to this action. PhixFlow automatically lists the attributes that pass into the action when the actionflow is wired to an input with attributes. You can also:
...
The data attribute properties has sections for Parent Details , Audit Summary and the following Basic Settings
Field | Description |
---|
Name | By default input connections are named in . Optionally, replace this with a descriptive name. |
Type | Select one of the data types - String
- Bigstring
- Integer
- Float
- Decimal
- Date
- Datetime
- Graphic
- TrueFalse
|
...
Output Connection Properties
Insert excerpt |
---|
| _parent |
---|
| _parent |
---|
nopanel | true |
---|
|
Basic Settings
Field | Description |
---|
Name | By default input connections are named in . Optionally, replace this with a descriptive name. |
Expression | Todo-Fiona - standardised expression |
Order |
|
...
Actionflow Wire Properties
Wire properties do not include the name. Todo-Fiona - check - I thought I saw where you could change its name
Basic Settings
Field | Description |
---|
Input | The action at the start of this wire. |
Input Connection Point |
|
Output | The action at the end of this wire. |
Data Mappings
Standard text
Request Mappings
todo