UiPath Reviews

I piloted the introduction of UiPath to my team with two projects. The first, domain monitoring, automated our ten-plus Pega applications' quarterly security and health checks. We designed an architecture that could be mapped across all domains, streamlining the process to run weekly instead of quarterly. This provided timely reports on application health via Webex. The second project was a more straightforward test suite automation for another UI-based application. These two successful pilot projects showcased the capabilities of UiPath, with the domain monitoring still in use today.

Building automation with UiPath is straightforward, but it's essential to be familiar with the target application and have a basic understanding of coding and if-else statements. This knowledge will help troubleshoot any unexpected errors. Overall, I'd rate the ease of building automation with UiPath an eight out of ten.

While working on the projects, we used two versions of UiPath: the enterprise and cloud versions. The orchestrator that comes with the enterprise version is different from the cloud version. The cloud version had better end-to-end automation, and the ease of use and accessibility were superior to those of the enterprise orchestrator, which is the on-premise version of UiPath. Although the enterprise version lacks a few features, the cloud version provides a complete solution.

I was impressed by UiPath's user community. We used an open-source library that someone else had built and generously shared with the UiPath community. It ideally suited our needs. The user community is also very responsive, and we readily receive answers to our questions.

We didn't see immediate benefits from UiPath because it was a new tool I was piloting. We had to prove to upper management that it saved significant time, and we eventually eliminated manual testing. It took until the project's end to demonstrate this, as management focuses on results, not processes. However, other teams adopted UiPath after completion, so benefits appeared after two or three months. It took time to get people on board, but they eventually embraced the idea.

UiPath has significantly improved our efficiency by automating domain and application monitoring, saving valuable time and working hours. These tasks were previously quite intensive and repetitive, demanding considerable focus and effort from our employees. With UiPath handling these processes, we've freed up our workforce to take on more engaging and strategic responsibilities.

My favorite aspect of UiPath is its user-friendly interface, as it's a no-code, low-code platform that eliminates the need for extensive coding. Its drag-and-drop functionality, coupled with UiPath's comprehensive library suite, simplifies automation tasks. For instance, the Microsoft Outlook and SharePoint libraries allow seamless integration with those platforms, streamlining processes like connecting to SharePoint in Microsoft 365. In essence, the combination of UiPath's robust infrastructure and versatile tools significantly enhances its usability and effectiveness.

I found the UiPath Academy courses to be a bit rigid in their curriculum. It was more beneficial for me to learn from the forums and YouTube videos. Their courses were tailored to particular roles, with a course on UiPath in data science being heavily focused on Excel. While it was a well-structured course, it didn't align with my job's limited use of Excel. Overall, their courses are well-built, but I found YouTube a more suitable learning platform for my needs.

UiPath Studio provides comprehensive tools and libraries for building automation, but it lacks a built-in feature to generate consolidated reports after automation runs, detailing successes, failures, and operational features. This absence of detailed logging information makes it difficult to troubleshoot issues and identify whether the problem lies within the application or the automation itself. While UiPath's orchestrator website provides some information, it's insufficient for demonstrating automation runs and accomplished features to stakeholders. Although a future release may address this, the lack of robust reporting capabilities remains a significant area for improvement. Additionally, UiPath's diverse suite of licenses can confuse end-users, making it challenging to determine the most suitable option. While the company has improved features, the increased number of licenses creates a knowledge gap between what's available and user understanding. Clearer explanations of each license would simplify decision-making for potential users and streamline adoption.

I have been using UiPath for one year.

Once we have the licensed version of UiPath, we don't anticipate issues with caching. We were using the 2021 Studio version because it was stable. Although the UiPath team suggested upgrading, I'm not certain about the reasons. I can't comment on the latest models, but the 2021 version was reliable.

The scalability of UiPath depends on the number of licenses. To deploy our automation, we need to utilize robots responsible for executing the automation we've built in a user-less environment. Scalability is directly proportional to the number of robots we have, which is, in turn, determined by the number of licenses. Therefore, more licenses translate to greater scalability.

