UiPath Platform Reviews

We use a feature called Document Understanding to extract data from invoices and generate reports. It uses the invoice number, amount, line amount, description, addresses, remit address, and other fields. This is the current project I'm working on. I'm using all the features available in UiPath to train the invoices to identify all the fields. Then, I deploy the training, create a pipeline, and use that ML skill in my coding while developing a project.

We are doing this for our team talent payments team. They usually receive different invoices from vendors for various reasons. My company currently has 700 vendors listed. These vendors send invoices for their services, and the talent payment team used to fetch and extract the data manually before we started working on this project. Whenever they received an invoice, they would open it and write down the data.

We have now completed phase one of the project and are in phase two. For this process, the bot will receive all the invoices and extract all the data needed by the team. We will then create a consolidated report in Excel for each vendor and present it to the talent team. This automation saves the talent team time. In addition, I have used email automation, Excel automation, API calls, and UI automation in this project.

We deploy UiPath on-premises, cloud, and hybrid environments depending on the organization's requirements.

Building automation using UiPath is really easy. Studio is a drag-and-drop environment with different palettes, search options, and simple properties, inputs, and outputs. It doesn't take much effort to develop a workflow in UiPath, even complex ones. UiPath also has recorders, so we can perform our actions and start recording before we perform them. UiPath will then develop the workflow for us based on our screen actions.

UiPath enables us to implement end-to-end automation, which is important to me from an analytics perspective. It makes it easier for us to provide solutions to businesses, regardless of their requirements. With UiPath, we can keep manual interaction to a minimum, from providing input to getting output. UiPath apps and interactions also make it easier to automate processes. In the past, people would develop scripts to automate tasks, but they had to keep in mind that there would still be some manual work involved, such as preparing an input file. With UiPath, we can minimize this manual intervention and prerequisites. This is a significant advantage.

Everyone on our team uses the Academy Courses when they start using UiPath, and whenever a new feature is added, we search the course list for the updated courses. The biggest benefit is being able to learn UiPath directly from the developers, rather than from a third party. When we learn from a third party, they have to learn UiPath first, and then try to explain it to us based on their own understanding. But when we learn from UiPath, it's like a personal experience, because they developed the product and know how it's supposed to be used. The other great thing about the Academy is that it's very interactive, with question-and-answer sections and plenty of resources. For example, they provide input files so we can try out new features. All in all, the Academy makes it really easy to learn UiPath. We just have to take the startup course, and they explain everything through videos, interactive sections, questions, tests, and data flows.

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

It also helps reduce human errors in the normal processes that we develop.

UiPath has freed up our employee time. For example, in the onboarding and interview processes, our organization may have many people applying on any given day. Sorting through applications was done manually, but with UiPath, the process has been significantly sped up. UiPath now performs all of the tasks, such as getting candidate details and making consolidation reports for the hiring team. Overall, UiPath has saved us a lot of time and effort, and it has been a great return on investment.

The most valuable feature is the document understanding feature of this current project, which is better than ABBYY FlexiCapture or Automation Anywhere. It can learn on its own, given enough instructions and data. With training, we can actually train it to recognize the specific fields on invoices that we want. For example, UiPath can still provide information from a few of the invoice fields without training, such as the invoice number and date, which are present on every invoice. However, some vendors have specific fields on their invoices, such as the candidate name, job location, or start date, which we can train UiPath to recognize. This gives us the ability to train UiPath beyond the common things, if we are looking for any specific information or if we want to personalize it for a vendor. We are then able to use this trained model in our code, which is very helpful.

I also like the Excel automation feature. UiPath has recently updated the Excel activities package, which gives us more options with a more modern look and feel.

I find the features UiPath provides to be excellent, but the documentation is difficult to maintain. I have noticed that it can be difficult to find information on some features in the UiPath documentation portal. The document portal needs to be kept more up-to-date. UiPath will release the new feature, but the document portal will still have the older version information. The documentation portal could be easier to navigate if it were redesigned to make it easier to find information about a particular feature. It would be great if the portal were updated as soon as new features are released.

I have been using UiPath for almost three years.

We have occasionally observed some abnormalities, but we have not yet found the cause. For one of the processes, we are running macros and triggering them with UiPath. These macros can take ten to eleven hours to run. Sometimes, UiPath stops while a macro is still running. Once the macro is completed, UiPath is supposed to perform another task, but the macro takes so long to run that this does not happen. I believe this is a problem with our program, as it is taking too long to complete. These kinds of delays can occur, and that is understandable.

