UiPath Reviews

We are using Studio, Orchestrator, and mostly the unattended bots.

Our primary use for this solution is to give time back to the employees.

We do not run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. It's drag-and-drop, and all of the activities are there.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. All of this information there is self-explanatory and it works. 

From the point where we started using the demo version, it was a couple of months until our first robot was ready.

This solution has probably helped to eliminate human errors.

I can definitely say that this solution has saved the organization time. With all of the processes together, we have saved one full-time equivalent person. 

The most valuable feature of this solution is the unattended automation.

This solution is easy to use and it saves you time.

In future releases, we would like to see more drag-and-drop, and more out of the box AI.

With respect to the stability, on a scale from one to five, I would rate this solution a four. We had some issues where we needed to get in contact with the support, and sometimes, UiPath crashes on our servers.

We have about eight people in our automation group.

Most of the time, the technical support for this solution is very good.

One one occasion, it was not very good. We had a problem with a new version. When we updated to 18.2, the robots stopped working after some time. We had a lot of emails that included session logs. I made it quite clear that it was really important because we were in the beginning phase and the robots had to run. In the end, I fixed the problem by downloading the next version, 18.3. When we asked whether the problem was version-specific, they never got back to us, which isn't very good.

We did not use another RPA solution before this one.

From the external consultants, we got the idea that RPA has the possibility to save us time and money, so we decided to do it.

The initial setup of this solution is straightforward. Orchestrator is easy to understand. You can connect the virtual machines to it and then run the robots.

In the beginning, we used a consultant from Roboyou to assist us with the process. Our experience with them was good.

We recognize ROI in terms of performance benefits as soon as a process is automated and an employee can do something else that is more meaningful. It is not a benefit listed on a spreadsheet, but the employees are happier.

Our licensing fees for this solution are €68,000 (approximately $75,000 USD) yearly.

Two years ago, we evaluated Automation Anywhere and Blue Prism, in addition to UiPath. UiPath was the best overall solution then, and it still is now. It has a big community, and you can download the demo versions to start testing immediately.

This solution saves us time in all areas. We don't keep track of exactly what we have saved in terms of time, but we can say that we have more customer experience. If somebody has a mundane task and wants it automated then we do it.

My solution for anybody researching RPA solutions is to try UiPath. When you want to start, it is easy to register and get going.

This is a good solution and it saves us time, but there is always a path for improvement.

I would rate this solution an eight out of ten.

It is looking externally at how we can enable the government to identify efficiencies and improve effectiveness. The other is, internally, how can we drive efficiencies within HR and finance, with everything that a big corporation can do. 

1. How do we help the government realize these benefits? 
   
2. How do we help our internal workforce benefit?

It is two different things, and they are similar, but they're not the same thing.

A lot of people externally are worried about the elimination of jobs, but at the same time, they still want that efficiency, and they are looking for it. We want to drive the effectiveness of the workforce, whomever we're working with. 

There are plenty of automation opportunities out there: DoD, the federal government, and commercial space. There are all sorts of stuff that we can do. Internally, we feel the same way. There are lot of things that we can do to make ourselves run more efficiently. If we are preaching to the government that they need to be using this, it's beneficial for us to say, "This is what we have done as a company."

Our company is 25,000 people across the globe. There are certain opportunities for us to include automation in what we do every day. We are doing it now by instituting RPA, specifically, and the tools that the UiPath bring to the table. It will be a game changer for us, if we can get it done at scale.

Automation is growing at our company. A lot of what we do is focused on AI. Going from zero to AI is a Herculean task. It's extremely difficult. However, there are many steps in-between zero and AI that we can do now to help realize the benefit to the company or the federal government, such as the benefits of the efficiencies that we can identify. That intermediate, non-threatening first step can be RPA, which ultimately will lead to enabling AI, but is not AI. 

Within our company, we are looking to identify what those pre-AI steps are, with the goal in mind that we know that the federal government is asking for AI. What we do in the interim is a type of level set, where you can build an algorithm, AI, or machine learning algorithm. This ultimately is what they want, but what they need right now is to aggregate their data in a structured way to be able to feed into those algorithms. That's step one. This is the first step to getting all your data right. It's not easy, because you have to take people out of the mindset of AI.

A lot of times, in the government, people say, "I'm wearing two hats." It's an idiom. The question I have in response is, "What if we could take one of those hats away?" We can take one of those responsibilities that someone finds cumbersome, or annoying, and remove that from their task list. We have them tell us the steps of their process, so we can automate it, if not pieces, but all of it. That is our starting point with a lot of people, "We can take this off your plate," which is definitely exciting for a lot of people. It scares some people too, but we're working on that.