The initial onboarding of UiPath was straightforward, but the only challenge we encountered was connecting UiPath Studio to the Orchestrator. UiPath Studio is where automations are built, while the Orchestrator is where they are deployed and run. This required some back-and-forth with the product team and my technical lead. However, this issue only arises during the initial setup. Once someone familiar with the process sets it up, it becomes easier. There were some challenges connecting and deploying the first automation, specifically between the Orchestrator and Studio.

Three people were involved in the deployment: my technical lead, who liaised with the product team to discuss progress and challenges; myself, responsible for building and deploying the automation; and one of my junior colleagues, who assisted me. In short, we had a three-person team.

We used UiPath and built and deployed that project, which ran successfully for approximately two quarters while I was away. However, the cost and licensing associated with UiPath became an issue. The license we were using offered excellent features specific to our needs, but it didn't provide much beyond that. It didn't make sense to continue spending much money on UiPath, even though it saved us time and money. The savings were essentially being reinvested back into purchasing the UiPath license. While UiPath licenses offer valuable features, they are expensive. For our single-use case, investing that much wasn't justifiable. We switched to Selenium, an open-source automation tool. Although it took additional time to deploy the same solution with Selenium, and it might not be a 100 percent match in functionality, it allowed us to save on costs.

The cost of UiPath is justified for organizations with many use cases but not for one or two use cases.

I give UiPath a seven out of ten.

The advice I'd like to give new UiPath users is to first understand their specific use case for UiPath. I've noticed some teams try to adopt UiPath by first figuring out a solution and then trying to retrofit it to their existing problems. Instead, I suggest thoroughly understanding the problem before creating a solution. Many teams see others using UiPath and assume it's a cool new tool they can simply apply to their existing issues. This approach rarely leads to optimal results. You might be able to build a solution, but it won't be the most efficient. For first-time users, I recommend understanding your problem, then exploring UiPath's capabilities to determine the best solution. There are plenty of resources available, like forums and YouTube, to help with the building process. Remember, understand the problem first, then build the solution.

There are multiple use cases. We have use cases for the ticketing system for assigning the ticket, resolving or maybe closing the ticket, and opening a new ticket. We also have a business use case related to insurance. I worked for an insurance client, and by using automation, we could create a policy that is used for testing purposes. If they had a new enhancement or an issue, they wanted to test whether it was working properly or not. They provided us with some raw data, and we tested that.

UiPath enables us to implement end-to-end automation. It is very important for us.

We use the AI functionality in our automation program. It helps us with decision-making. The AI functionality has enabled us to automate more processes overall.

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

UiPath definitely minimizes the operational expenses. By automating the static tasks that people are doing on a daily basis, there is a reduction.

UiPath reduces human errors. With static tasks, such as data entry, there are more chances of human error. With robots, there is less chance for error.

UiPath frees up employee time for other tasks. By automating static processes, we can save time and utilize it for other tasks.

UiPath definitely saves costs, but we cannot fully replace humans with robots. A human is required in certain cases. We can reduce at least 70% of manual tasks and for maybe 20% to 30% of tasks, we need human intervention.

The IDP feature is most valuable in UiPath because there are a lot of invoices and bills in every company. If they want to extract from a scanned document, it is very useful.

UiPath is very easy. We can build very complex processes within a few days.

UiPath has a very good community. If I am facing some issues, it is very easy to get the help of the community. They provide a solution very fast if I post an issue there.

UiPath Academy is good for learning purposes and certifications. They have beginner courses and advanced courses. By using them, it is easy to implement UiPath in a real-life project or process.

When it comes to decision-making, the robot will work based on what we feed it. It will not take any decision at runtime the way a human can. If they can put more intelligence in the robot for decision-making, it will definitely be beneficial for us. For example, if something is not working and it can dynamically decide at runtime what would be the next step, it will be beneficial.

