UiPath Reviews

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.

I use UiPath for a variety of tasks, including automating user interfaces, processing documents, utilizing process mining, performing test automation, and even handling natural language processing.

It contributed to revenue growth by enabling us to maintain a consistent headcount and resource level while expanding our business.

Unattended automation, particularly in the realm of UI automation, is the most valuable aspect. 

Its ability to swiftly create automation in UiPath Studio is highly beneficial. It's highly effective in pinpointing areas within the organization where assistance is required.

There are several areas where I see room for improvement in the tool. One of these areas would be a more solutions-oriented pricing structure. This is because the platform requires a multitude of building blocks even for the simplest use cases and when dealing with newer clients, this can be challenging. One area where I'd appreciate additional or new features is in the realm of insights.

I have been using UiPath for seven years.

It offers good stability features with minor bugs from time to time.

When it comes to scalability, UiPath exhibits a high degree of proficiency.

The customer support is quite commendable and we often make use of TAM when needed. I would rate it around an eight out of ten because there is room for improvement.

Positive

I've previously used a variety of automation tools, including Blue Prism, OpenSpan, Automation Anywhere, WorkFusion, and Microsoft Power Automate.

The initial setup was straightforward.

I collaborated with my IT teams to establish high-availability virtual machines in Azure, whether on-premises or in a semi-private environment. I also partnered with my security team to formulate our digital worker strategy, which essentially involved managing identities, and I integrated all these components into a cohesive system.

It comes with a high cost, but the value it delivers justifies the expense.

We conducted evaluations of various automation platforms, including Automation Anywhere, Kofax, Pega, and Blue Prism. There were several notable distinctions. Firstly, UiPath stood out because it offered a free starting point, which was not the case with the others. Secondly, UiPath's integration with Visual Studio was more seamless compared to the other platforms. Their open and free-for-all community is an enormous advantage.

My advice would be to keep your problem-solving approach simple and avoid the urge to plan every detail. One common issue I've observed is people tend to overcomplicate the deployment, strategy, and overall decision-making process when adopting a new software platform. Instead, I'd recommend that if you can identify one or two use cases where the tool's benefits outweigh its costs, you have a solid starting point. Keep it straightforward, and you'll be on the right track. 

Overall, I would rate it ten out of ten.

Our company, Block Mosaic, automates the creation and management of DeFi (decentralized finance) applications. This involves streamlining the development, deployment, and maintenance of these applications by automating repetitive and rule-based tasks. UiPath enables us to automate tasks such as data collection, communication with customers, integration with blockchain networks, and the execution of smart contracts.

We mostly use UiPath for the integration of bots in websites, as it provides integration features for AI chatbots, and we use it for the deployment of smart contracts on a large scale.

Automation not only accelerates our application development but also reduces errors and increases operational efficiency. It has accelerated our development process, and that means that our time-to-market has improved for DeFi applications, giving us a competitive edge in the fast-moving blockchain sector. It allows our team to focus on innovation and improving the user experience of DeFi applications.

UiPath is very important for our organization. It improves the workflow of our company, and it helps our company publish more DeFi applications. It helps accelerate the process of managing accounts in our company, as the DeFi applications we create are for managing many accounts on a platform.

It has helped with cost-cutting because UiPath chatbots have replaced many of the employees. The employees were not that efficient in comparison to UiPath bots. The bots are very efficient and productive and can do tasks in just minutes or hours, things that used to take a lot of hours to do.

We have also used the AI functionality by integrating AI chatbots into our website using UiPath. They help with amusing chats with our users for their entertainment. Our users do not like the simple Python or bots that are made with C++. They like modern bots like ChatGPT, so we have implemented that.

AI has played a significant role in improving our efficiency. Tasks that a person used to do in hours are completed by AI chatbots in a shorter time. Also, human error has been reduced when compared to bots. The bots are highly efficient. The AI functionalities have helped us manage all the smart contract deployments as well as the management of our user base. It has also helped with database and account management and in settling many transactions. And it has boosted the number of KYCs that are managed per unit.

Deploying most of the smart contracts and managing our user base are now done by the UiPath bots. This saves us about 30 to 40 percent of our time and gives us time to think more creatively about our solutions for making better DeFi apps and improving their functionalities.

Another benefit is that UiPath has reduced the cost of digital transformation because our projects require a lot of web services. We have saved money by using UiPath instead of cloud services.

One of the best features is the workflow automation. That is the most valuable feature for our company, as it plays a pivotal role in the efficient development of our DeFi applications. In the dynamic world of DeFi, where integrated financial processes and smart contracts are the norm, UiPath's workflow automation capabilities provide us with a valuable advantage. It enables the orchestration of complex sequences of tasks involved in DeFi application creation, from smart contracts to blockchain transaction monitoring.

By automating these workflows, we can ensure that all components work harmoniously and efficiently and reduce potential human error.

