UiPath Platform Reviews

We use UiPath to automate daily repetitive tasks.

I would rate the ease of building automation with UiPath a nine out of ten. It saves us a lot of development time, and the drag-and-drop feature is very useful. The cloud version's orchestrator is also amazing, as it can host our robots.

UiPath enables us to implement end-to-end automation, which is one of the most crucial parts for our customers. Most of our users are not technically proficient and do not know how to deal with these things. They want the automation to be complete without any manual intervention.

The UiPath User Community is really helpful and has helped solve a lot of problems.

The biggest advantage of UiPath is that a lot of time is saved, which can be used for other projects.

UiPath Academy courses are helpful. They help us gain a deeper understanding of the product.

UiPath's AI helps us perform more complex processes in automation.

It has helped us speed up our digital transformation by removing a lot of manual work.

Speeding up the digital transformation process does not require any expensive upgrades or much IT support to keep UiPath up to date.

UiPath has helped to reduce human error. This indirectly allows our customers to focus their employees' time on more productive projects.

It has helped us save time.

UiPath helps reduce costs, especially for accounting companies. They are able to automate basic tasks reducing the number of people required for daily tasks and can also have those tasks running twenty-four hours a day seven days a week.

UiPath is a no-code automation tool that saves me a lot of time when developing workflows.

UiPath is very slow for scraping. If they could make it faster, that would be great. We are currently using custom robots to scrape data, which is faster.

The initial setup of UiPath can be complicated. It would be helpful to have an executable file to simplify the deployment.

Integrating UiPath can be a complex and error-prone process, especially when it comes to calculations. A helpful feature would be the ability to add simple workflows using executables, which would be especially beneficial for small projects.

UiPath needs to be more compatible with MacBooks.

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

The UiPath software is generally stable, but some of the packages within it can sometimes be unstable. For example, we have had to switch to older versions of some packages in order to get them to work properly.

I would give the scalability a rating of seven out of ten. As we scale, we involve more users and machines, which means ensuring compatibility.

To deploy, UiPath needs to be installed on the production machine and the extensions need to be ready. One person is enough for the deployment.

The initial setup of UiPath can be complex, as we sometimes need to explain to customers that it is not as simple as copying and pasting an executable file. UiPath requires some setup and configuration in order to work properly. 

I would rate UiPath an eight out of ten.

The decision of whether or not to use UiPath depends on the customer. If the customer is a Windows user, then UiPath is a good choice because there are many third-party packages available that make tasks easier. The orchestrator cloud functionality is also very helpful.

UiPath is easy to maintain because it integrates with other applications.

I recommend UiPath for Microsoft Windows users.

We use UiPath to automate the repetitive reporting tasks in our organization. I am currently using UiPath for five Oracle-based projects.

UiPath has increased our organization's productivity and efficiency and saved us money. 

There is a short learning curve. We can learn to use it in one month, compared to other RPA solutions that take three months.

Building automation using UiPath is simple.

UiPath enables us to implement end-to-end automation. First, I build the code based on the customer's requirements and run the code in UiPath. Then, I run the code using an orchestrator on our VM when it is put into production.

The UiPath Community is a great place to find information without having to contact the technical support team.

I am a big fan of the UiPath Academy courses. When I first started using UiPath, I took all of the courses, which helped me immensely. Whenever I need to learn a new UiPath task, I simply go to the Academy courses.

UiPath helps speed up digital transformation and reduce costs.

If we input data into UiPath correctly, it can help reduce human error by 95 percent.

UiPath has helped to free up 25 percent of our employees' time by automating recurring tasks, allowing them to focus on other tasks.

It has helped our organization save around 30 percent of our organizational costs.

UiPath is user-friendly. Compared to other RPA tools that require knowledge of a programming language, UiPath requires less coding.

Occasionally, we receive an error message stating that a UiPath element is invalid, even though it should be working. This is frustrating and needs to be addressed.

UiPath needs to improve the selector and offer better integration for Python.

I have been using UiPath for two years.

I would rate the stability a seven out of ten because we sometimes encounter errors.

I would rate the scalability an eight out of ten.

The technical support is good but I usually find my answers using the UiPath Community forum.

Neutral

The deployment is not complex compared to other RPAs that require knowledge of Python or Java.

Deployment time varies depending on the use case but averages two to three days.

One person can complete the deployment.

UiPath offers two versions of its solution: a free Community edition and a licensed Enterprise edition. The Enterprise edition includes all features and automatic updates, which are not available in the Community edition.

