UiPath Cloud Synchronization V2
PreviousUiPath Cloud Synchronization V3NextGeneral Questions and Issues, Debugging and Troubleshooting
Last updated
Last updated
UiPath Cloud Synchronization V2 supports synchronisation with classic folders in UiPath Cloud Orchestrator.
UiPath Cloud Synchronization V2 only works with version 2019.9.6 and above of Enate.
See here for more information regarding which version of UiPath in Enate works with which versions of UiPath Orchestrator:
In Enate, we have a dedicated RPA section available in the Builder, where we can create and maintain the connections to Orchestrators :
Within this section, we can configure multiple UiPath Orchestrators with which the Enate environment can be synchronised.
To add a new connection, click on Add Connection, give a name to the RPA connection based on the release version select the relevant technology (here we have selected the technology as UiPath cloud synchronization V2). The popups are dynamically launched according to the RPA Technology selected.
To establish a connection, we need below details:
URL - URL of the UiPath Orchestrator
Account Logical Name - Account logical name for UiPath Orchestrator
Client Id - Client Id for UiPath Orchestrator
Folder Name - The name of the folder
Tenant Logical Name - Tenant logical name for UiPath Orchestrator
User Key - User key for UiPath Orchestrator
Credential Store Name – The name of the credential store, used to store robot credentials
Open the URL https://cloud.uipath.com/portal
Login into UiPath Orchestrator with the username and Password.
To get the details required to establish the RPA connection, click on admin (on the left-hand side) and then go to Tenants.
Expand the Tenants, click on the ellipses on the right-hand side of the orchestrator, select API access, copy the User Key, Account Logical Name, Tenant logical Name, Client Id and paste it in the desired sections of RPA connection in Enate
Copy and paste the relevant data in the relevant fields of the below-highlighted section.
To create or access the folders, select the orchestrator (on the left side) and then go to tenants, click on the folders tab, we can use an available folder or else can create a new one. (As of now Enate supports only the classic folders).
Copy and paste the folder name in the below-highlighted section of the RPA connection.
To get the credential store name, go to the credential stores tab in the Uipath orchestrator, copy and paste the credential store name in the dedicated section of the RPA connection (as shown below).
The URL will be the URL of the Uipath orchestrator. i.e., https://cloud.uipath.com/portal.
Test the connection and enable it, once the connection is successful.
After establishing the connection, we need to connect the machine to the orchestrator. To do that, go to the machines tab in the tenant, and then click on add a new standard machine, basically the name of the machine will be the laptop’s name (Open the Control Panel. Click System and Security > System). Give License as 1.
The next step is to create a Robot, Click on the folder which we created and then go to the Robots tab, click on Add robot(standard). Provide the Machine name, name of the robot, select the type (Non-Production), domain name/Username (the one which we use to login into the system), the password is the password used for logging into the system and the credential type will be windows.
Once the Robot is created, we need to create the Environment, (environment is the bot farm that we create on Enate), click on Add environment, give the name to the Environment, and click on create.
Since the connection between Enate and UiPath orchestrator is already established, environments and robots will be synced into Enate automatically.
In the Assets section, Enate will sync the environment URL and robot credentials.
To connect the machine (laptop) to the UiPath Orchestrator, copy the machine key from the machines tab in tenants and then open the Uipath Assistant in the machine(laptop), click on preferences in UiPath Assistant and then go to Orchestrator settings (on the left-hand side), select the connection type as Machine Key, give the machine name & machine key and orchestrator URL e.g. https://cloud.uipath.com/AnkitEnate/AnkitEnate, where (https://cloud.uipath.com- is the URL of UiPath Orchestrator, /AnkitEnate is the Account Logical Name/ AnkitEnate is the Tenant Name) after filling in the details click on connect, now the machine got connected to the Uipath Orchestrator.
And now when we go to the Robots section (under user management) in Enate, we can see the bot farm and the robot’s name.
Once the machine is connected to the orchestrator the relevant folder will appear at the bottom of the routine as shown below screenshot. (e.g., Amidha Folder).
In the Main file of UiPath Bot Routine, below Routine is published.
Get credential activity is used along with Enate activities. The output from getting credential activity will be username and password which is synchronized with Enate and UiPath orchestrator which will then be used for authentication of bot into Enate instance.
Username is the Username of the Bot created in Enate and password is the password created in Enate and it is a secure password. So Please tick the checkbox of “Secure String “ in Authentication.
The next step is to publish the Main file of the UiPath bot routine, to do that, select the package name that needs to be published. (Publish will publish the process in the relevant folder)
Once the package is published, go to the folders in the Uipath orchestrator, and then go to the Automations tab, click on Add Process. In the Package source name, select the package which was published recently.
Go to the Robots in the User management tab on Enate, select the Bot Farm and define the integration process. (In the Integration process user needs to select which process needs to be triggered when the Action for the Bot Farm is available to work on)
In Builder, we now need to configure an action that can be performed by the bot. To achieve that we need to go configure the Bot Farm in the Action General Settings in the Action Info.
In the general settings, the user needs to define the bot farm (can be performed by Robotics Group) and the estimated duration for the bot to complete the action.
Team Leaders are the only people who can access the Queues Page. To add the robot to the queue, navigate to the queues section from work manager, click on edit and then add the queue in which the bot needs to be added.
Once the respective queue is added, click on the ‘+’ icon on the queue and then add the robot.
The below screenshot explains how to add a robot to the queue.
As shown in the below Screenshot, the bot is now added to the queue.
Once a Bot Action is launched in Enate, it sends a message to the UiPath Orchestrator which in turn creates a job in Orchestrator (which is available in Automation’s tab in UiPath Orchestrator). Orchestrator, then invokes the bot to perform the action defined in the bot routine.
Team Leaders can see the bot farm and the current status of Bots in the Work manager.
In the above screenshots, there is an action that is available for a bot to perform. When the Bot Routines executes the bot will get the action. If there are multiple work items then the bot will get the single most important piece of work based on the SLA.
We can now see that the Action is completed by the Bot which was created in the Uipath orchestrator and synchronized in Enate.
