Versions Compared

Key

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

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue


Action Nodes

  • Every attribute is passed through* but in order to use an attribute in a specific action node it must be mapped in to it as an input parameter.
    • *although there can be exceptions such as the converge action,
  • Once a mapping is configured you it will reused in all instances of the actionflow. This is because the action nodes sit within the actionflow itself and only the data coming into and out of an actionflow changes (for each instance) 
    Excerpt
    nameIntro

    Action Nodes

    Action nodes are the building blocks of Actionflows

    , they

    and are represented as a circle with an icon. They perform specific tasks, e.g. 

    updating data

    decision gateways, performing calculations, and API integrations, and are

    wired

    joined together using connectors.

    Image Modified

    Action nodes can be dragged from the toolbar onto the canvas to create a new action, and some can be clicked to see existing objects, e.g. click

    Insert excerpt
    _action_screen
    _action_screen
    nopaneltrue
     to list existing screens, which can then drag be dragged from the Repository onto the canvas.

    Most action nodes run once per record they receive on their driving from the input connection point. However, some action nodes only trigger once run after receiving the final record or once per flow, e.g.  

    Insert excerpt
    _action_screen
    _action_screen
    nopaneltrue
    ,
    Insert excerpt
    _action_phase
    _action_phase
    namestart
    nopaneltrue
     and
    Insert excerpt
    _action_url
    _action_url
    nopaneltrue
     nodes.

    Usually, action nodes have Image Removed Driving connections, which pass data through to the next action node. Some action nodes have a  Image Removed Lookup connection, which send out a request for data, that is then returned to the action node data. 

    Nodes must be connected sequentially starting from the Image Removed Driving interface connection point. Records will then pass through each node and be manipulated accordingly.

    For most action nodes, data flow is configured when attributes are mapped to the input connection points. For Insert excerpt_action_gateway_action_gatewaynopaneltrue nodes, the data flow can be controlled by mapping to the output connection 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


    Excerpt
    namemapping

    Where attributes require processing by an action node, e.g. in an expression, the attributes must be mapped in as Input Parameters. These attributes are then mapped out of the action node as Output Attributes.

    Connectors between the action nodes pass through every attribute*, including any not mapped**

    *attributes not mapped are referred to as pass-through attributes.

    **there can be exceptions, e.g. Converge action.

    Tip

    Once mappings are configured they will reused in all instances of the Actionflow. This is because the action nodes sit within the Actionflow itself and only the data coming into and out of an Actionflow changes for each instance.


    For the specifics of mappings and connectors, see Mappings and Connectors.

    Image Modified