| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Excerpt | ||
|---|---|---|
| ||
Action NodesAction 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.
|
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
to list existing screens, which can then be dragged from the Repository onto the canvas.Insert excerpt _action_screen _action_screen nopanel true
Most action nodes run once per record they receive from the input connection point. However, some action nodes only run once after receiving the final record or once per flow, e.g. REPETION HERE ON RUNNING ONCE<
, Insert excerpt _action_screen _action_screen nopanel true
and Insert excerpt _action_phase _action_phase name start nopanel true
nodes.Insert excerpt _action_url _action_url nopanel true
| Excerpt | ||
|---|---|---|
| ||
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.
|
For the specifics of mappings and connectors, see 1.08 Mappings and Connectors.
