Currently, I think, we only need the workspace_id (and the workflow_id provided in the path) to run a workflow. I think this is always required for other implementers as well. Please correct me if I am wrong. But I think that it is likely, that we or other implementers may encounter another parameter needed, like the starting file-grp for example. Because of that, I decided to add the parameters section like in processorArgs. I think this gives more flexibility to the implementers. Because I am not too sure about that please don't hesitate to comment if you have another opinion on that.
Currently, I think, we only need the workspace_id (and the workflow_id provided in the path) to run a workflow. I think this is always required for other implementers as well. Please correct me if I am wrong. But I think that it is likely, that we or other implementers may encounter another parameter needed, like the starting file-grp for example. Because of that, I decided to add the
parameters
section like in processorArgs. I think this gives more flexibility to the implementers. Because I am not too sure about that please don't hesitate to comment if you have another opinion on that.