UiPath Platform Reviews

We do workflow automation for some of the functions such as form-filling or filtering data accession on the client's web application. We use UiPath RPA for data accession and other processes. We have done workflow automation that:

1. Opens a client's website.
2. Filters out the current data.
3. Lists out all the records that need to be processed.
4. Opens each record.
5. Enters the details gathered from a spreadsheet or somewhere else.
6. Submits the application. 

It does that for all these users that have been filtered out. That's why we're using UiPath.

We're able to automate manual processes and save the effort of our employees. We're also able to save our and our clients' time. With these automations, we could also save the time of healthcare workers and patients. For example, we did automation of insurance claim processing, and based on the feedback that we received, they said that insurance claiming is safer and faster as compared to the previous manual process. For example, previously, if they were processing 100 insurance claims per day, they can now process 250 to 300 claims with automation.

UiPath helps to implement end-to-end automation. We don't have any tool other than UiPath for automation. We build the bot through UiPath and run it on the client's application. We don't have any other automation tool. This end-to-end automation makes up 95% of our business. End-to-end automation is the only thing that we're doing in our current company.

When we started and got our angel funding, we planned to build our own RPA tool for workflow automation. We did the development for almost six months, but we faced a lot of issues. We then decided to use a top, third-party RPA tool. So, we decided on using UiPath. We now have seed funding. UiPath was a savior when we were starting out. Otherwise, we would have faced a lot of issues, and even the company might not have grown without UiPath. UiPath has helped us a lot because they have years of experience building the RPA tool, and they have a lot of features to make the development process smooth.

We have been using NLP for understanding the signature in one of our documents. We just want to get the text out of the documents that have been uploaded to our claims application. For this, we use the UiPath AI functionality. If UiPath doesn't have the AI feature, we might have to get help from the cloud vendor providing AI, but because the AI is built into UiPath, it supports document understanding or language analysis that we're doing. Because AI is integrated with it, we don't have to learn anything, other than UiPath, to get the task done.

One of our workflows is extracting text from images and PDFs. We use UiPath document understanding for that. If they didn't have this feature, we might not have been able to create a workflow for the client for running a process. UiPath has helped us implement more workflows and do more processes.

UiPath has definitely reduced human error. We did have some unattended automations with UiPath but not everything can be automated. Some issues might arise that need to be resolved by a human, but 100% of the things do not need to be done by humans. Because of that, human error gets reduced. For example, we have thousands of documents that need to be classified based on the text they have. If we give that task to humans who have to handle more than 20,000 documents in a day, they will get exhausted and might make errors in classifying the documents. With UiPath automation, it can be done without any human errors. It definitely reduces human error.

UiPath has freed up employee time. The workflow automations that we have done save the time of our employees and our clients. We save approximately two to three hours per day per employee. In a week, there are 10 to 15 hours, and per month, it comes out to be about 100 hours.

UiPath didn't save the cost for us because we're not using UiPath to run the workflow. We just build the workflows and give them to the clients, but it has saved the cost for the clients. For us, it reduces the development effort. It has a lot of tools to build applications.

When it comes to UiPath, the custom robots that we can run in an EC2 instance and the on-premise support are valuable. UiPath has cloud as well as on-premise support. We have some companies that ask to run the application on our own server, so we just install UiPath in our own system and enter the UiPath key. We're running it on-premises on our own bare metal server. We can also do asset management where we can store the credential for the client's application that will be used in a runtime environment. We like credential management. 

We also have queue support in UiPath. We can just put the data in queues, and it'll be processed in a transaction manner. 

With UiPath, development is easy because they have their own Studio. We just run UiPath Studio, drag and drop the components that we require, and connect all the dots. When we're doing website automation or web app automation, we can use their UI-based Studio and grab the elements from the web application using XPath, which makes the development easier. However, for that, the initial setup is required to be done in a certain way. After we have done the setup, which includes running UiPath Studio and connecting the robots, everything is easy.

We did the UiPath courses for onboarding. We onboard many developers regularly, and every developer has to complete the course before getting started with the development. UiPath Academy was useful for learning about UiPath and getting started with the development. If we had started development without UiPath Academy courses, we wouldn't know which tools are beneficial for which use cases. Otherwise, we would've ended up using unwanted features for the use cases, which would have increased the development time. UiPath Academy gives us a list of features and tools. We get to know which tool would be suitable for a particular use case. This way, it reduces the development effort.

In the UiPath Community, a few questions get resolved and a few questions remain unresolved. UiPath has a big user community, but it needs to grow more. For example, during development, we might face some hurdles or hiccups while doing some of the tasks that we don't do on a daily basis, such as executing some API calls and getting some data. We faced some issues related to that, but when we searched for or asked about such issues in the UiPath Community, out of 10 questions, five to six questions remained unanswered. We had to resolve them on our own. So, UiPath needs to improve its community. They can offer some kind of reward for answering the questions asked in the community.

