UiPath Reviews

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 use case is the Automation of invoice processing.

We're looking to automate some processes like invoicing in order to make the organization more efficient and reduce workload for the employees. Invoices are non-structured or semi-structured data, so we're going to use OCR to extract the data and then automate the invoice process.

We have automated some processes and have reduced the time that users take while doing those tasks. For example, we use to manually fill in certain forms with the chargebacks, and now we use Clockify Time Tracker with automation that fills in the forms and uploads them to SharePoint.

The Screen Recorder has a lot of different features like web and desktop. Native and Citrix Recording are pretty useful for speeding up the design process. 

Computer Vision using Microsoft and Tesseract are pretty useful.

The new release of Studio X is a game-changer because this new app focuses on Business users. It is going to be useful for the organization because they can start creating their own automations.

They should add chatbots functionality for Microsoft Teams and not only for Slack.

They could give more information about beta / pre-releases so more people can test them and give their feedback.

Keep updating the documentation because sometimes you get redirected to a non-existent page or an old version of the activity. 

We have been using UiPath for six months.

UiPath is pretty stable and if you have any issues with a new version you can rollback.

We did not use another solution prior to this one.

The initial setup is straightforward. There's a lot of documentation also you have the forum if you are facing any issue.

My advice is to ask about how the licensing works and how to get access to the other services that UiPath provides.

Before choosing UiPath, we evaluated Datamatics, AntWorks, and Blue Prism.

I would suggest downloading the Community Edition and testing UiPath yourself. Join the automation first industry.

We use UiPath for building business cases for customers and internally building RPA competency within my department. Our organization is just starting to implement RPA. As a business consultant, UiPath is our chosen solution for RPA implementation. 

UiPath has made it very easy to create business cases to showcase to executives the functionality and benefits of RPA. UiPath was instrumental in my initial business case, as they came in and executed the proof of concept. That was a huge help and my customer was very pleased.

I find the community most valuable as it allows you to find your solutions and people to help you.

I like being able to save components to reuse for other processes and not having to start from scratch each time.

I appreciate the simplicity of the interface as I am learning to be a developer.

I would say a better layout or interface between the Studio and Orchestrator tools would be nice.

I have been using UiPath for five months.

We did not use another solution prior to UiPath.

I'd advise others to consider sharing the costs after ensuring they understand their expectations for utilizing the capacity of the robots. Share the cost if you forecast not utilizing the entire capacity.

We did not evaluate other options before choosing UiPath.

There is already a new release and I am pleased so far. I think UiPath has done a great job making resources and tools available as well as providing opportunities for learning directly from their company and in the same quality as their employees.

We use this solution for our business purposes. We use it from the back end all the way to the front end. That's where we are looking to use this, although we haven't fully implemented it yet. We are exploring more processes to use it for.

Mainly, this solution has reduced the need for manual intervention. That's the main thing. It has saved us time. We can now increase our ROI.

We run a few automations in a virtual environment, but not all of them. I've been using some other automation tools, like QTP/UFT.

I would rate the ease of use of the platform for automating our company's processes as four out of five.

Its intuitiveness is great. This solution is very user-friendly. There is almost no need to have programming knowledge.

The solution has helped us eliminate human errors, by about 40%. It also saves us time.

The solution is fairly stable. I would rate it as four of five for stability.

So far, we have almost 50 people in our organization involved in our automation program.

The initial setup was in between simple and complex. As even my colleague was fairly new at that time, he came across a few challenges. However, he could overcome them and now I'm in three of the processes that are in products.

It took about three months from the time we purchased a UiPath license until our first robot was in production.

We used a consultant. I would rate them as four out of five.

We have definitely seen a performance benefit. Now that it is in the production processes, we are able to see ROI, in terms of saving time on repetitive tasks and the manual effort saved. That's our return on investment.

I would rate this solution as eight out of ten because it has saved us a lot of manual intervention, as well as time and money. We may have not yet explored the full horizon of what this solution can do for us.

