Human in the Loop - Keeping Tasks separate from other teams


My bot creates tasks that need to be allocated to a team of people. At the moment I create the tasks as Unassigned because I don’t know which team member will work on it. I can’t figure out how to keep Team A from seeing Team B’s tasks in Classic Folders.

Do I need to duplicate the dispatcher and robot (license i.e. cost) so that they run in different Folders?

The documentation available says that when you create a task the activity can create it in a different folder which only works with Attended robots but my task assignment robot needs to be Unattended in order to run the process on a Queue trigger.

Any guidance would be greatly appreciated

Using Orchestrator 2020.4.0

Hi @shaun.robertson
If you haven’t already, please take a look at the Studio snippet available here:

This example should give you some idea about what you could change in your code to make it works in your case.
As far as isolating it from users is concerned, using a modern folder does make it immensely easy to manage that. If you must use Classic folders, there may be a way to create user groups or use groups from Active Directory.
But this is just a speculation, I haven’t tried or seen this in action. I hope you find the solution and when you do, please share with us on the thread :slight_smile:


Thanks for the reply. Turns out this cannot be done in Classic Folders without duplicating the code, license usage, and infrastructure in different tenants. We will upgrade to the latest version of Orchestrator so that we can run Action Centre in Modern Folders that will solve for this duplication

1 Like

Good to know that you are taking the steps necessary to achieve this outcome.
Also, thanks for sharing the information back :slight_smile:

Good luck with the upgrade!

1 Like