UiPath Reviews

We work in the healthcare industry. We are trying to establish a use case for our company to speed up our processes. Because with FDA regulations, there are a lot of processes to follow. There are a lot of phases of implementation to follow. For example, if you want a drug for cancer, a lot of time is spent, but it takes more time to release to the market because of all the manual labor intensive work which is happening. 

Therefore, I am working with legislators and the FDA to see where we can cut paths. There's a lot of scope for automation. UiPath is one of the best product for this.

UiPath is user-friendly, so when we are working with the customer, if they want something immediately they will jump in. We don't have to give the level of estimation, then how much price will be (quote) at all. They don't really talk about the price or the time. They say, "There is a problem," and they are very excited about solving that problem. This excitement is good, and that's what our CEO has always said, "Immersing yourself is always important."

Everyone feels positive when they want to talk about RPA and what they want to do. When we go and explain how easy and adaptable it is, people are happy. It is not complex, because we are simplifying the way how they use it. 

If you're able to discuss and give the layout and the architecture purposeful meaning along with the training, then people can adapt to it well.

It is easy to implement and use to provide training to people. With a lot of other tools, it is more about scripting. Whereas with this solution, it has a more hands on GUI-based feature.

It is easy to use and quick to install.

With every product that we have, there are still improvements needed in some areas. There are certain areas that we need to see improvements: performance, efficiency, and complex environment. We need to work with the product manager on these, and say, "Now that everything has met the industry standards, there's a way to go."

We need to be able to span across a bigger complex network. Right now, the decision-making is based on a five step rule. It would like to see this increased, so we can take on bigger productions and work more efficiently. Also, the performance has to be improved in some areas.

For the last three years, they have been very aggressive. They have been progressing nicely. So far, the stability has been good, because of the continuous product implementation. There has been a focus on the product and everything working. 

The people who started the company are still with the company, and this is a good sign that there is stability. This can be seen in the financial markets. 

Scalability is one of the nice features, because they're able to come up with the UiPath Orchestrator. They have improved this with the 20.18.3 version, which has a lot of good scalability features compared to the previous one. Right now, it is scalable, and there are always new use cases coming out. The more use cases that we pump into the product development team, the more scalability that we will see and more features will be added on, because they can only think of what they have on hand.

Being a partner, I have my own team that I work with.

The UiPath Academy RPA training is good, but we have a good geek squad. Our people have really gone to the community research and downloaded it, so most of my team is self-learning. However, the support people are always available, if needed, when we need some help.

The initial setup is pretty easy, because now my team has been implementing it a lot. For more than a year, we have been a partner. We have been doing a lot of PoCs.

Overall, the steps, documentation, and information are pretty straightforward when it comes to the product, so there is no ambiguity.

The staff that we need for deployment and maintenance depends on the complexity of the process. Typically, we start with a couple of people for the PoC. Depending on how many parallel approaches we have to do, we may increase to four to five people. With that number, we are able to create a good sizable environment and solution. These staff members would be responsible for the architecture, one would be the lead developer, and another would be the functional expert to understand the processes, then there could be a couple of people helping in the development environment and doing all the testing to make sure whatever they have implemented follows the process.

We have use customer support for implementation of the projects because the team is really good.

Some of the return on investments are quick. Because some of the processes that we have implemented, a person who does manual labor over two weeks will see a reduction in hours. Thus, that person is already focusing on some other intellectual work. 

Our goal is not remove all the people, but repurpose their work time in better ways, therefore these people can work better and their throughput is good. So, customers are able understand ROI very quickly.

Its performance benefits are the reduced time, making it is very efficient. If someone is taking two weeks, and now it is takes them ten hours, you already have a performance benefit. 

In terms of product performance, there are still things they need to work on.

I would rate the performance benefits at an eight (out of ten).

If you want to do a demo trial, it is a 30 days free. 

However, the community edition is completely free. Then, people say, "There is nothing to lose, let me try it."

Automation Anywhere and Blue Prism are competitors. They have been in the industry a little longer than UiPath, which is just coming up. One good thing about UiPath is that it is really capturing the market.