It would be helpful if UiPath could provide developers to help us with the on-premises setup. Without that, we have to figure out how we do the setup.

Its cost could also be better. We need to have a license for every robot, and it isn't possible for us to be able to run UiPath in our on-premises environment based on our usage. Even if we need to run a robot for an hour, we need to get a license for one year.

We have been using UiPath for three years.

UiPath has good stability. They have monthly software updates, but they haven't caused any issues with our system. We didn't face any issues so far because everything runs smoothly. It's 99% stable.

UiPath is scalable. Because our setup is on-premises, we manage the Orchestrator or Studio as our own. When it comes to running the bots or workflows, every time we want to run more automations, we just buy a new robot and attach it to the pool. They run smoothly. UiPath is 95% scalable.

We have about 200 users using UiPath. It's deployed at only one location.

I've contacted them. They're definitely helpful. Whatever issues we have had, they try to debug and resolve them as soon as possible. They're good. I'd rate them a nine out of ten.

We didn't use any other solution previously. We started with UiPath.

It's on-premises with the AWS-managed cloud. While setting up the on-premises environment, UiPath documentation helped the most. Without that, we wouldn't have been able to set up the on-premises environment. We had the help of the DevOps team for setting up UiPath with AWS services because we ran our UiPath environment in the AWS cloud in our account. For 60% to 70% of tasks, we used the UiPath documentation, but for setting up the reusable services and scalable machines, we had to take help from the DevOps team for the setup. If UiPath had a team to help us set up the instance in the cloud, it would have been better.

It definitely requires maintenance. They have a monthly patch for the features and software updates. We need to install those patches. We have two to three people who are involved in maintenance.

We have definitely seen an ROI. We're investing a lot in the UiPath license. It gives us two to three times more than what we invested. We're giving the workflow solutions to clients, and they're giving us the money for the workflows that are running. The UiPath is running smoothly, and we're getting two to three times more than what we invested in UiPath.

We thought of Automation Anywhere and IBM RPA. That's all. These were the ones for which we planned to do a PoC and evaluate.

I'd advise going with the cloud version of UiPath instead of the on-premises environment because it'd save the development effort and the setup time and cost. In the cloud environment, you can also run the bots on a usage basis. Going with the cloud version of UiPath would save a lot of time.

Overall, I'd rate UiPath a nine out of ten.

We use it for handling processes that involve human effort savings. We are currently focusing on processes and problems that our users are facing in their day-to-day activities. It is used for the automation of business problems that are repetitive and error-oriented with a huge number of users working on them. We list down a set of processes where users are spending a lot of time, then we verify whether the use case is valid for automation using RPA. Once that is complete, we start programming the bot based on the requirements given by the user. We try to mimic each and every action performed by a human being by using UiPath Studio. It replicates what a human being does.

In terms of setup, the development happens in Studio that's on-premise, but the deployment of the robots is done on the cloud. They have their own cloud service called Orchestrator. UiPath hosts that, and it is available at cloud.uipath.com. It is basically the UiPath Cloud. The interface is completely handled by UiPath.

The biggest benefit is that before implementing automation, the users were spending a lot of time doing mundane and manual activities. Implementing the robotic process automation for processes that they were involved in helped them to avoid doing these manual activities and focus on more value-added processes. On the whole, it has helped the users to spend their time more wisely and also get more benefits for the same time spent. It helps us to improve user satisfaction by improving their working methodology because they are only doing things that are value-adding.

We are automating all the manual activities that can be successfully handled by the robots. So, the users are really happy, and we are getting good feedback from the users in terms of time savings. We are also achieving 100% accuracy in the output, which was not the case when the users were performing these actions. When they were performing the actions, the users had to validate the outputs, and the outputs were not as per the requirement. There used to be an error rate of at least 10% to 15%, but with automation, the error rate has been reduced to zero. So, the removal of manual activity and the reduction of the error rate to zero are two of the main benefits.

We are using it in our finance operations for our accounts payable process to process invoices. For this process, we were receiving invoices at a rate of more than 50 per day, and having humans perform those actions was not sustainable in the long run. So, we developed a robot that would automatically process invoices that we received through email. It extracts and updates the data into our ERP, and then, it sends an email to the users telling them that the invoice has been received, verified, and uploaded into our ERP. Now, we have a process that saves approximately two hours for five or more users on a daily basis. At an annual rate, we can save approximately 10,000 hours. We develop the bot in UiPath Studio and then deploy it in cloud Orchestrator via an unattended bot, which is a bot that runs on a predefined schedule. We have a particular time when invoices arrive in our inboxes. We set the robot to run at that particular time, and then the robot is able to process those invoices and proceed to the next action.

