Publish to different tenants - Deploying from Studio to Orchestrator

Help Studio
, ,
1

Hi Team,

Is it possible to publish to other tenants like UAT from the studio instead of downloading custom packages? Could you please provide the steps need to be performed in Orchestrator as well in the studio

2

Hi @Deeipauk

You can connect your Assistant to the UAT tenant, allowing you to publish workflows directly to Orchestrator.

Once your Assistant is connected to the required tenant, Studio will also connect to the same tenant, enabling you to publish code to the UAT tenant seamlessly.

Hope it helps!!

1 Like
3

First, check if all tenants are visible in your profile within UiPath Assistant. Then, select the desired tenant and restart Studio to publish the code to the required tenant.

Check below image to get to know where to change tenant in Assistant,

The image shows the UIPath Assistant interface, highlighting a user menu with options for tenant selection, preferences, help, sign out, and quit. (Captioned by AI)
The image shows the UIPath Assistant interface, highlighting a user menu with options for tenant selection, preferences, help, sign out, and quit. (Captioned by AI)833Ă—812 78.3 KB

If you are unable to connect to different tenant in assistant then Follow the below steps,

  1. Open UiPath Assistant, Go to Profile and Sign out.
  2. Sign in again to your same UiPath account where UAT tenant exist.
  3. After sign in, it will ask to select Tenant in UiPath assistant as below image,
    The image shows a welcome screen for UiPath Assistant prompting the user to pick a tenant between "DefaultTenant" and "Development" before clicking "Continue." (Captioned by AI)
    The image shows a welcome screen for UiPath Assistant prompting the user to pick a tenant between "DefaultTenant" and "Development" before clicking "Continue." (Captioned by AI)980Ă—971 21.9 KB
  4. Click on continue to sign in with required tenant.
  5. Restart your studio and you are able to publish your code directly to the UAT Tenant.

Hope it helps!!

4

@Deeipauk,

If your UAT tenant have the Developer license available, you can do it the way explained by @mkankatala.

If not, you can’t publish directly to other tenant than the Studio connected to.

You can publish it on local drive and then manually deploy it to the desired tenant.

1 Like
5

@ashokkarale @mkankatala - Thanks for your request response

This we want to perform as part of training to users so as mentioned by @mkankatala we don’t want to change Assistant then always publish will happen to UAT, I am exploring is there any way I can add “Custom URL” and “API Key” to point publishing to UAT tenant directly? while orch tenant feed publish option to Dev Orch as usual remains

is there any way I could get UAT tenant Custom URL and API from the Dev Orch details

Dev URL - UiPath

6

Have a look here as well:

And

1 Like
7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.