| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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. updating datadecision 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 drag be dragged from the Repository onto the canvas.Insert excerpt _action_screen _action_screen nopanel true
Most nodes run once per record they receive from the input connection point. However, some nodes are only only trigger trigged once 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 nopanel true
and Insert excerpt _action_phase _action_phase name start nopanel true
nodes.Insert excerpt _action_url _action_url nopanel true
| Excerpt | ||
|---|---|---|
| ||
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 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 there can be exceptions, such as the Converge action.
|
Note: The specifics of mappings and connectors are covered in a later in this course. NOT SURE THIS NEEDS TO BE A NOTE
