UiPath Reviews

We have tried more of the RPA part. We haven't used much of the cognitive part.

We use it for our client purposes. We don't use it much for internal use.

It has helped to automate many processes. One of the places where we have tried it is the Citizen Development Engagement Program. That's where some of the people who were tech-savvy were able to use it properly.

It enables implementing end-to-end automation to an extent. Having a single tool for everything is helpful.

It reduces human error. A person can focus on his or her core activities rather than doing repetitive tasks.

It has freed up employee time. The time saved could be 70% to 80% depending on the use case of an employee.

The product is good. It's highly scalable, and it's stable. Over the last one and a half years, based on whatever we have developed, we've found it to be pretty stable as compared to the other platforms, such as Automation Anywhere.

We have used UiPath Academy courses. In UiPath Academy, there are courses and role-based training programs. They are good and effective. They give you some exercises to perform, and the community edition is also available, which is good.

The cognitive capabilities of UiPath are pretty time-consuming. If that can be improved, it would help a lot.

I'm not using it directly. Our team has been using it for the last seven or eight years. I have some experience with it but not to a very detailed level. 

It's stable. I would rate it a nine out of ten in terms of stability.

It's scalable. I would rate it a nine out of ten in terms of scalability.

Their support was good, but at the same time, for certain areas where we had issues, we had to directly call them up and try to get support from their internal COE teams. I would rate their support a nine out of ten.

Positive

We weren't using any other solution previously.

I wasn't involved in its initial setup.

They would've not directly saved costs, but they certainly would've gotten some value in terms of time efficiency or productivity, which would've indirectly helped them to save costs. The savings also depend on the FTEs freed because of automation.

I didn't evaluate any other solution, but people in my company might have evaluated other options.

Understand the product first, go through their internal training, and then decide whether you like it and how you want to use it.

It can speed up digital transformation or reduce the cost of digital transformation, depending on how you use it and where you use it. This digital transformation doesn't require complex application upgrades, but support upgrades are required.

I've explored UiPath's community, but in a couple of instances, I didn't get any proper responses or proper answers. We had to directly get in touch with the UiPath team for insights and information about the queries we had.

Overall, I would rate UiPath a nine out of ten.

My major use case with UiPath is to create automation applications that reduce manual work. At the same time, we use it to record and update our processes. 

UiPath has helped us elevate our automation process and reduce silos in our businesses. We have been able to deliver better results by using UiPath.

UiPath has improved efficiency with its end-to-end automation process. For example, we do data transfer using UiPath automation. Right from the insertion of data to the transfer of data to the end-user, everything is completely automated now. It's very apt as end-to-end automation software. End-to-end automation is very important because there is no manual intervention needed, once it has been set up. A lot of time and a lot of effort has been saved because of end-to-end automation.

Because no manual intervention is needed, 80 percent of our time, overall, is being saved right now. For example, tasks that required around 10 employees to do only require two employees. The remaining eight employees can focus on something else, to improve sales or our product feature list, et cetera. And invariably, overhead costs and employee costs have been drastically reduced with UiPath.

We are using the cloud version of UiPath, and it has definitely helped us to reduce our on-premises footprint. There is absolutely no on-premises maintenance because everything is on the cloud for us. Server updates and the like happen on the cloud. Currently, we just have a couple of systems on-premises for manual work, but apart from that, our on-premises footprint is almost zero.

Another benefit is that UiPath has reduced the cost of digital transformation because it's complete, end-to-end automation software on the cloud. Everything is digital for us now. There is no paperwork or manual intervention needed. Employees who work remotely can get easily connected and download and process data, as well, with UiPath. This digital transformation didn't require expensive or complex application upgrades or IT application support. UiPath is very straightforward software. It's one of the easiest-to-understand RPA platforms. So we have not used any third-party applications or anything else to do our tasks.

We deal with a lot of data and UiPath has definitely reduced human error. Previously, while transferring data, data loss would happen here and there, and that consumed a lot of time. But since the end-to-end automation with UiPath, there are zero errors. It's very useful and has greatly improved our efficiency. We have seen about a 25 percent improvement in overall efficiency since we started using UiPath. It has saved us three hours per day out of an eight-hour workday.

The most valuable features for me are the Automation Hub and Studio. I engage with the Studio functionality in UiPath, as that is where most of the design happens. I'm from a non-technical background, so for me, it's very easy to just drag and drop the fields using the Studio functionality and place them in my workflow module. That is my favorite aspect of UiPath.

The option in Studio of the drag-and-drop functionality makes it very easy to design certain applications. One project that I have been working on is building security automation for our organization. For example, if anybody plugs malicious devices into a laptop or our system, a notification pops up. And if somebody logs in to our system from a different account, a notification pops up. It has been very straightforward to do that. It's not rocket science. Just drag and drop and proceed from there.

Also, the user community is fantastic. I just post whatever queries I have on the user community and I get a lot of responses immediately. That has been very helpful for me. It's one of the premium communities out there for any software. I'm enjoying the user community.

In terms of the product, I don't have any complaints. Here and there, small server downtime happens, but that is expected with any cloud-based software.

I've been using UiPath for about a year.

Being cloud software, it's stable. They just need to make sure that it's up to date.

Initially, we started out with 15 users and now we have 25. In that way, it's scalable, but any automation software is scalable.

They could provide much more premium, quicker customer service. I'm from India and the customer support team is elsewhere. There's a time difference and, whenever I post a query or ask them for help, the response is delayed. That is one way they could improve.

In terms of their product knowledge and quality, I'd rate their technical support very highly, but it's their response where they could be much more efficient.

Neutral