Additional features such as chatbots and AI should be included in the UiPath itself. UI development is another thing. It could be improved for web development and app development.

I have more than six years of experience with UiPath. I have also worked with Automation Anywhere for a year, but I am more familiar with UiPath.

It is scalable. They have ML and also Python. They are adding a few more features.

We have around 1,000 people using UiPath. We have different groups in our company. We have separate teams. There are multiple different tools. UiPath is in one vertical. Automation Anywhere is in a separate vertical. 

Most of the time, if we raise a ticket, they help us to resolve the issue. I would rate their support a seven out of ten. The response time is as per the issue. Sometimes, it is very fast, and at other times, I have to wait for a day or two to get help from UiPath, so I have had both good and bad experiences with their support.

Neutral

I have worked with Automation Anywhere. I have also done scripting, but I had to write a lot of code to automate, whereas, with UiPath, it is simple. It is drag and drop.

It is deployed on-premises. There was no issue at all in deploying it.

For the deployment of bots, we have different VM servers. They are unattended ones. The deployment of bots is a very simple task. 

I can do the deployment myself. It is not a big task.

It saves six to seven hours for one person in a day. It saves the cost of one FTE, which is very high in US dollars. It is more than the cost of a robot. There are definitely savings. If the utilization is more, the savings would be more.

When I started with UiPath, there was a desktop model, and we did not have to purchase Orchestrator. Now, there is a bundle or package of Orchestrator with attended or unattended robots, so the cost is a little bit on the higher end. They are selling the Orchestrator model or the admin model. If someone wants to purchase the standalone or desktop model, they cannot do that, so the cost is on the higher side, but if we purchase more licenses, it gets reduced. If we purchase fewer licenses, it will be high.

If you have good use cases, I would advise using UiPath. Compared to other tools, UiPath is very easy to learn. A trial version of UiPath is easily available, whereas the trial version of Automation Anywhere and Blue Prism is not easily available. Automation Anywhere provides a trial version nowadays, but previously, it was very difficult to train people on that. That is the reason UiPath is the market leader at this time.

I would rate UiPath an eight out of ten.

We are a partner of UiPath and a system integrator for our clients.

For most clients, we tend to begin by focusing on areas with the highest potential for automation. This typically includes finance, procurement, or HR functions, with the first two being the most common choices. These areas are chosen because their processes are generally stable and repetitive, making them ideal starting points for RPA implementation.

However, our experience doesn't end with just one client. We've had numerous engagements, including with large, multi-company groups. Once one division like the "glass division" successfully implemented RPA, it often sparked interest in other divisions like the pharmaceutical division. Demonstrating a solid proof of concept makes it easier to scale the technology to diverse use cases across the organization.

Ultimately, overcoming the initial hesitation and showcasing the tool's benefits is crucial. Once the value becomes apparent, a shift often occurs, transitioning from a client-driven demand to a proactive push from various departments eager to eliminate tedious manual tasks.

While we haven't encountered any major technical roadblocks, understanding the potential for automation has been the primary challenge for users. Initially, we also faced some learning curve hurdles during the first few projects. However, as our internal expertise matured, approximately 80 to 90 percent of use cases have been implemented smoothly with minimal or no support from UiPath. It's clear that effectively identifying tasks suitable for automation versus those requiring human intervention has been the key hurdle. From a purely technical standpoint, the capabilities have been readily achievable.

While UiPath facilitates end-to-end automation, its feasibility heavily relies on the specific use case and associated tuning costs. The decision to automate isn't solely driven by cost reduction, but also by the number of tedious tasks it can alleviate for employees. Clients are often eager to free their workforce from such repetitive drudgery, especially if the task is long-standing and well-defined. In these scenarios, full automation often presents a compelling value proposition.

