UiPath Platform Reviews

We are using it to automate business processes in the organization.

UiPath has impacted our operational efficiency quite a lot. There are a lot of scenarios where it has helped the end users. We also have benefited financially from it. We have streamlined the processes to an extent. We initially started with a basic data migration process, and now, we have our own intelligent automation and hyper-automation framework. We just get the requirement, put it in the framework, and start automating. We have progressed a lot.

UiPath enables us to implement end-to-end automation. There are certain instances where we do not get end-to-end automation, but those are the things that are out of RPA's capabilities.

End-to-end automation is important because we can showcase our capability more efficiently in front of our management and the client. We can show that something can be 100% automated if there is a use of 100% automation.

They have UiPath Academy. When UiPath was new, we did not have any online resources to go and learn. The YouTube community was small. There were no courses on Udemy or any of the online platforms. The offline platforms were also minimal. UiPath Academy was one place where we could go and learn and prepare for the exam. I got certified when UiPath certifications were free. I have done all the learning from UiPath Academy. As I move up in my role and responsibilities, if I want to learn a few more things, UiPath Academy is still the best place. You get a very crisp and clear understanding of everything.

We use UiPath’s artificial intelligence and machine learning capabilities for hyper-automation. In my understanding, RPA in the initial days was limited to redundant process automation, whereas now, the use of AI Fabric and other components makes the automation more intelligent. We can add decision-making to existing automation. There were many processes where we had stalled the process just because the next step was a decision-making step, and someone had to come and make a decision to move forward. Now, we have our own AI team to build the code that can make decisions on behalf of a person and also learn from the existing behaviors. That helps quite a lot.

UiPath saves time. It saves about 50% of the time. It never saves 100% of the time because we also spend a lot of time maintaining and doing enhancements to the process. Processes are never stable.

We have integrated it with multiple tools. The outcome has been very good. There have been challenges at times with the development, but the integration has been smooth so far.

Computer Vision is one good feature. AI Fabric is another good feature. The holistic Orchestrator platform is another feature that is very useful.

The RE Framework provided by UiPath is quite extensive. It solves a lot of problems and gives us a lot of time back. We do not have to create our own framework.

UiPath is more user-friendly than other RPA solutions that I have used. UiPath also has the biggest community.

Automation Hub needs to improve a lot. About two years back, it kept on crashing. It has improved a lot. We use it but not to a great extent. We try to build our own dashboards by using any of the data analytics tools.

It should give real-time data, and the integration with the servers is not that great. It can be because of the infrastructure that we have.

They can also consider integration with other automation tools because nowadays, a company does not have one automation tool or RPA tool. A company has multiple RPA tools. They can think of integrating the data from other automation tools in one automation hub so that it becomes centralized.

I have been using UiPath for close to seven years.

UiPath is quite stable. I would rate it a nine out of ten for scalability. It does crash sometimes. That could be because of the infrastructure we are using.

The reliability of any process that goes to the end user is tested with a set of data. We do rigorous testing because, at the end of the day, any error in production ends up in a financial loss, so we test the automation that has been built to quite an extent.

I would rate UiPath a seven out of ten for scalability. No technology is 100% scalable. As technology evolves, new features, such as GenAI features, need to be added. Scalability-wise, it can never go to a ten. Another reason why I rated it a seven is that I want Automation Hub to be scaled to its full potential. It has not been scaled up properly. I have got this feedback from different people across the organization.

The organization I belong to works on the use cases for building automation for given processes. We have around 15 developers doing this work.

I would rate UiPath support a ten out of ten. They have been quite supportive when we have raised any query with them.

I have been in the automation field for the last 12 years. I started with RPA with Blue Prism. I have worked with almost all main RPA tools such as Power Automate, Automation Anywhere, etc. I find UiPath to be the most user-friendly. There is the ease of having all the activities in the same panel. You can have the Studio setup and you can review the code as well with the analyzer. It gives a lot of flexibility when you are developing.

The one feature that is very good is that the marketplace is open. People can build their own set of activities and post them there, which is very useful. I myself have built a lot of activities. I have also used activities by other developers to complete my work. The marketplace is very helpful.

UiPath has the biggest user community. Its community is bigger than Power Automate, Automation Anywhere, and Blue Prism. Other than the community, there are also several groups. There are a lot of developers. If you are stuck with any issue, which is quite common, someone will have a solution for it.

Developing automation with UiPath is much easier compared to Power Automate, Automation Anywhere, and Blue Prism.

The deployment is handled by another team. I do not handle the deployment because the infrastructure team handles it. It should be a one-man job. It is not that difficult.

The deployment duration of a process depends on how big the process is and how much time and resources it requires for development. Usually, it takes two to three weeks. It can also take ten weeks depending on the process. 

All tools require maintenance in terms of upgrades, but that is probably handled by UiPath. We only maintain our own processes. If there are some changes to the selectors or any of the UI components, we have to update the project.

With RPA, it takes one or two years to see an ROI. It is not cost-efficient till then. When you start building hundreds of processes and utilizing the full capacity of the bots to work 24 hours, you get a good return on investment. Initially, it was expensive, but as we scaled up, we could see an ROI. We have seen a good profit.

Initially, the ROI is less. It is about 5% to 6% per year, but as the processes mature, the headcount reduces, and the human intervention also reduces. It eventually moves to 30% to 40% ROI.

It is the most user-friendly RPA platform, but it is also the most expensive RPA platform.

I would recommend UiPath to others because it is the most user-friendly. It is also developer-friendly because of the community. It also works across systems. These are the three reasons for recommending it.

