UiPath Platform Reviews

I have been in three different organizations working with UiPath. In all of them, I had to create the center of excellence for UiPath. For automation, we decided to use UiPath because it was easy to learn. We had citizen developers involved. Most of the use cases were typical manual repetitive tasks and did not involve too much intelligence. I did not use the AI components in any of the use cases that I have done in the past. We mainly had end-to-end automation of simple processes. They were not too complex.

I have worked in the energy sector, and there were processes that were connected to renewable energy projects, but they were not related to a good cause, such as improving sustainability. We also had processes that did not provide any financial gains for the company, but they improved the motivation of employees. For example, we automated a process to check employees' birthdays and sent an email congratulating the person and tagging their manager as well. There were no financial gains, but it had a good impact on employees.

In most cases, it is easy to do automation with UiPath. It is not always the best solution, but in most cases, you can imitate what a user is doing. You can substitute that and create a process. It is very easy to do this. The complexity normally comes from the reengineering of the process to make it more efficient, but that is not about UiPath. That is more about the company thinking that we have been doing this for a long time and how we can make it better. It is very easy and straightforward most of the time. From the thousands of activities UiPath has, I end up using the same activities 90% of the time. It is very easy to remember and organize in my mind. As soon as I hear a process, I know how I am going to do it. For example, on receiving an email with an Excel file, we will extract the data that goes line by line into SAP or another platform. We will then save it and then write back the status by email. This is a very simple case, but it would be very hard to implement using any other technology. When it comes to end-to-end automation, about 90% of the time, you can do end-to-end automation with UiPath, but there are times when UiPath is not the best solution.

The main benefit of UiPath is that it is easy to develop and deliver automation. We can do this while software engineers are dealing with a more robust solution for the future. For example, when we need to connect different applications, and there are no API calls they can connect to, UiPath can provide a bridge for the short to medium term while resources are working on the final solution. I do believe that UiPath has a lot of strengths, but in terms of maintenance, there is one more application in the middle that we need to make sure is working for the end-to-end process to not fail. I can deliver a solution in one to two weeks instead of waiting six months for the final solution, but there will be more maintenance.

UiPath has freed up employee time, but the time saved depends on the use case. We had some very big processes that saved a few days. Overall, it frees up about 10% of our employees' time. 

UiPath has saved us costs in theory, but in practice, I am not sure. It saves the time of our people, but we are not letting go of those people, so the cost of those people is the same. However, these people might be doing other work that might bring money to the company. 

It is very easy to develop and deploy. It is easy to work with different applications at the same time. For example, I can read an Excel file and then go to SAP or any other platform. I can then open Outlook and send an email from Outlook. I can even use Teams. Being able to combine all these applications is the main thing that I like. 

I also like how fast it is to develop a big, low-code platform engine. You just drag and drop, and most of the activities are done. It is very fast to create processes. I like it.

Its pricing changed again this year. I do not know why it just went up, but I do not like that. This is something that I would like them to improve for sure. 

It would be nice to have the possibility to change the values in the middle of the debug. For example, I am debugging a process, and I write at a place. The value of that level is one, but I want to see the results of it if I change it to two. It does not seem possible in UiPath. It is possible in other software, but in UiPath, it is not yet possible.

I have been using UiPath for six years.

The Orchestrator, cloud, and everything else have been stable.

It is scalable. We have about 20 people using it. It will impact around 40 to 50 people.

I do not have direct contact with the UiPath technical support because we have a vendor, and we go through the vendor. 

The UiPath community is very good. I myself do not contribute much to the community, but anytime I have doubts, it is very easy to find a solution in the UiPath community. The community gives a lot back. There are a lot of people writing back. It is very well established. About 90% of the time, I find the solution, and the other 10% of the time, I find a way to the solution. It normally takes me less than a day. There are a lot of activities created by the community as well, which are very helpful. I know some of the people who create these activities. People just give back.

In my current organization, we were not using any other solution previously. In other companies where I worked, UiPath was the first solution, but in one company, I also worked with Blue Prism. We had both UiPath and Blue Prism at the same time.

UiPath is easier to learn. It has certain activities that Blue Prism does not have. Visually, UiPath is much more appealing. I know the visual appeal does not matter much to a lot of people, but it matters to me.

It is deployed on the cloud. We moved to the cloud last year, and it took us two months to set it up and go from on-prem to the cloud. About 50% of the time was spent on things related to our company in terms of security and other things. It was not on the UiPath side. On the UiPath side, it was pretty straightforward. It was pretty nice.

Five people were involved in total, but they were not involved not full-time. 

We have seen an ROI, but I do not have the metrics.

Its price is fair, but I would prefer it to be lower.

I would recommend UiPath. I would recommend starting with very simple processes. Do not go for a very big end-to-end process. Start with a part of it, gain confidence in it, and then start building on top of it. Many times, the process that people want to implement is too complex, and they do not put it down on paper. They do not do a cleanup of the process, and most of the discussion is happening while developing, which makes it complex, so I would recommend starting with something small, seeing the results, and growing from there.

