UiPath Reviews

Primary use cases involve the following automation environments and processes:

1. Oil and Gas Domain: Automation of various applications specific to this domain such as Gopher, Tow, Toad, Excel, and various browsers.
   
2. Finance Banking: Here we have to deal with various legacy applications with a lot of PDF and Excel-based automation. UiPath comes with a lot of reliable solutions here.
3. Healthcare: Automation is a big challenge because the Healthcare domain is not a simple thing to automate. The ML extractor and Intelligent Automation activities are best to use here.

UiPath has improved the reputation of our organization in an exceptional manner. Our clients are happy with the solution that we provide them as a part of the automation. They are happy that robots are there with a helping hand, where they can learn RPA and give some time for their personal life as well.

UiPath helps them with saving their time, FTEs, and ROI.

Following are the most valuable features of UiPath:

1. Every month, there are new features released. These are all next-level and can disrupt the automation industry.
2. Vision for RPA and ML work together including ML skills, ML extractor, and Python activities.
3. UiPath is easy to use with very simple drag and drop functionality that allows you to automate processes without knowledge of coding.
4. Covering automation in all possible applications including SAP, G Suite, Salesforce, etc.

Possibility of improvement:

1. Exception handling and exception details can be much better and more user-friendly.  Many times, details of exceptions are not understood by somebody with a non-coding background. Example "Object Reference not set to instance of object", this is the exception message that we got and log from UiPath. For a developer it makes some sense and meaning but for a SME or User it is very complicated to understand the meaning if this exception
2. User interface in the coding area can be better and more compact: Some times expanding seq. cause the code to look very big and difficult to undertsand the scope of container

I have been using the UiPath Platform for automating various processes for the past three years.

It is extremely awesome. customer service/technical support used to assist with in an hour of raising services issue ticket on portal

Automation Anywhere

We switched to UiPath as it provides a lot of functionality than another tool in market

At Forest Service, we have a massive onboarding season. Because our primary mission is to combat forest fires, we have a huge intake of firefighters that we hire every season. Because of that, there's a lot of onboarding material that needs to be processed through HR, literally tens of thousands of people in such a short amount of time. I can see, potentially, RPA being able to help with some of the manual work that we do.

It's probably the best bang for our buck, but there are certainly other use cases potentially. That is the area that I'm more familiar with, though.

UiPath can batch process a lot of the hands-on manual work that nobody wants to do. I think that's probably its best value. That said, it does kind of highlight the need for standardized processes, which can be challenging at times, specifically in our space. Just having formalized documentation about what the end-to-end process should be is key. Once that's standardized, then it's a lot easier to leverage UiPath for automation.

Having looked at other RPA software, I think UiPath is the most user-friendly. At the same time, it's robust enough to customize and get into the source code. It's accessible, but also has enough features for more hands-on developers to be able to do what they need to do. From the two that I've seen, it was the more user-friendly one.

I have used UiPath's Academy for some of the foundational level training, not the more advanced ones. I think I had some feedback at the time. It's been a few months since I've taken it. Overall it was pretty good.

I feel like it's pretty good as it is. One thing I would change is when you're nesting certain workflows, it can get a little complicated as you start getting deeper. For example, if you have multiple blocks that need to live inside each other, and you're using a library to drag stuff or just insert it, it can be very challenging from a visual level to see what level it's in or how deeply nested it is. It's hard to roll it up into a parent level display. So, that's a little confusing sometimes. I guess, if there's any way to improve that, I think that would be helpful.

I think UiPath uses VBScript. If there were some kind of library of common things that developers could use, that would be helpful, but it's not a big deal. You can just Google that stuff. Making something like that accessible would be nice, but I don't think it's crucial.

The big question on my end is just how to scale and keep things stabilized. This is such a new technology for us, that there's a lot of questions around it. I think, being able to answer that would be helpful. I don't really know the answer.

I don't know about technical support. We were talking to a developer that was helping us at the time just to walk us through. Our experience with the developer was good. They have a very knowledgeable staff. They're very eager to help us figure stuff out. All in all, it was a positive experience.

The setup, at least from the local side, makes sense. This could be just more of my experience since my expertise in UiPath is not as high as it could be. I'm not super familiar with how Orchestrator is deployed and managed, in terms of multiple bots and scheduling, but that's probably a limitation more on my end then with UiPath.

We are currently in the research stage. It's more like proof of concept work. Right now, it's really about convincing people that this is a technology to look at and pay attention to. We are trying to convince the people with the authority that this is a good way to invest.