The most valuable features are the unattended bots. Initially, we are going to be looking at a number of attended bots in a pilot phase for our HR internal operations personnel. We are going to come in and try to remove tasks from their daily lives, such as ten minute tasks brought down to five seconds, or we could just completely eliminate them, making them unattended.

The training and certification online is very helpful.

The software is easy to use, as a drag and drop function. Even if it wasn't, the type of support that we get from the people who work for UiPath is paramount to the capability of the tool. The ease of use has exceeded our expectations.

The Academy Live that I took was only a half a day course. There needs to be diverse set of courses for those introduced to RPA for the first time. There are different people who show up to this course: 

• The developer who is interested in automation and automating different facets of the tasks that they have, either at work or for their clients. 
• Business managers who want to know more about what RPA can do for my business or company. They want the operational and strategic level versus the tactical level of how do I get automation to do the thing I want it to do?

The course was only a half a day, and although we were able to provide two automations and build two bots, it would be helpful if that was extended to include the RPA story and pitch. E.g., What's the story that we need to tell in order to get people to say, "How do I get into the pilot phase now."

I would like to have the course do an introduction, "Welcome to the course. This is what RPA is. Now, let us build your first bot." 

The sales elements of why RPA should be there too:

• What is the value proposition that RPA brings to the table.
• Here is the expected ROI for a menial task, saving an hour a week equals this in the long term. Even if you can cut a 25 minute task out of somebody's daily routine, this is the benefit in the long term.
  

That wasn't there as much. I wasn't really expecting it to be there, but in the long term, if there are a number of different types of training courses which are offered, people will have different breadths of understandings of RPA can really do, e.g., it needs a hardcore developing training and a capture manager. It needs to explain what sort of things a capture manager needs to know. Maybe not necessarily how to develop the architecture for it, but what does that even mean? For example, how easy is it for me to get Orchestrator onto a server? How do I become a reseller of the software? These are the capture manager responsibilities, and it would be helpful if they were explained. While this is probably more of a day two of a training rather than day one. 

I would like to see a UiPath user group to discuss issues. I am unaware of all the activities and features, and this would help. Right now, there is just the user's guide and UiPath GO! It would be great if this feedback went back to the UiPath development team. We should also be notified of new features through an alerting system on UiPath GO!

With our focus on the federal government, they're looking at dozens of bots: Scaling of five instances of Studio, 10 bots of Orchestrator, and three unattended bots. That is far easier to scale than in the commercial world, where they are asking for 1000 instances of Studio and 500 unattended bots, touching 100 different processes. We haven't had that experience yet.

The current staff at UiPath won't let you fail (the customer support and customer success managers). They are not going to leave you hanging.

They are an honest broker. They told us when things aren't going to work. They've been upfront and transparent about everything with us.

Our developers have found that it is relatively straightforward. With any installation issues that have come up, we have always had somebody just be able to pick up the phone and call.

ROI depends on the complexity the project. Unattended bots tend to see ROI immediately, where attended bots take longer. The savings starts as soon as a bot is deployed.

Getting licenses has been relatively easy.

We have all the prices for the software. Every project is up for a negotiation on how it's going to be done. A lot of times, with the federal government, it will be necessary to put it on contract. When we are bidding for something, we need to know, how many bots are we talking about? The tricky part is when the government is unsure what they actually want. A lot of times when contracts or proposals are put on the street, the government wants something that can support 100 bots. That's not really helpful given that the price points for unattended and attended are different. So, clarification is often necessary when we're asking, what ratio of attended to unattended are you really asking for?

There is some initial sticker shock from a lot of people regarding cost, until you show them what the actual benefit is. Initially, people are just going, "Why?" So, the retort for that is, "Look how much you will save, time, and budget-wise with one bot. If one bot costs X, this is how much it will save you over one year. This alleviates the "Oh my gosh" face, when it's 1200 dollars for a bot. 

Getting clients, and our own people internally, to recognize that this is an investment in efficiency to drive effectiveness. If you can do that, and you can get past any initial sticker shock, thinking strategically and long term, then you've got them. But if they say, "Look, my budget this year is only 10,000 dollars. Why would I put that into bots?" That becomes a different type of discussion. It's mostly focused on, you're thinking about today. We need you to be thinking about three years from now.

