Configuring a connection with your UiPath Orchestrator

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Bots > UiPath bot integration >

Configuring a connection with your UiPath Orchestrator

Configuring a connection with your UiPath Orchestrator

To configure the integration of a bot with a Bizagi process, you first need to have your bot developed and published into the UiPath Orchestrator. Make sure to create the corresponding Environment, Machine, Robot, and Process in order to be able to trigger the execution of the bot from Bizagi.

 

note_pin

Keep in mind:

 

Studio and StudioX robots are not supported to start jobs or create triggers from Orchestrator.  

If you use UI Path Studio in production environments via unattended scheduling configured in Orchestrator, use Unattended robots.

If you cannot change your robot type to Unattended, check the Unattended assigned robots in your license and if possible, assign a new one.

UI Path free account offers 2 Attended robots and 1 Unattended robot. If you need more robots, you will need to upgrade your plan.

 

OrchestrtatorBotConfig

 

Once you have taken care of the UiPath setup for the robot, head to Bizagi Studio and go to the Expert view.

 

UIPath-bot01

 

Click the Bots option and locate the UiPath branch which is under RPA bots.

 

UIPath-bot02

 

Click UiPath and then click on Add Connection. This option appears after clicking UiPath.

 

UIPath-bot03

 

At this point, the UiPath RPA configuration wizard appears. Note that you are able to configure an on-premise connection, where you will be responsible for managing all the infrastructure for your resources to work or a cloud connection, where UiPath manages all the infrastructure for your resources to work.

 

On-Premises Connection

The following list explains all the parameters that need to be configured in order to configure a successful on-premise connection to your orchestrator, which hosts the process you want to trigger from Bizagi.

 

Tenant Name: name of the orchestrator instance you provided at the time of its creation.

Username / Email: associated Username or Email of an admin user of the orchestrator.

Password: corresponding password to the previous field.

Orchestrator URL: URL of the UiPath orchestrator. Usually the value that must be inputted in this field is https://platform.uipath.com/.

 

Once you are finished filling up the form fields, click Test connection and check that the resulting connection status on the text field below, shows a message indicating a successful connection.

 

UIPath-bot29

 

If a message indicating otherwise is shown, review the inputted information and try again. Once your connection is successful, click ok.

 

Cloud Connection

The following list explains all the parameters that need to be configured in order to configure a successful cloud connection to your orchestrator, which hosts the process you want to trigger from Bizagi.

 

User key: allows you to generate unique login keys to be used with APIs or with 3rd party applications in order to log in and perform actions on your behalf.

Account Logical Name: logical name found within the portal's URL. For example, if your URL is https://cloud.uipath.com/yourSite, the account logical name is yourSite.

Tenant Logical Name: logical name of the selected service. Take into account that it may differ from the tenant's name. For example, if the tenant's name default, the tenant's logical name may be defaulthr8139.

Client ID: ID specific to the Orchestrator itself. It is the same for all users and tenants on a specific platform.

 

You may get the values for these parameters in the UiPath Automation Cloud portal. To do so, go to the admin option and under your tenant's name, click API Access

 

UIPath-bot43

 

Once you are finished filling up the form fields, click Test connection and check that the resulting connection status on the text field below, shows a message indicating a successful connection.

 

UIPath-bot44

 

If a message indicating otherwise is shown, review the inputted information and try again. Once your connection is successful, click ok.

 

note_pin

You can configure a different connection for each of your Environments by creating a new configuration in their respective tab. You can change these connections for your Test or Production environment from the Management Console.

 

Under the UiPath branch, the new connection appears. Its name is the same as the Tenant Name of your Orchestrator, and you can see your connection details in the main panel of the screen.

 

UIPath-bot05