UiPath Reviews

It is for automating tasks that are not meaningful for people to do, tasks that are menial and repetitive. The University of Copenhagen, where I work, is an old institution and we have a lot of different legacy systems that don't work well together. So, we have a lot of people doing administrative tasks that depend on moving data from one system to another. We use UiPath to automate these repetitive tasks and make the robots carry them out, so our people don't have to.

For example, in the case of our most recent robots, there were a set of tasks where three people had to print out 3000 PDF pages, then sort them into seven different piles, then sort those different piles into three different piles each. Afterwards, scan them and send them to different systems. We made this better. Instead of three different people taking a whole day, we did it in three minutes. This is an example of a very concrete, administrative task based on legacy systems, and we made it simpler. This was a huge improvement and positive thing for our company.

It is very easy to make beautiful, clear, well-documented workflows that clearly reflect the process. This is an achievement that is not always feasible with regular code. Even though each activity in UiPath is like a line of code, the user interface in Studio and the use of states, flowcharts, and sequences make it so easy to understand the overall process and get an overview of what is actually happening.

UiPath is easy to use, and it CAN be used by non-programmers, but it is even better to use for programmers. It allows us to make very robust and effective solutions because we have all the functionality of the powerful .NET Framework library within reach, all while the UI makes it possible to create truly beautiful solutions.

I would like UiPath to have a build-in method which informs the robot's process owner how it has managed its transactions and performed through the night. If the robot had a process that was set up for a 100 transactions, and two of these transactions had an application error, four had a business error, and the rest were fine, I would like a straight up method for the business owner to login somewhere and see what the robot managed to do and not do. There should be a method for accessing and logging into Orchestrator and see the logs for only one process, and this log should be presented in a way that makes sense for non-technical people. 

The stability is good, I've never encountered any major problems. UiPath works with websites and systems which are famously unstable, but it gives you the tools that are necessary to deal with hiccups and if something is not stable. So, if you add proper error handling to your robots, it works.

Out of the robots that I have built, three or four have had to perform on several machines at the same time. I haven't encountered many scalability problems, but then again I haven't built robots to perform on a 100 machines or anything near that. 

The initial setup was quite complex. I was not in charge of the task, but my colleague set up the whole infrastructure and mentioned some problems. He corresponded with the support team, and they did figure it out, but the setup guide was definitely more complexly written than it should have been, and some things were written in the wrong order. So, there were some hiccups in the implementation.

In our company, RPA doesn't necessarily mean less people will be hired or people will be fired. We probably won't see the ROI in cash. It will help with workplace productivity, and job satisfaction, though.

We were looking at Blue Prism and UiPath. 

UiPath is nicer to work with. The developers especially wanted to work with UiPath, but the business team was looking more at Blue Prism. However, UiPath was better for the slightly larger robots, which is good for a lot of Unattended Robots.

From what I have seen of Blue Prism, UiPath is both more aesthetically beautiful and stable. Based on .NET, UiPath makes sense as a solution.

Start small and make time to do things right from the start. The infrastructure and developer culture can vary massively from one RPA team to another, and it is really important to establish healthy code guidelines, test and operation manuals, etc. from the start. At my current company we are just starting up, getting everything right, which is very exciting, and I can see how different (and better) we are doing things that at my previous employer.  

Primary use cases would be within the finance sector. We supply financial services for other government agencies. The main robots that we have in use right now are concerning floating of financial periods, uploading reports, commenting on these reports, and so on. We are starting to look at invoice processing, to a larger degree. Then, we have a few quality and control robots which do checks on data quality, customer information, customer carts, etc. 

We are using approximately 20 robots right now for different uses.

We've opted for professional, traditional developers and programmers to do batch robots. We don't use it in our business units. Possibly because we are a government agency, we don't necessarily get enough IT security around the users applying their own robots. 

It is not easy to use in this way because we do use traditional programming skills. We are considering moving some tasks out into the workforce for Attended Robots, etc. We think that this will be a problem for us in regards to getting it pushed out there and still maintaining good quality. However, we haven't tried it yet.