The UiPath user community exists on two levels. First, there's the general UiPath user community, managed by UiPath itself. This broader community offers a valuable resource for learning, sharing experiences, and finding solutions. Second, once a UiPath instance is set up within a specific client's environment, a smaller user community emerges within that client's organization. While this internal community may seem less significant, its role in supporting individual users in tackling automation challenges is crucial. By sharing their experiences and overcoming difficulties, these internal user communities can act as "roll cages" for individual functions, providing guidance and support regardless of the specific challenges encountered.

Initially, our focus was solely on on-premise solutions. In fact, up until last year, I hadn't encountered a single client who had implemented their RPA solution on the cloud. This was primarily because we catered to a mainly small business clientele. However, the landscape has shifted significantly, with more and more cloud-native solutions emerging. This shift has been driven, in part, by the cost-effectiveness of cloud-based options. One of the major roadblocks to cloud adoption in the past was the pricing of the orchestrator. While it might be suitable for supporting large client bases with thousands of users, it wasn't cost-effective for smaller businesses with only 100-200 users. Fortunately, UiPath has introduced a new approach, allowing us to purchase orchestrator instances tailored to specific user base needs. This, combined with the inherent benefits of a cloud-based platform, has made the cloud a much more attractive option compared to 2019. In conclusion, cloud computing is now a critical factor in the RPA landscape, and the adoption of cloud-based solutions has become significantly easier. This shift has opened up new opportunities for businesses of all sizes to leverage the benefits of RPA technology.

We started with five or six people trained online by UiPath and the different certification programs available in the UiPath Academy courses were helpful.

UiPath has helped to drastically reduce human error to almost zero by automating all the structured data that used to be done manually by people. This has improved the quality of work for our clients.

UiPath has helped free up employee time. Previously, we analyzed each potential use case to determine its priority. Before committing to a specific case, we built a business case to assess its potential benefits. This involved analyzing how much time automation could save, the associated cost savings, and the number of transactions it could automate. We performed this analysis during the design and assessment phases of our workflow. Following this process, we would gather the data and present it to management for approval before moving forward with automation. The amount of time saved depends on the individual use cases but they are significant. What used to take hours now takes seconds.

UiPath has delivered cost savings for our clients' organizations, not through mere implementation, but through thorough assessment. We start by demonstrating the technology's value through small-scale projects, then scale up. At this point, we gather a list of potential use cases, identify the number of users who could benefit, and pinpoint the manual tasks ripe for automation. Only then, with a business case in hand, do we proceed with full implementation. This careful approach ensures that when use cases are deployed, they translate into meaningful time savings and reduced manual workload. As a result, our clients typically see cost savings in staff reductions of at least 30 percent.

UiPath is an efficient and user-friendly tool. It allows us to record and capture actions, which it then translates into underlying code. This makes development incredibly fast. The centralized orchestration feature is also a major advantage.

Clients are often convinced by its features and marketing. In some cases, when competing with Blue Prism and Automation Anywhere, UiPath has won out due to its faster time to market. This was especially true during the early days of RPA when clients were still experimenting and wanted to try multiple vendors. UiPath's flexibility and strong support, both during evaluation and implementation, were also key factors in its success.

We sometimes use the AI functionality mainly for document scanning but at the time it was poor and had room for improvement.

The operation costs have room for improvement. 

I have been using UiPath for over four years.

UiPath is a stable solution.

We haven't encountered any scaling issues, and UiPath is theoretically scalable for up to 10,000 bots. We've successfully implemented over 100 use cases for a large client with multiple subsidiaries, receiving no complaints.

The technical support is good.

Positive

The initial setup is straightforward and UiPath worked with us for every deployment.

We implemented UiPath for our clients in-house.

We evaluated Blue Prism and Automation Anywhere. Blue Prism and Automation Anywhere are not as user-friendly as UiPath and they don't have the same user community.

I would rate UiPath a nine out of ten.

