UiPath Platform Reviews

We have two use cases.

One is for our claim accessing process, for which I have developed a process for logging into the client's application. It includes launching the browser and getting logged into the application by entering the username and password and handling two-step verification. Handling that requires some logic. Once logged in, it navigates to the claim status feed and selects the organization's and payer's details. It then enters the required details of the patients. These details are given by the client in an Excel document that the process reads. It searches for the values, one-by-one. If there is no record for the patient whose details are entered, it will throw an error stating that there are no claims present. It captures such exceptions and records them in a separate Excel file.

If that person's claim is present, it fetches 25 to 35 key details from that record and they are written to an Excel document. Once the process is done, the Excels will be sent as email attachments to the client.

The second process that I am currently developing is one where I need to get the data from Google Sheets. This process involves four or five practice management systems. It has to log into each practice management system and, for each one, it needs to schedule appointments based on the data present in the Google Sheet. The process involves navigating to the respective screens, filtering the details, and entering them in a CSV file. Based on that file, we have all the data related to patients' records. The process checks the patients' payment records. There are exception-handling routines and any errors are noted in an Excel sheet. Once all the patients' records have been completed, it closes the application and sends the data to the respective clients. It produces a log file in Excel as an attachment, as well.

Automation has definitely saved us time and money. For example, for data entry, if a person takes around eight hours per day to complete and upload about 200 sets of data, a bot can easily upload around 3,000 to 4,000 sets per day. It reduces the amount of time to get data uploaded. If a person uploads one record in three minutes, the bot can upload the same data in about 30 to 40 seconds. The bot provides much greater time- and cost-efficiency. It speeds up digital transformation.

It has also reduced human error. Among those 200 records that a person can upload per day, mistakes may happen in 10 to 15 records. Bots don't do things incorrectly at any point in time. Values are entered correctly in each field.

As a result, it frees up employee time. If a bot runs for eight hours, a person only has to look at it for a little while, because a bot will definitely do the process perfectly. That means we don't need a human to dedicate much time watching something run end-to-end. If the bot does the process properly for four records, it will definitely do the next 4000 records correctly as well. So there is not much time required of a human to watch the bot.

On the basis of costs in India, where I work, if a person earns 30,000 per month, the cost of the process they work on is 360,000 per year. A bot for the same process may cost 150,000 or 200,000 only. Automating is more cost-efficient than hiring a person to work on the process.

Among the most valuable features is the ability to read Excel and Word documents with API calls.

In the Google platform, I need to generate security-related things like an API key and an API secure code. That enables me to get the data into UiPath. The product is built such that only if all the security requirements are properly done am I able to get the required data.

UiPath is also the best tool for a beginner or someone who has no knowledge of programming. It is easy to learn quickly and to understand. You can get working in it much more quickly than if you had to acquire a programming background.

I would rate the ease of building an automation at 3.8 out of five, as I have only been working in UiPath for the past 11 months. I am now able to understand everything and can design the kinds of processes I need to build. There are many courses available on their website in the UiPath Academy where they completely show you how to do things. Within a short period of time—I spent the first three months in the UiPath Academy—I was able to understand things clearly, including descriptions of the Properties panels and every field. I understand the uses of these Properties.

Also, many of the Activities are pre-built, but if any activities or logical processes are not available, I can get them through third-party packages that are in the UiPath Marketplace. I am able to build automations quickly. In the worst-case scenario, if it's a large project, I can develop that project within two months.

I have used the AI functionality for PDF automations. In these processes, the bot is able to capture the data properly about 70 to 80 percent of the time. But if a document is not proper or it isn't handled the right way, the bot struggles to get the required data. UiPath has to work on this aspect so that the bot will be able to completely capture the data.

There is also room for improvement in the area of third-party integrations. In the last week I have gone through a video for an integration service, but it did not show things end-to-end. Rather, they just explained the connection details only. After performing the steps they showed, I was not able to get things working properly in my process.

I have been using UiPath for around 11 months.

The stability of UiPath is quite good. In some particular areas, the bot struggles a bit and we have to implement Human in the Loop. Those cases are where the bot can't do certain validations. But overall, the solution is stable and accurate in the results.

The scalability is a four out of five. 