There are many areas where support can improve. However, it is not that bad. In terms of sticking to schedules, they are available quickly and listen to all of the problems. Sometimes, we have hit roadblocks because the people assigned to solve a particular support ticket did not have any idea about the feature. This has caused problems for us, as we have had to spend time filling in another person who actually had the knowledge about that feature. We have run into this problem a few times. 

Our organization previously used Automation Anywhere, a script-based RPA tool. The fact that we moved to UiPath suggests that we wanted to change products for a reason. We must have heard that UiPath is better than Automation Anywhere in some way, which is why we made the switch.

We have seen a good return on investment.

I would rate UiPath seven out of ten. UiPath has a lot of features they are working on but they take a long time to enter production.

Maintenance for UiPath is minimal. Small things such as changing the passwords because of the password rotation policy. We maintain our bots through VMs that run on AWS.

I recommend UiPath because it is a low-code/no-code solution that can be used by non-technical people. The Academy courses, which train users specifically on how to use the tool, make it easy to develop and automate processes. UiPath also offers a community version that includes most of the features of the paid version. Earlier in my career, I learned to use Blue Prism, which is a closed-source solution that only had basic courses available in its academy. It was difficult to use compared to UiPath, and it was hard to get any information on any forum or from its academy on how to use the tool and update it. In terms of learning, use, and understanding, UiPath is much easier than other solutions.

I'm using one or two robots. We use the solution for reports. We have another software yet we don't have support. Instead of pulling reports manually, we use the program to get the reports and pull them for us. 

The solution is very simple. We can easily create robots. It's easy to build automation.

UiPath enables us to implement end-to-end automation. We have some manual procedures and it helps to complete those tasks. 

We use the UiPath user community. It's free. 

The amount of work we have is very small. We don't have big workflows. However, employees can now spend time on other things, and it's helped us manage our time around reporting.

The company has helped us minimize our on-site footprint.

We've used Academy courses. I've done classes myself. I don't use it every day. I've only used it once, actually.

The solution speeds up digital transformation and reduces the cost of digital transformation. with UiPath, we do not require expensive or complex application upgrades or IT application support.

UiPath has helped reduce human error. It has also freed up employee time. It has saved about 20 to 30 hours or so.

I've dealt with compatibility issues with Microsoft components. When we upgrade the UiPath framework, we might be able to fix the issue. 

We'd like the accounting team to be able to have improved data out of SAP. 

I've been using the solution for one year. 

The product has been stable.

It's a scalable solution. We have about 150 people using the solution. We may increase the usage in the future if we have an opportunity to apply more robots. 

I haven't worked with technical support.

I did not previously use a different solution. 

We're using the 2023 version of the solution. 

I was involved in the implementation. 

The setup was straightforward with the help of UiPath documentation. The implementation process took less than one day and we implemented with one or two people doing the work.  

UiPath does require a bit of maintenance, however, it is not that much. We're mostly just dealing with compatibility issues with Microsoft. 

We deployed the product ourselves. 

As for the cost, I'm not sure if it has saved us money. The customer still keeps the same number of employees, for example. That said, the important thing is to reduce the time it would take for them to handle tasks. In some ways, it's done that.

Our use case is still very small. Therefore, we don't want to buy a solution that is too big for us. We don't want to pay more than $10,000 USD for a license. Therefore, we're focused more on the community version. 

We did evaluate other options. We found UiPath to be more localized. They were one of the top solutions.

We are UiPath partners. 

We do not use the solution's AI functionality just yet. We're only using small automation. We also have yet to try the document understanding features. We still need to try some advanced features and I look forward to experimenting with it.

I'd rate the solution eight out of ten. 

I would recommend the solution to others who need to create automation. 

Our use cases are generally related to front-end UI-based automations that emulate tasks done by teams. For example, we do front-end SAP automation for data entry and scraping or posting data to websites that are related to the organization. We use UiPath for other automations like extracting and manipulating data from Excel. The primary use cases are in finance, HR, and operations. In logistics, it's used in full-sprint solutions.

UiPath's ability to do end-to-end automation is crucial. If we do the automation in bits and pieces, it's challenging to integrate it. The best part is that the turnaround time is drastically reduced because the process isn't being put on hold in between two manual interventions. The more permissions we apply, the more we reduce the turnaround time. However, the smaller automations don't impact the turnaround time that much. If the logic is set correctly, it can completely eliminate human error. 