We run a roadshow across the organization to understand which processes are redundant. We try to understand which part of a process can be automated by using the general RPA automation and only one tool. We also categorize them in terms of what can go under intelligent automation where a certain amount of decision-making is required. Another category is hyper-automation where we try to understand how to include different tools, such as machine learning code, AI code, NLP data set, or data mining set. If we have an existing tool for data mining and process mining, the final steps can be automated. These are three major criteria. For basic automation, we try to assess the type of automation. Is it desktop automation? What kind of resources are required? Do we need an attended automation or an unattended automation? Based on my experience, almost all of them are unattended automation. We then try to pull in the use cases, prioritize them, and start automating.

UiPath keeps on enhancing its product. Four years ago, there was no AI Fabric or Automation Hub, and now, we have all those things. They help a lot in delivering the project and having a prototype view for all the projects that are running.

Overall, I would rate UiPath an eight out of ten.

I have used UiPath for very few projects. My go-to tool when it comes to automation is Power Automate. The reason for that is that I work in the Microsoft 365 environment, so Power Automate is better connected than UiPath.

With UiPath, I helped some organizations in my company automate tasks like data entry into systems such as SAP. 

I like UiPath. I enjoy working on UiPath. It has a lot of different features to control, especially related to desktop flows. I helped some organizations in my company automate tasks like data entry into systems such as SAP. They had Excel files, and all that data needed to be input on standard screens in SAP. It was taking a fair amount of time to do it by hand. We created a flow that transfers all that data, interacting with the screens in SAP, and uploads that information where another alternative, like an API or mass upload tool, was not available.

It is pretty easy to build automation in UiPath. We could easily implement end-to-end automation. I was consulting a group within my company. I was helping them build the flow. For them, it was a game changer because they would have spent several man-hours trying to transfer all that data into SAP, creating all those SAP items. After that, they were not only able to complete the task at hand; they were also able to replicate and create more automations on their own because they knew how UiPath works. They learned a little bit more and were able to continue to expand the other processes they had.

We were able to realize its benefits quickly. It took us a couple of weeks to finalize the flow, but once it was built, we were able to start seeing the benefits. It definitely saved time.

I like the way that I can reference specific objects on the screen, like a specific text box, and add a value to it. The capability that UiPath has to recognize elements on the screen is what I found most useful at that time.

UiPath has a lot of courses for easy learning. There were several courses that I offered to the organization I was helping. I myself went through several online resources that UiPath offers to figure out things.

UiPath should be less sensitive to changes in the existing UI of the system we are trying to manipulate. If it was more intelligent in adapting to changes in the user interface and the tools we are trying to manipulate, it would be beneficial. If the UI changes or a label is changed, sometimes the whole flow breaks. Identifying where the flow breaks requires going into edit mode and making modifications. It might be quite extensive work with the new, updated UI.

I have been using UiPath here and there for at least two years. It is a part of the solutions that my company offers, but I have not used UiPath as much as Power Automate.

It performs well. I do not see any issues there.

I use Power Automate on a daily basis. 

It was easy. It took us about a few weeks for ideation, selecting UiPath as a tool, getting everything set up, building the flow, and testing.

In terms of maintenance, users continually review and upgrade their flows. They can reuse the existing flows to create new ones.

I am not familiar with the pricing. I worked for an organization where the UiPath was available, so I do not know what the pricing is.

It was through an internal community that I connected with the organization for which I did the automation, and that is a great advantage. They were looking for people to help create automation. I was curious about UiPath, and I wanted to learn. I raised my hand to build that for them. An external community or a learning community is something that has proven its value by creating synergies between people who do not know and people who already know a little bit, allowing them to get together and grow.

In my opinion, RPA solutions are alternatives to digital transformation. Digital transformation is a big project. When you do not have access to those big budgets or the structure to get into new capabilities on an existing system or implement a future system, that is when you go to RPA to supplement the digital transformation. If the use case is not eligible for the big capital investment or the big project investment, you go through the route of RPA.

I would rate UiPath a nine out of ten.

I currently work for a data center company serving real estate clients. Our primary use case for UiPath involves large-scale automation using Document Understanding to process invoices. 

I have two models running. One is for our general invoices, including everything we pay for people coming on-site at all data centers worldwide. There's a separate model for utilities. Accuracy in our utilities spending is crucial for our data center business, where power costs are passed on to customers. 

Currently, we still use traditional machine learning from when we initially developed these models three years ago. However, we are creating a company strategy to implement GenAI and deal with the legal implications. GenAI is something we're considering as an enhancement to our document processing and data collection. We're still trying to figure out how that happened. We're figuring out which documents and data to include in an internal model and draw conclusions from. 

When working with data, our top priority is ensuring that the data is updated, accurate, and well-maintained. There's a structure involved because a ton of our information is in SharePoint, which is a mess. We have two SharePoint sites for every employee.

Some large-scale invoice-related tasks were overwhelming our existing processes and attempts to handle them manually. We are in the data center industry and dealing with all these technology companies, but many processes in the real estate business are a bit more outdated. Many of our people are comfortable working in Excel, and some teams are highly siloed.  One significant challenge I've faced as a UiPath developer is acting as an evangelist within the company.  We want to demonstrate the platform's capabilities and get buy-in from these different teams across the enterprise to raise the level of what we're trying to do. 

UiPath has been helpful with that first step of getting the information off the invoice. I've been learning and expanding my skill set on the workflow side. Many of our automations have a workflow with a human in the loop doing manual review. I look forward to automating between different departments, and that's one thing I want to develop at this conference.

We used to bring on seasonal contractors during peak seasons, and now we no longer need to do that because the existing staff have more capability. That was a big thing when we started. Our accounting team was so busy for the two weeks before and the one week after closing. There was a tiny window when they could engage with any process improvement or look ahead at what we could change because they were so busy keeping up with how things work. We've freed up these people who are intimately familiar with our business and give them more time to apply that knowledge instead of filling out forms. 

We were processing about 2,000 invoices a month when I started. Now we're up to about three thousand. It took about 15 minutes per invoice to process because there were so many different elements. Working with Yardi is challenging. There was a big issue with getting these into Yardi and uploading them in batches. If one invoice in the batch failed, it would kick them all out. We spent all this extra effort troubleshooting and doing all of this. 

