UiPath Platform Reviews

We use it mostly for reconciliation, automatic emails, and monthly, quarterly, and yearly reports and extractions. Document Understanding is another big use case for us.

The AI functionality cuts down development time. The out-of-the-box models are pretty good at extracting and do account for variations. We don't have to do it template by template, at least for invoices and purchase orders. Thus, it's a huge time saver.

We have more than a hundred unattended automated processes and hope to scale as well. We have a healthy pipeline, and our COE just prioritizes them and chooses the ones with the most impact.

The core RPA is the best feature because of how easily we can get started. The other most valuable feature is DU or Document Understanding. It doesn't require huge setup and implementation times. When you look at a pure machine learning model, it requires a lot of expertise. Though UiPath is not purely plug-and-play, it's almost like plug-and-play because it can be up and running very quickly.

UiPath has definitely helped us with productivity. It has helped us to grow because as we bring in more companies, we don't have to add more people or train new people. The existing staff can handle the growth. Also, the team no longer has to do some of the manual, repetitive activities and can focus on more value-added work. We're looking at how to move analytics and data into the department and use the time saved to upskill the employees.

I connect with local customers and find it very beneficial to share best practices. My team tells me that the UiPath user community forums are pretty active and that if they're stuck and post a question they get a response pretty quickly. I only hear good things about the forums.

I took the UiPath Academy basic certification training before I rolled it out to the others. It's pretty good, but you still need to be technical. You cannot pick an analyst and then put them through the full certification. However, the training is self-explanatory. The Automation Academy is good as well. The biggest value I've gained from UiPath Academy is the self-learning methodology. Having free self-learning material makes sense when you don't know whether you are committing to the solution.

I would like to know more about the product features and real use cases. Sometimes, all I hear is how quickly the solution can be up and running, and I don't hear about all the work that goes into it. Because everybody has a choice with bots and process improvements, unlike that with ERP systems, I would like to have more information on how to constantly evangelize.

In the UiPath Academy, there's not much documentation for Document Understanding and Process Mining. Documentation for some of the newer tools needs to be added to the UiPath Academy.

I've been using UiPath for three years.

I haven't seen any degradation in terms of performance.

It scales well.

UiPath's technical support is pretty good. If their level one support is unable to take care of an issue, they will then escalate it to product managers. I would give technical support a rating of eight on a scale from one to ten because they are not as good at supporting some of the newer technologies.

The initial deployment is straightforward. It took a few months to set up everything, and we scaled slowly. It's easier now that we've moved to the cloud.

We did it all ourselves. We tested everything in UiPath Academy first to see if it would work for us.

UiPath has reduced the number of hours spent on manual work, and that is our ROI.

The cost could be lower. The pricing is not transparent, so we don't always know if we really are getting a good price.

We evaluated Automation Anywhere and Blue Prism. When we looked at the total cost of ownership, UiPath felt better for our situation.

Compared to other solutions, UiPath offers a lot of products in its portfolio. The customer success manager attends to our needs, gives access, answers our queries, and takes care of us. Also, UiPath has a robust community, so it pays to be with the leader to get all of these benefits. Thus, I rate UiPath at nine on a scale from one to ten.

We use it to transfer information from one system to a government system.

We also use UiPath to automate processes that track mileage on vehicles, which would then allow us to calculate some of the GHG emissions.

It has really helped us become more efficient. UiPath has made the lives of our data operators a lot easier because they would normally have had to manually enter all this information or transfer data.

AI Computer Vision has been great because it works through VMware. It's able to see the elements through the VMware window on the government system that we interact with.

UiPath's user community is great. I get a lot of answers and am able to talk to folks who know the products and can provide support directly.

The UiPath Academy courses are an easy way to learn how to use Studio.

The licensing has been a challenge in terms of what is included with our current license. They've changed it a bit.

The learning curve to get UiPath up and running is hard, although we're pretty comfortable with it now.

Promoting its use is the hardest part for us. It's tough to get people to believe in using the assistant or Studio without fearing the loss of their jobs.

I've been using UiPath for about five years.

It's very stable, and we've never had an issue with it.

