Technically, I’m getting the Process Name from the project.json file, then storing it in the dictionary with all my settings.
where the json filepath is just “project.json” so it uses the relative path (current directory).
It desieralizes it and pulls in the “name” value from the project.json file.
You can use any method though, like store the process name in a regular variable/argument or however you choose. Pulling it from the project.json however allows it to be automatic, so if you change the name, no code changes are needed.
With respect, I’m not that expert and I think you’re assuming I would know where that json comes or is located jeje. I know we have a config file when using RE Framework and how we can save o put info there so to be read from the Dictionary but not sure where or how to get that Json first. I’ve heard about json in general but in this case I would not know before trying to work with the json file where is it or is located my friend.
•Do you have a sample that I can try on in my Studio and analyse the insights to get a good picture please?
Also, I do remember I was checking the ‘Get jobs’ activity before with some of the posts here at the forum and at the end I kept getting this error from Studio when trying to run that activity:
Get Jobs: Operation returned an invalid status code ‘BadRequest’
I’m not sure, but you should look in the Processes section to get environment that is tied to the process.
If a Robot is not in an environment, like “Dev-Bot”, then check the Environment section and add the robot to the environment. And if it already is selected in that Environment, then the details is just bugged.
Like I said, though, you should get the Environment for the Process in the Processes section.
If you any other questions on how that works, let me know
Hi, bad request error code means your request syntax must be wrong, i see your environment has a blank space in the middle and maybe this is causing you troubles… can you rename it for a test? Are you inputting any filter?
Good point about the limit but not is not interfering on it, is about not been able to connect o is nor reaching Orchestrator.
The ‘filter’ could be syntax but that part is good, which is why I removed it and still not getting to Orchestrator, must be something else definitely for which I’ve been reading about ‘bad request’ here and no specifics.
Make sure you verify Orchestrator that the process has jobs that are successful, that fall in the limit of 100 jobs. I would test using a different state too, so you know it works. Like instead of using ‘Successful’, use ‘Running’ or ‘Stopped’. That way, you can test that it’s working.
If you run a recent successful job, then test it, and it’s not pulling it. It’s possible the successful state is bugged or something. Let know if you find anything out on it, cause we might have same issue.