We focus only on processes that can be automated end-to-end, completely eliminating human activity. UiPath is flexible, and it allows us to build robots that prevent human intervention right from the start and all the way to the end. Then, we are able to deploy it on the cloud by using the Orchestrator solution. From start to finish, we have completely eliminated human effort, supporting our mission of end-to-end automation. For process analysis, we use a UiPath tool called Task Capture to understand the business case and draw a flow diagram for the steps involved in a process. UiPath has all the solutions required to implement end-to-end automation, and we are successfully using them for all our business problems.

This end-to-end coverage is important. Basically, we select processes where we can avoid human intervention. End-to-end automation is one of the key KPIs that we check before we even start automating a process. It is the first thing that we look for because we prefer no human intervention at all, be it for any kind of input, validating the output, or checking the logs of a process. All of these are predetermined and handled by the robot.

It is cloud-based. So, we do not have any infrastructure costs for maintaining the servers, etc. That is a big advantage. Also, Studio updates for development are pushed automatically. We receive the updates and just click on them, and Studio is updated. Overall, it saves a lot of time for the IT team because there isn't any involvement from IT resources after we deploy or install Studio on our system. From there on, there is literally no involvement of the IT department. That is how beautifully they have designed the tool for the updates as well as overall maintenance.

We went for the cloud to avoid any on-premises server costs that we might need to take care of on a recurring basis. The cloud was a big advantage for us. We are able to save approximately 15 lakh Indian Rupees, which would be $10,000 to $15,000, by not going for the on-premises setup. We were able to save that sort of investment in server costs by going for a cloud-based tool.

We were able to synthesize the value of this solution right from the inception. As soon as we deployed the bots, we were getting actual analytics for the run rate of the process and the total time of bot execution. Indirectly, the time during which the bot executes is literally the time that is saved from human effort. We get proper metrics of the time being saved by using Orchestrator. The other important thing is logs. In case a process fails, from the logs, we are able to derive insights about when exactly a process is failing. We are then able to develop a solution to handle these failures and re-implement them. So, overall the cloud solution gives us insights. It adds value to even developers' time by giving us an overall metric of the time saved as well as utilizing the logs for insights about the process runtime, et cetera. Overall, the cloud functionality is a great value addition.

It affects our ability to scale up automation. When we develop and deploy a process, other users in different departments take a look at the processes, and they are getting confident about the fact that this can solve their problems. We have been receiving requirements, and in that way, we are able to scale up the automation. On top of that, we develop the robots in a way that is modular in nature so that when we implement a process, we have reusable components that can be plugged and played into the new process. This improves the speed at which we can automate processes.

It has indirectly brought innovation from the users' perspective and developers' perspective. The users are saving time, and they are getting innovative in their day-to-day activities. In terms of development, we are on a constant learning path. When the vendor releases new software updates, we are able to effectively utilize those and implement them into our processes on an immediate basis, which improves the speed of delivering a process and the quality of output.

We can scale automation without having to pay attention to the infrastructure for doing so. We don't have to be worried about the cost involved with the on-premises setup. It is a cloud-based solution. So, when a requirement comes up and a bot is developed, only then we need to apply for the license and procure a bot. It has been beneficial because we don't need to pay any upfront cost until the bot is developed and ready to be deployed, and because the bots are delivered completely through the software service, that also indirectly proved very beneficial for global deployments and scaling of processes.

Its AI functionality is helpful to learn from the existing use cases and then implement the learnings on the new and upcoming test cases. As a developer, we need not spend any time developing templates for the extraction, etc. The AI module in itself has the capability to understand new forms of data. It can then accordingly extract and plug in the data to our templates without much effort. So, AI functionality has saved a lot of our time in developing a solution as compared to doing it the manual way.

We had one process where we had to use AI functionality, and we were able to eliminate any manual efforts. Previously, we had somebody who was verifying the output of the bot and after that only processing went to the next step, but with AI, we got the confidence that the bot has the ability to complete the action without manual intervention. That is one great example where AI helped to eliminate manual effort and improve the quality of the output.

It has significantly reduced human errors. Bots have quite a high performance rate with minimal or zero errors. The errors only occur because we haven't updated the business case in the bot. Once the business cases are updated in the robot, we do not see any errors. The bots follow all the steps as programmed and do not deviate from the set of rules defined while developing them. This reduction in human error has had a positive impact on users. The users had been feeling more comfortable using the robot output rather than relying on their own output, which sometimes had errors. So, overall the confidence level has improved and the lead time in delivering the output has also improved. The time they were earlier spending on the validation of their output has reduced. 

It has freed a lot of time. We only automate processes where we find huge time savings. We count it as full-time (FT) employee benefits. We only pick processes that have three or four cumulated FT benefits. With automation, we are saving at least three or four hours on a daily basis. This time is being utilized by business users in completing any other backlog work, focusing on other important things, improving their own work skills, etc.

