UiPath Platform Reviews

My primary use case is automation. I worked in multiple companies with the same product on the same profile, and most of them were automation. The actual business use case would vary from company to company, and project to project as well.

One feature that I personally found valuable was the orchestrator. It is a pretty mature platform as of now, and it was three to four years back when I started to first use it. It has matured quite well. They had a major change a couple of years back. Our company transitioned from an older approach to a newer modern approach that they deployed. The orchestrator platform was very well-suited to the new approach - as was the development studio. It's really easy to use and intuitive. That has matured quite well as far as I can tell. These two are what I liked the most about the product.

UiPath’s ease of use and quick deployment times were great as the cloud orchestrator, which did not need much of a setup.

To build automation using UiPath is fairly simple. The studio is quite easy to use. Even now, with the community edition, it’s great. If we want to learn to start or try out something, we do not have to wait for licenses or anything else. That said, we can also get an enterprise trial. If we want to do something, learn something, even during our personal time, we can just download it. They also provide a free orchestrator version as well, so it becomes quite easy to learn and develop. 

The building, deployment, and manual deployment processes, for small-scale projects, are very easy. If we need to build something, we just publish it, and it generates the NuGet package. It's very easy to deploy there.

The materials and the training courses are all pretty well-structured to get started with.

UiPath Academy courses have assisted in the process of getting our team up to speed. The basics were there even when I started out. I was not initially an RPA developer. I was into server operations before this. The UiPath Academy training really helped a lot with the initial courses, where they give you a tour of the platform and each and every activity. For audiences who are not much into software development, these courses can guide them towards that. The building blocks got us up to speed. They have very good courses there.

Regarding the Academy, it is a great learning platform for basic tasks. However, for more complex information, I turn to UiPath Forum. Sometimes I need some Python or C# scripts or am building custom libraries there. That gets shifted onto different platforms like Stack Overflow. We Google other platforms as well for the other types of queries.

UiPath Forum is a pretty good place in terms of the user community. Most of the queries that are posted generally get answered. Sometimes, even for smaller issues, we do not go directly into UiPath support and we first try to resolve the issues via what we find in the UiPath Community. Overall, it’s a pretty good place to solve our issues, and the community as of now is pretty active.

We saved time in our IT department since we started to use this solution. UiPath handles infrastructure for the orchestrator and its maintenance. There's a pretty good amount of time saved as we had initially had a server on-prem deployment as well. However, it became cumbersome to deploy multiple databases and they have some Elasticsearch requirements and security updates that need to be regularly maintained and in sync with UiPath. Due to this infrastructure overhead, our time could be consumed maintaining everything. Without them handling the infrastructure, we'd be maintaining instead of building automations and deploying them. We realized that an automation cloud would be a better option which is why we switched.

UiPath reduced human error. That said, we do not track errors in the process. It's a good metric to track as well, however, we currently do not track it.

It reduced employees’ time on certain tasks. The main purpose of automation is to save us the number of hours that the project will take. There are many other parameters, however, the time saved is one of the big ones. 

A weakness with Academy is that, with the current updates that they have, the newer updates, the courses are not up to speed. Nowadays, Academy does not feel that intuitive and does not give sufficient information about the product to the customer.

In our current use cases, we do not need much user interaction. One shortcoming with UiPath Apps is that it cannot directly integrate with the orchestrator platform itself. For example, if we need to fetch any assets, values, or cue data from the orchestrator itself, it's basically a web platform. Even if we develop apps and want to do something based on that data, they do not have direct integration with the orchestrator. We need a separate bot, which will then interact with the orchestrator and then pass it back.

If we need ten to fifteen users who might simultaneously use apps, and we want to run a process for each of these users, then we might need fifteen licenses to do that. That is something that has been holding us back from using it, as it does not have direct orchestrator access. We need a separate bot to get the data to perform some actions.

Scaling and licensing need major improvement. I know that they have released something called Serverless Cloud Robots, where the bot machines do not need infrastructure. However, we do not generally want to run the bots or the data in the UiPath cloud as well. There are some hiccups that do happen when we run bots on another machine. That said, it might be a good feature and we can scale up and scale down more effectively.

I've used the solution for nearly four years now.

