Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 26 Next »

This page is for application designers who need to configure functionality for components or events. It explains the properties for the input and output connection points. Connection points wire together inputs,  nodes and outputs in an actionflow.

Overview

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

  • 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, Open Screen and Open URL nodes
  • or processing out of the actionflow: Analysis node.

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.

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.


Input Connection Points 

Property Pane Toolbar

For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.

 Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Basic Settings

FieldDescription
NameThe name for the connection point. This defaults to in.
Type

Specify the type of connection:

  •  Driving input connection point: wire nodes via one driving input connection point
  •  Lookup input connection point: the following nodes can have a one or more lookup connection points. The following nodes can have lookup connection points: Calculate, Gate and View.
The following properties are available for open-screen nodes only.
FieldDescription
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:

  •  Driving input connection point: there can be only one of these.
  •  Lookup input connection point: there can be multiple of these
Open Mode

Available when Role is Component.

When the screen opens, specify what data fields will display.

  • Insert: data fields are empty, ready for the application user to add new data.
  • Update: data fields display latest changes.
  • Change Fields: data fields display data.
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.

Data Attributes

A list of attributes in other action nodes that you can map into this node.

You can refer to these attributes in an expression using the syntax:

connectionpointname.attributename

Lookup Attributes are available when Type is Lookup. 

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

To add a new attribute, click  Add New and specify the Name and Type; see Attribute.


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:

  • create a new attribute: click  Add New and set its properties.
  • drag add an existing attribute to this list.
  • double-click one of the listed connections to open its properties.
  • remove attributes, select one and click  Permanently Delete. 

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Output Connection Points 

The following nodes have intput connection points: 

  • Calculate
  • Gate
  • View

Nodes without an output connection represent:

  • either the end of actionflow processing: Save, Open Screen and Open URL nodes
  • or processing out of the actionflow: Analysis node.

Each output connection point has an expression that specifies the logic to control whether or not records flow to the next action node. 

For driving output connections, you can refer to an attribute in the expression using the syntax:

connectionpointname.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. 

Property Pane Toolbar

For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.

 Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Basic Settings

Field

Description
NameEnter a name for the output connection point
Order

Enter a number to indicate the order in which this expression will be run.
Remember that an expression that generates a value must run before an expression that uses the value.

The order is very important for exclusive gateway nodes, as the records pass through the first output connection that meets the expression condition.

Expression

Enter an expression that evaluates to true or false to specify whether or not records pass through this connection point. To work in a larger pop-up window, click  Show field in a large editor.

See also:


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

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Actionflow Wire Properties

Wire properties do not include the name. 

Basic Settings

FieldDescription
InputThe name of the node at the start of this wire.
Input Connection Point

The name of the connection point.

OutputThe name of the node at the end of this wire.
Output Connection PointThe name of the connection point.
Expression

Data Mappings

This section has a toolbar with standard buttons.

The grid contains a list of data  

To remove a mapping, use the toolbar button  Delete.


Request Mappings

todo

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Learn More

For links to all pages in this topic, see Understanding Actionflows. 



Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver

Sections on this page

Learn More

For links to all pages in this topic, see Understanding Actionflows. 


Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver

  • No labels