UiPath Platform Reviews

Currently, I'm dedicated to working within a finance organization. It develops processes in the scope of five months. I do not use the solution in a contact center environment. I work on projects for shared services.

It's FTE-saving. Since the beginning of this year, I have covered more than four FTEs. That means that for half a year, I saved three FTEs. That's a huge benefit.

The easy development process is very useful for us. I know how to use it, and I'm able to prepare and add to a solution in one or one and half weeks. It depends, of course, on the process, however, largely, if it's a simple process, it could be developed from the beginning very quickly.

It's very important that I can create end-to-end automation using UiPath. Thanks to that, the business is free to do more advanced processes and is not overloaded by less important, repetitive tasks.

I've noticed that UiPath has reduced human error. The first benefit is FTE saving, however, the second is quality of work. Human work, if it's repetitive, it's very often related to human errors. That said, if something is programmed really well and automated it works without the need for human intervention.

I had a problem with one thing and that was exporting activities packages between the test server and the production server. I'm not sure that it's my own issue, or a general problem from the global perspective of UiPath, however, I have a lot of problems with packages, using the test server and production server.

I've used the solution for quite a long time. I started using UiPath at the beginning of 2017. It has been more than four years.

The stability is good. Everything works well and I don't have any production bugs. I only have positive feedback, It works and there are no unexpected errors.

The scalability  depends on the developer. If we have an advanced developer, it is really easy to scale. If someone's preparing, for example, components, it is quite easy. From UiPath's perspective, it is easy to scale, however, that said, everything depends on the person who uses it and how familiar they are with the product.

I had a chance to contact UiPath when UiPath licenses needed updating. I had close contact. I wrote a ticket and I had contact with them in less than an hour. I was quite pleased with their response time. 

I made the right decision to go with a solution that can scale automation without having to pay attention to the infrastructure and to develop my skills in terms of RPA.

I had to do tests with Blue Prism and UiPath. Currently, I use UiPath, as I find it's much easier to use than other RPA tools. For example, I really like Orchestrator, from a user perspective. The control of both is really easy as it's centralized in NonProduction Orchestrator, and it's really easy to operate it. There's general ease of development. In Blue Prism, for example, if you want to develop something, first you need to prepare the object layer, and after that, you can go to the business layer and connect it in one solution. In UiPath, we create just a component and connect components together which is more logical.

I was not exactly involved in the initial setup as when I joined the company, UiPath had already been set up. Therefore, everything was prepared to start development. That said, for a few months, I worked in UI as a consultant for external clients. During that time I had the chance to install UiPath for external clients. In that sense, I've been involved in the installation of UiPath previously.

The initial setup's level of difficulty depends on a client's needs. At first, we need to think about the strategy of the client. In general, UiPath provides different types of architecture and it's generally straightforward.

The setup could take weeks if you need, for example, to order servers. However, if servers are already on-site, we can begin the installation. As I recall, I set up Orchestrator in a few hours.

We have calculations for that and we are on the right path. There is an ROI when using UiPath, however, I thought it would be higher. That said, we can calculate costs related to the UiPath environment and compare it to the automated processes created and we can see we are on a good path. It's hard, however, to provide exact numbers at this time. 

I'm not sure if UiPath has sped up or reduced the cost of digital transformation. It's a tough question, as the license for the solution is too expensive right now. In Western Europe, it may be okay to pay such money for a license, however, where I work now, in Poland, the license cost is too high for the local market.

We have a connection to ServiceNow. In ServiceNow, there is an approval process to publish UiPath processes on the Production Orchestrator, and that's easy. I'm able to set schedules or run a process model from our Production Orchestrator.

We have different servers for development, including a different server for Orchestrator and a different server for production. However, everything is in my company environment.

At this point, I only use unattended automation. Currently, there are no projects for attended automation as it's more for the business side. I am just a developer from the IT side. I am not involved in any business department.

I'd advise those considering the solution to find a really good developer and maybe a solution architect. Some time ago, UiPath had marketing such as, "everyone could be a developer," and so on. That said, it does not work like that. UiPath developers should have a large IT background. During my career, I've seen a lot of projects fail due to developers' lack of skills.

My biggest takeaway from the solution is that automation is a process that doesn't have a start and end point. It's an ongoing process.

Overall, I'd rate the product at an eight out of ten. If the licensing price matched the local market's capabilities, I'd give it higher marks. I would like to start deploying the UiPath solution in Polish companies, and there is huge scope to do it, however, for now, it's too expensive.

We primarily use UiPath for outsourcing. Customers call us when they need extra people to fill positions, on a temporary or permanent basis, similar to a temp agency.

The biggest use case that is running right now is that we get job openings or requests from a lot of different third-party brokerages, customers, clients, vendors, et cetera. They all arrive through different platforms. We get an email saying there's a request, please check it out and let us know if you have someone to fulfill the position, and the request is implemented through UiPath. It's automated. We've created all of the mailbox folders based on the sender and the subject, so we know which customer or which broker it is. Then, we make the email follow a link to the information for the job opening or the inquiry and we put it into our Salesforce system.

There are a couple of smaller use cases as well, where we have task operations that have to be done weekly or daily. Mostly it's reading emails or reading schedules and making changes in files.

The automation of job inquiries has a lot of sufficiency on how we operate as we used to have multiple people need to be available throughout the day to manually check if an email with an inquiry came in, and that would require them to drop work and open the email, check it out and maybe take action immediately. Now that the robot is running and taking care of the need for filtering through all the results for them, employees can stay focused on the other tasks that they have. They don't have to keep an eye on a second monitor every time and drop everything they're doing to read an email only to decide what is relevant or not.

I understand work has to be tested. It hasn't impacted the entire company yet as I've been here a little short of a year now and we haven't made that big of an impact just yet. 

The most valuable aspect of UiPath is the community in terms of the way they open up their platform to the community and make it freely available for people to try and to practice. The amount of feedback from that community makes it very easy for us to get into UiPath and if you're trying something that you've never done before, you at least have some insights. There's almost always someone who has done it before or who has asked the question. I would say the community is one of the biggest extra treats for UiPath. 

From a technical perspective, I like the learning curve in the Studio and in the orchestrator - or the Cloud Platform as they call it now - due to the fact that it's easy to get into. It's easy to grasp the basics and to get started. You can scale up as fast and as far as you'd like or need to for your customer. It can do everything. You don't have to learn everything in advance to be able to work with it. It makes it really approachable.