Previously, we distinguished between Automation Anywhere and UiPath based on their bundled offerings. Automation Anywhere included category two AI capabilities with their RPA solution, while UiPath focused solely on RPA and didn't have much presence in the AI space at the time. Although UiPath could integrate with other AI vendors, this wasn't a significant interest for our clients.

Most deployments we completed for our clients were central.

I automated the use cases related to medical processes such as posting the payments, downloading the files from the portal, and claiming medicals.

It is easy to create automation, and it is also easy to test for your test case. If you want to go live with a process, that is easy. You can publish the package from UiPath Studio, and in Orchestrator, you can see if the bot is working fine or not in the unattended mode. If the bot is not working fine and continuously throwing an error, you can stop it from your side. You do not have to log in and stop the bot manually.

One of the projects where UiPath has been beneficial is related to payment posting. It is a weekly process that we run on Friday or Saturday. There are about 1,500 records. Before automating it, we could handle 150 to 200 records per day. It took about 20 days to develop the bot, and the testing took two to three hours. After ensuring everything is fine and publishing it, in 10 hours, we are able to post all the records we have. It takes 15 seconds to post one record. We have developed this automation for one client who has multiple clients. We created a master config for that and changed the credentials and the input file. This way the bot processes one client and posts everything, and then the second client and posts everything. It will continuously run every day.

We also used Computer Vision automation for one of the projects, and we also have automation that gets triggered based on a real-time event. For example, on receiving a client email, the bot runs and does the required task.

As compared to other tools, UiPath is more specific. If you need to develop something specific and publish it, UiPath is very helpful for that.

Another valuable feature of UiPath is the training. Those who do not have a programming background and want to understand how UiPath works can go to the UiPath portal to get free training. They can train themselves as a business analyst, a developer, or an automation developer. The training system is good.

The development and practical aspects are also good. When you get a project and you start working with UiPath, you need to buy all the licenses, but you can also develop some processes without buying a license for demo or testing purposes. You can show it to your manager without buying the license.

In advanced features, there is a feature called Document Understanding, which is helpful for scraping the required data from a PDF.

UiPath Academy is very simple. You do not need any guidance on how to use it. After you log in, you get training based on your role, such as whether you are a developer, solution architect, analyst, or delivery manager. You go to the training section accordingly, which not only has text or PDF but also some videos and practical scenarios. They provide some dummy files as well that you can implement in your system. You can use them to see if it is working or not.

The UiPath forum or community is also there. If you have some questions, people will help you with that. Someone will definitely reply to you, and you will get a solution.

Some kind of code repository would be good. Other than that, everything is fine in UiPath. They improve it every quarter and bring something new.

I have been using this solution for three years.

It is a stable product. In the last year, I have not found any kind of issue or server error. I did not have any issues where the server was down, so you can rely on UiPath.

It is scalable. UiPath provides all kinds of solutions. Based on that, you need to build your project and diagram. You can then start the job immediately.

We are in the healthcare business. My client has about 5,000 members, but over the past year, we have deployed about 25 processes along with 30 payment posting processes. We have five developers.

You can buy licenses depending on the number of bots that you have. If you have 10 bots, you do not have to buy 10 licenses. You can buy one license and insert that one license to run the bots one by one. You can buy as many licenses based on your convenience.

When you have a licensed version, you can raise a ticket in case you have any issues. They usually respond within 24 hours, but they can also take two to three days.

We were facing an issue with the Computer Vision process for 20 days, and we were not able to find a solution. We raised a ticket with UiPath. They connected with me in two or three days. They monitored all the things and recommended the changes. After making the changes, everything worked fine.

I would rate them an eight out of ten because they should give an immediate resolution for any production-related issues. They should have connected immediately after we created the ticket, but they connected after two to three days, so we lost the money for two to three days.

Positive

I have only used two or three RPA tools. As compared to Power Automate and Blue Prism, UiPath is the best. The cost of Power Automate is a little bit low in comparison to UiPath, but Power Automate does not have flexibility. If you have a large project, go with your UiPath, and if you have a small project, you can go with Power Automate.

