UiPath Reviews

We are a partner of UiPath, and we utilize their solution for welfare unions and document understanding.

Building automation using UiPath is straightforward. I would rate the ease of building automation an eight out of ten.

UiPath enables end-to-end automation, which is essential to our organization because it saves time, is reliable, and is easy to use. Although it is somewhat expensive, it is worth the investment in the long run.

Being a part of the UiPath User Community helps us deal with various tasks. We can share our experiences with the members of the group and learn from the experiences of other members of the community.

Some of the benefits our clients have noted about UiPath are the speed and the reduction in operations at the end of the day. Our clients were able to achieve their goals quickly by using UiPath and witnessing a return on investment.

The introductory course of UiPath Acadamy is good.

UiPath accelerates digital transformation and reduces its associated costs. Initially, implementing such transformations may necessitate expensive upgrades. However, once the setup is complete, operations can run smoothly. Typically, when a company begins contemplating digital transformation, they often find themselves in a technologically outdated state. As a result, a comprehensive update of their systems becomes imperative, incurring significant costs.

UiPath helps reduce human error. It is highly beneficial to automate certain human tasks and mitigate the potential for errors.

It has freed up approximately 50 percent of our employees' time.

UiPath has saved approximately 20 percent of our organization's costs.

The UiPath Community is truly helpful.

Although we have to pay for the extra features that UiPath offers, they are extremely useful.

The introductory courses of UiPath Academy are adequate, but there is room for improvement. I understand that creating an automated course for everyone is not an easy task. After completing these courses, we are capable of performing simple tasks. However, if we truly want to learn, for example, Java, we must conduct further research on our own. The Academy courses should provide more challenging content.

The pricing in our region has the potential for improvement. The price is the same throughout Europe, despite the varying economies in each country, which poses challenges for all the partners involved.

I have been using UiPath for five years. 

I would rate the stability of UiPath as a perfect ten out of ten.

I would rate UiPath's scalability as a perfect ten out of ten.

We previously used Blue Prism but switched to UiPath to meet client requirements. Personally, I prefer UiPath.

As a partner, we experience a return on investment because we bear the cost of the solution, and subsequently provide the services. The client pays for both the services rendered and a portion of the licensing fee. For us, the benefit is clear, but as a lean benefit, compared to the really expensive fee that we have to charge the clients to have a margin.

The price is high. On a scale of one to ten, with ten being the highest, I would rate the price as an eight out of ten.

We also have to pay extra if we want Studio, Document Understanding, even if APIs are not going to be used for text recognition, or Insight. Insight is really expensive and doesn't offer anything new other than Elasticsearch and Kibana, which are free tools. The message we have received from UiPath is that they are the leader in the market, and we have to pay for that.

We evaluated Automation Anywhere, Blue Prism, Appian, and a few others before selecting UiPath.

I give UiPath an eight out of ten.

I recommend that new users first take the Academy courses before transitioning to the UiPath Community version. It is advisable to learn all the basics thoroughly, without assuming any prior knowledge, and to exercise patience.

I have learned that using a machine is better than I am.

We used this solution to automate monitoring, implement robots, and monitor the robots. We use it for network monitoring, ticketing systems, and remediation activities. This is a SaaS solution. 

This solution is mostly used by network engineers in managed services. The engineers look after telecom networks, and they are the end users. For automation, a sizable team of developers, specialized automation developers, and solution architects used the solution. There were about 40 RPA developers and 10 solution architects.

We plan to automate some of the business processes regarding financial reporting.

We used this solution in the automation of a legacy Jira application that was used for CR management. We use the change request template, and we're able to collect data from various systems through APIs and submitting requests.

Since we started using this solution, our team has had more time to work on other tasks.

The solution has reduced human error by processing the data directly from the source and into the destination application without human intervention.

Our internal clients are glad that KPIs are increasing.

A lot of my colleagues have used the UiPath Academy course. There were also colleagues who used the course and weren't involved in the day-to-day automation process.

It really helps employees be aware of how the tool works, how they can better describe processes, and with what level of detail they need us to describe processes so we can automate their work.