UiPath is easy to scale. If we want to share the bot or the scripts, it is easy to do so with other team members. It is also easy to add licensing and grow the current bot or create a new one.

Our experience with UiPath's technical support has been really good. We get great responses to tickets when we need help. On a scale from one to ten, I would give technical support a ten.

Positive

The initial setup was pretty straightforward. We learned Studio, started with a simple script or bot, and grew from there. Our implementation strategy was to look at our highest demand for transferring data and make the bot do that.

Our ROI is that instead of having a team of seven people to manually do the data transfer, we now have two people.

The pricing is fair.

We looked at Blue Prism and went with UiPath because of its ease of use, the Magic Quadrant rating, and the price.

It's great software and has helped us a lot. It gives us a competitive edge.

Overall, I'd rate UiPath at nine out of ten and would advise you to go for it.

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.

We use this solution for finance, HR, and for handling invoice reconciliation. We also make use of donation approvals.

I find that UiPath's user community was more helpful a few years ago. When I go to use the UiPath forum, a lot of the answers are copied and pasted from old answers and they don't make a lot of sense. That being said, I do still occasionally get some value from it. 

We also make use of the academy courses. We have put all contractors through the basic courses to make sure that they've got a basic level of competence. The academy courses are useful to test that people know what they should. The architecture courses have been most beneficial to us.  

We are saving approximately three and a half million annually based on the number of hours saved multiplied by a salary base rate. That ends up being approximately 60,000 hours a year that's being replaced by bots and this is a big deal for us.

The Orchestrator really stands out as the most valuable feature. We don't have to train anyone. They can usually pick it up really quickly. It is easy to use and intuitive.

A lot of the packages are very easy to work with. There are some challenges when updating a package that you've built or a library that you've built in UiPath. Overall, the extensibility is really nice. 

I would really like to see the package deployment updated. As it is right now, if you want to update something, you have to take down the latest code, sync the packages and re-upload everything back through the dev test to prod. It's a big hassle when we've tested the library ourselves. 

I have been using this solution for seven years. 

This solution is very stable. Any complaints I have come back down to package management and custom issues with custom libraries. Outside of that, upgrades are really quick and really easy. We have bots disconnect so frequently that it is easy for us to catch issues manually.

This is a scalable solution but UiPath could use some better visualization tools for bot utilization. They do have insights but they are a little bit rough to work with. I wouldn't want to put on a hundred bots at a time, but loading in a few here and there is really easy.

I used Automation Anywhere and Blue Prism for a while. The UiPath Orchestrator far exceeds the functionality of Blue Prism and Automation Anywhere. As far as the bot setup goes, UiPath is very easy to install, especially compared to Blue Prism. UiPath is more business user-friendly than Blue Prism. Sometimes it's nice to work with Blue Prism because it has such low-level code that it gives you a little bit more flexibility.

We keep it pretty agile by necessity. We use a lot of contractors to get a lot of different approaches. We have 168 processes on 27 machines. We have some restrictions based on the company requirements but internally we move as fast as we can because we have to.

It is really easy for us to set up a VM and get UiPath installed. It is a five or six-step process. UiPath is significantly bug-free compared to what I'm used to with other products. I haven't had to raise a support ticket yet for UiPath.

Initially, we had a customer success manager from UiPath who showed our admin how to run the installation. At this point, we take care of all of it ourselves. 

We've replaced the equivalent of 20 to 30 employees who have all been moved to more valuable positions. We've taken processes that were supposed to take months and reduced this to days which has improved our customer experience. 

I would like to see a few more options for developer licenses because we end up swapping them so often. We've tried going through floating robots and a few options that have been not exactly what we're looking for. Price-wise, the cloud offerings are good. 

I'd certainly say UiPath is worth it to save time and effort. The product is really stable compared to what I've worked with before. 

I would rate this solution a nine out of ten. 

We provide a lot of financial services. Its use cases are specifically in banking. There is a lot of Excel transformation where we are moving data from Excel into in-house applications. That's probably about 80% use of it.