Excel automation is extremely reliable. Excel integration is one of the top features that I have been using. We also have a feature called Document Understanding for processing the PDF format of an invoice by a bot. It has the capability to scan an invoice and then pick out the required fields, such as the name of the vendor, the details of the products being sent, or the cost of the product. There is an AI functionality that allows a user to program the required fields to be extracted, and the bot automatically follows those rules and extracts the data. Therefore, the AI functionality of Document Understanding is another important attribute that I personally like about UiPath.

I also like the Computer Vision functionality, where UiPath provides image processing abilities for robotic process automation. This provides a big advantage because images can be automatically processed without involving any additional tools. With an API, we can automatically link the Computer Vision engine and start extracting and processing images at a quick rate.

UiPath is a low-code platform, or mostly no-code platform, where coding is minimal. We can drag and drop all the required steps and then develop a bot in very less time. I am good at programming, but even a user who doesn't know programming can easily pick up the tool. The ease at which anybody can learn it is quite high. Overall, it is a 10 out of 10 in terms of usability. It is really easy to use with the tutorials that they have in place. Everything about it is quite simple.

We use Orchestrator to keep a track of all the robots that are deployed, monitor the logs, and deploy the robots on the runner machines. We use Orchestrator to upload the bots from Studio to the cloud and then deploy them to runner machines across our virtual machines. Once a bot executes, we get the logs, and if needed, we can monitor them to check that the processes are coming in smoothly. In case of any failures, Orchestrator also has the functionality to re-execute the process. So, we are utilizing the cloud to a greater extent for managing our robots.

The UiPath community is wonderful. It is one of the best communities where we can get a solution for any question that we post in a matter of minutes or hours. Whenever we post a question about any doubt or a bug, someone from the UiPath support team or community replies. Their knowledge is useful for other users who might face the same problem in the future. They have an MVP promotion where if I answer more than 100 questions, they provide us freebies or maybe certification vouchers. That's a good thing that they're doing to grow the community. I'm really enjoying the community members' involvement as well as their support shown during any problems that we face. I have also used Power Automate, and the community support of Power Automate is not that great, but the community of UiPath is very responsive.

It is expensive. Its licensing structure should be improved. They can introduce a license structure where they charge you on a per-minute basis rather than a full upfront payment. 

In UiPath Academy, the certification that they provide at the end of every course can serve as a good motivating factor for somebody who's learning it. That is a good thing, but one of the negatives is that previously, the certification program was free of cost, which helped a lot of developers to become certified developers, but recently, they introduced a paid certification course. I wasn't expecting that move from them. I would like them to go back to their initial certification method which was free of cost.

Sometimes, we do find that the bots misbehave or there are bugs that prevent the bot from executing even when the business cases are completely listed out. It could be that the cloud Orchestrator doesn't send the trigger to the runner systems to start the process because of small internet fluctuation. Sometimes, we find that the processes are killing the execution themselves and going into a halt state without any errors in the program. So, we do see some reliability issues, but these happen once in 20 or 30 instances. They are not on a regular basis. However, when that happens, it does create panic, and we have to immediately rectify it. If they can focus on that, it would be good.

I have been using UiPath for three years.

It is great. We are able to scale at a rate faster than what we had thought of because of the way we are able to develop our processes. UiPath literally automates most of the processes that business users are doing. So far, we haven't had any use cases that cannot be handled with UiPath, which helps in scaling implementation at a faster pace.

We have about a four-member team with analysts as well as developers who work with it, but the developers basically handle all the IT-related tasks. 

We are a manufacturing company, and we have deployed our solutions in almost every department. We have finance, planning, control, human resources, sales, and supply chain. We have 15 to 20 in each of the departments, and they are saving close to three hours individually. Overall, our estimated time savings are upwards of 100,000 hours annually. 

Our current usage of it is 30% to 40%. We still have a lot more potential to tap. We are still on the journey to reach 100% of user involvement where everybody is aware of the process. We are yet to hold the discovery workshops with all the users so that they're aware of the process. Right now, it is limited to a few people within the departments, but its usage will increase with time as we continue to automate processes at this rate.

We use UiPath Academy for the certification or onboarding of new members. When we onboard new members, we tell them to go through the UiPath Academy to get an understanding of the tool. It is free of cost, and it covers all the required modules for becoming an RPA developer. We use it extensively during the initial days as a developer, and over time and with experience, we learn directly from the tool.

They have a very responsive community. Sometimes, within minutes, we get a response to our query. We are quickly able to understand the solution that they provided and implement it. If it is a complicated problem, sometimes, the UiPath moderator from the UiPath company responds to the query and resolves it. If it is not resolved, we can directly contact their customer support. We are enterprise users, and we get quick responses to the queries that we raise. I would rate their support a 9 out of 10.

Positive

In between, we used Power Automate just to see the functionality, but we did not find it as intuitive as UiPath. We gave up on Power Automate, and we are now full-time users of UiPath.