Building automation can be really easy. The biggest challenge is to find the easy use cases as the use cases in the company can get quite complicated quite fast. That said, using the recorder in the Studio and then converting that to work in a mobile office is quite easy. I started in 2016 or 2017, and between then and now there's been a lot of changes. It's always been easy for developer-minded people to get started. However, now with the introduction of StudioX, it is even more focused on the different users and they have a different entry point for them. What I like about UiPath is that the training is really comprehensive. You can almost just record what you do by hand and then StudioX will translate that into a robot and then you can fine-tune it to make it more robust. Smaller costs can be easier steps. Just press record, do what you do, and then you're able to work with teams. 

Scaling automation without having to pay attention to infrastructure does make my job a lot easier for now. What I do see in companies is when they've taken the first steps and they start to scale up, a lot of them have policies or ways of working in place where they want to stick to the ways that they know. A lot of time I see customers will, in the end, do it by themselves anyway, so they use all of the upscaling functions that are available as they want to do it the way that they always did. 

UiPath enables us to implement end-to-end automation starting with process analysis, then robot building, and finally monitoring of automation. However, while it does facilitate end-to-end automation, it does take a lot of the development and running and monitoring of the robots on itself. That is something that is facilitated really well by UiPath. The process discovery and the analysis is rather newish within UiPath. Maybe it's not as well integrated into the community platform.

At this time, UiPath has helped to minimize our on-premises footprint as it is a cloud-based solution. It's important that the on-premise footprint has been minimized as it makes it easier for us being a small company. We have 160 people working for us in the Netherlands and then a couple in the Caribbean. Bringing new technology in like robotic process automation and then asking from the IT department to get me free service and results of my configuring and have all the discussions about what goes where, how the security works, how to find the work, who gets access, et cetera is easy. This is due to the fact that UiPath is offered on a cloud basis and I don't have to do all that on-site work, which allows me to get to building and talking about RPA quicker. 

The fact that the vendor handles infrastructure, maintenance, and updates saves time for our IT department. It helps us to implement a lot faster. The client companies can have a reliable cloud solution to help them do at least the first steps to get them acquainted with the product. It makes it a lot easier. It helps me a lot, and it helps our customers in starting out as well.

UiPath has decreased the time to value in that since it's cloud-based, I can deliver faster than I would be able to do on-prem. If we have an idea, or if we want to scale up, we can do so faster in the cloud solution than I could on-prem.

The product lowers the overall total cost of ownership by taking care of things such as infrastructure, maintenance, and updates, however, I'm not sure what would happen if we scale up.

The automation Cloud Platform has definitely helped reduce the time it takes to create automation. It brings a lot of things together. It's easy to use for clients and customers. It makes it easy to bring different disciplines together, so I don't need to think about how to reuse my code, or how to explain to the customer, and I don't need to share the processes to be able to release, run, and monitor and to get reports on the results. 

UiPath has reduced human error. There are fewer errors and the processes are less error-prone and once the technology has proven itself within the company, within the customers, people start to trust the robots to do what they do. Employees don't need to check the work that had been done as they know that if the robot reported that it was done correctly, then it was done correctly. In that way, it has saved a lot of time by not having to check anything. 

It has also freed up employee time. It's a three-person team and it saved them a couple of hours a week doing the work that they used to do. It saved them a lot more focus as they didn't have to monitor the email inbox all the time. They were able to apply more focus to the other things that they were doing. That said, it's hard to quantify the gains. However, overall, it has made them happy. That's one guarantee. They absolutely love that they gave the mundane work away to the robot because it was bothering them to be monitoring an email inbox all the time. It's given them the time to focus on cases that match the right people to the right inquiries or openings. I don't have any metrics on it, however, anecdotally, they tell me that it helped them to do the rest of their work better as they could apply more focus to more important tasks and placements are better attended to. There's much more focus and attention and better matches being made.

The solution has saved costs for our organization.

I'm trying not to sound negative about it as I like them a lot, however, the process mining and the process mining features stem further away from the development of the robots and the monitoring. The development, run, and monitoring are really closely knit, or really close together, and then process discovery is starting to get there. It's on its way, however, I don't see that it's as closely connected as the other three parts.

The automation operations have not brought down any company costs. Automation operations have gotten more expensive due to the fact that we added UiPath to them. That said, you do get gains at a different branch of the company. We didn't replace anything with UiPath. We weren't able to skip a step or program or tool, which makes it an added cost.

More documentation would be helpful, as they change rather quickly. There are two yearly stable releases and then a couple of community releases and data releases in between. Sometimes not all documentation is changed as quickly as the features are. Sometimes you can find something in the documentation that is not the answer, or not available in the product anymore. That's simply a side effect of how fast they develop the product. 

Sometimes it's not entirely clear what features are, for example, available in their community edition, or in the on-prem, or in the cloud. The difference between the on-prem and the cloud has become clearer in the past few weeks, however.

I've been using the solution for three years now. 

I started out at my previous company with systems integration. We started out with discovering robotic operations, discovering the tools, and suppliers. We chose UiPath and one of the competitors, as we found them to have the best suit with our customers. That was the end of 2016. That's when I started doing training in UiPath and started doing some custom integrations.

Now, I switched to a new job at a different company where they want to start an RPA practice as well and they chose UiPath solely for RPA.

From the operations standpoint, the stability of the cloud it's very good. I haven't had any issues with stability. The Studio will crash at random times. I've identified two scenarios where I'm able to make the Studio crash every time by just doing the same actions.

However, other than that, the automation was really stable, and I haven't had any issues or incidents. In Studio, I'd say it is good enough, however, there is some room for growth there.

Scaling automation without having to pay attention to infrastructure is a bit pro for UiPath as I'm starting an RPA practice. We don't have a lot of infrastructure engineers to build the project yet. Therefore, a lot of the time, with new customers as well, it will be a bit of a one-man show. Yet, what we can do is communicate to the platform and then make sure the infrastructure is there and then implement the platform and build a business analysis basically in an un-built realm. I have to do a lot of things by myself, so the fact that UiPath brings in the Cloud Platform and the Studio and it's all integrated and you can scale up without having to have too much. You need to know something about infrastructure to understand what it does for you, however, you don't have to do it all by hand. I don't need like three or four DP-trained individuals to be able to scale up or scale out. It's helped me get further faster.

Once you build the infrastructure and you know what you're doing and you know where you want to go with your platform and scaling, it's rather easy.

The only people really using it at this time are me and six trainees. There are a couple of ops people as well that are able to log in. We might have a total of ten people on the solution.

It's not being used too extensively now, however, that's for a large part due to the fact that most of my colleagues are working with our customers, so there are not too many internal processes or tasks. However, we do have plans to increase its priority as the tasks that we do have are at some points largely repetitive. We do a lot of operations and maintenance for our customers as well in different fields, so we are mainly looking at that for further automation opportunities.

