Enate UiPath Activity Library - Overview

The Enate Workflow Activity Library allows easy integration with Enate’s enterprise workflow engine. It allows bots to get work from the Enate platform, edit the data, add or download files and update the Enate platform. We can also create new work items on the Enate platform using the activities.

The .Net Workflow Activity library allows easy integration with Enate v2021.1 and above. The Activities will perform authentication when necessary and allow a single authentication token to be passed between concurrent calls to improve performance.

Authentication will be done through the Authenticate Activity. This will return an Authentication Token which can then be passed to the other Enate Activities.

All date/time values are passed in UTC and each Enate Activity has a standard set of 4 arguments:

• PlatformURL (String) - This should be set to the URL of your Enate instance, as you would type in a portal to get to the login page. e.g. https://hosting.enate.net/MyInstance

• Username (String) - Any valid Username for your Enate instance. Only required if AuthenticationToken is not set or has expired.

• Password (String) - The current Password for the user account specified in Username. Only required if AuthenticationToken is not set or has expired.

• AuthenticationToken (String) - After an initial call to an Activity has succeeded its authentication token can be reused if the next call is made within the configured timeout window. The timeout is configured per customer instance so please check your token validity duration with Enate Support.

Each successful Activity will output a new AuthenticationToken that resets the timeout window.

All activities can be found in the Activities panel, under Enate > Workflow > Activities.

These activities enable you to build complex rules for interacting with the Enate platform combining them with UiPath’s built-in functionality for if/else or switching to make conditional decisions for powerful workflows.

You can find all of Enate's Activity Libraries in the sections below, as well as explanations of each of the activities available.

Check out the setting up the Enate Activity Library in UiPath Studio section which details how to install this file in UiPath Studio to get access to Enate's dedicated Activity library.

Latest Enate Activity Library

Activity Library v1.3.3

Changes made as part of this release is:

• Fixed a bug related to CreateCase and CreateSubCase Activities.

Activity Library v1.3.1

In this version we have fixed the CreateCase and CreateTicket activities to add Service Agents contact while creating Case or Ticket - Previously while creating a Ticket or Case We were allowing only external contact to be added whereas Now users should be able to add service agent contact and external contacts as well.

Activity Library v1.2.19

This release focuses on supporting workflows in Windows Legacy which is in sync with the release of version 2024.1 of Enate. In this version, we have fixed the CreateCase and CreateTicket activities to add Service Agents' contact while creating a Case or Ticket.

This version of the UiPath package only works with version 2024.1 and above of Enate and is the final release for Windows Legacy Previous Activity Libraries

Previous Activity Library

Activity Library v1.3.0

This release focuses on upgrading workflows from Windows Legacy to Windows.

Activity Library v1.2.18

In this release we have updated the GetCommunications and SendEmailCommunication activities to align with the updated APIs in Enate following the most recent product release.

Activity Library v1.2.13

In sync with the release of version 2022.5 of Enate and the customer GUID field in the /Packet/GetContexts API being made mandatory, the GetTicketProcess, GetCaseProcess, GetCaseProcesses and GetCaseAttribute activities have been updated.

Note that the GUI for the GetCaseProcess activity is yet to be finalised, but users can still enter property fields in the Properties window on the right.

Also note that for the GetCaseProcesses activity, the Customer Name property has now been made mandatory.

Activity Library v1.2.8

You can download the Enate UiPath Activity Library v1.2.8 from the links below. In this version we have improved saving work item communication attachments. Previously when saving an email attachment, if a special character(s) was present in the file name, the special character(s) would be replaced by an empty space upon saving. Now when saving email attachments with special character(s) in their name, the name of the file is not changed - the special character(s) are included.

Activity Library v1.2.5

In this version we have added a new field in the CreateCase and CreateTicket activities called ‘Do Not Send Automated Emails’. When the Boolean value is set to True, the request acknowledgement email will not be triggered/sent. When the Boolean value is set to False or the field is left empty, the request acknowledgement email will be triggered/sent.

You can download the Enate UiPath Activity Library v1.2.5 from the links below.

Activity Library v1.1.9

Below is a copy of the Enate UiPath Workflow Activity Library for v1.1.9. In this version we have fixed the ‘AttachFile’ activity - previously it was mandatory when attach a file to a work item for the file to have a file tag whereas now users are able to attach a file to a work item with or without a file tag.

Activity Library v1.1.8

Below is a copy of the Enate UiPath Workflow Activity Library for v1.1.8. In this version we have added the Nito.AsyncEx library within the latest UiPath package so that you no longer need to add it manually.

Activity Library v1.1.4

Below is a copy of the Enate UiPath Workflow Activity Library for v1.1.4:

Activity Library v7.3.12

Below is a copy of the Enate UiPath Workflow Activity Library for v7.3.12:

Activity Library v7.3.10

Below is a copy of the Enate UiPath Workflow Activity Library for v7.3.10:

Activity Library v7.3.7

Below is a copy of the Enate UiPath Workflow Activity Library for v7.3.7:

Enate UiPath Connector v7.3.7 works best with v2021.1.

The key updates for this connector are:

• Ability to add file tags and contact tags to Cases and Tickets

• Ability to launch a Case linked to a Schedule

• Ability to launch ad-hoc Actions

• Ability to extracting communications and saving the communication attachments locally

• Ability to attaching files to Cases, Tickets and Actions

In v2021.1 bots can access Builder APIs to get contact tags, file tags etc. To enable this:

