Anyone have idea how to pass InputArguments in StartJobs API

I am using below request. it works fine if I dont pass inputArguments but it doesn’t work if I pass inputArguments parameter.

{
“startInfo”: {
“ReleaseKey”: “658fd343-0338-430c-91a7-37c85hg0ddb7”,
“RobotIds”: [
3434
],
“NoOfRobots”: 0,
“Strategy”: “Specific”,
“Source”: “Manual”,
“InputArguments”: “Argu1:Test”
}
}

Response

{
“message”: “startJobParameters is null!”,
“errorCode”: 0,
“resourceIds”: null
}

Hi Hiren,
Yes. First off, make sure you have declared an IN argument on your workflow. If not, update it and republish to orchestrator.
Then, as for the format of the InputArguments value, try making it a json string (by escaping the quotes on the key name and value) with the key being the name of the input argument in your workflow, as below.
Let me know if this works for you.

image

Hi Zell,

Thanks for your reply… but still I am getting same error “startJobParameters is null!”. I am using below request now.

Just FYI : We are using orchestrator 2018.2 version

{
“startInfo”: {
“ReleaseKey”: “658fd343-0338-430c-91a7-37c85hg0ddb7”,
“RobotIds”: [
2343
],
“NoOfRobots”: 0,
“Strategy”: “Specific”,
“Source”: “Manual”,
“InputArguments”: “{\“Argu1\”:\“test\”}”
}
}

Hi Hiren,
Can you try removing the ‘source’ key?
Also what is it that you’re using to test this so that I can try to recreate your issue.
And have you tried simulating it in postman or swagger api first?

Hi Zell,

Thanks for your reply. I think I have figure out the issue. It was issue with Orchestrator 2018.2 version. I have upgraded with 2018.3 version and its works fine.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.