1. The company culture: We are an extended family, not just a partner. Their entire team is available to us.
2. As a product, it is really coming up in the market with a different architecture, most which is .NET and C#. For a lot of my developers, it is easy condition for my team to learn more quickly. We have not really used the Academy. My team was able to learn on their own. 
3. The product has more in terms of supportability, predictability, ease of use, and overall culture of organization.
   

We have not really seen anyone moving from Automation Anywhere to displays or some other product.

Our customers want to see:

• Whether it is a viable product.
• Does it make sense for their business. 
• If it does makes sense and are there other companies, why should they go with UiPath?
• What are the benefits compared to other products? 
• What is the benefits that it is giving to the customer?

If I can layer all of those decisions, then I have walked them down the path of the realization of ROI and why they should be doing UiPath. So, it is an easy sell.

I work in the healthcare domain. We've automated a lot of financial and invoice-types of business processes, bringing in efficiencies in terms of saving time spent by field representatives in processing requests.

The time saved is anywhere between 10 to 15 minutes, on average, because a human would have at least that long, and up to 20 minutes, to do these tasks, while a bot takes just 4.3 seconds, which is huge efficiency.

Also, the time to market is very quick compared to other applications out there. RPA is very quick. My team has produced bots in as little as two days, from discovery to development and go-live.

Performance benefits rate a nine out of ten, because of a Citrix automation fragility concern. Otherwise, I would have given a ten out of ten.

It's easy to use and it's easy to host.

The most valuable features are the ease of use and the UI. It's much better compared to all the competitor applications out there. I've literally used all the applications that are in the market, and UiPath has been, by far, the best.

Another prime factor is that it scales up horizontally and is on the cloud, on AWS cloud. That's where we host our processes and our services. That connectivity feature, the availability, is a primary winning element.

The Citrix automation - the way that it's fragile right now - if that could be made stronger and more stable, that would be icing on the cake for UiPath.

When it comes to stability, it all depends upon what kind of touchpoints it has with third-party applications. Citrix automation is always a little bit fragile compared to non-Citrix automations, especially with UiPath. But I'm sure the 2018.3 version, which is going to come out, is going to fix that. I'm hoping that it fixes the issue.

Scalability is tremendous. My organization has been pretty happy with the amount of scalability that it has provided. One bot can literally run multiple processes, and process millions of records.

I feel customer support can be improved a little bit. I raise service requests day in and day out with UiPath. Compared to the competitors, support is very good. Still, the average SLA is around three to four days, which I think can be reduced to one to two business days. It would be very good if UiPath Support could do that.

I was involved in the initial setup: discovery, setup, and development stabilization, end-to-end. It is straightforward. It's a no-nonsense, plug-and-play type of application where you don't have to code something for it to start up and work. It's already available there. All you have to do is build flows in Visio or BPMN flows, as they can be directly consumed by UiPath. And then the solution is working.

It costs much less and it does much more than the competitors' solutions.

The only solution that is close to UiPath is Automation Anywhere.

There are three points that I always have my clients identify to determine if this is a good approach for them:

1. Does your process have a lot of manual steps involved?
2. Are they repetitive in nature?
3. Are they rules-based?

If these three are checked off as "yes," then they qualify for RPA. It's as simple as that.

Regarding UiPath RPA Academy training, I myself am certified by UiPath at all levels of certification which are offered by the LMS system. All my workforce is certified by UiPath as well. It's very intuitive and very easy to follow through and complete the courses, compared to the competitors.

In terms of staff required for development and maintenance with UiPath, for a small to medium-scale bot, we have around two developers working at any given point in time. Developers, here, also play the role of testers because it's an Agile implementation and a single person wears multiple hats. So there is one business analyst, there are two developers, and that's pretty much the team. We are very lean.

The important criteria when selecting an RPA vendor are the scalability, stability, and hosting and licensing costs. Hosting and licensing costs come at the end of the list because people are more concerned about whether the solution works or not. They always want to see a proof of concept and see that it's working. Then they get that sense of trust.

I've been using RPA for almost five years now, pretty much from the time where North America did not know what RPA was. UiPath has stood out and exceeded expectations, always. It's the best. Hands-down, go with UiPath. Don't even think about others.

