Versions Compared


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


Flux's variable managers are the storage depots for all of the data used in your workflows. Flux provides four such managers that you can use in your runtime data maps to send and receive data (for a more detailed discussion of the variable managers, see Variables and Variable Managers):

Action Property Variable Managers - Each trigger and action within your workflow has its own action property variable manager, which stores all of the property settings for the action. These are the same settings that you'll supply while building your workflow and configuring your triggers and actions – for example, the "Collection" of a For Each Collection Action, or the "Simple File Source" of a File Copy Action.


Runtime Configuration - This variable manager comes from the Runtime Configuration and Runtime Variables for your engine. Every workflow running in the same namespace will share the same runtime configuration variable manager, and workflows will also inherit runtime variables from their parents in the runtime configuration tree. 

Runtime variables within a runtime data map are specified either by the name of the variable you want to use (like myvariable), which will allow Flux to dynamically search back in the tree for the closest node containing that variable name; however, you can also retrieve a variable from a different namespace by specify the fully-qualified variable name (like /mynamespace/myvariable)the the fully-qualified variable name (like /mynamespace/myvariable). Within a runtime data map the namespace hierarchy IS NOT SEARCHED, which is different than variable substitution. For security reasons, the user running the workflow must have access to the variable manager for the namespace defined in /mynamespace/myvariable.

Runtime variables are very rarely used in runtime data mapping as Variable Substitution can typically handle all runtime variable usage requirements. Variable substitution provides some visibility improvement over runtime data mapping, so we strongly suggest using variable substitution when possible.