Before this, we were actually trying to develop an in-house application ourselves, but things didn't pan out for us. That's why we switched to UiPath. We didn't use any other software.

I was partially involved in the initial setup. I wouldn't say it was complex; it was a smooth process for us. It took around 25 days for us to get it up and running in our organization. We expected the process to go on for two months at least, but that didn't happen. It was quicker.

A couple of our guys, along with two employees from the UiPath team, worked together on the implementation. They gave us initial training on how to go about things.

We are a very small startup company. We have three teams in our organization and the platform is deployed across all three teams.

UiPath has resulted in a greater return on investment in terms of profits. We have seen a 20 percent increase in our overall revenue for the last financial year. We have seen a good return on investment from UiPath.

For the features and the quality of features that they provide, it's a very reasonably priced product.

We didn't evaluate any other options before going with UiPath because we knew it was one of the market leaders. It was just a matter of whether it fit our budget or not. Luckily, it fit our budget, so we purchased it.

The biggest lesson I've learned from using UiPath so far is that, in the current digital age, automation is everything. Automation is going to be the future. I would definitely urge others to start using at least the Community Edition of UiPath. That is the free edition. Try using that edition first, to get a handle on things, before going for the paid edition.

We are a service-based development company and we implement automation for our clients. UiPath is one of the RPA solutions that we use for this.

A recent use case that we implemented for a client involved a macro in an Excel sheet. The macro contained approximately 1,000 lines, and it was being used in an Excel spreadsheet about 10 pages long. They had dropdowns within the sheet that had to be set, depending on the action. They also had to work with some of the logic themselves.

With UiPath, we implemented a solution where the bot will create a task. It first checks to see if all of the necessary conditions are there. If they are, then the bot will automatically run the macro. If instead, some of the values are missing and user input is required, then the bot will create a new task to request the missing items from the user. It uses the UiPath forms and the client will receive an email to say that a task has been created and that it will be completed once the necessary values are selected.

Finally, once all of the values have been selected, the bot will run, use the input, and complete the execution of the macro.

A second use case for us was done using the Action Center. In this case, our clients send emails, and we have API calls that are done in response. Once an email comes in, a message ID is created and assigned to it, then it is turned into a Queue item. At that point, the user is presented with different actions that are dictated by the content of the email.

Depending on the user's selection, there are three or four paths that it can take. Ultimately, the bot will send an ETA and some request data to the appropriate parties, which is controlled by yet another process.

Using UiPath for automation is a little bit costly but it saves a lot of time, and it also reduces human error. When humans perform tasks, there are a lot of errors that come about. However, when a bot performs the same task, the number of errors is significantly reduced. This is the reason that companies are implementing UiPath and undergoing a digital transformation.

In our experience, bots run with minimal errors, in the one or two percentage point range. Of the thousands of items that they process, very few will result in an error. Humans, by contrast, normally have an error rate of 5% or 6%.

It is very easy to develop automation using UiPath, and I would rate it a four out of five in this regard. This is true whether it is IT automation, UI automation, desktop automation, or otherwise. We have even performed Citrix Automation recently, where we used remote runtime. In that case, we had access to a lot of features and this made our work very easy to do.

This product enables us to implement end-to-end automation. Some of our clients use the process mining feature, which includes task capture. Then, based on that, they generate the process design document (PDD). After they have the PDD, the bot is designed using Studio, and then it is ready for deployment. Deploying a bot includes publishing it using Orchestrator, and once it is running, Orchestrator monitors it. From end to end, UiPath is part of the process.

This is important to us because some of our clients are not very technical. They have ideas of what they want to do, so they walk us through the steps in a process. During that time, we will begin using the task capture capability to record what they do, making it easier for us to gather ideas and requirements. The whole process is an easy way to capture good use cases for the client.

Most of our clients are now opting for cloud-based deployment. This is important to them because they don't have to store everything on their on-premises servers. Essentially, they don't have to waste any space.

One of the features that I like is that the bot will continue to work on other tasks, even if one task is blocked because it is waiting for user input. For example, it's very good because whenever we need to have user input, we don't need to use the attended automation. Just because the user is not available to select the actions, it will not break the bot. Rather, the bot will work on other tasks. Once the person manually completes the required action, the bot will resume the pending task.

It is very easy for us to get selectors by using the UI Launch Explorer. I have used other tools that require we visit the webpage and get the selectors manually. This means that we have to inspect the page and find the elements. However, with UiPath, we have the selectors readily available using UI Launch Explorer.

Another good feature is the UiPath Academy. Whenever a new feature is released, we learn about it from the Academy. I would rate it a four out of five in terms of helpfulness for getting employees up to speed. When we review the new courses that they release, we can quickly get a complete idea of the feature that they are presenting.

The UiPath forum is very helpful. It is the best forum available for any of the tools that we have. I would rate the UiPath forum a five out of five.

One of our clients is using the UiPath Apps feature, and although it is easy to use, they are having some issues with it. For example, when they deploy an update, it is pushed to the cloud and then it will break an hour later. There have been two or three such issues and ultimately, they result in a high priority ticket to fix the problem.

I have been working with UiPath for approximately four years.

With respect to stability, the general system is stable. This includes the robots, Automation Cloud, and the Action Center. However, we have had a lot of downtime with UiPath Apps. It had been one or two days per month when our processes were getting blocked and although many of these issues are resolved, last month we had recurring issues with downtime.

The technical support team is very helpful. For anybody with a license, there is an option to raise a ticket based on priority. The support team tries to fix such problems very quickly.

Overall, the support team is very good and I would rate them an eight out of ten.

Positive

I have explored two or more other RPA solutions. One of them is Automation Anywhere, and another is Microsoft Power Automate.