I have local test environments that I've used personally. At Forest Service, they're very visually oriented. If you talk to them about it, they won't get it. They need to see it to believe it. So, I've been trying to do that locally in my own environment. I have been building use cases that I think are parallel to what we're trying to do, to demonstrate the value.

We looked at a couple of alternatives. Automation Anywhere was one of them. I haven't looked at the other ones, since we chose UiPath pretty early on, having heard about them previously. We also considered some others like Pega and a few others.

Automation technology is non-existent in our company currently, but definitely something that should be leveraged for. I think there's a lot of value in being able to free up people from doing small repetitive tasks and just be more strategic focused. The challenge, really, is just convincing people that they're not going to lose their jobs. We need to show them that we're freeing up their time to be more valuable. The challenge is just educating people about what it actually is.

I would rate this solution as eight out of ten. I think it's going a lot of places. It's definitely more advanced than some of the other ones that I've seen. UiPath is probably the best one that we've seen so far.

My advice is to make sure you have your processes documented before you try to fix something that can't be fixed through robotic process automation. At a fundamental level, your organization needs to be ready for it. It's not a magic bullet to fix stuff that's confusing at your organization level. But, if you have it straight and documented and you're doing high volume amounts of it then you should use this to free up people's time and make them do better work. I think it would be useful.

We use it in our robotics lab to deliver front and back office solutions for the clients. We're a BPO CRM organization, so there is a huge amount of opportunity, not just internally as an organization, but for our clients as well. We use UiPath as a delivery method to find reductions in costs and the like, year on year.

I would rate the performance benefits a very strong eight out of ten. You have to make sure that you pick the right processes that you're looking to automate.

For me, the biggest feature is that my developers love it. And if my developers are happy, then I'm happy. We're totally agnostic and we use multiple providers. But the developers definitely absolutely adore the product.

The speed that in which it can be deployed is something I really like as well because that cuts down on delivery times. I also like the ease of use.

I like the fact that we can program our own .NET to plug into it and there are APIs for multiple different solutions, and the convenience of artificial intelligence and machine-learning and those types of capabilities as well.

The new release broke everything, so I'd like to see that not happen next time. All of our automations broke. It happened to one of our centers of excellence. They just upgraded, pressed next, next, next, and probably didn't really go for the due diligence that we put in place, which is to do a controlled release.

I'd also like to see more machine-learning functionality. I'm really excited to see what's actually on the agenda. There's some really strong stuff about machine-learning being adopted. Unstructured data, robotics being able to read unstructured data, is really one of the strong cases for us. That's likely where we'll be going.

It's phenomenal. The stability is really good but some of the releases have been a little shaky.

To scale it is very easy. But you need to know how to scale robotics, it's not just deploying one on a PC somewhere. We do it on VMs in a data center which is fully monitored by a help desk. We know how to scale bots. It is very easy to scale, if you know what you're doing.

Support has been very good. One thing that the developers are always talking about is the social networking side of it, whereby the blogs and things like that are ongoing. They really like that, that we can actually find a lot of problems already solved within the community and take solutions from there. And the ticketing system is very quick as well.

We've been involved in RPA since early 2014. In 2014 we were using one provider and then we moved into another provider as well. But then we started to look at UiPath and the way it was performing in our proofs of concept. We felt that with those three providers, and our bespoke solutions as well, we were able to pretty much handle any project that came at us, depending on the infrastructure type, and the applications that are interacted with.

When selecting an RPA vendor, our criteria include ease of use, adoption, skillsets in the country, and the relationship with the vendor. I won't name them, but I have challenges with certain providers out there and the way they actually manage relationships. If I were to look again, relationship would be a very strong indicator. And that was one of the things that attracted us to UiPath in the first place, that relationship, that ease. They are very involved in listening to us.

Two things that attracted me to UiPath when we were doing the evaluation were: First, we'd done a proof of concept and we could not understand - I have some very smart architects and they could not understand - how fast UiPath was performing the tasks. The other factor was the interaction with the client side, the relationship side, with UiPath. Considering some of the challenges I've had with other providers, I think this is a refreshing approach. I'm just hoping that UiPath doesn't outgrow itself and leave that phenomenal customer service behind.

We see ROI all the time. We also see performance benefits all the time. We haven't delivered a project where we haven't seen a return on investment using UiPath. The return on investment is normally six to nine months, maybe a little bit less. But we've never not actually been able to achieve a return on investment.

Sometimes it's actually about setting the expectations as well, regarding what you're trying to do. Sometimes it's not about headcount reduction, it's about quality. It can be about looking at what the customer is actually really wanting, and then being able to deliver on what the customer requires for it be a success.