UiPath is also a very easy platform to use. It provides us with a canvas where we can draw from our imaginations, draw our settings, and then convert them to automations.

It allows us to enable end-to-end automation.

The user community of UiPath is very big and very helpful as well. When our team hits an error, the community is sometimes very helpful. And the customer support we are getting is also very full and good. I am satisfied with the community. I would rate it 10 out of 10.

The debugging capabilities need to be improved in UiPath because it is very difficult to find bugs in the chatbot. In Visual Studio Code, by contrast, we have an excellent debugger that fixes all the bugs.

Also, task management is complex and needs to be improved. They need to simplify the user interface so it can work properly.

I have been using UiPath for six months.

It offers a great amount of stability, and the team at UiPath is adding more and more features that are increasing the stability of the platform.

UiPath demonstrates excellent scalability with its consistent addition of features. It's impressive to witness that it remains current and continues to evolve and incorporate new capabilities. I rate the scalability at nine out of 10. It offers a great deal of scalability.

I used Blue Prism, which is quite a good solution, but it's not as easy as UiPath because it requires a high level of coding. UiPath offers good drag-and-drop functionality, which results in better automation. Also, there is no orchestrator in Blue Prism.

Automation Anywhere does not have the features that UiPath has. It does not have as good a web-based orchestrator as UiPath, which manages all the accounts and services.

Deploying the system took a couple of hours, done by a team of three to four people.

It doesn't require any maintenance.

After implementing UiPath, our organization realized a substantial return on investment. This was achieved through a combination of cost savings, increased productivity, and improved accuracy. We quantified the cost savings from reducing labor expenses and eliminating error-related costs. There is also ROI from optimizing overall operational efficiency.

Furthermore, UiPath automation capability significantly improved productivity, allowing us to process more and more transactions, take on more and more customer needs, and respond to the customers as fast as possible. We have been able to handle the increased workload. This has translated into enhanced customer satisfaction and market competitiveness.

By automating error-prone tasks, we also saw a remarkable reduction in errors and compliance-related issues, leading to further cost reductions and process efficiencies. After factoring in deployment and maintenance costs, we calculated a positive ROI, and the payback period for our initial investment was achieved in a very short timeframe.

We've seen about 30 percent ROI through the growth of our company.

The price of the Enterprise version is high, and the licensing is very complex. For small businesses like ours, licensing is a very complex task and takes too much time. I face many issues with that.

All our people, about 50 to 60 staff, use UiPath because we do not have an alternative. There is Blue Prism, Automation Anywhere, and Microsoft Power Automate, but UiPath is the best solution. The only issue is that the pricing is higher, but it has all the features that make it worth it.

UiPath has reduced a good amount of human error, but there are some errors that the chatbots make. They are resolved within seconds or minutes, although longer ones can take hours. But overall, the bots make many fewer errors and increase efficiency. It has removed about 80 percent of human errors. Since using UiPath, we have gotten good customer reviews about the websites and improvements in all our sites and management.

Using UiPath has been a great experience. It's the best alternative on the market. No alternative is better than UiPath.

I use the solution with different customers. Sometimes it's used for financial organizations, or for accounting or ecommerce. It can be used for mortgages, or loan processing for example. 

We use the automation a lot. 

It's very good at document understanding. Training machines and utilizing machine learning models is very easy compared to other models. 

The product offers easy integration with APIs. 

It helps with email automation and PDF automation.

It is easy to build automation using UiPath in comparison to, for example, Blue Prism or Power Automate. 

We use it to implement end-to-end automation. Internal automation is rather important to me. It's something the customer needs. There are multiple processes that are automated and involve API integration as well as document understanding. At the final stage, we'd need reporting as well. 

The user community of UiPath is very good. We have access to partner portals and learning portals. The forums are also very good. They have a good support system. If we get stuck, we get extremely helpful answers. In the community, there will be videos about new features coming out and will show the use cases. They show their plans in advance, which is very helpful.

I've used the UiPath Academy classes. There are lots of courses and I have an advanced certificate. The biggest benefit is having some training rather than going into the product and trying to learn it by trial and error. You can either get basic knowledge or do a deep dive. It gives you options to go as deep as you want.

We use AI functionality in our automation program. We use machine learning models, for example. Document understanding uses AI as well. It helps us automate complex and difficult processes. If I have to create complex logic or do some new API integrations, with the help of AI, it's easier. We can automate more processes overall. As you train the machine learning model, and do the right test cases in the right way, it begins to work really well.

It has helped to speed up digital transformation.  

The solution has helped us reduce human error. It's helped prevent us from fixing errors and reworking things. It also helps remove people from mundane tasks. It's helped people save time. How much time is saved depends on the process. Sometimes some human intervention is still required, however, it can typically save three and a half to four hours. 

The cost can be a barrier. Power Automate from Microsoft, for example, comes at a lower cost. 

