Need of DEV/UAT orchestrator

Is it necessary to have a DEV or UAT environment orchestrator? or can we use the production orchestrator to develop the BOT using the uipath studio?

Or can use the tenants to separate the 2 environments in orchestrator?


Welcome back to uipath forum

It is recommended to have one Orchestrator instance for Dev and Test environments and another Orchestrator instance for pre-production(UAT) and Production .

Else we will be having all the entities likeJob, Asset, folders in one database or in one place which will be difficult to manage

And more than that if you want to develop, test a process before moving to prod it is better to have it in a separate instance as we should not play with prod data.

Even if anything goes wrong while developing or testing it will not impact PROD data if it is done in dev and test instances
And to maintain them it is good to have separate orchestrator instances as well

Hope this would help you

Cheers @varunt1411

Yes, this is Ideal way which is follow almost each organization to have an Dev, Test, Pre-Production & Production Environment.
More over this instances will help you to analyze the application thoroughly. As per my personal experience some of the application work in one instance and same not work in another instance, So to overcome this challange better to work on this all environment.

Hope this would more helpfull…

As others have pointed out it is generally accepted best practice to separate your environments, but how you do that is dependent on your needs, tolerance to risk, budget, policy controls in place from your Privacy & Security teams, etc.

A few ways to separate your environments

  1. Distinct physical / virtual Orchestrator Clusters
  2. Common physical / virtual Orchestrator Clusters with multiple tenants
  3. Multiple Folders
  4. A combination of the above

Currently in our organization, we have two Clusters (One Production & One Non-Production). Each cluster has two orchestrator nodes.

Non-Production for the most part is limited to our Non-Production networks and application/services [Dev, Test, Pre, Staging, etc.) but there are exceptions where we might not have parity or test data in legacy systems.

Production is used for any production automations / interactions.

We don’t currently leverage multiple tenants in a single cluster but we do use Folders (Previously known as Organizational Units);

  • Where our Non-Prod instance has Folders for Development (Build/Developing NonProd Unattended robots dedicated to the developers testing), Preprod Folder (Acts as a staging area for us, QA will perform their regression testing, implimentation plans, etc).
  • Production has a “Default” for Production processes we also have a “UAT” Folder where we can do Dark deployments / Dry Runs / Limited testing against production in a controlled manner, this has been extremely helpful to use with our legacy platforms and allows us to .