UiPath

<< Click to Display Table of Contents >>

Navigation:  Automation Service Management > How to manage your environment with Management Console Web > RPA Bots >

UiPath

Overview

From the MCW, you can view your configured bot processes and modify the connection to your UiPath Orchestrator of your environment. Additionally, you can access your Orchestrator dashboard, where you can monitor it by using charts or retry your failed jobs.

 

View current configuration

Go to the RPA Bots section and select the UiPath option.

 

RPADasboard001

 

On the center panel you can see the available connections.

 

RPADasboard012

 

When you select one the window will now have the following sections.

 

RPADasboard002

 

1.RPA configuration: In this section you can see and modify your Orchestrator connection

2.UiPath processes: In this  section you can see the name of all your configured UiPath processes that use this connection

3.Dashboard: You can access the two sections of the RPA Dashboard: Charts and Retries

 

Configure connection

In the section called RPA configuration you can change your connection configuration. 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-Premise 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/.

 

Fill the required fields and click test connection.

 

RPADasboard014

 

If you get the following message

 

RPADasboard013

 

Save your changes

 

RPADasboard015

 

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

 

Fill the required fields and click test connection.

 

RPADasboard032

 

If you get the following message

 

RPADasboard013

 

Save your changes

 

RPADasboard033

 

Charts

In this section you can view a report of your Orchestrator's Jobs and Queue Items in chart form.

 

RPADasboard003

 

To access this section go to the Chart button under the RPA Dashboard section. You must wait a few seconds until the report loads.

 

RPADasboard016

 

You can see three pie charts showing the status of all jobs executed in the last 24 hours, 7 days, and 30 days. Additionally, a 2-D line graph shows the number of executions by status each month of the last year.

 

RPADasboard003

 

You can remove a status from your graph by clicking the label showing the status name. The Dashboard will cross-out the excluded status label.

 

RPADasboard018

 

You can view a similar report for your Queueitems by clicking on the Queueitmes button.

 

RPADasboard005

 

If there is no data to display a blank chart is shown.

 

Retry Jobs

In this section you can view the failed Orchestrator Jobs and Queueitems and retry them directly from the MCW.

 

RPADasboard006

 

 

To access this section go to the Chart button under the RPA Dashboard section. You must wait a few seconds until the report loads.

 

RPADasboard017

 

You can retry your failed jobs by clicking the RPADasboard019 icon. You can retry your failed jobs by clicking the icon. The MCW creates a new instance of the job. Since this is a different instance, the failed job will still be visible in the list.

 

RPADasboard020

 

A new panel appears showing additional information about the job.

 

RPADasboard021

 

Click Yes, retry job and wait until the following message appears.

 

RPADasboard022

 

You can view a similar window for your Queueitems by clicking on the Queueitmes button.

 

RPADasboard007