The UiPath community development forum is helpful. Developers can access all the information they need if they get stuck. For our use case, we refer to OpenMedia, not any particular program. To understand what are the RDP use cases. I personally follow primary and secondary research forums as well as McKinsey's technology consulting newsletters and documentation.

The UiPath Academy explains various use case scenarios through videos and training sessions. It's all practical, hands-on instruction instead of purely theoretical. That made a significant difference by increasing our confidence in the product and ability to create our own automation. You can track each team member's training steps in parallel because everyone needs to be on the same page.

Uipath doesn't necessarily reduce our on-premise footprint. We use UiPath to automate configuration integration, so I can't say there is any direct impact because RPA is now just part of our on-prem ecosystem. The solution doesn't require expensive or complex application upgrades, but certain applications need scripts to be enabled to get UiPath working on their front end.

It saves time, but the amount varies. Each process has a different impact depending on the frequency of that process. If a process is running daily, the values are high, but sometimes it's low. The organization aims to have one bot per person, so everyone has one attended bot that can replicate their monitor network. It's the equivalent of adding one FTE per year by default per person. Every person can have a bot, scale up the work, and get more done in a day. 

The amount of money saved also depends on how often the process runs. We pay per bot, so if the bot isn't running frequently, we might not save any money. However, if the requirement is to do many more tasks than a single person can handle, it makes sense to use a bot, and we can save a lot of money that way. Sometimes, we have different goals beyond just saving money or reducing the time that our staff members spend on tasks. We might deploy a bot to improve the user experience and save the user some time. In some cases, we might not see short-term savings, but we'll see a benefit from it in the long run as the process volume increases.

The feature I like the most is ONEWEB UI automation. UiPath's OCR technology also works well. There is another feature called Action Center that lets you decide what happens after the data is captured. It passes the data into Action Center, where a person can review and approve it before it goes to the next step. It helps us manage our attended bot processes.

It's generally easy to build processes because of the drag-and-drop configurable suite. However, more complex expressions may require some kind of functional coding. UiPath also has some prebuilt functions in its training module that can be utilized to enter the expressions and get the job done. That's one workaround.

UiPath's built-in integration with Python scripts could be more robust so that I do not have to depend on another technology and I can do everything on one platform. 

Each program you write on UiPath contributes to bot consumption and utilization. As you add more bots, your costs will increase for more actions. Python is open-source, so it is totally free. Depending on our automation needs, we go back and forth between these two technologies. Better integration between these two tools will help organizations cover all areas of automation without more cost-effectively. 

I have used UiPath for approximately two years.

I rate UiPath nine out of 10 for stability. We haven't faced any challenges with UiPath's stability because it is a SaaS product. It runs on the UiPath cloud, and things are working fine. 

UiPath is fully scalable. I haven't faced any challenges in terms of scalability because the cost is not per user or per process. It is priced according to the amount of bots being consumed, so it all depends upon the complexity of your own project. If the complexity is lower you can reuse and share 

I rate UiPath support nine out of 10. They always respond with solutions within the time established by the SLA. 

Positive

We were working with Power Automate. It has benefits from a cost perspective. The cost per developer is much lower relative to UiPath. Power Automate is a more cost-effective solution for larger enterprises. However, UiPath has more technological capabilities, and it's more user-friendly for developers, which is why UiPath is being adopted more over Power Automate. At the same time, Power Automate is continuously improving, so it may reach the same level as UiPath in the future. 

We are using the cloud version of UiPath, which is hosted by the UiPath team themselves. We do not use a private cloud. The network configuration didn't take much time. The deployment involves setting up a UiPath account and configuring permissions. It is a SaaS platform like Office 365.

The deployment time is just the amount of time required to develop processes for the project. It depends on the size and complexity. A project with hundreds of activities might take a few months, but a simple project with only two processes can be done in a few hours. 

I rate UiPath eight out of 10. 

We use UiPath to automate daily repetitive tasks.

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

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

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

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

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

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

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

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

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

It has helped us save time.

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

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

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

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

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

UiPath needs to be more compatible with MacBooks.

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

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

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

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

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

I would rate UiPath an eight out of ten.

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

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

I recommend UiPath for Microsoft Windows users.

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

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

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