The cost for UiPath is affordable.

I would rate UiPath a nine out of ten.

Basic maintenance is required for UiPath.

We have UiPath deployed in four of our departments including sales, booking, comp, and operations. In my department, we have five UiPath licenses.

I've worked in two organizations where I have used UiPath. The first organization was in banking and we used UiPath to help automate banking and financial forms. The second organization, the one I am currently working for, is a technology company with several sub-companies that include banking/financial, the hotel sector, and some overseas organizations. In this organization, we automate tasks that are repetitive, as well as reconciliations.

The main advantage is that we've synchronized our process across 70 sub-branches covering the entire island of Sri Lanka. Previously, we had three or four employees manually inputting the user entries for the various branches. We eliminated those positions so that data entry is now done by robots and performed in the head office.

We have multiple robots directing all of the data to the robot platform in the head office. We saw value within six months. That's how long it took to eliminate the positions. We stopped recruiting people who had previously done that task. More tasks remain, but the main use case was realized within six months.

The APIs are helpful in our workflow. We have a separate application for the government sector, and the Sri Lankan government provides that API. It's a matter of due diligence because we get the customer information, like the national identity card number. We use the API to exchange that information.

We get quick information about existing loans, including how they perform and whether the borrower is paying on time. If they are red, it means that the payments aren't being made in that period of time. That is the kind of information that is exchanged with the API. We can process 20 or 30 users every minute through the API on average.

Previously, our staff onboarding involved a large number of hard-copy documents—around 50. We have automated what was a long manual process, using automation to go through the documents to create a customized onboarding process, one that includes the government regulatory platforms that we are required to use. We used to have to store those documents in an archive, taking up our storage capacity. With UiPath's OCR platform, we get the information we need to do the task. That has resulted in huge savings for the organization, including environmental savings in terms of trees used for paper. It has also saved a lot of the human effort involved in verifying data in those documents.

In our previous process, the documentation was written entirely by humans, including data entry. That data entry was a critical point but there was a lot of human error. That has been reduced by 85 to 90 percent. In my current organization, we have automated about 70 processes and the amount of employee time saved depends on the process. For example, one of our automated processes has saved eight hours for one FTE, while another has saved 10 FTEs two hours each.

And we have done an end-to-end automation for an insurance platform, for renewals. There is no human touch at all.

UiPath has also helped us to reduce our on-prem footprint, compared to our previous platform. In our previous model, we worried a lot about our data. But with UiPath in the cloud, could our entire database be somewhere else, meaning not in our custody? A few years back, UiPath introduced governance and audit platforms, and that's when we felt that it was okay and that we didn't need on-prem platforms anymore. It was okay, at that point, to go for a cloud platform. We are migrating our on-prem platform to the cloud now.

UiPath Orchestrator is incredibly useful. It's the main dashboard platform we use. Orchestrator provides a single platform where we can connect with legacy systems and manage all the bots. 

Orchestrator lets us see the entire process across various department units so that they can see the separate tenants and units. The application can multi-task to handle processes even when we have a long queue. If the queue is piling up, we can assign multiple robots to clear the queue quickly. We can find the ETA for the queues and everything inside Orchestrator.

The Studio and development boards are also helpful.

The UiPath community staff is the best I have ever seen. I have worked in several communities, not only in RPA platforms but for other tools, but the UiPath community is the best. I am an active member of the community. If someone has a question, we always look after it there and are very happy to help them.

The UiPath Academy is very useful as well. My colleagues and I are always going through the new features that are available for our automation and new developments. We always keep in touch with the Academy.

Previous Orchestrator versions were very user-friendly for the admins and the users, but the new Orchestrator is a bit advanced. If they could reduce its complexity, to something more like what it used to be like, it would be better.

Also, if they can improve the performance of robots, that would be good. 

I have been using UiPath for more than five years.

There are no issues with the stability.

It is scalable and very easy to scale but, again, that comes back to the pricing.

UiPath scales easily, but scaling for the cloud and on-premises versions is different. For the on-premises solution, we need to add new licenses to scale up. But it's easy in terms of scalability on our end.

Support can be divided into two tiers: enterprise users and community users. Enterprise users like us get high priority because we are dealing with live operations and customers. When we raise a ticket, we have options like critical and onsite support. They reply in one or two hours, or in less than 30 minutes if it's critical. Their technical support is very helpful and the ticketing platform is very good.

We also get a fast response for non-technical customer service issues.