Technical support has been pretty good. 

I get a quick response and it's usually constructive. I manage to fix my own problems a lot of the time using the community forums and information from there. I haven't had too much interaction with UiPath tech support.

We did not previously use a different solution. 

I personally implemented the solution at my company. 

We currently have it running, so some internal processes. And, we're looking to expand that into the customer landscape.

The setup is simple. They deliver it in a cloud environment, I didn't need to do any installs or make any arrangements.

You need to make an account and get started and watch a couple of training videos that will help you through it. The adding of the robots is very well documented in the forum, in the community, and in the training sessions. They have made it really easy to get started and to get the information you need to take the first step.

The deployment question is a tough one as I started out at this company while already having a communicators subscription on my own account. Therefore, I started out using that one and then gradually shifted toward using more automated resources. I don't have a clear overview of how much time it took to deploy. It might have been a couple of weeks overall, however, I was doing different things at the same time, and I never took a metric of how much time it took. I'd say starting out if the prerequisites are in place at the company, it could be a matter of days.

Tasks such as setting up an account, getting some service, et cetera, if you know what you're doing and you know what to ask a few questions before starting, it's a couple of minutes or hours. That said, in reality, there are always things you forget or things that they didn't do, so it always takes a little extra time.  

My implementation strategy was basically to figure it out as I went, which is not the best strategy, however, it was the best we could do due to the fact that the company didn't really know what they wanted to do with RPA. I was figuring out my own place in the company and then their wishes with robotics with RPA. There were a lot of things at the same time, so there was not a closed strategy other than to start up quickly, as soon as possible, get feedback, and then try again.

For now, I alone handle deployment and maintenance tasks. That will be the case until our trainees finish training.

We did not use a third-party service such as an integrator or a consultant.

We have not yet seen an ROI and have no concrete plans for any in the near future.

While I have one or two sheets from old presentations that have pricing information, they are over a half year old. I have no current insights. I wasn't included in discussions between the company and UiPath in relation to licensing. 

The company might have looked at other options. However, they did this before I was hired. Ultimately, they did want to choose UiPath, and I was hired based on my experience with the product. They chose UiPath at that time as they were working together with Oracle and that company has always been very Oracle-minded.

I use the community Studio and the Cloud Platform. I take the cloud from UiPath. I'm not sure where they host their solutions. I use the automation cloud from UiPath.

End-to-end coverage is not too important to my work at this time. Maybe if they were more closely integrated, I would be able to offer it more easily to my customers. However, now, due to the fact that I often go in at the first interaction with a customer or at a company, I have to introduce the concept of RPA, I have to introduce the product of UiPath, and I have to introduce or orchestrate the Cloud Platform and Studio. What I've seen is that that's enough for the first steps, usually, the company will have a pretty clear vision of what they want to start out with in terms of automation. However, introducing the process mining capabilities would add an extra step to the start-up that we have to do and what they want to see is faster results in the early phase. It's short the time from when I come in to initiate the first value, so they can appreciate the value and start the business cases and go from there. Maybe, once they are a couple of steps further on and they have a couple of automations, then they go look at the process of task mining as they have the infrastructure, they understand what the process automation is about, and then they start to see the value process or task mining. Therefore, the end-to-end factor, for my job, for now, is not too important as I don't truly use the end-to-end approach. I do the start by myself with the customer and then we go from there. Then, in the next phase, I will build them practices and they will start to automate the beginning of the process discovery as well. There is not something that I have initially do. Once companies start beyond that first phase and the first steps, then process discovery and process mining can be really important in automation. In a later stage, it becomes more important. However, in my case, I work a lot in the early phases and haven't seen too much of the process discovery products in that phase.

Attended automation hasn't really helped us scale RPA benefits as we are a rather small company and there's only a small group that works with the product, and therefore, we haven't been able to use the assistance in the same way a larger organization such as a bank or insurance company might use it.

We don't use the staff solution yet and we have not taken advantage of the AI functionality. While I have played with AI, I haven't had any use cases to implement the AI sensor.

Overall, I am quite satisfied with the product.

I'd advise new users to start by doing instead of only reading. Start small, like finding small processes or if you're an individual, look at your own work. Find something you could do and automate that as it gives you the best appreciation of the value. Try it out in your own environment and just explore how it goes as that gives you the best insights. For me, when I started, it was a great feeling to watch your screen and watch your cursor follow the screen without doing anything. 

Keep asking questions when talking to users. When translating the biggest use case into other processes, spend more and more time talking to the users and going through the processes, and defining and understanding what happens. Otherwise, it's going to cost you a lot of extra time figuring out why you've got all these weird exceptions that you didn't expect. Everyone always talks about how easy robotic process automation is. However, only once you understand your processes from a user's perspective, you'll run into a wall. It's never standardized. It's never the same. I need to warn my customers more frequently about this pitfall, due to the fact that, yes ultimately, it's very fast, but it only is once you know exactly what you want to automate and that's why most of the time it's time-consuming.

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

We do not directly use UiPath in our organization but we do have some use cases. One of those is sending bulletins. These are the notification emails that go to users on their birthdays, on their work anniversaries, sometimes they are sent after some sort of achievement, like if they have a baby. These notifications go via UiPath. 

The way it works is that the data is maintained within our tracking sheet, which is sometimes on SharePoint, and UiPath uses this tracking sheet to check the data in addition to the user and will cc everyone within the organization. For example, when we receive birthday emails, it goes to the person whose birthday it is on that day and cc's in everyone within the organization or within the relevant department. 

In the case of one of the clients I've worked with, they're working on a process where they need to provide students with a student visa pass. It's within Singapore and every student that has joined this institute needs to apply over a website. 5000 applications are received every year. These applications need to be manually added to the government website.

We automated this process, starting from the beginning to the end. There's a lot of interaction required. The team worked on an Excel sheet. In fact, a number of people work on these Excel sheets. With many people, there's always a chance of misleading data, as I might at one point be doing some more revision on the sheet, and someone at the other point might be doing more revisions. There is the chance that data will clash. In order to make sure that this won't happen, we came up with a SharePoint list where we could add the data, and if anyone changes anything, there's a simple and clear record of who made the changes, and what the change was.

At the same time, the bot can work on the SharePoint list as well - and there is no chance of a clash occurring. We can create a process and a number of steps that involve reading the data and extracting data from an application while swapping or extracting data between two forms. 