Now, the bot can execute this work and upload them individually. If there's a single error, it can be isolated and kicked out as an exception. Someone can manually review it, and the bot can keep putting the rest of the invoices into the system. We've also had a great ROI on the monthly reporting. We generated reports from around 50 sites every week and then distributed them to a long list of different people on different projects. It's straightforward to do and only requires 10 clicks for each report, but it saves massive amounts of time for people. Now, all I need to do is maintain a list of who should get the emails and what projects need reports to run. 

I love developing automations. I often directly help people by improving the part of their job that is time-consuming and dull. In addition to saving time, we reduce errors caused by manually typing things in. I've demonstrated that in different departments at our company.

We won an award for our ESG efforts. I developed an automation to help us report our ESG metrics because all of these customers want reports to give their shareholders about green initiatives. We wanted to take all the data on energy reductions in data centers and distribute it to each of our customers. We had a very complex template that we wanted to iterate on until we delivered the report. I developed a bot that could generate the source data and template of these files for our customers by data center and aggregate them. 

Before I joined the company, they had no automation solution. They tried to do this with mail merge, which struggled because of the variability across our sites. We wanted to achieve greater complexity and offer this table of information when it's available or update it when the final file we're generating varies significantly. We wanted to be able to convert a Word doc into PDF format and aggregate all of those different PDFs at the site level and aggregate those per customer. 

UiPath's Object Repository was huge. I could build these libraries because our industry works with many of the same systems. It's hard to integrate with Yardi's core CRM, and many of our automation efforts focus on getting information in and out of that system. The ability to build these libraries of reusable selectors has dramatically benefited me over the past couple of years. 

I'm excited about all the new stuff around document understanding because I think that is a large area. We can continue expanding and delivering large-scale automations.

The messages and alerts that Orchestrator generates are a little overwhelming. I'd like them to be filtered down to the most actionable things I need to look at. For many things, we set up an automation that will send an email summarizing things to the stakeholders for the automation. With any of these types of things, you're generating notices, emails, and things, so you want to focus on some things that need your attention. 

I started using UiPath while interning and pursuing an MBA. I've always been a huge fan of Excel, Visual Basic, and automation in general. I've been in my current role for about three and a half years, but I began tinkering with UiPath for a couple of years before that. 

I have not experienced any performance or uptime issues with UiPath.

In my current role, it's been challenging to demonstrate the need to grow and bring on more developers. We're processing a high volume of invoices, but the rest of the business has around 200 employees. We have large capital expenditures building these data centers but not a high volume of back office processes. 

I have not necessarily been able to evaluate what it would look like to grow with 20 automations. We could keep a steady pace of new smaller-scale processes and look for new large-scale opportunities, especially with some of these new technologies. However, I don't think we'll be a large enough business to need these massive deployments.

I rate UiPath support 10 out of 10. I have submitted tickets periodically for a specific issue, or when I'm trying to solve a new problem, I haven't faced before. I am the only UiPath-focused employee at my company. I can work on iterating, researching, and troubleshooting. 

 I've always been able to put in a ticket and get on a call with some people. They're able to connect me with someone and help me understand either the problem I'm facing or the fact that we've been able to have more calls recently about new potential. The online community is also an excellent resource for finding ways to approach and solve problems. Their support has been great.

Positive

Prior to UiPath, there was no different solution implemented at my current company. At a previous company, we conducted a comparison between Automation Anywhere and UiPath and opted for UiPath due to its greater flexibility, capabilities, and entry offerings. At the start of my career, UiPath was one of the first to offer free online training and a lower entry point for businesses just starting out.

Automation Anywhere followed suit. While reviewing them, I built the same process in both systems and presented it to our executives. Automation Anywhere seemed focused on the financial industry. It had some excellent features if that's what you were what you cared about, but I greatly preferred the UiPath's general flexibility, capabilities, and breadth of integration. I've done some small-scale things with Microsoft Power Automate. That tool is hard to work with. They try to make it easy for non-technical people, but it means that I have a hell of a time trying to get it to do what I want.

The initial setup was straightforward, and it was conducted in-house. We host our own virtual machines for running automations and we are a cloud customer.

The implementation was done in-house.

We've seen the greatest ROI from large-scale invoice processing, but small-scale operations have had great returns. Before automation, we were processing 3,000 invoices monthly, which took 15 minutes each. It still requires time to review them in the Action Center manually. 

UiPath's pricing and licensing have been reasonable and manageable for us. Despite challenges in constantly monitoring SharePoint folders, UiPath has worked well within our resources. We have a fully dedicated, unattended license for our invoice processing, which needs to be a top priority and is always running throughout the day. We have another one for all of our other scheduled automations, and we've been pleased with that so far.

I rate UiPath 10 out of 10. I'm incredibly impressed with the pace of new features that have come out. I have been working with UiPath for six years since I graduated college, and I'm blown away by what's coming out every year.

For two years, I have focused on automating workflows related to processing documents in formats like PDF, Excel, and CSV. Using the document understanding feature, we have handled forecast orders and purchase order invoices. 

If you use input files like Excel, PDF, and CSV, we can automate file validation, such as checking data accuracy, format compliance, or missing information. It's integrated with Boomi, so after the files are validated, they're sent to Boomi for further processing. 

Boomi provides us with the RTF file, and we use UiPath to validate its contents and correctness. It automates the process of converting the RTF file into an Excel file. Another process is remittance, where we can get files from clients, validate them, and submit them to the credit managers for correction.

UiPath reduces human error by eliminating manual work and intervention. Some human intervention is still necessary, but it has been reduced. Realizing UiPath's benefits takes some time because you may have some issues after the initial deployment. The UiPath Academy was helpful. I took some courses and achieved developer certificates. I'm still learning. 

