UiPath Reviews

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

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

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

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

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

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

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

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

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

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

Its stability could have been better. 

It was installed around September of last year.

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

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

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

We did not use any solution previously.

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

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

It does not require any maintenance from our side.

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

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

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

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

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

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

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

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

The most valuable features include

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

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

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

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

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

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

I have been using UiPath for nearly three years.

The LTS version is very stable.

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

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

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

Positive

Setting it up is very easy.

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

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

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

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

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

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

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

I did a proof of concept for a music industry client. It went well, and the client adopted UiPath. 

UiPath improved lots of features, like sequencing, recording, etc.

I had some issues with the ERP Automation features, and the setup is complex. 

UiPath is stable. 

UiPath projects are highly scalable. There are lots of customization options and ways to easily scale your existing bots. 

I haven't contacted UiPath support because the solution is stable and doesn't require support in most cases. The UiPath community is strong, and you can find answers from multiple places online. 

As a project consultant, I analyze the client's applications and set up everything for them. The initial setup is time-consuming. UiPath involves a longer setup process than other RPA tools.

I rate UiPath a five out of ten for affordability. UiPath costs a bit more than other tools like Blue Prism and Automation Anywhere. 

I rate UiPath a seven out of ten. UiPath offers many customization options. I would recommend it to clients who want to do high-quality processes and complex use cases. You also must consider your budget because the license cost is a little higher than average. 

Our biggest use case right now is around business development. We use UiPath to run reports that we get off of the internet against our internal databases to try and find anyone who is a client because we're a law firm.

Most of my development right now has been on the business development side. We're helping clients with their cases, whether it's a litigation case, a bankruptcy case, or a real estate case. I use UiPath to help identify potential clients or current clients so that we can help them in their legal space.

UiPath has helped to alleviate some of the workload of our paralegals, assistants, and secretaries. They were going through large files of cell rows, and it was taking up many hours of their day. Using UiPath, I was able to automate a lot of it so that they don't have to spend that time. Now, it's more of a review process as opposed to a daily, mundane process of going through Excel files.

On one of the other processes that I developed, a marketing assistant had to take another daily report, and check to see if any of the companies that were filing for litigation on that report were clients or prospects. It took three hours of her day every day, and it's done five days a week. Now with UiPath, I have it unattended and running at 5:00 a.m. so that when she gets in, all she has to do is review the report that I generate for her. That's a consolidation of what comes off the website, what we have in our internal systems, and anything that matches.

I do all my developing in Studio. I develop and publish into the orchestrator cloud, and then I try and run everything unattended. So, Studio is a very valuable feature for me.

Another feature that I've been using a lot is the new integration app with Microsoft that triggers emails.

The UiPath Academy courses are great because when there are things that you don't know right off the bat, it helps you develop, learn, and grow within the platform. I've done a few courses and plan on doing more. It's definitely helpful for me being someone that didn't come from a development background. I taught myself UiPath in the beginning, and now that I know how expansive the Academy is, I'm definitely going to take more classes so that I can learn exactly how much I can do with UiPath.

I would like to see ongoing integrations with different applications. For example, we have UKG, which is an HRIS or HCM system. I'd love to see if there could be some sort of connection there because there are definitely some HR tasks from onboarding and offboarding that we do in the HCM that I'd love to have UiPath help with.

I like that UiPath is a platform for more than just one specific product. So, I'd like to see continued expansion of the platform and have different APIs connected to it. Different integrations sitting on top of it are just going to make it more beneficial because you'll be able to have everything come into one spot instead of having to buy four or five different products.

My firm has had it since 2019, and I've personally used it for about a year and a half. 

We're in the cloud and not on-premises, and I think the cloud runs pretty well. Up until last week, the stability was great. 

Last week, I had an issue with one of my licenses falling off of the unattended robot. I was surprised that it happened. I don't really know why it happened, and I'm working on getting it fixed.

The scalability is great. There's definitely a lot of potential for it to scale, especially in our environment.

They support infrastructure and not development, which at first was a little bit of a bummer for me. Their tech support has been great when it does revolve around infrastructure, and I'd rate them at eight out of ten.

Positive

We found a couple of clients using the UiPath processes with respect to business development.

I think the pricing is reasonable. I don't think it's too much of a stretch, and I think it's where it should be.