Building automation using UiPath is simple.

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

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

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

UiPath helps speed up digital transformation and reduce costs.

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

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

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

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

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

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

I have been using UiPath for two years.

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

I would rate the scalability an eight out of ten.

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

Neutral

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

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

One person can complete the deployment.

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

The cost for UiPath is affordable.

I would rate UiPath a nine out of ten.

Basic maintenance is required for UiPath.

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

We can't disclose our exact use cases, but we do intelligent automation with UiPath.

It reduces human error and most bots are able to generate 50 to 60 percent savings in terms of employee time. It's definitely helping our organization to save costs. We are able to do work at one-sixth of the cost. Even after adding an FTE for bot support in the back end, UiPath saves us significantly on costs.

The Task Mining is one feature that is very helpful to any business analyst. I do business analysis, and the info that I produce goes to our UiPath team to develop automations. Task Mining is the only part I leverage.

UiPath is pretty flexible and offers security aspects as well. It helps us do intelligent automation, providing multi-language support. It can also integrate with any kind of application, such as Java or legacy-based applications. We can call APIs when needed, and it can be scheduled. We can even manage UiPath licenses for multiple uses.

It has certain built-in Excel features, so if you want to pick data from Excel or crunch data in Excel without using Excel macros, you can use UiPath and take that data to any type of ERP application. In that way, it's quite flexible. It has very good features that help you process data across different technologies and platforms.

The UiPath Academy courses are also very useful. I became certified in UiPath business analysis training, and have also done UiPath technical architect courses. It helps you kick-start your career in UiPath. It's very helpful.

UiPath helps with digital transformation at the outset, but I focus on the amount of runtime support needed for managing bots. If a bot is going to save four to six onshore resources, at least one offshore resource is needed to support it. That is one area where UiPath, Automation Anywhere, and every automation software has to focus. A lot of bots are highly sensitive. Even the slightest change in screen behavior or a small change in the process and, many times, they are not intelligent enough to run on their own. That means there is a high level of dependence on the support team. Automation software providers need to improve on this.

Also, UiPath could bring in a type of low-code or no-code automation so that it can be used by the masses instead of only by technically proficient people to develop solutions. Low-code or no-code automations would be really helpful. 

In addition, for intelligent automation to become really robust, a lot of features need to be added, and the accuracy of the model has to be improved. Right now, if I am going to implement any UiPath or AI solution, in the beginning, it will only be 30 to 40 percent accurate. It doesn't get to 70 to 80 percent.

These are the types of things that need to be improved in UiPath.

I have been using UiPath for between six and seven years.

It is a stable environment. It doesn't encounter any errors on its own, unless there are system or functional exceptions.

It has good scalability. We can even redeploy an existing use case to a new use case. Or when a new migration takes place, we can use UiPath by modifying it and making it work in the new enrollment.

Our support team handles technical support. I haven't contacted them.

The price is reasonable, although Orchestrator is really costly. Not many organizations will be able to afford that, but without Orchestrator, you can't do bot management. It becomes pretty difficult. UiPath has to focus on orchestration pricing. They need to bring in some innovative pricing.

From the business analysis angle, refine your use cases and make sure you are identifying the right ones, before deliberating about any automation platform, whether it is UiPath or not.

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

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

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

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

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

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

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

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

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

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

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

The Studio and development boards are also helpful.

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

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

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

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

I have been using UiPath for more than five years.

There are no issues with the stability.

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

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

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

I've been using UiPath for around a year.

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

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

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

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

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

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

Positive

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

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

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

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

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

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

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

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

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

We are a financial services company, and our primary use is to increase daily efficiency and create automated solutions for our operations team. Our primary concern is time. By implementing a robotic solution for mundane tasks, it frees up our teams to focus elsewhere. For example, going to a website, extracting data, putting the data somewhere, and manipulating it can all be automated, freeing up the team to focus on data analysis. This makes us more time and cost-efficient. 

As a smaller company, it was very important to us that scale automation would be taken care of by the vendor. It was one of our key points in choosing a solution.

The solution saved us a great deal of time and money, while teams have been freed up to focus on more important work.

Human error has been greatly reduced and the solution saves a significant amount of time, these are the two main reasons we started to use UiPath.

The solution helps us to keep track of tickets and send notifications used within our department. It helped a lot with our back and front-end offices. Our main operations team normally had a lot of data manipulation, which is now taken care of. They can now focus on market analysis.