The stability has been quite good for a couple of quarters now. We had some issues two or three quarters ago, where there was a downtime of around thirty minutes which impacted assessment. After that, for the last couple of quarters, we have not seen any issues regarding the platform itself. It is pretty stable.

The product allows scaling up, however, when we deploy and run the bot, the bot does not actually run on the orchestrator. The orchestrator is just a management platform. When we need to scale up bots, what we would need to do is spin up new virtual machines. We need those virtual machines in order to scale up. This, along with the licensing affects the ability to scale.

If someone does not have a license, it cannot scale up. When comparing it to something like AWS offers, or any other cloud service, where you can rapidly scale up and rapidly scale down based upon our demands, that is currently not possible with the UiPath. We do not get to easily scale up. We need to plan in advance as to when we run our automation, what time we need to offset the loads, and which automation gets priority at that time. That becomes a bit of an issue.

As of now, scaling is a bit cumbersome, whether we are scaling up or down, and the licensing also revolves around scaling.

We use both attended and unattended automation. In the case of attended automation, scaling is a bit tricky. We need to consider licenses. Very few need the same automation to run on one hundred machines. If we do, then we would need to find a way to manage these one hundred licenses as well. It again comes down to cost.

Our thought process is that whenever possible and where we need to scale, we try to avoid human interaction, and we try to convert our bad pieces into attended automation. If some automation requires a manual login due to regulatory compliance or maybe due to capture, what we do is have these login paths that we take in as unattended input. Then where it’s possible, we would run it as an unattended mode and maybe then pass on the output to the attended mode.

We have support from UiPath, however, I'm not sure what model we are on. 

The support is not as responsible as we would expect. It's not bad, but it's not good.

The response time, the overall solutions that they provide, and the workarounds are okay. It's a mix of everything. We've had somewhat of a mixed experience with them.

Neutral

UiPath handles infrastructure, maintenance, and updates for the Automation Cloud - the infrastructure being the orchestrator infrastructure. The robot infrastructure is handled by us.

I was involved in the initial deployment of UiPath in our organization's deployment process. The deployment process is pretty straightforward with automation cloud data, so we did not need to worry about that. The administration is pretty straightforward as well. They have all of these access models, folders, and groupings. It's very easy, even for a new user that needs access to a particular box to run. It's also easy to maintain.

In terms of deployment on the cloud, there is no overhead. The administration process is simple. Maybe it took us around two to three days of initial setup. Most of the time was spent brainstorming on how we would need to structure our use case. That was what took the majority of the time. Once we decided on that, it was pretty easy. It can be done in one day. The process is also ongoing as the requirements change and the roles change, and it always requires some sort of maintenance, taking out users, taking in new users, et cetera. However, that's pretty easy.

In terms of the deployment of individual bots, it is pretty easy. The manual deployment is also pretty simple. We deploy it from the studio. We get a bundle package and we upload it at the studio level as well as the orchestrator, and it's done. This is a straightforward model. We do have a CI/CD pipeline setup for enterprises where we avoid manual deployments. In that case, we do not use UiPath CI/CD. We do use Git and pipelines to push our packages directly to UiPath.

I can't speak to if there has been an ROI or not.

The licensing could be more flexible. They might have a different enterprise cost strategy for each of the licenses. The license is rigid in that you cannot generally scale up. To scale up, we have to have a license procured before we can run a bot there.

I am not involved in the comparison between Uipath and its competitors, such as Blue Prism, Automation Anywhere, or any other platform.

We do not really have clients in healthcare, however, my previous company has mainly evolved into what I can say is a pharmaceutical supply chain. The company is an ordering platform for pharmaceuticals. I'm not sure whether I can consider that as a healthcare pharmaceutical or supply chain use case.

I had done some trial POCs around the UiPath Apps feature. We did some basic trials within our team, however, we do not have any end-users who actively use UiPath Apps.

We're still at an early stage in terms of using AI in our automation via UiPath. We tried out some POCs, and I'm also just getting training on that as well. We do not have any production use cases right now that go into full AI or ML.

In general, they have a good ecosystem of developers. It would be easier to set up and use it. However, if a new company has heavier workloads and needs scaling capability based on time, they’ll need to calculate their requirements. For example, if I process 1,000 to 2,000 transactions per day and I need ten robots to do this and it's fixed every day, then it's fine. That said, if I have varying workloads, where the workload is the last week of the month and the workload is very high, maybe I’ll need twenty or thirty bots to accommodate this workload, while, for the rest of the month, I’ll just need around five bots. That's twenty-five bots that I’ll need to purchase, with many idle most of the time. That is one issue that needs to be planned correctly during the initial stage. 

