UiPath Platform Reviews

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. 

I am a consultant working on RPA solutions in general. UiPath is one of the solutions that I am using.

The use cases depend on the clients. I have done automation of sending mail with invoices in it. We have used it for analyzing PDF documents, getting information out of these documents, preparing in three different languages depending on the client, and sending invoices by email.

We are also checking VAT numbers on the EU side to validate the client's VAT numbers and related data. We have automated the generation of reports out of SAP for two different managers and teams. We have also automated including specific signature images within PDF documents and sending them to the related service or email address.

We have mainly used UiPath to focus on processes related to the finance department. The targeted processes are the ones that are the most repeatable and require a lot of effort but there is no real focus and attention from the user. Because of its repeatable nature, the risk is that users do not pay attention to the process itself and make mistakes.

Generally, we do not implement end-to-end automation. The idea is not to automate an end-to-end process but to automate a part of the process that takes a lot of time and resources. That is the focus point, so it is not a matter of having an end-to-end process implemented. It may occur, but often, it is a part of the process where the focus needs to be reliability or time and resource consumption.

The benefit for our clients is time and reliability. They quite often see the benefits in terms of the reliability of executing the process, even reporting mistakes or errors that happen during the execution of the process. That is something quite valuable for them.

Usually, it takes our clients at least one month to realize the benefits. If the processes are executed on a daily basis, then it is quite fast, but there are processes that are triggered every month or every quarter. In that case, it will take at least a month or a quarter to see the benefits. Once it is executed, there is quite an immediate benefit. On the other hand, it takes time to analyze the process because often processes or procedures that are written are not in sync with what is executed by the user. We have to modify them. Often, by questioning the end user, you end up finding the shortcuts and implementing them, so the analysis takes more time, and the implementation takes less time.

UiPath reduces human error. That is one of the main reasons why automation is done for customers. Two main reasons for automation are reliability and resource availability. 

UiPath saves time for our customers, but it is hard to know how much time it has saved because it varies from process to process. For example, the process of validating the VAT numbers on the EU website used to take two or three resources every quarter, whereas now, it is reduced to less than half an hour. These time savings are valuable, but the added value is reliability.

UiPath has not had a lot of impact on the digital transformation because the processes that are requested to be automated are already digital. The reason for automation is to speed up the process or make it more reliable. There is no real impact on the digitization of processes.

In terms of the reduction in the on-premises footprint, I am not always aware of the eventual use of the processes that I am implementing for the clients with the bots. I see that some of the bots are not used anymore because they have their own application that includes a big part of what has been automated on their side. It depends on the way they use it and how often they use it because I have bots that are running every day, and I also have bots that are running once a quarter. The ones that are running every quarter are harder to evaluate because people are not always able to see the resources released from executing those processes. Because they are executed every quarter, they are usually not measured. Our clients generally go for automation for reliability.

Specifically in the recent versions, the ability to change the interface is valuable. One of my clients had to upgrade the SAP version and move to a web-based UI. This was handled by isolating the UI interaction within the library for the targeted SAP on the client side. I upgraded that library to handle the web-based, and the bots worked fine after that without modifying anything in them. The usage of libraries is very important for me because it helps a lot in this kind of upgrade, specifically because SAP is used across the company. It is impacting a lot of different businesses within the company.

It is quite intuitive and fully handled by a visual interface. It is no big deal for me. I have been a developer in the past, and I have used Visual Basic and C#. If I need to specify something exceptional, it can be done. It is not a big deal. For me, it is very easy. There is a competitor with an open-source solution called OpenRPA, but for me, UiPath is far better and more intuitive.

There should be the ability to customize the building blocks instead of having to specify everything in every step. We should be able to combine these building blocks to make specific processes faster.

There should also be some kind of templates, similar to Power Automate. Power Automate provides templates for a specific context.

I have been using UiPath for two and a half years.

I am absolutely satisfied with its stability.

I did not have to worry about it so much because usually, my clients want to take control of their bots. They want to execute it when they want, so I have had no experience with the scalability of UiPath. 