We are using UiPath to automate processes that deal with a good cause. We run a lot of charity work, and there is a bit of work going on there to automate the operational aspects of running these charitable causes and things like that.

We have not yet used its AI functionality in our automation program, but we would love to.

We started with nothing. We now have about 150 attended automations going with another 80 attended robots effectively. So, we've had quite a growth in automation capabilities in terms of its impact on the organization.

The ease of use of Studio is valuable. In terms of features, Excel Application Scope, web automation suite of products, and screen scraping are the features I use the most.

Excel Application Scope allows you to use Excel pretty easily and graph data from there, and then you can transform it within Studio and make any changes you need to do. You can then either write it back to another Excel file, or you can read the table within Studio and write it directly to a web-based application.

We have used screen scraping a lot. If you have a web application inside Chrome, you can go to Chrome, and it can grab all the data from there. You can put it into a data table in Studio, make any changes or transformations needed, and then write it back to whatever application you want it to go to.

We gain a huge value from the user community. I'm always running into problems, and I have been going to the UiPath forums to get answers to my questions. Usually, if I have a question, someone else would have already asked it, and I can get great info and insight from there. So, the community is a very important part of the development experience.

We have used UiPath Academy courses. We recommend our citizen developers to use UiPath Academy. I've used it on and off for things I don't quite understand, and people also use it to get RPA certified with UiPath. It's another great value service that UiPath offers. There is the ease of use of videos and the breadth of knowledge. There is also the applicability of the examples to everyday problems. I definitely know people who've been able to automate processes that are more complex with the help of UiPath Academy.

Our challenge with UiPath is getting the infrastructure assets up to speed, particularly on the Orchestrator side. However, I just now came from a demo for UiPath Web, and it seems to be to enable serverless robots, which would definitely be a lower barrier to entry. 

Our pain point is just on the infrastructure side and getting the assets coming up to speed. It's a big bank problem. We have a very large IT organization, which is not always aligned with the needs of teams like ours.

I've used UiPath for about two and a half years.

The product is great. It's very stable. It's reliable. We trust it with a lot of different and very important automations. If UiPath wasn't stable, it would introduce quite significant operational risks to the firm.

Its scalability is good. It could be better, but that goes back to my pain point on our struggles with infrastructure. That has been challenging. If we could get a better handle on our infrastructure, then scalability would be a bit higher, but overall, it's a very scalable product.

I would evaluate them very highly. I work with their technical support every time our technical account managers can't get something done. They're very confident and well-versed in what they do, and they always find a solution to our problem.

Positive

The only RPA tool I've ever worked with is UiPath. Some people used Blue Prism at work, but I never used Blue Prism. They're not using Blue Prism anymore. They switched because of better capabilities. UiPath is just a better tool all around. 

I wasn't in the decision-making process, but I know they tried to do a proof of concept. The Blue Prism team was supposed to do automation of some sort, and the UiPath team was also supposed to do it. The UiPath team did it in six hours and the Blue Prism team didn't do it in two weeks. The ease of use of the Studio product really drives home UiPath's capabilities.

It was complex, but it was straightforward with the help of account managers. We have two technical account managers with UiPath who are very resourceful and well-suited to working with us and helping us accomplish what we need to do.

Our implementation strategy was a citizen development framework. It involved getting the Orchestrator set up and then empowering people within the firm to start automating their various roles or tasks. We still have the citizen development framework, but we're also moving to unattended automations from our RPA developers.

We did it on our own with the help of our account managers.

I don't have any metrics yet, but we're at breakeven in terms of ROI. That's just in terms of monetary figures. In terms of general error reduction and things like that, we have seen quite an ROI.

Its pricing seems reasonable. I know we've been able to get a good amount of value in a few years. Our breakeven was only in year two. So, we're approaching breakeven in our licensing program. It's not a cheap product by any means, but the value that can be returned on an ROI basis is quite high.

To those evaluating such solutions, I would advise taking a good look at the capabilities of the solutions. The strength of UiPath is its capabilities in a number of key areas, whereas some specialized players in the industry might be really good at one specific thing. For scalability, you want to have a wider operating area that something like UiPath can accomplish, rather than a more specialized player.

