We use UiPath Studio, specifically the enterprise version, for developing projects per organizational requirements.

UiPath makes building automation processes easy and accurate. It allows us to create a wide variety of feasible automations. Even complex processes can be tackled using UiPath's features, such as object repositories and document understanding.

UiPath offers end-to-end automation, which is crucial for our work. This allows me to handle various tasks. I can efficiently open any web application required by the organization or our clients. I can download documents from web applications and fill in the necessary details within them. I can extract important metadata from documents or web portals. I can store the extracted data in a designated data queue. I would rate the process a ten out of ten.

By automating tasks through the use of robots, we can achieve significant time and manpower savings. This, in turn, leads to reduced costs for the company. Additionally, automation improves accuracy, as robots are less prone to errors compared to humans performing repetitive tasks daily.

I use the UiPath Academy courses in my free time to get some diploma-level certifications.

UiPath reduces the cost of digital transformation.

UiPath helps reduce human error.

UiPath helps to save staff 70 percent of their time through automation. 

The community version of UiPath has a limited feature set, which can make it challenging for users to fully explore its capabilities without purchasing the enterprise version. Offering a trial period for all features could provide a more comprehensive evaluation experience for potential users.

I have been using UiPath for four years.

While UiPath has disconnected on a few rare occasions, it has generally been stable.

UiPath is scalable 80 percent of the time.

The initial deployment is moderate. 

The implementation was completed in-house.

UiPath is expensive.

I would rate UiPath nine out of ten. There are many RPA tools and UiPath is at the top of the list.

UiPath requires maintenance for any changes that are made.

I recommend reviewing the documentation and completing the UiPath Academy courses before using the solution to automate processes.

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.

The use cases are quite broad.  UiPath is used in customer contact centers, supply chain management, operations, etc. It is useful for the intelligent automation of task-oriented processes.

It's easy to sell clients on a cloud-based solution like UiPath because it's the easiest to maintain and run. Some of the customers have already adopted a cloud-first strategy, so it's crucial for them not to have to operate their own data center. Others need to have a data center for privacy reasons. 

The solution helps customers reduce costs by about 20 percent. UiPath doesn't require any expensive or complex application upgrades. It has reduced human error. UiPath has improved outcomes like SLAs and customer satisfaction scores while reducing wasted time. 

UiPath frees up employee time, but the exact amount varies from client to client. It depends on your scope and your use case. You can obviously save time. It depends on how you design the process or whether you're automating one process or 10. 

I appreciate the stability of the UI automation, the studio, and the development environment. I also like the platform's rich capabilities. Stability and performance are always essential when automating through the user interface. This is what they definitely bring to the table. 

Regarding the ease of building automations, I would rate UiPath nine out of 10. It's the best tool in the marketplace. It's easy to build automations, and the interface is easy to use. I like how it integrates with the Orchestrator and everything works together. There are so many different use cases that we can easily connect through APIs, databases, and user interfaces to automate all kinds of applications. 

UiPath's end-to-end automation is critical. It's the most efficient way to automate. You automate mundane tasks so that people can focus on everything that requires expert skills or knowledge. 

The solution's user community is amazing. There's a lot of knowledge and experience, and it's easy to access that information. It's a highly active community. The UiPath Academy also has some attractive content that gives you hands-on experience with the product. The courses are easy to follow. 

I have been using UiPath for about three years. 

Excellent stability.

UiPath's scalability is excellent. 

I have had limited contact with UiPath support, which says something about the product. 

I have used Automation Anywhere and UiPath. I've looked at other options, but UiPath is at the high end.

Deploying UiPath is straightforward. It's fast. You can deploy UiPath in five minutes depending on what you need and how everything is configured up front. You need to get a platform account and set up the machines that will be part of the solution. You also need to set up users and assign them licenses. UiPath requires some maintenance based on the types of packages you're running. One person can do it. It isn't too complex. 

UiPath is relatively expensive. However, it's the leading product because it has so many capabilities. 

I rate UiPath 9 out of 10. When implementing, I recommend sketching out your costs over multiple use cases and comparing them to an alternative solution. 

We use it to automate repetitive processes. We are also using it to manage people and costs.

I have used it for automation in telecommunication, HR, and finance. I have also done two projects for IT. It is a combination. I have worked on all these different projects.

UiPath helps with cost savings and staff savings. We can use manpower for high-value tasks rather than for repetitive tasks.

UiPath helps with end-to-end automation. I have created end-to-end automation through UiPath. It is a high priority for our company. I have not yet worked on the AI functionality.