I was around when it was set up. I had personally taken care of the installation. I found it easy and not at all time-consuming. I was done with the process in a couple of hours. In about four or five hours, I was done with the installation and setup of Studio and Orchestrator, listing the licensed accounts, and deployment of the random bots. Everything was completed in a matter of no time. I am not directly related to the IT department. I am just a developer, but I was able to handle it with no external support.

We did it in-house. We only contacted UiPath. They delivered the license keys, and we just keyed in the license keys, and it started working. That's it. Nothing else.

It is lightweight in terms of maintenance. There's no maintenance at all. It automatically handles all the upgrades via the cloud. There are no issues. It requires zero effort from IT.

Overall, you don't have a lot of savings because of expensive licenses. The licenses are quite expensive, and they are not cheap. It saves money but not significantly. However, we are not focusing so much on the monetary benefits. We are focusing more on the quality of output and time savings.

It does reduce the cost of digital transformation, but that happens after a year or two from deployment. Immediate benefits are not evident, but within a period of one to three years, we are able to make a huge amount of savings in terms of time. 

This digital transformation doesn't require expensive or complex application upgrades or IT application support. We didn't have any issues, and we never needed IT to support the UiPath tool. We have been directly using it as it is without making any changes. The impact of this digital transformation on our infrastructure was zero. There were no costs involved. It was used as it is without any changes in the infrastructure.

During the initial two years, we hadn't reached a breakeven point. When the development was going on, we had both costs. On one side, the manual effort was going on, and on the other, there was the licensing cost. So, we didn't have cost savings. After the bot was implemented or after about one and a half years, we were able to receive proper monetary benefits or what we call a breakeven point. So, when we started eliminating human activity, that got converted to cost savings. The accuracy of the process also indirectly improved our customer satisfaction. All in all, we were at a breakeven point, after a two-year period. That would be the general thumb rule for most organizations. So, at an immediate level, we did not receive monetary benefits, but after a period of about two years, we received monetary benefits or savings.

We rely on UiPath Academy for knowledge during the initial days, and it saves a lot of time. We don't have any monetary spending for setting up training because it is available for free. So, we have made some savings. It has saved us time and money, and it has been helpful in getting employees up to speed on the solution.

It is expensive. Every product or component is built separately. All the components have a separate fee. UiPath Studio has a license cost. The cloud has a license cost, and bots have a license cost. These costs are recurring on a yearly basis. So, every product or component has to be licensed for a year, and on expiry, you have to renew it.

Their licensing structure should be improved. The cost of a bot is a lot. It is more expensive as compared to some of the competitors. It is probably $8,000 for an unattended bot. When I did a search on the internet, I found that other vendors offer much better plans. I would like UiPath to introduce some flexibility in the licenses. Instead of a full license, they can maybe introduce a license structure where they charge you on a per-minute basis rather than a full $8,000 upfront payment. If I'm just spending eight hours on the bot, the bot should only be charged for that time. There could be a per-hour rate. A plan like that would be beneficial.

Initially, it will be expensive, and it also won't be as per the initial thoughts that it is going to be a quick solution that saves a lot of time. With time, you can achieve cost savings but not immediately.

We had our eyes on UiPath from the beginning. We did not focus on others.

My advice would be to not use RPA as the only solution. You also have to use other complementing features, such as optical character recognition, so that the overall solution is usable. Just RPA can't solve all the problems.

There should be proper change management to bring awareness about the impact of RPA. A lot of time, people misunderstand and take it in the wrong sense that they might lose their jobs. The fact is that RPA can't automate everything, and skilled people will still be required for doing activities. We can only automate a certain set of manual activities.

I would also advise taking one step at a time. Automate a few solutions, check the user feedback, and then start scaling up rather than immediately scaling up without getting the user feedback.

I would rate UiPath an 8 out of 10. Overall, I have no complaints. Studio, Orchestrator, and all the other tools are top-notch. They are being updated with new features on a daily basis. The product is extremely good, and I have no complaints regarding that, but the license is something they can focus on. They can introduce some innovative plans for procuring the license.

We are targeting utilizing Gen AI for some social media marketing. We haven't really implemented it yet.

Implementing AI and automation has streamlined our processes, allowing us to focus on more important day-to-day work instead of repetitive tasks. This has helped with customer satisfaction. 

We have been able to automate a lot of internal processes, saving significant time for our managers and increasing the accuracy of reports and monitoring. We saved about 350 hours, which corresponds to approximately $500,000 in money saved.

The most valuable features are the autopilot or copilot AI feature and Insights. We haven't used it yet. I know that understanding the document is highly powerful and really useful.

I would like improvements in UiPath Studio speed. The development environment is sometimes slow, depending on the workflows, especially with legacy workflows.

This should be the third year of working with the solution.

We utilize the cloud Orchestrator, and it has been really stable with no issues.

We started with three bots and have maintained that number, with the addition of one test bot test license. We are always using it to scale.

