The Principles of Actionflows
These are the key principles to remember when configuring Actionflows.
- Only map in the minimal amount of data, e.g., primary key, which is then used to access the remaining data
- All Actionflows require an input,
this can be data or an interaction in the form of a - such as data, user interaction, scheduled task or API call
.- Action nodes receive data as Input Parameters and return data to the Actionflow as Output Attributes
- To use data within an action node it must be mapped in
- Data not mapped into an
input parameter for that nodeAction nodes return data to the Actionflow as Output AttributesActionflows only require minimal data to be mapped in for it to run, e.g. just the primary key, because we can look the data up using a unique identifier (Primary Key)Actionflows can be reused by connecting in different data to the input connection point(s). Each combination of data - action node will pass through and is available at later points in the Actionflow
- Reuse Actionflows by connecting in different inputs. Each reuse is referred to as an instance
, this includes Actionflows embedded within another Actionflow.1.03 Getting to Know Actionflows
Image Added