My current retail organization uses UiPath for finance-related activities like invoice generation. We also use the solution for pulling documents from any stored devices for customers. We save customer files like licenses, invoices, and other tax-related documents in the box. If customers want to use such files for any purpose, we need to extract them from the box environment. A bot will check for that particular customer-specific file, download it, and save it in client-shared locations.

Transactional details regarding whether a customer has delayed an EMI or paid the EMI on time will be updated in the system. A bot we defined using UiPath will do it around the clock without any human effort.

The most valuable feature of UiPath is the complete queue system-based framework because it is robust for all clients. If something goes wrong, we can define how many retries we can do for a particular request. In the next attempt, it can be achieved in a proper way.

The end users can expect the results without any manual intervention. This framework is very user-friendly, convenient for the developers or system integrators, and satisfies the client compared to other frameworks.

I would like to see more clarity in the solution's AI functionality. I have not completely implemented AI for our client. I'm trying to understand the areas in which AI will be more usable for my client.

The OCR is the only area where I expect a little flexibility and improvement. If you try to extract scanned documents or photos using any native or Google OCR, you won't get 100% accuracy.

I have been using UiPath for more than five years.

UiPath is a stable solution.

UiPath is a scalable solution. UiPath is deployed in one location with around 5,000 end users using the solution.

I also have more than four years of experience with the Blue Prism tool.

The only major difference between UiPath and Blue Prism is that UiPath is deployed in the cloud, and now Blue Prism is trying to be deployed in the cloud. Other than that, I did not observe any differences between the two solutions. Both are good products in the market, and customers are happy with both solutions.

UiPath's initial setup is easy.

Around two people are needed for the solution's deployment and maintenance.

Our customers have seen a return on investment with UiPath and are happy with the licenses, pricing, etc. They haven't raised any concerns so far, and they're increasing the licenses based on the processes we are deploying.

I'm a system integrator and one of the lead developers of UiPath for the end customers.

I use UiPath in the banking and retail industry.

UiPath is deployed on the Oracle cloud.

I would recommend UiPath to other users. The users need to configure the environment in a better way. If an organization wants to utilize only four or six bots, it needs to plan ahead and consider how big it plans to grow in the next five years. Planning in advance would clarify how the organization needs to configure the environment and what challenges it needs to handle. That's a better way to start using UiPath as an RPA tool.

Even before the deployment, we gave an estimation to the end clients regarding what to expect after deploying the solution. We told them about the things they will be very comfortable with and the time interval they will take to know things. They are comfortable and 100% satisfied with the solution.

Overall, I rate UiPath a nine out of ten.

Currently, I'm working with the regular UiPath, but in the past, I've worked with UiPath for healthcare use cases.

My use cases for UiPath vary. I've worked with the banking, renewable energy, marketing, and publishing domains. The most recent use case was for data entry, where my company used SAP applications to create orders for the vendor.

My company also uses UiPath to automate processes that deal with courses, such as environmental, employee diversity, sustainable production, etc.

UiPath is set up in my current organization. My organization takes advantage of the vendor's offer for end users to build smaller automation, which is another use case of UiPath.

Automation through UiPath has improved the quality of work in my organization. Using UiPath helped reduce the overall turnaround time for repetitive tasks. Each staff member can devote time to new tasks or other tasks rather than spending so much time on repetitive tasks.

Implementing end-to-end automation through the solution is essential to the organization because it's cost-effective and time-saving. It also helps boost employee productivity because employees now have the time to learn new things, such as the trends in the market, rather than doing many repetitive tasks that give little value. All these make UiPath beneficial to my organization.

What I found most valuable in UiPath is that it's easier to set up than other tools. UiPath, as a vendor, also provides flexibility, which most companies find attractive in the solution.

I would rate the ease of building automation using UiPath as seven out of ten. The gap in my rating would be eventually filled as my company starts using more AI-based solutions. Overall, building automation is relatively easy in the solution.

UiPath enabled my company to implement end-to-end automation. You cannot automate all jobs or tasks, but the solution does at some level, so I like that it provides further flexibility to automate end-to-end.

As for the UiPath user community and its value to users, that community is vast and provides a lot of learning. Users reach out to the community for any questions or doubts about full development, for example, or anything you want to learn in UiPath. The community also has a morale booster for users through the yearly Community MVP.