This product is very user-friendly, it only requires knowledge of the most basic coding and how to work with logic. They are quick to respond to software issues. They either fix them quickly or provide a workaround if there is one. Overall, UiPath makes building automation very easy.

We do use the solution's Automation Cloud offering. Sometimes we aren't informed of software updates, meaning we have to figure that out for ourselves, especially when there are issues. We mentioned this to support, as figuring out solutions to issues brought in by updates sometimes increases our workload. Overall though, I would say the solution does save a lot of time for our IT department.

The solution has increased our TTV significantly.

The Automation Cloud offering decreased the solution's TCO by taking care of infrastructure, maintenance, and updates. 

We used the Automation Cloud to build out our own pipeline and connected it to Azure. This has really solidified our SDLC, which in turn allows us to quickly put out automations whenever we need to. 

My team and I used the vendor's UiPath Academy course. The course was very effective, as none of the team had prior UiPath experience. We trained using UiPath Academy for around a month, which got us to a point where we could start to use the solution for projects, which helped us learn even more.

The community is much larger than I expected. I'm regularly on the forum or the community blog, which says a lot about how good it is, because almost any information you need can be found there. Everything is well documented, there's always UI path support, and people answer questions on there, so it's very useful.

Since UiPath is one of the bigger vendors in the RPA industry, there's a larger global community. Everyone is really helpful and I think that's great.

Technical support could be improved.

The setup documentation could be improved to make that process easier. 

We have been using the solution for two years now. 

I'd say the solutions are around 80 to 85% stable. There are some areas that we have to reach out to support for, and they work to improve these areas for the newer versions. For that reason, I can't say the solution is 100% stable all the time. 

The features provided by UiPath make it very easy to reuse, so it's very scalable.

We haven't deployed the solution to its full potential at our company yet. It's used by nine to ten teams out of a total of around 200 teams. We have a lot more to do, as we only started two years ago. We are working towards implementing for more of our teams, but we need a bigger team to push out solutions faster. 

The technical support is inconsistent, it can be good or bad, this depends on who you get connected to. 

Neutral

It was before my time at the company, but I believe they previously used Nintex RPA.

I wasn't there for the initial setup, but I do know quite a bit because we did have to set up more bots later. I'd say it's a little complex if you don't already know what to do, but once you do know, it's very easy to set up. I would say the documentation wasn't that clear.

We're a small team that consists of two developers, one tester, and a manager. This is sufficient for the deployment and maintenance of the solution.

We implemented the solution ourselves.

I would say the cost of the software is around 10K and we've had around 50 projects, with probably $500,000 saved per project. That's a lot of money saved that can be diverted to other areas.

The solution has sped up and reduced the cost of digital transformation without requiring expensive upgrades or support. The product has greatly reduced the incidence of human error.

The solution has saved us a lot of time. I would say it saves us an average of 900 to 1000 hours per month. The additional time has enabled employees to focus on more high-value work.

Overall, the solution has reduced the costs of our automation operations.

The cost of the software was around $10,000.

I would rate this solution an eight out of ten. 

The solution builds robots and monitors automation. There is a product called UiPath Task Capture which can do process analysis or business analysis, but I would say it's always better for a human to take care of this. For that reason, I wouldn't say the solution is end-to-end, though we could configure it to be. I would say it works very well from building to the end, and in the testing and monitoring that comes after that. 

We used unattended automation and quickly realized we need attended, because with unattended automation projects take up a lot of time. With unattended automation, we can't run two project processes simultaneously, but with attended automation, we can take out another server and give access to the UiPath cloud to our business partners to run whatever projects they need. We can do this at any time, which is very helpful.

RPA generally isn't widely used, and some people overlook it, but it can transform a business. I would say it's an essential part of any digital transformation, and UiPath is a vast vendor with a user-friendly product. 

I am an RPA developer and I work with UiPath in that capacity.

Our current use case involves the automation of a process involving healthcare-related data. This is confidential data that is received from the customer and inserted into Oracle forms. Reports are then generated from it and these reports are then used by the organization, which is in the healthcare domain, for their analysis.

The data being analyzed includes medical and treatment history. For example, with the current pandemic going on, there are all sorts of healthcare data that is related to it, including various types of treatments. When somebody walks into any clinic or hospital, all of the treatment is entered into a database and we get an extract of it. The analysis is used to get more details.