If you look around at the other software systems, we have chose to go with UiPath because of the ease of the interface and also the customer support that we get from their people. There are a lot of tools out there. The reason why we have gone with UiPath is because of the relationships that we have built and the type of success that we are going to get working with their account leads.

We looked at Blue Prism, Automation Anywhere, and briefly at a couple of the start ups. However, we figured that they didn't have the ATOs that we needed to go within the federal space. There are a lot of people who say they can do this, or they say that they have an offering that can do this. In many cases, that is absolutely true. We wanted to be with a company that we feel is up and coming and will be around in the next decade. We want to use software that is going to be recognized by the federal government as number one, or at least very close.

Be prepared, because you are going to be asked a hundred question. This product takes a team. Your senior management needs to want this product and sign onto training. You will need developers capable of using the UiPath software.

UiPath is not just a technology business. It really comes down to a people business. The people and culture that UiPath provides us leads us to use their software more often.

The NextGen workforce is not going to be cutting and pasting for eight hours a day. That is not a function that a human should be doing anyway. Therefore, we treat RPA as a digital assistant, because who would not want a digital assistant.

People are finding ways to automate the reporting functions that Workday can really provide. This is not at an individual level. At the individual level, you can go in and check your benefits and check your 401K. However, at a macro level, we need people to run Workday reports pretty much daily, and that gets updated in the systems that we have. Therefore, our HR and finance people are all working with Workday, as people of incorporate these big management systems, trying to find new ways to automate them.

It is now on us and our team to be able to implement automation with the Workday, and have it work more efficiently. That will be our next challenge moving forward, automating Workday.

For two years, I have focused on automating workflows related to processing documents in formats like PDF, Excel, and CSV. Using the document understanding feature, we have handled forecast orders and purchase order invoices. 

If you use input files like Excel, PDF, and CSV, we can automate file validation, such as checking data accuracy, format compliance, or missing information. It's integrated with Boomi, so after the files are validated, they're sent to Boomi for further processing. 

Boomi provides us with the RTF file, and we use UiPath to validate its contents and correctness. It automates the process of converting the RTF file into an Excel file. Another process is remittance, where we can get files from clients, validate them, and submit them to the credit managers for correction.

UiPath reduces human error by eliminating manual work and intervention. Some human intervention is still necessary, but it has been reduced. Realizing UiPath's benefits takes some time because you may have some issues after the initial deployment. The UiPath Academy was helpful. I took some courses and achieved developer certificates. I'm still learning. 

It hasn't saved time in my work because I'm still spending a lot of time learning the software. It was new, so learning and implementing those things in my work takes time.

My favorite feature is Document Understanding. I haven't used most of the new features, such as AI-enhanced document processing and process mining. The document understanding feature is especially valuable because I can use it to extract and process invoice data efficiently. It enables the quick and accurate handling of structured and unstructured data. 

The flexibility to work with templates and machine learning models for document extraction has been helpful when dealing with various invoice formats and forecast orders. Data extraction from PDF has been smooth, especially with UiPath's capability to handle scanned documents using OCR and AI-based models. 

The taxonomy manager lets you define the structure and categorize data from multiple document types. AI center integration allows continuous improvement in document extraction accuracy by training models based on historical data. I have utilized AI and machine learning models in UiPath specifically for processing complex PDF and Excel documents. 

UiPath's AI capabilities, such as pre-trained invoices and receipts models, have effectively extracted structured and unstructured documents. For example, when processing purchase orders, the AI model identified key fields, such as invoice numbers, dates, line items, and currency details, with high accuracy. I have found the machine learning models to be especially useful when working with documents that have different formats. In some cases, additional training or validation was required to fine-tune the models for complex or irregular documents. Overall, AI models and document understanding are my favorite features.

UiPath is highly user-friendly because it has drag-and-drop functionality to design and develop complex workflows without much coding knowledge. This has been particularly beneficial when working with different document formats. UiPath's built-in tools and integration capabilities simplify the automation process, leading to greater efficiency.

We have end-to-end automation and integration with other applications. For example, we have portal automation that's end-to-end. We use it to log in to the website and sign in to different accounts. It enters the CAPTCHA, downloads the files, and logs out. It can complete the automation without human intervention. 

UiPath has many resources online. We use its academy and online documentation. If we face any challenges, we can find an answer on the forum or one of these resources. I've never had a problem finding solutions to problems. They have the best resources.