There's a lot of swapping. We extracted the data via the backend, via the database, and directly put that into the IC application. The processing time for this application previously was somewhere around 20 minutes. Per record now, the time has been reduced to three minutes. Previously, there were 18 people working on any particular application. Right now, there are only two bots working on this website, and they are doing work like magic. 

If we look at the development part, UiPath Studio has been great due to its ease of use and its UI. The availability of the UI store helps us understand the complete pre-hierarchy of the UI elements that's available on the browser or website. It's easy to use and it can be manipulated in the way we want it to. It allows us to do more work on the browsers. 

The integration aspect is very useful. Right now, I'm working on SharePoint and that integrates nicely with UiPath. The integration model is really, really great, and 99.9% of the time it works. While technology can fail occasionally, UiPath has a great track record. 

The ease of building automation using UiPath is quite good. The kind of projects or processes we have been able to automate has been helpful. We need to determine if it's a complex process, which is dictated by the number of steps. We look at the number of steps and work to determine if we can improvise and reduce the number of steps, and, if so, how. We look at if the process ever requires human intervention and where. The type of human intervention might dictate the complexity of the process, as well, for example, the number of applications we are working on. We might have to write some code on the backend or maybe we are working with an API. Everything needs to be assessed before going into an automation process.

UiPath has reduced human errors. Previously, everything was manually tracked with changes noted on the tracking sheet and we would do a copy/paste from one place to another. There was always a chance of human error. However, when this process is automated, there was zero chance for mistakes. While there may be exceptions, it would be only in rare instances the automation itself would make an error.

The product definitely reduces cost. If a company deploys automation within their organization, they need to understand that automation needs some time. One process will not necessarily reduce the cost. They need to see there will be results in the long run. It just takes time and they have to understand automation. They have to implement automation within the organization. Often, organizations will start the automation process, and then they leave it as they believe the cost is going up. They perceive this due to the fact that they need a separate system for development, a separate system for testing, and a separate system for operation, plus they need three servers for the Orchestrator. However, in the long run, automation actually lowers costs. It's just a hard up-front number to look at.

Whether or not the solution has freed an employee's time depends. If you talk about the business level, definitely not, due to the fact that, for them, it might be a burden. To the business, it might be a burden. However, if you talk to the IT department or IT level people who are working differently from users they would say that the best thing is that deployment is easy, debugging is easy, logging is very easy, and tracking is very easy. Anyone from IT can easily track how things are going. Yet, if we are talking about it from the point of view of business, for them it's not their cup of tea.

For example, if the system freezes on a person, they just close the browser, however, if the system freezes on a bot, from that moment everything must be manually re-initiated. For a regular business user, doing that process may go above their head and they may not understand how to fix it.

The Orchestrator portion can be difficult. Previously, the Orchestrator which everyone was using, was quite simple to use. However, the new one is quite complex to understand. Even with developers, they sometimes don't understand it either. 

There's a lot of things coming up that need to be learned. They need to put some more information into the academy to help others understand the Orchestrator end-to-end, especially for the new version. The previous one was quite easy. The new one is very inefficient in terms of the user interface. That's the area that I find still needs improvement.

I would suggest that they should provide a more disciplined document where users can see what exactly needs to be done in case of failure. For example, there's a very clever document on the deployment of the setup, but there's no documentation on what happens if there is a failure. Users need to be made aware of what to do if exceptions happen. 

UiPath is already aware of these exception scenarios, and when you call support they know what needs to be done. These details need to be on documents somewhere, maybe in the form of knowledge articles. That way, if someone has some issue, they can go to an article and see what's going on. 

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

Stability-wise, it's really good. When it comes to backend automation, it's amazing. With the UI automation in mind, I would say it's quite stable. However, there is a chance of errors. I would say, if you're doing a process based on a UI interaction, the stability it gives is somewhere around 5% to 10% on each process. Again, it depends on a number of things, such as the start-up package you are working with and/or what is the response of that individual. It's something that somewhat falls outside of UiPath, in terms of stability, however, when it comes to the process, everything counts. Even, for example, electricity counts. If there's system slowness or a system crash, it can affect everything, even if it's not necessarily caused by UiPath.

Attended automation has helped to scale RPA benefits. It is scalable, as, moving forward, there are multiple processes in relation to the same person, and right now it's done manually by a number of users. Probably, in the future, we can help develop a direction for that. Right now, the client is happy with what they got.

The solution is quite scalable. It's easy to scale a process or a UI. With big automation, it depends on the number of people who are going to utilize it. In those cases, we need to make sure that that network is available to scale. If you don't take into account the number of users, or if there are a lot of people using it, then the chances of failure can go up. That said, it depends on how big the organization is and what sort of licenses were bought from UiPath. 

I have not really used technical support, and therefore cannot comment. With Studio, we've had maybe a few minor interactions. It's the same with Orchestrator.

I have worked with a number of tools including Automation Anywhere, Blue Prism, WorkFusion, Kryon, and Kofax. I have knowledge of a lot of other tools. 

Kryon, for example, has a process discovery feature, and UiPath also started up with this process development. However, what Kryon provides is amazing. The way they capture everything, the way output comes, the way each step is explained with the process, et cetera, makes discovery on Kryon amazing. In comparison to UiPath, UiPath just isn't as good in this area.

WorkFusion integrates well with the part where we have to read documents, especially bot scanned reading. UiPath does not have these capabilities, as of now, on its own. You can integrate Abbyy with UiPath, however, that's a different tool altogether. With Fusion and with Kofax, these features are amazing. On top of that, their invoice capabilities are amazing. There's a vast difference between UiPath and Kofax and Fusion when it comes to reading documents. 

That said, when it comes to working on the backend automation, when it comes to working with the UI automation, UiPath stands out from the crowd. It's amazing. The way it writes, the way it provides precision handling, the way it works with the queue, et cetera, is amazing. There is no other tool on the market that offers these capabilities. 

The one feature that I believe should be better with UiPath, however, is storing data in an independent manner. With UiPath, even though you store your password on the Orchestrator with the credentials, or even with any credential manager if you get at the end of the day and somebody has not reviewed your quote, you can tell your boss to send his password in a simple text format. This is where the UiPath lacks, and this is where Blue Prism comes into the picture. It's just better at securing data. People prefer Blue Prism for this reason over UiPath. 

With my current organization, the department model is quite simple. We have three different environments for this: development, testing (what we call acuity), and production models. We have these three stages of deployment that we deploy robots and the Orchestrator based on the requirement of clients.

The deployment took a maximum of one to two hours from one machine to another machine. A complete department deployment, however, depends on the process type we are working on, as there are some features we need to develop. Apart from publishing these packages, the deployment of the server, or of the Orchestrator, or the deployment of Studio, will take a day or two to do the complete setup on one machine.