It hasn't saved time in my work because I'm still spending a lot of time learning the software. It was new, so learning and implementing those things in my work takes time.

My favorite feature is Document Understanding. I haven't used most of the new features, such as AI-enhanced document processing and process mining. The document understanding feature is especially valuable because I can use it to extract and process invoice data efficiently. It enables the quick and accurate handling of structured and unstructured data. 

The flexibility to work with templates and machine learning models for document extraction has been helpful when dealing with various invoice formats and forecast orders. Data extraction from PDF has been smooth, especially with UiPath's capability to handle scanned documents using OCR and AI-based models. 

The taxonomy manager lets you define the structure and categorize data from multiple document types. AI center integration allows continuous improvement in document extraction accuracy by training models based on historical data. I have utilized AI and machine learning models in UiPath specifically for processing complex PDF and Excel documents. 

UiPath's AI capabilities, such as pre-trained invoices and receipts models, have effectively extracted structured and unstructured documents. For example, when processing purchase orders, the AI model identified key fields, such as invoice numbers, dates, line items, and currency details, with high accuracy. I have found the machine learning models to be especially useful when working with documents that have different formats. In some cases, additional training or validation was required to fine-tune the models for complex or irregular documents. Overall, AI models and document understanding are my favorite features.

UiPath is highly user-friendly because it has drag-and-drop functionality to design and develop complex workflows without much coding knowledge. This has been particularly beneficial when working with different document formats. UiPath's built-in tools and integration capabilities simplify the automation process, leading to greater efficiency.

We have end-to-end automation and integration with other applications. For example, we have portal automation that's end-to-end. We use it to log in to the website and sign in to different accounts. It enters the CAPTCHA, downloads the files, and logs out. It can complete the automation without human intervention. 

UiPath has many resources online. We use its academy and online documentation. If we face any challenges, we can find an answer on the forum or one of these resources. I've never had a problem finding solutions to problems. They have the best resources.

I would love more integration with Third-Party applications. Expanding the library of pre-built, plug-and-play connectors to include more industry-specific applications.

I have worked with UiPath for two years. 

I've never experienced lagging or crashing with UiPath. The app has never given me trouble. 

Installing the community version of UiPath was easy and only took five to ten minutes. 

I am using the free community version. The enterprise version is obviously a little expensive. 

In the past, we have used UiPath to automate repetitive manual processes for companies in the finance and banking sectors, but healthcare is our current focus. This industry involves processing tons of data from patients, customers, and doctors, so it's a huge field. 

Previously, I developed bots for compliance at financial companies. I've also created processes for reading PDFs, sending emails, Excel automation, logging, and exception handling. We have also contracted with insurance companies that need to pull data from emails into their main enterprise application.

The healthcare companies cannot provide us with direct access to their systems for security reasons. We are currently accessing their network through a middleware system so it doesn't compromise their security. UiPath doesn't work on that third machine and cannot retrieve the values as it should. If we scrape data from the web, it will get to the HTML that is behind the site. 

When we are accessing the third PC, we cannot get to it because it is a desktop machine. We are using the completed version activity, which is working mainly on the image image-based activity. This capability is available in UiPath, but I don't think Power Automate or Automation Anywhere can do this. It helps because we don't need to do any coding. 

UiPath tends to be deployed on the cloud, so clients can minimize their on-premise footprint. We deploy on-premise and cloud-based UiPath depending on what our clients want. For some companies, uploading data to the Orchestrator on the cloud is potentially a security concern that hasn't been resolved by the UiPath developers. Power Automate has an advantage in that regard. 

Our employees use the company's credentials to get training from the UiPath Academy and obtain certifications. I have a personal account on UiPath Academy, but it has some license issues. The academy is helpful because UiPath is implementing new features every three months or so. It's all about the documentation. We can learn about new features and do more. With more knowledge, we can develop something bigger.

UiPath reduces costs by eliminating human labor. Let's use an insurance company as an example. Let's say they have employees who are responsible for reading emails. Every day, they receive information via email from the customers, and their job is to retrieve the details and enter them into the main database. The average insurance company receives 400-500 emails daily. These people will spend the whole day completing the task of manually transferring data to their main application. 

We have a bot in pre-production that can handle 1,100 emails daily for the company. It has a significant impact on the efficiency of the operation because the bot can input the details into the database quickly and without any errors. The employees who were responsible for this work are now monitoring it and also learning about UiPath at the same time. It is a great tool for increasing productivity, thereby proportionally increasing the company's profits.

The first company I worked with had 20 employees in their compliance department working on some PDFs. The company had to send emails to around 6 million customers. We deployed the bots, and five bots could do the work of 10 employees. The company kept the other 10 employees but reassigned them to monitor the bots and fix errors. They also learned to develop their own bots. They could cut 10 positions and save money while improving productivity. Those employees weren't working as fast as the bots and cost more money.

The solution also greatly reduces human error. In the financial compliance use case, they were dealing with upwards of a million rows. That was labor-intensive work, and no human could complete the task in under three days manually. Sometimes, we would have some errors in which the values were reversed by accident because humans make mistakes when they are tired. In this kind of work, we're working with digital amounts and currencies, and we are applying mathematical formulas to the amounts, like credit, debit, or some business calculations. 

UiPath doesn't have large hardware or software requirements. We only need one physical PC on the client's premises. That computer requires some minimum specifications, such as a 1 terabyte hard drive and an i5 processor. We need that computer hardware and a license for the client. 

If the client doesn't want to purchase an enterprise license, UiPath offers a community version. There are no restrictions on the features, but it can only run one bot at a time. The enterprise version can run multiple bots. If our client only needs one process, we can provide them with the community version and deploy it on their PC. 