Overall, I would rate UiPath an eight out of ten.

Most of my use cases are spread across all the business units. It's used in accounts payable or for receiving reconciliations. It is also used in directory management and the banking finance sector. 

UiPath has a lot of features and they have added a lot of things. The apps and document understanding are good. We use document understanding a lot, even though they may not be common for day-to-day processes.

The Orchestrator is amazing. It provides a huge benefit including data security and data storage.

We can add a huge number of activities and can input code right into the platform.

While there might be companies that use the product to do automation for good cause, however, so far, in my experience, I have yet to do much of those use cases. I’m more on the business process side.

The product enables us to implement end-to-end automation. When they first launched, people used to have some sort of hiccups, however, now you don’t need different tools to manage your entire automation journey. With UiPath, from the discovery phase on, you have everything you need. We can understand the ROI clearly and can see what we’ve invested and what we’ve received.

The user community is valuable. It has the biggest community. Everyone knows it. One of the reasons UiPath is so successful is the UiPath community. We have tremendous people in the community supporting each other in terms of development or community events. People from different organizations can explain different pain point areas or explain good use cases and share learning and feedback.

We use both cloud and on-prem services. Most companies prefer on-prem over the cloud. From our perspective, we’re working to convert users to the cloud to reduce the footprint. Still, many want to maintain that on-prem segment.

We use the UiPath Academy courses. Since the beginning of my career, I’ve used it. Whenever there are new products that are launched, they will release certain courses for training purposes. I've gone through training at the Academy. I found a certified trainer also to provide training. Overall, having the training available really helps new people who want to kick-start their careers using the app.

They've also implemented community collaboration. If someone from the community has developed something, they will add training based on the community. The user has larger visual data now, compared to what happened previously.

The solution has allowed us to manage digital transformation and reduce the cost around it. Automation really helps boost digital transformation. We've seen cost reduction around resource use and the cost of operations as well. 

We've been able to reduce human error using UiPath. Of course, it depends on the people developing it. However, as long as the people have good implementation experience, we can really minimize errors.

It's helped free up employee time. However, it is not a major amount across every project. Comparatively, it can save a number of hours versus manual labor. 

We have saved money and that's calculated on the number of hours saved in terms of man hours. We haven't cut staff; they are now working on different tasks instead.  

We've used AI functionality. On a real-time basis, we haven't seen many benefits from the AI center. It's not cost-effective to run models on it as of now. We haven't been able to automate more processes. Some projects don't require AI at all. If it gets more cost-effective and has more use cases, that might change. 

The tool continuously redefines itself. They release three major versions every year and target one major feature once a year, like AI, et cetera. However, there are a few features at an early stage and not quite mature yet.

The initial tools are good enough compared to other vendors, however, they are still refining and need to change a lot of things, especially in the AI center, which is not that flexible when it comes to deployment. This is the same for UiPath apps. In most cases, nobody wants to invest a lot of money in attended bots. They need to work on that.

We'd like to see them work towards more stable outcomes to minimize hiccups. 

I've been using the solution for more than six years. I started in 2017.

Previously, we haven't noticed stability issues. In the past year, we have noted issues with stability. There have been some hiccups. 

The scalability depends on the way a company implements it. From a cloud perspective, the scalability is good. That said, the flexibility is there to scale.

We've had issues in the past where products were not working as expected and we've reached out to support. The experience has been mixed. Sometimes it is good. Sometimes solutions are delayed. 

Neutral

I did not use a different solution previously. However, I have used Automation Anywhere, Power Automate, recently, and also Intellibot and Blue Prism.

Power Automate is still quite young. There are still items missing as it's new. 

UiPath excels in the Orchestrator. The flexibility is great as well.

We've worked with both cloud and on-prem deployments. However, people seem to prefer on-prem. Almost all of our clients are maintaining their own cloud and then running UiPath into the cloud from on-prem.

I was involved with the deployment. The setup is straightforward. For the governance and audit security principles, we do need to add in a bit more. We might add, for example, a CI/CD pipeline. 

We tend to have three to five people, part of the support team, to help with the deployment.

There is some maintenance required. We need to monitor our VMs and understand if the robot is failing and if so what is the root cause. We have an interior support team for maintenance services.  

We did not use an outside vendor for the setup. Only people in the department are allowed to handle the deployments due to compliance. 

We cannot calculate an overall ROI. However, if something isn't getting 150% or more, people tend to not want to implement it. So far, we've seen a very good ROI. 

The costs have gone up recently. The pricing seems to be a bit higher for the end user. 

We are UiPath partners. 

I'd rate the solution seven out of ten. The most recent tools are not as impressive compared to what is happening in the market. 

As long as others don't need additional tools like Apps or document understanding, I'd recommend it. There are a lot of features and functionality to try. However, if you need document understanding and apps, I'd advise users to look at their use case, do a POC, and figure out if it's a perfect fit. 

From the perspective of pure automation, UiPath is excellent. However, if a company is looking for AI functionality, they really need to see what else is out there and what is best for them. 