One of the biggest improvements was that some of our colleagues who weren't technical and weren't working in the automation domain started to build their own robots to automate some parts of their work without help from our automation team.

UiPath's community is used by quite a lot of our developers to solve some issues and get resolutions faster. The community is quite big compared to other communities. We get more resources, and it's more active than other communities.

We use Attended Automation for some of the monitoring, like creating outlets based on network events. Attended Automation helped scale RPA benefits in our organization by automating department or role-specific processes that require human-robot collaboration. 

With the involvement of a lot of colleagues from different departments, mostly using Attended Automation, we have increased the awareness of automation and robot automation in the company.

I like the interface. It's simple to interact with. We can replicate and multiply the robots when we need to change something.

It's easy to build automations using UiPath. Colleagues who aren't very technical can develop their own automations.

The developer studio could be improved. There have been glitches, but it improved from year to year.

I have used this solution for three years.

We had some issues with stability because of some unattended robots. During execution, there were stability issues.

We didn't have many issues with scalability.

We have a good relationship with UiPath. We are in Romania, and they have an office here.

I would rate support an eight out of ten. 

Positive

The setup was easy. Within one month, we migrated from Blue Prism to UiPath and started implementing some robots.

We had a small POC to discover how it would fit in our infrastructure and how feasible it would be to have all the functionality from our previous tools. We rolled it out for a small department and migrated all automation to UiPath. Then, we gradually rolled it out to other areas.

Overall, the solution saved costs. Last year, it saved us between 8% and 12% of costs.

We increased the speed of delivery of automation, so it's a good return on investment.

We also evaluated Blue Prism. Due to its subscription pattern, it wasn't flexible enough for everybody to understand it and work with the tools. Licensing was a bottleneck.

Blue Prism didn't reduce the cost of automation, but it increased the number of automations we did in the same period by 30%.

I would rate this solution seven out of ten. 

My advice is that depending on the business domain where you want to implement the solution, it's more feasible for document processing and ingesting data in applications, not for executing commands in various application servers or infrastructure. 

Stability is an issue. In large deployments where you have a lot of robots, these issues can cause a lot of intermittent problems with the operation of the robots.

Our company uses the solution to process state reporting uploads for clients. 

For one use case, we automated the process of dragging forms, filling in fields, capturing confirmations, logging information, and moving files for upload. 

For another use case, we automated the process of manipulating data, setting filters, and generating reports in Excel. 

We are now moving to another department that uploads yearly tax reporting files to websites. 

We do not yet use AI but have many possible use cases for reading invoices and PDFs so we will try these processes first. 

We have saved a lot of time on uploads. For example, our state reporting uploads now take only two to four minutes and that saved us 7,500 hours for January alone. We anticipate similar time savings for the automations we are currently doing in another department. 

As we continue to automate our uploads, we will not need as many seasonal workers so that is a big cost savings. 

The solution includes preset activities but allows integration of code and expressions that make it more powerful and dynamic. In nine month's time I have barely scratched the surface, but it feels like it integrates to so many things that finding new use cases is easy. 

The automations allow us to better catch errors because data is always transcribed correctly.

The upgrade process could be improved so that it does not require download and reinstall. It would be nice to have an upgrade option that talks directly to the orchestrator. 

Some documentation can be improved. For example, documentation for integrations and activities tells you what it does but does not tell you how to fill in variables or fields. I had issues finding some things I needed for new activities or integrations. 

I have been using the solution for nine months. 

The solution is pretty stable. You may have version issues because there are a lot of updates, but that is not a stability issue. It is always important to make sure you have the latest updates. 

The solution is definitely scalable but it takes time to learn how to best scale. There are many routes you can take which depend on different things. 

The Community is super helpful because they share information that is of great benefit. Forums have been useful when I have needed help. 

I gained my experience through the Academy's courses. I was in a different role at my company but they needed another UiPath developer. For three months, I did a rotation with the RPA foundations course. After that, I was able to start working in the full time developer role. The Academy was very helpful and allowed me to jump in with no UiPath experience. 