I have not contacted their support. When I am developing, I try to make a bot quite stable. I am aware of what is happening and what it is doing, and I can notify people with logs or names of different events that are occurring during the process execution. I know exactly what is happening and where. It is quite easy and fast to diagnose and fix if there is an issue, but it is not often that I have to intervene in production. If a process is designed correctly and safely, not much intervention is required. Clients look for this kind of stability because that will save the time that they will have to spend fixing things in the production environment.

They have a UiPath Community, but I have not used it often. If there is something blocking, I go over there, but generally, I find the solution to the issues through my colleagues.

It has always been on-premises. The setup is quite straightforward. If there is some kind of Orchestrator to be installed, it is more difficult, and it takes more time. Usually, they want to have someone internally to handle the Orchestrator. I am more focused on the bots and the triggers for these bots to be executed. I am not that often involved in the implementation of the infrastructure of UiPath for the operational side.

Bot development duration varies. It depends on the process, but it can take a few weeks to several months. I have bots that were developed in two or three weeks, and I also have bots that took at least six months because they were quite heavy and complex. Generally, it does not take longer than that because then it will not be as valuable to the clients. If it takes more than six months, it is better to have it developed in their own software.

Bot deployment is quite straightforward for most of my clients because, during development time, I take care of environment parameters. So, deployment is quite straightforward. It is a matter of deploying and pressing a button to have the package deployed. We then set parameters in config files, but it does not take a long time to have it deployed.

Bots usually do not require any maintenance, but if the source of data has been upgraded or modified or the UI has been modified, they might require some maintenance. Usually, once the process is running and every source is stable, there is no need for maintenance. When the data source changes or the infrastructure changes, such as the main server being moved or renamed, then there is a risk over there, but it is not a big deal to adapt.

Generally, two or three people might have to investigate the cause of the issue. If the issue is inside the bot, it is not a problem. One person is enough. If it is related to external data sources or infrastructure, it may take two or three people depending on the segmentation of the clients' people in their departments and services.

I do not know about the exact price because I am not selling anything. I propose several solutions to the clients, and the client does choose one of them. If UiPath is chosen, they contact the official reseller in the country. In one case, I had the prices in front of me, and it was not expensive for the service it was providing.

I would recommend it depending on the needs. UiPath can do a lot of things, and I have covered only 20% of UiPath functionality. Based on my experience and the needs that I had so far, UiPath has been quite valuable.

I would advise defining your use cases. That is the rule for everything. Once you have the use cases analyzed, you can specify what is needed, how you would do it, and what is the best solution to have it implemented. One thing that I am doing is that I am mixing solutions, where, for example, UiPath interacts with Python processes that I have developed. Python processes provide information in files. Web scraping is not difficult in UiPath, but it is quite heavy. In Python, it is faster to develop and use than with UiPath. It also depends on the number of iterations and resources available to execute it. It is a matter of the quality of a particular functionality in UiPath. UiPath relies on the .Net framework, and it has its own limitations. It has quite a heavy set of libraries and frameworks. It is a matter of balancing what you are expecting of it.

I would rate UiPath an eight out of ten. It is a good product. It is well-designed and well-executed.

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. 

We are using UiPath for office automation for our clients. We use many activities of UiPath. We are using CV, RegEx, Excel automation, and email automation.

We are working on a project for a billing company in the US that takes care of patient records for a hospital and saves them on a website. We are handling the patient billing system. We have an email as input at the start of the automation. The bot reads the input. In the input, we have the patient's name and date of birth. The bot searches the patient's name in the EMR hospital application and gets the PDF from the application. We have put some filters on the application. In the PDF, we have a patient's details and a record of their visits and the issues they are having. The bot then uploads the PDF on a website.

We process multiple records. There could be 2,000 pages or 500 pages. It varies based on the patient. For example, an 80-year-old might visit the hospital once or twice a week and will have a bigger file with notes and pictures of their visits. We follow HIPAA regulations for extracting patient information.