We work with the government on HR-related data and banking reconciliation. We use the solution in the insurance industry for claims management.

We use the product in different use cases. We use it for automating repetitive tasks, email and document parsing, and posting data from different systems to centralized systems. In most cases, we use it to compare different Excel sheets for reconciliation and updating the master system.

The tool helps us to envision the automation processes and gives us an edge in offering our solutions to the customer. UiPath keeps innovating new technologies. It also localizes technologies like OCR for extracting data from documents to the regional market. The reporting tools are fantastic. It also helps us calculate ROI and manage bugs.

UiPath Document Understanding and Task Mining are valuable features. I am satisfied with the product overall.

Saudi has two calendars. UiPath does not support the Hijri date. They should add it in future releases. We also face regular issues while parsing from right to left and left to right. The Arabic language is not related to the platform. We have Arabic scripts which are sometimes difficult to understand. Also, the license is complicated.

The add-ons are not well documented. When we offer and pitch to the customer, sometimes we get confused about which one to offer based on the third-party tools. The solution must focus on microservices and web-based platform building. It would be fantastic if they could produce web applications connected automatically to UiPath.

OutSystems is a low-code platform for building web-based and mobile applications. If such features are available in UiPath, it will eliminate the need to integrate with different applications. We can directly build applications using UiPath.

I have been using the solution for the last four or five years.

The product is very stable. When we deploy it in the cloud, there is no need for maintenance. UiPath manages everything. Maintenance of the configuration has to be done by us.

The solution is scalable.

When we need a technical team member's support, they join the call and try to guide us. I rate the technical support a seven or eight out of ten.

Neutral

I have worked with Automation Anywhere. It is a good solution but not on par with UiPath. Automation Anywhere has a lot of features, which is very nice. However, UiPath exceeds our expectations.

UiPath has better support, resources, and scalability. UiPath provides very good vendor support. Automation Anywhere allowed users to download preconfigured processes already deployed elsewhere so that we could just fine-tune and use them.

The product can be deployed both on-premise and on the cloud. I worked as a solution architect. So, I get involved in the conversation if there is any conflict in the deliverables. The tool is easy to deploy. The time taken for deployment depends on the complexity of the processes. It takes two to four weeks for simple processes. For complex processes, it takes six to ten weeks for deployment. After the project's completion, our engineers are on standby to resolve any issues on the project's go-live date.

We focus on high-value solutions and look at the repetitive processes we can use. The HR initiative we did is on-demand in our region due to the regulations. We can develop the process once and deploy it multiple times with zero or minimal adjustments. We focus on the high return to the organizations, the shortest ROI, and the highest value to the business so that the customer would realize the importance of such technologies. When we build trust with the customer, we have very big upsell opportunities and referrals from them.

We need one or two people to deploy the product for a small project. For large projects, we need a team of six or seven. Our team has 10 to 15 people, including developers, solution architects, and support personnel. The tool requires maintenance. Our support people are responsible for different services. Around 10% of the resources in our company are involved in maintenance.

UiPath gives pretty good discounts.

The ease of building automation using the product is fantastic. The product speeds up and reduces the cost of digital transformation. I haven't seen many major upgrades to the customer's infrastructure or applications. I design and modernize the processes. If we can’t extract the data from databases, the customer will put that data in a flat file or Excel sheet and add it to a folder. We pick them up and do the processing.

We are not supposed to touch the core system in the banking industry. So we may get it with APIs. Sometimes, APIs are not available when we do the implementation. It takes some time for the banks to build those APIs. UiPath is equipped with different integration tools, whether it is native or not.

The solution has helped to minimize our on-premise footprint. It is very important to many of our customers. To minimize the cost and provide more streamlined processes across different customers, we have created a shared pool Orchestrator to connect multiple customers to the same Orchestrator. They pretty much share the same processes, but they have different system endpoints. We can clone the processes and modify the endpoint interactions and input data. Sometimes, they use flat files. We change the configuration minimally. The rest of the processes are cloned, enhanced, and supported.

The solution enables us to implement end-to-end automation. We can automate end-to-end based on the scope, expenses, and processes. The implementation could be lengthy or short, based on the processes involved. End-to-end automation provides an edge to us as a consulting company to provide our customers with very advanced automation tools. We have different services and products that we can integrate UiPath with.

We have a content management system. When we use Document Understanding, we relieve the users from indexing documents. UiPath would do the indexing using Document Understanding and archived document repositories. We sometimes do integrations with archives, too. It depends on the context of the implementation. Sometimes, we can automate 60% of the process because some are not UiPath-targeted processes, but we can automate the other process with other systems.

We do not use AI much. We rely on Document Understanding, which is part of AI. In the next couple of years, because of AI's popularity, I believe UiPath will provide more features and enhancements related to AI. The tool has freed up employee time by 70 to 80%. UiPath has saved costs for our organization.

A couple of weeks ago, we had a case about HR contracts in the Ministry of Labour in Saudi. By the end of this year, they want to digitize their contracts and link them to their official portal, where employee contracts are issued. They currently rely on Excel sheets to do the entry. UiPath processes that we support have proven that there are zero percent errors in them compared to human data entry errors.

