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.
Information you can enter here for UiPath Orchestrator:
Activities
Comments
Name
Your Enate-friendly name – you can enter anything you like here as a name.
Technology
Select UiPath
Description
A general description
URL
The URL of UiPath Orchestrator e.g. https://platform.uipath.com/
Tenant Name
Your individual UiPath Tenant Name (also known as Service). Take this from your ‘Services’ section in UiPath Orchestrator.
User Name
The username for this Service in UiPath.
Password
The username for this Service in UiPath.
Furthermore you can run a live connection test (which will store information in the Connection Log tab of the popup).
You are able to copy the Bot username by clicking on the copy icon.
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.
Enate supports various RPA Sync Integration for Cloud Orchestrator for UiPath, which uses their new authentication, UiPath Cloud Syncronisation V1.
The details required to enter into the new sync can be obtained from UiPath within their Admin\Services section of Cloud Orchestrator. On the Services tab, click the … elipses at the end of a row to display the ‘API Access’ section.Enate supports various RPA Sync Integration for Cloud Orchestrator for UiPath, which uses their new authentication, UiPath Cloud Syncronisation V1.
The details required to enter into the new sync can be obtained from UiPath within their Admin\Services section of Cloud Orchestrator. On the Services tab, click the … elipses at the end of a row to display the ‘API Access’ section.
These API access details from UiPath Cloud RPA Sync should be entered into the details in the RPA Connection configuration section in Enate Builder.
As an initial step towards moving to a purely Token-based approach for authentication between Enate and UiPath, we now have a new ‘Authenticate’ activity which can be used to generate a token for ongoing authentication throughout a process.
The main change here is:
Instead of requesting ‘username and password’ for each individual activity, processes should now use the ‘Authenticate’ activity at the very start of the process, which will return a token which can then be used for all subsequent activity.
For the moment Enate will continue to support both username and password approach, but will focus on using this new Authentication approach. If an Authtoken is present it will use this over the username / password. The username and password attributes have been removed from the main activity GUI, but can still be accessed via the activity properties screen. Over time, the support for username/password approach will be deprecated and eventually removed in a future release.
When you are using Robots/Farms which are being managed by UiPath Orchestrator, one of the settings you will need to supply for the robot farm is the UiPath Integration Process which that Bot farm is set to do.
In the User Manager section of Builder, open the Robots tab and select an Orchestrator-managed robot.
In the resulting screen, click on the Edit icon on the farm you wish to modify.
This will bring up the ‘Update Farm’ popup.
Since this is eternally managed, all data will be read-only except the ‘Integration Process’ dropdown. Select the relevant integration process, i.e. the UiPath Orchestrator process this robot farm is set to perform.
Previously this setting was only accessible by logging into the old User Manager client app.
The Enate Activity Library is available in the following RPA vendor’s software:
UiPath
Automation Anywhere
BluePrism
Softomotive
UNO technology (recently added)
The following activities are available within the Enate Activity Library for interacting with RPA software:
Get More Work - Returns the next piece of work the User/Robot should work on. The result is represented by a PacketForList object which contains enough information to determine next steps, which may include getting the full Case/Ticket/Action details with the appropriate Activity.
Get Action - Returns an Action and all its details as an ActionPacket.
Update Action -Updates an Action in Enate based on changes made.
Please note: There has been an improvement to Robotics workflow to allow it to move an Action from state of ‘schedule for follow up’ to a state of ‘running’ without impacting who the work is assigned to - this will make bot routines easier to program and will improve performance time.
Update Checklist -Updates an Action Checklist in Enate. Can be used to show progress during a long running Action (alternatively all Checklist items can be updated at once with Update Action).
Add File To Item - Adds a file from disk to a Work Item. (need to then save that change with an Update Action)
Save File - Saves a file from a Work Item to disk.
Create Case - Creates a new Case for a process instance. (Process instance available from GetCaseProcess Activity.
Get Case - Returns a Case and all it's details as a CasePacket.
Update Case Updates a Case in Enate based on changes made.
Reject Work - Sends a Packet back to the server and stops a Robot from receiving it again.
Is Work Available - Returns true/false indicating if there is more work for a User/Robot to work on.
CreateTicket - Creates a new Ticket for a process instance. (Process instance available from GetTicketProcess Activity.
Get Ticket - Returns a Ticket and all its details as a TicketPacket.
Update Ticket - Updates a Case in Enate based on changes made.
CreatePacket - Creates a new packet for a Case/Ticket for a process instance. (Process instance available from GetCaseProcess/GetTicketProcess Activity.
Get Case Process - Returns a ProcessInstanceVersionGUID (Guid) from the matching customer\contract\Service\process to be used in CreatePacket/CreateCase
Get Ticket Process - Returns a ProcessInstanceVersionGUID (Guid) from the matching customer\contract\Service\process to be used in CreatePacket/CreateTicket.
Add Row To Custom Table - Adds a row of data to a custom data table (Datafields collection within a Packet) (need to then save that change with an Update Action)
Add Data To Row - Adds a column data to tableEntry for use with AddRowToCustomTable Activity
Switch between live and test mode - New activities have been added to the UiPath activity library to allow bots to switch between running in live and testing mode, ‘Switch to test mode’ and ‘Switch to live mode’.
Once running in test mode, any subsequent calls the bot makes to Enate to e.g. get more work or create new Work Items will take place within test mode
Set assignee - This activity has been created in the UiPath library to allow bots to assign Tickets to specific bots.
Integration Job for Robots – For UiPath Robots their robotics workflow is improved to don’t create Jobs for all bots when new work is available for specific bot in a farm. After this update only the required bot will call enate for more work and process the task.
As an initial step towards moving to a purely Token-based approach for authentication between Enate and UiPath, we now have a new ‘Authenticate’ activity which can be used to generate a token for ongoing authentication throughout a process.
The main change is:
Instead of requesting ‘username and password’ for each individual activity, processes should now use the ‘Authenticate’ activity at the very start of the process, which will return a token which can then be used for all subsequent activity.
For the moment Enate will continue to support both username and password approach, but will focus on using this new Authentication approach. If an Authtoken is present it will use this over the username / password. The username and password attributes have been removed from the main activity GUI, but can still be accessed via the activity properties screen. Over time, the support for username/password approach will be deprecated and eventually removed in a future release.
Each Blue Prism activity which connects to Enate has now been given the following three new properties:
ProxyAddress
ProxyUsername
ProxyPassword
Using these attributes, you can now connect a Blue Prism environment to Enate via a Proxy, something which ws not previously supported.
