Looks like the parameter for the workflow variable is not escaped and/or quoted correctly and the shell splits it up. If the value contains spaces it must be enclosed in quotes. If you have quotes inside the value you must escape them, usually by using a backslash.
Hi Joana, have you resolved this issue? The command line looks okay for me, but there might be any issue with spaces and quotes? Can you try to execute a workflow without credentials and workflow variables, but with preferences. Cheers, Thomas
Since the comma is a separator for the three parts of the workflow variable argument (name, value, type), you must quote any values that contain commas. I.e. the arguments should look as follows:
The outer quote are to prevent the shell from breaking the argument apart at the spaces and the inner quotes (which must be escaped) are to prevent splitting the variable value at the comma.
Having fought this battle myself, with a complex workflow variable set by the command-line, I will offer this bit of advice for the next person.
Write a very small workflow that simply echos the variable into a file. I chose to write it as a comment into a csv file. That's the only way I was able to debug all the quoting and escaping.
I have many workflows variables defined in my workflow and all of them should be overriden in batch mode. Can some one help me in passing a file to command line execution. so the command line should look like below.