When I explored Power Automate, it didn't have many features. It is a product that is still growing but when I looked at it, UiPath had more features.

In the case of Automation Anywhere, it's a little bit more difficult to work on. As an example, Automation Anywhere does not have ready-made selectors. There is no equivalent to the Ui Launch Explorer so we have to go to the webpage and find the elements by ourselves.

One advantage to Automation Anywhere is that it's a little bit less costly.

Using the Apps feature for one or two of our clients has sped up the time required to develop bots for them. Also, because it is a drag-and-drop interface that only requires a small amount of coding, making it work is much easier.

Our clients dictate the deployment model, whether it is on-premises or cloud-based. One of our clients uses Amazon but the majority of them work using virtual machines that are running on their in-house servers.

The automation saves time and money for our clients, although the amounts vary and are based on the specific solution. As an example, in an email task that we automated, the bots replaced a team of people. On average, the automation saved 28 hours per day for that task.

In general, several hours can be saved per day for each automation.

Due to the reduced costs and other benefits, our clients are ready to create more bots.

UiPath is a little more costly than competing solutions such as Automation Anywhere. 

The cost for licensing is handled by our customers that use the bots.

I have not personally used the AI functionality when creating automations, although some of our clients use features such as Document Understanding for invoice processing. They also use the ML Trainer. These features help them to automate processes that are more complex. For example, when they have 20 or 30 invoices coming in each day, the bot is trained to look at them and it makes the job very easy to do. Also, when the accuracy drops, the bot can wait for input in an attended fashion. This has helped a lot of our clients.

I would rate this solution a nine out of ten.

I'm not currently using UiPath, but in my previous organization, which I left seven months ago, we had a complex trading application that included a web form and a Windows form. And on the Windows form was an Electron framework. If you want to run a web application inside a Windows application, Electron is a bridge between the web application and the actual Windows app. Because it was a complex application, it was not very easy to automate. That's where UiPath came in. It perfectly fit our automation testing scenario.

Before UiPath came into the picture, we were planning on doing automation testing with Selenium. The test plan with Selenium was going to take about three months. When UiPath was introduced and we started working on it, we completed the whole automation, end-to-end, in about one and a half months. It saved us that much time. And we made sure that our product was delivered with the required quality and that we did not compromise on that.

Because UiPath is SaaS, we were able to automate everything in a very productive manner. We were able to cross-verify all the flows and all the functionalities. And UiPath didn't require a huge amount of setup. It runs on minimal requirements.

In terms of human error, we saw a reduction, of course. It's not possible for a human to catch every error when new functionality is built. With UiPath automation, we were able to analyze errors right away and resolve them.

Another benefit was that it freed up employee time. It did a lot of the work by itself. The user only had to make sure that the correct workflow was involved and he could just sit back and check that everything was going correctly. It probably saved us 45 minutes daily.

UiPath makes you more productive because it comes with a lot of drag-and-drop features. You don't need to know the APIs to access particular elements on the screen. You can just drag and drop and define your actions and go ahead with the workflow. You can focus on the workflow rather than learning about the APIs, which is what happens with Selenium and other automation tools. That is one of the most beneficial features of UiPath.

I don't know if I was doing something wrong, and I did get assistance from the UiPath guys on this, but sometimes UiPath wasn't able to find an element on the screen. But that's what UiPath is for, and we wanted to make sure that our workflows were working correctly. Sometimes it was able to find an element and sometimes it was not. UiPath support did give us a solution, but it was not helpful enough.

The issue that I mentioned earlier, that sometimes it wasn't able to find the elements, was the only issue I saw with respect to UiPath. Otherwise, nothing was breaking and nothing was problematic on the UiPath side.

They were very friendly and they tried to be very helpful, but they weren't able to solve the issue I raised.

Positive

The version of UiPath that we used involved a direct installation. We asked our in-house team to get it installed because we didn't have the permissions to install software. They installed it in our system and we started using it right away. It was very straightforward.

I have worked with Selenium, which is an automation tool. That has quite a learning curve, but with UiPath it only takes you one or two weeks to get started. Once you're familiar with the basic tools, you can start writing a workflow. It is straightforward; nothing complex.

I never did the UiPath Academy courses because we had senior team members to help us and, in that company, we had a "learning playground" where we could go through the slides directly, without going through a whole learning process. We were then able to start our work right away.

UiPath did a good job. Before going into production, we needed to make sure that every test scenario and every case was handled. That's where we took advantage of the UiPath. We would run UiPath again and again and there were no breakages in our code and nothing was falling apart before going into production. I was working for an investment bank and every record was important.

We are partners with UiPath and Automation Anywhere. We use this solution for IT services and for the education sector.

OCR Tesseract, by default, is the good OCR search engine to extract data from a digital PDF. For any Unstructured document with a normal noise, background letters, either UiPath Document Understanding or AbbyyReader fails to extract the exact values. Very difficult to depend on Computer Vision too as a third party tool for small to mid-range business purpose. Hence, a combination of AI/ML with a good OCR Engine is required for UiPath to go forward.

UiPath Orchestrator is definitely a plus point in the product. This helps in all formats of UiPath version ranging from PoC till Product Deployment.

The OCR functionality for this solution could be improved. It should have a better capability to read unstructured documents. The next generation of OCR is ICR and UiPath does not have this. This would enable us to read and search through documents.

We have used this solution for two years. 

This is a stable solution. 

This is a scalable solution. 

The technical support is not that satisfactory. We have to find the answers by ourselves through non-community groups. 

Neutral

The initial setup is straightforward and the deployment was easy. 

It was implemented in-house. 