The automation hub and the architecture around test cases could be improved. They should offer more videos that would help us implement various scenarios. We'd like to see information about use cases specific to different industries. If there are use cases that have worked at different companies, we'd like to be able to see them to learn from what others have done to help us grow our business as well.

I've been working with the solution for the past seven years. 

The solution is very stable and good. 

The solution is quite scalable. It's no problem. With architecture on the cloud and the fact they support VMs and Azure, there's no issue with scaling. 

I used to contact support a lot. I don't do it so much anymore. 95% of the time they are very good. There have been times when we have faced roadblocks, however. 

Positive

I've used Blue Prism in the past and I am exploring Power Automate as well. Power Automate is expanding quite a bit. It's very good. The UI isn't quite up to the mark. It still has limited features, however, it is easy to use and the price is good. Blue Prism is still a very complicated tool.

I've been involved in the initial setup. I've created things in the development and test environment and then moved them to production. The process could be improved a bit. It would be nice if there was a button you could click to replicate across environments. 

We have senior developers that can handle the setup and integration process.

As consultants, we do not need to handle any maintenance tasks. 

We handled the initial setup ourselves. 

The pricing can be a barrier. For most clients, it is pricey compared to other solutions. However, it offers great features. 

I'd rate the solution eight out of ten. 

If a company has a lot of use cases where automation features are required, they should try UiPath. However, it depends on the company's requirements. 

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.

I own the robotics process automation program for our life safety segment. I also own the mergers and acquisitions project management for our life safety segment. We've started out by using UiPath specifically for mergers and acquisitions when migrating customer data from the acquired companies to our standard ERP. We're also implementing sales and use tax, filings, and things like that as well.

With our most recent robot, we transfer information from acquired companies to our ERP. Typically, it would take about six temp associates for about four to six weeks to clean the data and move it into the ERP. About three weeks of that would be actual data entry. With this product, we took that three weeks of data entry, times six people, and rolled it down to 12 hours of robot running. It was a pretty significant amount of savings for us.

Citizen development is great. With it, it's easy to develop or have self-developed robot intelligence. For example, instead of having to hire a developer, you can make the robots do what you need using the UAPs studio tool. This has been the most valuable aspect. StudioX specifically for our newer citizen developer is useful and I really like using Studio for myself.

We have seen a reduction in, for example, time, and not necessarily in human error. For example, we did an interesting analysis. We wanted to see what the human error rate was for entering data, and, due to the fact that our ERP is Microsoft Dynamics 2012, capturing some of that data is a little bit harder. We structured error rates based on entry. What we did was we created a robot to go back and check all their entries to see if they were missing anything. Oddly, the errors that people were making were nominal. I don't see any data that showed that we necessarily reduced error rates. It was really the people aspect of the process where there were time-savings based on the needed amount of human input. We've been able to reassign workers to more valuable tasks where we can't assign robots yet.

We do about four to five acquisitions a year and those are typically six-week processes for each one of them. We could say that we save about 25 weeks of labor in a year, and that robot will be about a week's worth of labor. Therefore, we save about 24 weeks of labor.

We've been taking some UiPath Academy courses. We've actually found it more helpful if we chose UiPath South American Developers to teach us to build as we're building. For my team specifically, it's been really helpful to have an expert involved to say "this is the use case that we want to do" and have them walk us through building a specific robot. That way, it's real-life experience versus a video-based session. While the academy is helpful, hands-on experience is just much more valuable.

UiPath Academy courses affected the process of getting employees up to speed. It affected it a little bit. It probably more affected our decision to use UiPath over Automation Anywhere, or even the Microsoft RPA program. Just the fact that there was so much available content that we could lean on if we needed to was huge. The others had content, however, not anything close to UiPath's capacity.

The on-prem orchestrator was an issue for us. When we bought it, it was a mistake. Our IT team thought it would be the best option for us, however, it's way more complicated to use. Out of the box, it feels more complicated. That said, once you get to know it, it's fine, however, it was incredibly hard to set up on our enterprise systems. Whereas, with the cloud deployment, we were live and up and running in an hour.  The initial setup took us about two weeks. That was a little bit of heartburn. It would be helpful if UiPath could offer some sort of support outside of a ticketing system.

I've been using the solution for about three months.

I've been pretty impressed with the stability. We've had a couple of minor issues that our developers helped us figure out. It's programming and nobody on my team are programmers. Some of it could be just user error, however, overall it seems like a very stable platform.

The scalability is really unlimited. It boils down to the organization's ability to implement a governance model quickly and successfully. I know UiPath has a governance tool or some kind of a framework, however, it is one of those pieces where it's way more expensive than us using our regular service channel tool that we already have implemented to do those submissions and approvals, et cetera.

In our organization, the users include two developers - me and then one of my assistants.

The only interaction we've had with technical support was during installation. The ticketing system and not being able to physically talk to somebody were difficult to deal with during the implementation process.