There are some outliers out there, but there is normally a very strong return on investment.

Look at what it is you're trying to achieve. Do due diligence on the assistance that you're going to interact with, the infrastructure that you're going to be managing, and then actually go out and have a look at a few providers. One of the really strong things about UiPath is that they provide evaluation licenses. There's absolutely no reason why you shouldn't try it before you actually start doing it in anger.

We have solution architects, senior developers, developers, business analysts, consultants, help desk, help desk supervisors, infrastructure, and a data center involved. For maintaining and developing UiPath there are 15 people who report directly to me, but the entire support structure is probably closer to 35 people, maybe a little bit more.

In terms of Academy training, we've done the basic and we've done the advanced training as well. The basic training is phenomenal. I think it's groundbreaking. The online university, in my opinion, is revolutionary in this area, when you look at some of the offerings that other providers have.

The advanced training was a little bit of a let down for us. We just didn't get out of it what we were expecting to get out of it. It just didn't achieve what we thought it would, especially for the price. Our expectations were that we would actually be able to sit all our developers in a room and do a process that we had already done, re-engineer it, and make it better. And that never materialized. It was just a little bit of a letdown. But the university piece is absolutely phenomenal.

Overall, UiPath is a very strong nine out of ten. I'm one of these people who doesn't ever leave a five-star review, there's always room to improve. Still, the nine is a very strong nine. This has become our weapon of choice. That speaks volumes.

We automate business processes that take up a lot of effort and manhours. Our company deals with a lot of documents. 

The most valuable feature is Task Capture. 

We work with Google Cloud and are excited about the possibility of a partnership. 

I have been using the product for six months. 

The tool is very stable. The product's stability depends on the processes you configure it with. 

UiPath's scalability is impressive. 

UiPath's support is great. 

Positive

The tool's deployment was straightforward. There were a few inefficiencies within my company. 

We currently have the tool deployed across different business lines suffering from silos. In the future, we may move towards a centralized structure. 

We have seen ROI with the product's use. 

We want to reduce our employees' demand hours and have them focus on high-value tasks. 

UiPath has fundamentally changed our organization, and we want to learn more about its capabilities. 

The tool has freed up our resources' time. 

I rate the product a ten out of ten. I like working with the software. It might be daunting to start automation and get employees to accept it. However, having a good rollout plan and strategy will ease your concerns. 

We are a distributor and most of our customers were manufacturing and financial companies, so the use cases fell into categories like financial, accounting, and procurement departments. We used it to improve business processes.

With UiPath, my clients were able to free their employees and staff for other types of work. They saw value in that. Staff didn't have to get up at 6 AM or work around the clock in front of a monitor all day. It freed up staff that had been doing menial, manual, repetitive tasks to do something more valuable.

In some cases, it reduced the time it took to get a task done from hours to a couple of minutes. Workflows that would take up to four or five hours were reduced to taking 10 to 15 minutes.

It also definitely reduced the amount of human error to almost zero. 

UiPath Studio has all kinds of tools and it's practical to navigate around the application. Implementing any project can be done very quickly using UiPath. Also, the robot capacity is phenomenal. They work as long and as much as you need them to and provide optimal performance.

Building automation with UiPath is easy and takes a small amount of time. It's really intuitive and doesn't require advanced development or any technical skills. It's easy for anyone to pick up and understand. Any lower-skill employee or developer can learn to use it quickly.

We would usually do a pilot project with a company and, afterward, transfer all the knowledge and capabilities to them so that they were able to develop things themselves. Especially with the UiPath Academy, which provides online courses, and the UiPath forums, everyone could learn how to use it. My clients had no problem picking it up after our first pilot project. The advanced developer courses help a new developer quickly learn how to use it.

There can be technical issues, but it's rarely about a server quitting. They are more like connectivity, platform, and software version issues, but there are no issues with UiPath performance.

I would also like to see UiPath assist clients in scaling up their usage of the application because most of our clients had trouble expanding their usage into other departments. It was hard for them to calculate the exact value they were getting. Some of our clients were flying blind.

Some of our clients hadn't really seen enormous impact from implementing and using automation yet. They had just started, and they saw the value in it, but it was hard for them to expand or add more value to automations with UiPath.

I worked with UiPath from 2019 to 2022.

It can take their technical support some time to respond. And sometimes, the assigned staff doesn't have the right knowledge, but that doesn't happen often.

Neutral