UiPath is also good when you have use cases where you need to save your portal credentials or FTP credentials. You can easily use the features of UiPath Orchestrator for that, whereas, with Power Automate, there is no way to save your credentials. You need to save them somewhere else, such as in a text file or an Excel file, which is not secure because if someone opens the file, they can see the credentials. In the case of UiPath, they can see only the username, not the password. This kind of protection is there.

UiPath provides two options: One is a cloud-based Orchestrator and the other one is an on-premises Orchestrator. For safety purposes, most of the companies are not using the cloud-based Orchestrator. They are using the on-premises Orchestrator, but you need to set up your database and connect it with Orchestrator. This way, all the things that you have done at the project level are stored in your database. UiPath does not take any responsibility for that. If you do not have a database and you want to run a process smoothly, you can go for the cloud one.

My current project is on the cloud because they did not want to install their own database and set up all the things. It was better to use the cloud option because they did not need to install anything on the system.

The deployment probably takes one to three days. When you buy your license and connect with them, they will guide you on how to set up things. It is easy for me because I have been using it for the last three years.

We calculate ROI every month end to see how much we have saved. For example, if we have a bot for downloading four files, we do not need to redevelop it for another client. With a few modifications, we can use the same bot, which saves money.

In comparison to Power Automate, UiPath's price is a little bit high. 

The Community edition of UiPath Studio is free. If you want to learn something or develop a process, you can install the Community edition of UiPath Studio. If you buy a license for UiPath Studio, the updates do not happen automatically, whereas, in the Community edition of UiPath, all the things are updated automatically. Once you log in yourself, after every four months or five months, when there is an update, it will automatically update itself, but if you buy the licensed version, it will not update immediately. It will not impact your project.

It is better to use automation. Nowadays, every company is adopting automation. I would recommend choosing an RPA tool based on your requirements. I have not used Blue Prism or Automation Anywhere much, so I cannot compare it with them. However, UiPath is better than Power Automate. Based on my discussions with other people who use other RPA solutions, it seems UiPath is the best. With separate components such as UiPath Studio and UiPath Orchestrator, you do not mix up things, so you can clearly do your job.

I would rate UiPath a nine out of ten because I have not had any disappointment from using UiPath Studio and UiPath Orchestrator. None of the jobs that I have built so far have failed.

I have worked on use cases for three domains, which include the banking, health care, and insurance domains, and designed bots for automating processes.

UiPath enables us to implement end-to-end automation. In my three years of experience, I have developed bots for banking, insurance, and healthcare domains.

UiPath is very easy to use. We are able to automate manual processes with bots, so the work gets done in a very short time. Manual work that takes months can be done in two or three weeks.

UiPath helps to speed up digital transformation. It is easy to use. It completely removes human intervention. We can develop unattended bots. It brings efficiency and also helps in reducing human headcount. After UiPath was launched in our organization, there was a reduction of 800 employees.

UiPath Studio and Orchestrator have been useful in designing the bots. I know about Document Understanding, but I am not working on integration services such as app integration. For building automation, a lot of activities are there. There is load taxonomy or taxonomy creation. After that, there is digitization, classification, and extraction. The validation part is also there. These are the steps for designing a bot using Document Understanding.

I have used UiPath Academy courses. I have done two courses. I did the UiPath Associate certification in 2021, and UiPath Advanced RPA Developer v1.0 certification in January 2023. I am currently preparing for the advanced UiARD certification. Through the UiPath Academy courses, I have learned a lot of things about queues, Orchestrator, advanced methods, etc. It is very good for learners.

On my organization laptop, while doing database activities, such as database connect activity, UiPath Studio hangs. We click on the screen, but there is no response. The only option that works at that time is to open the task manager and forcefully stop the services of UiPath. UiPath gets closed, and we again have to run UiPath Studio. 

UiPath Studio is also slow during web scraping and screen scraping.