The return on investment is really good. I would rate it a three out of five.

We're an official partner of both AA and UiPath and both of them carry the same weight with a very marginal difference but there is a difference in cost. Currently our clients are looking for cost optimization post-pandemic and UiPath comes at a high price point. 

I would rate this solution a six out of ten.

We primarily use the solution for automation of the back office. When speaking about our customers and use cases, I wouldn't highlight one specifically, however, mainly, we are using UiPath to build a center of excellence. The aim is to automate a majority of the processes in the company, and that includes Order-to-Cash, HR, supply chain, and even IT, among others. We are not approaching needs for one or another specific process. We want to automate the enterprise end to end.

There are many great features in UiPath that our clients consider valuable. I definitely like Studio. The Studio's a very powerful product, which helps very easily to build automations. Nowadays, there's also a StudioX for citizen developers, which doesn't require coding.

Orchestrator, which helps users monitor and schedule robots, manage assets, credentials, et cetera, is also very useful.

The third feature worth mentioning, I would say, is Insights. It is reporting and dashboards. Once the robots are running, it is quite valuable to see how those robots are performing. You can see KPIs and other aspects of both robots and processes.

Worth mentioning is the Automation app, which helps to manage the automation initiative end to end, especially building the pipeline and collecting the ideas.

It is quite easy to build automations with UiPath, especially now that they are segregated depending on seniority, meaning that you have the regular Studio and Studio Pro, which are truly for developers, however, you also have StudioX, which is more for people without a previous coding background. That makes it quite easy to use. People with a business background find it quite easy to pick a tool up and use it in daily automation. They didn't have any previous experience with programming or making macros or whatever else, and still, they have no problem with UiPath.

UiPath enables users to build end-to-end automation, and this is what we are doing on a daily basis. UiPath enables mainly our clients (through us) to build end-to-end automation in their processes. When I mean end to end, I mean that we help them to automate the chain of processes and do not focus on the single practice itself.

End to end coverage within UiPath is a great advantage and offers great possibilities. It is really important to have the ability to do end to end. Though it is not applicable all the time, it still is a nice option to have and use when needed.

Very soon after starting the RPA journey, customers realize much more important benefits than time-saving itself and FTE saving or FTE reduction. There are things that happen, like quality improvement. Whenever the work is done by robots, it is running in a much more stable manner and without any human mistakes and errors. It is also sustainable, predictable work, meaning that robots do not get sick or have a bad day, or face conflicts with each other, et cetera. They just do their work. They also can’t get viruses, such as COVID which means that we don’t have to worry about losing staff.

We have a customer speech workload that was growing dramatically in relation to COVID and having processes already automated, it was very easy to sustain and even upscale the delivery. The customer experience is better as well. It is not only important to spend less time or fewer resources in delivering the service to the customer, it is also important that the customer gets a quick response. Overall, the customer experience can be much improved when using robots in the processes.

In terms of the Automation Cloud offering, UiPath handles infrastructure maintenance and updates to save time for our client's IT department. Having UiPath in a cloud enables enterprises and customers to focus more on the automation initiative itself, instead of managing all the hardware and dealing with all their hardware problems and having more or giving more time to the IT department. Instead, you can use everything out of the box from day one and focus on bringing benefits to your end customer or end employee.

The Automation Cloud offering has helped to decrease time to value from UiPath. I would say that Automation Cloud increases time to value dramatically in the sense that you can start from day one. Literally day one, you can go and start automating the processes without bothering with all the infrastructure topics. The time required to deliver the first benefits is reduced dramatically.

Automation Cloud’s offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure maintenance and updates. It helps to reduce the cost of infrastructure maintenance, especially in the early stages of the projects, as well as on small and medium projects (for the long term). Not all customers or enterprises have strong IT departments or strong infrastructure in-house nowadays. Even large enterprises are moving more and more towards cloud services, even though they have strong IT infrastructure teams in place.

Automation Cloud is able to scale well due to the fact that we can, in a matter of minutes, or, in the worst case, hours, double the capacity. I would say that it positively and dramatically affects the scaling factor.

UiPath is a SaaS offering. It enables our customers to really quickly adapt and start using the technology almost from day one. It is very easy to start developing. It is very easy to start.

We are using UiPath Apps for our customers. However, this feature has not yet helped to reduce the workload on our IT department, or on our client's IT department by enabling end-users to create apps. Mainly, we are still involved as a service provider in the creation of the apps for the end-users. That said, where it brings added value is it reduces the limitations or the need to have an additional user interface, as you can create this app or user interface directly in UiPath to have an even better user, employee, or even customer interaction.

UiPath apps definitely increased the number of automations created. You can take more into the scope, what wasn't there before, with just attended or unattended automation, considering the fact that you can build a better user interface or any user interface from the very beginning. Before, there were only simple message boxes and prompts. Now, you can build really nice forms to interact with your end-users. It helps to accelerate initiatives.

Our teams have used UiPath’s Academy courses. Every team member of our company went through UiPath Academy. We always start with and actively involve UiPath academy.

UiPath Academy courses are a part of our standard onboarding procedure in the company, especially if we onboard junior developers. The very first thing we direct them to is UiPath Academy. Everyone starts with a basic foundation and goes through to a diploma and certification, and only then will we build on top of that more specifics about our standards, of our delivery approach, et cetera. I would say that UiPath Academy is a core and basic start for each and every employee in the company. Based on that education, we will later elaborate on different topics.

The biggest value I see behind UiPath Academy is its simplicity in terms of delivering the information. Even if you don't have any previous development experience and coding experience, all the explanations, videos, practical tasks, and reading material is formed in a way that is really easy to understand. The biggest value I see is its ability to bring people up to speed from really different levels, including very, very junior people with no previous experience in coding, programming, or the creation of robots.

