Enquero is a technology solutions company helping enterprises in their digital transformation journey. Founded in 2014 and headquartered in Silicon Valley, USA, we have more than 600 members spread across 8+ locations worldwide. We drive innovation through a creative mix of cutting-edge technology and technical know-how to solve our customer problems efficiently. Our focus has always been on the digitization of organizations through the integration of information, skills, and experience. At Enquero, we're helping our customers appreciate what's feasible, assess what's important, and execute what's meaningful. Our people and platform are the keys to doing this successfully.

42b0a651-eac6-4732-9826-f9e8e285b5b3.png

Principal Architect

BOT user is often required to access different physical and network shared file paths for various file I/O operations, especially when working with MS Excel, CSV or PDF files. All such shared directories and sub-directories have access permissions defined through some Group Policy by the IT administrators. In lots of business requirements, the BOT process during its execution is required to access the file paths to read or write files from/to the source/destination address respectively. But in practice, it is mostly seen during BOT development or migration to Test/Production servers, the BOT processing fails when the file paths access permissions are not as expected.

  

The FilePathAccessValidator workflow is developed using a Windows PowerShell script. The inbuilt Invoke PowerShell activity of UiPath executes the PowerShell script to query Windows Folder objects to list user permission details.

It expects two file paths as inputs: 

*   one to read access permission details
*   other to write output summary in a CSV file.

Further, a username is provided as input to query in the CSV result set. Later, developers can read the permission details from the CSV file to tailor their needs to proceed further in the workflow. In the attached workflow, its usage is also illustrated with a hypothetical use case to query and print the user’s permission details in logs.

Handle the file path pre-validation need and the access permission from the beginning of a BOT development cycle.

_Hybrid Automation_ is a practice of developing a single integrated platform of automation solution by bringing together the Attended and Unattended Robots to automate business processes end-to-end. Such robots are called hybrid robots. 

  

While the attended robot helps with the customer or user facing front-end processes, the unattended robot does intensive back-end processing. When the user triggers the attended robot, it picks the front-end processes to complete tasks which can provide enough context to kick-off the next unattended robot to complete the required back-end processing. This way, the user is in full control of letting the both attended and unattended robots function on the business processes on his demand. Customer Support, HR, Sales and Invoice Processing are some of the business use cases where the user at the front-end is in-charge of initiating the end-to-end processing tasks.

  

_Sales Mailing Agent BOT_ workflow is an abstract implementation of hybrid automation robot, bot in short. The implementation is based on a sales process scenario where a sales person is required to send a bulk email to multiple prospects in the introductory phase. The sales person has a list of prospects’ email-ids, names, company names, subject of the email campaign, etc. The sales person can delegate to the hybrid robots the task of sending emails to the prospects. This way, the sales person can engage himself into other valued added strategic tasks to convert prospects into customers.

Sales Mailing Agent BOT workflow is an abstract implementation of a hybrid automation robot to demo a sales process scenario, to send a bulk email as part of sales promotional campaign.

Software Engineer 

_Uber Invoice Reader_ is a BOT solution to demonstrate reading of an Uber taxi receipt and saving the receipt values into an output file. The use case is inspired from a _claim reimbursement process_ in Finance business, where office employees submit Uber taxi receipts to claim the commute expense.

  

The BOT solution is developed using both _Regular Expression_ match and inbuilt _.Net String functions_. UiPath BOT developers can refer to it to benefit and learn from both the implementations. The BOT results extracted from the Uber receipt is saved in an Excel file, which can be picked by following sequences to ingest into some financial ERP like system.

Uber Taxi Invoice Reader using Regular Expression and String Methods

Lead Engineer

**Sample use case:**

A process is scheduled to run only on the 5th business day of the month for doing payroll calculations for employees for the previous month. The Orchestrator scheduler runs every day for the first 10 days of the month to trigger the payroll process. The process first calls this custom activity to check if the current day is the 5th business day of the month. If this activity returns true, the process runs the payroll calculations. Otherwise, it does not take any actions until next day.

  

**Arguments:**

\- in\_Month\_MMM (String) - Optional input argument which allows the user to provide any month in the string format "MMM". Default value is the current month.

\- in\_OrchestratorCalendarName (String) - Optional input argument which allows the user to provide the Orchestrator calendar name. Default value leads to no non-working days to be considered including the weekend days.

\- in\_BusinessDayOfMonth (Int32) - The index of the business day to be checked for the given month. For example, to find the 5th business day of a month, the value for this argument is 5. Default value is 1 (1st working day of the month).

\- out\_NextWorkingDate (DateTime) - The output argument which returns the date of the nth business day of the month.

\- out\_WorkingDayFlag (Boolean) - The output argument which returns "True" if the out\_NextWorkingDate is the current day.

This activity returns the date of the nth business day of any month based on Orchestrator calendar

**Sample use case:**

  

A process is scheduled to run only on the 5th business day of the month for doing payroll calculations for employees for the previous month. 

  

The Orchestrator scheduler runs every day for the first 10 days of the month to trigger the payroll process. The process first calls this custom activity to check if the current day is the 5th business day of the month. If this activity returns true, the process runs the payroll calculations. Otherwise, it does not take any actions until next day.

  

**Arguments:**

*   in\_Month\_MMM (String) - Optional input argument which allows the user to provide any month in the string format "MMM". Default value is the current month.
*   in\_OrchestratorCalendarName (String) - Optional input argument which allows the user to provide the Orchestrator calendar name. Default value leads to no non-working days to be considered including the weekend days.
*   in\_BusinessDayOfMonth (Int32) - The index of the business day to be checked for the given month. For example, to find the 5th business day of a month, the value for this argument is 5. Default value is 1 (1st working day of the month).
*   out\_NextWorkingDate (DateTime) - The output argument which returns the date of the nth business day of the month.
*   out\_WorkingDayFlag (Boolean) - The output argument which returns "True" if the out\_NextWorkingDate is the current day.

This activity returns the date of the nth business day of any month based on Orchestrator calendar.

RPA developer

52f23d31-23a3-4459-8e05-ba96b946363d.png

In the schenario of having an Excel file with more than 10 million records and the need to apply some sort of filter condition for each and every record, this component helps to read the huge Excel file and convert each sheet into separate Excel files. Then, based on the chunk size (like 2.5lac Excel records as 1 chunk), loop through each newly created Excel file and convert it into small chunk XML documents.

  

In general, when UiPath is trying to access and load entire bulk Excel files into a single datatable and performing datatable activities like sorting, merging, filtering, it throws an "out of memory exception" issue, because UiPath is trying to access more RAM (32 bit application can access only 4gb RAM). In this situation, users can benefit from this snippet to process Excel files chunk by chunk.

This snippet takes the bulk Excel file as input and converts it into small xml based on the chunk size (total records in chunk).

IA Lead Consultant

635995a7-2c78-4343-855c-639d7468e288.jpeg

       Although most of the organisations have started implementing Robotic Process Automation in their business processes, only a few are in full control of the RPA robots. Maintaining high performing virtual robots goes beyond having skilled developers, they have to align to best practices and standards to benefit to the fullest.

  

      A CI/CD (Continuous Integration, Continuous Delivery) pipeline allows you to automate robot delivery process. The pipeline will initiate the build from version control process, ensuring code merges and after completing all the steps, the package will reside in the respective Orchestrator (Stage / Prod) automatically. It will help to take care of robot delivery process steps such as compiling & creating the package, uploading it to Orchestrator etc., in a seamless manner.

CI/CD pipeline allows you to automate robot delivery process. It will help to take care of robot delivery process steps such as creating and uploading the package to Orchestrator in a seamless manner.