UiPath can free up employees to work on more important things. One of my colleagues was doing some tedious work manually, but once the bot was in place, he only needed to click one button to run UiPath, which extracts all the data and updates the Excel spreadsheet in 10 or 15 minutes. Previously, he spent up to six hours preparing the data before he could complete the other tasks. The important work was being delayed every time. It increases productivity, which benefits the company. 

UiPath's most valuable features are its UI automation activities like scraping and manipulating data. We need to scrape the data before we can manipulate it or save it in another application. I think that part is very valuable and important.

Having worked with other tools like Microsoft Power Automate and Automation Anywhere, I find UiPath to be the most user-friendly because it provides all the actions on the side, and we can just drag and drop them. It's a simple interface that we can easily understand. Automation Anywhere has a more complex interface. UiPath is straightforward enough that our junior employees can easily pick it up. 

UiPath's ability to offer end-to-end automation is critical. We typically provide our clients with a simple demo of what UiPath can do. After that, they provide us with details about their end-to-end processes, which we use to determine what can be implemented through UiPath.

For our healthcare client, the initial assignment was to scrape the data from the website and put it into Excel. Later, they decided that they wanted the data in another application, so it could be stored in the main database. We constructed an end-to-end process for maintaining a million records in their primary database.

I also like the UiPath Community forum. I go there when I get stuck with anything. When I run into an error, it's easy to find the answer. The community is highly active. If I post a question, I can usually get a response from community members in an hour or two. 

I have tried a bot that uses UiPath's AI capabilities, but I didn't develop it. It's a portal for patients to make appointments and check into reception at the hospital. We implemented ChatGPT on an Android device, so customers can ask questions and get information. 

We also developed a bot that can derive the same types of data from PDFs with different structures and formats. For example, let's say the patient's name is on the first row on one form, but on the third row on another. We can configure a bot to extract the name regardless of where it is. We can train our ML module by telling it when the data is wrong and running it again. Now, it's mostly accurate.

I would like UiPath to improve its screenshot feature. It should have the option not to take screenshots unless the user specifically allows it. Sometimes, it is a security issue for companies that do not want to share screenshots of the main application. Another thing I want to see is a standalone mobile application that we can run anywhere. I would like more cross-platform application support.

UiPath can get unwieldy if the process becomes too big and complex. I had one client based in Saudi Arabia that had an application with 1,500 pages. Once the bot we were developing got much bigger, the application started having stability issues. It performs well in typical cases, but once we exceed that average, the application starts to crash or behave abnormally. 

I have used UiPath for four years.

Overall, UiPath is stable for most processes, but Power Automate is better at handling large, complex projects.

I have worked with Microsoft Power Automate and Automation Anywhere. The primary advantage of UiPath is that it's more accessible than the other solutions. You can learn UiPath without any knowledge of programming or computer science. It takes only about a month to learn the tool, even if you have no skills. For example, if you're a blogger and you want to automate posting to the website, you can do that through UiPath, so it is beneficial for personal use and commercial use. 

The other advantage is cost savings. UiPath saves organizations some money, and it's more accurate than Power Automate or Automation Anywhere. Automation Anywhere is my third choice. Power Automate comes in second place because It was developed by Microsoft, and most enterprise companies have a Microsoft subscription. If their license includes Power Automate, they prefer to use that instead of buying a separate subscription for UiPath. 

Many companies are switching to Power Automate because of this bundled licensing. The UiPath enterprise subscription is somewhat expensive. Microsoft can provide the same functionality, and it integrates with tools like Excel and Outlook. Companies can get all those tools within the same license, so that's an advantage Power Automate offers over UiPath.

Another advantage of UiPath is that you can also work with image-based processes. If we cannot get any selectors or access the HTML code behind the application, we can use image-based processes. This feature isn't available in Automation Anywhere. UiPath has the AI center, and Microsoft also implements AI in Power Automate processes.  However, Automation Anywhere cannot use AI in their product.

My current company is smaller, so I'm responsible for multiple tasks. I am the requirement gatherer, developer, and deployer. At my previous company, they had a business analyst who talked to the client and made an inventory of their requirements that he provided to us. Then, my only task was to develop the bot. It was the other team's duty to deploy the bot on the client's physical machine. 

The process involves three steps. We need to connect UiPath and provide the logs. Our client can access the Orchestrator to see logs of what the bot is doing online. He doesn't need to physically access the machine. There is also middleware called the UiPath Assistant that we use to connect UiPath to the Orchestrator. 

The number of staff needed for deployment depends on the complexity of the processes. If it is a single process, we don't need a deployment person or team. The developers can deploy the bots. My company has five developers, so everyone is developing their own bots and handing them over to the deployment team. For every five developers, we have two deployers. If the five developers are developing automated bots daily, we need only two deployers to deploy them on the machine. Also, if we want to have a backup version, we can deploy it on GitHub to make the repository and organize everything.

The maintenance aspect can sometimes be difficult. Exceptional cases can arise during the process. When we initiate some processes, we need to monitor them for about 30 days. We don't monitor some processes because we're not seeing any errors or exceptions. We have to monitor other bots, stop them as needed, handle the exception, and run them again. After 30 days, the bot should be mature enough to handle the exceptions without intervention. 

UiPath offers an excellent return. For example, a recent client in Pakistan was scraping data from a website with 349 products. His job was to scrape the title, price, and variants and place the data in an Excel spreadsheet. He was working all week alone, so I proposed UiPath. I told him UiPath has a function called "Extract Data Table" that can scrape all the details of the products and just dump it into Excel in five or ten minutes. He was impressed, and I developed the bot in front of him. 

Now, he's running my bot and dumping all the results in his Excel sheet. He's also working on other projects, and his routine has become very stable. He has more time to spend with his family. It has surely made an impact and yielded a positive ROI.

I don't know the exact cost, but UiPath is more expensive than Power Automate and Automation Anywhere. 

I rate UiPath seven out of 10. Learning a little JavaScript coding is helpful because there are some scenarios in which UiPath doesn't help you. In some cases, you may need to write a little code to perform some actions or call some functions. I would also take advantage of the UiPath Academy so you can stay up to date on the latest news and features. 