Technical support is very helpful. I only contacted them once for an issue with the Salesforce API package that would not run with attended users. They responded in a timely fashion and helped me quickly resolve the issue. I rate support a ten out of ten. 

Positive

Our company previously did not use an RPA tool but rather used command line scripts and tools with Python. 

One of our developers had been writing scripts and came across the solution. He showed our company how much time it saves while improving accuracy. 

The setup is pretty straightforward. 

It is amazing how easy it is to automate some things. Once you learn the interface, everything is straightforward. 

I assisted our department in implementing the solution in-house. I helped build and run things for our big rollout in January of 2022. 

Since then, I have automated fourteen processes with attended bots. 

There is a big learning curve to ensure you get everything invested in the solution to realize ROI. 

For example, my department only had two developer licenses but still managed to save 1,300 hours in the first year. Another department was scaling a much bigger deployment, so it took longer for them to hit returns.

The solution is affordable enough to get a good return on your investment. We get ROI over the cost of licenses. 

We started out on-premises because we did not have attended licenses. Now, we are moving to attended for bots and trying to publish more things to the cloud so others can run them. 

I looked at Blue Prism but have not spent time using it. 

Start with a couple of solid use cases that would realize time and ROI benefits so you can see how the solution works. 

Do not go too wide or too fast with deployments. Focus on a few things first until you are clear how you want to expand. It is important to decide whether you want more citizen or RPA developers and whether your bots will be attended. Just take it slowly unless you are working with someone who has high-level knowledge. 

I rate the solution a nine out of ten. 

Our company uses the solution to automate processing of intended and unintended regulatory transactions in the banking industry. 

We are just starting to use the AI function of the solution. 

The solution has been a tremendous efficiency game for our company. 

We have delivered hundreds of thousands of hours of efficiency over 300 robotic process automations. 

The speed to market is amazing because an automation can go from the initial planning conversation to production in weeks.

Most of our automations have been without a user interface and we need the ability to interact with users directly. That should be coming in the next release for us. 

I have been using the solution for four years. 

The solution has been very stable across hundreds of automations. 

We scaled from dozens to hundreds of automations and are very satisfied with the solution's scalability. 

Technical support has been great and I rate it an eight out of ten.

The solution's community forums are great and help solve many issues. We can easily reference documentation for similar issues and that provides a lot of assistance. 

Positive

We previously used Pega but switched to the solution for its speed-to-market benefit. 

Our strategy is to use automation for maintainable, high-quality, repeatable processes while delivering excellent speed. 

I was not involved in the initial setup within our environment, but have managed the deployment of several hundred automations and the process is straightforward. 

It is very easy to use our CICD pipeline to deploy and monitor solutions via the orchestrator tool. 

Our ROI is saving hundreds of thousands of hours in time by automating processes that used to be managed by staff. 

Academy courses have been very helpful in preparing our developers for certifications.

I rate the solution a nine out of ten. 

We do a lot of manual work on a routine basis. We brought in UiPath to reduce a lot of routine work and mundane tasks that we do. An example would be that we have developed internal tools in our company. We need to back up the logs for these tools. Earlier, we used to log into a system, copy the logs, and then store them at another place, such as Amazon S3. With the introduction of UiPath, we are able to achieve this completely in an automated way. We have set up a UiPath automation to log into a system automatically, take all the logs, and then put them in S3 so that we have a backup for all those logs. This was one of the major use cases that we had, and UiPath helped us to achieve that at scale.

We are using the cloud version. We have more of a hybrid model. We have a pipeline through which we deploy everything related to UiPath. We have a beta endpoint and a production endpoint. Everything goes through the pipeline. Once everything is deployed in beta, we do our testing, and when we know that everything is safe in the beta endpoint, we push everything to the production endpoint. It is basically a pipeline system that we manage.

Our overall efficiency has improved. Previously, the manual tasks that we had to do consumed a lot of time, and they were also prone to human errors because they were manual. With the introduction of UiPath, we were able to reduce the time by half, and we were also able to reduce resources with these automations.