We access resources at UiPath to assist us, however, resources can be hard to get. Better access to resources might improve the process.

Positive

The initial setup was simple for us. I am aware it could be more challenging for on-premises deployments.

We didn't use a partner for the initial setup.

We realized a return on investment by saving about $500,000 due to automation of tasks that took longer manually.

It is probably in line with the market. I am unsure about pricing for AI units as we haven't implemented them yet.

I would rate UiPath a nine out of ten.

The solution is to get requirements over to Jira, then we use it to automate some of the processes. We can automate changes and statuses.

The solution is user-friendly and easy to handle. Anyone can understand it pretty quickly.

The robots are helpful. The orchestrator is easy to operate. 

The UI is simple and easy to understand.

It makes automation very easy. There are some use cases where you need a small amount of coding. It's a very low-code way of automating. That means you don't need much knowledge to start building what you need. Overall, it's easy to learn. You can even Google questions and find solutions to your queries. 

We can make end-to-end automation, even though I might now always use it that way.

The user community is very good. On their own website, you can find a lot of great information.Their documentation allows you to understand it pretty well. There are videos as well. They make it easy to understand and follow along. Seeing it visualized makes things much easier. And if you have any errors, there are many people all over the world that may have already dealt with those, so you can get information to help you adjust. 

Since it's low-code, we saw the benefits of using UiPath very quickly.

We've been able to minimize our on-premises footprint. 

I've used the UiPath Academy. I've been certified. There are lots of videos and you can go through and you can complete any number of certificates. 

When you make automation, you can save a lot of time. Using it, you can reduce your manual output. It helps VAs and managers save time.

The automation saves on manual labor.

They already have a good overview of the product and training. I haven't found anything significantly negative about the product. 

The pricing can be a big factor for a lot of users. It could be reduced to help more companies leverage its automation capabilities. 

I've been using the solution for the past five years. 

The stability is good. We haven't gotten any kinds of errors. 

The scalability is good. 

I've never contacted technical support. 

I've used other RPA tools, such as Automation Anywhere. People do need to have a bit more knowledge about AA before using it. 

The deployment is very easy. There are just some steps you need to follow. We were able to deploy it in three to four hours. We had three people handling the deployment process as well as testing and creating automation. 

There is maintenance if you make any changes to processes. For example, if an endpoint changes, the automation will need to be changed. 

Automation Anywhere may be more widely used than UiPath based on pricing. 

We're UiPath end-users. 

They have a feature called communications mining. However, I haven't used it yet. 

I'd rate the solution eight out of ten.

It's a good tool to start with when exploring RPA automation, and there are many free items available on the UiPath Academy website itself. You just need to log in, and you can get certified and start practicing. You can start practicing with creating your own bot. It's a very easy tool, and very user-friendly. With small, low-code capabilities, a non-technical person can learn it; it just requires small amounts of coding.

We have a lot of use cases for UiPath including automation of processes and reconciliation.

Building automation using UiPath is easy.

It helps our operational efficiency by saving time and reducing costs. Manually processes that take an hour can be done in five minutes using UiPath.

The most beneficial feature of UiPath for our workflows is the seamless database connectivity.

UiPath facilitates end-to-end automation for well-defined processes. This eliminates interruptions caused by manual steps within the workflow.

The UiPath User Community is large. There is a lot of interaction and sharing making it easy for us to find answers to any issues we may have.

The biggest benefits we have seen using UiPath are the cost and time savings.

It has helped save around ten percent of costs.

The UiPath Academy courses are great. They have a lot of helpful courses.

UiPath has reduced human error by 70 percent.

UiPath excels at integrating with a wide variety of systems, including on-premises systems, legacy systems, and web pages.

The high cost of UiPath licensing significantly reduces the value we get from the solution. A large portion of the cost savings we achieve are negated by the licensing fees.

I have been using UiPath for four years.

I would rate the stability of Uipath eight out of ten.

I would rate the scalability of Uipath eight out of ten.

The technical support is great with the premium service for enterprise-level clients.

Positive

I'm certified in Automation Anywhere and currently use Microsoft Power Automate. However, UiPath seems better suited for enterprise-level automation. Unlike Power Automate, UiPath is system-agnostic. It can connect to any system, regardless of platform, making it highly versatile. On the other hand, Microsoft Power Automate prioritizes integration with other Microsoft products. Connecting legacy systems with Power Automate often requires purchasing premium connectors and potentially hiring an expert for configuration.

The deployment took around two weeks to complete.

We engaged Deloitte as our consulting firm for the UiPath implementation. While we handled a significant portion of the on-premises work ourselves, their team provided some technical assistance. Overall, I would rate their services a six out of ten.

UiPath promises a 50 percent reduction in operational costs, but the high licensing fees may consume most of those savings.

I would rate the cost of UiPath eight out of ten with ten being the most expensive.

I would rate UiPath eight out of ten.

