UiPath Reviews

I am an RPA developer and I am using UiPath to create both attended and unattended bots.

I develop bots that run doing overnight tasks and we can check the results in the morning.

UiPath allows us to scale without having to worry about the infrastructure. It is simple to scale any of the automations that you develop. 

UiPath makes it easy to build automations. It is very user-friendly and they provide all of the courses in the UiPath Academy. We can learn starting with the basics, and it is really simple. One person needs between two weeks and one month to learn it.

This solution provides us with the ability to do end-to-end automation, starting with the discovery phase and process mining. After that, we move to the building page where we have Studio X, and then we can deploy the automation on the cloud.

UiPath has helped us to scale RPA benefits by automating the backup of all of the projects running in the organization. This bot runs every night and reduces our workload for one employee by eight hours, or one day each week. 

UiPath handles all of the infrastructure updates and maintenance, which is really good.

The cloud offering has helped us to see time to value quicker. It has helped us in many ways, including with the automation of repeated tasks. One example is that I created a bot for myself that is responsible for filtering all of the spam emails from my inbox on a daily basis, and then removing them. The first step is the identification and the second step is removing them. This saves me time.

The automation cloud has helped us to reduce the total cost of ownership because we can manage everything through Orchestrator.

UiPath has definitely reduced the percentage of human errors that we have in our processes. In our system, all of the bots follow our best practices so there is a very small chance of error. The reduction in error rate depends on the process. For example, the OCR is not very accurate so the errors are higher but if the process involves an API or SQL queries then it is very good.

This product has helped to reduce the cost of our automation operations. There is more of an upfront cost but it is one-time, and then we start saving.

The best feature is the good community support that is provided in the UiPath forum.

I like that it is a cloud version and runs on Citrix. I used the cloud offering to deploy my bots and manage my Orchestrators.

It would be very helpful for us if they provided more business use cases and helped us to learn them.

We have been using UiPath for almost two years.

There are times when you need to shut down the automation and restart it. Other than that, it is very stable.

I am the only one developing the bots but I am currently training some other people who are just learning it.

To this point, we have not had to scale any of our projects. Our usage of it depends on the project and where we can use automation.

When other features and updates are released, we normally visit the forum to help understand them. I have never used technical support.

I have also tried using Automation Anywhere.

Each solution has different types of bots that are available. One of the differences is that with UiPath, you have Orchestrator to help you manage them.

Generally speaking, UiPath is easier to understand.

The initial setup is not complex. It is easy to deploy and the actual setup of UiPath is not very difficult. It is a matter of downloading the Studio and creating an account in the Orchestrator. Then, you can start working.

My IT team was responsible for the initial setup. Only one person was needed to complete it.

I take care of all of the maintenance.

I am using the Community Edition and am not familiar with the cost of the paid editions.

We do not yet use the AI functionality but I know that it is there.

I have watched some videos on the UiPath apps feature, which lets us create automations in a low-code/no-code fashion. We have not used it yet but this is something that we'll be exploring in the future.

The biggest lesson that I learned from using this solution is that they have a very good community forum, where you can share ideas and learn from other RPA developers.

My advice for anybody who is implementing this product is to start by taking the fundamental UiPath courses from the UiPath Academy. This will help to understand RPA and UiPath.

In summary, this is a good product and I'm quite satisfied with all of the functionality that it provides.

I would rate this solution a nine out of ten.

Most of our use cases are related to business, like reconciliation and reporting. Therein, they have some internal applications to automate SAP automation and Salesforce Automation. Our most recent use case is related to documents, like the invoices coming from customers. We have to extract that data from invoices via different formats, e.g., some are digital formats and some are scanned formats. So, we have to extract the data, which we are doing with the help of UiPath.

We are using both attended and unattended automation. For 90 percent of our use cases, we are using UiPath for unattended automation.

I use UiPath almost every day. When I finish developing one process, there is a new process to develop. If a process is complex, it almost takes six to eight weeks to develop it, then you have to deploy it for monitoring. After that, the next process comes up.

UiPath helps based on how it is configured. In our case, there are so many transactions coming in, it is not possible for a human to complete them in nine hours (working hours). So, we went with unattended bots, which we mostly run at night. We start the bots after the working hours of humans, so when the operations team returns in the morning, their work is complete.

From a developer perspective, the process is smooth and easy. You can find a solution on Google easily. You can develop your own code. From a technical perspective, it is 100 percent.

UiPath Studio is great. It has all the activities. You don't have to write anything. Even after that, if you feel that you have to do something for yourself, then you can write your on-premises code in it and develop your own framework. Everything is there. You just have to use UiPath Studio.

if you are a business user, even if you don't have a technical team, you can install the second version of the Community edition, which is StudioX. This is specifically made for business people who don't have a lot of ideas about technicalities. This is a great feature.