We play significantly in the BFSI and healthcare space. A lot of use cases have been related to BFSI. Insurance is much bigger, with claims and underwriting, policy admin, health benefits, and so on so forth. There are also good use cases on the functional level, HR and finance, and that cuts across industries. 

As an example, looking at fatality insurance for pets, clients had a high volume of documents come in, claims in all different forms, and they had to apply logic eligibility. There's a simple rule of whether you allow or disallow. If they don't allow the claim, then there's a comp process. By a sheer ability to read whichever way the document comes in, clients are able to load the system and quickly get the eligibility. 

This dramatically improves their claims operation by a big margin. Whenever there is some complexity in one, then we do an exception. We crunched the time so well and made the process so cost-effective it has given the client a huge benefit.

The democratization, automation, and attended automation, all of these are pretty good features. Those are all good value add to what it was there previously. 

The moment a machine takes over, there are fewer errors. That is inherent. When you say value, that is the cost-benefit. 

We have seen a lot of benefits on the backend, but then the algorithm is constrained, which can't transform because of the older technology. 

Sometimes in their partner communication, they aren't consistent. This maybe is related to the fact they are growing as a company.

The solution is fairly stable. 

The initial setup is always complex. Clients don't know the hardware, the licensing, or how it works. Any large organization will always have an initial hurdle. 

We have roughly around 164-165 trained RPA credentials on the engineering side, all on UiPath.

You do have complexity when it comes to maintenance, as you get to 50, 100 bots. 

As an example, one of the customers for whom we did an early bird, we estimated we could save this one division of their company $44 million. They only may have to invest about $4 million. There's $44.5 million for about 12 months. That's what we think we could save. 

The adoption of RPA has definitely been increasing and we know that all of that has been largely in the back office. In the back office, it's easier to check ROI. We've actually gone beyond ROI because ROI is a very simple statement, so we start showing clients value.

How long it takes to achieve ROI actually depends upon the client's way of implementing it. For example, some people will wait to take away the manual effort while they will stand by. Because what if it doesn't work? What if it fails? What if then my backlog increases dramatically? So, it is really up to them. If it is simple task automation, we can do it in about four or six weeks. In eight to 10 weeks they'll see the benefit. 

We're using all components of UiPath: attended, unattended robotics, and Orchestrator Studio. We have a very wide customer base and our clients use all of them.

Cloud adoption is increasing. Deployment models are a little bit more a logistic question than anything else because companies who want on-site are a little bit more conscious of security, but they take a normal amount of time, just to figure out the infrastructure. If we moved clients to the cloud, we can make it easier to implement. With email on the cloud, they have a huge set of processes. The larger the company, the larger the processing. With the cloud, it becomes faster. 

I've got a deep partnership with UiPath. I would absolutely rate them high. I'd give them a ten out of ten.

Our client's companies have extensive issues with SAP and getting information out of it. They have another technical ERP system with an in-memory database where they don't get the information out of it, then have to add it manually to SAP. That will be probably the first big use case for automation. So, we will get a bot reading it on the database from the Citrix environment and probably moving it to SAP.

The client will probably have it on-premise. They tend to be really risk adverse in terms of Cloud solutions. We have tried to get them to use the cloud more because it's just easier.

We are using Studio Orchestrator, and unattended bots. I have programmed attended bots before.

The client is eliminating human errors as they are eliminating some of the accrual processes from SAP, where a lot of mistakes can be made. If the bot is not making mistakes, then they are eliminating errors by 100 percent, but this depends on whether the bot is efficient or error-free.

You need an understanding of how to code, use the variables and arguments, etc. That was why I was excited for StudioX. I tried it earlier, and it was amazing. This is actually what they were missing. Studio is great because you can do so much stuff.

On a scale of one to five (where five is beneficial), I would rate the UiPath Academy as a four. There is some stuff that they could do better. I sampled the advanced, which is really difficult because it's just PDF. I had to use some YouTube videos to understand the framework that you need to pass for developer. They could do more videos on that.

