UiPath Cloud Synchronization V3
UiPath Cloud Synchronization V3 supports the latest features of UiPath cloud orchestrator. This synchronization majorly covers the modern folders features which can be widely used for orchestration along with its sub folders.
UiPath Cloud Synchronization V3 only works with version 2022.6 and above of Enate.
See here for more information regarding which version of UiPath in Enate works with which versions of UiPath Orchestrator:
Steps to synchronize Enate and UiPath Cloud Orchestrator V3
Create a new RPA Sync Connection in Enate
You do this by going to the RPA Sync Integration section in Enate Builder and selecting the '+' icon to add a new connection. Enter a Name for the connection and from the Technology dropdown select 'UiPath Cloud Synchronisation V3'.
In the following pop-up, fill in the following details:
URL - URL of the UiPath Orchestrator
Tenant Name - Tenant logical name for UiPath Orchestrator
Account Logical Name - Account logical name for UiPath Orchestrator (Field name: Organization ID)
User Key - User key for UiPath Orchestrator
Client ID - Client ID for UiPath Orchestrator
Credential Store Name – The name of the credential store, used to store robot credentials
See below for where you can find these details.
Once all the details have been entered, you need to Test the Connection.
Once the connection has been tested successfully, click to enable the connection:
Extracting Details from Orchestrator
To get the details required to establish the RPA connection in Enate, log in into UiPath Orchestrator with your username and password - link to UiPath Orchestrator.
Navigate to: Admin -->
DefaultTenant --> Services --> Orchestrator --> API Access
Click on the ellipses on the right-hand side of the orchestrator and select API access.
In the following pop-up you can find the User Key, Account Logical Name, Tenant logical Name, Client ID information.
Restart the application engine
Now go to Enate Manager and open the instance to re-start the application engine:
Open UiPath Assistant
Open UiPath Assistant and navigate to User Profile > Preferences > Orchestrator Settings.
In the Connection Type dropdown, select ‘Service URL’ and then in the resulting Service URL dropdown select ‘https://cloud.uipath.com/’.
Then click to 'Sign in'.
Click to 'Open UiPath':
Once you are signed in, the Status will now be showing as Connected.
Open UiPath Orchestrator
Now you need to make sure to check that your machine shows up in Cloud Orchestrator. To do this, go back to UiPath Orchestrator and then click on Tenant and Machines.
Select a Folder
Now you need to select a modern folder to assign a robot account to, to assign a machine to and to create an automation process in.
To select a folder, click on Orchestrator (on the left side), then Tenant and then click on the Folders tab.
Here you can either either create a new folder by selecting the New Folder icon or you can use the default ‘Shared’ folder.
Create a Robot account
The next step is to create a Robot account. You can do this by navigating to the Admin section of UiPath Orchestrator and then selecting:
Enate --> Accounts & Groups --> Robot Accounts --> Add Robot Account
In the following pop-up add the name of the Robot Account, select 'Everyone' under the Group Membership options and then click 'Add'.
Assign roles
Now we need to assign roles to the robot account. To do this, click on the folder which we created, and then go to Users --> Settings --> Manage access --> Assign Account/Group.
Search for the robot account we just added and select it from the drop down.
Then add a 'Robot' role to the robot account and click on 'Assign'.
Once you have done this, the robot account will appear in the modern folder with its roles.
Assign Machine to the modern folder
You now need to assign a local machine to the folder. To do this, click on Tenant and then Settings. Click on the ellipses of the folder you just created and hover over 'Settings'. Then click on 'Assign Machines'.
Select the local machine name and click Update.
Now the local machine will show in the modern folder you created under the Machines tab.
If a red warning symbol appears, it means that there is no license assigned to the machine. To assign a license, go to the modern folder home screen and click on the Machines tab.
Click on the ellipses menu and then select 'Edit Machine'.
Here you can update the production license from '0' to '1' and click 'Update'.
Now the machine is licensed and we can see that the warning symbol has disappeared.
Check Bot and Bot Environment Synced
And now when we go to the Robots section (under User Management) in Enate, you can see that the robot you've just created in UiPath Orchestrator is showing in Enate.
Update robot to run a job/process
In the Unattended Setup section, under the Foreground automated settings section select 'Use a specific Windows user account. Add credentials below'.
In the resulting fields give your Domain\Username according to the following format: enate\firstname.lastname with 'enate' as the domain and you name as the username e.g. enate\rama.verdelli and enter your enterprise password as the password.
Publish the Project in your Machine
The next step is to publish the the UiPath project in your local machine. To do this, go to UiPath Studio, select the desired UiPath project that Enate will trigger based on Action configuration and click 'Publish'.
And then in Package Name enter the name of project you are wanting to publish and click Next.
Then for the Custom URL click the folder icon and select the folder where you want to save the package and then select 'Publish'.
Upload Package to UiPath Orchestrator
Once the package is published you need to upload it to UiPath Orchestrator. To do this, go to Tenant, select the Packages tab and then click on Upload.
In the resulting pop-up, select the published package from the local folder you have just saved it to and click Upload.
The recently uploaded package should now be visible in the Packages tab.
Create a Process Using the Package
The next step is to create a process using the package you have just published in the previous step.
To do this, navigate to the desired modern folder and then click Automations > Processes > Add Process
Select the package that was just published in the previous step and click Next.
Add a Display name and a description if you want and then click Create.
Then click on the play button to start the job manually from Cloud Orchestrator:
In the following screen, enter the same robot account, local machine and hostname as selected in the above steps and click Start.
In the Jobs tab you can see that the job is now running.
And you can see when the job is completed.
Back in Enate, click to edit the robot that got synced:
And then click to edit the Bot Farm.
Here you need to click on the Integration Process dropdown and select the job you want the Bot Farm to perform:
We now need to configure an Action that can be performed by the bot. To do this we need configure the Bot Farm (from Orchestrator) in an Action's General Settings.
To do this, select to clone the General Settings of the Action and then add the bot farm that we adding in the integration process. You can add the estimated duration for the bot to complete the action if you want.
We then need to adjust the allocation rules for the Action. To do this, select to clone the Allocation rules and then in the Queue field select the desired Queue (we will add the bot to the Queue in the next step).
Set the process live.
Add bot to Queue
Once the process has been set live, as a Team Leader go to the Queues page, click on edit and then add the robot to the Queue you want it to work from.
When the Case process you have just configured gets launched in Enate Work Manager, and when the Action we have just configured gets created, the integration process will be triggered.
When the Action is created and pushed to a Queue that has the desired deep-integrated robot, it sends a message to UiPath Cloud Orchestrator to get a job ready for the selected integration process for the selected robot.
You will be able to see when the job triggered from Enate has completed successfully.
Last updated