Overall, I would rate UiPath eight out of ten.

One of the projects we have been working on is for a medical company. It includes fetching medical records from the company's web-based portal. These records have to be pasted into Excel and consolidated. We then send them back to the client via email. We use Orchestrator to schedule the process to run every day at three intervals. It is running as an unattended bot.

We have also used it for another company to help with their employee onboarding process.

If we had to build code from scratch in UiPath, we would have to configure proper exception handling and log creation. We would also have to connect it to Orchestrator queues. But with the predefined REFramework (Enhanced Robotic Enterprise Framework) template, those requirements have been built already. All we have to do is invoke our code in one of the four states: Init, Get Transaction, Process Transaction, and End Process. Because it is connected to Orchestrator's queues, we can then run the process.

We have also been able to develop our code based on UiPath's security and compliance credentials. UiPath supports confidentiality. Until now, we have never faced a security problem. It is the most secure RPA tool.

Another benefit is that UiPath automation saves our clients time. During our requirements gathering, one client told us that the process they wanted to be automated takes around 15 to 30 minutes to complete when done manually. As a result of the solution we implemented using UiPath, it is now completed within two minutes.

There are two features that I find to be the most valuable in UiPath. 

One is Orchestrator because it allows us to manage the bots and processes. For example, we can monitor unattended bots' run history and their logs. We can also modify our code based on screenshots by logging the screenshots and then viewing the logs in an Orchestrator job. That helps us trace errors and rectify them.

The second valuable feature is REFramework which is a pre-defined template built with proper exception handling and logging activities. Those aspects help developers to develop code properly.

In addition, I have implemented UiPath with ABBYY FlexiCapture for some projects, and that has been very helpful for successfully completing those projects and providing a positive impact for our customers. It makes it very easy to extract data from a PDF and then build code to process it in UiPath. The integration of ABBYY FlexiCapture with UiPath is a very good feature.

When it comes to REFramework, we need more training videos and tutorial documents for beginners. 

And while there are a lot of videos to learn about basic activities in UiPath, we need more documents and key points on how to connect third-party connectors. That would be very helpful for beginners and for quick implementation.

I've been working in UiPath for almost two years. I use it daily.

The stability of the solution is excellent.

The scalability is also excellent.

Sometimes technical support will get stuck on how to execute further, but we raise our queries in the UiPath Community Forum. There are so many RPA developers there and we get quick replies from them. We're able to build solutions based on their information. The forums are very useful for us.

Positive

I used to use Blue Prism.

I have seen a lot of return on investment with UiPath because it enables quicker implementation of automations.

When I compared the basics between Blue Prism and UiPath, I felt UiPath was much better.

With Blue Prism it takes a lot of time to build code and workflows. For example, to fetch data from Excel within UiPath only one activity is needed, called Read Range. But Blue Prism requires use of three activities to do the same thing. First, I have to open the Excel instance, then open the worksheet, and then fetch the data from the worksheet. Using UiPath means quicker implementations. 

And there are a lot more features in UiPath when compared to Blue Prism, and I haven't seen any disadvantages of UiPath. Using it, there is a solution for every process. There is no such thing as a process that cannot be done in UiPath. UiPath is the best solution for RPA and for our customers.

UiPath doesn't require any maintenance.

We are able to build workflows very quickly and it doesn't take that much coding knowledge to learn and understand UiPath. Beginners are able to learn it quickly and get into the businesses.

Choose UiPath. It is more helpful than any other tool for implementing solutions quickly and creating customer satisfaction. Based on my experience, UiPath is the best tool for automating RPA projects and repetitive processes.

I'm not currently using UiPath, but in my previous organization, which I left seven months ago, we had a complex trading application that included a web form and a Windows form. And on the Windows form was an Electron framework. If you want to run a web application inside a Windows application, Electron is a bridge between the web application and the actual Windows app. Because it was a complex application, it was not very easy to automate. That's where UiPath came in. It perfectly fit our automation testing scenario.