In terms of new features, UiPath already has many features, but its pricing can be better for small businesses.

I have been working with UiPath since December 2020. It has been three years since I have been working as an RPA developer.

We are an organization with about 1,300 employees, and we have 20 people working with UiPath.

I have not used their support. When I have a problem in developing a bot, we use the UiPath community, and they provide me with a solution for the same.

I have also used Blue Prism. UiPath is easy to understand. It is easier to develop and deploy bots in UiPath. In Blue Prism, there are some challenges related to how to create processes. In UiPath, there are many sections such as Control Panel, activity properties, or object repository. They provide a modern experience to the developers. It is better than Blue Prism.

To deploy three projects, I had to install UiPath on the client's machine, and it took only one and a half days. 

We have two or three people for the deployment of projects. We have one person to deploy the code on a client machine. We also have a solution architect and a support team. The deployment requires only two or three days.

Small businesses do not have the budget to purchase the UiPath license. They should provide a cheaper license option for small businesses.

It is a very good solution. There are various RPA solutions, but UiPath is currently the number one solution in India as well as outside of India.

I would rate UiPath a ten out of ten. I love this tool. It works very efficiently.

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. 

The way I'm using UiPath is to create workflows related to financial services. I work for a company called Cedar Financial here in Pakistan. The workflows are related to our data statements, clients' financial documents, and the like. It mostly involves Document Understanding and creating workflows to generate reports. My use cases are restricted to UiPath Studio, where I use the Activities to create workflows and automate some of my clients' work.

It's very cool to be able to create automations and reduce human effort. It really is a valuable and great tool to be working with. It has improved things immensely because our organization needs fewer human resources. In one department, 40 percent of the time has been freed up for other tasks. The work the bots do is more efficient and reliable. UiPath has reduced human error, which has had great effects: better results and better revenue. It has saved us about 40 percent of our costs.

Another important benefit is that UiPath enables you to implement end-to-end automation. Humans don't have to do repetitive, boring tasks.

The most valuable feature is its screen recording capability, where you tell it what the workflow should do, and it then automatically creates Activities for you.

It's easy to build automations with UiPath help. I have also been a Python developer, and there you need to do hard coding to create an automation. But when you're dealing with UiPath Studio, you have all the modules. You just need to know what to do and which Activities you can use. You get everything right, and the automation is ready for you. You don't need to do hard coding.

And UiPath's user community has been great for me. Every time I'm stuck somewhere, there's always a forum to ask questions and share my knowledge as well. There have been a few main developers, like Michael Jensen and a few others, whom I follow and really admire their work.

They need to keep fixing the bugs and improving the tool. For example, if an Excel file is running and I'm doing an automation on that Excel file, it doesn't complete. There are some bugs, and fixes and improvements are required.

The stability is good.

It's scalable.

Previously, I used Python and its multiple libraries and frameworks to do automation with Selenium and Beautiful Soup. We switched to UiPath because you don't need to do hard coding with it. You have more functionality. You just need to know what to do and keep on importing those activities. Create the workflow, and the automation is almost done.

UiPath is always a good investment.

I have tried Microsoft Power Automate, but UiPath has a lot of Activities and is easy to use.

The UiPath Academy is where everyone starts. I started there and took courses such as the RPA Developer Foundation course, and I still take courses from the Academy. It's very beneficial.

When you have RPA developers, they sometimes require IT support. The application team is also important in this.

The time it takes to implement a solution with UiPath depends on the problem and the workflow. Some might take 30 days, while others might take just one day. It does require some maintenance at times. There may be updates, or an error might appear. We have to provide support as well.

From a company point of view, it didn't take long to identify how beneficial UiPath could be. Every industry these days needs automation tools. If an employee generates the same report every single day, we can build a robot to do that.

It's a good and handy tool to use. Try it, and it will help you greatly boost your business. And your employees will be happy as well when their time is saved. Go for it.

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.