We don't use drag-and-drop APIs, but there are components that we drag and drop to build a UI that can connect to the backend robots. It has increased the effectiveness of how we implement apps. We can create the UI that we want visually, easily, and immediately. Through code, it would take us more time. UiPath's drag-and-drop functionality has drastically reduced the time because everything is visual. We are able to quickly build the app that we desire.

One of the features that I find most valuable is the Apps feature. We can easily create an app, or a web app, that can connect to the robots that we created with UiPath. It is just a drag-and-drop functionality, and we can implement an app with minimal code. Once we have the app ready, we can easily and quickly share it with other stakeholders so that they start using it. The apps are also pretty professional to be used at an enterprise level. That's the main feature I love in UiPath.

UiPath's community is great. It is a place where developers like us post questions and get answers from our fellow developers. We've been using that. Their community is very active. Some of the communities out there in the market don't seem to be as active as UiPath's community. Whenever I post a question, I get a detailed response within 5 to 10 hours, which is very good. My peers have also told me the same thing. We get support in the community, and we can also contact community members for help, and they are glad to help us with any problems.

UiPath is good in a lot of areas, but as an end user, I feel one thing that can be improved is UiPath Studio. It is an application that we can download to our system and then start building the use cases that we want. Sometimes, it takes a little bit of time to launch, and when we are building a complex application involving a lot of sequential flows, it tends to lag a bit. 

As a developer, initially, UiPath is a little bit difficult to understand because it has a lot of features and components available with it. Understanding each one takes a little bit of time. After we get into the solution, they can provide more out-of-the-box hands-on. It took some time for us to grasp the concepts and features of UiPath and then implement them. If that time could be reduced, it would be really good.

In terms of features, I'm happy with the features that UiPath offers.

It has been around one and a half years since I've been using UiPath in our company.

Its stability has been great. I've never seen it break or crash. It has been very reliable.

For production workflow, it is able to scale at high volume. It is able to take in a lot of transactions per second, which is really good for us because we have a huge customer base, and more customers are starting to onboard. The more RPA is used in the back end, the better it is. It is scalable as we expected it to be. It is able to cater to all the requirements that we have. 

One good feature of UiPath is that whenever I do a Google search, I get a lot of answers. The community of UiPath is very active, and they're great. Whatever question I post, I get a reply to it. 

They also provide professional service. We have the enterprise version, and they provide professional service and support. Anytime that we have raised a ticket with them, we typically get a response within 24 hours. That has been really good. I would rate them a nine out of ten.

Positive

We haven't used any other similar solution. We had in-house solutions, but they were not scalable. They couldn’t operate when the user base was increasing on a day-to-day basis. We saw UiPath and immediately went through the documents. Once we knew that UiPath could solve all our use cases, we just onboarded it and migrated all our in-house solutions to it, and since then, we haven't had any problems. It has been great.

I was not a part of the deployment team.

We were able to reduce the resources. Previously, if we used five resources, then after we introduced UiPath, the number went down from five to three. We need two less resources with the automation that UiPath provides. There is about a 25% increase in efficiency with the help of the automation that UiPath provides.

I'm not aware of the pricing because I'm on the development team. The pricing mostly comes from our marketing team. They handle the pricing with UiPath and give us access to the UiPath licenses as a company. 

We didn't evaluate other solutions. This was the first one that we encountered. 

We have not used UiPath's artificial intelligence and machine learning capabilities, but we are doing research on that. We haven't yet implemented anything in production.

I haven't yet explored UiPath Academy, but I have heard about it.

I would rate UiPath a nine out of ten.

Initially, we had some manual test cases running in the background, where we tried to call our UI and do end-to-end testing of the login, checkout, etc. We now automate end-to-end testing using UiPath to reduce the workload. We use UiPath for process analysis and making robots, but not for monitoring. We already have other tools in our system to monitor each and every step of our process

We work in a hybrid environment, but we're increasingly cloud-based. We are not driving as much traffic to our on-premises system. 