I would rate it a 9 out of 10. It's a fantastic tool that does what you need it to do. It's great for automating a wide variety of things. Ease of use is there in the various products. Any concerns I would have about having a lower barrier entry seem to be acknowledged by the product managers in the demo that I just now had with UiPath Web. So, in that regard, it's a very accessible and functional product.

We generally work on integrating it with our support ticketing system, which is ServiceNow. That way, we can standardize our input and get better results. It has been working really well for those kinds of processes.

A process that we worked on for operations, for example, was the ordering of phones for our new agencies. It accelerates a lot of that process and gets the people onboarded faster, more easily, and with fewer errors.

The most valuable feature is that it can be integrated with almost anything. We use in-house applications and we're able to integrate them through the database using endpoints and APIs. This sharing of information between systems via UiPath means our staff gets results quicker. Normally, we have to put in a request with the database team to go in and input the data. But UiPath already has access and it's really quick. It's really responsive and makes the experience easier for the business.

That is also true for third-party vendors. The vendor that we order our phones from has a UI, a website that we use, and we have been able to use the UI to integrate their application.

We can implement almost any interface that we want, in any way possible. It's really flexible.

And given that healthcare is highly regulated, UiPath works really well for credentialing and that type of security. We see that it has protocols that ensure that our data is not going to be stolen. We use the credential assets to save our passwords and sensitive information such as licensing.

I've been looking into Document Understanding. I've worked with it in previous jobs, things like AI center and OCR for documents. It would be helpful if they made the Document Understanding modules a little more user-friendly. There is a learning curve for using it correctly. It's a little bit hard, but once you get a feel for it it's good and it doesn't delay the automation process.

I've been using UiPath for almost four years.

The stability of UiPath is good. I haven't seen any abrupt occurrences in my time using it. Our production environment is always running. It's well-secured.

In regard to our processes, it's easy to scale. It is not that easy to scale on the business side of things, but the tool itself does provide an easy scaling process.

I haven't had the need to reach out to technical support that often because, with the community, you can find out anything regarding UiPath online. It's the same support team that answers those questions.

I did submit one ticket to support, and it was answered really fast. However, they did take a little long time to get to the root of the problem.

Positive

We did not have a previous RPA solution.

We do calculate ROI in terms of the hours we're saving the business. For example, with the specific processes that we created for phone ordering, we're saving the business a lot of hours. 

Currently, we're just using it for agencies because we want to see how this can impact things. But it's handling the process for more than 40 percent of our employees because most agency employees get phones as soon as they are onboarded.

I have evaluated other automation tools, and I've been asked many times in the different companies where I have worked why I prefer UiPath. It's the best choice because of the community, documentation, and the number of updates they come out with. They're really on top of things.

Other vendors are not on the same level. I have tried Blue Prism but it has poorer documentation and it doesn't have the support that UiPath has.

To get our certificates we had to use the UiPath Academy. The Academy gives you a sense of how UiPath works. It can get really technical, but to get a sense, at least, of how to start the journey of becoming a developer, in my case, it helped a lot.

Overall, it's a great tool to use. It has a lot of benefits documentation-wise and support-wise. It's really stable and it's really easy to use.

Our company is in the insurance industry and uses the solution to run RPA processes for the claims department to free up staff time. 

The scheduler tool is valuable because I can slow or speed up run times during peak use. 

Our solution is on-premises so we are unable to utilize phone apps.

I have been using the solution for three years. 

The solution's stability is 100% and really good because it never goes down.

The solution offers the best scalability of any known product. 

I have not utilized technical support because that is handled by other team members. 

I personally did not use another product prior to learning the solution. 

I was not involved in the initial setup. 

We track ROI quarterly and through Q2 we have saved more than $100,000 by using automated processes. 

We are getting to the point of reaching full ROI but need to build more automated processes to reach that goal. 

I am sure my company evaluated other options but the solution was already in place when I joined the team. 

I utilized Academy courses to understand the solution's full capabilities but haven't yet used many of those features such as AI. I am currently learning about OCR and plan to use AI in the future. 