Edit the bot in User management

Update the bots access permissions and save

Activity Library v7.2.10

Below is a copy of the Enate UiPath Workflow Activity Library for v7.2.10:

Activity Library v7.2.9

Below is a copy of the Enate UiPath Workflow Activity Library for v7.2.9:

Activity Library v7.1.1

Below is a copy of the Enate UiPath Workflow Activity Library for v7.1.1:

To set up Enate and UiPath, you'll need to go through the following steps in order:

1. Set up UiPath Studio

2. Set up the Enate Activity Library in UiPath Studio

3. Add a UiPath connection in Enate

1. Setting up UiPath Studio

You'll first need to set up UiPath studio. The following video will take you through how to do this.

You can follow this link to create a UiPath Automation Cloud account: https://cloud.uipath.com/portal_/register

2. Setting up the Enate Activity Library in UiPath Studio

Now you need to set up the Enate Activity Library in your installation of UiPath Studio. Watch the following video to find out how to do this:

3. Adding a UiPath Connection in Enate

Once you have set up UiPath Studio and then set up the Enate Activity Library in your installation of UiPath Studio, you can now add a UiPath connection in Enate's Builder.

To do this, go to the Marketplace section in Builder and click to 'Activate' UiPath Orchestrator.

In the following page click on the '+' to add a new connection.

In the following pop-up, fill in the following fields:

Depending upon which technology you choose, the following fields may also need to be filled in.

To enable a connection, the connection has been tested successfully first. Click to 'Test Connection' which will run a live connection test and when a successful response has been detected, the connection will be enabled.

You can see details about the connection test in the Connection Logs tab.

Editing a UiPath Connection

You can edit an existing UiPath connection by going to the Marketplace section in Builder and clicking to 'Update' UiPath Orchestrator.

When editing a connection, you are also able to see the activity history of the connection by clicking on the Show Activity button. You can see when the connection was created and by who and you can see if any subsequent edits have been made, when they were made and by who.

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.

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.

UiPath Cloud Synchronization V2 supports synchronisation with classic folders in UiPath Cloud Orchestrator.

See here for more information regarding which version of UiPath in Enate works with which versions of UiPath Orchestrator:

Synchronization between Enate and 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.

Details Required to Configure a Connection

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

Extracting Details from Orchestrator

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)

Enate Process and Queue Configuration

Builder Configuration

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.

Adding Robots to the Queue

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.

Manage Page View and Running a Work Item

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.

Overview

Enate supports a number of RPA technologies including UiPath, Blue Prism, Automation Anywhere and Power Automate.

The Enate UiPath connector allows easy integration with Enate’s enterprise workflow engine. It allows bots to get work from the Enate platform, edit the data, add or download files and update the Enate platform. We can also create new work items on the Enate platform using the UiPath Activity.

The UiPath section in Marketplace is where you can create and maintain your UiPath connections.

You can find out how to integrate Enate and UiPath to start including Enate activities in your bot routines here:

Click here to see Enate's latest UiPath Activity library:

You can find information on how to integrate Enate with the UiPath Orchestrator here:

Click here for a useful tip on how to populate row data directly into an Enate Case while it's being created:

Sample Integration Patterns Using UiPath

Overview

This section gives an overview of how to integrate Enate with the UiPath Orchestrator. It provides steps on how to establish a connection between UiPath Cloud Orchestrator and Enate.

UiPath Orchestrator is a web application that enables you to orchestrate our UiPath robots in executing repetitive business processes. Orchestrator lets you manage the creation, monitoring and deployment of resources in our environment. It acts as an integration point with third-party solutions and applications.

Enate’s process orchestration platform simplifies the process from start to finish, ensuring the right worker does the right thing at the right time. It streamlines the management and governance of large-scale processes involving digital, human and hybrid workforces.

There is a dedicated section available in Enate Builder to configure a bot Action where as soon as the bot Action is launched in Enate, it sends a message to the UiPath Orchestrator which creates a job in Orchestrator. Orchestrator then invokes the machine/bot to perform the action defined in the bot routine.

Enate has 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.

UiPath Orchestrator Sync Settings

This document provides information regarding which version of UiPath in Enate works with which versions of UiPath Orchestrator:

The Bot is a User in the system and there are some constraints in using the robots.

• RPA Sync Interval between Enate and Uipath orchestrator is defined under General Settings in Enate Manager. By default, the value is 5 mins, but it is configurable.

• As of now, robots cannot work on Cases and Tickets. It only works on Actions. However, Robots can create tickets and Cases.

• Robots cannot access User management i.e., user information, User GUID’s etc.

• If you delete the Robots in the UiPath Orchestrator, they are not deleted in Enate.

• The password of the robots created via RPA Sync with the orchestrator cannot be manually changed in Enate.

• For some reason, the robot authentication fails and there is a need to reset the password.

  • First, check the password is working or not. There is a single line of code that needs to be written to extract the robot password for the bot synchronized between Enate and Uipath Orchestrator.

plainStr = new System.Net.NetworkCredential(string.Empty,secureStr).Password

• This needs to be written inside an assign activity where plainstr is a string variable and securestr is the password output of Get Credentials.

• Once the password is obtained then open the swagger page and check if the authentication is working or not.

• If the Authentication is not working, then in the database update the PasswordLastChanged column to more than 30 days back in tblusers and after the RPA Sync Interval time Enate will reset the password for the robot and sync it with the Uipath orchestrator.

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.

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 Orchestrator V4

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 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.

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.