UiPath's user community is excellent. Being an MVP, for me, the community has huge value in the whole end-to-end journey of RPA. Meaning that, at the very beginning, whenever you need to learn new things, you can always find a lot of useful hints in the forum and in the community. Later, when you already have delivered some solutions, you might face some problems. Luckily, very likely, you are not the first person to face those problems. There is always someone who already has had this problem and may have even raised it in a forum or on YouTube, et cetera. Even when you are already deep in delivery, sooner or later, there will be a point where you reach out for help to the community. The community, therefore, plays a crucial role for developers and automation specialists - be it business analysts, developer architects, et cetera. Having a strong community is definitely one of the most important factors that sets UiPath apart.

I'm not actively involved in other communities, and therefore wouldn't be able to compare UiPath to other similar communities. I can only say that the UiPath community is very supportive and very active in responding to any queries. The way it’s organized, it’s inspiring the next generation of forum members to help others and pay forward with insights based on the help they receive. UiPath’s community is really responsible and supportive.

In terms of reducing human error, at the very beginning, almost every company when starting the RPA and automation in Germany thinks of FTE saving as the main benefit. However, very quickly they recognize how huge the value is behind the quality improvements that happen after automation. It is quite obvious that robots are not doing human-like mistakes that may be caused by, for example, not paying attention or not getting enough sleep et cetera. Robots also cannot get bored. Very often, and whenever you have to process 1,000 or 10,000 records in more or less the same manner, it just becomes super repetitive. A mistake can appear in manual work as humans can lose focus on redundant tasks. This is not so when robots are involved.

In terms of time savings and error reduction, usually in our initiatives, we can see not higher than 5% of error rates when executed by robots. Even in those cases, I wouldn't say they are errors and more likely exceptions, which are documented and later handed over with specific explanations. A good KPI for our robots is to have less than a 5% exception rate. Related to this is that, by improving quality, we still save a lot of time as it can reduce the number of reworks which we might have afterward. For example, in one of the projects we were delivering, it reduced by eight times the amount of reworks or fixes, which the customer needed to process due to human-directed errors. Mistakes and fixes, therefore, were reduced by eight times.

What I would improve in UiPath, or I would just say, keep on improving, is the other products in end-to-end automation. UiPath started with Studio and Orchestrator as a core product, and still, we are actively co-operating UiPath and suggesting improvements for the other products. 

One of the products where I would definitely see a need for improvement would be a Task Capture. It is already good, however, there are many aspects and many ideas, which, for example, our business analysts have, which can be improved.

I've been using UiPath since 2016. It is already over five years. I'm familiar with the product.

Both on-prem and cloud solutions are very stable. The cloud is stable thanks to the UiPath team and on-prem, in our case, is stable thanks to our customer IT infrastructure team. Between the product itself and the infrastructure, be it Azure Cloud or on-site infrastructure, the stability is good. If there's any instability, it could be related to the people involved in using it as I've had a good experience with both cloud and on-premises stability.

The scalability of UiPath is one of the main competitive advantages, compared to other products. The software and the solution give you the opportunity to stably run it and scale it. With stable operations, you can focus on the new automation instead of maintaining already existing solutions. UiPath is very good at scaling in a friendly way and has good support that can help too.

I'd rate the solution at an eight out of ten. I never give ten, just to keep the motivation to improve high. I still believe that there are areas of improvement, though I really rate UiPath's support very high. The response time can always be shorter, the specification on solving problems can always be better, et cetera. Overall, I am extremely happy with the support UiPath provides in over 95% of the cases. For the remaining 5%, we still received the needed support, it only takes another iteration to move through another team and have a look at the problem.

Comparing the initial setup on cloud versus on-premise, the cloud configuration is much easier. This is one of the purposes of the cloud solution. It's meant to be easy to deploy and easy to scale. Documentation for the cloud is definitely straightforward. In terms of on-premise deployments, it is also quite straightforward, especially at the start, however, the complexity grows with the demands and requirements from the customer. If we have to get into the area of high availability and more of a complex server setup, it takes some effort to establish everything.

The simplest deployment on the cloud would take a matter of 15 minutes or maybe even as little as five. After five minutes you are ready to go and can use Studio and the cloud Orchestrator. It is very fast. You still need to have your admin rights available on your PC, however, that's the only prerequisite. 

For deploying on-prem, it's nearly the same for a simple deployment. If you only want to use the Studio and attend the job, it is very easy to configure in a matter of 15 minutes. Whenever you get into Orchestration, it will require more complex setups. It might take one or two days to set up, depending on how good of an infrastructure team you have to onboard.

The strategy in implementation remains the same no matter which deployment. In the end, you still have the same setup of products, be it Studio, Orchestrator, Task Capture, or whatever else. You have the same configuration of the products. It is only on the backend that is slightly different as it is hosted in another place. You don't really recognize the difference between cloud and on-prem hosted services.

At the very beginning, when we started the RPA journey, we were always tasked with understanding and looking at the potential return of investments. Therefore, we don't start automating the process before understanding the savings. For each and every process which we automate, we start with understanding what it will bring to the end customer. Even if we see minimal savings in the processes, we automate these. The biggest processes which we were automating were saving more than 20 FTEs (Full Time Equivalents). We are speaking to just about one process.

For us, FTE saving and time-saving are the same thing. It’s just different units of measure. You can measure it in people equivalent or in an hours per year equivalent.

The good thing about UiPath is that they are very active when it comes to listening to feedback. Every release incorporates some of this feedback into the product life cycle.