We are able to smooth out peak workloads. Because with a lot of the period closures, like monthly and yearly closures, we work in peaks. Everything has to be done within a few days. When we can prepare a lot of the data and reports through the night, the employees can start on those in the morning. Therefore, we are leveling out some of the workload features, which is one of the main benefits.

Automation technology for us is mainly a way to get around the long-term IT projects. This is the future for us, when using UiPath, to start moving into the AI part of it. In addition, the bundling of the offerings into UiPath is quite important, so we don't have to go to several different vendors. We can try it out on our own and see if this is something we want to do. Then, we might bring in another partner or vendor to do some specialized training, debug the networks, etc. We're never going to get that capability ourselves. We don't have a large IT department nor do we have data scientists. For us, it's important that one or more of these skills are getting baked into the system.

The ability to integrate between legacy systems is the most valuable feature. We use it mainly to replicate manual processes, where you just have to pull out data or pull down large volumes of customer information, in general. We work across many individual customers, who are individual entities or individual databases in our ERP system. We work across about 220 databases. Therefore, the task of logging onto different databases alone is quite cumbersome.

The main thing is to make data available to the employees when they start working mornings, instead of them starting drawing out reports to see if there is anything that they need to act upon. With these legacy systems, which work on a one-to-one basis, we tried to batch process them a lot more.

We have looked at it with Citrix, and there are problems with it. Some of the new features coming will address it.

We have been looking at Attended Robots, which result in the inability to lock your screen. That is simply a no-go for ever using them in most government agencies, as IT security will prohibit us from using them. If UiPath wants Attended Robots to be used inside a government agency, it needs to be applicable on a virtual desktop.

A lot of what is coming is what we are looking towards: Both on the skill set with computer vision, but especially also on the enhanced identity management and security. The ability to debug and lock at a less complex level for us to look at. 

One to three years.

UiPath's stability is quite good. We don't see any problems with the stability of the platform application. All our problems stem from the basic systems that we operate on, which are quite vulnerable to network problems, time outs in various systems, etc. However, these have nothing to do with UiPath. Perhaps some of the things which are on the road map will help with the debugging of some of these issues.

One of the things that we are lacking right now is not stability, but usability with debugging, e.g., when you can't see what went wrong. We have to look through 50,000 pages of logs or so. 

The scalability is quite good. 

The main problem around scalability is the licensing structure and the inability to dynamically assign licenses across robots. While I know this is coming, this is our main gripe with scalability: the licensing structure. Because we are part of a larger setup with our own IT supplier, who does a multitenancy setup with Orchestrator, to have more flexibility with the use of licenses would be very valuable.

We are using virtual desktops to deploy and run the machines with robots. It is necessary, as we cannot scale it on individual on-premise machines.

We have used the customer support. Our main issue with them is they need to understand the problem that we are writing about, and not reply too soon with a standard answer.

All our developers are using UiPath Academy and are RPA certified. While they like some thing, some of the frameworks which were used in the Academy examples, the developers didn't agree with. This is probably because they are IT professionals themselves and are used to doing things a different way. Whether it's because the use case wasn't good or they were just used to something else, this was the main gripe.

The product has a lot of backing from our director, who has been pushing the agenda. To be able to stay relevant, even as a government agency, we have to reduce our costs every year by two percent. To be able to produce that, we need to be more efficient at what we do. The target is: Not to reduce staff, but keep up with the increased demand for production and costs.

I wasn't part of the very first setup.

We mostly did the deployment ourselves or with our own IT partner, who is not a partner of UiPath. So, it has mainly been done by our own IT people.

On the individual robots, we do have good return on investment. However, once you add in the governance, including when we are scaling up the solution and the maintenance of robots, then I don't think we are at a break-even point. This upcoming year, we are expecting positive ROI. For us, the return on investment is high quality data. 

It has helped us to eliminate human errors. We have a robot that is specifically requested to avoid, for example, uploading reports on the wrong customers because of GDPR cases, where data protection officers will have to get involved, even though, it's not sensitive data. We have seen problematic use cases drop from a couple of incidents from maybe 100 transactions to zero. We are looking to completely eliminate errors in some cases, not just reduce.