Learning the solution is a case of "I don't know what I don't know" so it is important to become aware of all the tools at your disposal. 

I rate the solution a nine out of ten. 

My organization is an outsourcing company. We work with various clients. So, we have many use cases. The current use case I'm working on is related to invoice processing.

We don't use attended automation. We use its AI functions a bit. Usually, we work with document understanding.

Currently, I'm using the latest version. It is deployed on the cloud and on-premises. It is the UiPath cloud.

It is easy and fast to build automation using UiPath. All of our automations are created with UiPath. Usually, we do automation for SLA purposes. Most of the time, the clients don't have enough resources or humans to do the job, and they need automation to improve the SLAs.

It enables us to implement end-to-end automation, starting with the process analysis, robot building, and monitoring of automations. It is good for my company. With these benefits, we can implement it and help with the monitoring.

It has reduced a lot of human error. For example, in the project that I'm working on, people were putting the invoice information on a daily basis. There were more than 20 invoices per day, and each invoice had more than 100 line items. Humans would do a lot of mistyping on the number of packages or the number of items in the package. After we applied the document understanding solution there, we can handle around 90% of invoices, and all of them are correct.

It has absolutely saved us time. It has probably saved us more than 20% of the time. People now have more time.

I feel comfortable with UiPath. The thing that I like most is that UiPath has a very large community and a large ecosystem. So, it is easy to connect with other applications or platforms.

UiPath Apps is a great feature, but it still needs time to evolve. They need to add more features. It hasn't increased the number of automations we can create while reducing the time it takes to create them.

I don't like the sequence feature in the UiPath. It is difficult to analyze and read the code.

The variable management is really messy. When I look at the code, I don't know where the variable is and in which scope.

I have been using this solution for around five years.

It is stable.

It is scalable. We have had three enterprises that are really big with more than 1,000 people. The others are small companies.

In our organization, we have 12 people working with it.

I haven't contacted their support. I have been using UiPath's support indirectly. I just put a question on the community forum, and they answer it very fast.

In the previous version of UiPath, it was a nightmare to set it up, but now, it is really comfortable and convenient. Overall, it is fast, but the deployment duration also depends on the solution. If you design a good solution and follow the best practices, it is really fast. It takes a couple of hours at the most.

We always try to split a project into small parts so that we can test each part and apply it easily. I have seen that many people create very big projects, but when you complete them, you cannot test them. It takes a lot of testing from end to end, and we still can't test it completely. That's why we try to split a project into small parts. We can test each part independently, and after the integration, we can deploy with high confidence.

I am not sure how long it takes for our clients to see its benefits after we deploy it for them.

We have a maximum of five people for deployment and maintenance. We sometimes have issues with the infrastructure. In many cases, the infrastructure is handled by the client, and there is no support or cooperation between the RPA department and the IT department. Usually, they will be late, or they did not check our requirements to deploy the bot.

If you use the cloud model of the UiPath, it will reduce a lot of the total cost.

Its AI functionality hasn't enabled us much to automate more processes. Most of the time, when we propose those functions, we don't have an agreement with the client because of the license price. Currently, the license price is the major obstacle.

My advice would be to contact the UiPath sales team directly. I know that they have different license models for different clients and regions.

I would advise following the UiPath Academy and their best practices. That is enough.

They provide very valuable templates for automation purposes. It depends on your purpose, but you can apply the ones that are already there.

I would rate it an eight out of ten.

Initially, we had some manual test cases running in the background, where we tried to call our UI and do end-to-end testing of the login, checkout, etc. We now automate end-to-end testing using UiPath to reduce the workload. We use UiPath for process analysis and making robots, but not for monitoring. We already have other tools in our system to monitor each and every step of our process

We work in a hybrid environment, but we're increasingly cloud-based. We are not driving as much traffic to our on-premises system. 

We were hiring developers to write test cases and perform automation for us. UiPath significantly reduced the amount of employee labor needed while cutting down on human error. The error count in our system dropped by around 10 to 15 percent. 

This is a considerable win for us. Our clients are happier because they see fewer errors in production. End-to-end automation helps us deliver quality work to our customers. UiPath helps us analyze every connected case with automated robot testing. 