In terms of the implementation strategy, the first thing to do is the pre-checks. We need to figure out what sort of system we need. Therefore, we need to first confirm the prerequisites. Once that is done, we need to download a package and install it, and then apply the license. After all of that, we just need to create one small robot just to check that everything is working fine. There are some tools that need to be installed with that. For example, if we are working on UI automation, in that case, we need to install an extension. If we need to install the network load balancer as well, we need to install some of the prerequisite packages on the machine, on the server, to make sure that this runs smoothly.

While the licensing models are quite simple, as a developer, I don't handle details about pricing or cost.

My company does not directly partner with UiPath, however, it's a partner via a client. If anything happens with the client, it goes from my company via one of those stakeholders who take care of these things.

Currently, we use attended automation. The reason being is, it's more about password prediction, as the company does not want to store the passwords. There are a number of options that we have given to users where they can store their passwords in the credential manager. However, the company does not want to do that. The only reason we are using attended is for this, which is that the user has to manually go and insert the credentials.

I have not yet used UiPath's AI functionality in any automation programs. I have done some POCs for this, for documents in this setting. However, we've never practically implemented it within the organization.

With the current organization and with the current client we are not using Orchestrator at all. We only use attended robots and not Studio and Orchestrator. However, with other clients, we have used the cloud-based enterprise Orchestrator and have had the Orchestrator installed within the premises of the organization. I've used both.

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

Earlier, there was no integration of PagerDuty. In any process, we had been working with many stakeholders and many other clients, however, sometimes if any process needed to be done at a particular time, for example, 8:00 AM in the morning, and was not running at that time, we would get a failure message. Now, we instantly get an alert on our phone, or we get an alert on Teams or Slack. This UiPath integration, with all the features, is very beneficial as it is keeping us up to date and on schedule. If there are any failures the production support team can know and handle them immediately.

All the features, all the packages, everything, have been great. All of the artificial intelligence which we are getting is super-useful, as are all the needed updates.

All the features are valuable as, much like any application, it cannot work without just one feature. For example, we have PDF automation, we have Excel automation, Citrix, SAP, and we have SharePoint automation - which makes it so that we can automate anything. All the features combined allow us to work on multiple projects or one specific project. 

The ease of building automation using this solution is good. I really enjoy the flexibility. It's also very easy. We do need a few coding skills with languages like C# or Power Automate. However, it's got a good UI, with drag and drop functionality. That makes it easy compared to other tools, like Prism automation. UiPath is much better and it's highly recommended.

Scaling automation without worrying about the infrastructure was easy. I simply did some googling and looked to see which automation tools were out there and which was the leader. There were multiple training portals - including UiPath Academy, where I was able to pull all of these tutorials and insights. There's also a free forum where queries are answered. It made everything quite easy. 

The solution enables us to implement end-to-end automation starting with process analysis, and robot building. This end-to-end coverage is important to me as we follow an agile methodology. We have an RPA development life cycle. This product gives us all the tools and everything we need. The requirement gathering and document preparation come as standard models. We have UiPath Studio for testing and UiPath test features for maintenance. We have the Orchestrator where we can maintain everything as well. We can see where things are working or not. In fact, we have integration with PagerDuty that gives alerts if something is failing or not working. It's really important that UiPath has integrated across all the life cycles, and that all the phases are working properly.

UiPath has helped to minimize our on-premises footprint, which has been very important to me. It's very important due to the fact that we can build a robust and scalable solution for an enterprise and have security in UiPath. It's very important that customer satisfaction is there, no matter what we are developing. It's very important to our organization.

It's a very fast solution. It can provide a result or automation to a business process within seconds. If we have an API, we can integrate EPS as well instead of using the UI. Basically, we can get any solution we need within seconds. It's very fast.

I have noticed that the solution reduces the cost of digital transformation as we are saving on manual hours. It's reducing them. We don't have to hire more people to do these manual jobs, which has helped us reduce the cost.

We did require application upgrades and IT application support. We wanted to update and get all the latest features that UiPath often releases. I've seen every month or every year we get all of these new packages. It's better to include the latest version to get all the latest features.

With UiPath, we have reduced human error. Humans are prone to making errors that they can make at any time. The bot does not. It's continuously given proper feedback. The lack of human errors has affected business a lot. The bot allows for complete confidence that perfect work is being done. It has also freed up employee time. We've saved thousands of hours. We have ten processes that are running in production. Up to this point, with those running, we have saved up to 1,918 hours from the automation. On top of that, employees can now focus on higher-value work. It has improved work satisfaction. There is more self-motivation that boosts the work, which we are doing.

The solution has reduced costs overall via automation. However, I cannot speak to exact cost savings. As a whole, it's saved our organization money.

Right now, we don't have many use cases in the field of NLP, natural language processing, or artificial intelligence. There are not many tutorials or any videos or enough insights shared by the UiPath Academy. If we could get more insights, that would be great.

With artificial intelligence or natural language processing, we need to get in touch with the servers, however, we cannot do it without getting a proper license. Maybe a mode of artificial intelligence and natural language processing should be included without needing a different license.

I've been using the solution for the past three years. I am currently working in Rackspace Technology. It's been two years looking at it now and one year in my previous organization, which was essential.

The solution is very stable. 

It is scalable. So far it's not been getting into trouble, and we haven't tested the boundaries, however, it's scalable.

I've been using the solution for the past three years myself. We also have a developer and some bigger production staff. There might be a few people who use it here and there. 

It's been extensively used in our organization. We are getting in touch with many internal clients, internal business units, and getting more projects. We are in the process of expanding it. Right now, we have five to 10 business units, such as accounting, et cetera, and we are trying to expand further out to other departments. 

I've never used UiPath technical support.

I did not previously use a different solution. 

The initial setup was easy. We basically had to install UiPath Studio and the tool, as well as the orchestrator. It was quite straightforward and easy.

The deployment process was just a couple of minutes. It was maybe five minutes. Not more than that.

We didn't have much of an implementation strategy beyond setting it up and working with a model via the deployment team. 

We handled the implementation ourselves. 

While I have noted an ROI, I cannot share specific data points.

I don't know much about the buying, the pricing, and other cost-related details. 

I did evaluate other options, such as Automation Anywhere, however, I have found that UiPath has a better interface and all the activities can be seen more visibly on the screen.

We are just a customer. 

At this time, we have not automated departments or role-specific processes that require human-robot collaboration. Mostly, we have unattended automation such as NOMA inclusion. We do not use the AI functionality in our automation process just yet and we do not use the solution's automation cloud offering. We also have not used the UiPath apps feature.