UiPath reduces human error. If it is a repetitive task, then bots cannot go wrong. They have already been coded with whatever is required, so human errors are generally not there, but there can be scenarios that have not been covered, and they can result in exceptions. We have to work on them and update the bots so that we do not get the same issues.

UiPath improves accuracy. The teams for whom we have done automation are happy. There are no errors. It improves their efficiency. Bots can work 24/7 or at whatever time they want. There is no dependency on time, which is not the case with humans.

The time savings vary from project to project. On average, if a human takes three hours for a task, a bot would take about ten minutes. UiPath reduces the costs, but I do not have the metrics.

UiPath is very user-friendly. There is ease of use. People can understand it very quickly.

It is very easy to use.  It is very good. There are many people who are uploading learning sessions on YouTube, which are free. It is good to learn from there as well. There are many sources to learn and explore it. There is also a community of UiPath users.

UiPath Academy has complete courses for developers and business analysts. A business analyst can follow the course path created for business analysts, and a developer can follow the course path created for developers.

I have been working with UiPath for the last four years.

It is a stable solution. However, if your applications are changing, you will have to do some manipulations in the code. Now they have a feature where you can keep your UI things in your config or in the assets, which is helpful. It is easy.

I do not interact with them directly. There is a team that communicates with their support. 

I know Automation Anywhere, and I have also done a certification on it about four years ago, but I did not work on it. I am not familiar with the features currently in Automation Anywhere, so I cannot compare it with UiPath. I have more experience with UiPath because we got more UiPath projects. We were going to work on a project with Automation Anywhere, but that did not happen.

I have also worked on UiPath Document Understanding, but most of my experience is with general automation.

I have set it up from scratch in one of the companies. It was not that hard. It was easy to set everything up. I was doing it for the first time, so it was a little bit confusing, but it was good. There were forums and YouTube videos. The UiPath team is also available if you need help with installation and what to use. It was good.

After the code is ready, the bot deployment takes 10 to 15 minutes. Three years ago, it used to take us an hour.

I have not worked extensively with any other tool. My experience with UiPath is good, and I would rate it an eight out of ten. I am satisfied with UiPath.

We have many use cases. We have used it in finance, HR, IT, business supply chain, insurance, etc.

It is easy to build automation using UiPath. UiPath definitely provides a lot of value to the organization. There is efficiency and effectiveness.

UiPath has helped to minimize our on-prem footprint. It is very important for us.

The AI functionality has given us a lot of flexibility to go to the management and tell them that we can enhance things. Some of the things that they initially thought could not be automated can now be automated.

The AI functionality has enabled us to automate more processes, but it is not an easy process to understand and implement automation. It is relatively new, and it requires a lot of change management.

UiPath speeds up digital transformation and reduces the cost of digital transformation. 

UiPath has reduced human error. There is an 80% reduction. UiPath has also freed up employee time by 80%. 

UiPath has saved costs for our organization by 30%.

The cloud feature is valuable. Automation Hub and AI fabric are also good features.

UiPath Community is good. They answer all the queries.

Their support should be improved. 

Any unnecessary features should be removed. Only the relevant features should be there. There are so many unnecessary features that are not used by the organization. They are offering too many things such as process mining, task mining, communication mining, intelligent documentation, etc. It should be a specialized solution. It should not do everything in this world because the value comes down.

I have been using UiPath for six years.

It is stable. I would rate it an eight out of ten for stability.

It is scalable. I would rate it an eight out of ten for scalability. 

It is being used at multiple locations.

Their support is very poor. It is not timely. They sometimes take a lot of time to find resolution.

We do not use UiPath Academy. UiPath Academy courses are good, but nobody on the team is doing the courses through UiPath Academy.

Neutral

I have also worked with Automation Anywhere and Blue Prism. All these tools are good. IQ Bot from Automation Anywhere is very good. It has better features than UiPath, but UiPath is marketed well.

I was involved in its deployment. It is a straightforward process. It took us three months.

It does require maintenance. We have five people for deployment and maintenance.

We have consultants.

We have seen an ROI. It took us five years to see an ROI.

UiPath is expensive.

It is a great tool, and I can help people to implement it.

I would rate UiPath an eight out of ten.

We are using UiPath to automate many processes. In my first job, I worked on billing and ticketing. We were automating the process for ticketing and billing for audit. The robot was responsible for auditing the process of an application. It was responsible for calculating the difference between the amount deposited by the visitors and the amount calculated and predicted by the application. It would then decide if it was the correct currency or not.

Currently, I am working on many applications, but the classic ones are where we are reading data from Excel or databases and then clarifying the data or closing some billings. I am also working on the process of taking some reservations on some sites.