They have three parts. The first is the foundation, and they are a lot of videos. The third part of it (advanced), there are no videos except one. That's only those PDF files, which you have to look and read through. I was like, "Okay, I probably can't do it." Then, I fell upon some community YouTube videos from other developers who just demonstrated it. This would be great if UiPath offered that, because I found out later that the developers made mistakes in their videos.

In the foundation, they get into much detail in the beginning. You're overloaded with information. You have to go through videos like three times to get it correctly. They could remove some stuff out of there. Those quizzes are really frustrating too. They are too detailed. If you sat with Uipath, you think it's really easy. However, it's not so much, if you get into those details.

Studio is a bit overwhelming in the beginning. They could get add some details, but not so many, into the foundation training. I've seen StudioX and loved the colors. Please get the colors into Studio. I loved the flow and that you got all these activities and colors too. It was so much easier. It was visually easier to understand where to click. It was really user-friendly.

I would rate the ease of use of the platform for automating our company’s processes as a four out of five (with five being very easy). I would rate it as a four because it didn't work in the beginning to get my bots active. I had to get into a lot of videos to get them running. I didn't understand how it needed to be designed or coded.

The Orchestrator training was much better, but I still somehow missed some details which I needed. However, it's not just do it, then it's done. You need some time to get into it. Though, it's much easier than Studio.

The integration with Outlook is not that good yet.

I would rate stability as a four (out of five). I had some cases where Orchestrator didn't work in it. We couldn't login and the platform was slow.

We are still small and just starting out. We have five developers/solution architects involved in automation projects. We have done our certificate through UiPath Academy.

Support is pretty good. It's responsive.

Our client was having some problems. They got a framework running on a scale: 

• Which processes should be automated?
• What are the easiest processes to automate and more difficult?

For our first client project, it took us five months from the time that UiPath license was purchased until we implemented the first bot. 

The initial setup was straightforward. They identified several easier flows, and it was like learning with the client together. I know they are phasing out some more complex issues where you have to get into the details of HTML coding and stuff like that to get some stuff done. That is where UiPath gets difficult, because it's just coding and tech.

Our client saw ROI after one month. They realized after we showed them the first process that three people would be free to do other stuff. They got to sort of afraid of what they would do with those three people, and those people were afraid, which was a big issue. 

We invented RPI and pizza. We all came to those pizza Fridays and showed them that they don't have to be afraid. They benefited from it more than not, and no one would lose their jobs.

We told the client UiPath is best. We looked for the biggest player in the market and decided UiPath was the platform.

We target medium-size companies and have long-term relationships with them. They trust in our opinion. We told them our reasons that we think UiPath is the best.

UiPath is biggest player in the market. They have this platform economy going. I'm really excited to hear that they bought the process goals. There's a lot of potential there, if they integrate process automation with process mining. That is a big thing for me.

We looked into other RPA tools, like Blue Prism. We decided it's harder to learn and implement.

I would rate the solution an eight (out of 10). They need to thrive to get better.

If you have some tech experienced people, then UiPath is the better solution because it's easier to learn and implement.

We are using Orchestrator for both development and production. We are using attended and unattended bots, and we are using Studio to develop them.

We use this solution for front-office processes, back-office processes, IT processes, and automating anything that we can.

We run our automations inside a virtual environment. We use Citrix and Citrix Server. We have sixty-seven processes that we've automated to run in the virtual environment and its very straightforward. It's deployed out of Orchestrator, and for attended processes, it's as simple as going in, opening a UI robot, and clicking the start button. It's phenomenally easy.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would say that it's a five. It's very easy. I'm a software developer by trade and I was able to automate several processes in a very short time span. In two weeks I can automate an entire process, end-to-end, which is incredibly fast for the ROI.

One of our processes was extremely complex, which was our customer onboarding process. The complexity was, in part, because it is handled by six different departments. The PDD for it was one hundred and forty pages long. One or two we've done were simple automations, and the rest have been medium to high complexity.