The initial setup is straightforward. Our clients did ask for tips and tricks, but they didn't need a full consultation. They managed it themselves. It's really intuitive.

UiPath pricing is high and sometimes it's quite complicated as well, because there are loads of components and loads of product portfolios. It works, but it could be better. The pricing could be more attractive.

UiPath definitely speeds up digital transformation but whether it reduces the costs of doing so depends on a number of factors.

Over the years, UiPath has done a pretty good job of continuously improving its product by adding robot capacities and changing versions. In terms of features, they have everything covered, with AI features, data mining, process mining, and all that was done quite ahead of everybody else.

I would say that UiPath, as a company, was better in the past. Nowadays, I have less confidence in the company's situation, not that I don't think it's stable. And their ability to improve is a 10 out of 10.

My advice is to study your use cases and go to the UiPath Academy. You'll find everything you're looking for and there is a big community. UiPath is easy to use, but you have to understand your work processes thoroughly and not just depend on the application to help you.

Our primary use case is for RPA. We use it for checking invoices and sending out electronic letters. It is also going to check the absence entered by people when they are sick and see if those fill-outs are correct.

UiPath enables us to implement end-to-end automation. It is very important. It makes us more efficient. It does not require that much labor.

We find UiPath quite good in terms of ease of building automations. It does not require an enormous amount of knowledge. It is quite easy to use, but we need to do some scripting and programming in addition to the software.

We use UiPath's AI functionality in our automation program. It is necessary to interpret PDFs. We only use it in one process so far. It has only been six months, so it hasn't enabled us to automate more processes overall.

UiPath speeds up digital transformation and reduces the cost of digital transformation. This digital transformation does not require expensive or complex application upgrades or IT application support.

UiPath has reduced human error. In the use case for checking the invoices, it helps us to handle an invoice more correctly and send the invoice to the correct person internally so that it does not go in a loop somewhere.

UiPath has freed up employee time. By the end of this year, it would have saved us two whole man-years.

UiPath has saved us costs. In the six months of running it, it has saved us something like one and a half million.

The software does what it is supposed to do. I do not have any specific features that are valuable. We mainly use it for automation. We use the standard application screens. It meets our requirements.

We would like to use several modules of UiPath, but they are very costly. All the additional features that we need are there, but they are in the modules that we have not bought.

Its stability could have been better. 

It was installed around September of last year.

The stability could have been better. We started out with one developer license and then we had another developer license. When both developers are working in the cloud platform, it shuts down. I am not sure if it is solved yet.

I do not know about the scalability yet. I hope it is scalable.

We have not used their technical support. We used the UiPath community for some issues. We were trying to learn how to program, and we were stuck and trying to figure out how to do certain things. We posted a couple of questions to the community. There are always people there who are willing to help and come up with good ideas to solve the problems that you have been stuck with.

We did not use any solution previously.

It is in the cloud. Our cloud provider is Digital Workforce.

The deployment took four months. It was straightforward. There were no issues. The integration between the cloud platform and our internal networks with the firewalls was really smooth.

It does not require any maintenance from our side.

It was Digital Workforce that showed us that this is how we would want to do it. We based everything on their strategy.

With the rate at which we are going with automations, it should take us a year and a half or two years.

UiPath has several modules that we would like to use. They will enhance our installation, but they are very costly. 

We are quite happy with the solution as it is. If I were to go for UiPath again, I would not choose Digital Workforce as a supplier.

I do not have any experience with any other solution, but we have had some glitches, so I would rate UiPath an eight out of ten.

I have used UiPath for a city utility. The main purpose is if they want to dig in a particular location, they need to know how many pipelines are underneath the road, what the situation is regarding high-tension wires, gas pipelines, et cetera. For that, we needed to go to about 18 websites and scrape the maps from them into a local repository. We use UiPath to save that data from all the websites.

From there, there is an AI/ML solution that identifies the danger signals and notations on the map. It summarizes them and sends them to a mobile application used by a person who is at that location. That person can determine whether they are able to dig in that particular location or not.

UiPath reduces human error by automating a lot of manual steps. 

It also helps free up employee time. The amount of time depends on the use case. For the use case I described above, for the utility, the whole process of preparing one package would take one person two and a half hours. Automating it using UiPath and AI reduced it to two and a half minutes.

In terms of costs, for that use case, it has saved that company 30 to 40 percent.

Scraping with UiPath is easy, as is integration with some services. It's also easy to deploy solutions. 

Building automation takes place in a normal programming environment like Visual Studio. It's the same environment developers use. If you know development, building automation in UiPath is easy. Visually, it's all interactive and easy to work on.

