Hi @Rohit_Nair,
We also have dev, uat and prod different tenants/sites in our organization.
Below is how we do it:
- after development and unit testing is done in dev environment, uat/prod environment needs to set up for process implementation.
- all the resources like folders, queues, assets, storage buckets need to be created in production and you should be creating them the same way those were created in dev environment- same naming conventions, structures etc.
- also, you would need to ensure your unattended robot and machine where that process is going to run is set up. In dev environment, testing is done directly via UiPath studio(in our case, can be different for others), so in uat/prod environment, you need to have robot account to run that process in an unattended manner.
- once machine and robot is setup, these also need to assigned to the prod folder from where process needs to run.
Please note: for assets or credential assets that you are using in dev environment, it’s good practice to leave the orchestrator folder empty or proper orchestrator folder name should be provided. In case when this field is empty, it will automatically pick assets from the folder where the process is running. In case its value is provided, it will look for assets from that folder and if it is not the same where process is running or assets from that folder doesn’t have access to the current folder, process would fail.
Hope this helps.
Regards
Sonali