At a certain point, we needed support from UiPath. The solution can be integrated with ABBYY. Getting an AABBYY license doesn't happen just like that. You need to get a trial license and it's a long process. We needed support from the UiPath team to get it done.

You can try to get a solution from the UiPath forum or from the documentation sections, but the UiPath support is the best. I have raised three or four support tickets over the year and they have helped me through each issue, completely, to the end. They respond within 24 hours. When you explain your issue to them, they create a step-by-step process to sort it out. And once I solved the issues, they inspected what I had done.

Positive

I used Microsoft Power Automate. I switched because Power Automate is not very user-friendly when compared with UiPath. And when it comes to integrations in the Microsoft product, most of the connectors are still in the preview state. In UiPath, all the integrations are active and enable you to get the desired result. Also, the Microsoft community does not have many active people handling it. With the UiPath community, you get an immediate response for any issue you have posted.

I use the UiPath forums if I have an issue and I'm unable to find a solution or develop my process. If I post it on the forum, in a maximum of two minutes I'll get an email response from other UiPath users, as well as from senior users who may have two or three years' experience. They politely answer my issues. I have also provided solutions to questions in the forum over the past two months. UiPath's user community is absolutely the best one.

The initial setup is completely easy and straightforward. It is just like installing software in a system by clicking "next, next, next." At the end of it, you have Studio in your system. 

If you need to allocate a particular system to Orchestrator, even that is a very simple process and there are videos available on the internet that show you how to set up the process quickly.

Instead of giving a monthly salary to a person, you can get a bot on a yearly basis. It is cost-efficient and will save you money. You'll also get a more accurate and stable result than if you had a human work on it.

Pricing is based on your process. If your process is fairly simple, it will not cost much.

UiPath has enabled me to build automations much more quickly when compared to other tools. If you go with Blue Prism or Automation Anywhere, you need to have some programming language skills to implement things. But UiPath is completely drag-and-drop.

I looked online at which is the best tool. I looked at many details, what each product provides, and decided that UiPath is a better solution as an automation tool.

Overall, UiPath has the best user community and the best, detailed videos. It is easy to understand, there is no coding at all, and even a beginner can create a process in a short period of time. It is also easily integratable. These are the points where it stands out against any other tools.

For us, in some use cases, end-to-end automation means a need for Human in the Loop. There are certain points where the bot is not able to validate things and a human is needed to verify whether the bot has done things properly or not. But bots are able to process 90 percent of an end-to-end process. For monitoring, UiPath has Orchestrator. If any error occurs, the data is immediately updated in Orchestrator and you can easily see the error and the cause, and you can easily resolve it.

In the UiPath Academy, UiPath offers the best content for each module and, after each video, there is a quiz so that we can show we have understood what we have learned from the video. There are also activities and a practice session where we can implement the use cases by practicing them in Studio. If we are stuck at any point after the practice, they have a solution area where they explain the steps you need to implement in Studio to get the desired results. They give sample workflows as well. I don't think any other software tool does this. They even provide detailed, step-by-step videos for third-party integrations.

We use Orchestrator, Studio, and Robot to work with automation in our finance department.

The product improves how our organization functions by automating tasks so users aren't having to spend time doing mundane things.

The most valuable feature is the unattended robots as they completely take tasks out of the user's hands.

In the next release of the solution, I'd like to see process mining to analyze business processes through event logs. It would help the end-users determine what processes need to or can be automated.

As for areas of the solution that have room for improvement, the usability for the end-users could improve so that they will be better able to program on their own. Coupled with process mining capabilities, that could remove the need to involve programmers or IT in the automation of simple tasks. The cloud platform could be improved so we would be able to deploy through that with sufficient security.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of the platform as a four. It is a four because I haven't seen any outages yet but we may need more experience with the product to be sure it is totally stable when we are completely live.

We have about four people are in our organization who are currently involved in our automation program and I can see that expanding as the company improves ease-of-use.

Our team has used UiPath Academy RPA training. On a scale from one to five where one is the least beneficial and five is the most beneficial, I would rate the UiPath Academy RPA training as a five. It is very good and very detailed.

We have also used customer support and it is good. When I called in they were helpful with answering questions that I had and they responded quickly. Usually, we had one person assigned to us that kind of helped us implement and who was familiar with our needs. This helped in several cases.