The platform also has features for logging and monitoring things and communicating when there are errors.

The UiPath user community is a very good ecosystem with information about a lot of new features like AI, chat integration, and WhatsApp integration.

For training purposes and certification, we use the UiPath Academy. It's a very good resource and you get very good support from the community.

We also use the solution's AI functionality but so far only on low- to medium-complexity processes.

I would like to see them transition to the cloud and provide services there. That would be an improvement.

Also, it needs more integration with external services, and I would like it to have generative AI and more artificial intelligence features.

I have been using UiPath for about one and a half years.

The stability is good. I am satisfied with it.

The scalability is also good.

UiPath's technical support is good.

Positive

I used Automation Anywhere. I switched because our clients switched since UiPath is cheaper.

There is definitely ROI from using UiPath. Based on the fees and the load of the input, ROI will be calculated and used to decide whether the use case is worthwhile or not. It will be decided in the analysis and discovery phases. If ROI is feasible, only then will development take place.

With UiPath, there is an additional cost for Document Understanding. If the use case demands it, that feature should be used.

Even though our clients may have an Automation Anywhere ecosystem, they choose UiPath due to budget and cost. Apart from cost, both platforms offer almost all the features. However, from a technical perspective, Automation Anywhere has more utilities and components for building bots.

If it weren't for the cost, I would personally choose Automation Anywhere, on the technical side, because it has huge utilities and components for building bots. The move to UiPath is driven by budgets and costs.

As for end-to-end processing, when you are trying to come up with use cases for RPA, you will probably look at existing legacy applications that are not extendable. They won't have any more new releases but we still need to extract value from them. Use cases include reducing the processing steps and manual steps done, day-to-day, by people. End-to-end automation will help to stitch all the gaps and reduce the processing time.

UiPath is not cloud-based yet, so most of the work is done on-premises.

In terms of maintenance, one person on our support team monitors all the bots and attends to any problems.

I would recommend UiPath for small and medium-sized automation. If a company doesn't have a large budget, UiPath is the solution.

We use it mostly for the banking and insurance domains. We are a service-based company and the tools we use depend on our clients' requirements.

UiPath provides scalability, quality, and a high level of accuracy. It has definitely reduced human error.

It also helps minimize the on-premises footprint, which is important for our clients' environments.

The most valuable features include

• multi-bot architecture
• UiPath Studio
• Test Manager.

It is easy to build automations with this solution as well. We are able to implement end-to-end automation.

There are also build connectors for Salesforce and SAP. Before the connectors, we could only automate the GUI. Now, it is very easy to integrate on the back end as well.

The UiPath Academy courses are also helpful. When a feature or release comes out, they demonstrate them in the Academy.

And if there are any issues, the UiPath community forum helps us to check whether others are also facing these issues. There are a lot of benefits from that.

For some of the cognitive features we have to learn the integration side. Other than that, everything is fine.

I have been using UiPath for nearly three years.

The LTS version is very stable.

It is also definitely scalable. I would recommend it for any size of company, from small to large. For example, if a small company only needs UiPath Studio, they can have it. They don't need UiPath Orchestrator. They can run things with Studio only. There are a lot of options with UiPath.

Their support is good to have, especially for priority issues. 

One thing that would be helpful is if the support team could quickly help us when we raise a ticket. It takes them at least one or two hours to get back to us. With Automation Anywhere, if there is a Severity 1 issue, their support responds within 15 minutes.

Positive

Setting it up is very easy.

The amount of time it takes depends on the client's security requirements. Some teams have restrictions and documentation on how things should be done. But once everything has been verified, deployment will take one to two hours.

Once it's deployed, it's the validation checks that take some time but it depends upon the project: the supporting files and checking that all the integrations are correctly mapped.

In terms of project deployment, we generally have three people involved. One of them will completely handle monitoring and supporting, as well as the Control Room and any logs or administrative tasks. The other two handle change requests.

As for maintenance, our setup is on-premises and we have an internal team that takes care of situations when the server is down. They will restart it and do patch updates, which they will inform us about.

We are using the Enterprise version. We are exploring using it in the cloud, but some of our banking clients do not accept the cloud because of security issues so we go for on-prem only in those cases.

We are not fully using UiPath's AI functionality but we are doing some PoCs, based on our clients' requirements, to check the feasibility. For that, we are using the Community Edition. As for UiPath speeding up digital transformation, I'm not sure. It depends on the process involved.

Overall, I don't see a need for any additional features. I don't have any difficulty using UiPath.