UiPath Reviews

The solutions or test cases where we have used UiPath are:

1. Formatting different types of files (.csv, .dat, and .xls) to .txt
2. Reconciling data between different applications
3. The direct-debit application process

We deployed the solution inside a virtual machine in Cloud.

The organizations where we have implemented the UiPath solution have seen reduction and savings in time and FTEs. Processors were able to focus on other tasks and have the robot work on mundane and repetitive tasks.

The most recent organization is happy with the output and is planning to have other processes automated.

The most valuable features of UiPath are the drag and drop activities.

Since UiPath offers eLearning it makes it useful for developers to learn the basic activities used in automating processes.

UiPath also offers documentation and forums that help developers during debugging.

The product should be made more friendly to non-programming users, as some functions require a background in VB.NET.

UiPath should also add activities for the Excel application like formatting Excel columns and rows.

We have been using UiPath for ten months.

The workflow was able to handle the exceptions gracefully. The solution followed the ReFrameWork template of UiPath.

The solution is scalable as we are able to reuse the workflow.

We have not reached out to customer service during the implementation.

From the start, we used UiPath in automating processes.

Installation of Studio is straightforward but the Orchestrator, we don't have visibility as the client's IT team performed the installation.

The implementation was performed by the in-house team.

We don't have visibility on the ROI, just feedback from the client to say they have seen reduction and savings in time and FTEs.

We did not evaluate other options prior to implementing UiPath. It was decided and chosen by the organization and recommended by the Business Analyst.

We have created a workflow that is dynamic and reusable.

Overall, UiPath Studio is easy to use and navigate.

The primary use case is for a medical claims process automation using UiPath RPA.

• Streamlined the medical claims process. It reduced errors by 30 percent.
• Improved user productivity by 50 percent.
• Turnaround time for claims payment has been reduced from 120 days to 30 days.

It is easy to manage the robotics environment with Orchestrator, including scheduling and reporting.

Optical character recognition for hand written documents could be improved.

I'm not using it myself. I'm working around it with consultants. I am in network IT. I have seen the product at work and tried it myself. It is sort of easy to use.

From our main systems, it integrates a platform for our citizens, sending them notifications.

We have released on time from the staff for IOPS, which is what they are going to focus on. We are leading in our country in this area. It is supposed to change our thinking about how we should work with newer process and how systems are thinking.

You can integrate it to do many things. We have a lot of different data that comes into it.

Studio needs to be more user-friendly, maybe it could be integrated with an AI.

We want to see more ways that we can use the product. We want to see more actual cases.

We haven't had that many problems. We have had more issues with the products integrating into it.

It does what it is supposed to do. We haven't had any complications in the less than two years that we have used the application, which is quite good.

Scalability-wise, it should meet our needs going forward.

I am planning to use the UiPath Academy going forward.

The application setup is easy, but the process can vary. 

We only use the technical support when we were renewing our license. The process could be easier, as there are a lot of steps.

We are set up for annual licensing and will be taking the time to renew.

Gone are the days when you have to deploy 100s of people for repeated tasks. We regularly update invoices of different channels and merchants to our workflow. Capturing each invoice requires some human attention. There are chances of using OCR or text-based extraction of invoices. We easily automate each type of invoice extraction to our spreadsheet. This reduces one hour (max 1.5 hr) of 100 employees in our organization.

Majorly replacing all the remote freelancers who were doing the copy-paste work for us to fetch invoices at low pay; they are now set free. We do not hire them, rather our UiPath robot does that, thus reducing the cost.

The best part of UiPath is you do not need to check anything manually. Whatever error comes, the robot automatically gets stopped rather than infiltrating absurd values in the next process.

We have deployed the technology for six months. We are facing a major challenge in front of us. The invoice automation can only be done when the invoices are on the website. Usually, we fetch invoices from partner websites as PDF. Thus we are doing extra work of converting the pdf to RPA readable file. If we had dedicated channel of PDFs then it would have worked but it is not like that. 

We are a financial shared services office; we have been using UiPath in our daily process. This is the most useful tool.

This has helped us to automate most of the jobs. Even if it has more control and manual works, this works well.