We were hiring developers to write test cases and perform automation for us. UiPath significantly reduced the amount of employee labor needed while cutting down on human error. The error count in our system dropped by around 10 to 15 percent. 

This is a considerable win for us. Our clients are happier because they see fewer errors in production. End-to-end automation helps us deliver quality work to our customers. UiPath helps us analyze every connected case with automated robot testing. 

UiPath has a simple, creative UI, where you can check on all the automated tools. Everything is well documented, and you can easily get support from the UiPath team. Whenever we were stuck, their team was always there to support us. The community is huge and powerful. 

The entire process of setting up automations is smooth. We could easily deploy each case on our cloud platform and make things work.

We aren't scaling up UiPath because it doesn't provide a satisfactory way to log and monitor data. Instead, we use other tools like Automation Anywhere for large-scale operations in our production environment. We're building solutions that can handle a huge amount of data so we can monitor real-time issues. I don't think UiPath solves that case for us.

We've been using UiPath for around a year.

We faced some issues with scalability, so we use another RPA in production. 

I rate UiPath's support nine out of ten. We always get a response within six hours. UiPath also has a massive user community, so you can get instant support from anyone. We faced some issues when we built our first robots, so we got help from the community. When someone else has problems, we try to help them. 

Working in the community, you are recognized for your support, and you can learn a lot from others. There are some complex things about using UiPath that we don't understand. 

The UiPath community is friendly, and they respond quickly. At most, it takes around six hours to get an answer from the community, based on our experience. I believe that anyone who adopts UiPath will learn so much from the community.

Positive

We deployed UiPath through a vendor provider who helped us through the entire installation and everything in our cloud environment. Initially, we tried UiPath in our testing environment. Once we saw that it was stable and improved our productivity, we moved it to our production environment with excellent results. It took 10 months for us to deploy UiPath fully. 

We had two people working on the deployment. One managed the installation, while the second person handled monitoring and other development areas. 

We had two developers working 20 hours a week writing test cases manually, so UiPath saves us 40 hours of labor costs. However, we spend about that much on UiPath when you factor in licensing, infrastructure costs, and other expenses. The value we see is from the reduction in human error. 

I rate UiPath eight out of ten. I deduct two points because of the shortcomings in terms of scalability and logging. It's a nice-to-have solution in our case. I recommend trying UiPath out and seeing if it's suitable for your use case. You should go for it if it fits. It's not too costly and it will reduce human error while improving the quality of your product.  

Our use case for this solution is for hosting and deployment purposes of web applications.

We are using the latest version.

UiPath is a good solution for automation. Our time management has improved by using the UiPath solution. On a monthly basis, it reduces one week of a developer's time.

It helps reduce human error. 99% of errors can be avoided by using this solution.

It has a very good, user-friendly user interface. This is its best feature - it is very easy to use. There is not much complexity when using it. For the beginners, this is also good.

For building automations, we can use a task manager because we also have job management or support in the development phase. We can apply first-in, first-out with work in UiPath.

For the automation, we do not require anything to be manual. We only need to set up the configuration. UiPath follows the instructions given by the developer or engineer. It automatically follows the instructions from end-to-end given in a set of files. 

The unattended automation helps improve our time management.

We are using the solution's AI functionality, which helps us automate more things. Now, nothing is complex. We just need to drag and drop things to create a flow. Everything is done automatically by the automation. It reduces our effort on these types of things.

They could make the solution better by improving the latency.

The community can be increased and enhanced. That way, if we are facing an issue and need an easy solution, we can then use the community.

I have been using it for a year.

It is capable of doing various tasks at the same time.

We have not experienced any downtime or issues.

It is scalable. We can add any number of users. This is the most scalable solution that we are using.

The technical support is good. I would rate them as eight out of 10.

We would like them to increase the community. That way, if we need 24/7 tech support due to an error or issue, we can resolve it as soon as possible.

Positive

We did not previously use another solution.

The deployment was neither straightforward nor complex. Some skills are required, i.e., basic courses are required for a developer or engineer using this solution. For a person who has hands-on experience with it, the deployment will be simple for them.