I was involved in the decision process to move to UiPath. We knew that we needed an RPA solution to take care of repetitive tasks that could be automated and we had been using solutions in other departments. We went through an RFP (Request for Proposal) process when the finance senior leadership wanted to see what RPA was about and how it could help in their processing. UiPath was one of three products that made it to the next stage of evaluations for this use case.

We did simultaneously use a different solution, which was Pega. UiPath was actually already being used in the company but the idea was to expand into the finance processes.

The initial setup process was straightforward. The complexity that we met with was because of the requirements of our own company. The setup, as far as the installation, was straightforward and simple. From the time we purchased the UiPath license until we had our first robot in production was about three months.

We did use a consultant for the deployment. The company was PwC (PricewaterhouseCoopers International Limited). On a scale from one to five where one is very bad and five is excellent. I would rate our experience with PwC as a three. They are not rated higher in our case because they didn't provide us with the best resources. They sent a younger team that seemed not to have really ever used UiPath.

We have only projected a total for return on investment and performance benefits from the solution through testing and past performance as we are not fully live yet. It will probably take six months to see the actual ROI when we know more about the performance benefits of full deployment. The solution has already helped to eliminate human error by about 25% and has saved our organization approximately 2,000 hours.

As far as pricing, I don't know what the company spends on the license. I do know about the robots. I think the attended robot is a little bit too pricey. With the unattended robots, we can put them on virtual machines — not really Citrix but regular virtual machines which are a little bit cheaper.

The vendors who were on our shortlist were UiPath, Pega, Automation Anywhere and Blue Prism. We chose UiPath because we already had the product in-house and we had already gone through all the security checks for the company requirements.

On a scale from one to five where one is very difficult and five is very easy. I would rate the ease of use of the platform as a three-out-of-five. I give it that rating rather than going a bit higher because it is a little bit difficult for the regular users to automate. In some cases, you have to be more of a programmer to automate successfully. Even so, it is better than other RPA tools.

On a scale from one to ten where one is the worst and ten is the best, I would rate the product over-all as an eight. It gets the job done, but there is still a lot of room for growth in the capabilities so that is why I think that eight is a justifiable rating.

The advice I would give to a colleague at another company who is researching RPA solutions is to read up on what RPA is and what it can do for your company. That is where I would start. Then try to go to as many meetups or conferences as you can to find out more about the products and how they are being used.

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.

We use AI mainly around sales processing and document understanding. Our current use cases involve traditional automation, processing different orders, order formats, languages, and language translation, and creating actual orders in any ERP solution.

We've done a Communications Mining POC, and we think that's promising, but we haven't used UiPath's process mining because we have another solution for that. 

We were already using a competing automation platform when we implemented UiPath. UiPath is a more cloud-based solution. We're biotech regulators, so we're trying to adopt new innovations as quickly as they are released. Regarding challenges, we're trying to simplify and automate processes to achieve a higher value and make problem-solving more seamless.

We engage our employees in automation in two ways. At the enterprise level, it's more about making it easy for there to be a centralized intake of opportunities and focus on the value of what comes through. Citizen automation is about empowering and training them on how to use it so they can build more. 

Our organization has experienced productivity increases, financial savings, error reductions, and streamlining of many processes in finance and accounting with UiPath automation. It has helped free up staff time so that they can focus on more value-added work, and when automations don't function as expected, employees can be upset because they don't want to return to previous manual methods.

I don't know about shareholders, but employees who learn to build automation can do more value-added work. It makes them happy. Customers within the company can have people in their teams spend their time on more value-added work, and they have better transparency.

RPA is always good, and UiPath's Document Understanding is interesting. We used the old model, but the new modern Document Understanding is much easier.

UiPath could offer better support for operations. It has all these cool features, but when you still need to build and run these bots. You need to have more features that make it easier to run bots, and they require fewer people to maintain. 

We have used UiPath since 2020, so it has been nearly four years.

The solution is stable, with, for example, only a thirty-minute outage in three years.

It is scalable, but successful scalability depends on how you build automations.

We have premium support, which provides excellent customer service. Our technical account manager is amazing, and that's one reason we keep paying for premium support. 

Positive

We previously used Automation Anywhere and switched to UiPath because it was easier for developers to use and could integrate with more products.

