UiPath Reviews

We use it for unattended automation. Most of it is centered around finance for various reporting purposes. We also use this solution to move data between systems.

The biggest improvement is giving people time back in their day. We're still not where we'd like to be with our automation journey, so we don't have the time savings that we would like at the moment. However, we are continuing on that journey and helping to free up users and allowing them to work on things they want to work on.

The Excel integration is definitely good. We use that a lot because our finance department uses Excel. Overall, I really like Studio and unattended automation. Automation Cloud is very good as well. The platform as a whole has been good for us.

I like the UiPath user community, and the forums are really good. Most of the time, I can find answers there to any issues I'm having. The UiPath forums are very active, and I like seeing the employees in there as well.

We onboard any new developers that we have for RPA using UiPath Academy. It reduces the amount of training time in which the RPA team is involved because the Academy courses can take care of a lot of the fundamentals on UiPath.

Integration is an area for improvement. I still encounter issues with it, like getting errors when I try to use a connection.

We've been using it since 2019.

I have no complaints regarding the stability of UiPath. We have never had any issues with regressions or weird bugs.

We're still in the early stage of our journey with UiPath. Right now, we have six unattended robots and about 25 processes running on those, which is not at a scale where we might see issues. However, I have no complaints with regard to scalability so far.  Also, achieving the scalability we may need seems pretty straightforward.

UiPath's technical support is on par with that of other companies. We seem to spend a lot of time sending logs back and forth, and because of that, I would give technical support a rating of seven out of ten.

Neutral

The initial setup was not too bad. We started in the finance units since they were the ones pushing for RPA, and they've been our biggest internal customers so far.

We worked with our reseller who guided us through the entire setup. They did a few automations for us until we had that practice in-house.

In terms of ROI, we are saving more than what the platform costs us. We are at about 1.5 million in savings due to recent automation. It was a little less than that before. These are soft savings and don't show up on balance sheets. We're trying to work toward automation that actually do lead to hard savings. We've saved about 43,000 hours in a year so far.

The licensing makes sense, but it does lead to a few adoption issues when a lot of the licenses are per user. Convincing some of our business units to pay for user licenses for either Action Center or attended robots can be a roadblock.

We looked at Blue Prism. The biggest reason for going with UiPath is that we are a heavy .NET shop. Therefore, the fact that UiPath is based on .NET and that we can write our own custom activities in C# bar and Visual Basic were big factors for us. It meant that we would be able to adopt UiPath faster and that it would fit with our current Microsoft stack as well. We also liked where the UiPath platform as a whole was going, becoming not just RPA development but integrations as well. In comparison, Blue Prism seemed to have stuck with RPA and not expanded much beyond that.

Take a look at UiPath's platform as a whole and what it can do aside from just RPA automation. I would also advise you not to discount the tech stack. Overall, I like the platform, and I think it's headed in the right direction. Because of that, I would give it a rating of nine on a scale from one to ten.

The use of this solution is spread out across our organization. On the IT side, we use it for synoptic notes like admission process, reviewing invoices and giving usage access.

The insights that this solution provides have been most valuable. We use these insights to report to higher management on the performance of our processes. 

UiPath also helps us reduce manual work although we do not yet use UiPath's AI functionality. We have learned a lot from the UiPath community and gained knowledge about future products and enhancements. 

The support for this solution is tedious. I would rate it a five out of ten. If we don't respond or the ticket closes, we do not get a response from them.

I have been using this solution for six years. 

This is a scalable solution. 

The support for this solution is tedious. I would rate it a five out of ten. If we don't respond or the ticket closes, we do not get a response from them. We then need to go through the process again and reopen a ticket with the same information.

Neutral

I have a little bit of experience using Automation Anywhere, but I prefer UiPath. The coding with Automation Anywhere was not developer friendly. 

Our whole team was new to this solution so there was a learning curve involved for all of us which made the setup difficult at times. At this stage, UiPath was one or two years old with limited documentation. The deployment did not take long.

We deployed this solution with the help of a partner called Ernst & Young.