The on-premises implementation was a bit difficult. We knew that we were going to have to pay developers to help us develop the robots, however, getting stuff installed, our only method of support was submitting a ticket and the turnaround time on that took a while. Our UiPath rep helped escalate what she could. It would be ideal if there was a setup hotline or something that we could call right away. Sometimes it's just easier to talk to somebody than emailing back and forth. That's probably the biggest area for improvement.

We handled the initial setup ourselves. We do almost everything internally. We have our own IT team, including myself. Our solutions architects set it up with us. What we ran into in terms of problems was that the instructions were really not very good. We weren't able to appropriately install it as the instructions that came with it just weren't comprehensive enough. In terms of the instructions that were published online, we found a couple of instances where they were saying to use functions that didn't exist. These might have been a little out of date. Eventually, the ticket team was able to help identify that. I would grade the setup probably a C-minus, and everything else an A-plus.

We're so early into the implementation, the ROI is a wash right now. That said, our one robot has paid for our development time, and then someone will be able to use it on future acquisitions. We will likely see ROI within a year.

You can buy enhanced support, however, it's an additional $30,000 USD a year or thereabouts. That's just too expensive, honestly. The competition didn't charge for that. We also felt pretty confident in our IT team's ability to be able to dissect the instructions and install it. However, the instructions just weren't that good. We had one of our top engineers working on it and it took a lot of effort to get it installed correctly.

The pricing, in general, is fair. It's a little bit more than some of the competitors, however, it's a little bit more flexible than some of the others. There's value there. The OCR pricing is out of market. We need it, however, we're actually going to use some third-party bolt-ons due to the fact that UiPath is way too expensive.

We looked at Microsoft and Automation Anywhere. We also looked at help systems and Brick is one that we currently use and one of our segments, however, they're only a five-person company, which is pretty small. I wouldn't even put them on the same level. We were looking for shared services. We were looking for the best in class so we could take a solution enterprise-wide. In the end, we boiled the options down to Automation Anywhere, UiPath, and Microsoft, and UiPath was the winner.

In terms of Brick, they don't have a citizen developer model at all, so their developers have to do it. They are less expensive and they're a little bit more turnkey where they do it for you, however, they're really novice. The methodology that we've really bought into it was the community developer, as we want to empower our associates to figure out what works for them to improve their work-life balance. Using a service like theirs takes that away as we have to do the due diligence and figure out what fits in the bucket, what doesn't, as opposed to just empowering the person to do it. That was the key to why we chose UiPath.

The sales process was way better with UiPath. Our UiPath rep was far more knowledgeable about the product than the other options in that we ultimately had more confidence, knowing that whatever we needed, UiPath would help take care of, which was huge. My organization's a little bit disjointed. We try to go after what we feel is going to be impactful without a whole lot of due diligence. That's why, with UiPath, having that resource to lean on was helpful.

We use attended automation right now. Primarily this is due to the fact that the ERP system that we have really can't function unintended. It's a Citrix space environment and it has some odd security protocols where it'll shut down or refresh out for so many hours and it's not planned refreshes. It's hard for us. It's almost random. It's hard for us to build an unattended robot to deal with that. I'm sure we could, however, right now, we want to start with attended robots as we know what functions we need. We decided to go that route and eventually we'll add unattended.

I'd advise new users to make sure they have team buy-in for the concept. That doesn't mean necessarily getting the team to know exactly what they're going to be automating. You just need to make sure that they understand it's not about replacing people. Rather, it's about making their jobs easier. That was key for us. That said, most of my team was overworked, and they were glad to take on the project of lightening their load. Most organizations would benefit from making sure the communication is solid in that regard, however. 

I'd rate the solution at a nine out of ten. With better technical support, I would give them a perfect ten.

We have automated tasks within our organization and are automating our marketing applications. Internally, we have automated in-person and webinar event creation for Microsoft. Whenever there is a request for creating an event that is covered on, for example, either on Jira or the Dynamics 365 application, the task makes an API and pulls data from both sources. It then creates an event on Marketo. It runs totally unattended. We have actually saved the build time that was previously around 45 minutes and we have reduced it to just four minutes.

Previously, we had a build time of around 45 minutes just to process one request. This was kind of a disaster because even in 45 minutes of build time, and this is the average build time, people were making mistakes. When these errors happened, the company had to actually pay money to the client. For example, if a company has an event at 3:00 PM on September 1st, and due to time zone issues, someone manually wrote \ 4:00 PM then people would arrive at 4:00 PM, whereas the event had started at 3:00 PM. Mistakes like that could become a very, very big issue.

Using UiPath, we were able to reduce these kinds of errors. We were also able to reduce the time by more than 90%, just by deploying the bot that could do API calls in order to complete a specific point of data gathering.

For the portion that we automated, the errors that were happening were reduced to 0% and the efficiency was up to 90%.

We've found the usability of Studio very easy. It's simple to understand everything. It's very simple to just start developing within UiPath. 