I work in finance, and we have diverse use cases for UiPath.We use it for invoice processing, ML detection, and tag categorization of items that we sell. 

UiPath Action Center is very valuable. 

We ran into issues during the upgrade. It was not warned before. 

I have been using the solution for five years. 

UiPath is stable. 

The product is scalable. 

We get good resolutions when we raise issues. 

We did on-premise deployment and had to check load balancers, SQL server, and Redis. It took us about eight to nine months to get into production, which was cumbersome. 

We have seen millions of dollars of ROI. 

UiPath is expensive. 

Our business objective in automation implementation was to eliminate manual labor. Initially, we started with RPA. The finance department has a lot of manual work, including prescriptive things like driver's licenses and transcribing. We started using RPA to gain ROI.  

The use of automation has enhanced our accuracy. 

UiPath has helped us save 100,000 hours, which translates to millions of dollars saved. 

I rate the product an eight out of ten. 

I use UiPath for invoice processing. We download all the invoices from our application and then send them individually to the respective customers via email. This involves email automation and automation of the user interface.

Building automation with UiPath is easy. When compared to other automation tools, UiPath offers a more user-friendly development platform.

It enables us to implement end-to-end automation, from the basic extraction of data to the complete uploading of data to the respective applications.

UiPath's User Community is excellent. Whenever I encounter challenges or need information about new developments, version changes, or anything related to UiPath, the community is always there to help. Therefore, I find the community extremely valuable.

UiPath can be a useful tool for anyone. It doesn't require a separate environment or the need for a developer. It is beneficial for anyone dealing with any system. Therefore, I believe it can serve as a regular daily process tool, enabling users to automate various tasks effectively. There are numerous possibilities and applications with UiPath.

In my early days of entering this field of development, I completed the UiPath Academy courses to gain a comprehensive understanding of the interface, the approach we should take, and how to utilize the portal functionalities that UiPath offers.

UiPath has been instrumental in reducing human errors by 99 percent in applications that are maintained correctly, particularly in activities such as typing. There are certain tasks where humans are prone to making mistakes while working with applications, but UiPath ensures that such errors are eliminated. Initially, I had some doubts about UiPath's ability to extract data from PDF files, as the UiPath OCR engine seemed to have limitations. Consequently, we started relying on ABBYY FineReader for this task. However, we are now exploring UiPath's UI for document understanding. As a company, we have already developed around 200 to 300 templates using ABBYY FineReader, making it challenging for us to transition entirely to UiPath document understanding at present. Nevertheless, we are considering the shift because the early versions of UiPath were not very efficient, and we couldn't fully rely on it for data extraction. However, with the recent integration of Google Vision, UiPath has significantly improved and is now providing better results in terms of OCR technology.

The user interface is the most valuable feature of the studio version. It allows us to develop all activities and create custom activities as needed. Additionally, it seamlessly integrates with the latest technologies, such as AI, making it very helpful, even for integrating ABBYY FineReader. Users can extract data from the time scripts, which is also a project involving data extraction from all PDF files.

The UiPath Community does not provide version control for the community edition. Let's say I'm currently using a specific version, and then it automatically upgrades the community version to the latest version without the user having the option to decide whether to update or not. Consequently, we cannot use the older versions in the UiPath community edition.

I encountered some issues with my local machine. I created one of the bots using a different version from the community variation, there were problems with compatibility between different versions in UiPath. While those issues used to exist, currently, it has been a long time since I last modified any of the workflows and migrated between servers and my local machine. I'm not entirely certain at the moment, but previously, there were instances where a particular activity in one version would not work in another version and would result in failure. Additionally, sometimes the select task would not identify the select areas in the actual application, even though it worked on the validators. These scenarios are rare but they do occur.

I have been using UiPath for almost two years.

I would rate the stability of UiPath ten out of ten.

I would rate the scalability of UiPath eight out of ten.

The initial setup is straightforward.

The licensing fee is moderate and is based on the volume of tasks for which we use UiPath. The cost is satisfactory.

I would rate UiPath eight out of ten.