It is very fast and convenient. Bots give you 100% results and work 24/7. Humans work eight hours a day, but bots can work 24/7 for you. They save time and bring efficiency.

UiPath brings accuracy. It gives you 100% results. When we do things manually, there can be human errors, but bots do not make any errors.

In the last two to three years, we have done millions of processes. If we give this work to a person, it will take that person ten years to process. For automation, we are using multiple instances and virtual machines. If we need more processing, we can use more VMs. It saves time, and it works 24/7.

It has been a good experience. UiPath is efficient and fast. There are multiple RPA solutions, but UiPath is very user-friendly. It is very easy and fast to learn. We do not need to know how to code for UiPath. It is coding-free. We just have to make a logic. We just need to know the basics but not the advanced things.

UiPath saves a lot of time. Bots are ten times faster than humans.

UiPath APIs were helpful for extracting data from the website and doing the work very quickly. We could get the data directly from the website database. It did not require going to the website, typing the URLs, etc. We could directly send a request to the website and get all the required data.

I have used Document Understanding a little bit for extracting the data from the PDF and images. Document Understanding machine learning capabilities, but I have not used it much. Other teams use it, and the feedback is that it is very effective and fast. They are probably using the Enterprise version for Document Understanding. 

There are two things that are very useful. The first one is RegEx, and the second one is LINQ. UiPath is giving us Excel activities, but it is very slow. With LINQ, we are extracting data from Excel in a very quick way. It is very easy and very fast. RegEx is helpful in quickly getting specific data or text from a chunk of text.

We are also using CV. It is very useful because it uses an image for clicking and extracting data.

If we want to learn something new about UiPath, we sometimes cannot learn it directly from the UiPath Academy. We have to go and search on the web. It takes a few searches to find the solution. We do find it, but it takes time. UiPath should give the solution in one area.

I started in 2020. It has been three years since I have been working with UiPath.

It is stable. They are updating things, but it is stable with the previous code.

It is very scalable. The scalability part is very good.

We have a small team working with UiPath. There are five to ten people.

We have not contacted them much. There was an issue one to two years ago, and we contacted their support. They gave us a solution.

I have used Automation Anywhere, and I have also used Power Automate a little bit. 

In Automation Anywhere, we cannot use CVs. Maybe in the enterprise version, we can use them, but I did not see CVs and other activities in Automation Anywhere. It is also web-based, which is not a good thing, whereas UiPath is application-based.

Power Automate is a very useful tool for Excel automation or web automation, but UiPath is the best for our needs.

UiPath is very fast and convenient. It gives 100% results. It is very easy. If needed, we can also use Python or JavaScript code to make a logic for automation.

I was not involved in its deployment. For maintenance, we just update the UiPath version. We have not had any issues.

As RPA developers, we use UiPath to create automation and then we hand over the bots to the support engineers. They oversee the processing in Orchestrator. They see the automation logs and the graphs. If a bot is not working properly, they send us a message to fix it. We are using CV. If the image changes, our bot will give a failure, and we have to fix that. We might get an error once or twice a week.

I am using the Community version in my office and personally.

I would recommend UiPath to others, and I would give it the best rating. I have used other tools, but UiPath is my preferred tool.

I would rate UiPath a nine out of ten.

We use UiPath in various internal departments to automate our HR, financial, and IT operations, including access management and ISO compliance to control traffic.

We have UiPath deployed both on-premises and in the cloud.

Building automation with UiPath is easy. The solution is user-friendly, and we do not require technical knowledge or skills to use it. With a little training, we can start building automation with UiPath. Customer support is helpful if we get stuck at any step, and the dashboard is user-friendly and centralizes control in one place.

We use UiPath for multiple end-to-end processes.

The UiPath User Community is a good place to learn and get answers to questions we have related to UiPath.

The UiPath User Community edition is flexible and allows us to practice and learn for free before taking what we have learned to our enterprise edition of UiPath.