It was complex because UiPath didn't have a biotech-specific offering. We were the first biotech company to use this, so we had to develop a product that would work for companies under regulation. We needed something called delayering. We had to educate UiPath on what it means to do this for health care and biotech.

UiPath helped us save around 500,000 thousand hours. Over our entire automation journey, that amounts to an estimated $25 million worth of productivity hours.

The pricing is very expensive, making it challenging to continue using UiPath when competitors like Microsoft offer cheaper alternatives like Power Automate. Why continue to use UiPath when you're paying three to five times more? 

I would rate UiPath a nine out of ten.

We use UiPath for intelligent automation integrated with machine learning models.

We previously did many of these processes by hand, and our team found that frustrating because it took a lot of time. There was a chance we could have errors in reports that are critical to the organization. UiPath processes are around 90 percent accurate. Since we implemented UiPath, it has become essential to our organization, and we cannot live without automation now.

UiPath has helped us reduce our on-prem footprint. Its AI functionality has helped us automate more processes while speeding up digital transformation and reducing costs. UiPath has saved team members' time, allowing them to spend more time on valuable tasks instead of tedious, repetitive jobs. 

What I like the most about UiPath is that we can build custom activities. If we want to customize functions based on our logic or use case, we can do that. 

We also like the UiPath community. It's the best help you can find online. If you have any issues, you go to the UiPath forum to find answers to existing questions. If you can't find the answer you're seeking, you can post your question and get an answer quickly. The UiPath Academy has some hands-on activities to practice, and they offer a certification. It's a great way to grow your knowledge. One drawback is that the cost of the certification exam is pretty high. 

The most valuable features are document processing and integration with AI/ML models. Using the solution's AI functionality was a bit challenging initially, but once we researched how to use the intelligent automation, it was fairly simple. Overall, building automated processes is easy. The end-to-end automation capability is crucial for large organizations because it reduces time and energy. 

We use intelligent automation for things like document processing. There is a validation center where the ML model extracts some values, and we can validate if it's correct. That aspect could be improved a little. The percentage of values extracted without validation could be increased. It's currently an attended process, but they should give you the option of making it unattended. 

I have used UiPath for more than four years.

I rate UiPath eight out of ten. 

I rate UiPath 7.5 out of 10 for scalability. 

I rate UiPath support eight out of 10. 

Positive

I have used Automation Anywhere. It's also a good solution that's easy to use, but I like UiPath a little more.  I prefer UiPath because I've done more projects on it.

Deploying UiPath is straightforward. The implementation took a few months because our use case was so complex, and we had to optimize the processes to make them more efficient. Our development team has four people. After deployment, the bots require some maintenance. Admins need to update the automations and ensure the bots are running. 

We've realized considerable time savings with UiPath. We were previously reading and inputting information from documents manually. One document took almost two or three hours. UiPath automation brought that down to two or three minutes. 

UiPath is relatively expensive. It's not expensive if you only need to automate one or two processes, but if you need to use more, it's somewhat costly. There's also a free community version.  

I rate UiPath eight out of 10. My advice for new UiPath users is to complete the training first. Get all the knowledge you need to implement automation before you start working on it. 

We needed a solution for users that had too many manual tasks. We're in a large bank, and there are tasks like account opening or other items that can be automated using the UiPath system. It can handle auditing as well. 

We've been able to increase productivity time by using UiPath. It saves time and costs. 

Previously we used the classic activity. UiPath modified the activity and it made it easier to do the development and create accurate products for the customers.

It's easy to build automation using UiPath. There are a lot of ways to make an automation, compared to other tools, like Automation Anywhere and Power Automate. It's very flexible. We can use different codes and use Excel modifications. It's very comfortable to use. 

In UiPath, we've developed a developer foundation and developer processes. If there are modifications to what has been done or ideas for new ways to do something, we embrace that. 

We can implement end-to-end automation. It's important for us. We do need to study the process and then create a process that is a better solution. Our users can study the whole process and come up with solutions and best practices for building automation. The best way to do it is to have one person handle the end-to-end automation so that there is no confusion in the process.

The UiPath Community is helpful for users. It's an advantage. It helps share knowledge. We're able to find the best solutions for issues with it. 

