Skip to main content Skip to footer

Flow Parameters

Parameters address the following two use cases:

  1. You want to use the same Flow on multiple Nodes, but some settings are different

  2. You use the same setting in multiple Flows, e.g. credentials for access to some external service, and this setting sometimes changes. An example is a username/password credential where you have to update the password every 6 months. Instead of changing every Flow that use that credential you can use a parameter and update all Flows by just changing the parameter.

You first need to create a parameter, this is done on the Parameters page by clicking on + Add Parameter. You then give the parameter a name and specify what data type the parameter has. The data type will control which module settings that can be overridden by this parameter. You also need to assign a default value, which will be used in case no value override is provided per Node. For the second use case described above, you only use the default value.

Once a parameter has been defined it can be used to override module settings. You can do this on the Flows page, or from within the Flow Studio when you have the Flow open. On the Flows page you select the Flow where you want to override some settings, then click on the number in the Modules column. The Parameters panel will open and show all modules used in this Flow. In the Flow Studio you can open the Parameters panel by selecting Managing Parameters from the menu on the Flow tab. Go to a module where you want to override a setting and expand the table using the arrow (>) to the left of the module name. Below the module name you will now see a list of settings that can be overridden, and their current values based on the module configuration. To override a setting you click on the pen to the right of the setting and then select one of the available parameters from the list. When you have assigned the parameters you want to use on the settings for this module you must save them. 

If the parameter you selected has a default value this value will now be assigned to this setting whenever you deploy this Flow. If you want to reuse the same setting in multiple flows, i.e. the second use case above, this is all you need to do. Just add the same parameter to some other settings in other Flows.

If you want to assign different values depending on which Node the flow is deployed to, i.e. the first use case above, we have to switch to the Nodes page. Click in the Parameters column on the Node for which you want to assign new parameter values. In the panel on the right-hand side you add a parameter to this Node by clicking on + Add Parameters. A popup will show all parameters that are currently defined in the system, together with their data type and possible default value. Go to the parameter you want to use and click on the pen symbol to edit the value for the parameter. You can add multiple parameters at once by editing multiple parameters. When you close the pop-up these parameters will be added to the Node, with their unique values for this node. Repeat this process for any Nodes where you want to modify some settings.

When parameter values have been added on Nodes, these values will replace the corresponding module settings when Flows are deployed to the Nodes, if the Flows use any of these parameters. The mapping between module settings and Node specific values is done through the parameter name.

Debugging with parameters

When you run a Flow in a remote session in the Flow Studio the settings that are set in the module will be used by default, i.e. the settings you see in the UI. If you want to test your Flow with the settings that will be used when deploying the Flow to a specific Node there is an option on the Node tab when you are connected to a Node: Use Flow Parameters. When checked the Node specific values will be applied based on which Node the Flow Studio is currently connected to. If no node-specific value is assigned the default value will be used.


Crosser Control Cloud | Functions | Debug with Parameters
Crosser Control Cloud | Functions | Debug with Parameters