Thank you very much. That will work. But can you perhaps explain how the Constant Value Column works. I don’t quite understand how to use it. I have tried a few things but they didn’t work.
Currently my workflow looks like this:
Table Creator -> String Manipulation -> GET Request -> Column Filter -> JSON to Table -> String Manipulation -> Generic Loop Start -> GET Request -> JSON to Table -> Constant Value Column -> Variable Condition Loop End
It does the following:
Set variables -> Create URL -> Call URL -> Get Column containing JSON -> Extract JobID from JSON -> Create get-status URL -> Start loop -> Call get-status URL -> Extract status from JSON (it can be “in progress”, “error” or “completed” -> if status=in progress then loop else stop
I hope my notation makes sense. My problem, off course, is how to use the Constant Value Column to extract the status value and then make the Variable Condition Loop End to respond appropriately. My thinking was to set a boolean variable “end” to false and then change it to true if the status changes to “error” or “completed” but I couldn’t get it to work.
You can do this in many ways, probably the easiest is to just use a Table Row to Variable node to get a flow variable with the status, then connect that flow variable with the Variable Condition Loop End node and configure that node to stop once the value is “completed.” To handle the error case you might need to manipulate the variable further, one way would be with the Rule Engine Variable node, where you can turn both “error” and “completed” into a stop-loop value.
I’m now really close but … the Variable Condition Loop End doesn’t work. Everything seems to run fine up to that point. I’m uploading a zip of my workflow directory. You won’t be able to run it because the REST service I use is on my localhost but if you wouldn’t mind looking at the workflow, you could perhaps tell me what I’m doing wrong.