Before UiPath came into the picture, we were planning on doing automation testing with Selenium. The test plan with Selenium was going to take about three months. When UiPath was introduced and we started working on it, we completed the whole automation, end-to-end, in about one and a half months. It saved us that much time. And we made sure that our product was delivered with the required quality and that we did not compromise on that.

Because UiPath is SaaS, we were able to automate everything in a very productive manner. We were able to cross-verify all the flows and all the functionalities. And UiPath didn't require a huge amount of setup. It runs on minimal requirements.

In terms of human error, we saw a reduction, of course. It's not possible for a human to catch every error when new functionality is built. With UiPath automation, we were able to analyze errors right away and resolve them.

Another benefit was that it freed up employee time. It did a lot of the work by itself. The user only had to make sure that the correct workflow was involved and he could just sit back and check that everything was going correctly. It probably saved us 45 minutes daily.

UiPath makes you more productive because it comes with a lot of drag-and-drop features. You don't need to know the APIs to access particular elements on the screen. You can just drag and drop and define your actions and go ahead with the workflow. You can focus on the workflow rather than learning about the APIs, which is what happens with Selenium and other automation tools. That is one of the most beneficial features of UiPath.

I don't know if I was doing something wrong, and I did get assistance from the UiPath guys on this, but sometimes UiPath wasn't able to find an element on the screen. But that's what UiPath is for, and we wanted to make sure that our workflows were working correctly. Sometimes it was able to find an element and sometimes it was not. UiPath support did give us a solution, but it was not helpful enough.

The issue that I mentioned earlier, that sometimes it wasn't able to find the elements, was the only issue I saw with respect to UiPath. Otherwise, nothing was breaking and nothing was problematic on the UiPath side.

They were very friendly and they tried to be very helpful, but they weren't able to solve the issue I raised.

Positive

The version of UiPath that we used involved a direct installation. We asked our in-house team to get it installed because we didn't have the permissions to install software. They installed it in our system and we started using it right away. It was very straightforward.

I have worked with Selenium, which is an automation tool. That has quite a learning curve, but with UiPath it only takes you one or two weeks to get started. Once you're familiar with the basic tools, you can start writing a workflow. It is straightforward; nothing complex.

I never did the UiPath Academy courses because we had senior team members to help us and, in that company, we had a "learning playground" where we could go through the slides directly, without going through a whole learning process. We were then able to start our work right away.

UiPath did a good job. Before going into production, we needed to make sure that every test scenario and every case was handled. That's where we took advantage of the UiPath. We would run UiPath again and again and there were no breakages in our code and nothing was falling apart before going into production. I was working for an investment bank and every record was important.

Our primary UiPath use case is reconciling data and getting data from the web and writing to either Excel or our system. The automations are very reliable. 

Task Capture is quite a helpful feature because it is easy to design a process flow with it. All you have to do is just capture it and then do the manual process. It then gives you the process flow and the process definition document, PDD, so it saves you a lot of time.

The database connectors I found are not fully free and expire after 30 days. That is something I would like looked at for MongoDB specifically. With regards to this, I was working on a project that needed a robot to read data from a MongoDB database. To achieve this, I used the CDATA ODBC driver because I couldn't find a direct Activity to achieve this from Studio. See the link to the CDATA ODBC driver for UiPath here https://www.cdata.com/kb/tech/...

It would also be great to have UiPath Insights included in the free Orchestrator. The Insights module is currently only available for paid licenses. It would be great for developers to have it included in the free version because then we could try it out. 

I have been using UiPath since May 2018, and have recently worked with UiPath Process Mining. I am currently not very actively using this tool because the projects I'm on at the moment are using Power Automate. However, I do look at it once in a while.

UiPath is quite stable. I have not seen any inconsistencies come up because even exception handling is well set up in case of bad themes. Transformational processes are well managed, including exceptions, so that adds to the stability. Also, you can scale out from one bot to tens of thousands, so automation is quite easy with UiPath.

Very scalable

The initial UiPath setup is straightforward. You just go on the cloud, create an account, and you get the Orchestrator right away. From there, you can download the Studio. So once you build the automation, you just publish it from the Studio and you can run it. It's a very seamless process.

There is no need to hire an external team. You can do everything yourself. Also, the forum is quite busy and active. You can get a lot of helpful material there.

I cannot give actual figures, but I have seen a return on investment especially in processing invoices. It used to take us a week to read certain invoices into Excel but now it takes us only a day. So we are saving five Mondays in a week and 30 or 40 a month. 