We have experienced a return on investment using the solution as it has led to three million in savings since we started using it. 

We would prefer it if the licences were packaged together. When it comes to developer licences, we need to pay to transfer licences when a developer leaves and this also creates additional work for our IT team. 

Overall, I would rate this solution a nine out of ten. 

I would recommend UiPath to others because it is a good tool and has a lot of potential to expand. 

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 am an RPA developer and I am primarily using this solution to fill up timesheets in an internal portal. I use Windows 10, 64 bit. My team uses a mix of Windows 7, 8, and 10. It is suitable for daily and weekly tasks, which pretty much don't change over time, and is what I choose to automate parts of my team's work.

We are an IT company that works on both products and services. UiPath has helped to automate tedious data-filling jobs for test data creation (Testing), and data extraction jobs from public websites (HR). It has added a new capability which we can showcase to our clients.

Data Scraping is definitely a unique and useful feature that we had not known about before.

Smooth integration of OCR, which is very quick, is a useful feature.

Manage packages to get more packages.

Save as a Template feature.

Snippets are really useful as a reference for logic.

Plus button between activities & Ctrl+Shift+T is very useful in adding activities quickly.

Having the ability to run the bot from a single click will help to democratize the RPA.

Currently, I am running the XAML file from command prompt mode and this is causing inconvenience every time I update the XAML file.

The regular update of the Community Edition means that the UiRobot path is constantly changing on every update.

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

There are not many complaints on the stability of this solution. Though the regular updates of the Community Edition have given me trouble at times, it has been quickly resolved in the subsequent updates. I think that the UiPath Forum portal is one reason for this.

According to me, on one side it is creating a buzz and everybody wants to be part of it. On the other side, there is resistance to embrace new technology in their process. Only over time, this can be scalable and it cannot be done quickly.

This was my first RPA tool.

The initial setup is straight forward. This got better after integrating the Chrome extension setup in the UiPath studio itself.

I did not evaluate other RPA tools.

The UiPath product team is doing an awesome job. Keep it up.

Our primary purpose is to automate our internal processes so we can increase our profits and reduce our headcount. We are an IT service provider, so our main focus so far has been our Service Desk but we are starting to work with our Finance, Payroll, and HR teams in 2020.

So far, we have not realised much in terms of benefit because we have only just begun our RPA journey. However, we have approximately four FTE of savings in our pipeline. It has improved our business so far by creating an innovation-based way of thinking amongst our teams.

Personally, I find that Explorer Expert and StudioX appear the most valuable to my role as an Analyst. Explorer Expert allows me to easily "record" processes and gives the developer the skeleton of an automation project. StudioX allows me to build simple automation projects without the need to engage our development team.

StudioX could use some improvement to broaden the range of automation projects suitable. At this stage, it is limited in terms of the functions that are available and I would like to see a lot more options added to this tool so that our business users can get even more benefit.

We have been using UiPath for three months.

There have been no concerns with stability as of yet.

It appears to be very scalable but we have only had the tool for a few months.

Customer service has been great so far. We have received answers to all of our questions quickly.

This is our first RPA solution.

We had some issues with the licenses at first, but we were able to communicate with UiPath to get this resolved.

We used an in-house team to implement our solution.

So far we have not had a return on our investment, but this will change in 2020.

Pricing is quite reasonable with UiPath and there are some tools which are free to use.

We evaluated a range of options on the market including Blue Prism.

So far, I highly recommend UiPath. They are constantly introducing new tools and features and they all seem to provide extra benefit.

We primarily use it for delegating access permissions to help desks, for example. We use it to automate certain things, like onboarding new users, or deprovisioning leaving users. When we add somebody to a group, it triggers some kind of automation workflow. Lastly, we use it to sanitize data entry, so to make sure that capital first letter in the street name is used, certain zip codes aren't allowed, others are, etc., so data is controlled.

