Managing UiPath resources

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Bots > RPA life cycle management  >

Managing UiPath resources

Overview

After you import all your UiPath infrastructure in Bizagi, some stakeholders in the project can manage some of the resources. This article describes managerial actions that stakeholders can execute in the project in three main items:

 

Managing Machines

Managing Applications

Managing Assets

 

Managing machines

Machines are physical or virtual computers where robots execute RPA processes. Usually these processes need to access or run applications installed in the machine. Therefore a Machine Manager stakeholder can control not just machines, but applications installed in them.

 

A user set as Machine Manager stakeholder has in its ME menu the Machines section group:

 

LCM_1_MNGT

 

Here you find a list of all the machines imported from UiPath, where you can see some information on each machine such as the hostname and operating system. Also, you can review the list of installed applications and the tenant associated with the machine:

 

LCM_2_MNGT

 

Additional to the information you can consult in each machine, a Machine Manager can perform the following actions:

 

View log: See all the actions executed upon the machine that is registered in the log.

 

LCM_3_MNGT

 

Update: You can update the machine information such as the name, Machine Key, and operating system. This action triggers a new case of the Update Machine processes so bear in mind that this case also appears in the Machine Manager inbox, Finish updating cases properly before continuing.

 

LCM_4_MNGT

 

note_pin

The machine key must be obtained from the UiPath orchestror.

 

Delete: The Machine manager not necessary is responsible for the machine. Therefore, only the machine responsible can delete machines. The Machine manager can request the machine to be delete. When he clicks the Delete button, Bizagi displays a request message:

 

LCM_5_MNGT

 

Install application: Before installing an application in a machine, the Application manager must add (register) an application in the list of applications that bots can use. See Managing applications. After clicking the Install application button,  the Machine manager can search for registered applications, and click create.

 

LCM_6_MNGT

 

Bizagi creates a new case of the Install application process, where the installation report and version of the application must be registered.

 

LCM_7_MNGT

 

Uninstall application: When a stakeholder clicks the uninstall application button, Bizagi opens a start form to select the application, and after clicking Create, Bizagi starts a case of the Uninstall application process:

 

LCM_9_MNGT

 

Managing applications

Similar to the Machine manager, an application manager can see a section in its Me menu, where Bizagi displays all the applications registered:

 

LCM_10_MNGT

 

For each application you can see the description, a list of all machines where this application is installed and the application's credentials needed by a bot to use it.

 

LCM_11_MNGT

 

Here an Application manager can perform the following actions:

 

View log: Every time an application manager change something on the application in Bizagi, a log displays the actions taken by the user:

 

LCM_12_MNGT

 

Deactivate: When the application manager clicks this button, Bizagi executes a rule that changes the status of an application to deactivated, so bots cannot use this application in a machine. Nonetheless, the application can be turned to active any time the same way.

 

Add credentials: Because applications can be used for different purposes, you can add different credentials so a bot can run the application with defined permissions. When the application manager clicks the add credential button, Bizagi creates a new case of the Add new credentials process. Here the manager can register a user name, and who is the RPA asset manager related to this credential. See Managing assets.

 

LCM_13_MNGT

 

Managing assets

Assets in UiPath are variables that can be stored in the Orchestrator so bots can retrieve them for its use. See glossary. An RPA Asset manager, hence, can manage the variables or credentials of all the applications registered in your RPA life cycle management project. In Bizagi there are four possible asset types:

 

Boolean

Text

Integer

Credential

 

note_pin

If you need to create a credential asset type, first you need to store a credential. Only the Orchestrator manager can add new assets, see Stakeholders and roles. Once an asset is in the Bizagi project, the RPA asset manager can manage them.

 

When the RPA Asset manager accesses the Work Portal, he has the following groups:

 

Credentials

Assets

 

LCM_14_MNGT

 

Credentials

A credential is a user name and password that a bot can use to use the application. In UiPath, you need to store credentials as an asset, so the steps are:

 

1.Register a new application by the Orchestrator manager

2.Register new credentials for the application by the Orchestrator manager.

3.Register those credentials as an asset by the Orchestrator manager. See import UiPath resources.

 

After these steps are executed, the RPA asset manager can manage both credentials and UiPath assets. When looking at the Credentials group in the Me menu, you can see the user name, the application and responsible of that credential:

 

LCM_15_MNGT

 

The RPA asset manager can:

 

Delete: Delete this credential related to a specific application. If the user is not the responsible of the credential, he can request the deletion of it by clicking the Create button:

 

LCM_17_MNGT

 

Bizagi starts a new case of the Delete credential process.

 

LCM_18_MNGT

 

View log: View the history of actions related to the credential in a log:

 

LCM_16_MNGT