I also sometimes use it to automate something on my personal laptop.

UiPath enables us to implement end-to-end automation. It is not only about developing robots or putting the code. You must also monitor and implement the whole solution. It is not just a robot.

UiPath provides more flexibility because you can use other languages such as C#. This opportunity is not there with Power Automate or Blue Prism because you are working with graphical tools. For me, it was an opportunity to learn C# and how to code.

UiPath provides the opportunity to work with the conceptual aspects. There are flow charts to help you design the workflow.

UiPath has helped to automate many manual processes. We can see the difference with automation.

UiPath reduces human error. It is one of the main benefits. UiPath also optimizes the time. It is helpful. For one of the processes, the time taken was reduced from seven minutes to one minute.

UiPath saves human resources. For example, we had a process that was done by four to five people, and we automated that process. The robot could do one day's work in 10 to 15 minutes. We have automated almost 15 processes so far, so there have been a lot of savings on human resources. These resources can now be utilized for other tasks. The manual and repetitive tasks were annoying for them, and now, they can work on other things that are more interesting and require human decisions, not just copying and pasting.

It is the most suitable tool for big beginners in RPA. It is simple to manipulate. I found it comfortable because it has ML, AI, and OCR. It is great.

It is easy for me to build automation using UiPath. I would rate it an eight out of ten in terms of ease of use. It is easy, and I enjoy making robots. It is not just for the sake of working. I enjoy it when I finish making a robot. I feel I did something.

I did not work much on it, but I like the OCR part. I found OCR interesting because we can work with unstructured data from a paper or handwritten text. It is something new for automation.

The Community edition and UiPath Academy are two powerful features of UiPath. The Community edition of UiPath gives hands-on experience. People who want to learn about UiPath can download it for free and use it. It is a solution for everyone. Anyone can use it to learn about UiPath and practice it.

It should have better integration with Microsoft applications such as Excel, SharePoint, Outlook, etc. Power Automate is better for communicating with Microsoft Office applications. With UiPath, we have some difficulty communicating with the Microsoft Office applications. This is the only weakness that I have come across.

I have been working with UiPath for about two years. I also worked with it during my internship.

It is stable. I would rate it a seven out of ten in terms of stability. 

For scalability, I would rate it an eight out of ten because it gives you methods to be scalable. You can scale many processes.

I have not interacted with their support, but the UiPath Community is there. It is a very big community now. When we have some questions or want some clarification, we can find resources on their site or in their community. When I started working with it initially, it was not easy to find solutions related to UiPath. Compared to Automation Anywhere, it was a bit harder to find solutions.

I have also used UiPath Academy for certifications. It helps to learn from scratch. UiPath Academy makes it easy to learn for someone who has not worked with UiPath. There are different levels. You can find your level and begin from there.

We have our private setup. We have our own Orchestrator. We have a platform that communicates with the Orchestrator. We put the robots on Orchestrator and we monitor them using Orchestrator and some VMs. 

The deployment complexity depends on each project. Some projects are easy. You just need to put the robots. In terms of maintenance, robots do require maintenance. You need to monitor them to ensure that they are meeting the business requirements. If the code is good, one person can maintain the robots.

We are working in a team, and we have our own resources. We have experienced team members who know how to do the deployment.

We have teams working in multiple locations such as Tunisia, Morocco, Romania, and France.

There is a significant ROI with process automation.

It is reasonable considering the benefits of automating the processes.

I would recommend starting with some simple or classic processes, such as reading data from an Excel sheet and a database. You will find it easy. My advice is to not start with something difficult.

I would rate UiPath an eight out of ten.

We are using UiPath for some automations. One of the roles that I have handled over the last two years was related to customer service. In customer service, you tend to have a lot of inquiries and redundant work that can be done through RPA automation. We managed to use it to reduce a lot of recurring tasks. Our experience is very nice when using automation to reduce the workload.

There are a lot of cases related to user inquiries or figuring out how to do things, as well as some tasks related to setting passwords, creating shared folders, and creating virtual machines. These types of workflows are tasks that require only line manager approval, and things can be done without daily human intervention. We have managed to automate staff onboarding and related tasks. 

I have recently changed to a governance role. I am now the governance director at the company. A part of my governance role is taking care of internal and CSR committees. We are considering using automation for good causes.

We are now both a customer and a partner of UiPath. We are using UiPath as a partner because we are selling it to customers and we are also using it internally for the benefit of our employees.