If you have a lot of paper processes or routine processes that are weighing down your employees, then UiPath and automation, in general, are the way to go. There's fear that it's going to take over the human role, which it just doesn't. From a 500 foot view it kind of makes sense, but when you're developing and working on the automations, you realize that you really can't get rid of the human aspect of it. This is because there are always going to be some sort of checks and balances as well as things that the robot can't do and decisions it can't make. So, don't have that fear and push away from automation or UiPath. They go well together, and you should definitely consider it.

Overall and considering the usability of UiPath, I'd give it a nine out of ten. I think there's a lot of documentation out there with the forums and with partners that support as well. UiPath does a really great job, and I'm happy that my firm decided to purchase its product.

We're currently rolling out some of our first few automations. So far, it's been in finance and procurement. We're just automating some of their inventory processing workflows.

The automation will be unattended. We have three that are in active development and another six in backlog awaiting development.

The first few automations have definitely had an impact already. One that we're rolling out, we anticipate having a great impact. One that I'm currently working on should probably have the biggest impact so far on one of our departments. It will save us time and therefore cost. It's a very manual process with lots of human error opportunities. Between how much faster it's going to happen now and how it will be 100% accurate, we anticipate seeing a huge benefit from that.

I appreciate the infrastructure. There are numerous platforms through which we can perform automation. We are in the Microsoft sphere, and so we have the opportunity to use the Power Platform to do lots of automation. However, I've been impressed with the infrastructure that UiPath provides in developing, publishing, and rolling out these automations and then being able to monitor and manage them effectively.

The community can be helpful. In the public forums, I have seen some forum threads that are very active with lots of people that respond with great answers and great context, and multiple options. That said, there are just as many cases where no answer is ever provided, and it just disappears into obscurity. I've had multiple of those types of approaches myself, where I've posted questions and gotten no response. The community can be helpful. For somebody like me that wants to get something out of it, I would also need to be willing to put something into it and help others answer their questions, as that's how the community works.

For the most part, I was impressed with the Academy courses. They did a great job of introducing me to a new piece of software I hadn't seen before and establishing some familiarity with it. The instructor-led training from UiPath, allowed me to put into practice some of the things that I had learned in the Academy. 

The biggest pain point we've seen so far is that we have trouble identifying best practices in certain areas and circumstances. There is no shortage of resources in the Academy and on the forums that have great information. That said, a lot of them are specific to use cases, or they're too generalized, which makes it difficult to know exactly how we should be handling a certain scenario or just some basic things about how to best set up the folder structure for our given environment.

It's been difficult to navigate that as it is still so early in our implementation of RPA. We want to ensure we're doing it right to establish a good foundation from which we will build all of our future automation. We are constantly concerned that we're not doing something the right way.

During a UiPath conference attendance, I really appreciated having access to experts directly. I can just ask them, "Here's our scenario. In this context, what's the best practice?" And I can get a straightforward answer. We don't have access to them outside of this conference. I don't always have the time to watch the videos or go through the multi-hour-long training to get to the one best practice that might be nested inside a larger training.

Finding some of the answers ourselves is difficult since they are contingent upon our scenario and the context we're building. There's not a one size fits all. To that end, it's no surprise that there's not going always to be a single solution that can just be published to say, "Always do this, this way." Without that context, we really do need to be able to talk to somebody, and we haven't had that yet.

In terms of the UiPath community, I probably can't answer a whole lot of questions since I'm so new; however, for a community like that to function and succeed, there have to be enough people with the expertise that are willing to put in that time for free. In a realm of automation that touts itself as a solution for people who have no time, it's no surprise that there are not always people that are willing to sacrifice what time they don't already have to begin with to give out free service.

Once I have automation ready for production, I don't see a way to deploy that to a production tenant environment without manually recreating everything. In a typical development environment in software development, you develop in one area, and then when it's ready for deployment, it's packaged up with all of the assets and everything that it needs, and then you deploy it to the production environment. You do some final testing to ensure the deployment takes, and you're done. Whereas here, it seems like I'm having to recreate everything manually. I can import the automation, yet I need the whole structure and orchestrator and all of the assets (75), and I have to recreate everything manually. It seems something is missing. 

I just started using the solution three months ago. 

The solution is pretty stable. That said, that'll be a question better suited for me in about three months after we've had our bots live. Since we're only in development and testing them in pretty controlled environments, it's harder to tell. It seems like it would be pretty stable. However, I can't answer that fully.

From what I understand, it scales well. I understand that's one of the directions that we see ourselves going. We'll be taking on more and more automation and scaling up quickly.

