Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

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 input action (
  • such as data, user interaction
or scheduled task/task plan)
  • , 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 node
  • Action nodes return data to the Actionflow as Output Attributes
  • 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)
  • 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 
    • 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