I would advise users considering the solution to try it once. The community edition is free. You can explore and download the community edition and take note of all the features which UiPath offers. If it suits the company, I would advise users to go contact the UiPath technical team or support team and get more information on how to implement UiPath.

The more you explore, the more you'll learn. It's not just the straightforward drag and drop functionality. Many people say that UiPath is just for a person with no technical knowledge. However, the more knowledge you have of the technical side, with an understanding of languages like Java, Python, C#, the more you'll excel as it's based on a .NET framework. 

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

I'm using the product primarily for building automation projects for shared services users. It's for internal customers. It's a shared services center for finance, HR, IT, and all processes like that.

UiPath enables you to implement end-to-end automation starting with process analysis, then robot building, and finally the monitoring of automation.

I use UiPath mainly for building a robot. I always use unattended bots. However, I also use it for task capture. I use the Task Capture feature a lot. It's pretty much a game-changer since Task Capture has become available, as creating documentation takes a lot less time than before. As for UiPath, I'm using it for building a solution and then testing using not only UiPath but also Orchestrator. In the end, we also use some document templates from UiPath. It's pretty much present all the way through the life of a project.

UiPath has sped up or reduced the cost of digital transformation in our organization.

For me as a professional developer, this is an obvious fact, however, people can notice that the robot can do their job a lot faster and they can concentrate on completely different things. They don't have to do simple tasks, repetitive tasks, and that's when they realize that this transformation is happening. Some people did not believe that it would happen so fast, yet, by using UiPath, we can prove to user that a process can be transformed into an automated one in a really short time.

It's reduced human errors in our company as well. I can use an example as a VAT declaration. That's one error that would cause some financial consequence for our business. After creating an automated project process, it is impossible for a declaration to be submitted with an error. It's basically eliminated typos or human errors in the case of VAT declarations and financial consequences.

The solution has freed up employee time. It's difficult to estimate how much as there are a lot of projects and I'm not the only developer on. However, thanks to my bots, we could free up, so far in half a year in this company, two FTEs, two full-time employees. Obviously, it doesn't mean that these people were let off. They are doing their job, however, they've just got different tasks, more complex tasks to do.

Mostly I'm using Studio. This is my main tool for work, and, for Studio, I can say that this is my favorite out of all the automation platforms. 

I like the fact that you can use and customize activities from the marketplace. The fact that even though the built-in activity sometimes cannot cope with some tasks, you can still find solutions outside of UiPath, internal kinds of built-in functions. You can use the third-party package marketplace. 

I like the way it handles debugging as it's very comfortable and it keeps the project under control. 

I'm also using Orchestrator. The newer version of Orchestrator is really very user-friendly and it's easy to manage projects there.

For basic automation, it's very easy to learn and it's easy to use. It's intuitive for basic functions. However, for more complicated automation, it gets more complicated. This is expected. The more advanced the project, the more advanced the skills you need. That said, as a basic product for simple automation, it's very easy to use.

The solution is user-friendly and has great training materials available.

I use the solution for automating my own work sometimes. I work at building small robots to make work go faster. For example, I'll create a robot that will help to create documentation. For example, analyzing arguments and workflows inside a project and outputting them in a DXC file or things like that. It's small ad hoc automation that makes life easier.

At the moment, I'm pretty satisfied with it. Thinking about UiPath, I can't see any downsides and the downsides are in like companies' infrastructure.

At this point, debugging, for me, is lacking the ability to edit on the go. It lacks the ability to stop the process on a breakpoint and being able to edit or even go a step back. At the moment when I'm debugging I'm only able to stop the process, check the locals etc. It is not possible to change anything in the code, go step back and try the changed code. You have to start the debugging process from the beginning. It is just slightly annoying and it was there since I started with version 2016. It's not a showstopper at all, just adds some time to development. I'm not even sure it could be done technically, it's just a wish.

I've been using the solution for about four years at this point. I've used it for a while. 

There are occasional errors happening, which cause the software to freeze up. However, this is not more than once every two weeks and I'm always able to recover the project. I would say it's stable. Regarding working automation, I also have no problems as the errors that we have on ready robots never result from UiPath's issues. They result more often from infrastructure issues or robot problems.

Regarding UiPath scalability, it's great. It's one of the biggest advantages. Over the years, you're able to build a library of modules that sometimes make your work a lot faster. You can use a few modules and you will have 70% of the project done. Every module that you work on, which is new and can be reusable, is very easy to make into libraries and to reuse.

In my organization, closest to me, there are only about five or six people on the solution. However, we also use external contractors and consultants who use UiPath and there are even UiPath MVPs there. That said, in my company, it's only developers, operators, and a project manager.

We have plans to employ more developers and to increase usage. 

We have an RPA department, which is using it and it's cooperating with all other departments in terms of creating automation. We have specialists that are specializing in using UiPath for automation. We create automation projects for every department that requires it. The people who are using UiPath are using it pretty much full-time. It's a full-time development. We are planning to increase the size of the development team as the projects are flowing and the backlog is growing. From the business side of our company, the satisfaction is high. The demand is growing.

The solution has exceeded my expectations over the last few months and technical support overall has been great. The way they approach customer service and help us through issues has been great.

The initial setup is pretty straightforward. I'm not a system admin or anything like that and I was able to set up UiPath on the server. It's pretty good.

How long it takes depends on the database that I'm working on. That said, last time it was not even the one full working day. It depends on how much data you have to back up. Usually, it's a few hours.

While I'm not the correct person to ask about ROI, I can say that UiPath has reduced the cost of our automation operations by making it 30% faster. 

I don't know the exact prices, however, I know that compared to other companies, other solutions, it's the best value for money, at least in our country.

I tried Automation Anywhere and also Blue Prism. At that time, there were only these three available for us. That was four years ago.

We are customers and end-users of the solution.

We use the enterprise edition of the solution.

At the moment we are not using the newest version. It's 2019.

It was not my choice to use UiPath. At the beginning of my automation career, it was chosen for me. However, I was able to test other automation software and give my feedback to the employer and UiPath was the winner for me. At that time I was a finance worker. I was not a developer, a professional developer yet. For me, it was the user-friendliness and the way that you could very easily start your adventure with it, and then learn as you go. I have to say that the training packages for UiPath were very good and are enough to make you start working with it.

In my experience, I would say that it is the best platform for people who are willing to learn to automate. Also, if you want to use automation software, you have to consider hiring someone who has experience in it. Even though UiPath is so user-friendly and so intuitive, you still need to have a professional who has some experience.