The AI functionality saves time and reduces the number of errors. It also reduces our costs in terms of human resources. It has reduced our costs by thousands of dollars.

We have a team who decides the software that we use. They chose UiPath because it was better than the other competitors. They conclude that UiPath was the best one, which is why we use it.

I would rate UiPath as nine out of 10.

I work for an international consulting firm and we work with enterprise clients. Our job is to provide them with RPA solutions and ultimately, we would like to provide opportunities for them to have every kind of automation.

We began with use cases in accounting and controlling departments, after which we moved to automate banking, legal, and IT processes. Nowadays, we are reaching out to HR to help automate some of their minor processes.

To this point, our implementations have been in an on-premises environment. At this time, we are in the process of migrating our on-premises UiPath environment to the cloud.

When I joined the RPA team, coming from a DevOps position, I assisted them with IT-related tasks such as implementation, packages, etc. I went on to become an RPA developer and began working on business sue cases. As part of my duties, I search for opportunities, help find internal clients, and improve governance inside of our enterprise. I am involved in all of the steps in the framework.

Our first automation was an on-demand service, used internally for us. We deployed an on-premises orchestrator, also used on an on-demand basis. Once we got this experience, we started building other solutions.

We deployed an internal chatbot named Alex, and our employees can ask whatever they want. For example, you can ask Alex what your salary is. Depending on your privileges, you will get more or less information. Everything is done using robots.

UiPath makes it easy to develop automations and this is the main selling point. I can speak with a client and in the meantime, I can prepare a demo on the fly that captures the client's thoughts at the moment. What it means is that as I'm speaking with you, I can start preparing a small demo. I find the product fun to work with.

An example of how this has improved our business is when dealing with internal clients. For example, if an internal business manager wants to use BI and needs to create a report with a specific set of data, they traditionally had to reach out to the IT department. IT will first examine the needs, then discuss how it is developed. It may need a database instance or other tools, for example. Traditionally, this is how it is done. 

One of the problems with this approach is that our headquarters is in France, and they are used to having internal discussions about everything. For a use case like this, they will consider all of the needs and other points before making a decision. It can be very time-consuming.

However, if we consider the same use case, using UiPath, we are able to create reports on the fly. We can be right in the same meetings with the IT people when we do it. 

If you're from a legal department and your solutions involve HR, as well as other company departments, I can automate several processes in four hours. Then, all of the processes can run during the night. It is an amazing product in this regard.

As we automate processes, another benefit that we receive is the ability to generate internal reports comparing departments and processes. We give these reports to the heads of the company to provide intelligence, helping them to better understand the organization. 

As an example of somewhere that UiPath has saved money, I implemented automation to replace a tool that one of our clients has. It is an internal timesheet tool and although the company uses SAP and SAP HANA for these tasks, this tool handles aspects that are specific to Spain. It is a small tool but is needed for a particular purpose.

The initial development of the tool, handled by an external third party, cost €20,000 (approx $22,500 USD) and there is a monthly maintenance fee of €700 (approx $790 USD). We discussed replacing the tool with our client but they were hesitant to change because they already had the solution.

We offered to replace their tool for free because we are trying to internalize processes, so there was also a benefit for us. We explained that once it was completed, we would be responsible for performing the calculations and analysis to ensure that the replacement was working properly. They agreed and it took me only one day to complete the automation. Now, it takes only a single button click from beginning to end. At the end of the day, it brings in all of the jobs. This automation saves them €700 per month in maintenance costs and it would have saved the initial development and deployment fee had it been implemented using UiPath from the beginning.

It was very easy to see that they were wasting money, and this is happening in a lot of places. We proposed to them that for these tasks, we would charge €600 (approx $675 USD) per day as consultants, and then for maintenance, we would bill them a monthly fee equivalent to 16% of the cost of the robot. For the bot used to replace their tool, it took me one day to develop and two days to plan and design it. The initial cost would have been €1,800 (approx $2,000 USD) and the monthly maintenance fee €200. They switched from their tool to the robot, since it was only costing €200 instead of €700 per month.