Another interesting use case, prior to this one, involved the documenting of invoices. We were working with approximately 250 different samples of purchase invoices, many in different formats. One might be a native PDF file, whereas another could be a scanned PDF, and yet another might be a simple handwritten invoice that was converted into a PDF based on a picture that was taken from a mobile device. We were receiving these invoices from our client and they wanted to extract data from them. It was accomplished by using the Document Understanding features in UiPath.

The other notable use case had to do with issuing refunds for purchases that were made on an e-commerce site. When a customer made an order and there was a problem that resulted in them wanting a refund, there were multiple ways that the client could request one. A refund application could be received by the customer care department in the form of a simple call, which was a verbal request, or as an email written by the customer, or as an automatically-generated email that was created based on filling out a form on the website.

Regardless of which of the three input methods is used, the refund request is gathered and sent to a mainframe application. At that point, the information is extracted from the mainframe and the refund is issued using another application.

The automation of these tasks using features such as artificial intelligence and document understanding has reduced our costs. For example, with the invoice processing use case, there was a team of between 20 and 25 agents who were doing it manually. Obviously, a team of that size has a large cost associated with it. Also, the volume was very high, which meant that the team was not able to deliver on all of the work. There are approximately 250 vendors sending invoices to our customer to process the data, which translates to about 1,000 documents being sent on a daily basis, to be processed by only 25 people. It was a huge task. With this level of volume, people tend to get frustrated. 

We implemented the automation and the team size has now been reduced to only five or six people, and that is only required to monitor the bots. For example, they check to make sure that the data being fetched using document understanding is at par. We have set the minimum confidence of the documents being scanned at 90% and each day, a report is generated and sent to the customer. Overall, it was a very cost-saving implementation.

When it comes to building automations, it's pretty simple. UiPath has a lot of features, starting with Process Mining. For example, when a business person wants to start from scratch, they don't necessarily know which process to automate. They can use the Process Mining feature available in UiPath to get an answer as to whether a particular process is worth automating or not. Features like this are available to shorten the processes. Once a process is identified, we can go ahead and implement and develop the automation. Overall, it is very easy to develop automations because of the inbuilt features.

UiPath provides us with features to implement end-to-end automation, and it begins with the initial steps. They have Process Mining or task mining features to help companies that have an appetite for automation but don't know what they want to automate. Once a process analysis is completed, it can determine whether a process can be automated or not. At that point, we can proceed to the bot development.

Once the bot has been developed, there are different options, including third-party support, for deploying them. After a bot has been deployed, they have the hypercare facility to monitor and maintain bots that are in production. Taken together, all of these features facilitate end-to-end automation. This is very important to our work. 

Consider that UiPath did not always have the Process Mining feature. In those days, in order to do process analysis, companies had to hire Subject Matter Experts (SMEs) for different domains at the beginning of a project to determine which processes could be automated. For example, if there were a requirement for a healthcare process then the company had to hire a healthcare SME. The SME would assist in process analysis and in the determination of whether it was something that could be automated. Nowadays, with the help of the Process Mining features, we no longer have to worry about who is doing the analysis.

From our standpoint, we have to do the recording and supply the inputs. With this, a report will be generated and it will tell us whether the process can be automated. If so, then the developers or an architect will come in and do the development. Following this, the DevOps team will come in for the deployment. Finally, the production support and monitoring are taken care of by the developers.

Using the cloud-based deployment helps reduce our on-premises footprint because we no longer have to take care of servers and local databases. There was a separate team taking care of the networking aspect, and another team taking care of the databases. For on-premises deployments, there are different teams that come into play, whereas with a cloud-based solution, we don't have to worry about anything. UiPath takes care of deployment and the databases, and everything is automatically handled. I can't estimate an exact percentage of how much our on-premises footprint has been reduced, but it has really made a significant impact in terms of substituting or replacing the on-premises facilities.

Attended automation has helped to scale our RPA benefits and in fact, in my almost five years of experience, I have not come across a scenario where the automation could be purely unattended. In the use case with the invoices where we used document understanding, there was still a minimally-sized team of five people in place after the implementation. They monitor the processes and if the criteria of 90% are not met then the invoice will be rejected and sent back to the vendor. In this case, attended automation is really helpful.

The Automation Cloud saves our IT department time because we don't have to worry about hiring different teams for different tasks. The infrastructure maintenance is handled by the vendor and all we have to do is pay for our licenses, then everything is ready.