The Orchestrator is fantastic in terms of usability as all you have to do is just need to deploy your bot there. It gives you several options of how to schedule it, how to monitor it, and it also gives you the dashboard that allows you to see the performance of your bot.

I really like the fact that we have a cloud model, where we can actually go ahead and use their cloud to run our bot. That is a very good kind of feature. 

I really like AI fabric and the documented understanding model, as that actually allows us to do a couple of very complex POCs. They went very well and right now, those prefaces are currently in the pipeline. Hopefully, they will get started with them next month.

The ease of building automation using UiPath is very easy. When it comes to comparing it against other tools, UiPath might be the easiest one. It's totally subjective, of course. That said, there are scenarios where automating certain kinds of scenarios with UiPath is not that easy. Overall, it's pretty good at automating all kinds of stuff.

UiPath enables us to implement end-to-end automation. End-to-end coverage is very important. While working with clients like Microsoft and Google, we have to actually go ahead and make sure that you're actually providing all of these kinds of services. With services such as documentation you also need to be on top of the latest market trends. UiPath actually provides us with not only the ability to handle all of this but to also document all of these kinds of things. That is available, either as a part of some other products or is embedded within the Studio itself as a part of an extension. That is something that I really like as that actually reduces the time that I invest in the creation of the documents. That, and the client actually requires all of these documents before even we can go ahead with the contract, makes having them on hand so important. 

The Automation cloud has helped decrease time to value. Earlier, the deployment of an on-prem Orchestrator took around two to three days for proper configuration and for making sure that there's a disaster recovery mechanism. Automation cloud has everything built already within it, which makes things faster and easier. This reduces the amount of time that is required by us to deliver. Within our area of work, within marketing, time is everything. Once you have taken on the project, the client expects you to deliver it as soon as possible. The requirements that you're getting from the client are very, very time-sensitive. If you're essentially not delivering it on time, that is going to be an issue. Automation Cloud actually helps us to do that without thinking about other things. It actually goes ahead and does a couple of things for us that we don't have to worry about, such as deploying the Orchestrator on the cloud, making sure that everything is properly set up, and making sure that the disaster recovery option is there. These kinds of things actually save us days of time for installation, if not days of debugging time. 

It's very important for our company to scale up automation without having to pay attention to infrastructure. There are a couple of projects that we have where we don't really care about the infrastructure. If it is handled by UiPath, it's absolutely fine. However, for example, in the case of some of our elite clients, what happens is that they actually need to know the details and how data is being propagated amongst different servers. If we're not controlling the environment, if we're not handling the entire knowledge, we won't be able to give them the same thing and the project might go away just because of this fact. Therefore, I'm not saying it's not very important. It's actually very, very important. That's why we use both services that are provided by UiPath - both on-prem and cloud. That said, if we have projects where we don't need to worry about it, it's nice to have the option not to.

UiPath has helped us minimize our on-premise footprint. Their customer service has actually helped us reduce that. UiPath was released in 2015. There are experts on this particular thing in the market, and most of those experts are found via UiPath only. When help is provided by UiPath themselves, that can actually resolve the issue in a matter of hours rather than days.

We use attended automation. We usually use attended automation within the HR department. Basically, we're using it for onboarding, for monthly salary management. It's great for automating some of the basic SAP projects as these are the places where we require human interaction, either to handle the credential part or to provide some inputs. This actually helps bring confidence into the process and also phases out the work of a particular human. Automation has integrated with some human day-to-day jobs so well that now when employees come in, the primary thing that they have to do is just to trigger the bot and start providing input. Work that they used to do for the first half of the day, is completed in the first hour of the day. That's the kind of benefit that is being provided by attended automation.

There is good AI functionality and we use it for some proof of concept projects. That said, we haven't yet used it for more complex or involved automation or processes just yet. We have one project in the pipeline that we have to start working on this month. 

We use UiPath Apps. We use UiPath Apps as a form. Essentially, we have created UiPath Apps in such a way that helps HR people to onboard individuals. For example, whenever someone has to get onboarded, they have to actually provide some details in terms of who they are, their previous company, and some other basic details. Also, HR will need to provide some extra details, in terms of who will be the individual's manager, et cetera. Finally, IT has to assign some kind of role. What we have actually done, is we have created an app where a user or a new individual has to actually provide all the information. Then, HR just needs to select the particular role. Everything is pre-configured. We automatically assign specific roles. In terms of IT, we can now automatically assign specific resources such as laptops, monitors, or headsets to that particular person. Since everything is automated, within a couple of minutes of registration the person receives his new ID password and details. Instead of waiting for an entire day, it happens in just a matter of one or two minutes.

UiPath Apps has increased the number of automation we can create while reducing the time it takes to create them. Earlier, we used to create automation, in terms of forms. Those automations were types of attended automation. A person had to have specific access to that particular computer before doing this kind of work. In this scenario, the issue we had was that every time it was not possible to handle manual steps if we were onboarding ten people at a time. Everyone had to wait for their turn and that was not very efficient. What we have done is we have actually deployed UiPath Apps whose links can actually get loaded onto an individual's mobile. One just needs to open it on their mobile and get started. That's it. Everything executes parallelly. We have also made our system scalable so that multiple VMs can learn the process at the same time.

