UiPath Platform Reviews

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.

I find the solution easier to use than other platforms and it's a user-friendly way to automate.

I work with Excel files, and I find it helps make it easier to work with the files.

The ease of building automation is okay. I just use the community version, however, I have found it's much better than others. Their community version is more user-friendly than many options. I really appreciate the useability of document processing. I mostly use the solution for document processing and invoice comparisons. It's simple. 

I've used the user community and have been in touch with one person who was very helpful. They've helped guide me. I've gotten positive responses and good answers. It's helped me learn how to do comparisons between two Excel files, for example. 

I've enrolled in UiPath Academy courses. I've also enrolled in Coursera courses. I'm still in the learning process. They have good tutorials.

I've used some of the AI processes. It is very efficient to use the AI functionality. We've gotten very good responses and results so far. We have found the responses we're getting are good. It helps with creating more efficiencies. 

It has helped speed up digital transformation. 

UiPath has helped to reduce human error. We're able to build effective automation. We're creating software boards where the bot will do what we say and pull what we are trying to pull.

The solution does help us save time.

I'm still learning the solution; it has yet to help me save money.

I'm not sure how UiPath is at data scanning. I need to look into this further.

They need to work on security.

I have used the solution for about one month.

I haven't faced any stability difficulties, at least on the community version. 

I've never contacted technical support.

I've used Power Automate and ElectroNeek. I found there were a lot of issues with ElectroNeek and Power Automate. For example, they are not good with ChatGPT or data scraping. They are also not as user-friendly.

The solution was very easy to set up.

The implementation took only ten to 15 minutes. It was my first attempt to set it up. Aside from an internet issue, I had no problems. 

I handled the initial setup myself. 

I don't have any insights into the pricing of the solution. I'm using the community version. If I like it, I will buy the paid version.

I'm an RPA developer who started working with the solution. I recently worked with Power Automate. I'm familiar with the UiPath community version. I'm not extremely familiar with UiPath as I haven't used it for very long.

I'd rate the solution nine out of ten - at least, for the community version. 

We use UiPath to automate various processes across different functions within our organization including back-office operations, with a particular emphasis on finance, procurement, HR, and IT, as RPA technologies initially emerged from the finance sector.

Also, we extend our automation services to areas directly associated with production and supply chain operations.

Our primary goal is process automation, which lowers costs, enhances quality and improves operational flexibility. This is crucial due to our multi-time zone operations, requiring continuous processing. We're also dedicated to integrating various applications within the organization and addressing gaps. While engineering and IT departments have substantial automation, we're working on refining and addressing specific gaps in these areas.

The orchestration process itself offers a high level of impact, flexibility, and ease of development. While we have made significant improvements, particularly in terms of integrations and the seamless connection of integrators to applications, the process remains remarkably straightforward and efficient. It has significantly improved the accuracy of our operations, particularly in terms of quality, and has also reduced the time required.

There's room for enhancement, particularly in the support department and in the area of reporting, to provide a more robust product for gathering insights.

I have been working with UiPath for approximately five years.

The solution's stability is quite commendable and even when we encounter incidents, we consistently update to the latest versions. We typically lag about seven months behind the latest releases because it takes around three to four months for the new versions to stabilize after their initial release. I would rate it nine out of ten.

Scalability appears to be quite robust, especially when we have a solid model in place.

The improvement is needed for their support services. I would rate it seven out of ten.

Neutral

The initial setup was relatively straightforward. Back then, we were using a standalone automation suite. While we now have a cloud-based automation suite, the transition wasn't complex, and we found it quite easy to implement.

We've seen a positive ROI. Our organization, with the assistance of skilled consultants, successfully implemented the system and we established a robust business model and have maintained a centralized approach.

We evaluated several solutions available at the time, all of which were related to end automation. Ultimately, we opted for UiPath and that decision was influenced by the learning opportunities offered through UiPath Academy. At the time, it appeared to have the most compelling value proposition, with a strong ability to market and demonstrate the product effectively compared to other options.

The ease of use depends on whether you're a developer or someone who mainly uses automation. Nowadays, it is much more user-friendly compared to when I first started using it back in the day. The landscape has evolved significantly with a wider range of solutions available today and they've made substantial improvements, especially in terms of document standards.

Overall, I would rate it eight out of ten.

We have a variety of use cases, primarily in finance and HR, which make up around seventy percent of our use cases.

Our focus has primarily been on document processing and it has significantly reduced the time spent on reading documents and manually inputting data.

The AI center's automation has proven to be highly valuable, although we haven't yet harnessed its full potential. It's exceptionally beneficial, particularly when it comes to handling invoices. 

With numerous hospitals generating thousands of invoices, this automation has made a significant impact. Implementing AI in our automation has significantly enhanced the accuracy of our operations. 

These improvements have resulted in increased efficiency and a significant reduction in the time needed for these processes. The last time we estimated, it amounted to around 60,000 hours saved.

Integrating with tools such as Asana or other service and project management platforms would be a valuable enhancement.

I've been using UiPth personally for approximately a year and a half, while my company has utilized it for around five years.

The stability has been excellent, and we haven't encountered any problems.

Scalability is a bit challenging for on-premises solutions. We anticipate that the transition to a hybrid environment and cloud will provide more flexibility.

When we initially engaged with UiPath Professional Services, the experience was excellent, they replayed and assisted swiftly and seamlessly. However, recently that changed. I would open a support ticket, and it would sit untouched for a week with no response. Even after I inquired or raised questions, there was no follow-up. Sometimes, I had to call multiple times a day to get any action. It seemed that some managers had to step in to take control of the situation, and even then, there were delays in responses. I rate it four out of ten.

Neutral

Overall, I would rate UiPath eight out of ten.

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.