UiPath helps minimize our on-premises footprint, though it doesn't matter much to me.

I've taken UiPath Academy courses, and I found UiPath Academy beneficial. Back in 2018, when I just started learning from the UiPath Academy, it gave me everything I needed to start using the solution. Later on, I learned advanced development and, just recently, solution architecture, from which I received a certificate. UiPath Academy also gives me information on the latest updates and trends coming from the vendor.

I'm also working with the AI functionality for automation via UiPath, which affects the ability to automate complex processes. Suppose we have a document, in particular, handwritten. In the traditional way of automation, my bot can't read or understand what's written on that piece of paper. Still, with UiPath, you can select any of these features: Document Understanding, Breakpoints, or Automation. The solution's features give my company flexibility and help extend its reach. Previously, my company thought the use cases weren't feasible because my bot couldn't read or understand handwritten text or characters. Still, with UiPath, it is possible to make life easier, especially with the new advances.

As for the solution's AI functionality enabling the company to automate more processes, my team has not used UiPath in many use cases that require AI, but in the future, when more cases come up, my company will be able to use UiPath more, and it will be beneficial.

I also like that the solution speeds up digital transformation and reduces the cost of the digital transformation. It also doesn't require expensive or complex application upgrades and IT application support. To elaborate further, suppose I'm automating something. I know the application will be upgraded in the next six months; I won't be automating that through my tool because I know it'll be automatically upgraded in six months. I just need to record my use case involving the website or whichever application.

I also found that UiPath helps reduce human error. A human can make mistakes, but your machine won't if you teach it correctly or give it the instruction properly. If you properly provide your machine with data, it won't make a mistake.

UiPath also helps the organization save money overall.

I'd say UiPath is on the right track now, but I feel some aspects should improve a bit, and the vendor could be working on the aspects in my head right now. Governing components in the solution, such as the Orchestrator, and configuring the robots should be easier. I also feel that the vendor should come up with more offerings or features involving AI.

I've been working with UiPath for about five years.

I didn't experience stability issues with UiPath in my current company, but I did in my previous company, where UiPath was down for some time.

On a scale of one to ten, with ten being the highest in stability, I'm giving UiPath an eight.

UiPath is a scalable solution.

My company purchased a plan where the vendor provides some support throughout the year on whatever UiPath issues the company faces. Getting support is easy, and the team is quite helpful.

I'd rate support an eight out of ten. It's not a perfect ten because the overall turnaround time to solve issues could be improved.

I've worked with other RPA solutions, such as Pega, Power Automate, and Blue Prism, before working with UiPath.

Pega is a legacy solution, so I'm setting it aside. UiPath is far better than Blue Prism. On the other hand, Power Automate is the real competitor of UiPath because it has similar functionalities with the new web apps in UiPath, but UiPath is more lightweight and requires less coding.

I found UiPath simple to set up. The process was very straightforward. As long as I have complete resources and information, I can get it ready in about two hours.

My company implemented UiPath via our in-house team.

I've seen some ROI from UiPath.

UiPath has a very costly AI automation license compared to Power Automate. After discounts, it costs around fifteen thousand euros, while Power Automate gives you the same features for only a thousand euros, so there's a huge difference in the licensing costs. Pricing for UiPath isn't very competitive.

I'm a solution architect who does UiPath consultancy.

UiPath is currently deployed on-premises and on the cloud, so it is a hybrid environment.

One admin is enough to deploy the solution, provided the developer and the responsible teams provide the admin with all the resources. UiPath can be deployed through a single resource only.

The solution only requires a little maintenance to keep it up and running. A more significant challenge only occurs if you have to migrate from one version to another; otherwise, maintaining UiPath is very straightforward.

In my company, UiPath is deployed across the globe in multiple countries.

I'd advise others looking into implementing UiPath that it is the best tool to automate repetitive tasks. Whether to use UiPath on the cloud or on-premises depends on your environment. For just a few use cases that you want to automate, go cloud-based, but if you have more than ten use cases, I suggest you go on-prem.

I'd rate UiPath an eight out of ten as a solution.

We do regular process automation for web applications and Excel. In one use case, we have a web application, and we need to scrape data and update it in a specified format in a spreadsheet and then upload it into another application. This is the use case on which I am currently working. There is another use case where I extract data from a web application and add the data into another web application, input the data into my Jira using APIs, or directly insert the records into a database.