UiPath has improved our operational process efficiency, allowing us to schedule processes to run 24/7 and freeing our employees from repetitive tasks so they can focus on other work.

UiPath Academy courses are useful for our employees. We also have access to the enterprise learning portal, where materials are available.

UiPath has helped reduce human error. When all the prerequisites are met and the process is fully automated there is a zero percent chance for human error. For the processes that are not fully automated, UiPath was able to reduce human error by 60 to 80 percent.

Before UiPath we had one employee tied to one business process and after implementing UiPath we have one employee tied to multiple domains. Our staff now has time to work on other tasks.

The most valuable feature of UiPath is the ability to consume APIs directly from any application.

UiPath is expensive, and its cost could be reduced to make it more accessible to small and medium-sized businesses that could benefit from it. The orchestrator and licensing cost should be flexible instead of hard-coded licensing.

UiPath is limited to one application at a time and cannot process two applications simultaneously. This functionality could be improved to support dual browsing, making it more efficient.

I have been using UiPath for almost four years.

We have not experienced any crashes of UiPath. We have experienced some slowdowns three times this year, but this could be due to our internal network rather than UiPath.

The scalability is good. We can adjust our workflows according to the conditions with no issues.

Technical support is extremely helpful. We contact support whenever we need to upgrade our volumes, and by following their guidelines and prerequisites, we can easily complete the upgrade ourselves. Once the support team responds to our call they are quick to resolve our issue.

Positive

Before UiPath, we performed manual integrations, but the types of processes we could automate were limited. We faced challenges automating any process where humans needed to make decisions or where minor tweaking was required between the target and source applications. UiPath has removed these restrictions.

UiPath is easy to install, and its representatives are flexible in supporting our installation. Upgrading our libraries and maintaining UiPath security protocols is also easy, which makes the overall installation process straightforward.

Two people are enough for the deployment.

We implemented UiPath in-house.

UiPath is more expensive than other solutions on the market, such as Microsoft Power Automate.

The Flex license is around $11,000. It should cost at least half that price compared to other solutions. We must purchase an orchestrator for each platform, which is mandatory and adds to the cost. UiPath should consider this and offer a more economical license.

I give UiPath eight out of ten. The cost brings down the overall rating.

Maintenance is required when running UiPath on-premises for the server, OS, and DB. On a bi-weekly and quarterly basis. We also have to implement tools for the firewall.

I recommend UiPath for large-scale and multinational organizations because they can afford the licensing costs. Organizations should explore UiPath before embarking on a transformation journey, as transformation requires significantly more cost than automating existing legacy applications. UiPath is flexible and can integrate with all applications.

Most of my use cases are spread across all the business units. It's used in accounts payable or for receiving reconciliations. It is also used in directory management and the banking finance sector. 

UiPath has a lot of features and they have added a lot of things. The apps and document understanding are good. We use document understanding a lot, even though they may not be common for day-to-day processes.

The Orchestrator is amazing. It provides a huge benefit including data security and data storage.

We can add a huge number of activities and can input code right into the platform.

While there might be companies that use the product to do automation for good cause, however, so far, in my experience, I have yet to do much of those use cases. I’m more on the business process side.

The product enables us to implement end-to-end automation. When they first launched, people used to have some sort of hiccups, however, now you don’t need different tools to manage your entire automation journey. With UiPath, from the discovery phase on, you have everything you need. We can understand the ROI clearly and can see what we’ve invested and what we’ve received.

The user community is valuable. It has the biggest community. Everyone knows it. One of the reasons UiPath is so successful is the UiPath community. We have tremendous people in the community supporting each other in terms of development or community events. People from different organizations can explain different pain point areas or explain good use cases and share learning and feedback.

We use both cloud and on-prem services. Most companies prefer on-prem over the cloud. From our perspective, we’re working to convert users to the cloud to reduce the footprint. Still, many want to maintain that on-prem segment.