• The recording features, basic Citrix, OCR, and desktop recording which gives good results
• OCR is at its best.

I'm from Chennai, and here I couldn't see any classroom training or academy which offers the classroom course.

• Invoice processing
• Claims processing
• Vendor onboarding
• Product fitment analysis
• Database monitoring
• Interaction with FTP and analyzing XML files
• Underwriter quote submissions
• Automating reconciliation of reports.

Ease of implementation.

Extensible framework assists in plugging in required components from existing scripts, and in implementing intelligent automation utilizing the best in class machine learning algorithms.

The framework provided has good recovery mechanism and exception handling capabilities built in. It can be customized based on the requirements and provides an easier start for implementation and to showcase in a presentable manner.

• Excel automation: It has activities related to most of the functionalities in Excel and makes life easier for anyone who spends a significant amount of time in Excel for analysis and reporting.
• PDF automation: It performs well in reading native PDF documents.
• Email automation: It integrates well with IMAP, SMTP, and POP3 apart from supporting Outlook and Exchange which are used extensively in large corporations.
• Web automation: The use of UiExplorer in extracting the properties of web elements and easy modification to improve the re-usability of workflows.
• Windows automation: It works well with Windows-based apps for updating information received in Excel spreadsheets and to capture the information and reports generated in the apps.
• Mobile app support to monitor bot health and status of the workflows.
• OCR integration works well with third-party engines.

• The core product is yet to include machine learning capabilities. 
• Focus on solving domain-specific high volume use cases to target the major pain points in each vertical.
• Simplify the knowledge requirements on .NET Framework for implementing complex automations.
• Including additional visualizations on the reporting side would help. 

A user receives data from an Excel file and then enters the data in the internal website/tool to calculate the price. So we automize this process using UiPath.

First, it reduces the typo mistakes; we are certainly sure that the data entered into the system are correct. Secondly, it saves a lot of time. Users don't need to type in data anymore and spend their time analyzing the process. Thirdly, our colleagues don't need to do much of the "monkey work" — typing. They just spend time controlling the results of the bots.

The training platform of UiPath is very good. It helps the business user without prior experience in programming to automize the process by themselves. This is a good approach because they are the ones with a great overview of the process and know how to control the quality of the results as well as foresee what the potential issues could be.

Also, it can work on everything. UiPath is like a VBA for Excel but can work on all applications (MS Office, SAP, web browser, etc.). So the potential for automation is nearly limitless.

• Compatibility with old systems and Java Script-based websites could be improved: During my project, I sometimes encounter issues when Uipath runs too fast while our old internal website (which was written in Java Script, I believe) is running slowly and we need to handle this type of error. Besides, some function of Uipath "Select item from list" does not work with our website (not compatible).
• More practical projects to be included in the training of UiPath Academy would help the business users to get used to executing the real projects (e.g. technical issues: why do we have to write the script this way, what errors usually occurred? and also project management - setting up timeline for the project, etc.)

This solution is used widely in different areas: from accounting to product order processes. 
I solve different business problems, like processing orders, collecting information, etc. There are many benefits: It's easy to use, exception handling is easy to handle, and flowcharts can be implemented directly.

UiPath has improved our organization by its ease of use, practical solutions to complex problems, and flexible working environment.

I found flowcharts most useful in UiPath. It is the best feature in UiPath, and you can easily create even complicated workflows with just a couple of clicks and dropping built-in activities without coding. You can also implement a state machine; which is also a great feature. Passing through states makes it much easier to design the main part of your process.

What I really don't like is some bugs in UiPath appearing from nowhere. In the new version, I see most of them, like when you are trying to change your variable name, it gives a very long error, etc. But still, there is one area not fixed: importing Outlook templates. 

I had an issue with implementing ".oft" files reading with "Microsoft.Office.Interop.Outlook" library. It was a real disaster; I couldn't define anything. I spent quite a lot of time implementing it, and I reached the conclusion that it is very close to impossible to use. They should direct activity for outlook messages and "oft" files. Except for that, UiPath is a great tool for automation. Also, debugging is not very convenient. It is hard to debug with UiPath if you are running a very big process.