The as-is process was that an HR personnel must log in to the platform and do the data entry so the contract would be issued and sent to the employee. The HR personnel would interact with four or five pages and provide data like employee ID, mobile number, date of birth, position, salary, and increments. If there is an error in the data, it has a negative impact on the company. It's an official contract that is issued to the employee. If there are any discrepancies, they would have to rectify the whole process again. Besides, it would affect the company's reputation in the market.

For example, if the HR personnel enters 50,000 instead of 5,000, the employee can claim that money. To avoid this, companies can export the HR master data into Excel sheets and put it in a folder. We can program UiPath to pick all the information and paste it into the Ministry of Labour portal. We can verify the data, do a quality check, and post it to the system. This process used to take three to five days to finish, along with an error margin. With the help of UiPath, we shorten the time by 80% with zero error margin.

We have subscribed to UiPath Academy. All our engineers are certified in different UiPath certifications. I am a solution architect. I have done a lot of courses and certifications. In addition to the certification courses, UiPath Academy provides us with resources, information, built-in demos, and process standards. We deal with all the stakeholders in the customers' company.

The product must empower localization. People who want to use UiPath must ensure that the processes they are targeting to automate are fulfilling the conditions for automation. Sometimes, a customer would expect to automate everything. We need to ensure the processes we are targeting to automate are repetitive. We also need highly skilled people to manage the automation. We must automate the high-value processes of the organization to see the results and recognize the return on investment immediately.

Overall, I rate the product an eight out of ten.

We have been using UiPath to automate regular activities for a business. I'm currently working for a vendor that has a contract with a business. We are using the UiPath solution to automate all the activities that they have been doing on a regular basis. These activities have simple functions, mostly with Excel data entry and some internal applications that the client needs.

So we use UiPath to take some input, and then we process the activities for the business. Then, we share our output with them as a report on a daily basis or a monthly basis.

There are multiple angles to look at this. UiPath has helped the senior level with cost savings it has done to them by just putting the licensing in a robot and using it for all the manual activities. From the mid-level management perspective, efficiency has improved, error has reduced, and transaction turnaround time has reduced. A robot can be available 24 hours a day, and it can be used at any moment. Human users can be available, but robots have proven to be more efficient.

Turnaround time has improved for this transaction, and errors have been reduced. A bank is a service provider, and its customers use its services. From the end user's or the customer's perspective, the turnaround time for each request has reduced, the errors have reduced, and everything has been going on faster. So, these are the multiple perspectives to look at, and everyone seems to be equally happy with the UiPath solution for automation.

The most valuable features of UiPath are data entry, data reading, and some simple logical calculations. Also, the solution's ability to use Excel and to read or add data to Excel has been very useful to us as a vendor. We have been proposing solutions to the clients through these good features that we utilize to the best.

UiPath can improve its AI and optical character recognition or OCR. Currently, reading digital images or PDF documents by UiPath is a huge challenge. I request UiPath to improve the OCR recognition.

I've been using UiPath for around eight months. Earlier, I was using UiPath for personal uses, but I recently started using it professionally.

UiPath is a pretty stable solution. We have never had any stability issues with UiPath. It's in excellent condition as of now.

UiPath can be scalable. Currently, AI is being implemented in UiPath, and that's a huge boost to UiPath's features and what UiPath can do. It can be scaled to a bigger picture in multiple ways.

I have never personally contacted UiPath's technical support, but my team members have been contacting them for support. From what I understand, their technical support is pretty good.

I have overseen the deployment but wasn't involved in the deployment. From what I know, there will be a virtual machine, and bot licenses will be allocated. The UiPath automation will be installed on that virtual machine, and the bot will be allocated to that machine and run in a completely virtual environment. That's the only detail I'm aware of, but I was not involved with any process deployment.

From what I know, UiPath's licensing has a reasonable cost. Compared to the huge benefits the solution provides, it's still a huge saving to the organization even after the licensing cost.

We are using a virtual machine and running the UiPath bots on that virtual machine. A little bit of cloud is involved, but mostly, it's on-premises because it's a sensitive environment.

From my end, UiPath does require some maintenance. A dedicated team oversees all the existing processes that are running live. In some cases, there will be some maintenance required.

For example, if the bot's accuracy level has reduced because of some internal applications being updated or changed, the bot has to be recalibrated to adapt to the new environment. In some cases, the bot will stop, and it has to be monitored and fixed. A dedicated team is monitoring and maintaining the bots as of now.

I advise users to consider the environment where the solution will be used, the features of UiPath, and the challenges. They should consider how much UiPath would benefit that environment and how much benefit the end user will receive by implementing UiPath. UiPath has its own challenges and benefits. Do the proper research, and if you believe UiPath will be a good solution, go for it by all means.

I will say it's fairly easy to do the automation. It's fairly straightforward and easy to use. Everything is simplified to the basic ground level. Everything is in the UI elements, and using those automation tools in UiPath is quite simple.