I have worked with most of the UiPath use cases. From 2017 to now, I have delivered more than 400 bots. I have worked in healthcare, energy, shipping, and other industries.

When it comes to manual processes, especially IDP and the combination of IDP and automation, the journey has been a bit difficult and challenging, but it has been worth it. Most other automation is straightforward. We take input from multiple platforms, put it into another platform, and so on. But with IDP, we have to read the document, validate the data, and then integrate it with the automation tool in UiPath.

I started integrating IDP and automation before UiPath Document Understanding and the Action Center were available. What I used to do was automate the process and then create a layout in ABBYY. I would then integrate the ABBYY layout into UiPath, evaluate the data, and then automate the rest. I did this in 2018 and 2019.

Now that we have our own Document Understanding and Action Center platform, I don't have to rely on any third-party tools for IDP. The combination of automation and IDP within a single platform has made a big impact on many businesses. It has helped them to reduce their annual efforts in data entry, reading documents, and correcting small errors in data extraction and copy-pasting.

I have seen the best results when IDP is combined with automation. It has reduced manual efforts by at least 80 percent. Automation is always helpful, but the combination of IDP and automation is even more effective.

In one example, we were able to deploy more than 700 bots for a single organization in the manufacturing industry. They had around 25 servers just to run the bots, but now they are running multiple bots on a single server. They are saving millions of dollars per month by using UiPath.

Overall, I think the combination of IDP and automation is a huge game-changer for businesses. It is helping them to save time, money, and resources.

Most of the elements we have right now as activities with this do not require us to work with the norm of 100 lines of code or anything like that. It is just drag and drop, so anyone can use UiPath from scratch and be approved within a couple of months. The platform itself is very easy to learn and use. I don't think there were any challenges at any point with respect to this.

UiPath enables us to implement end-to-end automation. We have many back-end processes that run without any manual intervention. We simply schedule the bots, and they run flawlessly. We also have a bot that generates reports for us. As a result, we have had end-to-end automation in place for almost a year now. We are very pleased with how it is working, and we believe it is a valuable feature.

The UiPath User Community is great. I am proud to be a part of the community, where I have earned the Community Moderator badge, the Bylaw badge, and the MM VPA badge. I have witnessed the incredible journey of the community, from a group of people who didn't know each other to a community that meets in person at least once a month. The quality of the answers in the forum is amazing. I have seen a few companies create internal competitions to see who can answer the most questions in the forums and receive prizes. These small gestures from the community make a big impact. I would say that the community has played a major role in the growth and deployment of UiPath. UiPath has never failed to surprise and value the community members. The company has never disappointed us, and it continues to support our efforts.

When we join the UiPath Community and become an MVP, we gain direct access to the company's product engineers. We can provide our feedback and reviews for every product and release, and we also have beta access to all products when we are eligible as an MVP. Every review, opinion, and idea that we provide to the product managers is taken seriously and reviewed. If it is valid, the product managers implement it. I think this is the best thing about being a part of the UiPath team, both as a team member and as an individual. I really like the core UiPath team very much.

We have UiPath both on-premises and in the cloud. I think we were able to make significant savings when we upgraded to the cloud, especially in terms of infrastructure costs, deployment, and upgrades. The dynamic nature of cloud computing has helped us to reduce costs and save time.

We often use the UiPath Academy courses. I believe that 80 to 90 percent of my team uses the Academy, and it is the main platform where we have learned to use UiPath. I recommend that everyone take the Academy courses. For anyone who wants to learn UiPath, the Academy is the best place because it has everything we need to know.

UiPath accelerates our digital transformation and reduces costs. We did not need to upgrade to expensive or complex applications to accelerate our digital transformation.

UiPath has reduced up to 70 percent of the human errors.

UiPath has helped free up staff time. We have citizen developers from UiPath who are using UiPath Studio X to save almost 70 percent of their daily time on email automation. Especially when it comes to process mining, they don't have to do the same update task; the processing is ready, and everything is ready to be given to the developers. Even the developers are saving time when using the RA framework for SAP or ERP applications, such as by creating and using libraries of common screens, selectors, and steps. This saves them at least 50 percent of their time, so they can focus more on research and development and new features.

Document Understanding and Action Center have added significant value to UiPath, especially for the IDP process.

There are a few businesses that are failing to generate their ROI. I think that's where UiPath needs to educate businesses so that they can choose the right product for them, whether that's the entire automation solution suite or just the individual products that they need. I think that educating businesses about this will help them a lot and make it easier for them to succeed.

When integrating with third-party tools, UiPath gives us the freedom to write our own code and integrate it. However, if we could get a repository of at least a few of the layouts for the GUI or AI Center, where we would only need to make minor changes, that would be helpful. For example, the files have a template that extracts all the information. I would just like to change a few things, but I don't want all of that. I know we can just hide it, but that won't help because processing the whole document extraction will still take the same amount of time. If we could get those codes in any of the repositories where we could make small changes to the existing code and then import them into our processes, that would be helpful. We do have all the code. We do have all the activities, but none of them are accessible or modifiable. We have to use them as is, or we have to create our own. Those are the only two options we have. If we could get the codes in the report that we want, and then we could make the changes and use them in our own code, I think that would help us more.

I have been using UiPath for seven years. I started my journey in December 2016 and we started delivering projects to clients in 2017. I have been impressed with the evaluation of the UiPath products from 2017 to 2023. The features that we have been receiving in recent years are very good.

When I started as an automation engineer in 2017, people at companies like Sony and other networks and large companies were scared to share their processes and credentials due to security concerns. I have seen this challenge firsthand. However, now, companies of all sizes, including national banks, are looking at automation.

I have seen an incredible journey from 2017 to 2023. I am happy to have been a part of it.