It has saved our organization time. We use the robots to try to address some of the peak workloads that we have. They are not there so much to address a certain number of hours that we want to save. We want to be able to use the robots to help address our customers' needs during designated time frames to reduce extra stress on our employees.

We would like to see improvement around the licensing and multitenancy. 

We also evaluated Blue Prism and Kofax Kapow. The reason that we went with UiPath has a lot to do with scalability, as our IT supplier has committed to a multitenancy set up, which was not possible with Blue Prism. 

We are quite happy with UiPath. We are not looking at other vendors at the moment. They are all offering similar solutions, but with a slightly different focus. We could use any other solution, but the development is so fast that even changing now would be no guarantee that we end up with what we want, because everybody is moving at a pace where we can barely keep up with the development of the products.

Try out different vendors and their labs. See how it fits to the processes that you are trying to automate right now. Some applications are better at old mainframe systems, and if that's what you will be focusing your efforts on, then maybe UiPath isn't the best vendor for you. There are others who focus more on that sort of environment. So, be realistic about what you want to automate, and choose your use case initially from that. 

We see the biggest benefit right now from Unattended Robots, but that's all we use. In the very long-term, Unattended versus Attended Robots will be able to generate a greater benefit. However, with the current licensing costs, they will need to change for it to be a positive business model. We have to be able to move licenses from one person to another. If we have to apply a fresh license to each person in the workforce, with our budget, it will not be possible.

Our use cases for UiPath AI and automation are diverse and cover a number of functional areas within our business. We are doing everything from building simple to medium to complex RPAs. 

We have started utilizing communication mining and have a unique use case leveraging document understanding. Essentially, we are getting our feet wet across the board.

UiPath has allowed us to free up time for our employees so that they can engage in more value-added activities. Although cost has not been a significant driver, we focus on being more efficient and consistent throughout the organization. 

It has enhanced the overall experience for our stakeholders, including employees and customers, by streamlining processes and improving engagement.

Document understanding has been immensely valuable due to the breadth and depth of its application. Additionally, the potential of Generative AI is expected to drive significant value.

Since we are still in the early stages of using UiPath, identifying areas for improvement is challenging. We anticipate that some aspects may emerge as time progresses.

We have been using UiPath for close to a year, approximately ten months.

The solution has been stable so far.

UiPath has proven to be scalable.

We have received excellent customer service and support from UiPath. We have a good Technical Account Manager (TAM) and a strong relationship with the team managing our account.

Positive

We previously used Power Automate and other solutions. Most automation has transitioned to UiPath. We switched due to the fact that UiPath offers a broader range of functionalities and addresses our speed-to-delivery challenges.

The initial setup of UiPath was straightforward, thanks to a good partner.

We have been using an implementation partner, and they have been great so far.

While we have not yet achieved the ROI we expect, we are on target to do so. There have been some instances of ROI, although we are still in the infancy stages.

Typically, pricing is reflective of the value provided. While more value for less cost would be preferred, we do not focus extensively on costs.

We evaluated other options before choosing UiPath. It seemed best in class and fit our needs after due diligence.

I would rate UiPath a nine out of ten.

I'm a network engineer at a nuclear power plant, and I oversee multiple crews. I use UiPath to automate the voicemail system, send alerts, and run tests. Our company has about 12,000 employees. 

UiPath has helped to reduce labor costs. 

You can set up processes using macros without basic knowledge of coding.

The hardest part is popularizing UiPath among our employees. 

I have used UiPath for around a year. 

I rate UiPath nine out of 10 for stability. 

UiPath is scalable. 

The South Korean team uses Blue Prism. That's a good solution, but it's too hard to use. 

Deploying UiPath is easy, and I'm teaching my crews. 

It's worth what we pay for it.

The cost isn't important because a good solution isn't cheap. 

I rate UiPath nine out of 10. There are still many other RPA solutions we haven't tried, so I can't say it's the best. 

We use the solution for automation. It helps with Excel automation, validation, data extraction, et cetera. We use UiPath for a client project we are working on. 