I believe UiPath can do some automation for a good cause. Since most transactions running today are digitized, UiPath can automate all those transactions and activities, usually in an efficient environment and workflow. That would, in turn, have a huge impact on everything around it, like the environment or supporting NGOs and other organizations. UiPath can be used in such situations and will be very productive.

Since we are a UiPath vendor, we have been doing all those end-to-end automation for our clients. We have been implementing end-to-end automation for a long time now. For each case, we are supporting businesses to move from a manual workforce to a digital workforce. I can share a few live scenarios where we implement the automation for the client.

Currently, there are some cases where the customer has to replenish an ATM for a banking corporation. We are automating it end-to-end, starting from the request to replenish the ATM until the replenishment has been done. Then, the data has to be reflected in the internal application related to the bank.

We start with taking the request, passing it to a third-party vendor who will do the replenishment, and we'll take the reports from them. Then, we'll do the data entry in the internal application, which will, in turn, be stored in the organization's back end. It's a huge database where all the data is monitored closely. So, we have implemented this solution of automating their ATM replenishment.

Another use case is fraud calls, which some clients receive from outsiders. We are helping the bank mitigate all the risks and reduce the damages caused by those fraudsters by automating all their required actions, as proposed by the bank's policy, in dealing with all these fraudsters. I cannot disclose more since there is an NDA between me and my clients.

The UiPath's user community is very helpful. There is the forum, and there is the UiPath support. Most of the time, we reach out to the UiPath support for any concern we have related to the UiPath's functionality. The forums are also a great help. They have many topics, and a lot of knowledge can be gained from those forums, with everyone sharing their knowledge.

So, both have different uses and different scenarios to reach them. One is the support, and one is the forum, but both are very helpful in everything they provide.

As a vendor, we are supposed to develop and maintain the solutions we provide, including UiPath. The on-prem footprint is increasing as we implement more automation. However, the on-prem footprint has been reduced from a manual workforce because everything is automated and fully digitalized. So, there are two different angles to this. The on-prem footprint is increasing from the vendor side and reducing from the manual workforce side.

We have been using UiPath Academy courses for different roles. As a vendor, we are required to take these courses as and when they are available or updated. So, my team members and I take those courses on a frequent basis, at least once a year.

UiPath's AI functionality is something we are exploring now as a vendor. We have not implemented it in any client-side projects, but we are exploring that angle to see the possibilities of combining UiPath and AI. We plan to use AI along with UiPath in the foreseeable future.

UiPath does increase the speed of digital transformation because we are digitalizing the workforce and all the transactions carried out internally in the bank. It incurs a cost, but I wouldn't be able to answer whether it has increased or reduced the cost of digitalization. A mid-level to senior-level management employee will be able to answer it. As of now, I'm a consultant, but we are not aware of such commercialization details.

UiPath has greatly helped reduce human error by a huge margin, up to 80% to 100%.

One of the huge advantages of UiPath is that it frees up a lot of employee time by taking a huge workload from the employee and passing it to the bot. The main aim of implementing UiPath automation on any project is to reduce the workload on human users.

Overall, I rate UiPath a nine out of ten.

We use UiPath to minimize human effort by automating repetitive business processes.

For a technically sound person, it is easy to build automation using UiPath.

We send out live surveys to thousands of people, and we use UiPath to develop bots that can take the information and create graphs that individuals can easily analyze.

We see good value in UiPath's User Community.

In most situations, end-to-end automation is possible using UiPath.

UiPath has helped improve our organization by automating sales scripts and performing daily calculations to provide quarterly profit analyses to our clients.

It has helped reduce our on-premises footprint and increase our digital footprint.

All of our users must first complete the Academy courses before working on any tasks involving UiPath.

We use AI Center and machine learning to extract more complex information from our image-based PDFs and purchase orders.

During the first six months, we faced many challenges and had to improve our processes. However, since then, UiPath has helped us to accelerate our digital transformation and reduce costs.

UiPath has helped our employees save 60 to 70 percent of their time. Tasks that used to take one hour to complete can now be done in one minute with UiPath.

Excel, PDF, and email automation, as well as document understanding, task mining, and process mining, are valuable features of UiPath.

We have two versions of UiPath: on-premise and cloud. With the on-premise version, we have good control and flexibility. However, the cloud version is less flexible and we often receive errors. We would like UiPath to make some enhancements to the cloud version to provide more flexibility for OCRs, email models, and AI centers. This would allow us to provide better service to our customers.

I have been using UiPath for two years and nine months.

UiPath is not as stable as I would like, and I hope to see improved stability going forward.

UiPath is scalable.

Technical support is good. We receive a response to urgent tickets within an hour.

Positive

The on-premises deployment was complex, but the cloud deployment was straightforward. Five people participated in the deployment.

The pricing for UiPath is reasonable.

I would rate UiPath eight out of ten.

UiPath is deployed across multiple locations. We have around 45 people that are currently using the solution.

The cloud deployment of UiPath does not require any maintenance. 

I recommend UiPath for organizations with multiple daily tasks that can be automated. However, I would not recommend it for just one task.