We do not use UiPath to automate processes that deal with a "good cause" that our company is involved in. We are automating internal processes for the project engagement we have with our customers. We have general developer access. We do not do process mining, but we use UiPath Task Capture.

It is easy to build automations using UiPath. Previously, we had to write lots of code and handle any changes or errors. All those things are now just a checkbox away for us. It is very easy. It saves a lot of our time. There is also consistency. When there is code failure, I can select the retry option, and it will retry for the specified number of times. That is a great feature.

UiPath enables us to implement end-to-end automation. It saves a lot of time and eventually, it saves money. Those are the benefits that we are seeing. The process that used to take a day can now be completed every morning within an hour. Similarly, a process that used to take an individual five to six business days now takes one and a half hours. We have better accuracy and more confidence that nothing has gone wrong. These time savings always get converted to money. People are able to focus on other things, which has an impact on money savings.

UiPath has helped to minimize our on-premises footprint. When I try to run my scripts that are somewhere on a remote desktop and are not accessible because of some issue, all my processes are on hold, whereas I do not find that problem with the cloud. I can log in anytime even from my mobile and then trigger a process from Orchestrator. That is a great thing to have.

UiPath speeds up digital transformation and reduces the cost of digital transformation, but this happens over a period of time. It takes at least six months to one year to see these benefits.

UiPath has reduced human error. There were a lot of exceptions that we had in the application. All the exceptions should have been extracted from the application and assigned to the respective team. When we started automation and extracted all the exceptions, we could see hundreds of exceptions. Some of them were even 300 days old. They were not attended by anyone. All such things were uncovered by UiPath.

UiPath has freed up employee time. In one case, it reduced their time from a day to an hour. In another case, it was reduced from 40 hours to 2 hours.

The document extraction or document understanding feature of UiPath is valuable. It extracts data from the PDF.

If I have any technical challenges or I am not able to proceed because I do not have the expertise to use a feature, I browse through the UiPath community. There are usually a lot of people who have faced similar challenges. There are also multiple answers or workarounds. I try them out, and they usually work for me. This way the UiPath Community has been very helpful. The community of Power Automate is also very helpful.

A lot of my team is currently using the UiPath Academy. The biggest benefit is that I do not have to train them on anything. I tell them the courses they need to complete, and after they complete a course, they show me how they have done that assessment. We try to understand the process they followed to complete that assessment. It is part of their academic certification. It is a great feature. It saves time that I would have had to spend on teaching my teammates. It allows them to learn at their own pace. Not everyone is in the same place. There are people who can go fast. Every individual can proceed at their pace. They do not have any dependency on others.

While working on Excel and PDF, there should be a feature to define which content to extract and which table to extract from a document. It should extract only that. There should be a possibility to ignore everything else. I should be able to show one sample for one page, the second sample for the second page, or one sample for all pages. I would love to see such functionality in UiPath.

I have been using this solution for almost a year now.

It is very stable. It is 100% stable. I am very confident of its stability.

It is scalable. It is able to increase its capacity and functionality based on our demands. Whatever use cases we are getting, we are able to implement them with UiPath. We are seeing a lot of features for which we have not even found the use cases. They are ahead of the market needs.

We have only two developer licenses, and we have four bots. Apart from that, we have four virtual machines in which these bots are deployed. We have one admin from the IT team who owns the controller.

We have plans to increase the usage of UiPath. We are proposing UiPath for all upcoming projects.

I have not reached out to them for anything since we got the license because we got all the support from UiPath forums, UiPath documentation, and UiPath Academy.

I did not use any other solution before UiPath, but after I started to work with UiPath, I also started to work with Power Automate. A lot of AI features that are available in UiPath are not available in Power Automate.

We recommend a solution depending on the process that a customer wants to automate. Depending on their requirement and business criticality, we suggest a tool. We cannot say only one solution is the best. If someone wants to automate only one or two web applications and Excel, Power Automate is good enough to do that. They do not have to go to UiPath. If they have a complicated process that requires implementing an AI model, the UiPath is good. It depends on the case.

We were not very experienced in the implementation. We spent two to three hours a day, and we were able to do it in two or three days. That is a good amount. We did not have to spend too much time.