We are using both UiPath's Automation Cloud offering and the on-premise solution. We have customers, which need on-premise as well as customers which are running it in the cloud. On-premise, we have clients using different versions, however, it's my understanding that we are using version 2020.10.

I would definitely recommend, when starting the RPA journey, to start to use UiPath. Think about RPA as a robot factory, as a strategic thing, however, do not focus on one or another process. Think big and aim for automating all the manual processes in the corporation and from day one, and work to adjust all your procedures and infrastructure, the way that you've been able to get to this point. Do not get stuck at some point and feel you need to rework anything. Rather, change your standards in order to scale. In fact, aim for scalability from day one.

I'd rate the solution at a ten out of ten. We are a happy partner of UiPath and we have had many successful implementations with our customers. I can confidently say, after five years of experience using UiPath, that I've been happy with it. I still believe that there is always space for improvement. However, I really do have an appreciation for the tools. They're making a really good product and they should keep on improving at the same great pace. We plan to keep on using this product to deliver the same great services to our customers.

It's on multiple platforms like Oracle EBS and other IT applications. We have a few of the local government applications that the client uses. We have worked on multiple use cases with all of these applications. All of the client's major work is all through Oracle EBS. We have finance-related use cases. They have Seabridge applications, which are one of the applications that we are automating using UiPath.

Oracle itself has been very helpful when using this solution, thanks to the redundant task they've currently defined. All those are being automated. We mostly use the UiPath Assistant, Video, and Orchestrator. These are the only three products that we use day-in and day-out for our clients.

The ease of building automation using UiPath is great. It technically provides good features in order to develop, automating different kinds of applications using UiPath.

UiPath enables you to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automation. It's usually very important. In some regulation cases, redundant cases, it’s been very useful. Instead of avoiding human intervention digitally, we are utilizing the UiPath to build up automation and run those in unattended mode.

If we could use the UiPath Apps feature, it would increase the number of automation and reduce the time it takes to create them. That said, at this time, I do not use this aspect of the solution.

UiPath has reduced human error in some cases. For example, a client has monthly payroll activities, which have to be done for multiple entities and in multiple in order to ensure the reports to be pretty good. It's a huge asset, having these multiple entities. It takes a lot of time for a human to execute the task. Here, automation plays a key role and it creates everything automatically through unattended mode. Of course, when a human is involved, there are chances for errors, such as missing the entities and updating the parameters. All of these things are instead being taken care of by automation. The likelihood of error is removed when the human intervention is.

The product has freed up employee time. It’s likely freed up more than a day, an average of 12 hours at least. That’s 12 hours per day. It allows our employees to focus on more high-value work.

We do use the Apps feature, however, it hasn't really helped reduce any workload. Everything is dependent upon the client's local language, which is Arabic. That is the major reason why we could not implement or utilize much of the Apps. It's not able to recognize Arabic versions properly. That is the challenging area which we are observing currently.

The solution is helpful in terms of speeding up or reducing the cost of digital transformation for our clients, however, the license cost is a little high. We are facing some challenges in the form of money. The license is costly. 

While employees can now focus on more high-value work, I would not go so far as to say it has improved employee satisfaction.

In UiPath, we have multiple products and recently there have been many product videos. There are videos around customization, deployment, et cetera. are all scattered all over. There are different products and different server setups and various other things, however, it is not organized. If it was simplified, it would be much better.

It could be more user-friendly. There are so many offerings and configurations and customizations that make things a bit complicated. Streamlining it would be ideal.

There are a few small things that should be included in UiPath. There are a few, although I can’t remember all. One, for example, is, when we are sending an email, we should be able to set up options and customize it a little bit. At this point, we need to create custom code and then go through APIs if we want to customize. It should be a built-in functionality, however.

I've been using the solution for two years now.

Stability-wise UiPath is good, however, it releases twice yearly. Therefore it will be a little hard for people to upgrade in-house each and every time. Clients also question why it's necessary every six months to upgrade. It won't be reasonable for the management. Every time when an upgrade is available, we have to complete the regulation for the previous use cases and whatever we already have deployed at production. 

When redeploying, everything is kind of a hectic task. Once in a year is okay, however, multiple releases in a year is a bit much. Clients would not be aware that yearly this many releases are happening and every release will have something more to add, that there are changes. Having to adapt to changes is something that is very difficult to make the client understand.

The solution can scale. 

You can use the application to automate any kind of application or any kind of use case. A few of them require some customization, using other technologies. 

Already we have some 25 bots running in production and a few of them are about to deploy to production and the client is looking for some more use cases. We are looking into a few more use cases that are in the discussion stage as of now. We are increasing our use cases and expanding usage.

The technical support is very helpful, however, there have been cases where we have had some urgent issues and support seems to move at its own pace. They won't rush for you. They don't seem to understand our concerns and they seem to only focus on their own timelines. 

Our SLA expectations are not always matching theirs. Even when we mark something as urgent, still there's a timeline of two to three hours. In that time it'll be hard to hold on.

Our clients did not use a different RPA solution before UiPath.

I do not have any other RPA solution experience beyond UiPath.

I am the solution architect who setups.

I was working on the 2018 version of UiPath. The 2018 and 2019 versions are very easy and very straightforward. There were not many changes or many complications in order to set up or upgrade. However, when it comes to 2020, from 2020 onwards it's very complicated.

Now there is an IAS. There is no connection string update. We cannot update any connection strings, and yet we could in the 2019 version. From 2020 we're not able to do the changes at all unless we go further and do another upgrade or something like that.

