Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The Principles of Actionflows

  1. All Actionflows require an input, this can be data or an interaction in the form of a user interaction, scheduled task or API call.
  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 (Primary Key)
  5. Actionflows can be reused by connecting in different data to the input connection point(s). Each combination of data is referred to as an instance, this includes Actionflows embedded within another Actionflow.


  • No labels