Versions Compared

Key

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

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue


Excerpt
nameIntro

Action Nodes

Action nodes are the building blocks of Actionflows and are represented as a circle with an icon. They perform specific tasks, e.g. decision gateways, performing calculations, and API integrations, and are 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 be dragged from the Repository onto the canvas.

Most action nodes run once per record they receive from the input connection point. However, some action nodes are only only trigged once run after receiving the final record or once per flow, e.g. REPETION HERE ON RUNNING ONCE< PLUS WE SWITCH TERMINOLOGY FROM RUN TO TRIGGERED 

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


Excerpt
namemapping

Attributes are mapped into action nodes as Input Parameters ONLY IF WE ARE GOING TO PROCESS THEM IN THAT NODE and out of action nodes 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 then pass through the data and attributes DATA AND ATTRIBUTES?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. CAN WE TIDY THIS PARAGRAPH UP, I THINK IT CAN BE MORE CONCISE AND CLEARER*although pass through every attribute*, including any not mapped**

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

**there can be exceptions, such as the 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.


Note: The For the specifics of mappings and connectors are covered in a later in this course. NOT SURE THIS NEEDS TO BE A NOTE, see 1.08 Mappings and Connectors.

Image Modified