After they switched, they realized the power of automation and have since asked us about automating more of their internal processes. They have presented a storm of ideas, and the potential for savings is amazing.

You cannot compare whatever you do with a robot to a traditional software tool, package, or service. This example of the tool that we replaced is only one use case, and there are others but they are all more complex. Overall, it saves a lot in terms of time and cost.

The most valuable feature is the forum, where there is lots of help available. For me, UiPath is the perfect partner to converse with. I have brought four or five topics to the forum and every time that I was stuck, the problem had already been registered. I see the comments from the internal team and they are always tuned to the issue, always looking to fix small problems that have been found. We find that after they have been pointed out, fixes come included in the next release.

The interface is intuitive and very user-friendly.

The UiPath Academy provides courses to help you get up to speed with the solution, and to my thinking, it is crucial to start with this training. Developing a report in UiPath and other RPA solutions is very different from the traditional way to learn. When I studied in university, software development was focused on data structures and optimization. This varies a little bit depending on the programming language but more or less, this is what every framework follows. It's logical and we are always trying to optimize our processes. With RPA, it's different because you base your process on the logic, and then tweak with the tools. It's the difference between painting a picture and shaping an object. For me, the training was crucial and it helps a lot to learn right from the beginning.

The basic course took me four or five days to complete. Just with that, it was enough to become familiar with the framework and quite enough to start making your own automations.

I'm always looking for new courses from the Academy. For example, I completed the architect training, as well as the course on governance. The academy is well structured and very useful, although not mandatory because you can start by yourself. That said, I definitely recommend it.

We use the AI-enhanced document understanding capabilities, as well as other related features.

UiPath is based on the .NET framework, which means that we are currently limited to Windows deployment.

The update process has resulted in several small issues for us. Sometimes when you update, there are several lines that are not included in the package. This kind of technical error, even though it's small, has to improve. I understand that they are trying to implement all of the services that they can, and this kind of thing happens when you expand your model. The same thing happens to us. That said, it needs to improve.

The .NET formwork is well known, as is C#, but it requires a lot of computing power. Everything is JSON-based, so it always has to preload all of the information. This means that there is overhead in the performance and if it were only a simple query, it might be slower with UiPath. However, with a cloud-based environment, we don't have to worry about this.

When it comes to migration, it's always painful. We have found several issues that require changes to be made from a coding perspective. In our current migration from on-premises to the cloud, we had a problem that delayed us by approximately a week. However, I don't consider this to be a pain point because it's a normal thing that happens when you try to size up your company by introducing many new services.

From a technical perspective, the migration is straightforward but we haven't completed our migration yet because we have not set up the gateways to access our services.

I have been working with UiPath since 2019, approximately three years ago.

Starting from version 20, UiPath has been very stable. Prior to this, it has not been 100% stable. That said, we have not had any troubles with the platform in general.

The problems that we have encountered were when we tried to upgrade or to migrate by uninstalling and reinstalling the Orchestrator. There were some internal issues where people didn't read the communications that we put out.

Generally speaking, Orchestrator is very well built. We have put a lot of stress on the system and haven't experienced any problems with performance.

Scalability-wise, UiPath is quite good. This is an interesting topic because, in the beginning, I didn't put much thought into scaling. I was used to building solutions, and that's all. UiPath offers special packages that target scaling up. These packages become relevant when you have more than 20 processes.

For example, you can have activities that trigger processes, and you can include one activity inside of another. With these features, you realize that a huge amount of work is already taken care of.

More to how well it scales, they have a very useful package of integration tools.

Personally, I have automated 70 processes and the total for the team is approximately 300. Within the past year, we have delivered more than 200,000 hours of automation.

Since I joined the group, we have brought a lot of RPA clients into the enterprise.

I would rate the technical support an eight out of ten.

The reason for my rating is that I have been waiting since last year for integrations that are coming. With respect to getting support for other things, I have not had any problems.