I haven't had any technical support directly from UiPath yet. I've only learned that we can request a technical account manager, and I understand that we don't have one right now. I'm not sure what additional cost that may incur, either. It's always that question of the cost versus the benefit. That's what we need - that technical expertise from somebody that can have a short conversation with us and help steer us in the right direction.

I have worked in the Power Platform with Microsoft. That is not specifically for RPA, per se. However, I've worked in it and have familiarity with it. 

One of the biggest pros for sticking with Microsoft would be that we're a Microsoft shop, so it would keep all of our solutions in the same realm. We wouldn't have to export and import data across services and databases. It would just all be under the same umbrella. That's a huge benefit of sticking with Microsoft.

With UiPath, there's a stronger infrastructure that supports the development, maintenance, and scale of automation versus Microsoft. However, Microsoft is still pretty new and young to the RPA development environment, and they move very quickly. I would expect that they are not done developing their RPA suite either. I imagine that we'll see future iterations where they become a stronger contender to what UiPath provides.

I was not involved in the initial setup. That happened before me. 

We have yet to see an ROI since we don't have any of our automation fully live. We anticipate an immediate return as soon as these are in production based on the countless hours that will be saved from people's workdays.

The licensing is a headache. Luckily, I don't have to deal with it directly. That's above me. As a developer, I have to deal with the licensing just in trying to build new automation and ensure that there are licenses available to be allocated at runtime. That alone is just obscure enough to make it complicated and leave me unsure as to if I've set it up correctly.

I'm an RPA developer.

We do not yet use the AI functionality. 

I would advise potential new users to make sure they know what it is that they want. In our case, we need to choose between the options of sticking with the Microsoft Power Platform or going in a new direction with UiPath. Even though the Power Platform could potentially do everything we need to automate, it's not apples to apples against UiPath. If what your need is better suited to one or the other, don't force your solution into one product.

I'd rate the solution eight out of ten. I'd rate it higher. However, there are technical issues that I've encountered and a steep learning curve. We've had difficulty in finding the specific answers we're looking for and lack access to technical experts that can answer complex questions, pricing, the ambiguous nature of the licensing, and how those get provisioned. There are some core features still missing.

I use this solution for mortgage loan origination, loan servicing, and IT administration. I'm currently using version 21.

We use the solution on-premises.

UiPath saves us a lot of time, which translates into operational cost savings. We saved around $40 million in operations last year by operating 140 bots in production. UiPath saves us costs, improves compliance, and helps with scaling up and down our operations.

We use attended automation but not on a large scale. We have three or four bots.

Attended automation improves our ability to automate processes that are more complex or involved. We use attended automation for use cases that involve websites that require actual users to log in. It's really helpful because a lot of use cases deal with federal websites and external websites where we need to download client information, credit reports, and fraud reports. That kind of information can only be done by a human, so attended automation is necessary for those types of use cases.

Right now, we aren't completely into AI. We explored document understanding for text extraction, and we know the capabilities. We haven't even started our ML journey, at least from the RPA automation perspective. They're still in the robotic process, so we haven't moved to include automation.

This solution speeds up digital transformation and reduces the cost. It gives leverage for the teams to transform digitally, because the traditional digital solutions take a long time to set up. It can take a few months for a solution to be in place. That requires expensive or complex application upgrades or IT application support to support the digital transformation. If we wanted to add a new app that would have oversight of all the loans being originated, it would take between two to three months to build UIs, dashboards, and all the features around it. With UiPath, the same kind of overview can be set up quickly: within two to three weeks.

The solution absolutely reduces human error. Most of our use cases involve looking at the input data, doing calculations, and updating fields. That always needs to be done by a human, day in and day out, continuously throughout a work shift. This RPA solution reduced that piece of human error drastically. I would say that more than 99% of human error is reduced.

The solution freed up employee time so they can work on other useful tasks. That's one of the main advantages of this solution.

Some of the processes have to be performed after hours and over weekends. When those tasks are automated, it gives valuable work-life balance back to our employees so they can do something useful with their time. The main ROI is saving manual effort, which is how we reduce our operational costs.

We see improvements in saved time, cost, quality, and risk production.

Attended and unattended automation, which support web and email automation, are the most valuable features for us. Building automations is easy and quick.

The solution enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automations. 
We aren't using the complete suite, like Process Mining, Process Insights, and UiPath Insights, but we use custom tools. Having end-to-end coverage of all these processes in one platform reduces cost and makes maintainability very easy. 