It's helped improve the organization via an increase in ROI. The employees are much more productive and they no longer have to do repetitive, tedious tasks. 

The product is very user-friendly. It has great drag-and-drop features. My background isn't in computer science, and it was easy for me to get familiar with UiPath and the user interface. 

You can do almost anything related to automation. If it's related to email. databases, Excel sheets, et cetera. There's nothing that needs automation that can't be done on UiPath.

It's very easy to build automations. We can easily build end-to-end automation. We had a process, for example, that needed to be triggered once an email was received. The attachments needed to be downloaded and processed and a reply had to be sent back. UiPath could handle each one of those tasks. 

The user community is pretty great. You can find an answer to basically any query. You can participate and reply as well. 

I've used the Academy courses to learn more about UiPath since I started using the product in May. I started with the foundational course and then did the advanced course and action center and document understanding overview course. It's helping me learn everything fairly extensively. 

The solution has helped us speed up digital transformation. They have enabled very fast digital transformation to meet a company's needs.

It helps reduce human error. I've helped deal with processes that would require employees to deal with thousands of forms. Using UiPath can reduce human error quite extensively. If there was a chance of human error at 25% before, it's been reduced to a maximum of 2% to 3%.

The solution helps free up employee time. The employee, in turn, can be more productive and learn new things in the meantime. It's likely freed up more than 30% of employee time so far. 

I've only used the solution for six months so it is hard to consider improvements. It would help if there was functionality whereby you could upload something like a flow chart and the solution could process steps according to the flow chart.

I've used the solution since May of this year. 

The solution is stable. From what I have heard from my team, it's almost always stable. 

Our clients are large-scale enterprises. 

It is very scalable. You can add or change things as needed and update processes as necessary. We do have quite a sizable process that involves ten to 12 departments and it works well. 

Technical support is responsive. They were very kind when I dealt with them.

Positive

I've used other platforms such as Power Automate and Automation Everywhere. UiPath is a lot better as it is very high-level. 

I did not directly deal with the initial deployment. 

There is not too much maintenance required. 

Clients have noted an ROI. They've found employees are much more productive. 

I haven't seen the pricing or dealt with the licensing of UiPath.

However, I have heard of clients switching to Power Automate due to the fact that it was cheaper than UiPath. 

I do not exactly use the AI functionality. It's not part of my job at this point. 

I'd recommend automation for digital transformation. As for which platform to use, it would depend on which processes they need to use. UiPath is quite suitable for mid-level to large enterprises.

I would rate the solution nine out of ten. It's an excellent product. 

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 use the solution to automate our processes. 

The tool's most valuable feature is its embedded activities. 

UiPath needs to be easier to use. 

I have been using the product for two years. 

I rate UiPath's stability a nine out of ten. 

I rate the solution's scalability a nine out of ten. 

The tool's tech support is good. 

Positive

I have used Blue Prism before. 

The tool's deployment was easy. 

A consultant helped us with the tool's deployment. 

We have seen ROI with UiPath's use. 

The tool's pricing is fairly reasonable. 

We wanted to minimize manual work so that our employees could utilize their time efficiently. 

The solution has helped us save employees' time and money. 

I rate the product a nine out of ten. You should utilize the training, practice exams, and all other information in UiPath. 

My previous company was a share market or brokerage company, and we used UiPath for the client's reports. We used automation to get the records of their clients and get their financial reports in the desired manner. We go to the company database, get the proper data of the clients, and arrange it in the desired manner of our company's officers or the manager for the back office or the accounting department.

We arrange the data in a particular manner. We give it to them so that they can analyze and get the record for themselves, analyze their market reports, and get the desired result. We use automation to get the data in the Excel database so they can use that data in a particular manner for the future aspect of the company's client.

My current organization is a service-based company. Our client is a US-based company that manages the insurance portal of the US. They arrange the insurance portal for their US insurance client. We go to their particular portal and automate it, get the desired data, and save it to the database of the client's company.

Firstly, we used Excel for database use. We are currently managing SharePoint using UiPath and arranging the data on SharePoint, where all the clients can access their data and save the record on their own.