Automation Cloud has helped to decrease our time to value. You don't have to worry about how the installation is to be done, you just have to pay the license fees and the team will do everything. They have packages, and you just have to give them the numbers according to what you need. Based on that, they will propose a solution and propose an infrastructure for you. Once that is agreed, they will do the installation within a very short time. After that is complete, your developers can start doing the development and within no time, you will start seeing the ROI.

The Automation Cloud has indeed decreased our overall costs.

It is really helpful for an organization to use the Automation Cloud when they do not have sufficient resources available themselves. In situations like this, the UiPath Automation Cloud plays a very important role. You just have to give them the number and they propose the solution including the infrastructure. You just need a few developers and everything else is taken care of by the Automation Cloud team.

We have a lot of clients who are looking at digital transformation, but they don't know what tool to use. There are a lot of vendors available in the market who provide products that are similar to UiPath, but UiPath has a lot of very strong marketing, a strong sales team, and at the same time, the product is very good. UiPath helps in doing quick installations, quicker deployments, and quicker turnarounds. Ultimately, it really helps with digital transformation for any organization.

Digital transformation requires an upgrade, but it is not very complex and not very costly. A company may have to be 25 to 30 million dollars to upgrade, which is a significant cost, but if it saves 100 million then in the end, the organization is saving money.

UiPath has helped to reduce human error to a great extent. When humans perform the same task over and over again, we tend to get bored and frustrated. Our excitement goes down day by day. However, when it comes to machines or bots, they don't get bored and they don't get frustrated having to do repetitive work. This leads to fewer errors, which has a positive impact on the business. There are fewer escalations and the customer is happier.

Our automations have helped to free up employees' time by reducing how long it takes them to complete their tasks. It leaves them time for learning or performing other jobs, and in general, it helps to reduce work hours. I estimate that percentage-wise, it saves my team between 30% and 35%. The total time saved is approximately 250 hours per month.

One of the ways that our employees benefited from having time freed through the use of automation is upgrading. A lot of people, in particular our technical staff, upgraded by learning new technologies. This ultimately led to helping the organization because they are able to work on different jobs.

Automation also leads to an improvement in employee happiness. If you ask them to do the same thing over and over again, on a daily basis, they get bored. When 30% of the time is saved by using automation, it frees up perhaps two hours a day for them to do different work or even recreational activities. 

UiPath contains a lot of very useful features.

The artificial intelligence and document understanding features are very good and have been helpful when it comes to processing handwritten or unstructured, especially when there is a high volume and it is repetitive. 

Using the artificial intelligence and machine learning features had a drastic impact on our use case. In the scenario where we used document understanding, we were able to successfully automate the use case without artificial intelligence. However, there was not a sufficient improvement. The success rate was between 78% and 80%. We did not use these features originally because they come at an extra cost and we did not have approval. When we were given approval and acquired the licenses, we re-implemented the automation and included the inbuilt AI and ML models. Our success rate went up to between 92% and 93%, which is significant.

The Orchestrator is in drastic need of improvement. Three or four years ago, the Orchestrator UI was very simple and comfortable to use but now, they have added so many features that it is difficult for new users to quickly understand it. The latest implementation that we did was so complicated that nobody was able to understand it, aside from the developers. Generally speaking, UiPath needs to improve the interface, and the overall user assistance should be boosted.

The developers are the core users of the product and it's important to make the product easy for them to use. The easier it is, the more people start using the tool. Then, as there are more developers available, more organizations start to hear about RPA tools and Uipath.

I have been working with UiPath for approximately four and a half years, across three different companies.

I have found that one or two times out of ten, UiPath Studio hangs and needs to be restarted. These types of technical glitches do happen but not often.

In the organizations that I have worked in so far, the UiPath features and the licensing available meant that we didn't have to worry about the infrastructure setup or scaling. You can start with a small number of licenses and robots, with little infrastructure requirements, and gradually, as you need more robots and more powerful infrastructure, you can scale up. It has great scalability. 

Even if somebody is using the community edition, we are able to build a PoC for them. In fact, using this approach gives us a pretty good idea of how the automation will proceed. Based on this, we get an idea of what the infrastructure will look like. Then, if everything fits into the customer's budget or request, we will go with the enterprise edition and implement the solution. Throughout the process, scalability is not an issue.