Currently, we are handling approximately 20,000 units of data on a daily basis. Our focus is on efficiently processing this data and integrating it into the scaled servers. We utilize the scale servers for data connectivity, verification, and storage purposes.

We are currently not using the AI functionality, but our company is anticipating a new project. The assignment of this project will happen very soon, and the company is considering the use of AI for it. However, this decision will ultimately depend on the user and the environment. If we determine that using AI functionality is necessary, we will integrate it into the project. At present, we have not encountered any users who explicitly require AI in their business logic. Therefore, we are not utilizing AI at the moment. Nevertheless, if any future clients request it, we will be prepared to integrate AI functionality accordingly.

Our organization has started using automation with UiPath. Before implementing UiPath, everything was done manually.

If the initial development is done correctly, then the maintenance would actually be significantly reduced. As a developer, we need to ensure that the code is always reviewed by developers, and they should always be available for this purpose. If the initial development is not carried out correctly according to the requirements, then imagine the consequences in the future. The development might need to be revisited for up to 15 years, or at least five years. If it is not done that way, the maintenance cost would be very high because the business processes keep changing. Therefore, to keep the system functioning well and the applications up-to-date, as they are not static, we need to continuously maintain the code. For instance, in the past six months, we've had to make two changes to the application we are working on. Many alterations occurred, such as UI element changes, shifting locations, and complete interface and navigation changes. Hence, it's essential for developers to always keep the code protected and up-to-date.

I recommend conducting a proof of concept using UiPath to ensure that the budget and return on investment are sufficient to implement the solution within an organization.

I'm not currently using UiPath, but in my previous organization, which I left seven months ago, we had a complex trading application that included a web form and a Windows form. And on the Windows form was an Electron framework. If you want to run a web application inside a Windows application, Electron is a bridge between the web application and the actual Windows app. Because it was a complex application, it was not very easy to automate. That's where UiPath came in. It perfectly fit our automation testing scenario.

Before UiPath came into the picture, we were planning on doing automation testing with Selenium. The test plan with Selenium was going to take about three months. When UiPath was introduced and we started working on it, we completed the whole automation, end-to-end, in about one and a half months. It saved us that much time. And we made sure that our product was delivered with the required quality and that we did not compromise on that.

Because UiPath is SaaS, we were able to automate everything in a very productive manner. We were able to cross-verify all the flows and all the functionalities. And UiPath didn't require a huge amount of setup. It runs on minimal requirements.

In terms of human error, we saw a reduction, of course. It's not possible for a human to catch every error when new functionality is built. With UiPath automation, we were able to analyze errors right away and resolve them.

Another benefit was that it freed up employee time. It did a lot of the work by itself. The user only had to make sure that the correct workflow was involved and he could just sit back and check that everything was going correctly. It probably saved us 45 minutes daily.

UiPath makes you more productive because it comes with a lot of drag-and-drop features. You don't need to know the APIs to access particular elements on the screen. You can just drag and drop and define your actions and go ahead with the workflow. You can focus on the workflow rather than learning about the APIs, which is what happens with Selenium and other automation tools. That is one of the most beneficial features of UiPath.

I don't know if I was doing something wrong, and I did get assistance from the UiPath guys on this, but sometimes UiPath wasn't able to find an element on the screen. But that's what UiPath is for, and we wanted to make sure that our workflows were working correctly. Sometimes it was able to find an element and sometimes it was not. UiPath support did give us a solution, but it was not helpful enough.

The issue that I mentioned earlier, that sometimes it wasn't able to find the elements, was the only issue I saw with respect to UiPath. Otherwise, nothing was breaking and nothing was problematic on the UiPath side.

They were very friendly and they tried to be very helpful, but they weren't able to solve the issue I raised.

Positive

The version of UiPath that we used involved a direct installation. We asked our in-house team to get it installed because we didn't have the permissions to install software. They installed it in our system and we started using it right away. It was very straightforward.

I have worked with Selenium, which is an automation tool. That has quite a learning curve, but with UiPath it only takes you one or two weeks to get started. Once you're familiar with the basic tools, you can start writing a workflow. It is straightforward; nothing complex.