We use the UiPath Academy courses. Since the beginning of my career, I’ve used it. Whenever there are new products that are launched, they will release certain courses for training purposes. I've gone through training at the Academy. I found a certified trainer also to provide training. Overall, having the training available really helps new people who want to kick-start their careers using the app.

They've also implemented community collaboration. If someone from the community has developed something, they will add training based on the community. The user has larger visual data now, compared to what happened previously.

The solution has allowed us to manage digital transformation and reduce the cost around it. Automation really helps boost digital transformation. We've seen cost reduction around resource use and the cost of operations as well. 

We've been able to reduce human error using UiPath. Of course, it depends on the people developing it. However, as long as the people have good implementation experience, we can really minimize errors.

It's helped free up employee time. However, it is not a major amount across every project. Comparatively, it can save a number of hours versus manual labor. 

We have saved money and that's calculated on the number of hours saved in terms of man hours. We haven't cut staff; they are now working on different tasks instead.  

We've used AI functionality. On a real-time basis, we haven't seen many benefits from the AI center. It's not cost-effective to run models on it as of now. We haven't been able to automate more processes. Some projects don't require AI at all. If it gets more cost-effective and has more use cases, that might change. 

The tool continuously redefines itself. They release three major versions every year and target one major feature once a year, like AI, et cetera. However, there are a few features at an early stage and not quite mature yet.

The initial tools are good enough compared to other vendors, however, they are still refining and need to change a lot of things, especially in the AI center, which is not that flexible when it comes to deployment. This is the same for UiPath apps. In most cases, nobody wants to invest a lot of money in attended bots. They need to work on that.

We'd like to see them work towards more stable outcomes to minimize hiccups. 

I've been using the solution for more than six years. I started in 2017.

Previously, we haven't noticed stability issues. In the past year, we have noted issues with stability. There have been some hiccups. 

The scalability depends on the way a company implements it. From a cloud perspective, the scalability is good. That said, the flexibility is there to scale.

We've had issues in the past where products were not working as expected and we've reached out to support. The experience has been mixed. Sometimes it is good. Sometimes solutions are delayed. 

Neutral

I did not use a different solution previously. However, I have used Automation Anywhere, Power Automate, recently, and also Intellibot and Blue Prism.

Power Automate is still quite young. There are still items missing as it's new. 

UiPath excels in the Orchestrator. The flexibility is great as well.

We've worked with both cloud and on-prem deployments. However, people seem to prefer on-prem. Almost all of our clients are maintaining their own cloud and then running UiPath into the cloud from on-prem.

I was involved with the deployment. The setup is straightforward. For the governance and audit security principles, we do need to add in a bit more. We might add, for example, a CI/CD pipeline. 

We tend to have three to five people, part of the support team, to help with the deployment.

There is some maintenance required. We need to monitor our VMs and understand if the robot is failing and if so what is the root cause. We have an interior support team for maintenance services.  

We did not use an outside vendor for the setup. Only people in the department are allowed to handle the deployments due to compliance. 

We cannot calculate an overall ROI. However, if something isn't getting 150% or more, people tend to not want to implement it. So far, we've seen a very good ROI. 

The costs have gone up recently. The pricing seems to be a bit higher for the end user. 

We are UiPath partners. 

I'd rate the solution seven out of ten. The most recent tools are not as impressive compared to what is happening in the market. 

As long as others don't need additional tools like Apps or document understanding, I'd recommend it. There are a lot of features and functionality to try. However, if you need document understanding and apps, I'd advise users to look at their use case, do a POC, and figure out if it's a perfect fit. 

From the perspective of pure automation, UiPath is excellent. However, if a company is looking for AI functionality, they really need to see what else is out there and what is best for them. 

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.

We use UiPath to create automation for our clients. The best use cases are the ones where we automate an old system. We had instances where we migrated one customer's data over to another. Until that migration occurred to the new system, we could get an automated solution using the old system.

The product provides better customer service and builds better customer relationships. Customers receive statuses and reports in a timely manner. Instead of somebody constantly sending out emails to customers, automation is doing it for us.