In my department, we have between 70 and 80 people working with UiPath. Out of these, 80% are developers, perhaps between 10% and 15% are business analysts, and the remaining people are solution architects or tech leads.

We use UiPath extensively because it helps with quick implementation and a short turnaround time. Deployments are very quick and easy to do. Given the current pandemic situation, I don't see the demand for UiPath or any other RPA tool going down.

I have been in contact with technical support many times and they are very good.

The issues that we typically face are related to Studio and sometimes licensing. The support has a fast turnaround time and if the organization is large, with a lot of licenses, then they have dedicated support for them. It is not necessary to deal with customer care, for example. Instead, dedicated technical support is available and they are really good.

The companies I have been with did not use another RPA tool prior to UiPath.

As a developer, I have not been directly involved in a UiPath installation or implementation. It's generally the responsibility of the implementation team that every organization has, and developers don't have the authority to simply download and install or implement UiPath. That said, I have given my input in the past.

Every company has a QA team and once they identify and finalize which automation software they want to install, the implementation team takes care of it. In my experience, the developers are given an instance of it to use after this.

It used to be a very simple installation, although, as I have seen UiPath change over time, it has become very complex. They have now Studio versus Studio X. They also have the Automation Cloud, which is different from an on-premises deployment. Somebody who is new to UiPath will not be able to do anything.

In terms of how long it takes for deployment, it depends on what process you want to automate. A very simple process can be automated, end-to-end from process analysis to deployment, in about a week. Complex automations have been taking us between six and eight months to complete. It all depends on what kind of automation you are doing.

In general, the implementation strategy is simple. Again, it depends on what kind of process we are automating. If the process is very complex and it involves a very high volume of data to be processed and stored, then it will require greater network bandwidth and more database storage. It may also need a fast server, with regards to processing speed. 

All of the implementations that I have seen have involved an in-house team. There are different departments involved, such as the networking team, the database team, or the IT department. Also, for the latest implementation that we did, involving Automation Cloud, the UiPath team helped us.

UiPath has reduced our overall costs. For example, if you are replacing 25 to 30 humans, where instead you only have to pay for licenses, the expenses are much less.

The company and our clients see a return on investment through savings in time and costs.

There are different licenses available, including variations for an on-premises versus a cloud-based deployment. For example, an on-premises installation is very easy and not very costly, and is suitable for a client with a simple optimization that does not have cloud-based requirements. Generally, companies do not have to worry about infrastructure because of the different options that are available.

Different licenses are used to activate features that the organization wants to use. For example, they offer licenses for UiPath Studio X, attended automation, unattended automation, document understanding, and so forth. They also have customized licensing and packages available. For example, if a customer requires 50 attended and 150 unattended licenses, but it does not fit into an existing package, then UiPath will create one for them.

They have an on-demand, floating license available for companies to save on costs. In this case, if a company wants 40 licenses and is only using 10 at a time then they only have to pay for the ones that they are using, with the remaining 40 triggered only when requested.

There are other automation tools on the market, such as Automation Anywhere and Blue Prism. Of these, UiPath is very strong and this is because of the UiPath academy for training, the UiPath certifications, and other things that impact the RPA developers.

The company that I am with did not evaluate other products before choosing UiPath.

Over the time that I have used it, the number of resources available in UiPath has grown to a very high level. For example, with the advent of Automation Cloud, the organization no longer has to worry about protecting against on-premises failures.

I have used the UiPath Apps feature but have not yet put it into production. I have completed a PoC and done some self-learning, but I haven't yet come across a scenario or process where we have to implement it.

We completed a proof of concept where our client was looking for customized input forms for their client. In that case, if I had to write the code for this customer's input form, I would need to hire additional resources at an extra cost. It might be, for example, code that has to be written in Java. In UiPath Apps, we were able to create a customized form for our client within a span of two to three days. It would be able to handle their various survey-related inputs. This feature is very helpful because it is much quicker than writing customized code for the client.

The Apps feature did not affect my IT department's workload but it did reduce the work required by my team. This was important because our client was not originally seeking to use UiPath for this part of their project. Instead, they had confidence in us and asked how it could be done, and whether Uipath could accomplish it. When we completed the input form using Apps, it definitely helped in reducing my organization's workload and in turn, reduced the overall cost to the client.

In summary, the features are very good and there are plenty of tricks and tips available, depending on what it is that you're trying to do.

I would rate this solution a nine out of ten.