UiPath speeds up and reduces the cost of digital transformation. Doing so does not require expensive or complex application upgrades or IT support.

We have found that UiPath has reduced human error. We were getting some human errors related to time zone issues and some of the other issues such as daylight savings. There were several other issues related to accidental typing or of people not focusing properly, even after several integrations. That's part of the reason we went ahead and automated processes. Obviously, a bot only follows what you have programmed it, what you have programmed within it. The errors are literally reduced to zero within that specific section.

UiPath has freed up employee time. We have actually retrained the freed-up employees into UiPath to act as support engineers. As a rough guess, I would say that we have saved around 120 hours a week just by deploying UiPath.

The additional time enabled employees to focus on more essential work. For people who were actually acting as build personnel, we have re-deployed them as a person who actually interacts directly with clients or who does QA work. This is a higher position that comes with a higher salary as well. There have been promotions simply due to implementing UiPath.

Employees are pretty happy. Initially, everyone was scared that they might lose their jobs. However, but adopting UiPath methods and retraining people, some are even getting promoted and we find that they are actually encouraging automation processes so that new work can come in and the remaining people could also get on better.

The product has reduced the cost of our automation operations. In terms of marketing operations, for example, it has reduced the cost. Along with the help of similar investments, we need fewer people and more bots currently. That's definitely a big thing for us. We had a cost reduction of approximately 20% in our operations. This is just a ballpark. That said, overall, UiPath has saved our organization a lot of costs. I cannot speak to exact savings, as that requires business knowledge, which I do not have complete access to. 

The AI Center area could definitely improve. The StudioX model could also improve just a little bit so that the introduction of variables is better and would make it possible to pass on a similar kind of data in between multiple activities. This is a very simple concept, however, this kind of feature is not available within UiPath. 

From the business perspective, a little bit more insight on the dashboard that is currently available in Orchestrator would be ideal. I agree with UiPath having a dedicated tool for insights, however, right now, it's a paid tool. 

If I can get a little bit more data and a little bit more customization on Orchestrator, that would be really great.

I've been using UiPath for three years and eight months. I've used it for the same amount of time the company has used it.

The product is quite stable now. There are certainly some places where UiPath has to work, specifically in terms of actual stability, where there are still some unknown errors that are coming in. 

In terms of Orchestrator, I have noticed there are some places where there are glitches. Things are not very clear at first as everything is changing quite quickly, I'll say that. Even in the enterprise version, everyone wants to be on the very latest version. However, there is a drastic change between the versions themselves.

For example, 2019, 2020, and 2021 versions, all three are drastically different amongst themselves. This kind of change is definitely good for the provider in that they are doing something better. However, as a consumer, I don't really want to go ahead and go through an entire learning curve all over again along with handling my current job of handling all the work, just so that I can cope up with what changes the product team has made. It should not be necessary to go through this level of adjustment for each and every release. At this point, I have been through three to four migrations and in each migration, I have gone through some kind of a learning curve.

Automation Cloud actually helps us to rapidly scale up. We don't have to invest time now in configuring Orchestrator, or the cloud version of UiPath. All we have to do is we just need to basically request for a particular package and, maybe, either with the help of a package or with the help of the UiPath team, it is pre-configured for us. That way, we just need to utilize it. Therefore, scaling is simple.

The scalability is great. It has actually allowed us to schedule the bots or maintain the bots in multiple VMs without having any worries about how to utilize licenses, or how to actually go ahead and deploy the bots manually or install the bots manually on certain VMs. Everything is automated within the UiPath environment.

If we talk about attended users, right now, we have more than 10 people using attended bots. Their roles are essentially from the recruitment team, from HR. Some of the marketing staff are also using it in analyst positions. 

We definitely plan to increase usage and we're using UiPath pretty extensively. We have a couple of projects in the pipeline and currently, we're also working on some of the more complex projects within the team.

All the projects are having a specific date of delivery. Everything is running parallel as we also follow an Agile method. In this Agile method, if something is stuck, it will eventually impact the date of delivery. And we really don't want that. UiPath actually helps us a lot by providing 24-hour support and it helps us in setting a lot of the items we need to use. They do it quite easily and quickly.

On the scale of one to ten, it's definitely a ten. Whenever I have a doubt, they are always there. They even offer to get on a call with them and actually go ahead and resolve the issue themselves, if they know how to do it. 

Many times, there have been scenarios where the issue was unique to us. They actually presented us with some debugging steps that we can do on our end. Most of the time, those debugging steps actually helped us to resolve the issue. When none of these options work, they were very keen to figure out how they could actually improve the experience and what could be implemented by the developers within those specific parts of the product in order to resolve the issue. We have given them feedback in the past and in a couple of future versions, we were able to see those ideas implemented.