It's very important to educate people to make them aware of what the RPA is. To be honest, from my experience, humans are the weakest link here, and people who are submitting, for example, input data for robots, cause the most problems. It is important to invest in the education of people and to raise awareness about RPA. 

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

I am a service provider and developer who implements UiPath for our clients. But in the company that I work for, we also use UiPath to make invoices for ourselves and, mainly, for payroll activities.

We need to get reports from our HR tool and combine them with another source of information where employees are recording the hours they spent with various clients. We then create the documents needed for the IRS. In our case, all the users of UiPath are data entry specialists in different departments, such as HR, finances, and marketing.

UiPath definitely helps reduce the cost of digital transformation.

It also reduces human error. We can be sure, given that our test case is successful, that there are no errors when none are reported. This definitely helps businesses. Errors generally lead to work being postponed. When errors come back to someone at a given point in time, they can rapidly overwhelm that person. With automation working, this is no longer the case because everything is smooth. And if there are errors, they will resolve them one by one.

In addition, it definitely frees up employee time. That is the purpose of automation. Unfortunately, I can't share metrics about this. But the additional time enables employees to focus on more important work and that affects employee satisfaction. Repetitive tasks make people irritated about the nature of their work. When they can work on new tasks that are more complex and creative, it makes an impact on their job satisfaction.

UiPath saves costs in our organization because we don't have errors where it is deployed and because it has reduced the number of FTEs who do repetitive tasks. On average, within a small company, it can save up to 10 FTEs.

One of the most valuable features is that UiPath is easy to deploy, especially for medium-sized companies. It is also easy to scale.

Also, the fact that you can scale automations without having to pay attention to the infrastructure for doing so is quite critical. The infrastructure could require a lot of maintenance resources and affect costs, so that feature is quite important.

UiPath enables you to implement end-to-end automation, with its full range of tools, starting from Automation Hub, which is the initial point for gathering your processes from business lines. It's driven from employees or a center of excellence, and goes on to include implementation, and the reporting in Orchestrator is quite powerful as well. The end-to-end coverage is important, as clients always like one tool that covers their needs and plans.

The only thing missing is something to track the development cycle. We use third-party tools to do that. That is the only gap in UiPath.

Also, scheduling of UiPath robots could be improved. Scheduling is a feature for defining in what sequence, and on what machines, you want your automations to be launched. That area could be improved.

I have been using UiPath for more than three years.

Overall, the stability of UiPath is about average. We do have some instability, because of workloads that are too massive for Orchestrator, but it could be that it was not installed in the right way.

Scalability is connected to the stability. The situation I noted when talking about the stability of UiPath happened for our largest client, where they already have 160 processes running. There are problems with the maintenance of such a large number of bots.

But in terms of increasing our usage, we are in a phase with our clients in which we are constantly enlarging the automation within their companies.

UiPath support is definitely willing to help. They will usually propose a call, if they think that will be easier for solving an issue. Their services are quite good.

We did not have a previous solution, except for Excel macros.

It is relatively easy to deploy. Of course, it's not as straightforward as a simple application installation, but with the help of UiPath, in particular, or with the help of the UiPath Community Forum, which is quite enhanced with answers about installation, it's not a big deal to install it.

Taking into consideration internal IT restriction and internal IT resources, deployment can take up to two weeks.

Our deployment strategy usually involves convincing clients that they need to start setting up a center of excellence for automation and then there are lots of initiatives that need to be undertaken within the center of excellence. Among the most critical are awareness, dealing with IT stakeholders, and of course, the capabilities of developers. Taking care of those things will lead you to a smooth path for digitizing the first processes, which are low-hanging fruit. The further you go, the more you can then enhance your automation with the more advanced capabilities, like AI, Document Understanding, or chat bots, et cetera.

Deployment of one robot takes about three months and up to five people. We need an SME who knows the process that is being automated. In addition, there is usually a business analyst who tries to help optimize the process so that it will work better with robots. We need a developer, of course, and we usually have a data solution architect who helps to ensure that overall infrastructure is functioning. It also helps to have an automation evangelist on the business side.

We have two roles for UiPath maintenance. One is the IT maintenance guy who makes sure the VM is working correctly, and that we can easily scale from the infrastructure perspective. The second role is the operator, whose day-to-day tasks include scheduling the bots correctly, implementing quick deployments by creating assets in Orchestrator, and maintaining things from an RPA perspective.

ROI usually takes six to 12 months.

Licensing is quite complex, and sometimes that's true even when we have to explain it to our customers. There may not be a way to do it more simply.

The only potential additional cost when implementing UiPath involves the third-party tools. It can be a quite big portion, of course, so you should consider that aspect. Examples would be integrating different systems within a company, systems such as Salesforce, SAP, or ServiceNow; all of the main CRMs that businesses use.

We looked at the main competitors, Blue Prism and Automation Anywhere. The decision to go with UiPath was based on contacts we have, clients who had already implemented RPA. We got better feedback about UiPath from them.

The first thing to consider within your organization is whether it's easier to deploy it on-prem or via the cloud version. Then focus on how to structure your development team. It can be either entirely a third-party service provider, or in-house developers, or it could be a hybrid. The third thing to consider is what the cost center will be for RPA implementation in your company.

The marketing side of how easily you can build automations with UiPath is a bit exaggerated. You definitely need some programming skills to do very powerful automations with it. But it still provides various levels of development tools, meaning that you could have zero programming experience and still automate some processes in your company.

UiPath is definitely the market leader in RPA. The biggest lesson I have learned from using it is to start with the low-hanging fruit, and then go on to more complex stuff.

I am currently involved in healthcare-related projects and wholesale/retail-related projects. Previously, I was involved with banking and financial services, healthcare, and retail.

My current company is using a combination of the UiPath tool and SAP automation.

In my previous company, I used the UiPath tool for many projects.

It has a very easy drag and drop process and logic base setup. Previous projects were taking a lot of time. However, when we used UiPath on the same projects, instead of a process/task taking a day, it was now taking anywhere from 10 minutes to five hours.

There is almost no human involvement. For example, in banks, a bank manager will receive so many loan applications. We create some bots to check the requirements after validation and do the follow-up work. The manager is only checking boxes for the final approval request.

In the banking sector, I am using AI Center and creating some workflows. Some machine learning is needed to create these workflows in AI Center. This gives us a 94% accuracy, which is good accuracy.

Document Understanding is a good feature. It is a combination of artificial intelligence and machine learning. We have created some workflows using Document Understanding. We are using its machine learning to do some language analysis, semantic analysis, and invoice processing. UiPath currently provides some language conversions, such as German to Russia and Russian to German. However, it does not offer Russian to German, English to German, German to English, Russian to English, and English to Russian as well as some non-trainable languages.