If websites are made in a recent programming format, it is very easy to automate them with the help of UiPath. However, if that technology is based on legacy applications, then it is very fragile and hard to do that. So, we have to choose the technology first, and if the technology is new, then you can easily automate it with other applications or the help of an RPA tool.

The process can be complex if an application is a legacy application or the data is unstructured. The analysis of some bots is lacking. If a customer asks for analysis of a particular bot, you cannot just get the data from the UiPath and give it to the customer. It is not that easy. I would rate this process as a seven or eight (out of 10).

The Document Understanding feature should be more developed and advanced. For example, you have to make a template with their ML model. Currently, we can't use our own ML model, and we have to use the UiPath ML model. UiPath has only a few ML models right now. They should come up with more ML models or make it easier for us to use our own ML model. While they are working on this, I have felt much difficulty in extracting data during our last process for Document Understanding. We had to go with the Python language. So, I think they are lacking in this feature.

After deploying the bots in production, processes are very stable, unless something happens with the machine. You don't have to monitor a process every time. So, I am very impressed and satisfied with things.

We are looking to update to version 20.

This solution is very much scalable. If you are working in a small or large organization, it doesn't matter. It is very much scalable, up to anything.

We have a team of around 100 to 120 people in RPA automation, in which 60 or 70 users have the developer license. 

I am very much impressed and satisfied with the UiPath solution. Earlier, I used the Automation Anywhere solution, and it is sort of messy and complex. You have to pull everything from a single workflow. Then, I moved to UiPath, and everything was very sorted. If you really like coding, you can do that. It gives you a real developer type feel.

Developing and deploying robots with UiPath is very straightforward. It hardly takes five minutes to deploy a process on Orchestrator.

The last process that UiPath covered saved the work of two people.

If you have repetitive tasks, you can apply UiPath and have your people trained to do other work.

If you want to start doing RPA, I think you should definitely go with UiPath because it has the Community edition. You can just install it and check whether or not your process works fine with UiPath. It will be an attended bot, but you can form an idea whether your bot can easily be automated.

We have one use case related to Microsoft Word Automation. Word Automation is not compatible with other tools. However, in UiPath, we were able to write our own code to automate and format the Word document, which is why UiPath Studio is the most valuable feature. We are also using the Automation Anywhere. But, in Automation Anywhere, we cannot write our own code. So, we can't automate Word Automation from Automation Anywhere as well.

Automation Anywhere has come out with its own new version of 2019, which is as effective as UiPath. However, when I have tried to run or deploy the bots, it still lacks in features. For example, in UiPath, AML activities are coming up very frequently. Whereas, in Automation Anywhere, these features are lacking, which is why I go with UiPath. Also, Citrix automation is very good with UiPath. You feel like you are able to detect the elements and images.

UiPath gives you REFramework, which is absolutely amazing for business use cases. Automation Anywhere also lacks this feature. With Automation Anywhere, you need to make your own framework, and if you are making your own framework, then the look becomes messy. If someone is trying to understand it, then they have to spend more time on the framework to understand it.

I use the IQ Bot of Automation Anywhere, and even after training a hundred documents, it's not picking up or extracting the data from documents. I feel like I have to train the model again, which is not the case with Document Understanding. If you properly make the templates in Document Understanding of UiPath, it gives you full text values. So, it is more advanced and suitable for me.

We use UiPath Assistant to run processes about 10 percent of the time. Most of the time, we are using Orchestrator. 

UiPath releases new features every 15 days to a month. They have already come up with AI and machine learning.

If scanned documents are coming in for some of the work, we are also using Python language for this.

If you already have a technical team, then you can ask them to look into UiPath Academy. If they have basic knowledge of programming or coding, then even in seven days, they can easily learn UiPath and start applying it in their organization. You don't need to hire outside developers.

Overall, the solution is a nine (out of 10).

We are a UiPath customer, working with them to develop some products. It is a bit of a mixed thing where we are developing some products with them from scratch, but they are acting as the provider. We develop things, and if they're useful for others, then others can use them.

We are doing some pretty bespoke things to help us develop some solutions, but also help them develop their UI solutions in the legal area. We are working on a few things with UiPath to develop some search robots, some solutions to automatize subcontracts, and some timekeeping entries. These are several things that we are doing right now.

We are doing three things with them:

1. A robot to help us with software for time management, automating time entries. 
2. A robot to help us with filling in our engagement letters (contracts). 
3. A robot to help us with various public searches, i.e., the automation of searches of the public record.

We are adjusting robots from similar things that they do. The robots are not yet in production. 

The most valuable feature is its ability to save time with a task. In general, it improves accuracy as well.

