Trigger Dependency

Dependencies between parameters are triggered when opening the Start Workflow form in Portal using the On Next premises, this means that dependencies will be triggered only when clicking the Next button, in order to navigate to the next parameter group. This option will reduce the waiting time for dependencies triggering and will be applied only for the next group. For the first parameter group/Unassigned group, the dependency is triggered automatically when Start Workflow form opens. The dependencies are triggered again for the current parameter group on every value change on the dependency parameters.

Check the Trigger on Empty option if you need the dependency to be triggered even if the dependency parameter will be empty. If you select this option, make sure that the dependency parameters are set as optional, otherwise the workflow will not start in Portal.

Configure Dependency

A parameter value can depend on another parameter value, including parameters of type Password. To configure that, follow the next steps:

Select the parameter that should be dependent on another
Select from the Depends On drop-down list the parameter that will be the dependency

Use the dependency parameter in the parameter fields, where needed
In order to insert the dependency in an expression, first select the field where you want the dependency inserted and click on the Insert Dependency button. The Insert Dependency window will open containing all the parameters selected as dependencies:

From the Insert Dependency window, click on the dependency parameter and then click the Add button to insert it in the field/script. The inserted dependency can be tested by providing a test value to the dependent parameter before you click on Close button.

NOTE: The testing values can be changed after the Insert Dependency window is closed, by editing the dependency parameter test value field and clicking on Close button.

NOTE: The dependencies can be set between members of the same or different Parameter Group.

For example, inside a ComboBox from Powershell we have the echo "%argument2%" inserted dependency. For testing the script before leaving the Edit Parameters window, just click over the Preview Values button. The result should be displayed in the Result area (for the echo given example).
The dependencies and their test values can be saved in profiles and applied later.
After editing the parameters, click the Save & Close button to save the changes, or Cancel to abort the current operation.

A parameter value can also depend on a global variable or a global variable attribute, including fields of type Password from the parameter configuration. To configure that, follow the next steps:

Select the parameter that should be dependent on a global variable or global variable attribute
Select, for example, VM Picker type
On the upper side click on the Insert Global Variable button to open the Insert Global Variables window where the global variable tree can be seen with all the defined global variables and attributes:

In order to insert the dependency in an expression, click on the desired item from the tree (global variable or global variable attribute) and then click Insert and Close. It should look like in the following examples, for global variables and attributes:

In order to visualize the dependency inserted for the Password field, click on the and hold in order to display the value
The inserted dependency can be tested immediately, the global variables and attributes already having values set in Configuration Items → Global Variables.
After editing the parameter, click the Save & Close button to save the changes, or Cancel to abort the current operation

Browser not supported