From what I hear, UiPath's licensing costs are a bit high, but I can't evaluate that information because I haven't actually experienced the cost. We are using a free version at the moment. A good thing about the Community Edition is that they allow you to deploy even as a company as long as revenues are below $5 million I think.

I recommend automating the small processes in the Community Edition. This is the best way to evaluate how scaling would go within your organization. 

It is also important to fully understand what you want to automate. I also recommend trying the Process Mining feature to make sure you are able to pick up areas of automation within the organization's processes before committing to paying for automation. 

In terms of product testing, I use it in the product with the test suite to mount the test manager and then follow with the requirements. After that, I create the test cases and I'm running them on different platforms on the web so that I can proof back from the web with test suites.

I use the different tools of UiPath. However, in the future, I’m hopeful UiPath will help us to expand into different countries. right now, I use it personally. Soon, the entire company will be using it as well.

The automation of the cloud offering helps to decrease the solution's total cost of ownership.

The document understanding is great. I interact with different documents of people. The IDs of one are different from a document or a PDF. For example, our contracts, et cetera. It can understand the differences.

I’m not quite sure about the ease of building automation using the solution just yet. It seems to be moderate. Not too easy or difficult.

The solution has helped our organization save costs. It’s likely saved us about $10 million.

UiPath has helped us reduce human error. That’s had a partial impact on our business. Our techs understand the different types of processes and competencies it can help with. Regular users cannot see this just yet.

It has freed up employee time. It’s allowed for a focus on higher-value work. Employees seem happier. It’s an easy tool to use and deploy.

We’ve used the UiPath Academy courses. All employees take the course and learn about it. You still need more education afterward, however, the biggest value of the Academy is the knowledge. I've got people who are new in the company and I can just say "take these courses." It's accepted by everyone as part of the process.

The graphics could always be improved.

I've been using the solution for three years. 

The stability of the solution is good. UiPath has a different release each year at the moment.

The scalability is great. You have a manual so you don't have to do the courses. You can read through it.

We have about 200 users at this time. We have different areas in the company that uses UiPath. For example, the administration uses that tool. You have a test suite and you can have development using the UiPath Studio as well.

Technical support has been great. Whatever my query is, they are able to answer it.

We did not use another RPA solution before UiPath.

The initial setup was straightforward and simple.

The deployment took about one month.

The pricing and licensing have been great.

We did look at different automation tools before choosing UiPath. We looked at Blue Prism and Automation Anywhere, however, we ultimately chose UiPath.

The UiPath Academy courses were a big selling point. Also, its ease of use. Automation Anywhere and Blue Prism were so difficult to understand. UiPath is more interactive and it's more visual.

We're a UiPath partner. 

I've used both cloud and on-premise deployment. Right now, I am using the cloud. 

At this point, we do not use UiPath's apps feature.

We have not used the solution's AI functionality in our automation program yet.

If I were to advise anyone on using UiPath, I'd let them know it's easy to use. You have manuals and courses to help you navigate the solution. The new releases make it so that it continuously gets easier. 

I would rate the solution at a ten out of ten.

We have four robots. One we're sending out shipping labels as our members do returns. Once they create a return, we used to have someone that was manually entering in and creating the shipping labels. That was like the first robot that we built. The cost savings on that alone covered the costs of UiPath in total. We have a few other ones that we've been playing with, however, that first one was a big one that covered the cost of UiPath. 

UiPath has freed time for our employees. With the shipping label robot, for example, we basically replaced two jobs and now they're able to do other things. They can take on other more vital responsibilities.

I'm really excited about task capture. We haven't started it yet, however, that's going to really help capture the processes that we want to automate. We're excited about that.

The solution is just opening our eyes to what is possible. There are a lot of people in our company who hate doing mundane repetitive things. It's giving enough hope that we can replace those jobs that people hate with automation. We're excited about that.

I'm not a developer, however, the two developers that are under me, like the shipping label bot and found it easy to build. A developer was able to create that in one day and it replaced two positions. I'm sure we can build it better and faster with what we're still learning. With a partner coming on to guide us I foresee that we will definitely get better at it.

We’ve used UiPath's Academy courses. I don't think we would be where we are today without it. My two developers had zero experience with UiPath. They went to the Academy and learned as much as they could and started building right away.