We've used the UiPath Academy courses. It helps users to study UiPath: what it is, how to use it, and how to build solutions effectively. It's great for users who want to study and be more confident in the development process. 

It has helped us reduce the cost of digital transformation. When we have more people, we need to pay more salary, and it takes more time. Using UiPath, we can save valuable time and reduce costs. What a man can do in one hour, UiPath can usually do the same task in half the time. 

It reduces human error. Sometimes people aren't in the right mindset. If they are tired, for example, they can make mistakes. However, a bot always does everything the same way. 

I'd like to see the accuracy improved. Sometimes the development works fine. Other times, it requires some small changes in the development. 

They could add enhancements in AI technology that could be helpful for everyday developers. 

I've used the solution for three years. 

The solution is stable for the most part. I'd rate it eight out of ten. Most of the time, it's working fine. However, sometimes we have small problems with the data connection or pushing data. It can be difficult to identify the orchestrated things. 

We have about ten people on our team servicing clients with UiPath bots. There are three senior developers. We have bots across multiple locations. 

I'm unsure if the solution scales well. 

We sometimes have to ask a lot of questions as the accuracy can be missing. When they provide us with a solution, there are options between classic and modern. It might take a while to fix things or if there are issues again and again the customers can sometimes be disappointed. 

Neutral

I've used Microsoft, Automation Anywhere, and Blue Prism. I'm most comfortable with UiPath and Power Automate.

Power Automate is developing a lot of its own solutions right now for Microsoft. I find UiPath more advanced than Power Automate and Automation Anywhere, which don't have as many features. Power Automate is the most comparable to UiPath. 

The main disadvantage to UiPath is the cost, which is really high. 

When we do the deployment, we have to take into account security, et cetera. It concerns us when we're talking about using the cloud. There may be particular processes we cannot do on the cloud. 

One good developer is all you need for maintenance. If you have to update the system or do a modification, we need to update UiPath. So there is maintenance required and a person does need to watch the process. We provide the maintenance.

Currently, our vendors are doing the installation. After it's installed, we provide all of the bots and processes. 

I don't have any metrics in relation to ROI. 

The licensing is very expensive for UiPath. Many clients are going with Power Automate or Automation Anywhere based on the high cost of UiPath. 

We're an end-user of UiPath. 

Currently, we aren't using AI technology in our solution. However, I like the idea of it. We'd maybe be able to resolve redundancies with it in the future. It may be on our roadmap in the future. 

I'd recommend UiPath. It's very accessible. I use a lot of products and this is the best product to give to customers overall. 

I would rate the solution nine out of ten. 

We have multiple use cases, including banking and finance. We are primarily taking data from PDFs and manipulating it in Excel, but we also build some UI-related automations. 

UiPath has saved my team some time by streamlining our processes. Previously, it took nearly a month to complete the accounting processes, but we've reduced it to one week. Before we implemented UiPath, they were working day and night to complete the task, so it reduced the time by almost 90 percent. We're further refining the process to reduce the time to five or six days.

The solution has reduced human error, which also saves us some time because we don't need to go back and correct mistakes. It's almost 100 percent error-free. It saves us money from server costs when we automate processes because there are typically so many people working on the same task. It reduces payroll costs. 

The UiPath Academy offers multiple certificates, which is excellent because we're asked for certifications during our interviews and audits. We've completed most of the UiPath Academy course. There's a foundational certification, and UiPath offers additional courses when they launch a new feature. We can get a deeper understanding of that particular function. The best thing is that it's free, and anyone can access the academy courses. 

UiPath's interface is excellent and accessible to new developers. It's easier for beginners to learn, and the learning curve is shorter compared to other tools. If you know Python and any other programming language, writing custom scripts is simple. Other solutions like Robocop and Power Automate have less flexibility in the scripting languages you can use.

We can implement end-to-end automation in most cases because we can use a different language if we encounter any limitations. For example, in one of my projects, we had an issue extracting the data from a scanned document. After reading that scanned copy, it couldn't pull the correct number. We could clean the image using Python scripting, and recreate it so that the output was correct. If we reach a hurdle we can't get over, we can switch to a different scripting language. 

UiPath's community is another thing that sets it apart from other RPA tools. Whenever we get stuck on something, we can go to the community to see if others are facing the same issue. There are many queries in that forum. That's how my team often solves an issue. The forum will have the solution 90 percent of the time. It's a fantastic resource. 