Document Understanding has been one of the best features for invoice processing. For example, companies require some keywords in invoices. While normal frameworks take much of time, we upload the invoices using Document Understanding, then determine the keywords required for cross referencing. The cross reference is very fast. It will capture the amount and put that in an Excel format. This is a very good feature.

A valuable feature of UiPath has been the REFramework. In banking, we need to log in to the website with a user ID and password. Once, we did that wrong and the workflow stopped. Using REFramework, there is exception handling. Stability depends on the correct configuration of error handling, so this is the best feature. 

It has some Citrix recording options.

The AI Center feature has been very good. It supports many machine learning languages and skills. It speeds execution and provides a good savings on time.

I like the certifications offered by UiPath Academy.

I would like UiPath to give free trial licenses for more features, like AI Center. UiPath currently offers two licenses for the trial version. However, if I need to practice in AI Center, then I need four to six licenses.

I have been using UiPath since 2018.

The stability is very good.

There are no limitations for Windows.

We have over 500 activities in UiPath right now.

I haven't used the technical support so much. My colleagues use it sometimes, depending on their problem. The speed of their response depends on the type of plan, normal or enterprise, that needs support. I would rate them as 10 out of 10.

There is also social media support through Twitter and LinkedIn.

The user community is very good. I am a member. If a developer has any doubts when working on a project, then a lot of people in the community are ready to give immediate answers.

Positive

We have faced challenges when installing market-related data. We need to dig deep when we are installing it with Orchestrator and/or VMware. All the documentation is available, but it needs to be prepared in advance. Whereas, we work in real-time.

I have been involved with many client installations for UiPath and Orchestrator. We do standalone installations for single node and multi-node systems, like Linux. Linux is not fully supported, as compared to Windows. UiPath deploys well on Windows.

My previous company had good ROI using UiPath compared to other tools.

UiPath Academy is free of cost.

The UiPath Community Edition is enough to implement any complex workflows.

The price for attended robots is good.

Some features are very costly, like Document Understanding. That is why in India many customers are not using the Document Understanding license. This is a premium feature and its licensing costs are high compared to other tools.

Compared to other tools, UiPath provides a good, rich environment.

I am using AutomationEdge, which is similar to UiPath, but a small tool. It provides the same features as UiPath, but it is not as popular a tool. The UiPath Academy videos are very good and better than those offered by AutomationEdge. While AutomationEdge also has a free learning course, you must watch their videos from start to finish. UiPath has no restrictions on its learning, which is good and the best option. For example, when you are an advanced learner, you want to go to advanced training courses. However, AutomationEdge makes you start from scratch, even as an advanced user of RPA.

Some processes are faster in AutomationEdge than in UiPath for insurance-related organizations.

I am also using Automation Anywhere, which is a popular tool in comparison to UiPath. However, feature-wise, UiPath is easier to use because Automation Anywhere requires complicated coding knowledge, though some of their features are very good. While UiPath requires some coding knowledge, it is not as high level as Automation Anywhere.

UiPath is the number one tool in my opinion. I would recommend choosing UiPath for someone looking to purchase an automation tool for the first time.

UiPath has very good accuracy. I would overall rate this solution as 10 out of 10.

I am an RPA developer and I am using UiPath to create both attended and unattended bots.

I develop bots that run doing overnight tasks and we can check the results in the morning.

UiPath allows us to scale without having to worry about the infrastructure. It is simple to scale any of the automations that you develop. 

UiPath makes it easy to build automations. It is very user-friendly and they provide all of the courses in the UiPath Academy. We can learn starting with the basics, and it is really simple. One person needs between two weeks and one month to learn it.

This solution provides us with the ability to do end-to-end automation, starting with the discovery phase and process mining. After that, we move to the building page where we have Studio X, and then we can deploy the automation on the cloud.

UiPath has helped us to scale RPA benefits by automating the backup of all of the projects running in the organization. This bot runs every night and reduces our workload for one employee by eight hours, or one day each week. 

UiPath handles all of the infrastructure updates and maintenance, which is really good.

The cloud offering has helped us to see time to value quicker. It has helped us in many ways, including with the automation of repeated tasks. One example is that I created a bot for myself that is responsible for filtering all of the spam emails from my inbox on a daily basis, and then removing them. The first step is the identification and the second step is removing them. This saves me time.

The automation cloud has helped us to reduce the total cost of ownership because we can manage everything through Orchestrator.

UiPath has definitely reduced the percentage of human errors that we have in our processes. In our system, all of the bots follow our best practices so there is a very small chance of error. The reduction in error rate depends on the process. For example, the OCR is not very accurate so the errors are higher but if the process involves an API or SQL queries then it is very good.

This product has helped to reduce the cost of our automation operations. There is more of an upfront cost but it is one-time, and then we start saving.

The best feature is the good community support that is provided in the UiPath forum.

I like that it is a cloud version and runs on Citrix. I used the cloud offering to deploy my bots and manage my Orchestrators.

It would be very helpful for us if they provided more business use cases and helped us to learn them.

We have been using UiPath for almost two years.

There are times when you need to shut down the automation and restart it. Other than that, it is very stable.

I am the only one developing the bots but I am currently training some other people who are just learning it.

To this point, we have not had to scale any of our projects. Our usage of it depends on the project and where we can use automation.

When other features and updates are released, we normally visit the forum to help understand them. I have never used technical support.

I have also tried using Automation Anywhere.

Each solution has different types of bots that are available. One of the differences is that with UiPath, you have Orchestrator to help you manage them.

Generally speaking, UiPath is easier to understand.

The initial setup is not complex. It is easy to deploy and the actual setup of UiPath is not very difficult. It is a matter of downloading the Studio and creating an account in the Orchestrator. Then, you can start working.

My IT team was responsible for the initial setup. Only one person was needed to complete it.

I take care of all of the maintenance.

I am using the Community Edition and am not familiar with the cost of the paid editions.

We do not yet use the AI functionality but I know that it is there.

I have watched some videos on the UiPath apps feature, which lets us create automations in a low-code/no-code fashion. We have not used it yet but this is something that we'll be exploring in the future.

The biggest lesson that I learned from using this solution is that they have a very good community forum, where you can share ideas and learn from other RPA developers.

My advice for anybody who is implementing this product is to start by taking the fundamental UiPath courses from the UiPath Academy. This will help to understand RPA and UiPath.

In summary, this is a good product and I'm quite satisfied with all of the functionality that it provides.

I would rate this solution a nine out of ten.