Insert excerpt

	_Banners
	_Banners
name	actionflow
nopanel	true

This page provides details of the properties for the input and output connection points, which you use to wire toghether nodes in an actionflow.

Overview

Use the input and output connection points on nodes in an actionflow to wire the nodes together.

For input connection points, map which attributes to pass into the node.
For output connection points, specify an expression to determine ??? passed onto the next node.

Live Search
spaceKey @self
additional none
placeholder Search all help pages
type page

Panel

borderColor	#00374F
titleColor	white
titleBGColor	#00374F
borderStyle	solid
title	Sections on this page

Table of Contents

maxLevel	3
indent	12px
style	none

Input Connection Points

From the Inputs pane on left, into the actionflow.
From one node to another within the actionflow.
Hover your mouse pointer over a node and click Add Output to add an connector to another node.
From a final actionflow node to the Outputs pane on the right of the actionflow.

Connection points available depend on the purpose of the node.

Output connection points:
- Calculate
- Gate
- View

Nodes without an output connection represent:

either the end of actionflow processing: Save Action Configuration, Open Screen Action Configuration and Open URL Action Configuration
or processing out of the actionflow: Analysis Action Configuration

When you wire nodes together, you need to map which attributes pass through to the next node. To change the mapping, click on the connector to open the Mapping window.

Node properties have sections for Input Connection Points and Output Connection Points on the node. Double-click on a listed connection point to open its properties.

Note
The properties available for connection points vary depending on the node on which they occur.

Driving and Lookup Connection Points

If you connect a node via a driving connection, records are returned individually to the connected node and flow one by one through the remainder of the actionflow.
If you connect a node via a lookup connection, the records are returned as an array within one recordset. Nodes wired via lookup connection points require both:
- Data Attributes: add attributes from the view. PhixFlow looks-up data from these attributes.
- Request Attributes: when the actionflow runs, PhixFlow returns the data to these attributes.

The following sections explain the properties for input and output connection points.

Connection Points
Anchor
input
input

Open the

Insert excerpt

	_property_settings
	_property_settings
nopanel	true

for each connection point (input, lookup, output) by clicking on the node.

Image Added

Insert excerpt
_property_tabs
_property_tabs
name basic-h
nopanel true

Insert excerpt

	_parent
	_parent
nopanel	true

Basic Settings

Field	Description	Connection Point Found On
Name

Enter the for connection pint.Type

Driving

Requested - lookup

Data Attributes and Request Attributes

A list of attributes in other action nodes that you can map into this node. You can refer to these attributes in a gateway's

Actionflow.

Insert excerpt

	_input
	_input
name	caps
nopanel	true

Insert excerpt

	_lookup
	_lookup
nopanel	true

Insert excerpt

	_output
	_output
name	caps
nopanel	true

Action Phase

The

Insert excerpt

	_action_phase
	_action_phase
nopanel	true

that the connection point is in. See Actionflow Phases.

Insert excerpt

	_

driving_output_connection_point_driving_output_connection_pointnopaneltrue expression using the syntax:

Code Block
connectionpointname.attributename

Request Attributes are available when Type is Request.

You can also add a new attribute by specifying the properties Name and Type; see Attributes for details of these properties

input
	_input
name	caps
nopanel	true

Insert excerpt

	_lookup
	_lookup
nopanel	true

Insert excerpt

	_output
	_output
name	caps
nopanel	true

Validation

Field

Description

Connection Point Found On

Minimum Records

The minimum number of records that the Actionflow needs to run. If the received records are not above the minimum set, the Actionflow will not run.

Insert excerpt

	_input
	_input
name	caps
nopanel	true

Insert excerpt

	_lookup
	_lookup
nopanel	true

Maximum Records

The maximum number of records that the Actionflow is permitted to run. If the received records exceed the maximum set, the Actionflow will not run.

Insert excerpt

	_input
	_input
name	caps
nopanel	true

Insert excerpt

	_lookup
	_lookup
nopanel	true

Input Parameters

Field

Description

Connection Point Found On

Name

The name of the input parameters (attributes) mapped into the Actionflow.

Insert excerpt

	_

property_tabs_property_tabsnameaccess-h

input
	_input
name	caps
nopanel	true

Insert excerpt

	_lookup
	_lookup
nopanel	true

Insert excerpt

	_output
	_output
name	caps
nopanel	true

Type

The data type (e.g. integer) of each input parameter (attribute) mapped into the Actionflow.

Insert excerpt

	_input
	_input
name	caps
nopanel	true

Insert excerpt

	_