It helps mitigate the risks. With traditional native active directory delegation, it becomes real messy, real fast. You lose oversight on who has access where. We are an acquisition merger company, so we let go of certain companies and onboard new ones. With native delegations, you lose track of who has access where. With Active Roles, we can always see who has access and what they can do in a very granular way. You can modify the street name but you can't modify the city for example. Or you can modify the picture, but not the names and so that granularity is not available normally.

This product has eliminated a lot of tedious IT tasks, especially when people leave. There are about 10 or 15 actions that Active Roles does, scripted, in the same way, each time. It used to literally be a list of things that the admin would do, like: hide the mailbox, disable user, remove the groups, etc. Also, the auditing history that it keeps is very handy for us. We have a change record of what's been done to a user, who did it, and when they did it, which really helps us out.

We really needed this kind of product for its Active Directory delegation. We could not allow everyone to have native access to our Active Directory. The delegation bit was really the trigger. Automation is also a major reason we use UiPath. There was just so much room for human error that we wanted to script activities rather than rely on the admins to know what to do. This is especially important now that we are outsourcing many activities and dealing with a changing audience. In order to make sure that everybody does the same thing at the same time, tools like these make sure that you do everything in a structured manner.

The value for us is that it resembles the native tools that most people have grown accustomed to. Most people come from another company where they may not have used Active Roles. Active Roles resembles traditional tools like Microsoft's, which is really good because it eases the way people interact with the tool.

AD and AAD management features are really good. They're better than native tools; they offer an added value. They show more fields than traditional tools, such as password age and status of things that you normally wouldn't see. We still have the mailbox and user information all on one screen, whereas in native tools, you need two tools to show that information.

Active Roles works with policies and access templates, as well as workflows, which are really powerful. While it comes with a lot of example policies and access templates, there are zero built-in workflows. I would personally love for it to come with 10 to 20 sample workflows that achieve a certain task but are not enabled by default. In that case, I would be able to just look at those to see how it's done. I could clone them, copy them, and modify them to how I want them. Then I would be good to go, rather than having to reinvent things from scratch.

The solution is very stable. Even if components lose connectivity, or the database dies, as soon as it comes back up, it just reconnects and goes.

It covers all we would like to do. It's scalable; you can make it replicate databases. We don't use a lot of those features, but it is very scalable.

It needed a bit of getting used to, in terms of where you set what, but once you get the hang of it, it's really straightforward.

I think we're just paying for mitigating risks. There is the risk of leaving all authorized access behind and the risk of having Active Directory pollution. With that comes a risk of people getting access that they shouldn't have or having multiple accounts for the same thing. There's no money or value added from using the solution, but there is risk management. That is really what you pay for.

We did consider using the Microsoft solution because it's free and built-in, and that's what everybody does. However, when you grow beyond a certain ping, or scope, you find out that it just does not cut it anymore. We also considered using other tools, but at the time, I think Active Roles was very much alone in this world. I have to admit, now there are other vendors available, which I don't have any personal experience with, but on paper, they seem to do a bit of the same thing. At the time, though, there was simply nothing else that could even come close.

I would rate UiPath as nine out of ten. There's always room for improvement. This is definitely, really up there.

We are trying to focus on using UiPath for our mission. A lot of people use RPA for things that happen everywhere, such as in financial or HR. We are a bit different. We are trying to focus on things which will improve what our customer are doing.

For example, one of our customers is a bank. Therefore, we are focusing on improving their relationship with the bank's customers by using RPA. While there are use cases everywhere, we are focusing on trying a company better and more streamlined at their core.

The robot (in the bank example) focuses on improving the way a customer interacts with the bank. The robot facilitates the monthly interaction that customer the bank by providing information to the bank, processing information much more quickly, helping the customer and bank at the same time. The bank doesn't need to spend a lot of time or resources looking at the information coming in. The robot can process the incoming information, validate it, and do lot of the work which had been done before. It is a win-win on both sides of the relationship.

We are seeing RPA use cases everywhere. Pretty much every one of our customers has some type of RPA that we are talking about as turning into a pilot or have already moved forward with as an RPA solution.

One example is we created a robot to use with DocuSign, which is fairly industry standard.