I hope their support can be developed because when there is a difficult case, sometimes it seems that it's a new issue for them as well. I have experienced that. That should be improved a bit. Overall, support is very good, but there is room for a bit of improvement.

Positive

We didn't have an automation solution previously. As a developer, there are lots of costs in our country associated with switching to automation. There weren't other solutions that could integrate our entire operation like UiPath. I don't think it was possible to select another one.

As a user and an administrator, I can manage the entire server from the main controller. I know everything that UiPath is doing. I also can't think of another solution that has the same broad user community.

UiPath runs Orchestrator and the application in the cloud, but our robots work on-prem in our data center.

In my previous organization, I deployed UiPath, but when I got there I didn't even know what UiPath was. Fortunately, they have nice documentation on the UiPath website, step-by-step. I followed that and was able to deploy things. Since then, I have helped several organizations, via the UiPath community, to deploy Orchestrator within two or three hours. If they have completed the relevant prerequisites, it can be done in that amount of time for a standard installation.

We had a detailed plan in place that progressed in phases. In phase one, we eliminated the data entry function in the main office and the branches. In phase two we would optimize our existing processes. Once all the automation is finished in the head office, we optimize those head office processes.

We have seen significant cost savings throughout the company. Before we started to use UiPath in 2019, we had three or four people doing data entry in every branch. It has eliminated human data entry and also frees up our cashiers because the cashier cannot go anywhere when the queue is long.

We calculated what we have spent for our entire RPA platform and what our ROI is. Our calculations showed that after one and a half years, we had recouped our entire spend on the RPA platform. That included the entire robot cost, servers, the software license, et cetera. That means we had ROI after 18 months.

When it comes to unattended robots, the cost for us in Sri Lanka is huge. It's tricky for us to convince management when they think about the price. We have to prove the value with evidence. We explain that we will save this or that amount, so please help us with this tool. 

Maybe for Middle Eastern or other countries, the price of that robot is not a big deal, but roughly $10,000 for an unattended robot is a very big deal for us. 

They are switching their licensing from a legacy mode to flex licensing. With that kind of license, they have given up a certain fee, which is okay, but the robot cost is high. Orchestrator is now free on the cloud platform, but we need UiPath Studio, the developer platform, as well as attended and unattended robots, and those are the things we pay for. The unattended robots are the highest priced. On a scale where one represents the most expensive and 10 is cheapest, I would rate UiPath at about two.

We have looked at several automation platforms. We have done several demos and looked at the price of Automation Anywhere and Blue Prism. But they are more complex than UiPath.

If you consider other applications, like Blue Prism and Automation Anywhere, the UiPath platform is better because it's user-friendly, making it easy to get tasks done. Even for a beginning developer, it's easy to catch up with all the stuff in UiPath.

UiPath has noticed that I'm an active contributor, so they contacted me to get feedback and invite me to build the community. If I check my LinkedIn profile, I can see all the things I've done in the UiPath community. I don't see that with the Automation Anywhere platform.

If I don't know how to do something, I can watch one video and learn everything I need to know. If we post a question on the forum, we get an answer in one or two minutes from another user.

My main use case for this product is process automation. For example, we use UiPath to make quick and easy applications for our internal office use.

It has reduced repetitive tasks. We now have more efficient processes. Manual testing was one of the time-consuming tasks that we used to do. Our testing team used to spend days and nights testing. UiPath has completely boosted the process. For example, previously, if we needed three employees to do a particular manual test, now, because of the automation that is available, we require just one employee. It has saved a lot of time, and it has also enabled us to deliver better-quality products. With automation, less manual work is involved, and the quality of the product that we deliver is very good. We have also been able to automate a lot of tasks, such as compliance tracking.

It's very easy to build automations using UiPath. Most of the things are just drag-and-drop. People with zero to minimal coding knowledge can build applications using UiPath. It's straightforward. One thing that facilitates this is that a lot of in-app guides or inbuilt tutorials are available, which makes UiPath very easy for a beginner who is starting out with UiPath. With such a good knowledge base, it becomes very easy for them to get a grasp of everything and start building applications.

It enables us to implement end-to-end automation. It also improves the employee experience. In software development, especially in the field of testing, there are many repetitive tasks, and they are prone to many manual errors as well. Automation through UiPath boosted employee morale, and it also improved the customer experience. We have been able to deliver better products on time to customers with UiPath.

It's a cloud-based solution, and it has helped to minimize our on-premises footprint.