We were using AutoHotkey before this product, as well as Selenium. However, after implementing UiPath, we have not used anything along with it.

The initial setup was straightforward. The installation of the Studio was quite straightforward. We just had to go through all the legal terms and everything. Once we went through those, we just had to install it. The same thing is true for Orchestrator as the on-prem installation of Orchestrator is pretty straightforward. You just have to get the setup, link it with the skilled server, and then install it. 

Apart from that, the configuration within Orchestrator was very simple as there is only one file that allows us to log on to everything. It made it pretty obvious.

The deployment took somewhere around two days for the entire setup. 

In terms of the implementation strategy, firstly, we decided to set up all the databases and all the dashboard-related services such as Power BI. We decided to do this first due to the fact that the dashboards and databases are the base of any application. 

We decided to implement it first in Azure. On the same day, we decided to get the cloud version of the Orchestrator as well. It was quite easy in terms of Azure. There's a three-way plugin that is available there. We just had to install that on the specific VM and we were done. Finally, on the second day, we went ahead and installed all of the Studio. Once Orchestrator is up, we could install Studios and link them to Orchestrator in order to get the license. That was our strategy and our approach.

We essentially have one dedicated resource for maintaining all the deployments and to watch if anything goes wrong. We have three dedicated resources for maintaining all the bots that are currently running as well. We don't need a big team to maintain everything. 

In one of our projects, we actually used Azure Cloud for the deployment of Orchestrator and the deployment of packages. The experience is quite good. Azure provides the DevOps side of our service that allows us to set up the pipeline and automatically deploy any kind of project to the Orchestrator as soon as it is committed.

While the company has likely been looking at ROI, I don't directly deal with those details.

A couple of our clients cannot actually go ahead with the initial investment of Orchestrator as it costs quite a lot. The thing is that we don't need that much of a license in order to automate our processes. Having a free version of a cloud or having a cheaper version of Orchestrator has actually helped a lot.

Automation Cloud helps decrease UiPath's total cost of ownership. However, overall, if we talk about scalability, once the number of licenses that I need increases, ultimately, Automation Cloud might be a bit expensive. It depends upon the version you're using. Yet, since the license cost is increasing, what happens is if you go ahead and buy more than five licenses, then essentially you would have been in better shape if you would've actually bought the paid version of Automation Cloud and installed it on-prem. That would've been a cheaper option. It's subjective. Our scenario is just that we need two unattended licenses to do the job.

Some of the clients do consider the initial investment of UiPath to be expensive. It's seen as expensive specifically from the cost of getting a licensing for an on-premises setup. For some projects, UiPath can be overkill. However, it is the best software a company can invest in for automation purposes. 

I cannot speak to the exact cost, as I don't handle licensing directly.

It's paid per year. We get licenses not directly from UiPath. Rather, we get them from a vendor.

There are additional costs as well. For example, the cost of an SQL server is one. We are definitely using the Azure product suite as well. We had to actually invest quite a lot in SQL Server in terms of database management, just to make sure that everything gets logged properly and that the Orchestrator is functioning properly. 

We switched to UiPath after we compared multiple tools. We looked at certain parameters such as the ability to automate marketing tools, the ability to automate quickly, and how user-friendly it was. Out of all these three parameters, UiPath stood on top.

We looked at Automation Anywhere, Blue Prism, and PEGA.

I specifically have been using the community version of UiPath. The company has been using the enterprise version.

We do use the Automation Cloud offering.

We do not use the SaaS version of the solution. 

I'd advise users to give it a try. I started my career in UiPath and since then I've been loving it. I became a UiPath MVP as I really enjoy working with the product so much.

That automation does not need to be very complex, so you don't need very complex tools to automate any software. Tools like UiPath can do most of your job.

I'd rate the solution at a nine out of ten.

I am a UiPath developer and my role in the company is as an automation developer specialist. I'm working mainly in UiPath Studio, not Studio X, and I also work with Orchestrator. We are using attended automation.

We are automating the processes in our company, for example, in the finance department. One of the ones that are now automated is invoice coding determination, which no longer involves humans. At this time, 80% of our processes are completed by robots. The remaining 20% is approved by humans but I think that this will improve later. 

With respect to the ease of building automations using UiPath, from my experience, when you have a basic knowledge of programming, it is really easy for you to start your journey with the UiPath environment. You can do it without this knowledge but then, you will just need to spend a little more time learning the details.

I really like working in UiPath because the programming allows me to do whatever I want. I can declare any type of variable, I can check the locals, and I can add breakpoints whenever I need to check the states. For me, it's a very professional platform.

I really like that they offer the possibility to work with it from two sides. It can be operated from the full-programming side, as well as from the standpoint where you don't need this knowledge.

UiPath has helped to minimize our on-premises footprint, although I cannot estimate by how much because I am not responsible for that aspect.