We use Kibana Dashboards with UiPath Insights, which was introduced within the last two years. For process analysis, we still use a traditional business analyst type of setup, but we don't use Process Mining. It's something we are exploring.

We use the academic courses to train all of our new developers and also upscale ourselves with new platforms. UiPath Academy is a single source of training for our team and it's free. We also hire college developers and new developers from other teams who want to work in RPA. We recently started StudioX citizen development. Academy is where citizen developers can get trained quickly.

It covers all of the various products, and it's easy to search through courses. We can skip different sections and get to the part we're looking for.

The UiPath community is a big and vibrant community. I think contributors are being rewarded for their contributions, and that happens in an organized fashion. That's the reason why people are so actively involved in contributing to the community. I would say that 90% of our development queries are answered in the community forum. It's really good compared to other platforms.

There are a lot of AI and ML-based enhancements that could be included in the core product and activities. Right now, there are plugins available from external vendors like Microsoft and Google. If those AI and ML activities can be provided out of the box for developers to use, that would really help the product go from an automation RPA to one automation suite.

I have used this solution for four years.

The latest versions are pretty stable. I haven't seen any issues with stability.

It's scalable. If we have enough bots, we can quickly scale up and down. If it's on the cloud, it's easy to scale up. If it's on-premises, we need to set up the machines, which takes time.

It can take a long time to get a response from technical support. They have to go through multiple hoops to get a solution, so that could be improved.

I would rate technical support as five out of ten.

Neutral

For the initial setup, we needed UiPath's support team to be on board. On-premises setup is always really tough. I think the cloud version would be really easy to set up, but we haven't explored that.

I would rate this solution seven out of ten. 

It's a pretty robust solution. When it comes to automation, it's pretty easy to set up and easy to use. My advice is that the cloud version is the best way to go forward when you're setting up UiPath.

Our primary use case for UiPath is the automation of some of our processes. The main departments that have been affected are accounts payable and accounts receivable.

We are developing expertise internally. At least for the first year, we worked with an outside consultancy to provide us UiPath development. They were working with the business team here closely, but also helping to train our people.

The main parts that we've got are in the area of invoice automation, but we also have some bots that deal with the automation of some of our engineering applications within Oracle.

We run six bots, primarily dealing with invoice automation from our suppliers. That is working in conjunction with Abbyy. So, part of the process is UiPath and part of it is Abbyy FlexiCapture. We also have some engineering applications in Oracle that we also use it for. Examples of this are updating bills of materials, or printing out invoices.

The key savings and kind of the real business case of the project were to do with invoice automation.

UiPath allows us to implement end-to-end automation. We utilize the Task Capture functionality for some of the initial parts. Then, building the bots is done with Studio, and Orchestrator is used for monitoring. It's complete, end-to-end automation.

The invoice reconciliation has been very useful. We now process 80% of our invoices automatically, of which 80% of those get no human contact. The remaining 20% of the ones that are automatically processed are either exceptions or they are certain expense items or the price doesn't match up. In this case, there's some human intervention, but we are getting a high percentage of things going through automatically.

This automation has enabled us to move some headcounts into different, higher value-adding activities instead. We have freed up approximately 10 full-time employees by using UiPath. We didn't let anybody go. Rather, they've been moved into other more creative roles.

The most valuable feature of UiPath is its usability. It's very easy to understand. I think in general, some parts of the process were difficult to grasp, and there were challenges along the way. But now at this more mature part, it's definitely increased employee satisfaction. People have been able to move into higher value-added, more enjoyable tasks.

We've got a group of citizen developers that work on UiPath. These are people that weren't developers but given a bit of training and its ease of use, they have been able to utilize it.

Both members of my team and I have used the UiPath Academy, and the training has been really good. It has enabled us to utilize the citizen developer approach. It is because of the conciseness and quality of the teaching that we have been able to employ citizen developers. We didn't really envision that as something that was possible, but given the ease and usability of the tool and the quality of the training, that's been possible for us.

UiPath has definitely helped to reduce human error. The main process that has gone through automation is the accounts payable process. Now, some of our suppliers may offer discounts and stuff like that. So, it's reduced the time for us to get things into the system. We've got increased visibility, and we've reduced the number of people working on this process, ultimately meaning cost savings as well.

The one negative that this solution has is its reporting. I found it a bit confusing because it was suggested to us that we use Elastic and Kibana for reporting. To me, this seems a little bit fragmented. I understand that UiPath has the Insights feature, but it wasn't what they recommended for us and I think the reason is that it isn't powerful enough for what we want to do. Ideally, we should not have to utilize other tools for reporting.