UiPath could improve machine learning for its Document Understanding module. We have to train that model to pull the data from different digitized or non-digitized documents. The classification could be improved, but I'm not sure how they could make it better. 

Sometimes, we get an error when we are developing something in the UiPath Studio for Salesforce. It gives me an error when I create one line of code, but I don't get the error when I make the same line of code again. We also get some bugs when UiPath adds new features. If we're developing multiple activities on one core, it can slow the response times a bit, and it will take more time when we try to download the dependencies or other packages. 

If we're doing UI-related automation, updates to the website might remove a specific UI element, and it affects the code. That's a drawback to using UiPath for a website.

I have used UiPath for more than four years.

There are some performance issues during development. When we transfer a process from one machine to another using GitHub, it will work fine on my machine, but it will take time for the other developers to redownload the particular dependencies. It is not going to update immediately. 

I rate UiPath nine out of 10 for scalability. 

I rate UiPath support seven out of 10. Their frontline support agents don't know that much and often cannot recognize the issue. After contacting UiPath two or three times, they finally assigned us a technical person who could resolve the issue within twenty minutes. However, it took two or three days altogether. Our bot wasn't functioning for that entire time. 

Neutral

I have used other RPA tools, including Robocorp, Power Automate, and Automation Edge. UiPath is great for data manipulation. When we want to take values from tables like columns and rows, it's effortless because it's using the .NET language. I use Power Automate and Robocorp because some clients need to develop their processes with these tools. 

UiPath is better than the alternatives, but some of the other tools perform better. For example, if I have the same code in Robocorp and UiPath and run the processes at the same time, Robocorp will complete faster if we're only considering UI-related automation. In most use cases, it's the same, but Robocorp is a little bit faster when automating UI-related processes because it's directly selecting that particular UI element. 

If I want to click to the next page and process the data, it will be faster in Robocorp. In UiPath, it's easier to develop the code and configure the bot, but Robocorp is faster. 

Deploying UiPath is easy. Only one person is needed to install it. It takes around two or three hours to install and configure the solution because the file is larger We have to download UiPath Studio and other components

UiPath requires some maintenance. If the process involves a user interface, we need to adjust it when the website is updated and a UI element is changed. When that happens, we need to update the code that references that particular UI element.

UiPath is expensive compared to other solutions like AutomationEdge, which is cheap. Last year, it wasn't too high, but I believe they updated their licensing model, making it very costly.

I rate UiPath eight out of 10. UiPath is an excellent tool, and you can get support quickly from UiPath. One thing I would note is that you can negotiate with UiPath for lower initial costs, but they will likely increase the price after you enroll. 

I am a UiPath developer. I have automated web-based processes like HR and finance. I have also worked on a use case consisting of web-based automation, Excel automation, and email automation.

The solution reduces FTEs in processes that require 100 people for repetitive tasks. It really helps customers to reduce human effort and guides the robot to do efficient work within the schedules.

It's very easy to manage and automate Orchestrator because it allows plug-and-play models and drag-and-drop approaches.

UiPath should be able to adapt to other operating systems like Linux or macOS. The tool must reduce the activity required for workflow design. It should be made similar to Visual Studio. It should provide a better way to analyze the recursion functions.

I have been using the solution for six years.

Compared to Automation Anywhere or other open-source tools, UiPath's stability is very good. However, when it comes to very complex hybrid automation with high-density bots, where we require many third-party applications, UiPath cannot handle such scenarios.

PDF automation is very complex. Either we will have to use a third-party Python script, or we will have to build a custom OCR. We require good programming knowledge. The product must improve its stability. I don't see much stability. Though it is available in an environment like Mac, it is not up to the mark as it is in Windows.

The product is scalable.

First, we validate with the logs. In logs, we have to identify certain categories of errors. From there, we identify the root cause. During development, we rename all the activities to appropriate annotations so that we can backtrack them accordingly. If there are any exceptions, it is passed on to the Global Handler. If any error occurs, we email the support team with a screenshot. For example, if ten transactions have been processed and there is a system exception, we immediately send a screenshot to the support team.

Positive