UiPath has helped us a lot to reduce unnecessary load on the agents. In customer service, you tend to do a lot of repetitive tasks. After some time, the employee or agent ends up not being happy because they have been doing the same thing every day. When you take away such reoccurring and redundant tasks, you keep the employee or the agent free to do what matters more. It increases customer satisfaction and employee satisfaction. 

UiPath frees up employee's time for things that matter and need to be done by a human. It has saved 30% to 40% of the time of the customer service staff. We can easily automate tasks that our agent is conducting. The benefits are seen more outside working hours when you have fewer people working.

UiPath helps us be more efficient by freeing staff from doing unnecessary tasks. There is better load balancing and utilization of the agent's or employee's time, so there is going to be more productivity.

UiPath helps speed up digital transformation. Bots can do multiple tasks at the same time. Humans need more interactions for every task.

UiPath helps reduce human error. Bots are more precise than humans. A bot gives the output based on the instructions without making mistakes.

As the head of the division, I do not use UiPath myself. However, I am the decision-maker, so I review the features. The combination of both full-attended and half-attended automation, where you can automate tasks and still interact when required, is very useful. 

It provides efficiency by freeing staff from unnecessary tasks, resulting in a balanced workload and more productive use of an employee's time. The tool has a noticeable ROI, and the investment is worth every penny as it reduces tedious tasks and improves scalability.

It is very easy to use. During the COVID lockdown, my son who was 11 at the time attended a UiPath and Automation Anywhere training with me. He has already automated his school tasks requiring saving data and uploading some documents to the portal. If a kid can do this, it shows how easy it is.

UiPath is an RPA solution, but I have never explored the AI part of it. I am unsure if it has an AI element or not. Merging RPA with AI and ChatGPT would be beneficial. Adding more AI could help in small tasks that require intelligence or machine learning, leading to the next stage of automation.

We have been using UiPath for about five to six months.

It is stable. I would rate it an eight out of ten for stability.

It is very scalable. I would rate it a nine out of ten for scalability.

It is being used at multiple locations by many customers.

I do not have experience dealing with customer service, but the feedback from my team was positive. My personal experience is limited, but I never had any complaints from my team.

I had a chance to explore the UiPath Community in 2021. The interaction was positive at that time. After that, I have not had the need to use the community. I also used UiPath Academy at that time for a short course. I am an engineer, but I have been in management roles for a long time. I found the learning material to be tough at the time, but it was not a big course. It was a public course. Their big courses would be of better quality.

Neutral

It provides an ROI. We managed to get a return on investment differently with it. It is costly, but when we consider how much time we have saved and how happy our employees are after removing a lot of annoying tasks or non-intelligent tasks, the investment is worth every penny.

Using such tools also gives scalability when the demand is high. You can hire more resources, but it is a costly process. You do not have the budget to keep adding more employees. With automation, you tend to distribute tasks to the same robot. A robot does not require time to eat or rest. It also does not fall sick or ill. It drives productivity differently. It is more efficient. In the end, it is cost-effective.

Especially when it comes to customer service, there is less load on humans. A bot can be there 24/7.

It has saved about 20% to 30% of costs.

We evaluated Automation Anywhere, ServiceNow, and others. Our evaluation process took us a while because there are a lot of automation applications. The top ones definitely include Automation Anywhere. We did a lot of evaluation to see which one quantifies or fits all our purposes and needs.

My recommendation is to focus on optimization before automation. Decide what to automate and then proceed. Sometimes automation can create more issues. Ensure that the process is clear and structured. It works very well for repetitive processes or tasks done in large volumes.

In terms of maintenance, we are teaching the bot to normalize. If the UI interface changes, we need to redo the bot, but that does not happen often. The bot can learn a little bit, and the changes are not much. The maintenance is minimal.

I would rate UiPath an eight out of ten.

I have several use cases but primarily I use UiPath to input transaction data to the websites.

UiPath has helped us improve operational efficiency by automating tasks previously performed by humans. This frees up employees to focus on more meaningful and strategic work. In one project, we achieved 100 percent automation, while another reached approximately 70 percent.

Building automation using UiPath is easy even for inexperienced users.

We use UiPath to automate production processes in the healthcare industry.

To automate end-to-end processes, we employed multiple UiPath bots, as a single bot couldn't handle the entire process due to the disparate nature of the systems involved. These bots consisted of a web automation bot, a secure automation bot, and an existing legacy automation bot, which served as the backbone of the automation.

The UiPath User Community is accessible through the UiPath developer portal. It's a valuable resource full of information, where we can learn about the impact of new releases from other users and experts.

In the time I have been using Uipath, I have noticed that the text recognition tools have improved making it the best in the market.