We have around 15 users that work with UiPath for the attended bots.

UiPath Orchestrator requires regular maintenance and updates.

I recommend UiPath. The only negative area of UiPath is the licensing fees. 

I use UiPath for work projects that involve various applications, including license rebate processing and healthcare licensing. I develop reusable components for these projects.

Specifically, the process involves launching different licensing websites and extracting essential information such as license number, status, effective date, expiration date, and any disciplinary actions. This data is collected from providers like physicians, dietitians, opticians, and speech therapists. We validate the extracted information against existing databases or applications, updating records where necessary.

This validated information is crucial for determining the approval or denial of applications, such as those related to provider enrollment. Essentially, my work centers around creating processes with defined inputs and desired outputs.

Currently, I'm focused on a project within the manufacturing sector, specifically a constant bidding branch. Here, we gather order information for stakeholders, including tracking numbers, tracking statuses, and approximate order values. We store this data in an Oracle database, generate a CSV file from it, and distribute this file to stakeholders via email.

Building automation using UiPath is easy for developers. It is easy for them to manage and start building with the automation.

UiPath empowers organizations to improve their staff's time management and become more cost-effective. By automating routine tasks, it frees up employees' valuable time to focus on higher-priority work. 

UiPath enables end-to-end automation. Our process begins with meeting stakeholders to determine which processes are suitable for automation. We assess if existing tools are sufficient or if new ones need to be implemented. We also identify applications that automation could potentially replace. If all requirements are met, we obtain sign-off for automation and prepare process documentation, such as Process Definition Documents. We then consult with business stakeholders and obtain managerial approval on the Solution Design Document. This phase can take several weeks and involves outlining the specific solutions and applications required for the automation. Next, we create a video demonstrating the automation workflow and explain the process to stakeholders. After securing sign-off from management and SMEs, we begin the development phase. The completed development is sent for UAT and then moved into production. We typically monitor the automation in production for one to two months. Any errors trigger email notifications, allowing us to promptly address issues within UiPath Studio and re-deploy to the live production environment.

The UiPath User Community is a valuable resource for developers. It allows us to share knowledge and find answers to questions or issues we encounter, without needing to submit a support ticket.

It has significantly improved our efficiency by automating many manual tasks, leading to a noticeable benefit for patients. Now, thanks to automated benefit processing, patients receive instant approvals or denials from their insurance providers.

Our company encourages us to complete UiPath Academy courses to further our understanding of Robotic Process Automation. These courses equip us with the skills and knowledge necessary to solve complex problems encountered in real-world scenarios. Completing the Academy courses and obtaining certifications can be beneficial not only for career advancement within our company but also for understanding new features and process flows implemented in future updates. Additionally, these certifications can be valuable when transitioning to other companies as they demonstrate our expertise in UiPath products.

Human error is minimized by utilizing exception handling.

UiPath helps free up our time.

The most valuable feature is the easily accessible tool, such as the ARI framework, which I have used extensively. My interest in the ARI framework has grown significantly because the templates are built directly into UiPath, making it possible to automate more complex processes, while also simplifying the development and understanding for developers.

The UiPath Community Edition lacks some key features that developers find essential for learning and building their knowledge base before transitioning to the paid Enterprise Edition. To provide developers with a more comprehensive evaluation experience, UiPath could consider including all features in the Community Edition for a limited trial period. This would allow developers to fully test the solution's capabilities before making a purchase decision.

I have been using UiPath for four years.

UiPath operates reliably around 80 percent of the time. However, automation speed can sometimes be hindered by internal applications.

I had to contact their support once and they were extremely helpful in resolving my issue.

Positive

While I have experience with Automation Anywhere, I find UiPath to be more user-friendly and offer a more robust orchestration tool. Although Automation Anywhere offers child bots and AI IQ bots, it is not as well-suited for handling complex automation scenarios.

The initial deployment is straightforward. We can sign up with UiPath and set it up on our local desktop, or we can deploy it from our cloud cluster.

I would rate UiPath eight out of ten.

The amount of maintenance required depends on the project and the bots being used. On average maintenance is done monthly.

We are primarily automating business processes from SAP applications and a few from a web-based application. 

UiPath reduces the number of human employees needed to do repetitive tasks. A person can only work during normal business hours, whereas a bot can work 24/7 without making mistakes.

UiPath is user-friendly. Building automations isn't complex, and it doesn't take many days to learn. If you have basic knowledge of any programming language, you can start building small projects in 30 to 45 days. 

If it is a fixed process instead of a dynamic process, we can do end-to-end automation. Automating this kind of process is easier. If it's a dynamic process, we need some kind of external integration. 

UiPath's community forums were helpful in my early stages, when I was learning the product. When I got errors, I was sometimes unsure what they meant, so I could go onto the forum and find answers easily. 