With the AI functionality, we have been able to identify areas where automation can be implemented. We are trying to identify where process automation can be brought in and efficiency can be improved. The AI functionality is good, but there's a lot of initial work that needs to be done for this. It has enabled us to automate more processes. Within a month, we have been able to automate around 40 to 45 processes that were pending for a long time. It has definitely speeded up the entire process.

It speeds up digital transformation and also reduces the cost of digital transformation. Less manual intervention is needed, and less manpower is needed. It definitely reduces the overall cost for the company. Also, when something is automated, it's very quick. Redundant or repetitive tasks are completely reduced, and a lot of time is saved. So, it definitely saves time and cost.

This digital transformation didn't require expensive or complex application upgrades, or IT application support. Everything was inside UiPath. We just took some additional training from UiPath to get it implemented. Other than that, we did not use anything.

It has reduced a lot of human error. With manual testing, there were a lot of errors. With automation, that has been completely eradicated, and a lot of time and effort has been saved. It has reduced human errors by 100%.

It has improved our customer experience as well. We provide services to our clients or customers. Any human error leads to a delay in delivering the application. With automation, we have completely removed human errors, and we are able to satisfy our customers. It has impacted the retention of our customers.

It has freed up employees' time as well. A task that previously required three or four employees just requires one employee now. We do not spend all our time on a process. Once we implement and start an automation process, everything happens automatically. We can concentrate on other aspects of software development. It has saved 20 hours per week or 4 hours per day. 

It has saved a lot of costs for us in terms of employee reduction. We now need just one employee for a task rather than four employees. So, there are savings in terms of employee salary. We are also able to retain customers better, which has improved our revenue. Overall, about 25% of our cost has been saved. We were losing revenue and customers because they were not satisfied. With UiPath, our efficiency has improved, and the time to market has reduced. 

There are two features that I like a lot in UiPath: one is the Orchestrator option, and the other one is the Studio option. I especially like Orchestrator because it's very insightful for us. It's like a centralized hub to manage and maintain all of our process automation and task-mining. It systematically organizes each and every folder so that it's easy for us whenever we need to know, set, or take something. Studio is where we primarily do most of our designing. It's a very good tool. Most of it is drag-and-drop. These are the two main useful features for us.

The dashboard view could be more visually appealing. Dashboards in any software should stand out with colors, numbers, and other things, but in UiPath, the dashboard is not that visually appealing. The UiPath team could make it more visually appealing for us to get more insights.

Another improvement area is related to product updates. Earlier, we used to get monthly updates about the product, but that has stopped now. If they could bring that back, it'll be very good.

We have recently tried the AI functionality. There is a lot of learning that we need to do with regard to AI. It's good, but it's not as smooth as Orchestrator or Studio. The AI aspect of the product could be better. We're currently working on allowing the AI to automatically detect areas where automation can be brought in and efficiency can be improved. That needs some more refinement. It's currently not straightforward. Sometimes, it just repeats whatever it said previously, so nothing new comes out of it. The AI aspect of the product can be much more refined. Apart from that, I don't have anything else. It's a well-thought-out and complete product. It's very easy to use and easy to understand.

I've been using UiPath for around a year.

It's a cloud-based solution. It's very stable, and we just need to make sure that it's up to date. Personally, I have not seen any bugs, errors, or performance issues with this. We are not using an on-premise model. It's cloud-based. So, the service is always available, and it's always quick. It's very stable, and I have no complaints.

The applications that we develop with UiPath are also very reliable. They don't crash or have any performance issues. They are very stable and reliable.

When we started with UiPath, our main use case was to be able to quickly and easily make applications for internal purposes, but now, we are doing a lot more with UiPath. We are doing compliance, and we are doing AI-related process automation. It's definitely a scalable solution.

It's deployed across multiple departments. Each department has its own RPA functionality and RPA usage. In my department, 20 of us use UiPath, but I'm not sure about its users in other departments. 

Their support team is very knowledgeable. Whatever issues we have, they try to explain them to us in a better way. The SLA or response time is pretty quick. It's 24 hours for us. I have no complaints. I would rate them a nine out of ten.

In addition to the support team that UiPath has, I depend on the user community for all my queries. I see the UiPath Community as the main support tool. It's my go-to space for anything related to UiPath, and I am very satisfied with the quality of the community.

Positive

I am not aware of any other solution that we used to use.

It didn't take a lot of time to implement, which is a very good thing about UiPath. In about two to three weeks, we got the entire setup done. That was very quick.