It has a core tool set of things in use to quickly put together an automation, whether it's interacting with an application or website. It gives you the tool kit that you need to quickly put something together. Very often, we can create something in a very short time frame, like in less than a day, and show it to someone. Then, they can see the immediate value of the solution.

UiPath was easy to use when I first came into it. Though, I have a software developer background, so a lot of the concepts were very easy for me.

UiPath has a whole bunch of online courses in the UiPath Academy. These are very helpful on understanding the capabilities of the tool and some of the nuisances of it. 

It takes a bit of thought to find the right thing that fits into RPA at this point. However, with the things that we are branching into with natural language processing and imaging things, there will be more possibilities and opportunities.

UiPath should continue to grow and integrate with things that we can interact with, particularly with other enterprise solutions out there. They should continue to have out-of-the-box things that we can just take and work with.

I have seen a lot of improvement in the stability and scalability in UiPath over the last year or so. There have continued to be new releases with new updates, along with new technologies that help. Therefore, the maturity of the product has gone a long way in getting to a stable, scalable product.

Going forward, I would like to see more stability in the robots. When I create a robot, then I want it to work for quite some period of time. I've had some situations, where things will update, change, and the robot is broken. Part of this is making a more stable implementation easier.

We have put together a couple installations using Orchestrator. We haven't had the need for huge scalability yet, but it seems that the platform is there and has the capability for it.

One of our customers is a very large financial institution that has a lot of automation, because they have millions of customers. Then, some of them are smaller who are just trying to put their toes in. Even at our very large customers, there are still opportunities for improved, additional automation. However, the maturity across our customers is very diverse.

UiPath has always been there to answer the questions that we have or help staff when we need it.

Our customers ask us about the solution because of the government mandates.

Compared to the other RPA platforms, like Automation Anywhere and Blue Prism, UiPath is much easier to set up. This is the value that a lot of our customers have seen, because it is so easy to set up, you can set up and install something on your own computer, use it, then run with it, and finally, play with it.

That is a huge advantage: You don't have to set up a large infrastructure just to do RPA now. Of course, Orchestrator is a little bit more complicated, but then I've had a much easier time setting up Orchestrator than I have had with some of the other leading RPA products previously mentioned.

The biggest thing for a lot of our customers is ROI. It takes about a year to see ROI, but it does vary based on use case.

One of the use cases that we are looking at is for a large government agency. They are taking people out of doing reports and putting them back in the field. In a cost constraint environment that we are in, this is critically important.

Some of the things that we've done have cut down tasks that took four hours to 30 seconds. So, there is a lot of benefit. Our customer are experiencing very large benefits from automation.

Go download it, install it, and play with it. You can't do this with any of the other platforms.

There is an easier level of entry for UiPath.

While you can easily automate with RPA, the tasks someone does repetitively and is likely to make mistakes, thus eliminating human errors on a lot of things, but at the same time automation is only as good as you make it. So, humans are creating the robots at this point, and obviously there is still a possibility for errors. However, in processing workload, you will definitely cut down on the errors happening there.

We have a lot of maps worldwide which order some stuff from my department, and this is the compiled path. This goes into our database, then it comes to us. 

It uses data that we have already in the company, which is just sitting there waiting to get picked. You just have to tell a robot that a human does this, now you do it. We have so many processes which could be done like this. Right now, it's just scratching the surface. We are really exciting about it.

The product is very intuitive and easy to use, and I am not a developer.

The product is stable with no downtime.

The product can scale and meet our needs going forward.

I haven't used UiPath's technical support.

The UiPath Academy is good. I started there and learned how to use the tools.

The initial setup was very complex. We had the data, but we had to streamline it. You can build a robot in 30 minutes, but the robot needs to get the data correctly. This was hard to do because the laboratory in the U.S. uses the system one way, then the Chinese lab does it another way, so we have to streamline those before we can use the robots. 

Therefore, I should have looked at the data beforehand, since it took too long to get the data to be recognized correctly. We have learned from that experience.

The product has saved us on time.