Earlier it was straightforward. Maybe there was a little bit of conflict, fine, however, now that it's split into multiple things with a conflict DLL file, orchestrated DLL file, identity server file, then an app setting the adjacent file. That is gathered completely into all of these things, where until and unless you have both end-to-end documentation understanding, you cannot go ahead and do anything.

On top of that, there is the SSL certificate. Until 2019 we didn't require each and every robot or a development machine to have the same SSL certificate. Now, we have to export and import to all the machines and add the user's perspective.

From the licensing perspective, licenses were straight, and there was no migration required for the license to be utilized in any of the versions. From 2020, there is a license migration required from the UiPath end. We now need to contact UiPath for that in order to get this migration done.

All of these changes, as well as the identity server database creation, everything has a kind of impact on the ease of deployment.

Upgrading doesn't take much time, however, users deploying the solution should have a ton of knowledge about each one of the steps. They need to remember everything in order to perform the upgrade or else something might be missed. Even if you miss one step you will have to spend hours and hours in order to rectify that.

For the 2020 version, for the initial deployment, I did not actually do it from scratch. I just upgraded. That said, if a user wanted to do it, I would estimate it takes more than a day to complete.

The implementation strategy depends upon the requirements of the client. For example, if it is on-premises versus if it is on cloud and/or if the client is looking for Elasticsearch or Insights or test automation, et cetera. All of these things will be dependent on the other. If you ask for Insights, you need to have an extra server setup for that. The same thing follows with the test automation and SQL database. What we call roles and responsibilities also will be dependent.

The unattended licenses are a little costly. That's the challenging part for us. That said, with the continuous support to the client, as we are increasing the use cases, it will lessen the cost probably by the middle of next year. At least, that’s what we are hoping for. We hope to see an ROI then.

The license cost is a little high. Unattended modes are really costly. If it's not as costly, then we could propose and purchase the licenses. Of course, we get discounts from UiPath, however, just for 10 bots, not even 10, if we load 5 to 10 unattended bots within the production orchestrator with the three development licenses, we have to pay for them twice. I'm not sure how much it is exactly in terms of the dollars, however.

My company does not have a business relationship with UiPath.

We do not use UiPath in a contact center environment.

We use completely unattended automation. 

We do not use attended automation at this time, or AI, although we are aware those are options. We're looking forward to AI and it is part of the reason we recently upgraded to the 2020.10 version.

It's one of the best tools where you can work for automation. If you have more redundant work, then it is very helpful.

Except for this upgrade and installation initial steps, apart from that, the solution is pretty easy to use.

I would rate the solution at an eight out of ten.

I have worked on two UiPath use cases. The first use case is for the IT Infrastructure team for submitting server requests. They receive a request from a third-party portal through email, and then my bot reads the email and fills in the details in the company portal.

The second use case is the data extraction from Word documents. The team receives Word documents with some important contract information. I extract those paragraphs and put them in the CSV format given by the customer.

We are using UiPath Studio 2020.10.2, and the Orchestrator version is 2019.

I heard about UiPath RPA in December 2019, and I went to the UiPath Academy website and completed their learning plans. Till March 2020, there was free certification, and I completed the free certification and kept on practicing. I showcased my skills to the management in my company, and I got into RPA projects. The certification has helped me in getting good projects. It has also helped me with my work for the use cases. My position is now better as compared to the previous years, and my work is also good. 

They provide end-to-end solutions. They have UiPath Studio for the development, and they have Orchestrator for package deployment. We can also monitor the performance and execution in Orchestrator. All these are helping us in managing end-to-end automation.

All UI automation activities in UiPath Studio and REFramework are useful. UiPath Orchestrator is also valuable. These features help me a lot in my projects. 

UiPath Studio's UI automation activities help me in easily developing automation. It is difficult for RPA developers to write complex code because no one knows everything about all automation areas. For UI automation, it is not mandatory for a developer to know how to write the code for the element on the screen that needs to be clicked or typed into. The UI automation packages of UiPath provide built-in activities, and developers can directly drag and drop and indicate the element on the screen that needs to be clicked or typed into. 

REFramework is a template using which we can prepare quality workflows for the transactional processes. It has very good error handling, retry, and logging mechanisms.

We can monitor robots in Orchestrator. We can check logs, monitor the performance of each robot, and divide robots into different environments. These features are very helpful for me in managing my work. If I have two or three robots on a set of machines and I want to define my process only for these robots, I can add that process into the environment. My process will be executed only on those robots. This is a good functionality.

For every transaction, there is the queue functionality in Orchestrator. I can go to a queue and add each transaction item to the queue. For every transaction, I can check the logs. I can also check their logs based on the jobs executed. We also have triggers, so we can schedule our jobs with the help of triggers. These features are helping me a lot in managing the performance of my robot and understanding how my robot is performing.

They have UiPath Forum where I can ask any questions. Many UiPath Most Valuable Professionals are on that forum, and they help us a lot. We get quick replies. If anyone is having any challenges, they post their challenges on the UiPath Forum. I can go through them, and if they are already solved, I gain knowledge by reading those solutions. If not, I try to answer them. In addition to gaining the knowledge, I'm getting some visibility in the UiPath Forum. All these things have really helped me a lot in increasing my technical level and expertise and getting good work.

UiPath Studio supports three types of workflows: sequence, flowchart, and state machine. Flowchart and state machine are good. Sequences are also good, and they're for linear workflows. However, in a sequence, as we keep on dragging and dropping the reusable components, the size of the screen increases. If we drag and drop the conditional or looping activities on the site, the screen size increases in length and breadth, and it becomes too complex for a developer to navigate between activities. 