accessaccessauditauditOutput Connection Points

Default Expression

A value or expression that is evaluated when no value is mapped to the attribute, or if the value is null or unavailable (e.g. if the user did not have permission to see it).

Default value expressions do not use the order they are set in and are automatically resolved in the appropriate order based upon other attributes they reference.

For referencing attributes, use the notation, in.attributeName

Note
If ${_NULL} is entered, this will convert to a null value, not an empty string.

Insert excerpt

	_

property_tabsproperty_tabsbasic-hparentparent

Basic Settings

FieldDescriptionNameThe name of the connection pointExpression

Expression

OrderOrder

Output Connection Points

FieldDescriptionExclusive

Used to control if a stream-item can flow through more than one option.

Insert excerpt_check_box_tick_check_box_ticknopaneltrue the stream-item flows out the first connection point where the condition is met

Tip

If the

Insert excerpt

	_run_action
	_run_action
nopanel	true

tool is used on an Actionflow containing Default Expressions, the default values can be overridden on the Run Action window using the tick boxes. True/false fields with a Default Expression of true will be toggled off. To enable, tick the tick box and toggle on.

Expand

title	See example

Image Added

Input Connection Points

See Input Connection Points.

Input Connections

A grid of Input Connections.

Open Screen Action Input Connections

The following properties are available for Input Connections for

Insert excerpt

	_action_screen
	_action_screen
nopanel	true

action nodes only.

Field

Description

Role

Specify whether the actionflow will provide data to the view or screen being opened.

Primary: selected by default.
The view or screen opens regardless of data.
Component:
The actionflow provides data to the view or screen when it opens.

Type

Available when Role is Component.

Specify the type of connection:

Insert excerpt
_driving_input_connection_point
_driving_input_connection_point
nopanel true
: there can be only one of these.
Insert excerpt
_request_

checkboxuntickcheckboxuntick the stream-items will flow out of any connection point where the condition is met.

Output paths process data using expressions; see pages in the topic Expressions and Scripts.

Gateways can have an unlimited number of output paths.

Stream-items will only pass through the output paths if the condition set in the expression is met.

Note
Remember to check if if the gateway has been marked as Exclusive. Records will only pass through the first output path where the condition is met if the gateway is exclusive.

: there can be multiple of these

Open Mode

Excerpt

name	screenInputConnections

Available when Role is Component. For example,

Image Added

When a screen opens, specify how data fields will display:

Insert data fields are cleared and variables are passed to the screen from the actionflow, the screen is then ready for the application user to add new data. Typically used for adding new data.
Update Variables created in the actionflow are set on the screen, any filtering is applied, data is retrieved from the server and displayed in the fields. Note the values set by the actionflow are persisted. Typically used for updating existing data.
Change Fields Variables passed to the screen are set. Typically used to set a value on one screen from another.

Attributes

A list of attributes available on the input connection point. These directly link to the fields available on the form.

Primary connection points display the screen properties as attributes.
Component connection points display attributes available on the associated form.

HTML Comment

Not yet implemented - and may need to be on the input connection page.
Each open screen node has 1 primary input connection point by default called 'screen'. Available when Input connection point Role is Primary, optionally set:

Field	Type	Default Values if not set	Description
Height	Number		Sets the height of the screen
Width	Number		Sets the width of the screen
Top	Number		Sets the top position of the screen relative to the window
Left	Number		Sets the left position of the screen relative to the window
Maximised	Boolean	whatever is set on the screen properties	True will open the dashboard in its maximised state. False will open the dashboard in its minimised state and will use the above properties.

When you connect an open screen node to a screen, PhixFlow automatically adds an input connection point for each form on the screen. The input connection point is automatically set to:

Role Component.
Attributes: all data fields and dynamic text fields are added.
This means you can map to the attributes and pass data to them.

Data Attributes

This section has a toolbar with standard buttons. The grid contains a list of

output connection points and their expressions. To add a new output path, in the section toolbar

the attributes that will pass through the wire into this node. All nodes can have a driving input connection, which passes data records one-by-one into the node.

To refer to these attributes in an expression, specify the names of the connection point and attribute with the syntax:

Code Block
connectionpointname.attributename

Double-click on an attribute in the list to display tje properties related to this node and connection. This can include Name, Type, Component, Primary Key etc.

To create a new attribute: click
Insert excerpt
_add
_add
nopanel true

to open a new output path and set the expression edit output path, double-click it in the list to open its properties output path and in the section toolbar click

Image Removed Permanently Delete. The expression properties has sections for Parent Details , Audit Summary and the following Basic Settings:

and click
Insert excerpt
_delete
_delete
nopanel true

Insert excerpt

	_structured_data
	_structured_data
nopanel	true

Request Attributes

Available for

Insert excerpt

	_action_view
	_action_view
nopanel	true

,

Insert excerpt

	_action_gateway
	_action_gateway
nopanel	true

and

Insert excerpt

	_action_calculate
	_action_calculate
nopanel	true

nodes, which can have Lookup connection points.

This section has a toolbar with standard buttons. The grid contains a list of the attributes that you want to lookup from another table. Lookup connections pass a complete set of records into the node.

To refer to these attributes in an expression, specify:

Code Block
req.attributename

Double-click on an attribute in the list to display its properties related to this node and connection. This can include Name, Type, Component, Primary Key etc.

To create a new attribute: click
Insert excerpt
_add
_add
nopanel true
and set the Name and Type; see Attribute.
To change its properties, double-click an attribute in the list; see View Attribute
To delete an attribute, right-click and select
Insert excerpt
_delete
_delete
nopanel true
.

Insert excerpt

	_structured_data
	_structured_data
nopanel	true

Output Connection Points
Anchor
output
output

This section is not available for actions that do not require output connections because they represents the end of actionflow processing, e.g. Save, Open Screen, Open URL, and Analysis nodes.

For all other nodes, the output connection point has an expression that specifies the logic to control whether or not records flow to the next action node. The syntax for a driving connection is:

Code Block
connectionpointname.attributename

The syntax for a lookup connection is:

Code Block
req.attributename

If the expression evaluates to true for the record flowing through the node, it will pass through the connection point onto the next node in the sequence.

Insert excerpt
_property_tabs
_property_tabs
name basic-h
nopanel true

Basic Settings

Field	Description
Name	Enter

an expression name.Where the gateway action runs and expression for each output path, enter should especially if the gateway is marked as exclusive which determine if stream-items will pop-up

Image Removed_property_tabs_property_tabsnameaccess-hnopaneltrue Insert excerpt_access_accessnopaneltrue Insert excerpt_audit_auditnopaneltrue Insert excerpt_description_descriptionnopaneltrue Insert excerpt

Note
Gateways can have an unlimited number of output paths. If the Gateway Action Configuration is Exclusive, records only pass through the first output path where the expression condition is met.

Actionflow Connector Properties

Connector properties do not include the name.

Basic Settings

Field	Description
Input	The name of the node at the start of this wire.
Input Connection Point	The name of the connection point.
Output	The name of the node at the end of this wire.
Output Connection Point	The name of the connection point.

To remove a mapping, right-click and select Image Added Delete Mapping

Input Mappings

The left grid contains a list of attributes available from the input.

Output Mappings

The right grid contains a list of attributes available to map to in the output.

Live Search
spaceKey @self
additional none
placeholder Search all help pages
type page

Panel

borderColor	#00374F
titleColor	white
titleBGColor	#00374F
borderStyle	solid
title	Sections on this page

Table of Contents

maxLevel	3
indent	12px
style	none

Learn More

Version	Old Version 3	New Version Current
Changes made by	Fiona Sargeant (Unlicensed)	Zoe Baldwin
Saved on	Jan 12, 2022	Sept 19, 2024

Page Comparison

Versions Compared

Key

Overview

Live SearchspaceKey@selfadditionalnoneplaceholderSearch all help pagestypepage

Driving and Lookup Connection Points

Connection Points Anchorinputinput

Insert excerpt_property_tabs_property_tabsnamebasic-hnopaneltrue

Basic Settings

Data Attributes and Request Attributes

Validation

Input Parameters

Basic Settings

Output Connection Points

Input Connection Points

Input Connections

Open Screen Action Input Connections

Data Attributes

Request Attributes

Output Connection Points Anchoroutputoutput

Insert excerpt_property_tabs_property_tabsnamebasic-hnopaneltrue

Basic Settings

Actionflow Connector Properties

Basic Settings

Input Mappings

Output Mappings

Live SearchspaceKey@selfadditionalnoneplaceholderSearch all help pagestypepage

Live Search
spaceKey @self
additional none
placeholder Search all help pages
type page

Connection Points
Anchor
input
input

Insert excerpt
_property_tabs
_property_tabs
name basic-h
nopanel true

Output Connection Points
Anchor
output
output

Insert excerpt
_property_tabs
_property_tabs
name basic-h
nopanel true

Live Search
spaceKey @self
additional none
placeholder Search all help pages
type page