Its biggest value is the continual learning on offer. We're pretty overwhelmed right now with what it can do, however, the Academy just teaches us how or where we can go with it. It’s great.

The setting up of the cloud was a little bit confusing for us. We expected someone to walk us through that process and we just did it ourselves and weren't sure if we were doing it right. We thought that getting assistance with the setup would just be kind of a given or they would at least lay out the steps. We didn't have that. We were asking a lot of questions and trying to figure it out with our salesperson. She was likely not the right person to help us with that. If there were directions on how to set it up, that would have been helpful.

We've had the solution for three months. 

In terms of stability, the robots have been running well. That said, we've had a few failures that we had to go in and fix, however, it was a pretty minimal effort to fix them. I'm not sure of the exact reasons. I remember my developers were telling us one failed and we needed to go figure it out.

It wasn't like an all-day fix. It was just a pretty quick fix which required simply stopping it and restarting it and then it worked. 

In general, for stability, it's been so far so good.

We have the goal of scaling, however, we are still just barely with our heads above water. We're just trying to figure it out as we go. Our biggest asset is bringing a partner on to help us and allow us to build up that scalability. Without their help, we would be lost. We would build without having a good foundation. The partner is coming on for a three months contract to train us and get us up to speed to make sure that we're building a good foundation so that we can scale.

We first created a technical support ticket when we had the issue with the trial license versus our actual license. It was hard for my developer as he didn't have the URL for the cloud. He really couldn't diagnose the issue as we thought it was all on the one referred to us, yet there was that disconnect. We went back and forth over several days trying to figure that out and the tech person couldn't help us. We were lost there. That was a little confusing.

This feedback isn't against the technical team. Maybe it was just the way we didn't get the correct training we needed to set up correctly. UiPath should've killed those trial licenses or transferred them and they never did and that first robot we built was on a trial license. 

It would have been helpful if they told us to import the robot or something over to the real licensing. 

We did not use a different RPA solution previously.

I'm not a tech person, therefore, the setup was a little outside of my wheelhouse. It was a little bit harder for us. We've been trying to figure it out. 

The issue that we've found is we had a trial license and my two developers were on the trial. Then, when we got the actual licenses, a developer was still building under the trial. The trial was allowing them to do things and build over there, however, it wasn't under our automation path. It took us a while to figure out what the disconnect was as I just didn't know how to set everything up. That was a little bit confusing.

We realized ROI on our first robot. 

The automation cloud offering did not decrease the total cost of ownership of UiPath. It was a little bit more, however, we didn't have to set up our own server and maintain that.

We bought the starter package and we were able to cover the full cost of it with one robot within two days. It definitely paid for itself.

We were also looking at Automation Anywhere and it was a pretty close tie between the two.

We chose UiPath as a colleague who had worked with UiPath at his last job and he was a little bit more familiar with it. We thought the security was a little bit better in UiPath as well. Those were the two main reasons that kind of pushed us towards UiPath.

We haven't used the UiPath apps feature yet. We've signed up with someone that is going to be our partner to help us learn all the new aspects. Hopefully, in the next couple of months, we'll be setting everything up, including the automation hub, and trying out apps and task mining.

We do not yet use UiPath's AI functionality.

Based on my lack of knowledge, I would probably rate the solution at an eight out of ten. We've been super happy with it this far and from all the things I've seen, we're excited about where we can go with it.

Our primary use case is to document image processing. We're six months in, so our first case was sorting and filtering the data, extracting the image, and determining if it's a certain type of document. If it is, it starts putting it into different buckets, which ultimately we'll run something to extract and put those into our data source. 

Our second use case is for the healthcare industry. We're looking at catalog data and a customer might want to know about a product. Is this product safe? Who provides this product? Is it on a contract somewhere? We go out to multiple different web sources to look up information about that document, put it back in our database, save it for that customer, then save it for any future customer that asks the same question.

We're looking at other things like taking snapshots of the image of the product. We also want to automate other basic automation, low-hanging fruit type functions, like automating uploads of data to sites, spreadsheets, contact-center, and Salesforce.

Longer-term, we want to take what we're doing in the document image and apply it to other areas of our business. We have purchase orders, invoicing, shipping documents, compliance documents, credential documents, a lot of images in this particular space. We'll go as deep as we can in the data processing side of things.