I am a UiPath developer. I have automated web-based processes like HR and finance. I have also worked on a use case consisting of web-based automation, Excel automation, and email automation.

The solution reduces FTEs in processes that require 100 people for repetitive tasks. It really helps customers to reduce human effort and guides the robot to do efficient work within the schedules.

It's very easy to manage and automate Orchestrator because it allows plug-and-play models and drag-and-drop approaches.

UiPath should be able to adapt to other operating systems like Linux or macOS. The tool must reduce the activity required for workflow design. It should be made similar to Visual Studio. It should provide a better way to analyze the recursion functions.

I have been using the solution for six years.

Compared to Automation Anywhere or other open-source tools, UiPath's stability is very good. However, when it comes to very complex hybrid automation with high-density bots, where we require many third-party applications, UiPath cannot handle such scenarios.

PDF automation is very complex. Either we will have to use a third-party Python script, or we will have to build a custom OCR. We require good programming knowledge. The product must improve its stability. I don't see much stability. Though it is available in an environment like Mac, it is not up to the mark as it is in Windows.

The product is scalable.

First, we validate with the logs. In logs, we have to identify certain categories of errors. From there, we identify the root cause. During development, we rename all the activities to appropriate annotations so that we can backtrack them accordingly. If there are any exceptions, it is passed on to the Global Handler. If any error occurs, we email the support team with a screenshot. For example, if ten transactions have been processed and there is a system exception, we immediately send a screenshot to the support team.

Positive

The initial setup was straightforward. It did not include the CI/CD pipeline. There were two machines. One was the developer, and the other was the production machine. We had to deploy it into the production machine. An Orchestrator admin and a developer are enough to deploy the solution.

To deploy the solution, we create the package and describe the overall process. We compress it into a new package and assign the robots with the machine key. Then, we create certain asset queues for the processes and upload them into Orchestrator.

Once all the assets are created, we assign a VM to the package. Then, we upload the package and map it to the process name. We add triggers if required, and if any change request comes, we raise the request, the manager approves, and we proceed with the implementation. It is very easy to maintain the product if there are no version changes in the applications.

The licensing cost is very high.

UiPath's cost is very high. When we transfer the knowledge of a robot to another, certain images are not available. It's difficult to identify the XML collectors. A proper annotation or guidance must be given to the user. When a new version is updated, the tool becomes slower. It is very difficult to maintain version history because of the bulk update activities. If we want to convert from Windows to Windows legacy, it is very difficult.

We get the input files from emails. We read the input files, extract data from the template, and open it in the browser. We worked on an engineering product. We used UiPath to get information about the testing and the model's integrity. Certain information was in the Excel file. We had to extract information on whether the model had to be tested with plastic or without a plastic cover. There were drop-down messages. We captured the values and injected the JavaScript modules to autofill the data.

Once the testing was created, we created a sample order. We filled out a form from the input file, gathered all the details into a summary, and wrote an HTML code for it. Then, we sent it to the client and informed them that the test had been created successfully.

For SAP, we did an auditing type of automation. For example, we automated payments and filled in all the information from the template. Then, we had to propose, settle, and release the payment. In SAP, we are using VBScript also. It has some complex scenarios.

If it is a PDF type of automation, I would recommend the latest technology called Document Understanding. I can define and train the fields using certain anchors and then go with extractions. Machine learning models are also possible. It would be the best way to do a PDF automation.

Calling an API would be the right choice if it is an API approach. If we have been asked to download certain files from SharePoint, we create a custom Azure application. We define secret keys, certificates, and IDs. We define certain API permissions. Then, through UiPath, we install Microsoft 365. We can then download the file. If the process is more complex, ABBYY is the best choice.

Building automation using the solution is easy. We need a little bit of programming knowledge for complex or hybrid automation. For easy automation, plug-and-play connectors and activities are readily available in the solution. We just have to get trained and use them.

UiPath speeds up digital transformation and reduces the cost of digital transformation up to a certain extent. We required a ticket-tracking system where we needed additional third-party software like OneDrive and Office 365 to be installed. For Box drive, we had to install SDK. We also had other solutions like Google Drive, spreadsheets, and Zoom APIs. The solution has helped a lot to minimize our on-premise footprint.

It enables us to implement end-to-end automation. It is important for customers because they want to avoid repeated tasks. If a customer wants to search for an email and upload it in a different portal, they might have to open multiple pages. However, if we choose end-to-end automation, things can work in the backend. The Picture-in-Picture mode in UiPath allows the user to work parallel to automation. So, while the robot runs, the user can do their work parallelly.

I have not used the AI functionality much. I have used AI for a POC of a custom model where I had to identify objects from an image. There were many questions like how many people were in the image, how many cars were there, how many street lights were there, and how many fruits were there. I had to find the count of the people or objects and their confidence scores. It was a small POC with the object detection model built with Python.

The product has helped to stabilize standard and structured processes. If the data is unstructured or unorganized, we use ABBYY as a third-party application. We have to train and classify all the assets and forms. The robot trains the modules using the connector and converts the semi-structured data into structured data. We can make automation more scalable using third-party applications. The cost is very high, though. UiPath is not that stable.