I would love more integration with Third-Party applications. Expanding the library of pre-built, plug-and-play connectors to include more industry-specific applications.

I have worked with UiPath for two years. 

I've never experienced lagging or crashing with UiPath. The app has never given me trouble. 

Installing the community version of UiPath was easy and only took five to ten minutes. 

I am using the free community version. The enterprise version is obviously a little expensive. 

I'm using UiPath on an automation project for my company in the banking domain. The use cases are for things like insurance claims and debit card transactions. We use it for our clients' requirements and also internally to address any of our company's needs for UI automation. 

When we started the client's project, they had a simple process, but they were dealing with a large volume of data. Most organizations primarily rely on Excel as their main solution, and they're doing processes through that. They wanted to automate Excel processes that they had been doing manually. UiPath improves productivity and saves time. For example, I developed a bot for processing insurance claims in UiPath. It involved checking documents and comparing them to the information in the databases. The process would take around 40 minutes to perform manually. We reduced that to eight or nine minutes per process through automation. It greatly increased the volume we could handle, producing a lot of value for the organization.

As we developed more automations for Excel, their manual work decreased, so they gave us more requirements. I've developed about 15 separate processes for the banking project I'm working on. Each process has its own way of doing it. We have developed network solutions. UiPath has contributed so much to the development of automation in our company. Our clients are pleased because they can boost their revenue by introducing bots.

UiPath has helped us reduce our on-premise footprint. The development cycle depends on whether it's a major or minor process. We start development, test, and deploy. After that, a support team will maintain the process, and we will not be involved again. We have multiple people working on a particular project, and it changes with every sprint of a cycle.  

UiPath Academy has lots of videos and other resources. While we can go to YouTube or some other source to learn about UiPath, we don't get a comprehensive understanding of the solution or the latest features. We can only get this through UiPath, and everything we need is in the courses. You can take a foundational course to learn the basics and get a certification that is valid everywhere from the advanced developer courses. Every company expects its UiPath developers to have this certification. 

UiPath's AI functionality is useful if we're working with unstructured data. For example, if we have a PDF where the data we want to extract is not separated, we can use AI to define the data for automation. I have done some practice use cases for learning purposes, but I haven't used AI in a project.

The solution helps to speed up digital transformation. I'm not sure about other countries, but many banks in India are still doing things manually and not using UI automation. This is a revolution in banking technology because bots are doing everything, and they don't need a lot of people to do the tasks.

UiPath can reduce human error, but a developer needs to understand the process completely that the bot will perform and provide all the conditions for how to perform things. After the client approves a project, we create a bot, and it will function based on the solution documentation. The UiPath bot will perform whatever conditions I give it. About 80 percent of the solutions we develop will complete the process without human intervention, and the remaining 20 percent of automations require some manual effort.

The solution frees up employee time because UiPath doesn't require much coding knowledge. If we can find a working solution for many purposes, we can download it. We don't need to spend time developing as many processes. 

I like UiPath's coding engine. We don't need to know much code. Most of the activities in UiPath are drag and drop. It's easy to build automations in UiPath. If we need support also, that doesn't require much effort. The UiPath tool gives us a structured framework. That is used in almost every project I work on. It made our development process effortless. We've completed a lot of projects with the help of the framework. 

The UiPath community enables users to share knowledge and bots that they've developed. If I have a bot installed in our machines, it doesn't require much effort for other users to run it. The user experience is seamless and user-friendly. Everything is ported on the back end, and it works as expected everywhere. If we have any doubt about a topic, we can post a question on the user community forum, and people from around the world will offer solutions in minutes. It takes very little time to get the solution. 

We only use the UiPath Community for support. It would be nice if a team of developers or a support person were available to help us work internally on our project. That would be helpful.

I have used UiPath since 2020.

UiPath is stable. All of my colleagues in other companies feel that this is highly stable compared to other tools.

UiPath is scalable.

I rate UiPath eight out of 10. We primarily get support from the UiPath Community, but sometimes their solutions work differently when we take it to our machine sometimes we have this capability. 

Positive

I also learned Automation Anywhere at the same time, but I found that the UiPath interface was easier for beginners to learn. 

We use UiPath as a cloud service. You create packages that are deployed through Orchestrator. Any machine with access to Orchestrator can just download the package and run it. The deployment is straightforward if we have the necessary access. We need to add a package to Orchestrator and download it. It doesn't require much time. 