We're going through a culture shift to get to an automation-thinking platform as opposed to a lot of our business relying on BPO humans to do the work. Making that paradigm shift is taking time because we're only a week-plus live. If we prove the value, they'll give us more opportunities to make those big changes. But it's good that the business is thinking that they need this. Now it's just getting the community aspects of it.

The automation cloud offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates. 

Although we don't use it, document understanding for our use cases is very compelling, but it was a little cost prohibitive just out the gate. We are looking at it long-term now that we have the data filtered if we can more strategically apply it to the best data to fit it. But overall, the platform is very innovative. I don't think I can call out one particular feature. The ease of use of integrating to and from Amazon components, being a cloud-native application ourselves, has been really helpful in the development and the ease of transferring documents between our internal systems and platform.

The ease of building automations using UiPath depends on the use cases. Overall, the development is really easy. Where you run into challenges is in workloads that are highly rule-based. So we abandoned one use case where it had 50,000 different decision points. It wasn't worth the time. It wasn't a product thing. It was just too time-consuming of a process, something like that.

There have been some limitations as far as how do we execute our bots, when? This new release that they just mentioned today actually addresses a lot of our concerns around the integrations component that they recently released. If we could find an email instead of waking up and checking the email inbox. That's a big improvement we're looking to, but it wasn't a limiting factor.

I have used the Academy. It was really just myself and as well the one IT guy who's supporting the platform. Our office partner came in with the knowledge, but the course was really good. We came in with no RPA experience, and it covered everything from the basics of RPAs to the processes of identifying.

They recently addressed a major problem of kick-off processes for the integration function. That addressed a lot of the community concerns around that. If you are using queues, their queue system isn't as reliable as I would like it to be. 

One of our concerns is that we were not a Microsoft shop at all before bringing this in. That was actually my limiting factor in bringing in the software. We lost it below the party lines. The ability to address other workloads, Mac, Linux, etc., is going to be a game-changer.

From a new customer, new investment perspective, there are a lot of cost-prohibitive aspects that we decided not to add to our initial investment. We weren't sure if or when we'll figure things out for use cases.

I have been using UiPath for six months.

We want to triple our capacity and triple our workflows. 

I've only had to use support once, and it was more of a documentation problem. I didn't understand what I was seeing, and they worked it out within an hour. So far, they've been good. 

The cloud was up two days after we signed. Then to get our bot infrastructure up because it's Windows and we're in a Windows environment, it took us about a month to run through that and get the IT people and security.

Cloud solutions will save you a lot of headaches and time. We broke halfway through and decided we're going to cloud, not on-prem.

Reputation was a big reason we went with UiPath, as well as the growth and the ability to integrate specifically to the cloud which was missing in other solutions. That was a big plus. The ability to use something like document understanding and the ability to interact with internal APIs were also key features. It's not just web scraping and doing things in Excel or other things like that. We wanted it to work with our internal native applications.

UiPath has not yet saved costs for my organization. We're still going live and we're anticipating about a two-year ROI.

Make sure to understand your use cases before you sign your agreement. That way you're not idle for six to nine months trying to figure out what it is you're trying to automate.

I would rate UiPath an eight out of ten. 

We do product downloads, accounts, updates, maintenance, a lot of operation stuff, reading emails, responding, organizing stuff to send, etc.

It's definitely added some efficiencies. It's added the ability to do jobs without having to worry about error handling and process tasks on a daily basis without having somebody having to be responsible for it.

We see UiPath as a money-saving solution. It also saves us man-hours and human error. It affected our ability to automate processes that are more complex.

The Academy courses are good. That's usually what I start new developers with; to do those and then have them try to do courses periodically to stay up to date and especially when a new release is coming out. The hands-on training is the most valuable part of it. 

We use the solution's error functionality. 

There's a little bit of a learning curve to build automations, especially in the citizen developer world. Usually, the technical people are busy a lot of times, so it's hard to get them trained. But as far as developers, they usually come along pretty well, from my experience.

We could use a little more interaction with users, like with UiPath, the vendor, and support.

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

We had a vendor that kind of offered to do a few, like bring you the UiPath and do some automations for us. We dipped our toes into that and liked what UiPath has, so we kept them.

I would rate UiPath an eight out of ten.