I never did the UiPath Academy courses because we had senior team members to help us and, in that company, we had a "learning playground" where we could go through the slides directly, without going through a whole learning process. We were then able to start our work right away.

UiPath did a good job. Before going into production, we needed to make sure that every test scenario and every case was handled. That's where we took advantage of the UiPath. We would run UiPath again and again and there were no breakages in our code and nothing was falling apart before going into production. I was working for an investment bank and every record was important.

I work at a financial firm where we do trade settlement activity. We are using UiPath for cleaning up data, doing reconciliation, and finding where the trade breaks and trade files are. It helps us lay the groundwork for the value add work, which comes later.

It allows us to grow our business. The use case that we have is a huge time saver because we do not have a lot of volume right now. We are looking to sell part of the business and get more clients onto it. The only way we could do that or even open that door for possibility is to automate and go through a lot more volume. 

Our teams are under huge pressure because trade volume has gone up over the past year. UiPath is just getting us back to the status quo and then also opening the pipeline for more volume to go through. We have a very strong program that encourages people to get trained up on tools. 

StudioX is going to be a big game changer for us. We found with the other tools that we use that as soon as we put UiPath in the hands of everyday users and ops users, they will be able to quickly learn it. This will make a big impact because we will get big volumes and projects coming through.

UiPath has done a good job coming up with the broadest use cases. However, I would like to see them dive into more industry-specific use cases. For example, checked OCR and brokerage statements are common. Anything unique to the financial industry would be useful for us.

We have using UiPath since February when it got brought into our team. We just had our first box go live about two weeks ago. We have had three go live so far; one using StudioX and two using Studio.

So far, I haven't heard any issues. We are always going to expect issues, but so far so good and I hope the stability is good. Alteryx had issues at times, which created some pretty big problems. Hopefully, UiPath will not do that as much, because we are expecting to lean on it.

I have not used them directly. 

It was not so much a switch for us. We are still using Alteryx. UiPath is a much better automation tool than what we were using before because it was self-service. We didn't have to have our COE build it and related solutions for us. We have similar functionality with Alteryx. Anyone can learn it and start building and go through our governance process. Doing so, they can have a huge impact on their team.

We are a large company and the initial setup took our COE quite a few months. However, I believe their experience was positive overall. A lot of the issues we had were internal and concerned how we were going to do our governance. We were very strict about that. 

Getting people access was easy and so was learning to build. Everything on the UiPath side went smoothly.

We're a mature automation team. Over the past four years, we've delivered well over 150 FTE. We're always looking for new tools and to pick up some of that automation that we couldn't do before. 

UiPath has helped with data scraping and plugging into websites and combining that with Alteryx. We can attack 90% of our use cases now. We can not deal with the other 10% for internal governance reasons and not so much capability.

The three use cases we have implemented with UiPath have saved about half an FTE. 

I know that the reason we went with UiPath is because it is a lot cheaper than the other vendor we were using. It is of a better quality as well, but it is less expensive to run on an ongoing basis. 

I'm not sure if we evaluated other options. My team does not look into the suite of options. We have a separate COE that sets everything up for us. We are tasked with implementation. 

My advice is to first build a good team that you can trust. Because great tools are useless if you don't have any builders or people that know how to use the tools. That is what we have been focused on. Also, have very specific support for your team.

In terms of product testing, I use it in the product with the test suite to mount the test manager and then follow with the requirements. After that, I create the test cases and I'm running them on different platforms on the web so that I can proof back from the web with test suites.

I use the different tools of UiPath. However, in the future, I’m hopeful UiPath will help us to expand into different countries. right now, I use it personally. Soon, the entire company will be using it as well.

The automation of the cloud offering helps to decrease the solution's total cost of ownership.

The document understanding is great. I interact with different documents of people. The IDs of one are different from a document or a PDF. For example, our contracts, et cetera. It can understand the differences.

I’m not quite sure about the ease of building automation using the solution just yet. It seems to be moderate. Not too easy or difficult.

The solution has helped our organization save costs. It’s likely saved us about $10 million.