UiPath is stable.

UiPath is scalable. We are able to upgrade anything.

Whenever we have a challenge or similar issue, in rare cases, such as when there are multiple questions assigned to a support ticket, there may be a slight delay in technical support responding.

Positive

The initial deployment is straightforward.

The deployment time depends on the complexity of the project, ranging from six weeks to four months. For a very simple UiPath automation project with multiple applications, we can complete the development, UAT, and deployment within six weeks. However, if the project involves IDP, validation, and other complex features, it may take three to four months to complete.

The number of people required for deployment depends on the complexity. I always suggest having proper planning. I would not let any of the junior developers deploy to production at any time. I would always have two different teams. This is my preference. Instead of having junior developers deploy to production with only one person, even if they are capable of doing it, I would suggest not giving access to everyone to deploy to production. Instead, they should reach out to the production support team, and the production support team should do a code review before the deployment. Once the code is reviewed, the production support team can publish the package to production.

I have seen organizations that have been able to generate an ROI of almost 100 percent, as well as organizations that have struggled to generate even a 10 percent ROI. Some companies are very good at knowing what licenses they have bought and how to use them, but I have also seen companies that have a whole suite of automation tools that they are not using, including process mining and test suites. They are still paying for all of these tools, but they are struggling to generate an ROI.

The main complaint I receive about UiPath is the pricing. Many people purchase the entire suite, which can be expensive, even though they don't need all of the features. The pricing is also somewhat opaque for businesses of all sizes. Unless a company is a UiPath partner, it is difficult to customize the solution to pay only for the features that are needed.

I would rate UiPath eight out of ten. We have experienced some automation processes that did not turn out as expected, especially with legacy applications, which can be challenging.

I have not seen any challenges with UiPath upgrades, but there are a few things to keep in mind. Consider a client with an on-premise deployment. The developers have returned their code, which is very old. After two or three years, the client is finally upgrading. During this time, a few activities may have changed drastically or been removed from UiPath because they have been merged into other activities. In these cases, we need to do some maintenance to ensure that the upgrade is successful. We need to check that everything is ready and that the upgrade looks good. This may take some time, but it is the only maintenance that is required.

We currently use UiPath to process birth certificates. One of my tasks was to apply OCR to the birth certificates and use a named entity recognition model to extract details like the names of the individuals, parents, and the place of birth. The project requires us to handle certificates from all 50 states, and every state uses a different format. 

We're supposed to be doing intelligent automation, but we're not there yet. I work in the applied analytics and statistics section, and we're supposed to find ways to inject more advanced analytical methods into some of these places where we can automate. Our IT department has a CoE that conducts intake processes. They use Automation Hub to review each process, and the executive governance board votes on it. I don't know how they decide internally because I'm not part of that. 

Automation through UiPath provided a framework and a low-code solution, which generally improved the process. It reduced the burden on the workers, freeing them to do what they wanted. 

It is also utilized in identity governance, especially within IT environments. For example, say I want to install a particular piece of software on my computer. There's a process to request access, and it goes through an approval chain. Ultimately, it gets to someone who has to click a button or provision an account. Someone will get an email and copy-paste the stuff from the email into another system and click "provision." 

And when an employee leaves or switches job roles, they no longer need access to a particular system anymore, so you must remove that access as soon as possible. Automation helps. Governance is one area that we would like to use it in more.

UI automation is helpful for interacting with legacy systems, mainframe systems, and various web applications. Someone might use all those things during their jobs, and many of them don't necessarily have APIs, either.

Although improvements have been made, such as auto-healing, there is room for improvement. Changes in the UI can break automations. If you upgrade from Windows 10 to 11, you may need to rewrite some of those UI selectors completely. That is probably the biggest weakness that I can think of.

I have been using UiPath for four or five years.

The solution can be fragile, but there have been significant improvements over the years. The unified target framework, which considers strict, fuzzy, and image matching, helps to stabilize the application somewhat.

UiPath has been able to perform as our organization grows or as the demands on UiPath increase.

In my previous job, I interacted directly with UiPath support, and they were always effective. Currently, support is accessed through IT, which escalates issues if needed, so I have less direct interaction with customer support.

Positive

I've used Python and VBA and experimented minimally with Selenium, but they're not as strong when it comes to UI automation. I've also used Power Automate for Microsoft products. Sometimes, I want to automate Outlook, but I don't want to ask the security to enable the UiPath activity to pull emails. 

We've saved time and reduced human error. 

I rate UiPath eight out of 10.

I've worked in two organizations where I have used UiPath. The first organization was in banking and we used UiPath to help automate banking and financial forms. The second organization, the one I am currently working for, is a technology company with several sub-companies that include banking/financial, the hotel sector, and some overseas organizations. In this organization, we automate tasks that are repetitive, as well as reconciliations.

The main advantage is that we've synchronized our process across 70 sub-branches covering the entire island of Sri Lanka. Previously, we had three or four employees manually inputting the user entries for the various branches. We eliminated those positions so that data entry is now done by robots and performed in the head office.

We have multiple robots directing all of the data to the robot platform in the head office. We saw value within six months. That's how long it took to eliminate the positions. We stopped recruiting people who had previously done that task. More tasks remain, but the main use case was realized within six months.

The APIs are helpful in our workflow. We have a separate application for the government sector, and the Sri Lankan government provides that API. It's a matter of due diligence because we get the customer information, like the national identity card number. We use the API to exchange that information.

We get quick information about existing loans, including how they perform and whether the borrower is paying on time. If they are red, it means that the payments aren't being made in that period of time. That is the kind of information that is exchanged with the API. We can process 20 or 30 users every minute through the API on average.