All programming languages, such as C, Java, Python, or Visual Basic, have script-level support. So, we can reuse their functions because they support scripting. For example, if we want to use any reusable components, Python has modules, and there is a way to import packages. For complex automations, if we can write a script, it makes it easy to manage and know the line on which we are getting a syntax error or a runtime error and how is the structure. If I want to modify the logic, it makes it easier to know in which block I need to make the changes. So, it is easy to navigate in the program. Instead of the drag-and-drop blocks, UiPath should have support for scripts such as VBScript and PowerShell. It should support scripting even for complex automation.

The user interface for logging should be improved in Orchestrator. Currently, the logs in Orchestrator show how many hours ago the execution is completed, but it doesn't say how much time it took for a particular execution to complete. It just gives you a rough idea that it started three hours or one hour ago. It doesn't tell you exactly when a particular execution started, and at what time, it stopped. To get a clear idea, I need to click one more button and go to the details of the log. I need to check the start time of the first log and the end time of the last log in the same job, and then I need to calculate the difference to know the exact time it took for completing the job. Instead of doing all that, there should be a column that gives me the exact amount of time in minutes and seconds. It will help me in understanding how much time each execution took and what I should do to improve the speed of the execution.

In my current project, there are no intelligent automation requirements, but I have learned it recently. Just today, I completed the UiPath AI Center course. I also have some basic knowledge of machine learning. They're giving us options to use the out-of-the-box models developed by UiPath and their third-party vendors. With our internal data science, we can also develop our models, integrate them through UiPath AI Center, and deploy them. They're giving us an option to use them as a part of our RPA workflows with the help of the UiPath Studio activity called ML Skill. So, it becomes very easy for RPA developers to integrate machine learning models into their automation workflows, which is very nice, but I feel there should be some more improvement. They should give more visibility into how much time a model takes to finish the training and on how many algorithms it is running. They should also give visibility into which algorithm is best suited for my requirement and which algorithm is giving the best results for my requirement. If they can also give such insights in the same UiPath AI Center, it will help me in picking up the correct model and algorithm for my requirements.

When it comes to intelligent automation, machines use machine learning. No machine learning model can reach 100% accuracy or give 100% accurate output, which is a limitation. However, there is a possibility to increase the accuracy by tuning the parameters. So, UiPath should give more visibility into their models, how the pipeline is running in the AI center, and which factors can improve the accuracy of my model. Such insights will be useful for me in improving the accuracy of my intelligent automation.

In December 2019, I started learning UiPath, and I became an RPA developer in November 2020.

Until now, I have seen good uptime. There were no disruptions in data. I've seen the services running properly 99% of the time. Their logging mechanism, job schedules are also running properly in Orchestrator. So, it is a stable environment.

We're getting good support from UiPath. I would rate them 75 out of 100. Most of the time, I get fast and good replies from the support team. Sometimes, I receive late replies, or they don't understand the question properly, and I need to explain multiple times, but they are mostly good. 

I have worked on different IT process automation tools in the past. Their support did not respond as fast as UiPath's support, and they put the tickets in the suspended mode for a long time. They also didn't understand the question a lot of times and took too much time to analyze the issue. 

I also have the advantage of talking to my Infra team because we've deployed it on-premise. They can act as the first level of support and check if there is anything wrong with the on-premise server. If it is related to UiPath functionality, then we raise a ticket with UiPath support.

It was already set up when I moved to this team. I was working in IT process automation, and I moved to the UiPath development team. The setup and licenses of UiPath Orchestrator are managed by our Infra team members. They provided me with the licenses and links to the UiPath Orchestrator. So, I make use of the resources already deployed by my team. I just build and publish the packages to UiPath Orchestrator.

I have not deployed anything in the live environment, so I cannot comment about the return on investment. I've seen my colleagues deploying it, and with the help of data automation use cases, they have reduced around 10 hours per month for each support team. For my use case, we will be able to reduce at least one or two FTE for the support team when it goes live. I'm able to predict this because I have developed and tested many test cases for my use cases.

I only know about the community version. They give us two robots as a part of the community version, and they are enough for my practice and personal automations. For the office work, my Infra team checks the licenses needed for a particular use case, and my management team manages the pricing and licenses. 

Nine times out of ten, I would recommend others to use UiPath. I have also worked on other IT process automation tools, and none of them provides the functionality, support, and community like UiPath. I had conducted a survey on LinkedIn and asked about the RPA tool that people preferred. I got 60% of the votes for UiPath.

From the development perspective, I've seen a lot of improvement in the UiPath services in the last one year. They're giving more out-of-the-box models for the AI Center, and they are also improving their courses. They are also introducing new functionalities such as the orchestration processes in which you can use persistent activities, and your robot can wait for the human task to finish, and then it can continue its job. If they make any enhancements required for our current automation, we will make use of new UiPath functionalities to enhance our automation.

They have released two new versions of their certifications. One is UiPath Associate Certification, and the other one is UiPath RPA Developer Advanced Certification. I have completed the Associate certification. For these certifications, we have learning plans. There is recommended training, and everything is given on the UiPath Certification Program website. We have the option to check their recommended training and do the practices. They also guide us about how to book the exam from the Pearson website. Going through the recommended training and doing the Associate certification has increased my credibility. I've gained more trust in the company. It has changed my career. So, UiPath has played a prominent role in my career.

It can reduce errors by 100% because a machine can give 100% accuracy and work faster than humans. Just like all RPA tools, UiPath can provide 100% automation accuracy for rule-based automation. You also get better speed because machines are faster than humans. When it comes to intelligent automation, machines use machine learning, so there is a limitation. No machine learning model can reach 100% accuracy in automation.

I would rate UiPath an eight out of 10.