The Principles of Actionflows

1. All Actionflows require an input, this can be data or an input action (user interaction or scheduled task/task plan)
2. To use data within an action node it must be mapped into an input parameter for that node
3. Action nodes return data to the Actionflow as Output Attributes
4. Actionflows 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 (UID)
5. Actionflows can be reused by connecting in different data to the input connection point. Each combination of data is referred to as instances, this includes Actionflows embedded within an Actionflow 

1.3 Getting to Know Actionflows