We have a team of people. Every deployment includes developers, a support team, and an engineering team that will deploy the code to the production machine. The support team will ensure the bot is running properly after deployment, while the developer is the one who creates the package. UiPath doesn't require much maintenance aside from upgrading the bots with packages from UiPath. 

The pricing model is based on the number of processes. My colleagues tell me that UiPath's pricing is pretty normal compared to other solutions. 

I rate UiPath nine out of 10. I would recommend it to anyone who is interested in RPA. It's easy to learn and implement. You will not be disappointed. I still have a lot to learn. There are so many capabilities. 

We are using UiPath for office automation for our clients. We use many activities of UiPath. We are using CV, RegEx, Excel automation, and email automation.

We are working on a project for a billing company in the US that takes care of patient records for a hospital and saves them on a website. We are handling the patient billing system. We have an email as input at the start of the automation. The bot reads the input. In the input, we have the patient's name and date of birth. The bot searches the patient's name in the EMR hospital application and gets the PDF from the application. We have put some filters on the application. In the PDF, we have a patient's details and a record of their visits and the issues they are having. The bot then uploads the PDF on a website.

We process multiple records. There could be 2,000 pages or 500 pages. It varies based on the patient. For example, an 80-year-old might visit the hospital once or twice a week and will have a bigger file with notes and pictures of their visits. We follow HIPAA regulations for extracting patient information.

It is very fast and convenient. Bots give you 100% results and work 24/7. Humans work eight hours a day, but bots can work 24/7 for you. They save time and bring efficiency.

UiPath brings accuracy. It gives you 100% results. When we do things manually, there can be human errors, but bots do not make any errors.

In the last two to three years, we have done millions of processes. If we give this work to a person, it will take that person ten years to process. For automation, we are using multiple instances and virtual machines. If we need more processing, we can use more VMs. It saves time, and it works 24/7.

It has been a good experience. UiPath is efficient and fast. There are multiple RPA solutions, but UiPath is very user-friendly. It is very easy and fast to learn. We do not need to know how to code for UiPath. It is coding-free. We just have to make a logic. We just need to know the basics but not the advanced things.

UiPath saves a lot of time. Bots are ten times faster than humans.

UiPath APIs were helpful for extracting data from the website and doing the work very quickly. We could get the data directly from the website database. It did not require going to the website, typing the URLs, etc. We could directly send a request to the website and get all the required data.

I have used Document Understanding a little bit for extracting the data from the PDF and images. Document Understanding machine learning capabilities, but I have not used it much. Other teams use it, and the feedback is that it is very effective and fast. They are probably using the Enterprise version for Document Understanding. 

There are two things that are very useful. The first one is RegEx, and the second one is LINQ. UiPath is giving us Excel activities, but it is very slow. With LINQ, we are extracting data from Excel in a very quick way. It is very easy and very fast. RegEx is helpful in quickly getting specific data or text from a chunk of text.

We are also using CV. It is very useful because it uses an image for clicking and extracting data.

If we want to learn something new about UiPath, we sometimes cannot learn it directly from the UiPath Academy. We have to go and search on the web. It takes a few searches to find the solution. We do find it, but it takes time. UiPath should give the solution in one area.

I started in 2020. It has been three years since I have been working with UiPath.

It is stable. They are updating things, but it is stable with the previous code.

It is very scalable. The scalability part is very good.

We have a small team working with UiPath. There are five to ten people.

We have not contacted them much. There was an issue one to two years ago, and we contacted their support. They gave us a solution.

I have used Automation Anywhere, and I have also used Power Automate a little bit. 

In Automation Anywhere, we cannot use CVs. Maybe in the enterprise version, we can use them, but I did not see CVs and other activities in Automation Anywhere. It is also web-based, which is not a good thing, whereas UiPath is application-based.

Power Automate is a very useful tool for Excel automation or web automation, but UiPath is the best for our needs.

UiPath is very fast and convenient. It gives 100% results. It is very easy. If needed, we can also use Python or JavaScript code to make a logic for automation.

I was not involved in its deployment. For maintenance, we just update the UiPath version. We have not had any issues.

As RPA developers, we use UiPath to create automation and then we hand over the bots to the support engineers. They oversee the processing in Orchestrator. They see the automation logs and the graphs. If a bot is not working properly, they send us a message to fix it. We are using CV. If the image changes, our bot will give a failure, and we have to fix that. We might get an error once or twice a week.

I am using the Community version in my office and personally.

I would recommend UiPath to others, and I would give it the best rating. I have used other tools, but UiPath is my preferred tool.