I have used the Academy courses. I have also completed enterprise training and acquired a certificate as an RPA developer. UiPath has a very good community. If we get stuck on anything, we can get solutions for our problems. Currently, ChatGPT is also helping us in many ways. My UiPath skills are really good. I keep doing R&D on AI Fabric, automation, and other features. The community helps me to learn.

A little bit of programming knowledge is a must to use the tool. A level one automation or a straightforward case with repetitive tasks does not require much programming knowledge. The user can use the solution if they have knowledge about the dynamic selector and wildcards. They should have a little bit of fundamental knowledge of computers and automation.

Overall, I rate the solution an eight out of ten.

We use it for automation with different applications and use Document Understanding, AI Center, and Action Center.

There is a good chance that people will make mistakes in manual operations, especially in whatever data-entry operation they do. By defining a solution in UiPath that is prerecorded and scripted, there is a lot of reduction in manual errors. If you have 100 transactions, 80 to 90 of them can be automated because they are straightforward cases. That means we can eliminate human error from 90 percent of the transactions.

In addition, the automation solutions that we, as a partner, implement for our clients reduce the amount of manual work and they are able to use their critical human resources for other useful processes.

The prebuilt AI models that are available in AI Center are valuable to us for things like invoice processing.

UiPath is also a solution that is user-friendly for developers with a lot of prebuilt activities and ML models. It enables developers to quickly develop a solution.

We can also implement end-to-end automation.

I have been using UiPath for the past four years.

It's absolutely a stable product. It has been in the market for more than six years. Whatever solution we develop for a client is completely stable.

It's definitely a scalable solution.

The first level of support is that we search for solutions in the forum of the UiPath user community. Most of the time, we'll get a solution there. If not, we'll contact the technical support.

If I raise an urgent ticket, they quickly respond. Within an hour I'll get a call, and they'll arrange a team within two to three hours.

Positive

I used Automation Anywhere. Out of 10, UiPath stands somewhere around 8.5 to nine, while Automation Anywhere is around 7.5. The reason for that difference is UiPath's user-friendliness and versatility on the development side. For example, if you want to integrate it with VB code, UiPath provides a lot of options. And on the Excel automation side, UiPath is more reliable than Automation Anywhere.

In RPA, UiPath is far ahead compared to Automation Anywhere.

For some clients it's on-prem and other clients have deployed the cloud option.

The amount of time it takes to set up depends on the components a client purchases. If they only purchase the basic components of Orchestrator, a robot, and Studio, it may take only two to three days, or a maximum of five days, for the deployment. But if they go for high availability and some kind of DR setup, that would take an additional week of deployment. And for AI Center, it will take another week. Deployment usually requires two to three people. We involve the infra engineer, the database engineer, and a solution architect.

As for maintenance of UiPath itself, there are updates that may impact a solution and we will need to upgrade the packages, for example, legacy Windows. UiPath updates very frequently, and they don't support the earlier products. Officially, they are not supposed to support three of the versions. That means customers have to update within a year or two years.

UiPath solutions fit European and American clients, but especially for medium- and small-sized businesses in India, the cost may be the one factor that constrains customers. That's especially true when it comes to AI and ML solutions. It would be helpful for small and medium businesses if there were a reduced level or some kind of modified licensing.

On a scale from one to 10, where one is cheap and 10 is expensive, UiPath is an eight or nine for the region that we work in. But in other regions, it is somewhere around six to seven.

The solutions we provide to clients to automate their business processes need maintenance. They can usually take on a few processes on their own, but if it goes beyond 10 processes, some level of bot admin is required.

We don't need a proof of concept for a product that has been on the market for a long time. In the past three or four years, UiPath has been a proven solution. Customers can rely on the solution. We just have to make sure that their requirements can be met by the solution, and the other aspect is the cost. If these two aspects are taken care of, we can recommend that people go with UiPath.

UiPath is one of the leaders in RPA technology, and we get more business from it. Customers either want UiPath, Automation Anywhere, or Power Automate. But most of our business is with UiPath. They keep on updating it and are building their own RPA ecosystem. That makes it very easy to convince clients to stick with this one platform for multiple solutions.

We use UiPath to automate processes.

Users who are not proficient in programming can still use UiPath.

UiPath makes it easy to build automation because it can fully integrate with third-party applications.

UiPath enables us to implement end-to-end automation, which is crucial because it allows us to focus on other aspects of our work rather than dealing with repetitive tasks that can be exhausting.

It helps to eliminate 70 percent of our human error by automating routine tasks and enabling drag-and-drop activities.

The UiPath User Community is helpful.

UiPath has helped our organization improve by saving us 80 percent of our time through automation, which is vital to us. We no longer have to manually manage hundreds of lines of code and it simplifies our work.

I would rate the Academy courses eight out of ten. The courses are good, but I would like more of them.

UiPath has helped speed up and reduce the cost of our digital transformation.

The automation and the customization of the platform are the most valuable features.