Currently, I'm working with the regular UiPath, but in the past, I've worked with UiPath for healthcare use cases.

My use cases for UiPath vary. I've worked with the banking, renewable energy, marketing, and publishing domains. The most recent use case was for data entry, where my company used SAP applications to create orders for the vendor.

My company also uses UiPath to automate processes that deal with courses, such as environmental, employee diversity, sustainable production, etc.

UiPath is set up in my current organization. My organization takes advantage of the vendor's offer for end users to build smaller automation, which is another use case of UiPath.

Automation through UiPath has improved the quality of work in my organization. Using UiPath helped reduce the overall turnaround time for repetitive tasks. Each staff member can devote time to new tasks or other tasks rather than spending so much time on repetitive tasks.

Implementing end-to-end automation through the solution is essential to the organization because it's cost-effective and time-saving. It also helps boost employee productivity because employees now have the time to learn new things, such as the trends in the market, rather than doing many repetitive tasks that give little value. All these make UiPath beneficial to my organization.

What I found most valuable in UiPath is that it's easier to set up than other tools. UiPath, as a vendor, also provides flexibility, which most companies find attractive in the solution.

I would rate the ease of building automation using UiPath as seven out of ten. The gap in my rating would be eventually filled as my company starts using more AI-based solutions. Overall, building automation is relatively easy in the solution.

UiPath enabled my company to implement end-to-end automation. You cannot automate all jobs or tasks, but the solution does at some level, so I like that it provides further flexibility to automate end-to-end.

As for the UiPath user community and its value to users, that community is vast and provides a lot of learning. Users reach out to the community for any questions or doubts about full development, for example, or anything you want to learn in UiPath. The community also has a morale booster for users through the yearly Community MVP.

UiPath helps minimize our on-premises footprint, though it doesn't matter much to me.

I've taken UiPath Academy courses, and I found UiPath Academy beneficial. Back in 2018, when I just started learning from the UiPath Academy, it gave me everything I needed to start using the solution. Later on, I learned advanced development and, just recently, solution architecture, from which I received a certificate. UiPath Academy also gives me information on the latest updates and trends coming from the vendor.

I'm also working with the AI functionality for automation via UiPath, which affects the ability to automate complex processes. Suppose we have a document, in particular, handwritten. In the traditional way of automation, my bot can't read or understand what's written on that piece of paper. Still, with UiPath, you can select any of these features: Document Understanding, Breakpoints, or Automation. The solution's features give my company flexibility and help extend its reach. Previously, my company thought the use cases weren't feasible because my bot couldn't read or understand handwritten text or characters. Still, with UiPath, it is possible to make life easier, especially with the new advances. 

As for the solution's AI functionality enabling the company to automate more processes, my team has not used UiPath in many use cases that require AI, but in the future, when more cases come up, my company will be able to use UiPath more, and it will be beneficial.

I also like that the solution speeds up digital transformation and reduces the cost of the digital transformation. It also doesn't require expensive or complex application upgrades and IT application support. To elaborate further, suppose I'm automating something. I know the application will be upgraded in the next six months; I won't be automating that through my tool because I know it'll be automatically upgraded in six months. I just need to record my use case involving the website or whichever application.

I also found that UiPath helps reduce human error. A human can make mistakes, but your machine won't if you teach it correctly or give it the instruction properly. If you properly provide your machine with data, it won't make a mistake.

UiPath also helps the organization save money overall.

I'd say UiPath is on the right track now, but I feel some aspects should improve a bit, and the vendor could be working on the aspects in my head right now. Governing components in the solution, such as the Orchestrator, and configuring the robots should be easier. I also feel that the vendor should come up with more offerings or features involving AI.

I've been working with UiPath for about five years.

I didn't experience stability issues with UiPath in my current company, but I did in my previous company, where UiPath was down for some time. 

On a scale of one to ten, with ten being the highest in stability, I'm giving UiPath an eight.

UiPath is a scalable solution.

My company purchased a plan where the vendor provides some support throughout the year on whatever UiPath issues the company faces. Getting support is easy, and the team is quite helpful.

I'd rate support an eight out of ten. It's not a perfect ten because the overall turnaround time to solve issues could be improved.

Positive

I've worked with other RPA solutions, such as Pega, Power Automate, and Blue Prism, before working with UiPath.

Pega is a legacy solution, so I'm setting it aside. UiPath is far better than Blue Prism. On the other hand, Power Automate is the real competitor of UiPath because it has similar functionalities with the new web apps in UiPath, but UiPath is more lightweight and requires less coding.

I found UiPath simple to set up. The process was very straightforward. As long as I have complete resources and information, I can get it ready in about two hours.

My company implemented UiPath via our in-house team.

I've seen some ROI from UiPath.

UiPath has a very costly AI automation license compared to Power Automate. After discounts, it costs around fifteen thousand euros, while Power Automate gives you the same features for only a thousand euros, so there's a huge difference in the licensing costs. Pricing for UiPath isn't very competitive.

I'm a solution architect who does UiPath consultancy.

UiPath is currently deployed on-premises and on the cloud, so it is a hybrid environment.

One admin is enough to deploy the solution, provided the developer and the responsible teams provide the admin with all the resources. UiPath can be deployed through a single resource only.

The solution only requires a little maintenance to keep it up and running. A more significant challenge only occurs if you have to migrate from one version to another; otherwise, maintaining UiPath is very straightforward.

In my company, UiPath is deployed across the globe in multiple countries.

I'd advise others looking into implementing UiPath that it is the best tool to automate repetitive tasks. Whether to use UiPath on the cloud or on-premises depends on your environment. For just a few use cases that you want to automate, go cloud-based, but if you have more than ten use cases, I suggest you go on-prem.

I'd rate UiPath an eight out of ten as a solution.