It's a cloud solution. We have deployed it on AWS. Being a cloud solution, it requires very less maintenance from our side. That's one of the very good things about UiPath. We just need to make sure it's up to date.

We have definitely seen an ROI. Customer satisfaction has improved a lot. We have been able to retain customers better, and we have been able to reduce manual errors by 100%. 

Its pricing is straightforward. There are two editions: one is the community edition and one is the enterprise edition, which is a paid one. The paid edition is priced reasonably.

They charge extra for additional training and implementation, but that should be bundled up with the enterprise edition itself. All in all, it's reasonably priced.

To anyone considering UiPath, I would advise checking out the trial version of UiPath before going on to the actual version. Before you start using UiPath, there are a lot of things you need to get your head around. People who generally use UiPath have zero or minimal coding skills. This is something that you definitely need to know.

You can try out the UiPath Academy as well. They provide certification courses. I have not used UiPath Academy, but I have seen my team using it for the certification program they offer. I have heard that it's very good.

I would rate it a nine out of ten because I have not faced any issues with the product. Whatever we wanted to achieve with this product, we have been able to achieve.

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 more than a 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.

Our primary use case involves the democratization of software through the Sysen Lever and Power User Program. Essentially, we are trying to automate complex processes that can be easily rules-based, eliminating the need for repetitive motions.

UiPath helped relieve some of the burden related to paperwork and regulation, making people happy and excited about new opportunities.

The drag-and-drop features are useful, and having the ability to integrate technical scripting is beneficial. It speeds up development while offering additional flexibility.

Scaling efficiently and supporting people with technical information has been challenging.

We have encountered scalability issues trying to figure out how to make the operations work with different setups. My particular employee group is all remote.

I did not evaluate other options before choosing iMac.

I rate UiPath an eight out of ten.

Our primary use case involves automating low-hanging fruit processes such as daily reporting, order entry, and AP invoice processing. We are a printing company with 33,000 to 34,000 transactions a year, and 70% of these are repeat orders that we aim to automate.

Implementing UiPath has increased speed and accuracy, freeing up staff to focus on higher-level tasks requiring creativity and attention. It has resolved the issue of order entry delays, reducing a process that could take two to four days to just five minutes.

The document understanding feature has been particularly valuable as it recognizes and extracts data from invoices and purchase orders, greatly saving time.

The fast growth of UiPath can be difficult to keep up with, so more informative sessions or webinars showcasing potential returns on investment for specific industries would be beneficial.

We started using UiPath in 2018.

In general, the stability of the solution has been positive.

UiPath has been able to keep up as our environment grows.

The customer service and support have been great, consistently providing answers or guidance.

Positive

We did not use a different solution previously. We chose UiPath for its user-friendly Studio and comprehensive resources.

We initially partnered with a company that was not the best fit, and have since switched to a more suitable partner, greatly improving our experience.

We have yet to realize a significant return on investment due to initial partnership challenges. However, we are now on track with a new partner.

Pricing is fair. That said, it requires justification for returns due to a tight budget.

I would rate UiPath a ten out of ten.

We use UiPath for social media marketing.

UiPath increases efficiency, speeds delivery, and automates repetitive tasks to save time. We can streamline tasks and make daily work more meaningful. Instead of doing the same things over and over, employees can focus on more important work.  

It also allowed us to automate many internal processes, saving significant time and increasing the accuracy of reports and monitoring. It also helped improve customer satisfaction and made significant time and cost savings.

The most valuable feature is the autopilot or copilot AI feature. While we have not used it yet, I'm told the Document Understanding feature is also highly powerful. SaaS is also valuable.

The UiPath Studio development suite response can be a little sluggish, depending on the workflows you use. I use a lot of legacy workflows, and the application response is slow. 

I have used UiPath for three years.

The UiPath Orchestrator has been pretty stable overall. There have been a few outages. 

We started with three licenses and still have that. We also have one test bot test license, and it's scalable.

When we opened a specific ticket, UiPath lacked the resources to help us. Getting someone to help you was hard because you needed to go through different channels. 

Positive

We needed to connect three unattended bots to the Automation Cloud and Orchestrator. Setting up on-premises for different applications that don't have their own infrastructure may be a little more difficult. 

We did not use a partner for implementation.

We've saved about 350 hours using UiPath, which equals about $500,000. When we automate jobs that take longer manually, the time savings are pretty straightforward.

UiPath's pricing and licensing are in line with the market. We haven't used AI units yet, so I'm unsure about their pricing.

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.