They also have these UiPath Academy courses. I've taken the foundational course and the advanced courses on Document Understanding and data manipulation. I still haven't had a chance to work on Document Understanding, but the data manipulation course has been helpful. I learned to do some queries that simplify the workflow and make it faster. 

I have fewer issues with the user interface when I'm using Blue Prism or Automation Anywhere. For example, if you want to perform an action in  UiPath, it's a little tricky because you must click on a particular icon. When you click on that, some selectors are generated. That will change whenever the application updates, so you must change the selector again after the update. When we are dealing with Automation Anywhere, we'll not get any selectors if we are using that action once. 

I have used UiPath for more than two years. 

I had an activity crash once when the permissions failed. When we were using that activity, it automatically created multiple activities. Even though we dragged it and used it only once, it created multiple activities. That only happened once.

I have tried Blue Prism and Automation Anywhere. 

UiPath is deployed on-premises. We only needed to download UiPath Studio off the website and install it. It took about 30 minutes. 

I rate UiPath eight out of ten. I recommend taking the UiPath Academy courses first. Take the foundational course. It has some hands-on exercises with small automation processes. Later, they can complete the advanced course. 

We're a tech consulting company that works for insurance companies. We use UiPath for tasks related to payment processing, deductibles, and denial of coverage. We check each part of the process to ensure that the patient has met a set of criteria. We're checking the deductible to see if it has been met, and we update the notes on the platform. UiPath is useful for all of our clients regardless of the industry. For example, we have used it for payroll and payment processing at Citibank and Doshi Bank. 

A bot can run 24/7, reducing the human labor required. That is UiPath's major advantage. It reduces the number of manual tasks while also improving and enhancing human labor. A manual task that took 10 minutes in the past can be completed in two or three. We are saving a lot of time. 

Let's say we have eight people doing a particular task eight hours a day on a five-day work schedule. Once we automate that task, we can run the bot 24 hours a day Monday to Sunday. Automation reduces our costs and human error. The accuracy and data security are high. It's beneficial all around.

Uipath facilitates data sharing between systems. We have some shared folder packs that enable us to share the data from one system to another. This functionality can be important, depending on the project and type of data. We use some encrypted features. If we want to share data in encrypted mode, we can put it in an Orchestrator folder on-premises so only those with access can see the data. 

The business will share the data, including employee and patient records. All the data is shared within the database.  Either the employees can send data over, or they can access the data from that particular folder. UiPath offers a central portal for managing patient information. We've done a lot of things to extract and utilize patient information, ensuring that it can be accessed by the appropriate teams. We have to train our bots to capture the right information, like the patient's name, address, ID, location, etc.

UiPath is good for data scraping and extracting information from websites. UiPath is approachable, and it makes life much easier by automating repetitive tasks with the help of drag-and-drop flexibility, eliminating human interaction. The drag-and-drop APIs make it easy to get data from the API quickly.

I also like UiPath's security features because it gives us lots of tools to secure sensitive information. We can encrypt the customer data and store it in UiPath on-premises. We can also control access so that only authenticated users can obtain the data. 

Citrix and email automation could be improved. We can use the features, but the accuracy isn't 100 percent. 

I have used UiPath for the past five years. 

I rate UiPath support eight out of 10. They provide us with assistance while we are developing bots. We can send the Orchestrator logs to UiPath to find out where a process is failing. For example, a web-based process might be using an old particular password. The support team will notify us that we need to update the password in the production environment. 

Positive

Before we implemented UiPath, we tried Automation Anywhere. I like UiPath the best because it has capabilities like Document Understanding, AI, fabric, etc. UiPath has more features than Automation Anywhere. When we did a POC of Automation Anywhere, we found that the data scraping wasn't as accurate when working with PDFs. 

The deployment may be straightforward or complex, depending on the project. Before each project, we have a testing phase of about seven to eight days. We have a 10-day monitoring period. In that 10-day period, the developer is also involved with the support. We have a different support team that takes care of most of these things, like deployment and monitoring the processes. If something goes wrong, they have to open a ticket and reach out to the developers. 

Our implementation process involves checking all the business requirements. We look at the software and machines our clients use and the steps involved. Once we know the business requirements, we start working on the modules. We determine how many modules we need and the amount of time it will take to develop them. 

After that, we have a daily scrum call. If we have issues, we reach out to the business, and they will come back with a solution. We need to undergo this initial development phase before starting anything. Once the development is completed, we have multiple process design documents detailing the processes and steps. We also work with third-party integrators. About seven or eight staff members are involved. 

This solution does not require much maintenance once it is deployed and we've granted the access required. Once we've ensured the process is running and done the initial updates, we don't need to maintain it.

I haven't calculated the ROI, but I've heard that other people have seen 60 to 70 percent return on what they invested.

The pricing depends on the project and how many hours we will charge. 

I rate UiPath nine out of 10. There are still a few areas that require improvement. Before implementing, I suggest doing a POC so you can evaluate other tools side by side to see which one is best.