1
0
-1
2 answers
- 10-1
Hi, I believe the query parameters including processInstanceId are optional parameters. Did you try to make the API call without any additional parameters?
Add your comment... - 10-1
Yes, it turns out the parameters are optional and it works flawlessly., thanks
Add your comment...
so i used the API Builder to Upload a File and Form Data successfully, I got back a recordId (guid) value, i want to start a process on that recordId ( i know the process information that i want to start, be it ProcessDefinitionID or Name ), the API Builder has a method startProcessByUser and even startProcess, in both cases it wants a "ProcessInstanceId" that ">> has been created but not started << "" that a kicker, how do i do this now. create but not start this needed instance id.
I want to use a REQUEST.POST programmatic call the url to start the process, but with no success here is what i tried
i tried to call the URL named "Link to Run Process" with an additional &recordId=<uuid-here>, it complains about 403 error
I looked at the beanshell as "Process Tool" idea, but even if i move the call to a new Stub process that collects the RecordId and calls the Main-Target-Process via beanshell, i am still back to square 1, how to i call the Stub Process.
I am considering the Schedule Menu model, but now i got to go look for records without a process instance and try to start a process on that record id
what is it so hard to say POST with a call to say Start Process on a recordId with a user name, Why is there a need to a created but not running instance ?? this is a major hurdle IMHO
Please help ..