I have a task within a baseline that has fields for parameters within the description of the baseline. These fields let the user input the parameter for “Repo”. However, if I want to run the task outside of the baseline, I’d like to use the action parameter query command so the user can input the parameter for Repo. However, it seems action parameter query runs regardless and ignores the if block. Is there anyway to achieve similar functionality to what I want outside of making the task parameterized like the baseline?
if {not exists parameter "Repo"}
action parameter query "Repo" with description "Please enter the network location of the driver repository:"
endif
It’s best to use unique parameter names to avoid conflicts.
action parameter query will always trigger a prompt, even if wrapped in an if condition.
action parameter query is processed by the Console at Take Action time, whereas parameterized parameters are evaluated on the client during execution.
Note: To avoid failures at client level due to an unresolved parameterized value, you should include a fallback such as: if {not exists parameter “Repo”} Perform action using “Action Parameter Query” endif
I haven’t fully tested this specific example, but you can give it a try.
Alternatively, it’s often safer to keep two Fixlets, a parameterized one for standalone execution and another that uses action parameter query only for baseline execution.