What is the best way to add queue items in a folder where the robot is not assigned?
As you’ve seen in the subject we have the following setup:
Each department has its own folder
Each robot has its own rights(applications with AD integration) for its corresponding department
We cannot just add a robot to another department.Why?Because...
Since each robot is setup to only run on a specific department due to the AD integration, if we were to add the robot to another department, correct me if I’m wrong, the trigger would try to start a job with this robot even if the robot doesn’t have any rights. Also, we don’t want to maintain a list of robots in the triggers.
@Nithinkrishna This sounds great. We’ve used the API extensively and was wondering if we’ve missed any other method like @AndyMenon mentioned but for our orchestrator version.
@AndyMenon Thanks again for the info and as soon as we migrate to a better version of Orchestrator we will be using this. But, for our particular case I’ll mark @Nithinkrishna reply as the solution.
Most important is that you found a solution to your problem regardless of which one it is. But thanks for your kind gesture.
Definitely. APIs are another way to to go.
That said, I personally reserve API solutions as the last option as it is technically more involved as compared to sharing queues. In your case however, APIs is the way to go as that seems to be the only available option.