UiPath's ease of use for automating our company's processes is a five out of five. We have found it very easy to talk to them, identifying what can be done along with the potential use cases. They have been very good at guiding us through what is realistic at this point, how their robots could help us save time and improve accuracy, and how our users can engage with their robots, e.g., ensuring that users engage with the robots and use their product. 

When we started to talk about practical implementation, their team was extremely switched onto identifying and fitting their product to our needs. They explained to us how we can use their products, what can be done to adapt their product, and what may happen sometime in the future, not necessarily now. I found this very helpful and straightforward.

What we have in mind in terms of what the robots could do for us is significantly more than what UiPath does now, but it takes more work. From my perspective, there is just a wide scope of implementation that goes beyond what we're starting right now. That is essentially the improvement. While I have nothing negative to say about our experience with them so far, I think we can work to develop more complex products with them. They are already working to develop something for our use cases, but what I would like is if we could develop more things for more complex needs, e.g., where we start with simpler stuff, then we can add things to what we're doing now.

We are in the development phase.

It is too early. We are still in development.

During the development phase, there are five people involved in the development phase. The users will be about 100.

We have not used their support.

We were not previously using something in this area. 

We have been thinking about ways to streamline our activities using technology. It happens that we knew UiPath, so we started to engage with them about what they could do for us. We had something like 20 ideas that we could implement, then we just started the easier ones which were closer to the products that they have. As things go, we will see whether we expand to other things.

We have known UiPath quite well and for a long time. They are also the leaders in the field, so it was a very easy choice.

The initial setup was quite straightforward. We started to discuss potential solutions, then we met with parts of their team, developing that business area. After that, we met with the technical people designing the product. We had a couple of initial conversations and did some testing. It has been extremely simple and straightforward.

We are supposed to review some of their proposals and provide feedback. We are probably a week or two away from production.

UiPath could have probably implemented the solution in a couple of weeks. We had some delays on our side.

We did the initial setup ourselves.

It is important for whatever we implement that it's cost effective in a sense that the robots will replace some human time. If human time costs less than the robot, then that's not a good deal. Normally, human time will cost more than a robot, and that's what we're trying to displace: the human time. We want to replace it with a cheaper robot. 

We only looked at UiPath, because we know them quite well.

So far, the experience has been excellent. I would rate the solution 10 out of 10, but we haven't finished the implementation.

Look internally what your needs are. Try to identify what you could improve with software robots, ensuring these needs are clearly identified and the product is fit for purpose. Also, you should make sure there will be buy-in in the organization, so people will actually use the product.

We have a system to create a multiple orders to perform automation testing. Here, UiPath helps us to create a bunch of orders without the hassle of creating a separate automation suite for this need.

When creating orders manually became a tough job for the user then it needed a benchmark for us to resolve this kind of situation to make teams more agile at work. This motivated us to find a solution to counter this problem in our organization. Definitely, it has helped to make us more agile. 

UiPath has helped us to achieve our goal as we are able to do what we intended to with automation. We are now dependent on UiPath to create the orders instead of having to do this manually. Earlier, this used to happen in a very traditional way and it was time-consuming, but UiPath has helped to perform this task with lightning speed. Now, we have more focus on implementing other things smoothly. 

Scraping data from the application using OCR and other text validation features is amazing in UiPath. These have helped us to create a reliable solution for our needs.

UiPath support needs to be a bit quicker than it is currently. They need to be very quick when they see a customer is struggling with something and taking the step to contact support.

The UiPath team needs to put some effort into improving the support section online. They should also improve the UiPath community forum so that beginners can receive help with activities that they require. 

I have been using UiPath for the past eight months.

Stability is a part where I would definitely rate UiPath a five out of five. It is really the best among all RPA products in this regard. 

We have a small flow that we have automated, but I feel UiPath will not let us down if we increase the capacity.

This is a part where I really think that UiPath needs improvement. They need to take up the issues from customers very quickly and resolve them on the highest priority.

We had not used any other RPA solution before UiPath.

This solution is very easy to set up. There is a bit of a hassle if support is expected from the UiPath team.

We have implemented using our internal team.

Significant manual efforts put into tasks have been reduced and a good amount of time is being saved. Overall, our time savings results in ROI.

The setup cost is minimal as far as other options are considered. 

We did indeed evaluate other options before choosing UiPath. We thought to use Automation Anywhere for our RPA needs but after doing some research, we chose UiPath.

During the evaluation process, we found significant failures when performing tests on exactly the same tasks.

UiPath is the most amazing RPA solution available in the market. Certainly, this gets plus points when it comes to feature versus cost ratio. Therefore, I would highly recommend UiPath because it comes with more stability and reliability than other solutions.

There are some features like different types of recorders. For example, Citrix and desktop are the variants we have in UiPath to solve our problems.

Other than the issues with technical support, I think that UiPath is a complete package for automating solutions in a rapid and fast environment.

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.