In my previous organization, one process took a person two to three hours to complete. With automation, that process could be done in only 15 minutes. Two to three hours of hard work could be utilized with another process, and the person is free from that particular complex process. In my current organization, the user needs to log into every portal, get the details, and arrange data in a particular manner.

It took almost four to five hours to get all the insurance details and fill up in a particular manner. This process is now done through automation within one hour or half an hour so that the person can utilize that time with other work. UiPath automation provides optimization, accuracy, and a three-fourth reduction in working time. Compared to other tools, UiPath automation immensely helps a person or an organization.

The most valuable features of UiPath are Excel automation and web portal automation. There are many complex details and works in Excel that the operation department does manually. They arrange the data in formulas or in a particular manner. Through automation, Excel work is done very smoothly.

After that, we can arrange the data and save it in the desired manner. When using the web portal, the manual person needs to go to the portal and get the desired information. With UiPath, a lot of work has been done through automation so we can get accurate data in the desired manner.

UiPath is a user-friendly tool compared to other automation tools. UiPath can be made easier to learn. There is a lot of complexity in the things we can do in UiPath, like connecting to an organization's databases or using APIs in the process. We are now using SharePoint. There can be more simpler things to connect with SharePoint. We have to go to the SharePoint website, get the client ID or the user ID, put it on UiPath, and then connect every time we start the process. So, there are a lot of things that can be simplified.

I have been using UiPath for more than three years.

UiPath is much easier to use. Stability-wise, the solution has a lot of scope because there are many complex things in other tools. UiPath is a stable solution.

I was involved in the solution's deployment. We had some difficulties at the start of the deployment process. Firstly, we deploy our code on the UiPath orchestrator. But there is a lot of complexity to organize that orchestrator through our organization. We found the solution by deploying our codes on our own Windows server and running it through them.

At first, we did all the R&D on deploying the code ourselves. Then, the DevOps team came in, and they did the rest.

It doesn't need a lot of people to deploy because it is easier to do once you understand the deployment.

We are using on-premises servers to deploy our codes on UiPath. We are using our own server to deploy the code for automation.

Not much maintenance is required for the solution from our end. We deploy the code on the server, and the process runs smoothly after the deployment. However, if there is a change in the process, website, or the way in which we get data, we need to make necessary changes to get the data in a particular manner.

Although I am an engineering person, I was out of touch with technology for eight years. However, I didn't need proper experience to use UiPath because UiPath is a coding-free platform. We can learn UiPath even if we don't know coding. It can be difficult if any nontechnical person wants to learn UiPath, but they can properly understand the UiPath. Other automation tools like Automation Anywhere or Blue Prism are complex tools. But UiPath is the most user-friendly tool for automation.

One process in my previous organization took two or three hours to complete. A person needs to sit at the table and do what's needed for two or three hours, which is a complex process. Once automation was introduced in our company, the process was done in only 15 minutes with accurate data and reports arranged in the desired manner. People don't need to sit at the table for two or three hours; they can be utilized for other things.

UiPath enables us to implement end-to-end automation. In my current organization, I use web portal automation to log into a particular website or portal page and deliver the data to a person who can share the data with higher management. There's no need for human effort to arrange the data for that particular person.

There's a UiPath forum where people can go and ask questions. They connect you with the proper answers as much as possible and give you the proper solution to your problem. Communication with UiPath's user community is much easier.

I've done the foundation course from UiPath Academy, and I'm currently pursuing the advanced certification from UiPath Academy. UiPath Academy courses have benefited me a lot. I was out of touch with technical things, and UiPath was almost a new thing for me. I learned a lot of things through UiPath Academy. It helped me a lot because I learned many things from there and implemented them in the processes.

We are not currently using UiPath's AI functionality, but we are considering using it in the next one or two months.

UiPath has greatly helped reduce human error because UiPath performs the processes accurately. A lot of complex operations are performed on Excel. Through UiPath automation, all the permutations and combinations are applied, and we get accurate results.

UiPath automation has saved us a lot of time because the process takes almost half the time to get things done.

Overall, I rate UiPath an eight out of ten.