UiPath has been beneficial in helping to minimize our on-premise footprint by automating 100 percent of some tasks.

As developers my team and I use the Developer Academy courses from UiPath to get certified. We also use the courses to help train new users which is helpful.

I am happy with the AI functionality. It has helped reduce the development time for us.

The AI functionality has helped us to automate more processes overall.

UiPath helps speed up our digital transformation and reduce the cost. Our digital transformation using UiPath did not require complex upgrades or application support.

UiPath reduces human error by 80 percent, enabling faster transaction rates compared to manual processing.

UiPath is the most user-friendly automation tool in the RPA category.

Storing data partially using internal data tables for internal calculations, without relying on a full database, is most beneficial for our workflows.

Computational text recognition has room for improvement as it is not 100 percent accurate.

I have been using UiPath for around two years.

I would rate the stability of UiPath ten out of ten.

I would rate the scalability of UiPath ten out of ten.

The technical support is good.

Positive

I previously used Blue Prism but found UiPath to be the most user-friendly.

The deployment was straightforward and took two hours to complete using four people.

UiPath is expensive which is why we need to have bots that run 24/7 to maximize the work and justify the cost.

I would rate UiPath nine out of ten.

We have UiPath deployed in one location.

Maintenance is only required when changes are made to the website.

I recommend UiPath to others.

I developed several use cases using UiPath. One involved website scraping, where I extracted data like temperature, humidity, and pressure for various cities from a specific website and displayed it in an Excel sheet. This was a small project, but my main focus was a prototype for a client: digital marketing automation. Using UiPath, I created an automation to automatically post articles on different social media platforms.

UiPath has certainly improved our operational efficiency. My prototype adheres to its principles.  UiPath has a sheer number of functionalities and features in UiPath. While these are beneficial, considering operational efficiency, UiPath excels thanks to its modularity. It's comprised of distinct components like Orchestrate, robots, and studios. This breakdown allows each component to function independently, increasing work flexibility and ease of use.

I would rate the ease of building automation using UiPath an eight out of ten with ten being the easiest.

I would rate the UiPath User Community ten out of ten. It is the best community I have used.

I'm taking advantage of the UiPath Academy courses and find them helpful.

UiPath helps to speed up our digital transformation and reduce costs.

Automation through UiPath helps reduce 80 to 90 percent of human errors.

The UiPath User Community is the best feature. We can find a solution to all of our issues there.

UiPath's interface element identification is arguably more reliable than Automation Anywhere's. This is because it utilizes an element descriptor method, which essentially locates "anchors" within the target element, not just relying on its absolute position. In simpler terms, it seeks a stable reference point within the element itself, even if its overall position on the screen shifts. As a result, changes to the website's UI are less likely to break our automation, as the code doesn't depend solely on the element's position. Additionally, UiPath offers a wider range of app integrations and features compared to Automation Anywhere or Blue Prism, making it more versatile for different automation needs.

Logging is also valuable. We can see any system, business, or technical errors.

One area that could be improved is how we access the UiPath Academy courses. While it's fantastic that each course provides an assignment, it would be more convenient if we could view the solutions directly within the platform rather than downloading them each time and opening them in our individual UiPath Studio applications. Ideally, there would be an interface integrated into the course platform itself where we could access and review the solutions directly within the browser. This would save time and streamline the learning process.

In Automation Anywhere, each line of code is displayed in a list view, offering clearer visibility. In contrast, UiPath condenses everything into a boxed view or flowchart, which can become cumbersome when dealing with numerous intricate conditions. Pinpointing specific segments for modification within such a condensed format proves challenging. Therefore, UiPath's UI design could benefit from an overhaul to enhance clarity and ease of navigation, especially for managing complex workflows.

I have been using UiPath for one year.

I rate the stability of UiPath an eight out of ten.

I rate the scalability of UiPath a nine out of ten.

I find Automation Anywhere to be more user-friendly for newcomers.

While I have more experience with Automation Anywhere, and it's where I've worked more extensively, UiPath is currently the market leader in the field. This prompts me to explore what's behind its success and delve deeper into learning UiPath. There must be compelling reasons why it holds the top position.

UiPath is more expensive than Automation Anywhere.

I would rate UiPath nine out of ten.

I recommend UiPath as the leading RPA technology, considering the current market trends.

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

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

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

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

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

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

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

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

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

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

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

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

I've used the solution for three years. 

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

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

I'm unsure if the solution scales well. 

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

Neutral

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

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

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

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

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

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

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

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

We're an end-user of UiPath. 

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

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

I would rate the solution nine out of ten.