Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

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

Live Search
spaceKey@self
additionalnone
placeholderSearch all help pages
typepage

PanelborderColor#00374FtitleColorwhitetitleBGColor#00374FborderStylesolidtitle

Sections on this page

Table of Contents
maxLevel3
indent12px
stylenone

For output connection points, specify an expression to determine ???  passed onto the next node.

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.

  • For input connection points, map which attributes to pass into the node.
    • Output connection points: 
      • Calculate
      • Gate
      • View

    Nodes without an output connection represent:

    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. 

    Input

    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_

    toolbar

    settings
    _property_

    toolbar

    View node is auto set to primary,

    does something get set to component based on the instance input?

    • Primary 
    • Component
    TypeAvailable when

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

    Image Added

    Insert excerpt
    _property_tabs
    _property_tabs
    namebasic-h
    nopaneltrue

    Insert excerpt
    _parent
    _parent
    nopaneltrue

    Basic Settings

    FieldDescriptionConnection Point Found On
    Name
    Enter the name for the connection pint.Role
    The name of the Actionflow.

    Insert excerpt
    _input
    _input
    namecaps
    nopaneltrue

    Insert excerpt
    _lookup
    _lookup
    nopaneltrue

    Insert excerpt
    _output
    _output
    namecaps
    nopaneltrue

    Action Phase

    The 

    Insert excerpt
    _action_phase
    _action_phase
    nopaneltrue
     that the connection point is in. See Actionflow Phases.

    Insert excerpt
    _input
    _input
    namecaps
    nopaneltrue

    Insert excerpt
    _lookup
    _lookup
    nopaneltrue

    Insert excerpt
    _output
    _output
    namecaps
    nopaneltrue

    Validation

    FieldDescriptionConnection Point Found On
    Minimum RecordsThe 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
    namecaps
    nopaneltrue

    Insert excerpt
    _lookup
    _lookup
    nopaneltrue

    Maximum RecordsThe maximum number of records that the Actionflow is permitted to runIf the received records exceed the maximum set, the Actionflow will not run.

    Insert excerpt
    _input
    _input
    namecaps
    nopaneltrue

    Insert excerpt
    _lookup
    _lookup
    nopaneltrue

    Input Parameters

    FieldDescriptionConnection Point Found On
    Name

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

    Insert excerpt
    _input
    _input
    namecaps
    nopaneltrue

    Insert excerpt
    _lookup
    _lookup
    nopaneltrue

    Insert excerpt
    _output
    _output
    namecaps
    nopaneltrue

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

    Insert excerpt
    _input
    _input
    namecaps
    nopaneltrue

    Insert excerpt
    _lookup
    _lookup
    nopaneltrue

    Insert excerpt
    _output
    _output
    namecaps
    nopaneltrue

    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
    _input
    _input
    namecaps
    nopaneltrue

    Insert excerpt
    _lookup
    _lookup
    nopaneltrue

    Insert excerpt
    _output
    _output
    namecaps
    nopaneltrue


    Tip

    If the

    Insert excerpt
    _run_action
    _run_action
    nopaneltrue
    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
    titleSee 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
    nopaneltrue
    action 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:

    • Insert excerpt
      _driving_input_connection_point
      _driving_input_connection_point
      nopaneltrue
      : there can be only one of these.
    • Insert excerpt
      _request_input_connection_point
      _request_input_connection_point
      nopaneltrue
      : there can be multiple of these
    Open Mode

    Not seeing this for the INPUTS input connection

    Available


    Excerpt
    namescreenInputConnections

    Available when Role is Component.

    text

    • Insert
    • Update
    • Change Fields
    Action Phasedefault

    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

    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:

    FieldTypeDefault Values if not setDescription
    HeightNumber
    Sets the height of the screen
    WidthNumber
    Sets the width of the screen
    TopNumber
    Sets the top position of the screen relative to the window
    LeftNumber
    Sets the left position of the screen relative to the window
    MaximisedBooleanwhatever 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 buttonsThe grid contains a list of 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

    Lookup Attributes are available when Type is Lookup. 

    Double-click on an attribute in the list to display

    the

    tje properties related to this node and connection. This can include Name, Type, Component, Primary Key etc.

    • To
    add
    • create a new attribute
    , click
    • : click 
      Insert excerpt
      _add
      _add
      nopaneltrue
       and
    specify the
    • set the Name and Type;
    see Attribute.
    •  see Attribute.
    • To add an existing attribute to this list, open the list of attributes and drag one onto the grid.
    • To open its properties, double-click one of the listed attributes.
    • To remove an attribute, select one and click 
      Insert excerpt
      _delete
      _delete
      nopaneltrue

    Insert excerpt
    _structured_data
    _structured_data
    nopaneltrue

    Request Attributes

    Available for

    Insert excerpt
    _action_view
    _action_view
    nopaneltrue
    ,
    Insert excerpt
    _action_gateway
    _action_gateway
    nopaneltrue
    and
    Insert excerpt
    _action_calculate
    _action_calculate
    nopaneltrue
     nodes, which can have Lookup connection points.

    This section has a toolbar with standard buttonsThe 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:

    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
      nopaneltrue
       and
    set
    • set the Name and Type; see Attribute.
    • To change its properties
    . Todo-Fiona - why would this be useful
  • drag add an existing attribute to this list Todo-Fiona - is this possible??
  • double-click one of the listed connections to open its properties.
  • remove attributes, select one and click Image Removed Permanently Delete. Todo-Fiona - check icon and label. What does this do? prevent them being passed through?
    • , double-click an attribute in the list; see View Attribute
    • To delete an attribute, right-click and select 
      Insert excerpt
      _delete
      _delete
      nopaneltrue
      .

    Insert excerpt
    _structured_

    audit

    data
    _

    audit

    structured_data
    nopaneltrue

    Output Connection Points 
    Anchor
    output
    output

    This section is not available for actions that do not require output

    Each

    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

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

    . The syntax for a driving connection is:

    Code Block
    connectionpointname.attributename

    The syntax for a lookup connection is:

    Code Block
    connectionpointname
    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_toolbar_property_toolbarnopanel

    true

    Insert excerpt
    _property_tabs
    _property_tabs
    namebasic-h

    nopaneltrueexcerpt-include_parent

    _parent

    nopaneltrue

    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.

    Tip

    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

    popup window, click 

    Insert excerpt
    _editor_expand
    _editor_expand
    nopaneltrue
    .

    See also:


    Note

    Gateways can have an unlimited number of output paths. If the Gateway

    Node is Exclusive 

    Action Configuration is Exclusive, records only pass through the first output path where the expression condition is met.

    Insert excerpt_audit_auditnopanel

    true

    Actionflow

    Wire

    Connector Properties

    Wire

    Connector properties do not include the name.

    Todo-Fiona

     

    - check - I thought I saw where you could change its name

    Basic Settings

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

    The name of the connection point.

    OutputThe
    action Insert excerpt_terms_changing_terms_changingnopaneltrue
    name of the node at the end of this wire.

    Data Mappings

    Standard text

    Lookup Mappings

    todo

    Insert excerpt_audit_auditnopaneltrue

    Learn More

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

    Output Connection PointThe 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
    additionalnone
    placeholderSearch all help pages
    typepage

    Panel
    borderColor#00374F
    titleColorwhite
    titleBGColor#00374F
    borderStylesolid
    titleSections on this page

    Table of Contents
    maxLevel3
    indent12px
    stylenone


    Learn More