For implementation, we first had to go through all the prerequisites for installing the developer tool and deploying a bot. We had to understand these things, do the infrastructure setup, and then deploy it. The deployment did not take a lot of time. Meeting the prerequisites took 50% of the time.

UiPath does not require any maintenance. It is only our scripts that will need maintenance for any changes.

We implemented it ourselves. We had one person doing all the setup and installation, and we had two people helping him wherever required.

We have seen almost 70% to 80% ROI.

Before we procured the license, the pricing they quoted was too high. We continued to negotiate for almost a month. This is something they can improve from their side. If they had quoted the right price, we would not have had to negotiate. We got more than a 50% reduction in the price, which is bad on their part.

To those evaluating UiPath, I would advise first understanding their needs and the features that the tool is providing. They also do not need any external training to implement UiPath. Their identified resources can just go through the UiPath Academy and reduce their implementation costs or training costs unless they have a very complicated process to implement.

I would rate UiPath an eight out of ten.

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 work on database automation. We just delivered a dynamic workflow in an Excel automation as well. We work on many types of formulas. In addition, we develop physical automation. For example, we created a process that posts many photos at once on many groups.

We are able to produce output with UiPath in less time. Where a manual process takes one to two hours, we can develop a UiPath solution that takes 15 minutes. In terms of saving time, one bot has saved 60 to 70 percent of the time the task used to take. We have also seen human error reduced by about 60 percent.

We have automated processes with 20 to 25 bots, and our organization is very happy with UiPath.

It's easy to go with UiPath. It's user-friendly, and any IT person will find it easy to use. It can be learned in six months to one year.

Also, we can use Orchestrator with Action Center for end-to-end automation. With Orchestrator, we can schedule automations.

I would like to see the setup improved. First we install it, then we log in with Orchestrator, and then we have to log in to the UiPath website. I would like all this to be merged into one setup.

I have been using UiPath for 2.7 years.

The stability of UiPath is a nine out of 10.

The scalability is between eight and nine out of 10.

Support can take a lot of time, two to three days to receive a response.

I have developed Excel automations with Power Automate.

We are using the Community Edition of UiPath and it is deployed on our servers. We use it in one location in one department. It was not a complex process to install it, although there was a little bit of complexity to it.

If there is any activity or anything changes in the environment, maintenance of UiPath can be required.

We have saved both time and money and have definitely seen return on our investment.

The price of UiPath is not too expensive or too cheap. It's in between.

We have four people involved in deploying automation: one developer, a team lead, and two DevOps developers.

My recommendation is to learn flow development.

We utilize UiPath to manage workflows and deploy application solutions into our customers' environments. UiPath simplifies various business tasks, such as automating applications, Excel, and segregating data.

We deploy UiPath both on-premises and in the cloud depending on the customer requirements.

Building automation with UiPath is straightforward. Even individuals with limited technical proficiency can utilize UiPath.

We implemented UiPath for one of our partners. They previously required human intervention to manually manipulate data in a 17,000-column Excel spreadsheet for monthly reporting, which used to take one hour. By employing UiPath and incorporating a Python script into the process, we automated the Excel spreadsheet. As a result, the task now only takes three minutes. This automation saved the organization time and money, increased the accuracy of its data, and allowed its employees to focus on more value-added work.

UiPath enables us to implement end-to-end automation. I have a client in Malaysia, and I am from Vietnam. I visited the client on-site for two weeks. They are in the manufacturing industry, and my purpose was to gather information about their automation requirements since they had never utilized automation before. I managed to assist them in standardizing their processes by offering advice on how to implement the solution. I collected the end-user requirements, which were then used to create the necessary documentation. Once the document got approved, the developer and I developed the bot and subjected it to UAT before obtaining final approval for its production release.

The UiPath User Community is wonderful. While many RPAs have their own communities, none compare to UiPath's. The community edition of UiPath boasts a substantial user base, with expansive groups across various social media platforms. When I first started using UiPath, I would always turn to the user community whenever I encountered an issue. I noticed that others had already asked the same questions and received answers, which was quite convenient for me.

Everyone associated with UiPath usually completes at least their first year of Academy courses to acquire a fundamental understanding of RPA and the platform's functioning. This knowledge is crucial for facilitating the easiest possible approach to automation. I genuinely appreciate all the videos from each course. Every video contains valuable information, and I never skip any of them. In the beginning, the Academy was a great help to me.