UiPath has a simple, creative UI, where you can check on all the automated tools. Everything is well documented, and you can easily get support from the UiPath team. Whenever we were stuck, their team was always there to support us. The community is huge and powerful. 

The entire process of setting up automations is smooth. We could easily deploy each case on our cloud platform and make things work.

We aren't scaling up UiPath because it doesn't provide a satisfactory way to log and monitor data. Instead, we use other tools like Automation Anywhere for large-scale operations in our production environment. We're building solutions that can handle a huge amount of data so we can monitor real-time issues. I don't think UiPath solves that case for us.

We've been using UiPath for around a year.

We faced some issues with scalability, so we use another RPA in production. 

I rate UiPath's support nine out of ten. We always get a response within six hours. UiPath also has a massive user community, so you can get instant support from anyone. We faced some issues when we built our first robots, so we got help from the community. When someone else has problems, we try to help them. 

Working in the community, you are recognized for your support, and you can learn a lot from others. There are some complex things about using UiPath that we don't understand. 

The UiPath community is friendly, and they respond quickly. At most, it takes around six hours to get an answer from the community, based on our experience. I believe that anyone who adopts UiPath will learn so much from the community.

Positive

We deployed UiPath through a vendor provider who helped us through the entire installation and everything in our cloud environment. Initially, we tried UiPath in our testing environment. Once we saw that it was stable and improved our productivity, we moved it to our production environment with excellent results. It took 10 months for us to deploy UiPath fully. 

We had two people working on the deployment. One managed the installation, while the second person handled monitoring and other development areas. 

We had two developers working 20 hours a week writing test cases manually, so UiPath saves us 40 hours of labor costs. However, we spend about that much on UiPath when you factor in licensing, infrastructure costs, and other expenses. The value we see is from the reduction in human error. 

I rate UiPath eight out of ten. I deduct two points because of the shortcomings in terms of scalability and logging. It's a nice-to-have solution in our case. I recommend trying UiPath out and seeing if it's suitable for your use case. You should go for it if it fits. It's not too costly and it will reduce human error while improving the quality of your product.  

We automate everything using the UiPath solution. We have some ongoing stuff, e.g., generating test cases and testing some of our development platforms. We need to define all the parts, such as how to test the entire environment to determine if everything is working okay.

We utilize all our services on the cloud, then they can be easily used across all our offices.

We only use unattended automation.

If a product is about to go live, we heavily rely on coverage from UiPath. This is during the development phase. However, when onboarding to production, we use other solutions, which don't rely on automation, for monitoring purposes.

When we are in the development phase, we have multiple edge cases, like iOS, Android, and other platforms, checking in. For a tester, it is difficult to check every edge case. Instead, we define automation test tools in UiPath, then our automated work does everything for us. Once it is done, it gives us a detailed analysis about where the product is performing well. We get handy videos before going live so we can improve everything and ensure that our end customer will not be impacted.

Our bandwidth has been drastically reduced, by nearly 60 hours, because of this solution. We have reduced the number of testers by three. 

The most useful feature of UiPath is that it is very easy to use. 

It helps us a lot with digital transformation.

The UiPath solution doesn't currently provide unique testing for mobile devices.

I have been using it for around six or seven months.

To the extent that we are using the solution, it is pretty scalable.

We use a third-party for support of this solution.

When we were facing some small issues going to the cloud, we tried to get help from the community. The community has been very helpful. Everyone has been willing to provide some good information to other users.

Previously, we were using an automated script to test everything. Now, with UiPath, we are automating everything. 

We used the community to help us with the setup.

The vendor helped set this up and guided us how to do everything during the onboarding process. Therefore, we didn't have any issues with the setup.

UiPath has reduced human error by 20%. 

We have reduced our costs by approximately $200 a month.

Creating our digital transformation didn't require any additional costs.

The vendor gave us a 30-day money-back guarantee. We were fine with that. We saw improvement during that time and kept the solution. 

We didn't consider any other solutions.

I would rate UiPath as eight out of 10.