# UiPath Synchronization V4
UiPath Synchronization V4 supports the latest features of UiPath orchestrator. This synchronization majorly covers the modern folders features which can be widely used for orchestration along with its sub folders.
{% hint style="info" %}
UiPath Synchronization V4 only works with version 2022.6 and above of Enate.
{% endhint %}
See here for more information regarding which version of UiPath in Enate works with which versions of UiPath Orchestrator:
{% file src="/files/fBP8rm5M1UdMOWGsEaRq" %}
## **Steps to synchronize Enate and UiPath Orchestrator V4**
### Create a new RPA Sync Connection in Enate
You do this by going to the [RPA Sync Integration section in Enate Builder](/enate-help/integrations/enate-integrations/uipath/setting-up-enate-and-uipath-orchestrator-synchronization/uipath-synchronization-v4.md) and selecting the '+' icon to add a new connection. Enter a Name for the connection and from the Technology dropdown select 'UiPath Synchronisation V4'.
In the following pop-up, fill in the following details:
* URL - URL of the UiPath Orchestrator
* Tenant Name - Tenant name for UiPath Orchestrator
* Username - Username for UiPath Orchestrator
* Password - Password used to access UiPath Orchestrator
* Credential Store Name – name of the credential store, used to store robot credentials
[See below for where you can find these details](#extracting-details-from-orchestrator).
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
Create a user account for your on prem Orchestrator and use these details (URL, username, password, tenant name and credential store name) to establish the RPA connection in Enate.
### Restart the application engine
Now go to Enate Manager and open the instance to re-start the application engine:
### Log in to On Prem Orchestrator
Create a machine template by clicking Tenant and then Machines. Click on Add Machine Template
Click Provision after entering the Template name and increasing the number of Licenses to at least 1
Now you need to make sure to check that above created machine shows up in under Tenant -> Machines.
### Open UiPath Assistant
Open UiPath Assistant and navigax\`te to User Profile > Preferences > Orchestrator Settings.
In the Connection Type dropdown, select ‘Machine Key’ and then in the Orchestrator URL field enter your organisation's on prem orchestrator URL.
Then click to 'Connect'.
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
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 Tenant and then click on the Folders tab.
Create a new folder by selecting the New Folder icon.
### Create a Robot account
The next step is to create a Robot account. You can do this by navigating to Tenant -> Users -> Add Local User
Click on ‘Unattended Robot’ section on the left side, make sure to enable the toggle ‘Automatically create an unattended robot for this user’ and enter domain\username and password of the account under which this robot runs and 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. Browse to the modern folder created in previous step, navigate to Home -> Machines
Click “Manage Machine in Folder”
Search for machine created in previous step, select and click Update
Now the local machine will show in the modern folder under the Machines tab.
### 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.
### 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 Continue.
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 on prem 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 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.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.enate.net/enate-help/integrations/enate-integrations/uipath/setting-up-enate-and-uipath-orchestrator-synchronization/uipath-synchronization-v4.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.