When it comes to speeding up our process, it has not made any impact. This is because the licensing and agreement part is quite time-consuming. Where we may have wanted to scale up quicker, we've been limited by signing contracts or getting things moving in that regard. As such, it's not really sped up our procurement process or enabled us to scale as quickly as we'd like when we wanted to.

We scale up some parts of the system quicker and we were seeing large delays in processing some of the documents that we wanted. This problem was that we didn't have the hardware or software ready for us to scale. So, in that regard, we've not found the ability to scale beneficial.

The error handling is in need of improvement. We'd had a problem tracking when errors occur, and troubleshooting how things are captured in production.

I have been working with UiPath for between 18 months and two years.

My impressions of the stability are largely positive. However, I'd like to see more emphasis placed on error handling for production.

With respect to scalability, I'd like to see it be made more fluid. It was a bit slow for us to be able to scale. If it was more elastic or there was a different way of billing it instead of having to sign up we had to sign up for a year-long license, it would have been useful. It wasn't that we minded the length of the contract or the cost. Rather, it meant that there were contracts that had to be signed, etc. 

With the processes that have already been implemented now finished, we're actively looking at where else it can be deployed. There is even interest from the executive team. They would like to see it used further.

UiPath has an active community but we've not really engaged with them very much. When we were in need of help, we contacted support and our account executives, but not the community.

The technical support has been really useful. I would rate them a ten out of ten.

In general, they've been very responsive, and easy to get them on a call if required. I've been really happy with the SLAs they've provided to us.

Positive

This was our first RPA implementation.

The initial setup was fairly straightforward. As we are using the on-premises solution, we've had to invest in additional hardware.

We used a consultant to assist us with our deployment. We definitely found it beneficial because it gave us experience. We didn't have any experience with RPA, and they helped us to get off the ground and provided some best practices.

There are three members of our team that are responsible for bot deployment and maintenance. One is a UiPath developer, another is a support developer, and the third is a business analyst.

We have definitely seen a return on investment.

UiPath has helped to both speed up and reduce the cost of our digital transformation. Compared to traditional automation approaches, it's been a lot quicker and less costly to implement. It very minorly affected us in terms of needing IT support. For example, we've had to work with our Oracle applications team, as well as our infrastructure team, in getting some of those parts set up. Overall, I've not found it to be burdensome.

UiPath has definitely saved on costs for the organization. I think that initially, there was some skepticism. Obviously, there were significant implementation costs but now, we're definitely seeing the fruits of that. 

Our total savings at the moment is between 50,000 and 100,000 per year.

The licensing fees are billed annually.

The company evaluated Automation Anywhere and Microsoft Power Automate before choosing UiPath. I can't speak to the pros and cons of the different options because the decision was made just before I became involved.

Overall, in terms of ease of building automation, our experience has been positive.

UiPath has features available for attended automation, although all of our automations are unattended. Similarly, we don't yet use the solution's AI functionality but it's something that we're really interested in starting to use.

My advice for anybody who is looking into implementing this product is to ensure that the processes they want to automate are standard and standardized. That was a key barrier that we realized, and it delayed things for us by quite a bit.

I would rate this solution an eight out of ten.

We have a web application, and we also have iOS and Android applications. We are automating the regression testing part for these applications. Mainly, we are navigating and interacting with UI elements, and we are verifying certain buttons. We are also verifying certain data with RDBMS outputs.

UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring of automations. UiPath has been doing well in terms of Orchestrator and how we can see the execution and the reports and results of our test cases. It is doing well in these aspects, which is very important for us. We are doing end-to-end automation and monitoring using Orchestrator, and it is quite useful. This is something that we were looking for while deciding on the automation tool that we would like to go with, and that's why we decided to go with UiPath.

It has been helpful for regression testing. We are developing a big web application, and we are expecting changes every quarter. The development and deployment have been going on every quarter for the past two years. Previously, we had a team of seven or eight people who were doing the manual testing. By automating the testing, we have reduced the team's size to half. The remaining team members are not just analyzing the executions that we are doing with UiPath; they are also providing support. It has increased employee satisfaction because they don't have to do repetitive work again and again. It has been quite good.

It has been useful for unattended automation, and it has also reduced human errors in our organization. Reduction in human errors is the best benefit that we have got from the UiPath implementation.