UiPath helps reduce the cost of our digital transformation. One of our large financial industry clients mentioned that where they used to require 13,000 employees, they are now only using 6,000 to complete the same work through digital transformation.

UiPath assists in eliminating human errors. Numerous tasks performed by humans each day involve typing in information. Humans can make mistakes due to factors such as fatigue, mood, or feeling unwell. However, automated processes are not susceptible to these issues.

UiPath can contribute to cost savings for an organization, contingent upon the organization's size and the quantity of tasks being automated relative to the number of employees presently engaged in performing those tasks. On average, UiPath has the potential to reduce costs by approximately 30 percent.

The most valuable feature is the ability to view my own activity and customize it on the platform.

We cannot utilize the UiPath community edition license to operate any bots that we have created using that version in an enterprise environment. This is because we are obligated to employ UiPath Studio, which necessitates a distinct license for professional use.

I have been using UiPath for two years.

UiPath is the most stable platform.

UiPath is scalable.

I previously used Power Automate before switching to UiPath which is an out-of-the-box solution.

The initial setup is straightforward. We just need to run the orchestrator and the packet. I can complete the deployments myself based on the documents.

I would rate UiPath nine out of ten.

UiPath requires proper maintenance which is outlined in the user manual.

I use UiPath for invoice processing. We download all the invoices from our application and then send them individually to the respective customers via email. This involves email automation and automation of the user interface.

Building automation with UiPath is easy. When compared to other automation tools, UiPath offers a more user-friendly development platform.

It enables us to implement end-to-end automation, from the basic extraction of data to the complete uploading of data to the respective applications.

UiPath's User Community is excellent. Whenever I encounter challenges or need information about new developments, version changes, or anything related to UiPath, the community is always there to help. Therefore, I find the community extremely valuable.

UiPath can be a useful tool for anyone. It doesn't require a separate environment or the need for a developer. It is beneficial for anyone dealing with any system. Therefore, I believe it can serve as a regular daily process tool, enabling users to automate various tasks effectively. There are numerous possibilities and applications with UiPath.

In my early days of entering this field of development, I completed the UiPath Academy courses to gain a comprehensive understanding of the interface, the approach we should take, and how to utilize the portal functionalities that UiPath offers.

UiPath has been instrumental in reducing human errors by 99 percent in applications that are maintained correctly, particularly in activities such as typing. There are certain tasks where humans are prone to making mistakes while working with applications, but UiPath ensures that such errors are eliminated. Initially, I had some doubts about UiPath's ability to extract data from PDF files, as the UiPath OCR engine seemed to have limitations. Consequently, we started relying on ABBYY FineReader for this task. However, we are now exploring UiPath's UI for document understanding. As a company, we have already developed around 200 to 300 templates using ABBYY FineReader, making it challenging for us to transition entirely to UiPath document understanding at present. Nevertheless, we are considering the shift because the early versions of UiPath were not very efficient, and we couldn't fully rely on it for data extraction. However, with the recent integration of Google Vision, UiPath has significantly improved and is now providing better results in terms of OCR technology.

The user interface is the most valuable feature of the studio version. It allows us to develop all activities and create custom activities as needed. Additionally, it seamlessly integrates with the latest technologies, such as AI, making it very helpful, even for integrating ABBYY FineReader. Users can extract data from the time scripts, which is also a project involving data extraction from all PDF files.

The UiPath Community does not provide version control for the community edition. Let's say I'm currently using a specific version, and then it automatically upgrades the community version to the latest version without the user having the option to decide whether to update or not. Consequently, we cannot use the older versions in the UiPath community edition.

I encountered some issues with my local machine. I created one of the bots using a different version from the community variation, there were problems with compatibility between different versions in UiPath. While those issues used to exist, currently, it has been a long time since I last modified any of the workflows and migrated between servers and my local machine. I'm not entirely certain at the moment, but previously, there were instances where a particular activity in one version would not work in another version and would result in failure. Additionally, sometimes the select task would not identify the select areas in the actual application, even though it worked on the validators. These scenarios are rare but they do occur.

I have been using UiPath for almost two years.

I would rate the stability of UiPath ten out of ten.

I would rate the scalability of UiPath eight out of ten.