My first robot went into production within a month of me being in my position. That included going through all of the UiPath training, getting familiar with our IT systems, and then actually vetting out a process and automating.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. It was very informative and very detailed.

We are using the unattended robots more than we are the attended ones, and we're trying to continue that drive. We understand that there's a need for some processes to run attended, but if we can, we do process optimization to make it work and be unattended.

We have definitely seen savings in time. I can only speak to one particular instance, which is one that I automated. It was taking a product marketing team roughly an entire month to process, so they were always a month in arrear processing invoices for orders. When we developed this quote-to-order process, it saved us something along the lines of seven thousand hours per month for the one group. I was able to shrink down what a team of twelve people was doing in a month's time, to about seven days.

Unattended robots are my favorite because it allows us to completely remove a process from a person's day. The process can be fully automated and scheduled out of Orchestrator to run. Whether it's several times a day or once a month or whatever it may be, that user no longer has to worry about whatever that task was.

I would like to see support for native C# capability. I have a .NET background, so it's easier for me to write in that language.

With respect to the stability, on a scale from one to five, I would rate this solution a four. There are some issues we've run into where we just can't exactly figure out what is causing the problems.

A robot would run through a process two to three dozen times with no issues and then on the very next run, it will stall in the middle of the process. When we tried to debug it, we can actually replicate that stall but clearly, it's not throwing an error. There's no rhyme or reason to why. It just stops and it just kind of hangs. I would say that it may be a stability issue.

The technical support for this solution is great. They're responsive, and always willing to help. We got infrastructure support to help us through an upgrade so I could actually migrate everything from our on-premises server into Azure. I would rate their technical support a ten out of ten.

This solution started as a homegrown operation by one of our satellite offices that downloaded a trial license and started using it. Once our IT department found out, we hired Deloitte to come in and talk us through the whole process. Then, Deloitte left and we started our own kind of homegrown development. The did not actually deploy it with us.

Prior to choosing UiPath, we evaluated Automation Anywhere and Blue Prism. There may have been one more, as well. We are a very large SAP shop, and UiPath was the only one that touted that it was integrated well with SAP. For the most part, it did.

For anybody researching this type of solution, I would suggest that they try this out and they will instantly see the value.

I would rate this solution a ten out of ten.

The primary use case is business services (finance).

When we would have a huge backlog, we would hire short-term employees for some of our cases. Now, we don't have to do that anymore.

It is easy to use, automate, and scale.

UiPath should make the solution part of customer's everyday (more user-friendly).

I would like to see the following additional features going forward:

• Advanced scheduling
• Easier implementation of the robots
• Better analytics
• Easier non-technical overview of the process.

The stability is pretty good.

Our Citrix environment works, but it is quite unstable. It takes a lot of processing time because it is unstable. We have to do a lot of checks and so on.

The scalability is pretty good.

I have not had to use the customer support.

The UiPath Academy is fine. I would like it if the videos were more written out for reading purposes, since I have been developing in UiPath for some years before taking the Academy. Having to watch all the videos was a bit slow and time consuming.

The company was not using an another RPA solution previously.

The implementation went really well. The initial setup was straightforward, but when you start to scale, you have to figure out how to do it.

Our Citrix environment works, but it is quite unstable. It takes a lot of processing time because it is unstable. We have to do a lot of checks and so on. 

I was a consultant doing implementations for many years before taking an implementation with this company.

We have seen ROI. It has saved our organization time.

It has eliminated human errors. There are now more processes where we do checks and controls than we would do with an actual human, because it takes no time for a robot to do the checks. 

We are only using Unattended Robots. Though, I can really see a use case for Attended Robots, especially with these cases where there are a lot of errors. The user could help the robot and we can process the case, instead of having in error.

It is really easy to use and get started with, but if you want to build up more complex processes, you need to have a bit of a development background to make it easier to understand anyone other than yourself.