The initial setup was straightforward. It did not include the CI/CD pipeline. There were two machines. One was the developer, and the other was the production machine. We had to deploy it into the production machine. An Orchestrator admin and a developer are enough to deploy the solution.

To deploy the solution, we create the package and describe the overall process. We compress it into a new package and assign the robots with the machine key. Then, we create certain asset queues for the processes and upload them into Orchestrator.

Once all the assets are created, we assign a VM to the package. Then, we upload the package and map it to the process name. We add triggers if required, and if any change request comes, we raise the request, the manager approves, and we proceed with the implementation. It is very easy to maintain the product if there are no version changes in the applications.

The licensing cost is very high.

UiPath's cost is very high. When we transfer the knowledge of a robot to another, certain images are not available. It's difficult to identify the XML collectors. A proper annotation or guidance must be given to the user. When a new version is updated, the tool becomes slower. It is very difficult to maintain version history because of the bulk update activities. If we want to convert from Windows to Windows legacy, it is very difficult.

We get the input files from emails. We read the input files, extract data from the template, and open it in the browser. We worked on an engineering product. We used UiPath to get information about the testing and the model's integrity. Certain information was in the Excel file. We had to extract information on whether the model had to be tested with plastic or without a plastic cover. There were drop-down messages. We captured the values and injected the JavaScript modules to autofill the data.

Once the testing was created, we created a sample order. We filled out a form from the input file, gathered all the details into a summary, and wrote an HTML code for it. Then, we sent it to the client and informed them that the test had been created successfully.

For SAP, we did an auditing type of automation. For example, we automated payments and filled in all the information from the template. Then, we had to propose, settle, and release the payment. In SAP, we are using VBScript also. It has some complex scenarios.

If it is a PDF type of automation, I would recommend the latest technology called Document Understanding. I can define and train the fields using certain anchors and then go with extractions. Machine learning models are also possible. It would be the best way to do a PDF automation.

Calling an API would be the right choice if it is an API approach. If we have been asked to download certain files from SharePoint, we create a custom Azure application. We define secret keys, certificates, and IDs. We define certain API permissions. Then, through UiPath, we install Microsoft 365. We can then download the file. If the process is more complex, ABBYY is the best choice.

Building automation using the solution is easy. We need a little bit of programming knowledge for complex or hybrid automation. For easy automation, plug-and-play connectors and activities are readily available in the solution. We just have to get trained and use them.

UiPath speeds up digital transformation and reduces the cost of digital transformation up to a certain extent. We required a ticket-tracking system where we needed additional third-party software like OneDrive and Office 365 to be installed. For Box drive, we had to install SDK. We also had other solutions like Google Drive, spreadsheets, and Zoom APIs. The solution has helped a lot to minimize our on-premise footprint.

It enables us to implement end-to-end automation. It is important for customers because they want to avoid repeated tasks. If a customer wants to search for an email and upload it in a different portal, they might have to open multiple pages. However, if we choose end-to-end automation, things can work in the backend. The Picture-in-Picture mode in UiPath allows the user to work parallel to automation. So, while the robot runs, the user can do their work parallelly.

I have not used the AI functionality much. I have used AI for a POC of a custom model where I had to identify objects from an image. There were many questions like how many people were in the image, how many cars were there, how many street lights were there, and how many fruits were there. I had to find the count of the people or objects and their confidence scores. It was a small POC with the object detection model built with Python.

The product has helped to stabilize standard and structured processes. If the data is unstructured or unorganized, we use ABBYY as a third-party application. We have to train and classify all the assets and forms. The robot trains the modules using the connector and converts the semi-structured data into structured data. We can make automation more scalable using third-party applications. The cost is very high, though. UiPath is not that stable.

I have used the Academy courses. I have also completed enterprise training and acquired a certificate as an RPA developer. UiPath has a very good community. If we get stuck on anything, we can get solutions for our problems. Currently, ChatGPT is also helping us in many ways. My UiPath skills are really good. I keep doing R&D on AI Fabric, automation, and other features. The community helps me to learn.

A little bit of programming knowledge is a must to use the tool. A level one automation or a straightforward case with repetitive tasks does not require much programming knowledge. The user can use the solution if they have knowledge about the dynamic selector and wildcards. They should have a little bit of fundamental knowledge of computers and automation.

Overall, I rate the solution an eight out of ten.