Previously, our staff onboarding involved a large number of hard-copy documents—around 50. We have automated what was a long manual process, using automation to go through the documents to create a customized onboarding process, one that includes the government regulatory platforms that we are required to use. We used to have to store those documents in an archive, taking up our storage capacity. With UiPath's OCR platform, we get the information we need to do the task. That has resulted in huge savings for the organization, including environmental savings in terms of trees used for paper. It has also saved a lot of the human effort involved in verifying data in those documents.

In our previous process, the documentation was written entirely by humans, including data entry. That data entry was a critical point but there was a lot of human error. That has been reduced by 85 to 90 percent. In my current organization, we have automated about 70 processes and the amount of employee time saved depends on the process. For example, one of our automated processes has saved eight hours for one FTE, while another has saved 10 FTEs two hours each.

And we have done an end-to-end automation for an insurance platform, for renewals. There is no human touch at all.

UiPath has also helped us to reduce our on-prem footprint, compared to our previous platform. In our previous model, we worried a lot about our data. But with UiPath in the cloud, could our entire database be somewhere else, meaning not in our custody? A few years back, UiPath introduced governance and audit platforms, and that's when we felt that it was okay and that we didn't need on-prem platforms anymore. It was okay, at that point, to go for a cloud platform. We are migrating our on-prem platform to the cloud now.

UiPath Orchestrator is incredibly useful. It's the main dashboard platform we use. Orchestrator provides a single platform where we can connect with legacy systems and manage all the bots. 

Orchestrator lets us see the entire process across various department units so that they can see the separate tenants and units. The application can multi-task to handle processes even when we have a long queue. If the queue is piling up, we can assign multiple robots to clear the queue quickly. We can find the ETA for the queues and everything inside Orchestrator.

The Studio and development boards are also helpful.

The UiPath community staff is the best I have ever seen. I have worked in several communities, not only in RPA platforms but for other tools, but the UiPath community is the best. I am an active member of the community. If someone has a question, we always look after it there and are very happy to help them.

The UiPath Academy is very useful as well. My colleagues and I are always going through the new features that are available for our automation and new developments. We always keep in touch with the Academy.

Previous Orchestrator versions were very user-friendly for the admins and the users, but the new Orchestrator is a bit advanced. If they could reduce its complexity, to something more like what it used to be like, it would be better.

Also, if they can improve the performance of robots, that would be good. 

I have been using UiPath for more than five years.

There are no issues with the stability.

It is scalable and very easy to scale but, again, that comes back to the pricing.

UiPath scales easily, but scaling for the cloud and on-premises versions is different. For the on-premises solution, we need to add new licenses to scale up. But it's easy in terms of scalability on our end.

Support can be divided into two tiers: enterprise users and community users. Enterprise users like us get high priority because we are dealing with live operations and customers. When we raise a ticket, we have options like critical and onsite support. They reply in one or two hours, or in less than 30 minutes if it's critical. Their technical support is very helpful and the ticketing platform is very good.

We also get a fast response for non-technical customer service issues.

I hope their support can be developed because when there is a difficult case, sometimes it seems that it's a new issue for them as well. I have experienced that. That should be improved a bit. Overall, support is very good, but there is room for a bit of improvement.

Positive

We didn't have an automation solution previously. As a developer, there are lots of costs in our country associated with switching to automation. There weren't other solutions that could integrate our entire operation like UiPath. I don't think it was possible to select another one.

As a user and an administrator, I can manage the entire server from the main controller. I know everything that UiPath is doing. I also can't think of another solution that has the same broad user community.

UiPath runs Orchestrator and the application in the cloud, but our robots work on-prem in our data center.

In my previous organization, I deployed UiPath, but when I got there I didn't even know what UiPath was. Fortunately, they have nice documentation on the UiPath website, step-by-step. I followed that and was able to deploy things. Since then, I have helped several organizations, via the UiPath community, to deploy Orchestrator within two or three hours. If they have completed the relevant prerequisites, it can be done in that amount of time for a standard installation.

We had a detailed plan in place that progressed in phases. In phase one, we eliminated the data entry function in the main office and the branches. In phase two we would optimize our existing processes. Once all the automation is finished in the head office, we optimize those head office processes.

We have seen significant cost savings throughout the company. Before we started to use UiPath in 2019, we had three or four people doing data entry in every branch. It has eliminated human data entry and also frees up our cashiers because the cashier cannot go anywhere when the queue is long.

We calculated what we have spent for our entire RPA platform and what our ROI is. Our calculations showed that after one and a half years, we had recouped our entire spend on the RPA platform. That included the entire robot cost, servers, the software license, et cetera. That means we had ROI after 18 months.

When it comes to unattended robots, the cost for us in Sri Lanka is huge. It's tricky for us to convince management when they think about the price. We have to prove the value with evidence. We explain that we will save this or that amount, so please help us with this tool. 

Maybe for Middle Eastern or other countries, the price of that robot is not a big deal, but roughly $10,000 for an unattended robot is a very big deal for us. 

They are switching their licensing from a legacy mode to flex licensing. With that kind of license, they have given up a certain fee, which is okay, but the robot cost is high. Orchestrator is now free on the cloud platform, but we need UiPath Studio, the developer platform, as well as attended and unattended robots, and those are the things we pay for. The unattended robots are the highest priced. On a scale where one represents the most expensive and 10 is cheapest, I would rate UiPath at about two.

We have looked at several automation platforms. We have done several demos and looked at the price of Automation Anywhere and Blue Prism. But they are more complex than UiPath.

If you consider other applications, like Blue Prism and Automation Anywhere, the UiPath platform is better because it's user-friendly, making it easy to get tasks done. Even for a beginning developer, it's easy to catch up with all the stuff in UiPath.

UiPath has noticed that I'm an active contributor, so they contacted me to get feedback and invite me to build the community. If I check my LinkedIn profile, I can see all the things I've done in the UiPath community. I don't see that with the Automation Anywhere platform.

If I don't know how to do something, I can watch one video and learn everything I need to know. If we post a question on the forum, we get an answer in one or two minutes from another user.