UiPath is our platform for automating tasks and processes within our manufacturing environment, to boost productivity and streamline overall operations.

UiPath utilizes a hybrid deployment model, where our virtual machines reside in a federated cloud environment, while the UiPath orchestration engine itself remains on-premises.

UiPath stands out for its user-friendly development environment and minimal programming requirements. Building automation with UiPath is a breeze, making it a strong selling point for those looking for an easy-to-use RPA tool.

UiPath offers end-to-end automation, but there's a catch: it requires full access and control within the target environment. This means UiPath needs security permissions to interact with and potentially run other applications, which can be a challenge to set up. While achieving end-to-end automation is valuable, this access requirement can be a hurdle.

UiPath has reduced our on-prem footprint, freeing up resources that were previously dedicated to maintaining that infrastructure. These resources can now be used for other tasks.

We saw the benefits of UiPath immediately upon deployment.

The UiPath user community has been a valuable resource for quickly solving problems. By interacting with other users, we've been able to share insights and find solutions to specific programming issues.

We leverage UiPath Academy courses to prepare developers for certification exams. These courses serve a dual purpose: getting new developers acclimated to the platform and providing foundational knowledge for citizen developers who want to learn UiPath quickly.

UiPath accelerates our digital transformation, but integrating legacy systems can be a hurdle. While UiPath excels once deployed, the process of granting it access to legacy data for proper functioning can be time-consuming in our environment. This may be specific to our setup, but it's worth considering nonetheless.

UiPath significantly reduces human error by automating tasks and allowing for faster turnaround. This means that even if users make mistakes in their submissions, UiPath can quickly catch them and provide feedback so the user can fix the error and resubmit the issue.

UiPath has helped free up our employee's time for other projects.

UiPath significantly reduces our transaction processing costs. Previously, transactions took days to complete, but now they're done in minutes. This efficiency translates directly to cost savings, and it's just one example of how UiPath can optimize internet-based processes by streamlining workflows and minimizing processing time.

A key feature of this solution is its built-in VM orchestration capabilities, allowing us to manage virtual machines without additional setup. This includes basic functionalities like starting and stopping VMs, as well as integrating queues into our orchestration workflows. Additionally, we can leverage built-in Insight reports to extract transaction and volume data for analysis.

The biggest hurdle in UiPath Academy courses has been completing projects, especially for advanced certifications like RPA developer. With everyone juggling work and deadlines, dedicating significant time to capstone projects becomes difficult, leading to course completion struggles for many.

UiPath could improve its services and account management. Specifically, greater interaction with the services team would be beneficial to understand their capabilities better. This could involve trial runs where the services team demonstrates the value they can provide before being engaged. Additionally, providing sample automation, such as starter automation for SAP workflows, would give users and teams a starting point to build upon instead of starting from scratch.

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

Our daily automation runs smoothly, and weekly ones seem stable for users. However, I get frequent alerts about downtime, potentially due to VM configuration issues. Since we have multiple VMs and I might receive alerts for others, some get unintentionally ignored without impacting functionality.

We've found UiPath easy to scale by adding virtual machines to handle more automation. As we expand our automation to support more users and environments, we anticipate needing another bot. Adding a new bot to UiPath is straightforward - we can simply assign an existing automation to the new bot and keep it running. The only additional cost is for the new VM. Overall, UiPath scalability has been positive for us.

The quality and speed of the answers from UiPath technical support are good. We have a good support-level contract with UiPath that gives us enterprise-level support. 

Positive

I would rate UiPath eight out of ten. It is a good solution but it wasn't made for ambiguity.

We primarily focused on UiPath for automating desk-level processes without initially considering other solutions. However, before implementing any automation, we assess its suitability for UiPath and whether a workflow tool like ServiceNow might be a better fit. In essence, we compare these two technologies for workflow automation needs.

UiPath took longer to use at first due to the learning curve, but now we're more experienced with the software, so creating automation is a breeze.

UiPath requires annual maintenance, which involves upgrading to the latest version. This process includes migrating virtual machines and thoroughly testing existing automation to confirm their functionality after the upgrade.

New UiPath users should consider two main factors: process type and system compatibility. UiPath excels at automating well-defined, repeatable processes that can be observed and coded. It's ideal for desk-level tasks and works well with Microsoft applications and many browser-based systems like SAP. However, custom systems may require additional effort as pre-built UiPath packages might not be available. By focusing on deterministic processes and compatible systems, new users can identify the best use cases for UiPath.