I was doing automation development before UiPath and did everything typically by code. It had its own functionalities. However, when navigating older systems, we can use the solution's user interface to tell the cursor to go to a specific location on a screen. Another functionality also supported by the product is the ability to select the selectors, where we can define a specific attribute to a button and ensure the cursor clicks it. The user interface guide helps speed up automation development for customers. We can also use background code, so we have coding capabilities and a user interface to navigate some of the older systems.

UiPath provides Cloud Robots functionality but they should provide more Cloud Robot integrations. I feel that Cloud Robots must have a very, very strong integration with AWS or some type of cloud service where that integration is almost seamless.

We use a lot of virtual machines. It would be nice if UiPath checks the virtual machines and ensures they perform well. We have run into some performance issues. The product must have better performance checks to determine whether a virtual machine fits the functionality or if something is missing. It would be great to know if we will run into some issues. We will be able to think ahead of it.

I have been using UiPath for more than three years.

The tool has some bugs, and it doesn’t respond sometimes. However, it’s no more unstable than Windows. It is fairly stable.

We’re new to the tool. Around five people are using it in our department. The product must improve its scalability. Our security team hasn't approved the Cloud Robots functionality in some cases. I've noticed that our time gap is getting smaller, and we may need additional virtual environments. That is why I wanted better integration with the cloud. It will allow us to be able to launch virtual environments immediately. We would love it if the product could provide the same scalability that AWS provides. We would love the same type of scalability when integrating cloud functionalities with UiPath. If it needs another environment, another environment must shoot up right away so that we can immediately start working on it.

I haven't used the technical support. When we contacted the other department connected to technical support, we got responses and workarounds within a few days. The support has been decent. The team replies pretty quickly.

The solution is deployed on the cloud. The deployment was straightforward. The deployment was pretty quick. It was done within a few minutes. For my current organization, we need one person to deploy the product. My organization has multiple departments, but I only operate on one.

The solution does require maintenance. While dealing with our websites, some changes or updates are done, and then we make changes to the code.

I chose UiPath because it offered UiPath Community, where I could learn UiPath on my own without a business license. I like the idea that there's community support for UiPath. We can learn and teach ourselves. I like UiPath Enterprise, too. Since they have a community version, it makes learning UiPath much better and easier.

Building automation using the product is pretty easy. Over time, we get better and better through experience and create it more efficiently. Some of the additional functionality released by UiPath helps us enhance our automation. The solution speeds up digital transformation. We transitioned to a brand-new system. As we transitioned, we spent a lot of money on this new system and found there were limitations to the system. We used UiPath to mitigate that cost tremendously.

UiPath enables companies to implement end-to-end automation. Currently, we do not have end-to-end automation. Our company is going through a strong transformation. The processes are still a bit archaic. We use digital transformation to help us do our jobs first. Eventually, this will lead to automating new processes rather than someone else doing it. A bot doing 24/7 automation is better than someone assigned to do it 24/7.

We are not using the product's AI functionality yet. However, we are looking into incorporating AI functionality. The product has freed up a lot of employee time. The solution has saved us more than $ 400 a month in the current project. The solution has reduced human error. A lot of the work that the bots do is tedious, like sending a hundred emails to customers or consolidating reports from five different sources. Mistakes can happen in these processes. The solution has reduced human error in our organization by at least 80%.

I have used UiPath Academy courses. We have also provided our business personnel with the courses so they can see it from the business side to learn UiPath. I like the user community. There are a lot of forums where people post questions and help each other. There are YouTube videos where people share their experiences with certain issues. The community is strong.

The massive improvement from DBA to RPA is the user interface interactions. UiPath has a free community version. I would recommend the solution to others. I've taken training on Automation Anywhere, but I've never been able to touch it because my previous organization decided to keep it only in one department, and our department never received it. I could never use what I studied in Automation Anywhere because it requires business licensing. There was no community version. On the other hand, we can start working on Uipath on our personal computers. We can also use UiPath Academy.

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