I have a requirement to run a review on a bi-weekly frequency. Since out-of-the-box Aveksa scheduler doesn't allow me to generate a review on a desired frequency, I decided to use runReview web service command in a custom task to meet my requirement.
runReview command returns 1 output variable called run-id that I need to store in a custom workflow variable.
I followed the workflow guide and created a response variable called $(jobUserData_runidReturned} to store run-id value returned from the web service command.
Unfortunately, I am getting an error (see below) while parsing the response. I am not able to identify the root cause of this error given same setup works fine when I use a different web service (for example loginUser) .
Has anyone into similar issue when handling web service responses?