UiPath has helped to reduce the cost of our digital transformation because it really speeds up the processes. When we compare the time it takes for a human, with perhaps a one-hour task, and it only takes 30 minutes for the robot to do it, we can see the savings. You just multiply this by the salary and we also see the reduction in cost.

UiPath has definitely reduced the number of issues arising from human error. We can confirm this with 100% certainty because we have compared it to when humans were completing processes on their own. I estimate that the error rate has been reduced by approximately 60%.

In my previous company, we managed to save about 20 FTE after our UiPath implementation. It was about two years of work. Thanks to the ease of access, as well as the fact that our employees did not require programming knowledge, we were able to show it to normal employees and explain the automation. After this, they were not afraid that they will be replaced by robots and instead, understand that they are co-working with them.

The most important part of Studio is the debugging feature. It gives you the ability to watch local variables, as well as highlight elements as it is moving through the process. The results of actions are displayed and indicate whether particular actions are performed successfully or not.

Outside of the company, I am using UiPath's AI functionality and it very much speeds up processes and improves accuracy for reading data. For example, the OCR is much better than Microsoft's solution. With UiPath, I was able to read handwriting samples but with Microsoft, I was unable to do it.

The AI functionality has allowed me to automate more processes in my own projects. It adds flexibility and improves process speed. I don't have to think about boundaries when I decide how to approach a project. 

It lacks something crucial, which is a map of the variables and arguments. When we are using a lot of variables and arguments, sometimes, we get lost. UiPath should create a map that connects different files and shows the connections between them. For example, from file A, we have variable B, and file C contains variable D. However, they are actually the same variable, but it's connected by argument and we don't know it. It is something that we have to remember explicitly. In this case, it would be really helpful for me, as a developer, to have this picture of the net. It would show me what is where and how it's connected to everything.

For the on-premises solution, if we ignore any problems that may occur with the infrastructure, such as the network, then stability is very good and the platform works well.

In my experience with cloud-based deployment, I haven't faced any problems with stability.

Scaling UiPath is really easy. When you get to the point where you have to think about scalability, you use the UiPath Installer to extend the Orchestrator by another node. There is an option for it and you don't have to know much about the network to do it on your own.

I am part of a four-person development team that is working primarily with Studio. We have approximately ten processes at the moment, and it is difficult to estimate how many employees are affected by the automation. 

The technical support is very professional and they work quickly. Usually, we are able to get responses in about two hours. Sometimes, it takes one day, but I have not faced a situation that took longer than two days.

The help from their site is also very professional, and well-described.

Overall, it is really easy to resolve errors.

Prior to UiPath, I used Selenium WebDriver. The problem with this product is that you have to know the Python programming language. You have to know everything inside Python, and there is a lot more typing. In UiPath, you have some clicking, and there is some decent orienting stuff, which you don't have to define. You already have some pieces of code that you can use, and this is a really nice feature.

I have also used Kryon RPA and the problem is that it's based on the OCR. This is something that I would never accept with an RPA tool unless the OCR is fully working. Right now, OCR is not a perfect technology and it causes many issues. UiPath allows us to use selectors, so we are able to track the exact area of the display in the program that we want to access.

The initial setup is quite easy, although we faced a few issues. With the help of the UiPath service desk, we were able to quickly fix our problems. The deployment was completed in a few hours on one machine. This included checking everything to make sure that it was working fine.

We followed the documentation provided by UiPath, as well as their guidelines.

At this time, we are using the on-premises version. In the next few months, we plan to move to the cloud environment, so we are currently planning the transition.

In my previous company, I was responsible for moving to the new version of the UiPath, with the Apollo interface in the Orchestrator. Where I am now, this was already done. So, yeah. I was responsible for this transition. Right now, in this company where I'm working currently, the UiPath setup was already done but I helped with the optimization.

With respect to upgrades, once we knew what had to be done, it took about one hour to complete. Otherwise, there is no maintenance required.

I have calculated ROI for our project and it seems that we will reach our ROI point in approximately two years, which is quite good.

Price-wise, it is not the cheapest one on the market, but it provides the fastest automation and the best training that I have ever seen for RPA, through the UiPath Academy. It's really easy to set up a new developer in this environment. Everything considered, the pricing is very good.

There are no costs in addition to the standard licensing fees.

We are currently evaluating Kryon RPA.

My advice for anyone who is implementing UiPath is to always check the documentation before you try to look for answers on the forum. Another good point is that when you have a problem, there are plenty of people in the UiPath community that can help you in a few minutes. This is the perfect solution, in this case.

From the maintenance side, you have to remember to increase your database with the scaling up of the automation because it can really slow down your process.

The biggest lesson that I have learned from using UiPath is to always create a backup copy of Orchestrator before you update it. This was a very big lesson for us because we had an issue with the installation. It is also really important to back up the related databases.

I would rate this solution an eight out of ten.