The initial setup is straightforward.

The licensing fee is moderate and is based on the volume of tasks for which we use UiPath. The cost is satisfactory.

I would rate UiPath eight out of ten.

Currently, we are handling approximately 20,000 units of data on a daily basis. Our focus is on efficiently processing this data and integrating it into the scaled servers. We utilize the scale servers for data connectivity, verification, and storage purposes.

We are currently not using the AI functionality, but our company is anticipating a new project. The assignment of this project will happen very soon, and the company is considering the use of AI for it. However, this decision will ultimately depend on the user and the environment. If we determine that using AI functionality is necessary, we will integrate it into the project. At present, we have not encountered any users who explicitly require AI in their business logic. Therefore, we are not utilizing AI at the moment. Nevertheless, if any future clients request it, we will be prepared to integrate AI functionality accordingly.

Our organization has started using automation with UiPath. Before implementing UiPath, everything was done manually.

If the initial development is done correctly, then the maintenance would actually be significantly reduced. As a developer, we need to ensure that the code is always reviewed by developers, and they should always be available for this purpose. If the initial development is not carried out correctly according to the requirements, then imagine the consequences in the future. The development might need to be revisited for up to 15 years, or at least five years. If it is not done that way, the maintenance cost would be very high because the business processes keep changing. Therefore, to keep the system functioning well and the applications up-to-date, as they are not static, we need to continuously maintain the code. For instance, in the past six months, we've had to make two changes to the application we are working on. Many alterations occurred, such as UI element changes, shifting locations, and complete interface and navigation changes. Hence, it's essential for developers to always keep the code protected and up-to-date.

I recommend conducting a proof of concept using UiPath to ensure that the budget and return on investment are sufficient to implement the solution within an organization.

I am a developer, and I use UiPath to extract PDFs for invoices and logistics in the banking industry.

UiPath can be deployed either on-premises or in the cloud, depending on the customer's requirements.

There are times when the logic is difficult, but the majority of the time, it is easy to build automation using UiPath.

UiPath enables us to implement end-to-end automation, which is essential for our customers. We gather all the requirements from the customer, analyze their feasibility, and proceed to the development phase where we build bots according to the customer's needs. After that, we move on to User Acceptance Testing to ensure the bots meet expectations. Finally, we deploy the automation into production.

UiPath aids in enhancing organizations by cutting down costs and saving time. Without UiPath, a task like collecting and uploading information that typically takes humans around 40 minutes can be completed by the UiPath bot in just ten minutes.

Our customers primarily use UiPath for cost savings.

In addition to saving time, UiPath also eliminates human errors by consistently processing 100 percent of the tasks each time without requiring any human intervention.

UiPath helps reduce our customer's on-premises footprint.

UiPath Academy is excellent for learning about the solution's capabilities and how it works, especially in the beginning. It provides end-to-end courses and certifications for both beginners and advanced users.

UiPath accelerates digital transformation and reduces costs by eliminating the human element. However, this transformation does require IT application support for configurations and security.

UiPath's most valuable feature is its ability to view and extract any data throughout the entire development process in the automation framework.

The document understanding has room for improvement.

I have been using UiPath for three years.

UiPath is extremely stable and that is why customers ask for the solution.

I rate UiPath's scalability a nine out of ten.

The technical support is good.

I previously used Microsoft Power Automate. When comparing it with UiPath, one significant difference is that we can use UiPath on a local machine to easily build a process, upload it, and create schedules effortlessly. Microsoft has an advantage in the cloud, but it is not as effective on-premises.

The number of people required for each deployment depends on the complexity of each project. For more complex projects, two to three people are required, and it can take up to three weeks to complete.

Our customers experience a return on investment when using UiPath, owing to the time saved in performing tasks and the improved accuracy compared to manual efforts.

We can start to see value after one month of using UiPath.

There are two versions of UiPath; the first is the free community version, which is limited, and the second is the premium version which requires payment but is recommended for large-scale productions.

UiPath's cost is acceptable.

I would rate UiPath a nine out of ten. UiPath is reliable and accurate.

The maintenance is easy. We only need one person to monitor and maintain UiPath.

I recommend trying the free community version first to ensure that it meets the organization's requirements and then consider upgrading to the premium version in order to handle larger projects.

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.

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.