When using 'multiple parameter set' within an element, does one have control on the order of execution of the sets ?
As an example: for a cisco manager element we want to 'move' a vlan fron Trunk 'A' to trunck 'B' using the remove VLAn en Add Vlan parameters.
However we want to be sure that the 'remove VLAN' parameter is applied before the 'Add VLAN' parameter is set.
Hi,
The multiple sets are indeed send in the order you click them in Cube, and we do preserve that order throughout the flow.
Note that you can double-check the order in the confirmation box:
The order will match with what you see there.
The only exception is parameters that have dependencies, those will be grouped (see https://docs.dataminer.services/user-guide/Basic_Functionality/Parameters/Parameter_dependencies.html )
Hi Hans,
If the order of execution is important you could use an interactive automation script to do the sets. In that script you could then also check if the VLAN was properly removed before adding the new one or show an error message when that would not be the case.
Thanks a lot for the clear feedback.
I am re-assured !