Automation is most valuable. When it comes to web automation, data scraping and UI-related activities, such as the Find Element activity, are quite useful.

UiPath Academy courses have also been very useful. Whenever we have to work on something new, I go to UiPath Academy and browse all the resources that they have provided. When I started working with OCR about two or three months back, I used UiPath Academy courses. They are very helpful, especially for new people who join the team. New associates need exposure to the tools that we are using, and the content that is present in UiPath Academy is quite good. It gives them an idea about the tool and the things that they can do with it. UiPath Academy has been quite helpful in training new associates.

UiPath is developing day by day, and there are certain products, such as AI Fabric, that UiPath has launched lately. These products are quite new to most of us in the RPA industry. Because there are courses available for these products in UiPath Academy, we are able to get an idea about a tool, its capabilities, and how to use it.

There is a big room for improvement when it comes to mobile automation. The Find Element activity is not present in mobile automation. There are activities to extract data, but we don't have data scraping in mobile automation. These activities are available for UI automation of web applications, but they are not available for mobile automation, which is a drawback when working on mobile automation with UiPath.

There are also so many bugs in mobile automation. I've been working with mobile automation for the past six months, and in the past six months, I have found so many bugs. We have reported them to UiPath. Some of them are posted on the forum, and I haven't seen any positive feedback in terms of whether a bug has been created or they are working on improvement. So far, there is nothing like that. 

There is also a bug related to the Pick Branch activity, and we can't really work with the UI elements in this particular activity. This issue was first reported by someone in 2019, and this post is available in the forum. It has been more than two years, and this bug has not been fixed. 

For mobile automation, there is a tool provided by UiPath called Mobile Device Management (MDM). We do the automation using that tool. In our project, we are using cloud APM services. UiPath Studio communicates with MDM, and MDM communicates with Sauce Labs, which is the cloud APM service provider for us. There is a huge gap in the synchronization of both of them. I have observed a visible difference. When I execute an app activity, it gets executed at Sauce Labs very fast. The final output that we should be getting first comes to MDM and then UiPath takes that output from the MDM, but there is a synchronization gap. There is a visible difference, and UiPath is lacking in this part. So, mobile automation is the part where UiPath can improve a lot.

I've been working with UiPath for almost two years. I'm into development, and I have worked on Excel automation, mobile automation, and web automation.

I don't have any opinion on its scalability at this time. In terms of its usage, we have to create 2,000 automations for our client, and we have already implemented more than 1,000. We don't run those automations every day. We run them as per the requirements, so there would be 200 to 400 processes once a week.

In my project, there are five people who are working with UiPath, but in my company, there are many more people. One of them is the manager, and four of them are working on development. 

There have been some bugs for which we connected with UiPath support. It was a mixed experience. There were some technical support experts with whom we connected, and they tried to get to the root of the trouble. They did their best to provide us with the best solution possible. We have also had other scenarios where there was no answer or explanation for the issue. We didn't get any positive feedback from them.

I had posted a few queries related to mobile automation on the UiPath community, but there was no instant solution. I was expecting a reply within one or two days, but there was no reply. Because this is a niche field, there are not many people working in this domain, but I got replies from the UiPath team on some of the queries. So, overall, the experience was good. I would rate them a six out of 10.

I was not involved in its setup.

It reduces the cost of digital transformation in a way. When it comes to the scenario of our automation, UiPath isn't so fast, and there is the speed issue that UiPath can fix, but because a bot has the capability of working 24/7, there is a reduction in the cost of digital transformation.

We evaluated Blue Prism. We didn't explore Automation Anywhere. After comparing it with Blue Prism, we decided to go with UiPath. As per our client's requirement, there were three applications to be automated, and because UiPath supported web automation and mobile automation for iOS and Android, we went for UiPath. We just had to buy the license for one, and we could automate all three applications.

Rather than implementing RPA on a big scale, I would advise starting at a small scale and doing good process task mining. It is very important to identify the right process to automate.

UiPath is quite an impressive tool. It was the first tool that I started learning when I got into RPA. Recently, I got familiarized with Automation Anywhere. I used to think that Automation Anywhere is better because it is on the cloud, but now that I know that UiPath also has a cloud option, I'm going to explore that option. It is a good solution, and UiPath is doing well when it comes to the improvement of the product. My experience is good overall.

We have not used AI-enhanced Document Understanding in our automation program. We are planning to implement it, but it may take a while.

I would rate it an eight out of 10.