I would like to see improved support and cost management for advanced certification. The cost is too high for many people to afford.

I have been using UiPath for three years.

UiPath is an unmatched platform for robotic automation services. One of the most stable and up-to-date databases to automate and reduce workloads for organizations.

It is scalable.

The technical support is good.

Positive

The initial deployment was neither complex nor straightforward. It required around 15 people and took two to three hours to complete.

UiPath is reasonably priced.

I would rate UiPath nine out of ten.

UiPath allows me to create automation solutions that are perfectly adapted to my business needs, making my work more efficient.

Fifteen people in our organization use UiPath, and they are also responsible for maintaining the solution and ensuring that it is up to date.

UiPath is used remotely within our organization.

I recommend UiPath to others as it truly saves organizations a lot of time.

We use UiPath to automate routine tasks in our organization.

Building automation using UiPath is easy.

We have used UiPath to automate sustainable production tasks for some clients. The automation saved our clients time.

The UiPath user community is a place where we can learn more easily.

Since implementing UiPath, it has saved our clients a lot of time.

We can use UiPath Academy courses to learn about the product and apply that knowledge in our organization.

The AI functionality in UiPath enables us to easily improve our more complex automation processes.

The AI functionality has helped us automate more processes.

UiPath has helped reduce human errors by 90 percent in our automation.

UiPath has helped free up 50 to 80 hours per week of employee time.

It has helped us reduce costs by 80 percent by automating routine tasks.

Integration with third-party tools, machine learning models, and document processing are all valuable features.

The price always has room for improvement.

I have been using UiPath for two years.

UiPath is stable.

UiPath is easily scalable.

I previously used Microsoft Power Automate. Although both tools are popular, UiPath is easier to integrate with third-party tools and more accurate.

The initial setup is straightforward. The deployment took one and a half hours.

UiPath's cost is moderate.

I would rate UiPath a nine out of ten.

The maintenance required is minimal.

We have UiPath deployed in one location.

I recommend UiPath.

We use UiPath to understand and refine supply chain business processes. Our company is a solution integrator developing solutions for clients. We help companies undergo a digital transformation and digitize existing processes and systems.

You can monitor and automate existing processes, but it's challenging if there's a skill involved. You need to optimize the process and ensure the system is fully integrated. You're pushing the data into UiPath and optimizing the process. You want to integrate it with another system that isn't part of your environment or improve your process. In that case, sometimes you don't have the data in place. That is what you call process mining or process automation.

If you want to understand the processes you have in place, UiPath can help you understand the gap between the design and execution. For example, you can see if the data is pointed in the right direction and identify where your process has problems. You can also integrate some monitoring capabilities to detect some patterns. 

Another important thing for our organization is migration. If you want to change something or relocate a process, you can measure and transfer those things. If the method you want to migrate isn't in place, you need to create something from scratch that currently lacks support. UiPath is suitable for detecting and monitoring existing processes but is not good at identifying new flows, cases, and procedures. That's one area where it needs to improve.

UiPath helped minimize our on-premise footprint. We use AI for some aspects, such as detection and segmentation. Some companies implemented ChatGPT-type functionality, but we haven't tried that. 

UiPath substantially reduced human error. It speeds up the business. You can communicate with the customer and show them what's happening. That's the advantage. It frees up employee time because it's an automated process, and you can replace a lot of labor with the tools and the general report. It depends on the data and the efficiency of the data integration, but you can save 20 to 60 percent of labor time.

I like how you can download the log and perform static analysis. You can also do dynamic monitoring to look into the system integration. The ease of building automation depends on the vendor you are integrating. You bring data in and push it out through the API. It's relatively easy either way. 

The UiPath community is helpful because you can ask questions and get tips from other people on best practices. Many of the problems have already been resolved by others so you can get advice from those people. You can also see how other people use the system. 

UiPath could add more interactive features that enable you to explore and design processes from scratch. There should be more features that support the digital transformation process from the design phase. In the current data panel, you need to start with a process that's already in place. 

You can do end-to-end automation with UiPath, but the problem is that the system hasn't been integrated from that perspective, so UiPath has some disadvantages. It's easier to handle an existing system in UiPath, but it's harder to integrate and model a new system. 

I have used UiPath for about a year. Before I started using UiPath, I was involved in developing these kinds of processes for more than 10 years, so I'm experienced in this area.

Deploying UiPath is straightforward. We had a team of two people primarily responsible for the deployment and one or two additional staff. 

We worked with UiPath during the deployment. They have a consulting team that we use when possible. 

The real ROI comes in the later process monitoring stage. You need to spend money initially planning and building processes. Once you get to the evaluation phase, you start to recognize the advantage of using these tools.

Most tools have a trial license. With UiPath, you need to pay from the beginning. Many customers aren't familiar with the product, so it would be helpful if they offered a free evaluation period. 

We need experience with UiPath because we have to convince the customer to adopt it.

We evaluated several other options, but I can't recall which ones. UiPath's advantage is that you can do system automation. 

I rate UiPath an eight out of ten.