I would rate UiPath a nine out of ten.

We use UiPath primarily for tracking purposes. We are a logistics provider and have external portals and websites. The tool aggregates information from these systems to our core application. 

We leverage the whole platform. The tool's most valuable features are unattended and attended robots. 

We have to change our account representative every year, which is frustrating. We have to re-explain our business every year. 

I have been using the product since 2020. 

UiPath is stable. 

The product is scalable. 

Support becomes frustrating when the team asks about the cloud and organizational details. 

Positive

Our implementation strategy involved choosing a small use case first, improving the value, and accelerating. 

Two to three partners helped us with the implementation. 

The product is worth its money. We have seen an ROI of 274 percent. 

UiPath is not cheap. 

We evaluated Automation Anywhere and Blue Prism. We chose UiPath because I was familiar with it, and the local representative didn't have a sales pitch tone. 

There is a gap in the marketplace for tracking specialized services. UiPath was the only way to achieve it quickly. 

AI-powered automation has fundamentally changed our organization. We have repurposed the hundreds of headcounts and enabled them to focus on more meaningful work. 

UiPath AI Center has grown and evolved from what it was. We are looking at more opportunities since the person who managed it has left the company. 

We are still trying to figure out AI's use in our operations. It brings in efficiency, but we are in the process of validating it. 

AI use has sped up our time to about 256,000 hours a year.

We have only started to use process mining.  

We use UiPath for invoice processing and PDF extraction.

Building automation using UiPath is extremely easy. Everything required is available online.

UiPath enables us to implement end-to-end automation, which is the most important aspect for us.

The UiPath User Community is strong.

UiPath has helped us to minimize our on-premises footprint. We are using an on-premises orchestrator and working in the financial services industry, where we have to process 30,000 invoices per day. This would normally require a lot of manpower, but with UiPath, we are able to do it with only five bots.

We use the UiPath Academy courses and my team recently received the AI certification.

We use the AI functionality in UiPath to help automate more processes overall. 

UiPath helps speed up our digital transformation.

It has helped reduce human error a lot.

UiPath has helped free up our staff time by automating the manual work and saving our resources. 

The Orchestrator feature is the most valuable of all the automation solutions I have used, including OpenBots, Robocorp, and Microsoft Power Automate. It is essential for managing all of the processes in UiPath.

The UiPath Academy Orchestrator training needs to be updated to reflect the recent changes.

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

UiPath is stable.

UiPath is scalable.

The price for UiPath is on the higher end.

I would rate UiPath ten out of ten. I have used five other automation solutions and UiPath is the best.

No maintenance is required.

The development, scalability, and reliability of UiPath are the best, and I recommend the solution 100 percent.  

UiPath is an end-to-end automation tool that helps businesses accelerate their processes by providing solutions for automating routine activities. These solutions enable faster and more efficient business exchanges.

UiPath offers a user-friendly automation building process utilizing a drag-and-drop workflow feature for UI automation. Additionally, the platform includes recording capabilities and a playback feature to ensure accuracy. Advanced scraping options are also available for more complex tasks.

We utilize UiPath to automate processes that relate to good causes. Our approach involves creating a playbook task and subsequently automating the process. After that, the IT department assists us in collecting and interpreting data from various applications in the UA portion.

UiPath's automation capability is important because it saves us a lot of time. There are two sides to consider: the client side and the server side. On the client side, the UI allows developers or data users to communicate directly with the system. This can be done using tools such as RobotStudio or data browsers. Essentially, these operations can be seen as back-end tasks. On the server side, tasks and workloads generated by the user are stored in SQL databases.

UiPath has minimized our on-prem footprint.

The UiPath Academy courses are beneficial. 

The AI functionality in UiPath helps us save time by streamlining our workflows within the studios. Additionally, it enhances our automation capabilities, speeds up order processing, and enables us to make better decisions, ultimately reducing the risk of errors.

The automation has saved us between 70 and 80 percent of our processing costs.

UiPath has freed up employee time and increased productivity.

The screen recording feature is valuable.

The data team support that provides the UI and the chat services has room for improvement.

I have been using the solution for six months.

The solution is stable.

UiPath is highly scalable.

The technical support is good.

Positive

Before, I used Blue Prism, but now at my new organization, we use UiPath. Unlike Blue Prism, which only specializes in back-end applications, UiPath works with both front-end and back-end applications.

I give the solution a ten out of ten.