The support wants to teach us how to build an automation ecosystem inside the enterprise by combining artificial intelligence models, data analysis, and these kinds of things.

During our implementation and afterward, they have given us ideas about how and where things should go. This has been helpful but from my perspective, it is all still a little bit hard to understand. There is a lot of documentation to study. This is, in part, because they are growing and building.

I have done several RPA jobs in telecom when I worked for another company.

We first deployed version 18 of UiPath, and we found the initial setup to be quite straightforward. It was well packaged and easy to install.

The only pain point for us was issues related to implementing the solution inside our ecosystem. It contains VMs, firewalls, and other things that add to the complexity. This, however, belongs to us. From the perspective of UiPath, they gave us a package to install the Orchestrator, and another to install the runtime in every machine that we want it to work with. Things are quite straightforward in this regard.

In our case, we needed a newer version that came with some of our internal tools preinstalled. This is because we used to have access through Citrix. The installation was very easy.

It took approximately a day for each installation and within a week to two weeks, the service was working. There were five of us working on implementation and deployment. Four of us were working on installation and testing, and three people in the team were IT architects.

UiPath has saved us a lot of time. We calculate our benefit by counting hours saved and last year, we saved 200,000 hours. This means that we replaced between 120 and 140 people by using automation. This is our main metric for calculating cost savings.

When we first started with RPA, we compared UiPath with Blue Prism and Automation Anywhere. We chose UiPath right at the beginning.

For me, it was a straightforward choice. UiPath has a lot of help available, and they have a lot of tools. The forum, for me, is the winning factor. For now and in the future, UiPath is the product that I will use.

Another factor in our decision was the ability to use the product before purchasing it. Blue Prism had a demo account so they were a little bit open. However, Automation Anywhere wasn't open at all. They wanted us to pay while we learned how to use it. For me, that was the breaking point because UiPath could be used for free and was open from the beginning.

Coming in as a developer, I very much appreciate that the platform and the code are open. They don't keep everything that they are doing a secret. They have their own business model and they provide the tools. They let you play as much with the solution as you want to.

The interface is also more user-friendly than the other products for creating automations. In fact, I didn't use the other tools very much. In total, we evaluated them for two months, although this time included installation, learning how to use the platform, and trying different automations. Ultimately, based on everything, we chose UiPath.

We tried to compare the products while we were creating simple automations and on every point, we found a huge distance between UiPath and the other tools. For example, the interface was much more intuitive than the other two products.

At the time, UiPath wasn't as big as the other two solutions. However, it had a lot of potential for growth. This was another point that my boss took into consideration when making the decision.

Since the beginning, UiPath has been trying to work out a partnership with Google, including the main tools and main services. For us, and from an enterprise perspective, that is very good. We expect UiPath to grow a lot.

If we have a server and a good investment in machines, virtual or physical, then we don't have anything to worry about. 

As I continue my career in RPA, what I understand is that it's the beginning of a new industry. It's like an industrial revolution, but for automation. When we began with use cases in accounting and banking, it was all related to numbers and we were always using structured data. However, today, we are using things like chatbots. We are also expanding into AI use cases and UiPath continues to grow to include new capabilities and functionality.

In the next ten years, I expect there to be a huge demand for automation. This will be in every kind of enterprise, as well as our day-to-day life. One example is the smart house, with implementations for domestic processes.

My advice for anybody who is implementing UiPath is, firstly, not to panic. It is a new way to develop and understand your business model. Second, do not go too fast. Sometimes, the easiest way to develop robots can lead you to forget about your basics and best practices. Third, bring a strong internal framework, including your business model, best practices, and internal documentation.

It's crucial to be able to scale up in the future, so be sure to consider your larger processes at an early stage. Don't look at things in a traditional way. For example, you can use Python for automation, which is a very open framework, but Python doesn't let you do all of the things that you can do with UiPath. You need to follow a more structured coding approach. Essentially, you always have to be organized and try to take things step-by-step. Otherwise, you will have an internal fight between robots in your Orchestrator.

I would rate this solution a nine out of ten.