Cloud migration question - controlling which robots a process uses

Help Orchestrator
1

We are now fully on cloud for our QA system and working towards migrating to production.

We have a need to be able to assign all robots to all folders via the top level folder, but we don’t want all processes to be able to run as all robots. To illustrate:

  • Top Level Folder
    • Dept Folder
      • Automation folder 1
      • Automation folder 2
    • Dept 2 Folder
      • Automation folder 3
      • Automation folder 4

We want to assign the robots to Top Level Folder, but still be able to control which robots are used by the processes in Automation folder 1, Automation folder 2, etc (within triggers).

How would we achieve this? Machine Templates let us control which servers the jobs run on within the trigger, but it doesn’t appear there is any similar feature for robots.

Yes I know we can specify ONE robot in the trigger, but we need to be able to allow it to select from a grouping of robots the way it can select a machine from the Machine Template.

2

@postwick

May be your way should be to use account machine mapping and select them to each trigger

cheers

3

Does that allow grouping multiple machines and robot accounts together and then the job can select any combo from that grouping?

4

@postwick

there is a mapping strategy you can map multiple

cheers

5

Hi @postwick

This isn’t supported the way Machine Templates are. If robots are assigned at the top-level folder, they’re available to all subfolders, and there’s no “robot group” selection in triggers.

The recommended approach is to control execution using Machine Templates (assign specific robots to specific templates and select the template in the trigger) or redesign folder structure to limit robot access. Robot grouping at trigger level doesn’t exist today.

6

The trigger configuration doesn’t currently have a robot grouping feature equivalent to Machine Templates. The typical approach is to assign robot accounts directly at the subfolder level (Automation folder 1, 2, 3, etc.) rather than at the top level.

One option to consider:

Account-Machine Mappings (available under Tenant > Machines) let you pair specific robot accounts with machine templates. When combined with Machine Template selection in triggers, this provides control over which robot account + machine combinations can execute jobs.

Setup approach:

  • Assign robot accounts at the automation folder level where needed
  • Use Machine Templates for server control (as currently being done)
  • Optionally use Account-Machine Mappings for additional pairing restrictions

Documentation: Orchestrator - Managing Robots

7

I think nobody is understanding what I’m asking for.

We want to be able to group multiple machines and accounts together. For example:

  • Group A
    • Server1
    • Server2
    • Robot1
    • Robot2
  • Group B
    • Server1
    • Server3
    • Robot1
    • Robot3

This way when configuring the trigger we canselect Group A or Group B to tell it which server(s) and robot(s) it can run on.