UiPath has helped us reduce human error. That’s had a partial impact on our business. Our techs understand the different types of processes and competencies it can help with. Regular users cannot see this just yet.

It has freed up employee time. It’s allowed for a focus on higher-value work. Employees seem happier. It’s an easy tool to use and deploy.

We’ve used the UiPath Academy courses. All employees take the course and learn about it. You still need more education afterward, however, the biggest value of the Academy is the knowledge. I've got people who are new in the company and I can just say "take these courses." It's accepted by everyone as part of the process.

The graphics could always be improved.

I've been using the solution for three years. 

The stability of the solution is good. UiPath has a different release each year at the moment.

The scalability is great. You have a manual so you don't have to do the courses. You can read through it.

We have about 200 users at this time. We have different areas in the company that uses UiPath. For example, the administration uses that tool. You have a test suite and you can have development using the UiPath Studio as well.

Technical support has been great. Whatever my query is, they are able to answer it.

We did not use another RPA solution before UiPath.

The initial setup was straightforward and simple.

The deployment took about one month.

The pricing and licensing have been great.

We did look at different automation tools before choosing UiPath. We looked at Blue Prism and Automation Anywhere, however, we ultimately chose UiPath.

The UiPath Academy courses were a big selling point. Also, its ease of use. Automation Anywhere and Blue Prism were so difficult to understand. UiPath is more interactive and it's more visual.

We're a UiPath partner. 

I've used both cloud and on-premise deployment. Right now, I am using the cloud. 

At this point, we do not use UiPath's apps feature.

We have not used the solution's AI functionality in our automation program yet.

If I were to advise anyone on using UiPath, I'd let them know it's easy to use. You have manuals and courses to help you navigate the solution. The new releases make it so that it continuously gets easier. 

I would rate the solution at a ten out of ten.

We're still building up the program, but right now our primary use case is for report review. We're looking to branch that out more.

It's reviewing reports. I worked for a bank and there are reports of transactions from the previous day. UiPath was looking for anomalies for fraud and things like that.

It's still very early on but we have caught a few instances of fraud that we would not have if we weren't using UiPath. 

UiPath has reduced human error. We're very early, so it's not a big impact, but we did find a few instances of fraud that we would not have found without it. 

We see time savings for our users in the sense that they now can do more tasks that should have been done all along but weren't getting done. That's more where the gains have been this far.

I like the whole ecosystem. They're not just looking at the automation tool, they're looking at automation from end to end. 

It's pretty easy to build automations. I have a coding background so it's not particularly challenging for me to use Studio, but for a person who does not have that coding background, I think that the Visual Builder guides you through the process pretty easy.

UiPath Academy is a good training program for people without that coding background. It's good to get them into the mindset of how exactly flows works of automation.

The Academy offers us familiarization with Studio and how it functions.

The API integrations need improvement. They should build a better framework for the ability to integrate with other external APIs.

I have been using UiPath for less than a year. 

I would rate the stability an eight out of ten. 

It's pretty straightforward. It either runs or it doesn't. Occasionally it does crash and we've had to restart services and whatnot to get it going again.

We haven't been using it enough to see how it can scale. 

There are two ITs who use it in my company.

We have plans to increase usage. 

We don't really see our staff as being good candidates for citizen development. There are a few that could, but we do plan to expand out into other departments as far as gathering ideas and implementing processes for other departments.

Their support is pretty average. It's not good or bad. It's off-shored. There are always difficulties with cultural differences and language barriers. They know what they're doing but sometimes it takes a while going around in circles to get the question that you're asking across. That's pretty normal. Most companies are the same way. I would say all companies have huge room for improvement there.

The initial setup was pretty straightforward. It was easy. The installation instructions walk you through the process. We didn't run into any problems. It took less than a week. 

We also looked at AntWorks and Blue Prism. We went with UiPath because of the maturity of the product that seemed far more mature than its competitors. The product seemed more thought out.

Based on our experiences, I would say you have to have employees that are dedicated to doing this. This can't be done as a side project.

I would rate UiPath a nine out of ten. Nothing is completely perfect. The stability of it could use a little bit of improvement. The support is not great. UiPath is very good, but no one is perfect.