UiPath Reviews

I am an automation consultant and most of the robots that I work on are unattended.

Some of our use cases involve end-to-end automation. One of them is an SAP system where the transaction data, material numbers, and other things are used for T-codes. Based on the value of data in the T-code, it opens other T-codes in the process and updates those registries accordingly. This may include, for example, T-codes one and two. Then, from T-code one, I need to get input with regard to my material numbers. This might be a materials invoice or the invoice numbers of material orders. With those, you have to put it in one T-code and get output.

Based on the output of the T-code one, you need to do the rest of the operations in T-code two and T-code three. Once the job is completed, update all the information about the different T-codes in an Excel sheet and then update it back to the system.

UiPath saves time both from the perspective of a developer and an end-user. I can talk about the two positions because I have been involved in both roles. On the development side, the features make it very easy and tasks that normally take half an hour can be completed in a minute or two.

With respect to the end-user, assume that a process normally takes an hour a day to complete. Once the automation is in place, the whole process will be done in a minute or two. Importantly, the user does not have to monitor the process because it runs in the back end or on a server in a remote location. The entire process will run without monitoring.

At the same time, the user will be informed. Let's say that you have to get some data out of it; most of the time, the data available every few days. Personally, given that I am not normally in the role of the end-user, I have to log in to all of the systems and look for the data. However, if UiPath is configured and developed properly then it will inform you in an email that the data is now available. Similarly, if there is no data available then it can be configured in such a way that the user will be informed of that. This would give the user the opportunity to save and plan to utilize their time for other purposes.

In our company, we have a lot of use cases where we were able to implement unattended automation. This meant that we saved a lot of time and we were able to reutilize the employees for more useful engagements. 

An additional thing that we are able to achieve through using an RPA like UiPath is a reduction in errors. When we are performing any kind of activity, such as a recalculation in Excel, or calculations in a step-by-step process that involves manually copying data between two places, there is a high chance that an error will occur. This is a human error that can be avoided once we implement the automation and move it to production. Ultimately, all of these types of errors will be eliminated.

It is difficult to estimate the total number of errors that we avoid, but I can say that we were able to save time and with each process, the number of errors is reduced.

The most valuable feature is the set of data scraping tools. You can scrape data into your tables, then easily transform it or convert it between formats. If UiPath or another similar automation tool was not there, it would be very difficult to automate something that is a UI- based application. There is no other option to get that back-end data out of it. If we were not able to convert the formatting, or if for whatever reasons we cannot extract the data into a table format, it would be very difficult for us to convert and get the data that we want. The data would be difficult to format and we would spend a lot of time on it.

UiPath provides the data in a table format and in a structured manner, which means that we are able to get the required value from the table and do the necessary calculations on it. It saves us a lot of time in this process.

We have started using the AI functionality but so far, not to any great extent. For example, we were able to identify different types of images while reading an invoice. Prior to using the AI capabilities, we were not able to read them. This is our only use case for AI at the moment, but we plan to explore other activities and possibilities.

We have used the UiPath Academy courses and by doing so, we were able to learn a lot of things. They had examples of use cases that can occur in different scenarios and instead of getting that from a live environment, or during development, we were able to learn it from the Academy and a live example.

With the Studio, we can do basic troubleshooting in the production machine or VM, in case any error occurs. This is helpful because we don't have to move the data back to the development machine.

The integration with APA should be improved with respect to adding data from external sources and being able to bring in data from third-party applications. Also, it should be better the other way around, where UiPath is providing APA data to other applications.

I have been using UiPath for the past four years.

If the application is working fine, without making any updates or changes, then the bot will work as expected about 95% of the time. However, if there are any changes to the end-application made by the developers, or there is a content change, then we definitely have to align to those changes and it will take time.

Generally speaking, we move a process to production once it is stable.

We can easily scale this solution so the scalability is quite good.

We have between 15 and 20 developers in my team who work with UiPath. I am not sure about the number of people on the other teams. In terms of end-users, there are more than 100.

I have developed 30 processes personally, and my team has created more than 200. We plan to continue using UiPath in the future.

We have used technical support and the UiPath technical team is good. Whenever there is help required, and we are not able to find the solution for that from the UiPath documentation, we get a ticket with the support team. Based on the criticality of the process, they help us.

We did not use another RPA solution prior to UiPath.

The initial setup is straightforward and very easy. The main component is called Orchestrator and then there are two more components called Studio and Development Robot. These two are connected to Orchestrator, and once the development is complete, you can do the unit testing on the same machine. After this, you publish the package.

Once the item is published, it will be pushed to the Orchestrator and then connected to the bot. This is where you're going to run the process. Once it is complete the bot will start running. The whole process will take approximately 10 minutes and you can move the data to production.

When the process is running in production, Studio allows you to troubleshoot from there, without having to move it back to the development machine.

I deployed UiPath on my own. They have provided enough documentation.

The pricing and licensing costs seem okay to me, although it is a little bit on the high side.

In the past, you needed to install the Studio license if you wanted to be able to troubleshoot in production. However, that has changed and you no longer need to buy it separately.

My advice for others who are implementing or using UiPath is to ensure that they test the robots and processes thoroughly before moving them to production.

I would rate this solution an eight out of ten.

I started my RPA journey as a developer, and I first heard about UiPath as a low-code, drag-and-drop automation platform. Back then, it was very much in the beginning stages of its development. Ever since then, I've seen it evolve quite fast. I would say even faster than other RPA platforms that I've used, in just a few years.

Thinking back to when I first started using it, there are many new features and updates and it's my preferred platform for RPA.

We primarily used unattended automation, where you deploy the bots to work autonomously. This is unattended, end-to-end automation with no human in the loop, other than providing the inputs or checking the outputs.

We have several use cases, but our main one is reducing manual work. The processes that require a lot of manual input and have a lot of human error are the focus. That could be, for instance, processes that have to do with invoicing, billing, reporting, and coding, which require a lot of man-hours, are very reliant on a human being available, and are time-sensitive. Those are the ones that are on the top list to be automated.

Beyond that, I can't specifically talk about the processes that we've automated.

UiPath helps to implement end-to-end automation, although the discovery of processes, gathering requirements, and creating the design, all happen outside of UiPath. But the development, which is developing the bots, then testing and then deploying them, does happen end-to-end within UiPath.

The end-to-end development capability is important, but this is because every tool offers this and it is expected. That said, there is definitely room for improvement in that end-to-end should include process discovery. It is end-to-end, but those ends can extend further than what it currently is. In that sense, it's no different than other RPA tools.

Another way that UiPath improves the way our organization functions is that the robots can run 24/7. If you think about a human workforce, they work eight hours a day, they take days off, they get sick, they leave, and they take knowledge with them once they leave the company. But, the robots can be run non-stop 24/7, and each process can be scaled up. The same process can be run by one bot, or it can be run by 10 or 100 bots. This means that there's a lot more flexibility that the bots bring, especially for high-volume processes that perhaps even have some peaks, such as an end-of-month rush to produce invoices or meet a deadline or an end-of-financial-year crunch.

These robots have an easier time addressing and variability when it comes to volume. They really create a lot more scalability to where businesses can grow and know that they can meet the demands of the future. So, they're a lot more future-proof, whereas people are harder to rely on.

Speaking from a business perspective, it's the FTE savings. A company obviously needs to spend money on UiPath licenses and development costs, but those costs are oftentimes lower than the cost of that FTE, the full-time employee, whose work is getting automated. If you purely just think about the financial benefits, it's the lower staffing costs.

There is also the ability to free up people. This means that even if people aren't replaced and their salary isn't saved, what they can do is pivot their focus to, for instance, be a lot more customer-facing or do a lot more strategic or creative tasks that perhaps get pushed to the side because there's not a lot of time allocated towards performing them. Now, FTEs have a lot more capacity to contribute and perform tasks that still to this day cannot be automated, like creative thinking, complex decision-making on the spot, strategy, and just human interaction.

In the beginning, employees meet automation with a critical eye. They're thinking, "Well, what's going on? Why are these robots coming in? Are we going to work alongside them? How is this going to work?" But to be honest, in the end, there are winners and losers. What I mean by that is that some jobs are replaced, and that's just simply because of that FTE saving that is usually the driver to justify the cost of development. But on the flip-side, the employees that do stay and do work alongside the bots are usually a lot happier because they have to juggle a lot fewer things.

The robots are there to make people feel like people and not like robots, where they just do the same thing over and over and don't enjoy their job or don't enjoy what they do. A robot takes that away and helps people enjoy their work a lot more because they can do non-repetitive tasks. They can be a lot more customer-facing and perhaps build stronger relationships with their customers, know them better, and have more time available to work on other projects or work on other things that they may never have had the time to do.

In our organization, the robots work on multiple projects. The amount of employee time that is freed up depends on the project and what you are automating, but a pretty good estimate would be a 20% to 40% savings.

With respect to the reduction of problems related to human error, the fact of the matter is that some employees, whether you like it or not, are more error-prone. By automating a process, we were able to standardize it, and therefore, identify the cause of the human error and remove it by replacing the process with a robot that makes a more reliable judgment in terms of action. It is literally just an if-else statement. It's a lot easier to quantify and therefore it's a lot easier to evaluate, and therefore the result is a lot more reliable. Whereas with an employee, let's say the output of their work is a lot more unreliable simply because they could be working on 10 different things on the same day. There could be a deadline approaching, and the quality of work fluctuates with an employee because of it.

With a robot, you will notice that over time, in fact, the quality improves, and that's just the basic truth of RPA. It doesn't happen automatically, and it does require work. It happens because you see the results of the automation and you see areas for improvement, ultimately leading you to make adjustments. You iterate on the RPA solution and make it better over time.

Although it does not improve automatically, through a conscious effort you can be a lot more confident in the output and then be able to see unbiased results at the end of the day. Part of these results is your exception rates, which can be errors. It can be failures, whether technical in nature or decision-making business rule types of errors. Then, you can adjust your process to where it can positively improve that exception rate, and just iterate on that to where it becomes acceptable. Moreover, it's quite stable, which is not the case with the human workforce.

The automation cloud Orchestrator has its benefits and negative sides. The benefit is the fact that it's web-based. A person who has the login credentials can access it without the necessity to have something installed. The development and the monitoring of the bots are separated in UiPath, where the development happens in the Studio and the monitoring happens in the Orchestrator.

In other tools like Blue Prism, it happens in the same place. I've used both, and the Orchestrator is nice. It has a very nice UI, it's user-friendly, it has a lot of features, and I find it quite easy to use. For example, you can see all of the machines, you can see the robots, and you can schedule them. If the business wants to see a lot more across the output of the Work Queue, they can have that visibility from Orchestrator, which is great.

The downside of Orchestrator is the package deployment, which is perhaps another minus of UiPath in general. The deployment of a new package does not take a long time, but there are a lot of steps. It's not an intuitive process. If you have to release a lot of packages, which does occur, especially in the early stage of deployment, when you are releasing hotfixes, or when something goes wrong and you need to redeploy a fix really quickly to minimize business impact, it does slow you down.

I wish it would be just one or two clicks, rather than the whole importing or exporting and connecting to the desktop application and everything that accompanies it. I wish it were a lot easier. Again, it has its upsides but it's not perfect.

The best feature in UiPath is their robotic enterprise framework because that is an inbuilt processing framework for utilizing their work queues. It's plug-and-play, and already pre-built to where you don't have to start from scratch. It's enterprise-grade and ready to be used. All you need to do is populate your dispatcher, create a queue, create a performer, and you're good to go.

The highest benefit of it is that it's just there, ready to use, and you don't need to start from a blank screen. You don't have to figure out, for example, how to create an environment where the robots can check if there's anything in the queue to be worked on. The framework is already there. The other tools that I've used, like Blue Prism, don't have that built-in quite as well.

My perspective and overview are from that of a developer, and I find that the recorder feature is really good. This is because UiPath lets you record your actions on the screen. So, if you want to interact with a web-based interface, for example, then you have UiPath record your actions and then build the activities that you would need in order to replicate those actions through the robot. It makes it a lot better and although it's not perfect and it does need to be reviewed and adjusted, it speeds up development quite a bit. This is especially true when it's basic back development like populating fields and clicking buttons and navigating on a web.

Compared to other RPA tools that I have used, something that stands out to me in UiPath is that it has a very extensive library of activities. Those activities are easy to search for and use.

When you are writing code, there is a feature called IntelliSense, which autocompletes your code. More specifically, when you're typing code, if you're starting to type the name of a variable, it will show you all of the variables available and you can just click them. It's very interactive and it's reminiscent of the Microsoft Visual Studio environment, both from the UI perspective and the coding perspective. This means that developers that are familiar with Visual Studio will probably feel right at home using UiPath. It's very developer-friendly and it's geared towards appealing to existing developers.

The UiPath Academy courses definitely help in the process of bringing employees up to speed. The Academy is the go-to place for UiPath learning and I think that other RPA tools are copying this model of disseminating knowledge, being a lot more open with training, making it freely available, and providing an online classroom. These are things that UiPath has always done, and it certainly helps new developers get upskilled in RPA, and specifically with UiPath.

When it comes to ease of use, UiPath is intuitive insofar as the basic features have a low learning curve. However, if you want to take full advantage of what UiPath can do, and if organizations want to create more sophisticated automation solutions, it is more difficult. For instance, automations involving back-end access, maybe writing directly to databases such as SQL or using API, that's a steep learning curve. In fact, I think the learning curve is exponential.

If you just want to make a robot that sends an email, that's really easy to do. But, if you really want tangible benefits, like if you really want something that solves a business problem, it is a huge learning curve and it takes a while to master. Obviously, it does have that low-code requirement, but I would say that's only for entry automation projects, like proof-of-concept or something along those lines. For something that really solves a business problem, you would need code, because that just makes it a lot more robust and a lot more powerful if you can custom-code certain steps of the process.

Features for process discovery would improve the end-to-end development capabilities.

From a developer's point of view, my biggest struggle with UiPath is debugging. The debug mode in UiPath feels clunky and it is a sore spot. It feels it's hard to control the flow of the process. There are a lot of internal errors and it's not intuitive. In general, debugging is not a good experience and I don't enjoy doing it. In contrast, Blue Prism has better debugging capabilities.

Blue Prism is a little more dynamic; you can adjust variables, you can jump around the flow, and it's easier to control. With UiPath, it's a little bit of a nightmare. It becomes harder to debug the bigger your automation is, because it's quite unpredictable, and it's quite unstable. Definitely, if debugging was improved, I would say UiPath would get 11 out of 10.

Something that I noticed recently is that they have moved to paid certification for developers, whereas it used to have free certification. This is a little bit outside of the platform itself but the pain point here from my perspective is that there is a barrier to entry for new RPA developers, or ones that want to renew their certification. It has become a lot harder and that used to be a differentiator for UiPath. It had a very strong online learning offering and it offered no-charge recertification on top. This is now very similar to what other tools are doing and I see that as a negative.

My first introduction to UiPath was in early 2018 or late 2017.

The robots could be a lot more stable, which is another area for improvement. The stability issue with UiPath is a prominent one, especially in comparison to other tools like Blue Prism. I feel that there are a lot of errors that are caused by the UiPath framework, as opposed to the robot design. Sometimes it's just very unreliable and crashes unexpectedly, which creates serious issues in terms of reliability. In early deployment, it always happens that it's very late nights, and there's a lot of babysitting processes. The robots need it because you never know what's going to crash.

In comparison with other RPA tools, it is average when it comes to reliability. I would rate other tools a little bit easier to manage expectations as to what you can reasonably expect to go wrong, and what you can reasonably expect to break. With UiPath, our developers, even our experienced ones, oftentimes get errors that we've never seen in our lifetime. This is partly due to the flexibility of UiPath, with it being so easy to adapt to all types of applications and all types of environments and it being so malleable. It is one of the most versatile tools; it's industry agnostic, platform-agnostic, and tool-agnostic, but that flexibility creates a lot more room for error in the code. It means that a lot more things can break or interfere with each other, compared to other platforms that are perhaps more niche and more targeted in what they're actually trying to solve.

UiPath is definitely scalable. It is modular, where you build a workflow and that can be reused across multiple robots or multiple processes. Those processes can then be run by one, two, three, five, and 100 bots, provided that they can work concurrently in the same environment, performing the same process. It's wonderful and the scalability is uncapped. If you have licenses, then you can use them, which is great.

The only limits are how many licenses are you willing to buy, and the inherent limits of your own infrastructure and your own process. It comes down to how many robots can realistically work concurrently in the same infrastructure and in the same network without breaking it.

We have approximately 20 developers who use UiPath. We have business users, but it is difficult for me to say how many there are.

I have been in contact with technical support, and I have experienced submitting a support ticket to them. I even got on a call with them and they were very helpful. We had been having issues with automating a platform and we wanted to get their specific insight as to what was going wrong. It had to do with UiPath not being able to extract selectors from that specific interface.

I was really surprised because they spent the time to not only address my ticket and answer my questions, but also to allocate time to schedule a meeting, and really look into the platform via screen share. I was sharing the screen with them and showing them what was happening, and they really looked into it and gave it a lot of attention.

I understand they get a lot of tickets, and I really felt they provided a good answer. They responded really fast, I would say within 24 hours, and we began exchanging details through a back and forth conversation.

They provided me with the outcome that I was happy with. It was a very good experience.

In addition to UiPath, we used Blue Prism and Automation Anywhere. UiPath is king here, and I rarely hear anything about the other two. I would estimate that we use UiPath 95% of the time, perhaps even 99%.

The alternative to UiPath that I am more familiar with is Blue Prism. From my perspective, UiPath is geared towards developers. The audience towards which it's skewed is the developer or the technical person. Blue Prism is geared more towards business people. It's geared towards converting business people, including SMEs and subject matter experts that know the process well, into developers. You will find that the language that each program uses is one that's geared towards the target market. Consequently, UiPath uses a lot of developer language and developer concepts.

For example, UiPath works similarly to the Visual Studio Environment. Blue Prism, on the other hand, uses a lot of flowcharting visuals, as well as the language that it uses for the same concept. It's going to use a definition that's more from a business process flowcharting realm. Recently, both platforms are converging onto each other and I feel like they're becoming more and more similar, but they still have a few things that are different.

One thing that stands out for me is that Blue Prism has wonderful debugging. It's a lot better than UiPath, and it's an all-in-one tool where the monitoring and the building of the robots happen in one application. The deployment is also really easy.

Blue Prism also offers online learning, which is great. They didn't use to have that offering, and I think that they got a lot of inspiration from UiPath. Their online courses have been great because previously when I was learning RPA, I had to use YouTube. Now, they have a whole Blue Prism university, which is amazing.

Blue Prism has inbuilt version control and a lot of other great features. They have a heavy emphasis on security and encryption, which UiPath perhaps needs to improve on. Companies such as banks, insurance agencies, and finance agencies are a lot more interested in Blue Prism because of its very strong security protocols. The encryption offering is a key requirement for companies that work with a lot of sensitive personal data.

I have never been involved in the initial setup, although my understanding is that it's quite a journey.

The areas of the organization with the most ROI from UiPath are operations, finance, HR, and sales. Those are the key departments, although it's across every organization because those departments have a lot of manual work-intensive processes that are the first contenders for automation.

We have a yearly licensing model that gives us access to the development and production environments. The cost of licensing is expensive.

Part of automation is the analysis and optimization of processes because the analysis phase is a by-product of wanting to automate a task. If you want to automate something, you have to break it down into parts and really look at it and think, "How can I reduce this into a series of business rules, a series of decisions, or series of steps?" It's an exercise of process optimization in and of itself because a good practice in automation is to not just take what it is and automate it, but to think, "Does what is currently in place actually work? How can it be improved? How can it be streamlined? How can it be done in fewer steps?" It's a good chance to practice some process review, improvement, and transformation.

The idea is to make it optimal because the current process usually has unquestioned practices that maybe haven't been reviewed for a very long time. A lot of businesses say, "We've always done it this way," and they've never thought to revisit the approach. RPA gives you an opportunity to think about whether what you've always been doing will work when it's being done by a robot. Most often, the processes get streamlined through the requirements gathering phase, understanding the as-is, and then a key part of that is doing the process design, which is the to-be vision.

During that time, processes go through a few design iterations where they are optimized and streamlined because we want the robots to be as efficient as possible. This means performing as few steps as possible without sacrificing value and efficiency. It is important because any inefficiencies in a robot are going to scale with the number of times you're going to run that process. If you run a process a thousand times, and let's say there exists inefficiency that results in an extra minute being used, that could be shed if you were to review and optimize that process.

Ultimately, optimization is an important exercise because the benefits include a further capacity to run more automated processes, and less time is taken up by inefficient steps.

Something to be aware of is that updates to the platform have to be managed because any update could impact the performance of a bot that was built with an earlier version. To avoid having a newer version impact the performance of something that was built previously, all of the updates need to go through a due diligence process.

The biggest lesson that I have learned from UiPath is surprising; not everything needs to be automated. It feels weird to say it because thinking, "Well, I have this platform, I have these bots, why not just automate absolutely everything?", but the truth is that there are things that can be streamlined outside of RPAs. Also, some processes can be automated through other means. Consider the very simple example of sending automated emails, or sorting out your inbox by putting the right email in the right folder, those types of things can be done with email rules rather than RPA.

If a platform already has some sort of inbuilt automation, whether that's a social media platform, email platform, networking platform, or any other type of platform, it's always better to explore that first before looking to solve that problem with RPA. There are times when an Excel Macro or an email rule will be a lot faster and a lot more cost-efficient. RPA should be directed towards big-ticket items, big problems, and large volumes to where no existing solution would provide the same level of value.

My advice for anybody who is considering UiPath is to try it out for themselves. The most beautiful thing is when companies take the leap to have a very small citizen developer team, where they upskill a few technically-minded people with free courses and try to build a small proof of concept to see if RPA is the right path for them. I really encourage that sort of curiosity and experimentation because all of the resources are out there and anybody can learn, as long as they're driven and passionate and curious about automation. I would really encourage people just to give it a try and see what comes out of it.

In our organization, UiPath is the number one RPA tool. Being close to the industry as a developer, and I do feel like it's the preferred tool, at least where I'm based in Australia. It is definitely the preferred RPA solution on the market. Our usage is definitely going to increase in the future. I feel like the future is bright for UiPath. That said, it isn't perfect.

I would rate this solution a nine out of ten.

We use UiPath for cases where we have to do a workflow-related mechanism. Most of these use cases are small, Excel-based solutions and desktop-solution-related workflows, where one or two applications have to be connected, along with the Excel operation, for the end-to-end workflow creation.

We use both attended and unattended automation.

We have created 10-plus solutions using UiPath, and the savings that have been generated from these solutions are around $1 million. They are very cost-effective solutions: finance, order-to-cash, and protocol-to-pay processes. It has created value on the higher end, because the processes were quite cumbersome. We re-engineered the processes and started using UiPath for workflow automation.

We have saved roughly 50 FTEs on a yearly basis. It also enables us to use a lower skillset workforce, which is a cost-effective measure.

Quality, no doubt, is one of the key parameters of automation. UiPath has resulted in quality improvement for the overall processes where it's deployed.

It's on the OCR side and the workflow side where UiPath creates value to us.

The most important and valuable feature of UiPath is the ease of creating automations. It's a workflow-based model. End-to-end coverage is, no doubt, very important, because when you use a fragmented solution, the overall process flow becomes shaky. UiPath has the required capabilities to create an end-to-end solution for a business case. For our scenario, the business cases are quite small. That way, the turnaround time to create a solution is short and it becomes very easy to deploy, which is quite helpful for us.

Another important feature is the OCR capability, which integrates quite easily with other kinds of tools. We have integrated with ABBYY and we have even used the Amazon OCR engine. From an integration perspective, it is scalable enough to integrate with third-party solutions, whereas that kind of thing becomes a bit of challenge when we use Automation Anywhere.

We are able to use Python scripting and Python libraries for data extraction.

We also use the solution in creating attended automations. They are very much division-specific and are currently used by the procurement and the finance teams. These are on-demand, data reconciliation activities that are performed once a week. The bot is clicked by the person who is attending, which is generally a procurement or a finance guy. These are tedious activities so that's why we have the dedicated license for the attended format.

It is quite user-friendly with the drag-and-drop functionality. It has connectors which are quite suitable and industry-standard for basic applications that we use on the desktop, like for the Microsoft suite. From an integration perspective, it has done well.

We have also used its selector technology to automate processes with dynamic interfaces for one of the finance applications, where the UI screen is changing.

The cognitive area is one where there is room for improvement. Automation Anywhere has grown in that area, whereas UiPath still is more dependent on third-party integration. That is something which they should be focusing on more. They should acquire a product and get it integrated.

I have been using UiPath for around two and a half years. I have used both Automation Anywhere and UiPath. We have both tools.

UiPath Robots are quite robust, and from a maintenance perspective it has become easy, if you create logs. It's pretty good.

In terms of scalability, as I mentioned, it has certain challenges, but with the minimal capacity which we are running, it becomes easy to maintain the bots.

We have 10 to 12 automations already in place, and there are around five to six more in the pipeline, which are still being rolled out. The RPA tool we used is determined on a case-by-case basis.

UiPath technical support is pretty good. Most of the answers are provided by the community forum. If you raise a ticket, they are proactive in getting back to you and addressing the point. It's good.

The initial setup was okay. I was involved in the setup of Automation Anywhere four years ago, and with UiPath. Compared to Automation Anywhere, it was much smoother because the community side is quite good with UiPath. In the early days when we were facing issues, we had the UiPath community support to find answers. We did not have to raise a ticket with UiPath because we were able to get our answers in the community forums.

The first case took us around seven to eight months to put in place. The first one is, obviously, always a tricky one. We also picked a use case of medium complexity and it took a bit of time. Later on, we started building more of a workflow solution using our low-cost workforce and, after that, the journey was quite smooth. Initially there were some hiccups, but once the team understood the tool itself it became easy.

We deploy developers who require a lower level of skill sets, developers who do not have that much training. They are normal .NET developers whom we train for one and a half months on UiPath and they start developing UiPath solutions. We have a center of excellence with our developers who work on UiPath. We recently hired two more, so we now have around 11 developers who are working on UiPath.

Taking UiPath courses to get up to speed has been very helpful. I am certified for the tool because of the courses. The curriculum is at least on par with that of Automation Anywhere, although I would say it is much better. The only issue is that the courses are very limited. The AA University has increased to a vast number of courses, and most of them have become free for the end-user. The UiPath course material is good, but there are notably fewer courses and less certification available for people like us, who are more on the business side. AA has a business analyst program and a program manager certification, but I was not able to find anything specific like that in the UiPath Academy.

Our strategy with UiPath is that we generally go for unattended automation because that doesn't lock up our licenses for the bots. We prefer solutions which require unattended automation, because of a lack of budget and other constraints. From the deployment perspective, we have a dedicated server and we're following the minimum guidelines which are required to conform to the deployment standards.

The ROI generated is quite high because of the cost factor.

It is much much cheaper than the Automation Anywhere. That is a key differentiator. It is targeted at mid-level enterprises. It is cost-effective.

There are no additional costs beyond the standard licensing fees. We have taken few of the training-related services from them. Once we move to the cloud version we may require some consulting services to move from on-prem to cloud. That would be the only other cost associated with UiPath.

When it comes to the main differences between UiPath and Automation Anywhere, UiPath is cost-effective. It is quite a lot cheaper than Automation Anywhere. It is also drag-and-drop, a fact which makes basic automation very easy compared to Automation Anywhere. It's quite user-friendly. In addition, the OCR functionality is quite robust in UiPath because it also provides a third-party integration. Python scripting becomes easy and that means our OCR solutions are quite good. These are the pros of UiPath. 

Regarding the cons of UiPath when compared to AA, the first one is the level of scripting details. Custom scripting is quite lacking in UiPath. It's more a drag-and-drop functionality which doesn't allow that higher level of customized scripting when compared to AA. Secondly, the scalability is quite robust in AA as compared to UiPath. Even though we are not pushing the limit, the general opinion out there is that UiPath fails quite visibly when you try to scale solutions that involve operations plus a new product rollout. That's a challenge with UiPath. And, as I mentioned, AA has improved a lot in the cognitive area and UiPath has not reached that level. It relies more on the third parties.

Even if you are a large enterprise and you're trying to start your RPA journey, UiPath is the answer. It sits in the top one or two solutions, along with Automation Anywhere. It's one of the leaders in RPA, and with the low cost model of the license structure, it is very easy to start with UiPath rather than with Automation Anywhere.

If you are looking for a strategic approach, where you have projected that within five to six years you will roll out 250 to 300 bots, scalability is something you have to factor in when starting your journey.

We haven't used the solution's artificial intelligence. We tried to run a PoC using a chat bot, but it didn't do well. I don't think UiPath has its own AI engine. They provide an API-level integration with other AI tools. We had a challenge there because most of the AI functionalities had to work on the cloud. We had to integrate with the Google Cloud and Amazon cloud, but both are in the public domain and transferring data from our office to the cloud was a challenge. We hit a wall. For that scenario, we moved on to Automation Anywhere, which provides us an on-prem solution.

Most of the automations that we work with are internal to our systems. We are also trying to use it with BPM.

We are reducing people's activities in our organization. For example, there are monthly reports that we have to upload and read, and it was taking a day to do this activity. Then, using UiPath, we can reduce that time to two hours. 

It has helped a lot to minimize our on-prem footprint. This is really important because it minimizes tasks that people work on, including myself.

If you automate with UiPath, you don't have to worry about firing someone who is doing the same process. Instead, you are giving that person more time for analysis for the information that UiPath brings in.

The OCR is something that is really cool. You can work with a lot of systems and use the HTML feature to interact with websites. I really like that it interacts with websites. 

UiPath Portal works great for accessing features.

UiPath provides single sign-on, which is very important, because we don't have to manage a lot of passwords.

It is fast. With UiPath Studio, you can get the passwords and work in it quickly. 

The UiPath Academy is great for learning the solution. It helped us a lot.

We would like to know how to implement the artificial intelligence (AI) feature because we are working on some activities in this area.

The bank knows about UiPath, but not all people consider UiPath something they really trust, which is why there are just two of us working on it full-time. We do teach people about UiPath, but they are not 100 percent involved with it.

The stability is usually really great. However, at this point, we are uploading a new version because the stability is not right. They told us that our version, 18.4.5, is not 100 percent compatible with Orchestrator. Therefore, we don't have the stability that we had before.

The scalability works great for us. It is really fast when we ask for something.

It is really fast at scaling automations. At the beginning, it was slow because we couldn't work the way that we wanted. Now, it scales automation quickly.

We haven't had contact with technical support because UiPath has been working great for us.

This is our first RPA solution.

Before Orchestrator, we worked on an application to manage UiPath because we didn't have Orchestrator two years ago. So, we create our own application to manage UiPath.

It was very easy to set up UiPath the first time. We implemented UiPath with virtual machines, and that didn't affect our costs in a significant way.

The timeframe for setting up a new bot for implementation depends on whether it will be big or small. It might take a day, if it is really easy, or a week.

Getting the idea to have a new bot for the first time is kind of complicated. Once you can explain how it will work or be a solution, then you can just go for it.

I have to be involved in the beginning when implementing a new bot. 

Two people from our bank were involved in the deployment. One person develops the solution and another does the QA.

We worked with a third-party (BDG) to set up UiPath. They were really good.

It has helped a little to reduce our work. Before, we had people working at 6:00 AM because they had to inspect, analyze, or look into the systems for prevention. For example, they had to prevent the systems from going down. Now, with UiPath, that person doesn't have to come early because we get everything in reports from UiPath. So, that person doesn't have to come early anymore. That person now just has to look at the report and see, for example, that UiPath did a fix in the morning. 

The solution really works for its price.

The license cost is the only cost to start a new bot. However, if we want UiPath to do an activity and go through another machine, like Remote Desktop, or application, like Bloomberg, then we have a special license that is an extra cost.

We also evaluated Automation Anywhere, but decided on UiPath, which is friendlier. We also considered that UiPath has its Academy and more documentation.

We are glad UiPath has security because not all the RPA solutions have security.

We are getting into AI now, because we haven't worked with that yet.

Right now, we are 100 percent familiar with Orchestrator.

We didn't have to install a lot of features with this infrastructure. We just download some activities to work with everything, and it works fine. We don't have a lot of infrastructure for using data.

Our first step is getting Orchestrator because we really want to have the entire bank involved in UiPath. The solution is great. It can reduce costs, especially with all that stuff that people do. We have big plans for UiPath going forward.

I would rate this solution as 10 (out of 10).

We are using UiPath primarily for unattended automation. We are automating processes for business functions like finance and go-to-market.

We have Orchestrator which is hosted on the cloud and we also have UiPath deployed on-premises. We have three different instances of Orchestrator: one for development, one for staging, and one for production.

There are multiple business processes involving finance users. For example, for intercompany settlements, the end-to-end process was handled manually before. But now, the entire intercompany settlement, which involves many transactions, takes place automatically. Users don't need to intervene. They just need to verify whether all the calculations made by the robot are correct.

Another win for us was in the go-to-market function, where our customers talk to a customer advocate for purchasing different products and offerings. If they want to renew a quote or generate a new quote, they used to contact the CAs and talk to them on the phone, which would take a lot of time. It would take more than a day to process their requests and place their orders. Now, with the help of UiPath, we have developed a fixed form which we hand out for the customer to fill in. The average response time, as a result, has decreased a lot. We are now able to close a deal and generate revenue very quickly, compared to before. The process is around 90 percent faster for us.

We have just started using the AI functionality for unstructured invoices which we receive from different regions. Until now, when we wanted to extract information out of them, there was not any particular rule or way to get that information. A human had to be involved. That is where the AI functionality has come into picture. It makes our robots smarter and gives us the ability to train a robot to extract the relevant information out of different types of invoices.

Of course we have also been able to produce increased accuracy for a lot of our processes. With processes where we are receiving data in bulk, it's very natural for a person to miss out on certain things, but a bot does not miss out on any of the information and create errors in that way, so we have been able to reduce human errors to a great extent.

One of the most valuable features is its ability to allow us to integrate any external scripts—code or any other scripting file.

Also, they have recently come up with new features, like Document Understanding and AI fabric, which we have also started to use. These are helping us a lot with unstructured data extraction from invoices. The AI Fabric has out-of-the-box models, so we are using the invoices model from Document Understanding package. There is also the capability to train the model and that is a great way for us to get information out of the different invoices, as we deal with different invoices from different regions, rather than a single format. This is a great feature which is built-in.

It is also important that all the new services that UiPath is adding to the Portal are managed from the same place. Ease of onboarding for the customer should be a main priority. If the new services can be managed from a single place, it would be very easy for us to onboard them, to understand how to use them, and to enable them in our current workspace.

In addition, things like UiPath's navigation, drag-and-drop options, pre-packaged templates, and low-code features help developers, and people who have some understanding of tech, to build solutions quickly. With these features, we don't have to go down the same path all over again. This helps developers.

Each one of us has used the UiPath Academy courses and that has played a major role in getting people up to speed. I, myself, learned about UiPath by doing the Academy courses and then doing UiPath certification. If anyone wants to start with RPA, and UiPath in particular, it should definitely be their first point to get started with it. The Academy courses are really good.

There are challenges raised by the fact that UiPath is coming up with different versions almost every quarter, and at times almost every month. We plan to upgrade almost every quarter. Recently we were trying to add AI Fabric into our production Orchestrator, but we faced a lot of challenges. We had to involve the UiPath support team in the upgrading process. We were quick movers to upgrade to AI Fabric, as not many companies have done that. There were some bugs that we discovered during our upgrade journey, and that's how UiPath came to know about those bugs. It was little tricky, but UiPath's team is always present and helps along the journey. They have been coming up with a lot of new services and products and there are a lot of announcements on their Portal as well. But it's difficult for customers to keep up with their announcements.

Another area for improvement is version control functionality, particularly for Git. So far, for a lot of files, especially Excel, we are not able to compare the differences between two versions of a project. File conflict resolution could be improved.

I have been using UiPath for two years and three months.

The robots are pretty stable. It just depends on the way they are coded and how robust the developer has made the solution. If they have taken care of all the edge cases and of the possible areas of failure, the robots are predictable.

The solution is scalable. There is functionality to add as many robots as you want by purchasing additional licenses. There is a feature where we can use one machine and add different user profiles which is great. We are able to run the robots by using just one piece of hardware with different user profiles.

But if you are willing to scale up and you want to enable a lot of your team members to use the automation functionality, you can easily do that by purchasing more licenses and you will be able to schedule your processes in a better way.

We have about 15 people who use UiPath in our company. They are mostly developers, solution architects, or business analysts. We have 20-plus end-to-end automations and we use the tool on almost a daily basis.

Not all teams within our company know about UiPath. As of now, we have onboarded the finance and go-to-market departments. We plan to onboard the other teams, to run sessions with them and let them know that something like this exists and that it can help them in their day-to-day work. We are definitely planning to increase our number of automations.

The UiPath support team is there to help us to onboard stuff faster. It helps us achieve our business objectives quicker. We are able to solve stakeholders' problems very quickly. Because we have already planned to go live with certain bots, if our platform is ready earlier, we are able to provide the business value as soon as possible. That has really helped.

I would rate their technical support at nine out of 10. They are pretty helpful. Even if they're not able to come up with a solution right away, they ask for the specific files and all the logs and, usually, things are resolved within a couple of days.

I don't really know about the specifics of pricing, but identifying the type of automation you need will determine whether you can go with attended or unattended licenses. Think about whether you want your robots to run unattended and 24/7 or not, or whether you want a person to validate something in a given process, or if you want to constantly monitor the bot. Those are the types of things that will help determine the types of licenses you need.

With unattended, they now have something called Action Center where you can do a hybrid automation. That type of automation will be unattended, but there will be a human in the loop.

It really depends on what you are looking for and what kind of budget you have. If you already have the Microsoft Office suite, you get Microsoft Power Automate which is also an automation platform. You need to decide how extensively you want to go into the automation journey and whether you are really planning to expand it. If you are planning on going big with Automation, UiPath is the way to go. But if you just want to experiment and try out automation, and you already have Microsoft Office suite, you should try the Power Automate platform.

We develop and deploy use cases in the area of the cloud. We have deployed over 100 use cases. Most of our use cases are related to SAP applications, web applications, and mainframe applications.

One use case example is related to mainframe applications. The bot monitors mainframe applications 24/7. If there are any new jobs, they are identified, then the bot changes the status of the job to differentiate it. 

Previously, we are using the 2016 version of Orchestrator, then we upgraded to the 2018 version of Orchestrator. Some clients are deploying the 2020 version. It depends on the client. We suggest using a version back to clients, i.e., the 2019 version. 

We automate retail, sales, and agricultural services.

There are a bunch of candidates being monitored 24x7. Automation Cloud monitors these jobs, and whenever new docs come into the application, it will then change the status manually based upon certain conditions. Once we deploy the automation into the production, our manpower has been reduced so there are only one or two people needed for the backup. The rest will be taken care of by the automation itself. So, there has been a drastic reduction in our workforce.

We schedule different jobs using Orchestrator only. We have a separate team who takes care of jobs that we apply in Orchestrator. So, if there are any failures, it will automatically send email alerts to us. 

Within Orchestrator, there is a tab where we can restrict roles from the admin level to the user level. Developers give only access to the jobs. Whereas, admins have a roles option to restrict access.

There are still some areas that need improvements. Currently, the tool is not 100 percent accurate with hand written notes and image based automation. It is also tedious using it with Word applications. 

We are doing automation to take care of all our processes, but we still need support people 24/7 to monitor these jobs. So, human intervention is still there. We have two people monitoring these automations 24/7 because there are still some challenges with the automation.

I have been working with it for two and a half years.

When new bots are developed, we definitely see some errors in the first few days, which are usually connector issues. Once the bot is moved to production and has a lot of enhancements and patches to the automations, we make sure that the automation is running smoothly. So, during the initial stages, it won't be very stable, but after a few enhancements to adjust to the automation as time goes, then it will become stable.

Once we deploy and release the automation into production, we will monitor production to see if there are any new challenges, different scenarios, or bugs that we need to fix. We have monitored the automation after deployment for around six to seven months, and the automation went smoothly without any issues. Because the automation is performing pretty well, we have deployed it to more of our workforce and their different jobs.

We have separate, dedicated test data in three different environments. Orchestrator has a database and email server, so everything is in Orchestrator. Apart from the servers, products, and services, everything has a separate operations team, which has eight to 10 members, who take care of everything.

Previously, they used on-premises services for the bots. Then, they asked us to migrate more than 20 bots from on-premises to our AWS environment. So, we have created a dedicated AWS environment for them.

The deployment process goes this way: 

1. Developers develop the use case in a development environment. 
2. Once that is done, then they will move the code to the non-cloud environment.
3. They will test the code if the automation is running fine or not. If automation is running fine, they will show the data which is running fine as a code to the client. 
4. Once they have the desired output, then we will move to the production environment. 
5. The operations team will then deploy that process. 

The first time, it is a bit tricky. Going to production, it will take around 20 to 30 minutes to deploy the first time. If there is already existing automation, we only need a patch to implement it in production, then it will take roughly five to 10 minutes to apply.

The process of testing and deploying code takes roughly one to four nights maximum.

For deploying UiPath, we need at least three to four RPA developers. In general, one person can deploy at any time. The other two to three people are just there on support calls. 

Post-production, we have an operations team of eight to 10 members who take care of the automation.

There are some automations that save us thousands of hours monthly. These are automations that we run 24/7 as well as some automations that we run every five minutes for installing backups. Depending upon the amount of time the automation is standing, we will manage the capabilities of the server. 

To some extent, it has reduced the operations:

1. The automation is sending an email whenever there will be an error. Automatically, it is not going to the user. The user just needs to verify their emails. 
2. Whenever an error is noticed in the code, the automation will fit the address and email the operations team members. 

In these ways, it has helped to reduce operation costs, but not completely.

There are three types of licenses: unattended, attended, and developer.

We also use Automation Anywhere (version 10) and Blue Prism automation tools, but I think most clients prefer UiPath. There are more activities available in UiPath versus the Automation Anywhere version that we use. For example, UiPath has database-related activities, but Automation Anywhere, version 10, does not have this feature. I have tried using mainframe appliances in UiPath and Automation Anywhere, and I found that UiPath is more flexible and has more options available.

The solution is single sign-on, so the authentication is done for us, because it is difficult to remember all our passwords.

We have a ServiceNow ticketing tool for reporting issues related to UiPath.

UiPath is very good for developing web-based applications, especially for SAP and the web. For these two applications, you can go with UiPath without any doubts.

I would rate this solution as an eight (out of 10).

I have multiple use cases as part of this solution, since I work in different domains with different technologies and applications. We use attended and unattended bots.

One use case was for a credit-based client where we worked on the UI automation of the application. We were using UiPath Automation Cloud because our team is spread across different geographical locations, like the U.S, APAC and EMEA regions. We had different RPA developers who are developing the script simultaneously and putting it on the system, and our business case was that we wanted to automate the UI applications. Since there were different developers in different geographical regions, they created the bots on their system. Due to the cloud offering, we were able to move the bots to production using a click of a button. There is also an Orchestrator offering as part of the cloud, which is hosted. Once we had a thorough peer review of the bots being developed, we pushed it to our production-ready cloud-based Orchestrator. From there, we use it to run the script. That is an unattended bot, which is also one of the features. Since it is a credit-based UI automation, there are some instances where manual intervention is required in order to see whatever data is sent out to the client, if it is in the correct order or not. That is why we use the unattended offering of UiPath. Both these technologies help us a lot in creating our production-ready implementation. 

For another use case, we did an implementation in the SAP application. It was a procure-to-payment (P2P) cycle, where a third party sends out the invoices which get fed into the SAP application, then it gets verified and goes out to the payroll team. Once that is verified by the payroll team, the payment is released to the concerned vendors. All these points of entry were being done manually: the third-party invoices entered into the SAP application, SAP verification, and the payroll team verification. Since it involved a lot of financial data, people were very hesitant to get it automated. However, since we had this UiPath offering, that initial hesitation was turned into a very good implementation of whatever we wanted to achieve as part of this UiPath automation. We were using the unattended bot as part of the cloud offering. We ran the processes at night from Orchestrator, so people working from home didn't need to stay up late in order to run the processes. Since we were using the cloud unattended bot service of UiPath, we were able to trigger the whole process in a single click of a button, which is amazing.

As part of the UiPath offering, we have three offerings: Studio, StudioX, and Studio Pro. These three offerings are provided via cloud on a single system and installed on our laptops or desktops.

I am working as a senior analyst. As part of this particular role, I have to cater to the client's needs if they want to get a UiPath implementation. Then, I do the consulting as part of the implementation. I also get involved in the PoC development and how we should use the cloud offering, e.g., what benefits are there.

We were able to move prototypes, which were in PoC stages to production very quickly, which helped us a lot. There has been more collaboration happening because of the cloud implementation. Because we have different geographical locations where in RPA bots are getting developed, at the end of the day, everything is pushed into Orchestrator Cloud. From there, we can execute it. In terms of collaboration, this has been very helpful. 

UiPath Automation Cloud has helped us to minimize our on-prem footprint. We were able to get our prototypes into production very quickly. In turn, this helped us to get stuff minimized quickly because we were able to move the prototype as part of the PoC into production faster. We were also able to scale. For example, if we had new people joining the team, we could easily move them into the cloud offering and add a new tenant. We have added two or three new members who could readily go ahead and use the solution to develop RPA bots.

It is a single point of truth. There is no discrepancy or ambiguity. We can go to the leadership team, and say, "This is what it saves us on costs, man-hours, and effort that we used to do manually versus what we are doing now using the bots."

The most valuable feature (as part of the cloud offering) is Orchestrator. Even if we have the RPA developers spread across different geographical locations, we are able to get the bot ready and pushed into Orchestrator, where any non-technical guy can come in and run the process. When I say non-technical guy, I mean any person from the business or leadership who just wants to see how it works. They can go ahead and log into Orchestrator and execute the process.

The Orchestrator portal is very intuitive, so you don't have to run around and talk to anyone. It is so intuitive because it is like using a web-based application. For example, nobody has to train us to go and do whatever they want us to do. It is so intuitive that we can figure out, "Hey, this is what I need to click in order to add new tenants. This is what I need to click in order to change the geography from India to APAC or any other location. In terms of execution, whatever bots are in execution right now will be shown there. Also, whatever bots are not running, they will be displayed as part of the dashboard as well as the failures.

UiPath provides granular, role-based access control and management, which is very important as part of the monitoring. When we want to drill down on why there is a failure, we need to do a root cause analysis as part of understanding on why this particular bot failed and what could be the reason: 

• Is it because of some kind of data issue? 
• Is it because of an issue from the product? Then, we need to reach out to their support teams. 
• Is it because of an incorrect implementation of the bot or feature that we want to get implemented as part of the solution?

We are moving from single sign-on to no password sign-on. As we are moving ahead with technological advancement, maybe that feature can be added. This totally depends on how that technology is accepted by the people. If people in big enterprises are not willing to switch and don't want to move away from the single sign-on, then it will be very difficult to digest this. However, whenever there is a change, it is very difficult to digest. Eventually, people will like it. I believe if it is implemented as part of UiPath, who is a technological leader in terms of RPA and new stuff when they roll out every release, then this would be a good area that they can look into for enhancement.

They could add more features in order to get that dashboard more intuitive, e.g., how easily can we visualize everything being reported. I believe this should be improved as part of our Orchestrator offering. Now, we have different visualization tools being used, like Power BI. The data gets flooded into those kinds of tools and the dashboard is easy to understand. So, someone with a non-technical background can see the dashboard and understand what has happened. However, to provide detailed analysis, there has to be some improvements so we can provide drill-down data to developers showing, "Hey, this has gone wrong." If they could also incorporate that as part of the reports, then it would be very quick to view on the dashboards.

I have been using it for two years.

UiPath has a number of offerings: on-prem Orchestrator, Automation Cloud, Automation Hub, Cloud Orchestrator, Task Mining, Task Capture, etc. Sometimes, it feels like other new areas are getting more focus compared to areas, like dashboard Insights, which should be more relevant. They should focus on these other areas to make the cloud offering more robust. Though, they are working towards it and releasing updates. Therefore, eventually, they will look into it, work on it, and iron out any kind of discrepancy.

It was very easy to scale up. Since we started getting a lot of data from the client which was getting filled as part of the UI-logged application, we were able to push in data as part of the UI. So, we were able to reduce replies to clients significantly.

We find the solution to be scalable. Since this RPA technology is now widely accepted as part of our enterprise solution, businesses are coming in. Once the business team is onboarded, we can easily onboard the people who have technical expertise to create the bots, analyze them, and provide logic on how we need to design the bots. As part of the initial stages, we only have a business person, a solution architect, and a tool expert. First, we create the credentials for them, then we provide the solution to the business as part of a PoC. After that, if we are using any other traditional system, then it will take a lot of time to get 10 or 15 people onboarded in order to develop the solution in a fully-fledged manner. However, since we have the orchestration capabilities, we can just go in that particular Orchestrator dashboard and create our tenant with a few clicks. We can also move in and out between different geographies. For example, if I want to go and look into what is happening in the Indian service line, I can just go and click on that particular service line, which is already configured as part of Orchestrator.

Initially, when we were going with the idea of creating an RPA bot, the first thing was to get a nod from the business to make sure about how scalable the solution is. At times, what happens is once we get the business sign off, then it takes around a month or two in order to get the team onboarded with all the necessary accesses. Once they get all the accesses, they will start working on the solution. However, in this particular case, as part of this Automation Cloud offering, we didn't have to waste any time after we got the business nod, saying, "Hey, you guys can go ahead and implement this full-fledged solution." Since the orchestration capabilities are there, the moment we received an email from the business, we shot out an email, "Hey, we are getting these pieces and have already created the credentials. Tomorrow, you can get the ball rolling in terms of solution development."

There are multiple channels where we can reach out to them. One of those channels is the Community Forum, which is being constantly monitored for any issues. So, if anybody has already faced it, they go ahead and have it answered. Or, if nobody has seen it before, then the forum moderator comes in, and says, "Hey, why don't you go ahead and reach out to the IT support?" So, this is a channel that gets a response and has faster ways to directly approach the support team managing the servers.

The UiPath Community Forum is worldwide. It is being monitored by community moderators. I have seen feedback being put through to the IT support team, then that is put through to the right channels to get addressed. They really listen to the customer feedback, which is what I appreciate about them. 

The support is responsive at resolving any kind of tickets or issues when we reach out for help. This is one of the primary factors for going with Automation Cloud versus other cloud offerings, like Automation Anywhere and ElectroNeek. UiPath support is very much available and provides a solution. Even if they don't have the solution, they tell the affiliate, "This is how much time it will take," or "It will be released in the next update."

We don't need any IT support in order to maintain this particular solution. Since it is a cloud offering, everything is taken care of by the URL.

In case of any issues for the setup and updates, we reach out to the UiPath support team.

The initial setup is very easy. It is like installing an app on your iPhone. That is how simple it is. Basically, it is not an installation at all. It is just signing into a cloud account. As part of the cloud offering, we are provided with a URL, which gives us access to the Orchestrator instantly. There is no setup whatsoever. You don't have to go and download any EXP or MSA file on your system, then double click it and a number of forms are popping up. It is nothing of that sort. It is a single URL, where you can log in with your credentials, and that is one time activity. After that, it is a single sign-on the moment that you access that particular URL.

The implementation was frictionless with the single sign-on feature.

By using the Automation Cloud version, when there is a new version pushed out, then I do not have to do a reinstallation again in order to get all the newest features. Since I am using the SaaS offering, the new functionalities being pushed out as part of the newest version will be easily accessible to me without doing an uninstall or installation. This is a good part of the offering.

We are seeing a good ROI.

The maintenance work has been reduced because of the bots. Initially, the time that we invested in order to zero in on this particular product was 60 to 70 percent of the job data. This helped us a lot when we were deploying it.

This solution has reduced business costs. For example, products and bots that we designed for UI automation were also deployed for back-end services.

The setup cost is minimized drastically since it is a cloud-based offering. We don't need to have a dedicated person or team to monitor it. We just subscribe to the services, get the URL, login, and the next moment, we are creating tenants and the service line. Then, "Boom!," we are ready for executing the bots from our test check.

Our license cost is reduced since we don't require any IT support. 

I used the free versions of other vendors when we were trying to zero in on the solution that we wanted to use. We used a few other competitors of UiPath as when we were doing the PoC, and the features that we liked the most and made us lean towards UiPath were its intuitiveness and ease of use. We liked how Orchestrator can be used by the business or by anyone with a non-technical background. That is what helped us to make our decision in favor of UiPath. 

With other tools, we had some issues with their support where they were frequently not reachable. They were not able to set up any discovery calls, such as, "Hey, this is how it is going to work." They also don't have very active community forums. 

Instead of talking to the support or sales teams, we investigated on our own. We went to the UiPath Academy, which is readily available, and looked into its documents, which were highly detailed. We also monitored their Community Forum, which is being moderated properly. Then, we read some reviews on IT Central Station, seeing how people are reviewing it and why they are paying for it. For example, if their whole community is coming out with good words, then there has to be something which they are doing well. That is what made us make the decision to zero in on UiPath Automation Cloud.

When comparing UiPath with different vendors offering RPA,like Automation Anywhere or ElectroNeek, we initially thought that Automation Anywhere was ahead of the game and UiPath was playing a catch-up. A few weeks back, UiPath had a good investor round, then they went all guns blazing out in the market. There is a lot of community awareness in terms of UiPath implementation. So, I believe the road ahead for UiPath is very good. 

One of the newest upgrades that we had was in respect to payments getting added. New functionalities are getting added. They also work on the feedback that they get from interviews conducted by sites, like IT Central Station, who take unbiased reviews. They work off this feedback, which is why they are upgrading their products out in the market.

I haven't used the AI Fabric solution as of yet because we don't have a business case for it as of now.

If you are ready with your own business process that you want to get automated, then I would recommend UiPath for its intuitiveness. You should consider the intuitiveness of the UiPath as one of the parameters in your solution decision. For example, if you have the business process ready, then that is half the job done. The other half will be taken care of by your RPA developers or solution architect. So, if you are using UiPath, the learning curve is very small. You don't need to invest a lot of time. 

They have their UiPath Academy learning website, where you can go in as well as ask your team members to learn based on their roles. There are different series of educational videos based on job roles and how that particular role should look at UiPath as a solution. For example, as a manager, if I'm going in and looking into the UiPath, I do not want to be bothered about how I'm going to pull in activities and develop the automation bot. As a manager, I am going into Orchestrator to see how many bots have executed successfully or failed. If I was a solution architect, then I need to know how to design the service lines if they are located in different geographical regions. 

Everybody is really looking for some kind of solution that eases our life since we are working from home. It takes a toll when we are working from home. When we have these RPA bots coming to our rescue, then it makes a difference in our day-to-day life. Then, we can spend more time with our loved ones rather than spending more time in front of our laptop screens.

I would like to rate it as nine (out of 10) because I believe no one is perfect and all the bots are being developed by humans. Going forward, I read on a forum that UiPath is developing an AI feature where the bot will autoheal itself. Once the autohealing feature is implemented, I would rate the solution as 10 (out of 10) because there would be no manual intervention.

We are a small but global company. We are about 1,200 people. We are a logistics company, and most of our employees work in our warehouses. So, our office workers are somewhere between 400 to 500 across the globe. Being a logistics company, we are maybe a little bit old-fashioned. There are a lot of papers going back and forth, and we are trying to automate different scenarios. We cater provisions to ships, so we are basically a grocery store for ships. 

One important thing is when a ship is going into port somewhere, they put in an order for whatever provisions they need for when they leave port again. So, we need to be quick at expediting their orders. When they put in a request for a quote for whatever products they need, we need to respond very quickly, because the tendency is that whoever responds first gets the order. So, we want to do that. We are trying to sort of increase the speed of those types of operations as well as the quality of them. 

It is hard to really pinpoint what it is we are doing, but it's the communication between customers. When we receive a communication from a customer, we want to move the process through our company as quickly as possible and with high quality.

We are fairly new to UiPath still. We do intend to use it company-wide and have started out with purely unattended scenarios so far.

We invoice every month quite a substantial amount of money to our customers. We saw a problem in that about 20 percent of our invoices were sent to the wrong addresses. That meant that, at month's end, when we were expecting money to come in, we would be missing around 20 percent of our cashflow that month. Of course, we wanted to prevent that because 20 percent of the cashflow of $300 to $500 million a year is a lot of money. 

We have automation that runs every night through all our invoices. Because we have some problems with our master data in the company, it does a number of measurements, on whether an address for an invoice seems to be the correct address, and a number of checks, such as, what ship was the goods delivered to? After that, it looks up information through the international registers of ship ownerships, then it will do a number of checks, giving each invoice a score as rating the probability that the address is correct. If it is below a certain threshold, then we will do some manual processing, and we are looking into UiPath Action Center for this. For four or five of our largest branches in the US and Asia, we have seen a significant improvement in the payments at month's end, which has definitely improved our cashflow.

The administration is a SaaS solution, which helps to minimize our on-prem footprint. The only things that we have running on-prem are the machines running the robots. Everything else is handled in the cloud. We don't need to worry about backups, etc.

We are adopting as much as we can some of the things that should reduce the maintenance costs. We are using Robotic Enterprise Framework in our development and Automation Hub to sort of qualify our ideas. So, we are trying to implement a uniform way of doing things throughout the lifecycle of an idea. UiPath supports this fairly well, and I think it will get even better.

Just this week, we are launching our Automation Hub effort because we need to start building a pipeline for our automation candidates. Right now, we have eight or nine ideas in our Automation Hub. That will grow quite quickly because we need the help of Automation Hub to decide on which idea that we will be moving forward with next.

UiPath continues to add services to the Portal. It is fairly important that they are all managed from the same place because it is a single point of access, which was a factor that really played into our choice of vendor, UiPath. We use Automation Hub to sort of collect ideas and discover what ideas are good for information, then we use Orchestrator to manage them once they have been developed. We are hoping to use Insights at a later point, when that is available in the cloud, so we have a complete end-to-end solution in one place. 

Automation Hub is an immature product. We have only been using it seriously for about a week and have already seen some things that will give us a few headaches down the road. We are committed to using it and will continue to use it, but I have some suggestions for improvement. We have been in contact with our local UiPath office about that, and their initial response was positive.

We would like to see more detail and refinement. It is still a young product, and we are confident that the product will improve a lot over the next few months.

We are hoping for some integrations between Automation Hub, Orchestrator, and Insights.

We are missing a way to quantify that money isn't everything with this solution.

Our license was activated sometime in July. So, we have been using it for about six to seven months.

We have seen a few quirks here and there. Overall, we are satisfied with the stability.

We have only a couple of handfuls of automations running, which are very stable. So, we are not doing much maintenance at all. Maintenance needs half an FTE, if even that.

The potential scalability is really good.

I don't know what the scale is for UiPath Portal. There are still signs that it is a young product, but we see it moving and improving at a really good pace. So, we have high expectations.

The technical support has been good. I have only used them a couple of times. The response has been good. They are knowledgeable. 

One of the big reasons why we chose UiPath is that it has a big following in online communities. It has a good forum itself: Forum.UiPath.com, but I really wish that UiPath would have moderators in their forums who are more active. There are a lot of questions that go unanswered, and that is a shame.

We didn't previously have any other automation solutions in this company.

Our initial setup was very straightforward. Our deployment took only a couple of days. We are a small operation with only two unattended licenses. We created the Orchestrator account and installed the robots on two servers. 

As far as development goes, we really just have the base package. Then, we are adding on Automation Hub right now.

We did engage with their local consultancy. They sort of helped us build a strategy for the infrastructure structure setup and strategy, as far as how to identify candidates, operations, and development. However, initially, we just wanted to pull the trigger very quickly. We had an evaluation phase of a couple of months, where we were testing different products and had tried to set up UiPath before, which helped.

We have used Carve Consulting, and our experience with them has been fantastic. We are working with this third-party consultancy to have them come up with a couple of ideas for some solutions that would involve AI Center for the end of this year or next year.

The initial deployment needed just a couple of people from our side, including me. I worked a little with some of our infrastructure guys, getting the accounts set up, the service division, provisions, etc.

We just haven't scaled to a point yet where there has been any kind of return on investment.

There are not very many users because the stuff that we have automated so far has just taken work off people's hands. Where a person used to spend all day uploading pricing data into a database, we have a bot doing that now. So, people are not using UiPath, they have just sort of been relieved of their duties. While that sounds bad, we have made an effort to find areas where FTEs get to spend time doing what they are best at.

The licensing is too expensive. It is not a cheap product. We constantly have to build business cases where we have to justify our existence as an RPA team. 

We have engaged in a long-running licensing agreement because we believe in the product.

We have used a third-party consultancy, and that's definitely not free.

We looked at a local variant of Kofax RPA called SmartRPA, which was built by a Danish company. It is basically Kofax RPA with an Orchestrator service built on top of it. We evaluated that. We also looked at something called OpenRPA, mainly due to price.

UiPath is built on top of Windows Workflow Foundation, which is a platform that I have worked with previously. So, there was a lot of familiarity and extensibility. Then, we looked at how good the product is at automating desktop applications. There was not really a contest there; UiPath was better by far.

The fact that this is a SaaS solution very positively affects how fast we are able to innovate when it comes to automation. When we did the evaluation of what product to choose, UiPath versus something else, the ability to assess deployment of the whole administration was a key factor.

In our decision to go with UiPath, it was very important that we didn’t have to worry about future installations and upgrades of Orchestrator. We just didn't want the trouble of having to do upgrades. With UiPath being a young product that is evolving very quickly, we would be doing on-prem upgrades every few months and we don't have time for that. So, we liked the idea that it is a cloud-based setup.

Security was a factor in our decision to go with the solution. We didn't look into all the technical specs and certifications. We just looked at some of their customers, and said, "If that bank is using it, and it is used in the defense industry, then they know what they are doing." They had good references.

It is the best product.

It is an automation product. At the end of the day, it is software development. If there is anything that is important in software development, it is that you have a defined process from beginning to end, from the birth of the idea until it has been put into production and eventually retired. So, you need to have a defined process for different stages in the lifecycle that you need to be in control of. The product somewhat helps us do this with Automation Hub and the Robotic Enterprise Framework, but we are looking forward to even more tools for stuff like that.

So far, we are still in the meat and potatoes space. We haven't really gone into the AI or Document Understanding stuff yet. 

UiPath Portal is good overall for enabling administrators to work with Orchestrator. I have seen a lot of improvements, even in the last six or 12 months. We are learning as we go. For the first few months, we were working in a classic folder. Now, we are adopting modern folders in order to better be able to scale our efforts.

UiPath provides granular, role-based access control and management. Right now, that is not so important to us because we do everything unattended. So, we have a couple of service accounts that run everything. However, once we move into attended scenarios, then it's really important that we have that granular control.

I know that there are some new features coming out in regards to deploying automatically and elastically, but we haven't looked that much into them. We don't expect them to be a problem.

We are looking forward to doing attended robots, but that will probably be in the second half of this year when we start looking into that.

For the size of our company, we started fairly big. We went all in, buying licenses, consultancy hours, etc. We have spent a lot of money this first year. I would probably advise someone to start small but still be ambitious. Do a lot of PoCs and see how it fits into your organization. There needs to be a lot of disciplines surrounding it, e.g., if you just stay with five or 10 automations, then things are good. However, once you build 100, you start running into maintenance problems and things like that, so there needs to be a discipline. 

You don't need to spend a million dollars to sort of get off the ground, so I would advise people to start small.

I would rate this solution as an eight (out of 10).

We primarily use it to reduce manual effort and to increase accuracy and on-time implementation. We perform end-to-end automation, since we are a company where SAP is used very widely. We use UiPath for SAP automation.

We develop both attended and unattended solutions. We're using the platform as a service and it's hosted on-premises.

So far, we have 15 bots in production. As a result, we are saving a lot of time, although I don't have a figure right now, as well as a lot of effort. We are also able to provide timely delivery to our customers, so the automations have been generating a lot of buzz here.

Attended automation has helped to scale RPA in our organization by automating processes that require human-robot collaboration. An example is our invoices that have data that needs to be scanned. The scans we were receiving did not have the accuracy that we were looking for. We also had a hard time getting the results through OCR. With the help of attended automation, we are able to have users verify data when the bot is running. Once the verification is done, the bot will perform the rest of the actions.

UiPath also definitely helps us with process analysis.

Although I have not used it yet, they have recently introduced a feature which brings more accuracy to the selectors, using the image and the selectors themselves. I feel that will be good. When we are creating selectors, there are elements that it's hard to get at, or there are times when the selectors get changed for some reason. The new feature should make it easier to work with in these situations.

They have also recently added a feature for attended automation, Picture in Picture, which is also nice to have. It's helpful because you don't want to just sit back and let the bot run and not work during that attended automation. Using the PiP feature, you can have it running on your desktop without having to interrupt it to your work.

I would also compliment them on the UiPath Academy, the learning platform that they have built. It contains everything that a developer or architect or tester or, anyone who is looking to benefit from an RPA, would need. It's all there on their platform. It helps speed up onboarding employees to UiPath. When I joined this company, I had prior experience with the RPA and UiPath. But two of my colleagues, who were working on test automation, didn't have that kind of experience. The Academy helped them to get started. We aligned quickly, once their fundamental developer training was done through the Academy. The Academy helped them align with the current practices of UiPath and RPA.

One area that needs improvement is monitoring. I know there are tools that let us see what a bot is actually doing on the virtual machines. If we could get that kind of offering from UiPath that would be great, because when a bot is running on the machine, we don't know what it's doing. Although we have programmed it, there are times when something causes a bot to fail. During such instances, the bot behaves differently when we run it in attended mode than it does in unattended mode. It would be great to have a feature where we could see, on a screen, what the bot is currently doing.

We started this UiPath journey two years back. 

I act as a UiPath lead because I joined early and I have some prior experience with it. There are three other people in India, and one more in the U.S, who use it in our company. The one in the U.S. does the managerial stuff and it's the developers who are in India. Then we have the business users for each of the bots and they also use UiPath. And we have a set of about 20 users who use the attended solution that we have provided to them.

Robots on the SAP system seem stable, but on the web they sometimes lack stability. Still, it's not a very common occurrence and I have overcome any issues with the help of the Trilogic. For example, we had an issue while getting an email from Outlook. A UiPath robot is not able to do that. It will time out. With the help of the Trilogic, we were able to overcome that.

Initially you have to put some effort in to obtain stability and then it is mostly stable. Some maintenance is required, but that's most probably when requirements change, or to add to the stability, but it's not a lot overhead right now for us.

It's highly scalable, in both development terms as well as business terms. We have the capability to add on robots. We can add to the VDI or machine anytime we want. They have put some serious thought into the scalability, when it comes to giving support to developers as well as the business.

We plan to increase our usage of UiPath. We have a lot of things in the pipeline. We have almost finalized on providing RPA as a service, something that we will offer internally. Right now, we are giving this free of cost to our customers who are the business people. We did so to get some attention and to create some interest in the tool. Now that we have almost finalized this as a service, we are going to involve business analysts who will be helping us to find more RPA use cases and finalize more RPA solutions. That means our usage will increase. We're still in an early phase.

I haven't had the chance to interact much with the technical support because the forum has so much information. If I browse through the forum, I will most probably get an answer. So I haven't needed to go to the technical support for any answers.

We have both test automation and UiPath working in parallel. Test automation has been here for the long-term, something like 10 or 15 years. The two guys who work with me, who didn't have prior UIPath experience, are working on that. That part mostly requires maintenance, and they now mostly work on UiPath development. So although we had a test automation solution, we didn't have a business automation solution. That is why we went with UiPath. It gives us an edge in business automation.

The initial setup of UiPath was pretty straightforward. I didn't find anything unusual or complex.

We went through an upgrade recently. We have dedicated cloud architects who helped us do it. We got instructions how to do it from UiPath support and we conveyed those instructions to our cloud architects and they performed it at their end to get UiPath cloud upgraded. Upgrading didn't take much time. It was done within half an hour.

One more feature that is useful is that earlier, we didn't have the option for a concurrent-user license. With the help of the concurrent-user license, we can save on licensing costs while running multiple bots under the same license.

If you are going to implement UiPath, my advice would be to look at how you are going to gather the requirements and how you're going to manage the requests for UiPath. 

Also, get some low-hanging fruit first, before going into the complex automations. That way, if you are new, the low-hanging fruits will generate confidence in the solution. Once that kind of confidence is generated, you can move ahead with the complex automations and complex solutions.

Go through the UiPath Academy extensively. They provide good training materials that I don't believe are available elsewhere. So I really recommend that. I recently attended a dev conference and I learned a lot about this stuff. I work in a closed environment where I don't have much of an idea of what's going on in RPA. This conference helped me keep in touch with the current trends in RPA and UiPath.

I rate UiPath at eight out of 10. For me, that's a very good mark. The two missing points are because there is scope for improvement. Overall, I'm pretty happy with UiPath.

Most of our use cases are related to business, like reconciliation and reporting. Therein, they have some internal applications to automate SAP automation and Salesforce Automation. Our most recent use case is related to documents, like the invoices coming from customers. We have to extract that data from invoices via different formats, e.g., some are digital formats and some are scanned formats. So, we have to extract the data, which we are doing with the help of UiPath.

We are using both attended and unattended automation. For 90 percent of our use cases, we are using UiPath for unattended automation.

I use UiPath almost every day. When I finish developing one process, there is a new process to develop. If a process is complex, it almost takes six to eight weeks to develop it, then you have to deploy it for monitoring. After that, the next process comes up.

UiPath helps based on how it is configured. In our case, there are so many transactions coming in, it is not possible for a human to complete them in nine hours (working hours). So, we went with unattended bots, which we mostly run at night. We start the bots after the working hours of humans, so when the operations team returns in the morning, their work is complete.

From a developer perspective, the process is smooth and easy. You can find a solution on Google easily. You can develop your own code. From a technical perspective, it is 100 percent.

UiPath Studio is great. It has all the activities. You don't have to write anything. Even after that, if you feel that you have to do something for yourself, then you can write your on-premises code in it and develop your own framework. Everything is there. You just have to use UiPath Studio.

if you are a business user, even if you don't have a technical team, you can install the second version of the Community edition, which is StudioX. This is specifically made for business people who don't have a lot of ideas about technicalities. This is a great feature.

If websites are made in a recent programming format, it is very easy to automate them with the help of UiPath. However, if that technology is based on legacy applications, then it is very fragile and hard to do that. So, we have to choose the technology first, and if the technology is new, then you can easily automate it with other applications or the help of an RPA tool.

The process can be complex if an application is a legacy application or the data is unstructured. The analysis of some bots is lacking. If a customer asks for analysis of a particular bot, you cannot just get the data from the UiPath and give it to the customer. It is not that easy. I would rate this process as a seven or eight (out of 10).

The Document Understanding feature should be more developed and advanced. For example, you have to make a template with their ML model. Currently, we can't use our own ML model, and we have to use the UiPath ML model. UiPath has only a few ML models right now. They should come up with more ML models or make it easier for us to use our own ML model. While they are working on this, I have felt much difficulty in extracting data during our last process for Document Understanding. We had to go with the Python language. So, I think they are lacking in this feature.

After deploying the bots in production, processes are very stable, unless something happens with the machine. You don't have to monitor a process every time. So, I am very impressed and satisfied with things.

We are looking to update to version 20.

This solution is very much scalable. If you are working in a small or large organization, it doesn't matter. It is very much scalable, up to anything.

We have a team of around 100 to 120 people in RPA automation, in which 60 or 70 users have the developer license. 

I am very much impressed and satisfied with the UiPath solution. Earlier, I used the Automation Anywhere solution, and it is sort of messy and complex. You have to pull everything from a single workflow. Then, I moved to UiPath, and everything was very sorted. If you really like coding, you can do that. It gives you a real developer type feel.

Developing and deploying robots with UiPath is very straightforward. It hardly takes five minutes to deploy a process on Orchestrator.

The last process that UiPath covered saved the work of two people.

If you have repetitive tasks, you can apply UiPath and have your people trained to do other work.

If you want to start doing RPA, I think you should definitely go with UiPath because it has the Community edition. You can just install it and check whether or not your process works fine with UiPath. It will be an attended bot, but you can form an idea whether your bot can easily be automated.

We have one use case related to Microsoft Word Automation. Word Automation is not compatible with other tools. However, in UiPath, we were able to write our own code to automate and format the Word document, which is why UiPath Studio is the most valuable feature. We are also using the Automation Anywhere. But, in Automation Anywhere, we cannot write our own code. So, we can't automate Word Automation from Automation Anywhere as well.

Automation Anywhere has come out with its own new version of 2019, which is as effective as UiPath. However, when I have tried to run or deploy the bots, it still lacks in features. For example, in UiPath, AML activities are coming up very frequently. Whereas, in Automation Anywhere, these features are lacking, which is why I go with UiPath. Also, Citrix automation is very good with UiPath. You feel like you are able to detect the elements and images.

UiPath gives you REFramework, which is absolutely amazing for business use cases. Automation Anywhere also lacks this feature. With Automation Anywhere, you need to make your own framework, and if you are making your own framework, then the look becomes messy. If someone is trying to understand it, then they have to spend more time on the framework to understand it.

I use the IQ Bot of Automation Anywhere, and even after training a hundred documents, it's not picking up or extracting the data from documents. I feel like I have to train the model again, which is not the case with Document Understanding. If you properly make the templates in Document Understanding of UiPath, it gives you full text values. So, it is more advanced and suitable for me.

We use UiPath Assistant to run processes about 10 percent of the time. Most of the time, we are using Orchestrator. 

UiPath releases new features every 15 days to a month. They have already come up with AI and machine learning.

If scanned documents are coming in for some of the work, we are also using Python language for this.

If you already have a technical team, then you can ask them to look into UiPath Academy. If they have basic knowledge of programming or coding, then even in seven days, they can easily learn UiPath and start applying it in their organization. You don't need to hire outside developers.

Overall, the solution is a nine (out of 10).

We use it for financial use cases: purchase-to-pay processes, reconciliation processes, vendor payment, and merchant payments. This is just in finance. Then, we have retail order processing, order creation, PO generation, delivery note generation, and all those things in retail. We even have banking processes as well, such as a payments portal. We use it in most of the fields.

We don't use cloud licenses. Most of our licenses are on-prem.

We use both attended and unattended automation in UiPath.

We are partnered with UiPath. Sometimes, UiPath refers customers to us, bringing us business. We also give them business.

We have a third-party order processing portal, which keeps on changing its UI very often and has elements that keep on shuffling between the metadata. What we had in this case was the script running was shuffling the elements, and we are disabled that thing. Then, we used the selector technology instead. Selector technology is very important for all our UI-based processes. We rely on it. 

We used the AI Fabric functionality in one of our projects. We had to categorize users' reviews based on the sentiment scores. Everything was already available, including the model. So, we just have to click on all those things from UiPath now.

The new features that they are adding in, these are very different from other RPA tools in the market:

• AI Fabric
• Integration with different data models
• You can do all the data processing, data mining, etc., in the back-end UiPath. 
• You don't need a separate tool for data mining or other cognitive abilities. You can do all the cognitive abilities in UiPath. 
• UiPath Apps, which they're bringing in just now, is a really good thing. It has a good user interface.

Most RPA tools do not directly have these features. Also, we don't have to rely on other tools in order to develop these things. We can directly develop and integrate them with UiPath on one platform. So, we don't have to struggle within multiple platforms.

UiPath Apps is available only on Community. So, this was a best case scenario for us. It was pretty good. The only thing is that it has to be more advanced. Now, it is very basic. I would like more integration with the UI elements. It should be more user-friendly, especially if we go for any other application development. For example, in other UI development platforms, you can easily drag and drop to develop in a UI. However, it is a very initial phase for UiPath Apps, and maybe in the future, they might improve this.

We have used the Picture in Picture functionality for a few attended automations, where the user is monitoring or we are installing a new interface. Sometimes, in my experience, Picture In Picture is a bit buggy. It takes over your control, then the controls get mixed. That is one of few issues that I have found. Other than that, Picture In Picture works pretty well.

I had an instance when UiPath crashed on my computer. Then, the code that I was working on also crashed. This was a very crucial process for us, but we apparently didn't have a backup. UiPath also didn't have any way to recover that code. This was something which I found very strange, because ideally the source company should have a mainframe where they can recover a code. Or, if I give them a corrupted damage file, then they could easily recover that code. 

The stability is pretty good when we follow the best practices, i.e., whatever is in the REFramework. 

Scalability is something that we are still figuring out. RPA is something which we cannot do for everything, because there is a small gap between profit and the cost.

The support has been pretty good so far. The response time could improve, then it would be much better. However, once we get a ticket assigned to a technical person, then it is pretty straightforward. They are very fast, know their job, and know how to resolve the issue.

The on-prem setup is straightforward. There is very detailed documentation. We always get support from UiPath, so it is not difficult. I have never faced any issues, but I have only deployed on a small scale.

The timeline of the project depends on the project's complexity. Usually, the due diligence and everything else takes about two or three weeks. Then, the design takes another one or two weeks before we start with the development, depending on the inputs.

I get involved with small client setups.

There is a client-facing team of around 25 people who do due diligence and design work. There is also our back-end/technical delivery team, which includes mostly developers, a product project manager, project owner, and developer lead, who are there mostly for their technical abilities, not for their design abilities. 

The price of Orchestrator is pretty high in general as well as compared to other solutions, because Automation Anywhere does not charge for its Control Room.

We can develop our own packages and integrate them, which is pretty good. Other tools don't have that.

There are a lot of cons with Automation Anywhere, which we are using. They deployed a new version, 2019, which is very buggy, and they are still working on that. I don't know how or why they released it to the public. They did so much testing, but it is still buggy.

Power Automate (previously Softomotive) needs to improve on its UI. The ease of use is not there with this solution.

Go for it. It is a pretty good tool, which is straightforward and easy to use. They have training in place. Even if you are new to it, you can go ahead and learn to do it. 

They are bringing in new things. You can automate, integrate, and test things. It is even used for mobile testing. It is pretty good in that case. For most of people's use cases, UiPath will suffice for their use cases.

I would rate the solution as an eight (out of 10). 

One of the use cases that I have recently completed is related to SAP and the interaction with Excel and our internal application. We are going with the JD Edwards EnterpriseOne ERP application and we used UiPath to help in this area, and were able to do so within a few days.

Some of our people are going for process automation and some are doing desktop automation.

It helps our developers learn and implement things faster.

Also, the UI Targets feature has helped us with some difficult situations. We were using other solutions for these situations but our company has moved away from them to using UiPath, and it's working very well. 

UiPath provides lots of integration to our ERP application and lots of new updates are coming out day by day. It helps us to automate our tasks.

We are using the solution's selector technology for UI automation. That is the most important feature for us. For example, one of the applications in our company is being updated day by day, by the development team. We use selector to make it dynamic.

We also use the latest version of the desktop Assistant tool for some queueing activity in UiPath Orchestrator. The tasks in the queue are continually updated and then they are run by robots. Using Assistant, we get a lot of information about our queues, like if something fails, for example. Also if a robot fails we get robot status-type information from the Assistant. The Assistant plays a good role because, if a process is going wrong, we have control. Using the Assistant we can stop that process. It is a most important feature from UiPath.

An area which the UiPath team is rapidly working on is machine learning and artificial intelligence. At the moment, it is a little difficult to understand. If they could add some more training on it in their Academy, it would help customers to learn about these features.

I have been using UiPath for the last eight months.

We only use the stable versions, regardless of whatever they are releasing, to avoid bugs and errors. In the stable versions, we have never found any issues or any bugs. If there is any issue, we have a team that will contact the UiPath team and we will get quick solutions. But so far, we have never had any problem or issues with a stable version of UiPath.

We use the Assistant to handle all the robots' actions. We are scaling and tracking it. That is very important for us. The scalability features of UiPath are awesome.

In the eight months I have been working with UiPath I have implemented seven or eight projects. Day by day we are increasing our usage of it, and UiPath is also increasing the product's features and adding technologies. That enables us to work on more projects, as it is easy to integrate.

We have been able to implement a lot of little projects. That is one of the reasons that it is cost-effective. In addition to the affordable price, it just takes a few days to develop solutions for these projects.

In India, a developer costs about 16,000 rupees per day. Using UiPath, all our projects have been done in 30 days. If we tried to do these little projects in another technology, they would be more costly because they would be more time-consuming.

Our company is based on automation. UiPath is the correct solution for this. It is cost-effective and has an affordable price.

UiPath is not the only technology we are using, but we are migrating to UiPath because it is cost-effective. The previous solution was Blue Prism, but for the little projects, it was not the right solution.

In addition, the Control Room is really required for other technologies, like Blue Prism, but there is no need for it with UiPath, because we manage and deploy it with our team only. We don't need to worry about the Control Room.

For the beginner the UiPath Academy has a lot of training available. It's important to go through the training. After the training you can easily work on any project in UiPath. So first of all, follow the training. For intermediate-level users, UiPath is the correct solution. These users just need to keep up to date, day by day, because the UiPath team is rapidly updating the features.

The Picture in Picture functionality for attended automations is a new feature. Up until now we have not used PiP, but we have some use cases for an internal project we are doing and are looking into it for the future.

We are using UiPath Automation Cloud, but we have not yet migrated our on-premises UiPath instance to it. We are thinking about the on-premise because it fully depends on our own enterprise. If we go to the cloud, we will be able to collaborate better with our team and what others, because it is "public."

We use UiPath to automate business processes such as certain types of reporting that have to be repeated on a month-to-month basis. Another example is invoicing processes, which can be automated. Generally, it applies to different business cases for enterprise automation.

An example of how UiPath has improved the organization stems from a cyberattack in 2018. We already had an RPA team and during that cyber attack, all of our systems went down. Our SAP provider cut our access to it, leaving us with a limited number of users. It was not a big enough team to deliver on to our clients all of the orders that were being received.

What we did with UiPath in that crisis scenario in a couple of weeks was that we created a process for order automation. We already had a proof of concept, and we were able to scale it quickly. It was not perfect but rather, done in an emergency situation.

With that couple of users and limited access to SAP, a couple of robot users were capable of working 24 hours, seven days a week, and we started to process all of the orders that were coming from the rest of the company. This is probably something that you could not have done with more classical solutions.

This was, of course, an emergency order automation and it was a topic that we were already working with. Prior to this, it was already a benefit for the company, but the fact that we had this flexibility showcases how powerful this tool is, or what its potential is.

Having the cloud-based version allows us to be at the latest version of UiPath Orchestrator and different products without having to take care of the upgrade process.

UiPath's portal for enabling business users to trigger and monitor jobs is a big deal for me because it's something that we have been trying to do for a long time. We have been asking for it. With the previous solution, which was the orchestration platform alone, it was not a good approach because the business users would have a lot of information on their hands and you have to either split your licenses so that they could not access everything, or create your own web portals for them to access specific parts.

The fact that they now have an intermediate portal where they see only their processes, which they can monitor for themselves without getting too much information that is not relevant for them, is a big deal. Something as simple as triggering your own process, which in the past would require dedicating a full license to, can now be done through the portal. It might be a task like checking emails for customers or creating your own application with their API. It's a huge increment in quality.

The portal can also be used for administrators and although we have the Action Center, we don't use it that often. From the point of view of administrators, I can say that the recent improvements make our life much easier. It also enables us to think of more complex setups. In the past, I would never allow certain configurations because they would either be a security risk or it would just create more problems than solutions. Now with the current interface, especially with what they will be adding in the future in terms of more governance from the platform, they just enable you to do more complex things. It allows you to go a little bit beyond what the normal scope would be.

That applies to the platform as well as the orchestrator in the new modern setup. They have the option to split within the same tenant and different companies, or different company departments. Also, the fact that you can dynamically allocate the licenses so that you don't have to worry or have to split them, brings us to another level.

It offers more granular and role-based access control and management. We now have more complex scenarios that in the past we would not even consider because it would be a problem if someone were able to see something that they should not see.

The fact that this is a SaaS solution is important to us and it is clear to me that they want to push a SaaS solution, more than the on-premises deployment. It means that we have the latest version without having to upgrade the systems. We always have the latest version of the studio, for example, and there's no disruption to our services. Furthermore, we are able to follow all of the previews that they come out with. We can try all of their new products, which is something that in the past, we would not have been able to do. It would have required, for example, upgrading our system twice a year. Certainly, we wouldn't be able to do it at the speed we can now.

Being able to minimize our on-premises deployment is really important. It was almost a given for us because we lost some of our interfaces during the cyberattack. From that point on, the company has had a clear policy of cloud and SaaS as a priority. The fact that we have the opportunity to access all of our services without any requirements from our side suits us very well.

The vendor continues to add services to the portal and we are connected through their insider program. This is something that we are really happy with.

It is helpful for us that new services being added to the portal are all managed from the same place because it simplifies our work, makes it cohesive, and makes sense from a philosophical point of view. Definitely, if they had it on different platforms, it would take away from the ease of management. The fact that they have it in a single place makes everything a little bit more interconnected. What they are doing seems to make sense and for me, it is good because we only have to take care of one single platform. This also speeds up our processes, which is a plus.

On the topic of security, especially coming from a cyber attack, having SOC 2 certification is important because it is a requirement for us. We probably would have tried to find an intermediate or an agreement, but the fact that UiPath is now SOC 2 certified means that we have complied with requirements.

The licensing system is something that needs to be improved. I think that if they are trying to push for a SaaS solution, with respect to the way they license their individual products. The robot licenses and the Studio licenses should be something closer to a pay-per-use, rather than a year-to-year license. Right now, the licensing model and the pricing are the only stoppers for us, in terms of escalating our use. The bottom line is that the licensing system is not as modern as the tool that we're trying to implement.

We have been using the UiPath Automation Cloud since January 2020, and prior to that, we had an on-premises solution from UiPath.

Four to six months ago, this was not the most stable solution. We had a lot of issues, especially during the summer and early autumn. The system would fail, or would not be accessible, or we had lost some of our logs.

Right now, the tool is working and is much more stable. It shows that they have put an effort into making it more robust.

With respect to scalability, the licensing system is the limitation.

The platform itself is scalable, although not infinitely, but to a couple of orders of magnitude of what we have now. However, you still have to go through the procurement processes, which always makes it a little bit more limiting. Ultimately, it means that we cannot utilize the full power of what this tool offers in escalation.

Currently, we have five people who are working on UiPath. There are three developers, I am the technical lead, and we have a manager that operates as a product owner for the projects. The three developers are also responsible for maintenance. We also have a business analyst who works through the documentation and is the point of contact for some of our business.

We have other non-official roles, who are people that know and use the tool or perform business analyst functions, but there are only five people in dedicated roles.

At this point, we are using the tool to the full extent of what our licenses allow us to do. We could scale it to be much bigger but in the current situation, I don't think that we will do so. We negotiated the last contract to be a five-year deal and I hope we can move beyond that, but for now, there's no plan to a scale.

We have mixed reviews for the technical support and depending on the topic, they will answer faster or slower, more personalized or not.

They have a ticketing system and the webpage is normally broken, depending on the browser. The response time may vary from topic to topic, so I don't have a consistent impression of the support system. They do answer our questions, but it is not always within the proper time or with the solution that we were hoping for.

What we are using now is the same thing as the previous product from UiPath, without the cost of having to host it yourself.

I have some experience with other products, but not at the professional level. My impression is that with UiPath, you can get started more quickly when compared to other RPA products. Also, the licensing costs are not as high.

Migrating from our on-premises solution to the cloud was not a typical case because we lost our on-premises deployment during the cyberattack. We had at least a few months without the Orchestration solution. When it comes to execution runtimes, where we run our processes, we used the same machines.

Basically, we had to set things up from scratch on the cloud. The process was pretty straightforward, and the fact that we didn't have to set up the Orchestration tool saved us from a lot of the complexity in the setup process. Normally, this is the complex part, including setting it up with the databases. We just had to connect our runtime with the Orchestration platform, which made it much easier.

With respect to the setup costs, the cloud setup balanced out because you don't pay for the orchestration platform, but you pay a little more for the individual licenses. 

Having this product has reduced the amount of maintenance work related to our automation operations because it is a managed solution. The fact that we don't have to host it ourselves is very important.

With respect to maintenance costs, we are a relatively small project, so I wouldn't say that we had a huge overhead. It would certainly be higher if we tried to do what we are doing now, which is being at the latest version all of the time. To do that, we would have needed somebody in a role who was taking care of it. As it is now, from a development or project management point of view, we can take care of these things without needing an architect involved all of the time.

We chose Automation Cloud because it was, at that point, the most flexible option.

UiPath is known for a certain number of products, and the role of our team is to use all of them. On the topic of the UiPath Cloud, the new products that they have come out with, like the possibility to create your own applications for your internal customers, or host certain data services from the same platform, were things that were not available in the past. These capabilities are useful. In general, all of their products are pretty important for us.

For UiPath as a company, we like the availability that they have and the fact that we can try and test all of their products beforehand, without paying. For a relatively small project such as ours, or even for a big company, it's pretty useful to be able to access this type of information and not be burdened with extra budget requirements.

This is a product that I recommend because the starting point is completely free. That's one of the great points of UiPath. My advice is that when it comes to scaling the project, it's really important to clearly set up goals and expectations. Otherwise, there will be an eternal loop of PoCs and non-viable products.

I would rate this solution an eight out of ten.

We have a use case that involves an invoice billing process, where vendors from an external organization submit their details for the invoice. This automation works as expected, independently of anything else. It is also a good example of how we were able to scale RPA benefits in the company with the automation of a specific process that requires human-robot collaboration.

Our internal tools include the database where all of this information is stored, and we have a second automation that is used by the billers in our organization to tally the data that includes details such as what each vendor has submitted to get their payments.

We built a third automation in UiPath, which basically compares these first two. But, due to the complexity and the nature of the tally that has to occur, we require some human input in between certain steps.

For these particular steps, we have developed a four-bot configuration. These are four separate bots that run and a couple of them have an attended automation part, where a human can intervene. It's a verification step, where the human can decide whether or not something is okay. Specifically, the bot compares two fields and if they match, then it's great, but if not, it triggers a request to a human user for manual verification. If they approve then it is marked as a successful verification.

Because we use technologies like OCR, there are details that cannot always be interpreted properly. This is where we need an additional check, which is the reason that we have humans in the loop as part of the process.

We have saved a lot of time by using UiPath. We have also improved a lot in terms of accuracy and reducing errors in a lot of projects. In fact, in one of the projects, we automated the entire job, which involves coaching people on what has to be done end-to-end, by the robots. It was built on UiPath and on this project, we had a savings of more than €100,000 euros. That was a big saving for us, and it's continuing right now.

More importantly, a lot of the clients had complained about the end-user, which is outside of the organization, with respect to the accuracy of the data. There were errors. When we deployed robots based on UiPath, the accuracy has vastly improved and the clients are very happy with the results. They no longer have to keep coming back to our billers and telling them that things were not done properly. The robot functions like it has been programmed every single time. So, it's been perfect for that purpose as well. The customer trusts us more because of our deployments in robots.

UiPath definitely allows employees to delegate mundane tasks to their personal automations, saving them time. A major reason for a lot of our automation cases is because most people are not 100% involved in certain tasks. For example, if you spend two hours on a particular process, and then over the next four or five hours, you're supposed to be working on more complicated processes, but what happens during the first two hours is that things get complicated and the day is ruined dealing with small tasks. Now, suppose that the two-hour allotment for the smaller process is automated using UiPath, the person is free to dedicatedly perform more important functions. In the entirety of our automation effort, this has been a primary driver for all of the new use cases. It's a huge plus for us.

With respect to employee satisfaction, it has been a mixed result for us. In certain cases, it's been a huge boon because there was a heavy workload on the employees and UiPath really helped them cope with it. This was especially true during COVID when the workload increased exponentially, and people could not go into the office. However, there were times in the past when people were no longer required because UiPath was doing their jobs perfectly, making them redundant. As they were no longer required, they left the company.

So, we have had both scenarios, but moving forward, instead of telling people that they're no longer required, we have retasked them to other projects. Essentially, we have reabsorbed them and in turn, have simplified the hiring process. In this regard, we have adjusted.

The new UiPath assistant is very good.

The customizable forms that UiPath has recently launched allow us to give the user an exact input that they can provide. Being able to customize this is extremely helpful for us because we have other attended automation processes, and they can each be tailored to the needs of the business.

We use the selector technology for automating processes with dynamic interfaces on a daily basis in almost all of our projects. Our extensive use of this feature includes all of the different kinds of selectors that UiPath allows. We have the flexibility to modify these selectors as per our need. This functionality gives UiPath a big edge over its competitors and I know this because I've personally used products by other vendors. The selection-making process is much simpler with UiPath, with improved accuracy and reliability.

This feature is important because a lot of the processes are Citrix-based or remote desktop applications. Because the robot would not have a direct connection to the application, we have to use Citrix technology. All of the applications are different in nature, so having the flexibility to switch between different kinds of selectors and select our activities allows us to build the perfect solution for remote applications. Even the performance, in my experience, has been the best, especially for Citrix-based automations or remote desktop-based automations.

There are a few features that could be improved, and one of them is good integration with the Microsoft ecosystem. For example, Microsoft launched Power Apps as its platform, and even though its capabilities are not as good as UiPath, it has the advantage of being so well-integrated with Excel Online, Word, and everything else. We don't have to perform a lot of development work, and it's pre-approved in our organization. Applications like SharePoint are another example of pre-approved solutions. But with UiPath, we have to prove that it's a secure process. Simply put, a stronger collaboration between Microsoft and UiPath in a lot of areas would be helpful because it would ease the development process for us.

Another example is with the Automation Hub. At this time, Automation Hub does not allow you a direct login process or single sign-on option using Azure Active Directory. This means that you're limited to going through either Gmail or something else. This is true for the on-premises solution, not the cloud one. Although we had decided to purchase the Automation Hub license, this lack of functionality held things up because we did not want to manually go in to update all of the new users again and again. We wanted the information to be picked directly from Active Directory whenever a user wanted to sign up for it.

I have been using UiPath Attended Automation for approximately three and a half years.

In the past, stability has been great. However, more recently I have been facing some issues, and I'm hoping for some resolution. For example, we recently upgraded to the new orchestrator in Studio, and we had to upgrade a few packages also, In particular, the UiPath automation packages.

Some of our GUI activities, which are not fully backward compatible, have been facing some issues. Consequently, some of our bots have been impacted. We have already raised the issue and we are in discussion to find a resolution. This was the first time we actually faced an issue in terms of reliability with UiPath.

Our past experience has been very good, and I cannot say that we have any complaints regarding the reliability of UiPath solutions.

Scalability-wise, it is very good. It is easily scalable and we have a lot of options for expanding and configuring as per our requirements. It is also customizable.

We have a team of between 20 and 30 people, which includes approximately 10 developers, 5 team leads, two architects, two production managers, and one overall manager. We have some contractual workers, as well.

We have approximately 35 automations that are in production right now. From a process perspective, we have pretty much worked on all verticals including finance, healthcare, internal IT processes that needed automation, and more. An example is ServiceNow, where jobs like creating user accounts, deploying new machines, and other administrative tasks have also been automated. HR processes, including onboarding, have been automated.

It is a very large organization, and there are lots of processes, so I expect that our usage will grow.

The technical support is excellent in our experience. Whenever we have had a problem, they've always been there to support us and help us with the problem. I don't have any complaints, as they've always made the effort. Even if things have taken longer than we had hoped or expected, they've always come back with the best resolution they can offer.

I have worked with Blue Prism and in my experience, UiPath does a much better job, both in terms of dev and listening to the community. For example, Blue Prism is a very closed community and very limited. They have improved, I would say, based on the success of UiPath, but it's not very open-source or open-natured.

The biggest advantage that I have noticed is with Citrix-based automations or remote desktop automations. There are cases where Blue Prism did not work, but UiPath was very good. I did not have to spend too much time with UiPath before it worked perfectly. The reliability was also great.

More importantly, UiPath listens to the customers as well as the developer community, and in turn, they implement features that make their lives easier. They constantly reach out for feedback and it's a good process because it helps to know that the customer is happy. If I am speaking about myself, I'm happy that if I have a need, or I'm facing some challenges, I put it in the pipeline for UiPath and within six months, I will see that feature live in production.

We started with a disaster recovery scenario, where we have one live production orchestrator, as well as one backup orchestrator and a load balancer installed. This is a high availability disaster recovery (HADR) configuration, where all of our live bots are on the main orchestrator. In the case that the live orchestrator goes down, we have the backup orchestrator kick in.

The overall deployment and installation process was simple. However, we did face some issues with the Redis part. Configuring Redis was one of our pain points, and we reached out to UiPath about it.

Although it was resolved, it took a lot of time and effort, from our end as well. That was the only experience that stood out as a problem for us. But overall, it was a smooth process.

It took about a week to set everything up, although we had constraints from our own internal infrastructure team. The delay was not related to UiPath issues.

The licensing is close to optimum; however, there is room for improvement in both the cost and flexibility of the licenses. It isn't the best pricing in the market but it's pretty close.

For developing our attended automation, we began by coding the bot to our requirements, and then made modifications to it for attended automation.

My advice for anybody who is considering UiPath is to be sure of what your needs are regarding an RPA product. If you're looking for something very small-scale, very easy, then there are a lot of options. But if you're looking for a long-term, feature-rich solution, which has access to third-party integrations, then choose UiPath.

You will require a development team, at least to some level. UiPath is now simpler with the Studio X products, but in the past, it was a bit more challenging to dive deep into UiPath directly. It required some training but now, things have definitely improved.

One of the major lessons that I have learned from using UiPath is to make sure that everything is documented well. There is a lot that needs to be tested before bots are put into production because a lot of things that work on your local machine may not work on another. It can vary from machine to machine and where something works on one, a change in environment for another may cause it to fail. This means that you should change from machine to machine during the testing phase.

Overall, I feel as if now UiPath is on the right path with its competitors. It is a very good long-term solution.

I would rate UiPath a nine out of ten.

We use it with ServiceNow for maintaining tickets. Our task works to automate some scenarios such as software updates. In that scenario, there are some repeated steps. We use UiPath with Python scripting to automate those repetitive steps.

One of our use cases is for our insurance team where we have built a prototype which has helped the insurance team cut pricing. That is one of the automations that has made a difference.

Also, the fact that this is a SaaS solution means we are able to innovate much faster when it comes to automation. We have been able to complete use cases in as little as one month. There can be problems with the on-premises version because there are certain restrictions for accessing that database. But because this is on the cloud, we can access the data from anywhere in the world. That is very beneficial.

UiPath has also helped to reduce the amount of maintenance work related to our automation operations. It has a feature to keep the different automatic tasks monitored. That monitoring helps us if there's any problem in an automation. We get notification that there is a problem. If we don't know about those problems then, after some time, maintenance on them will be harder. It does help us to maintain things.

Before, we were using the on-premises service for our automation activity. By using UiPath Automation Cloud, we don't need to go anywhere. There is a single tool where we can keep track of the maintenance. Doing so with the on-prem solution was much more time consuming and slow. With UiPath it's so much faster so it helps us cut costs.

And in terms of overall cost savings, before we implemented one of our automations there were around 100 people taking care of the task. Using UiPath, we have automated that task and we have saved the fees of 100 people.

The speed is much better because we're doing it on the cloud. With other solutions there were network problems, but in UiPath I have found that network connectivity is much stronger when transferring data from the back end to the front end. It is much faster.

The Portal for enabling business users to trigger jobs with business input and for monitoring those jobs is great.

There is also the granular, role-based access control and management which is very important in our organization because we have different roles. Our manager has a much higher role, so that if there are some changes in an automated step, there are permissions from that higher authority. Otherwise, low-level employees could make changes without informing the higher levels and there could be a lot of conflicts. This way, we don't allow the lower-level employee to make any changes without proper permission from the higher authority.

The solution's single sign-on is also important because without it, a user ID and password could be compromised by a third-party or hacker. Single sign-on gives us another level of security when logging in to UiPath. It's very important and a good security feature.

UiPath also continues to add services to the Portal. There are proper updates that come out monthly or quarterly. They update different features or any problems with features, so the updates are very useful for us. It's very important that all the services are managed from the same place because no matter where a team is, if there is a glitch and we raise a question with customer support, and they do some fixing, that fix is available for all the users who are using UiPath. It comes from the centralized location, which is a very good thing. It is available for all our users around the world.

They should include new machine learning and AI algorithms for better forecasting and analytics.

I've been using UiPath Automation Cloud for two years.

It is very stable. In most software, we find that when we increase the data size, there is some kind of decrease in network connectivity, a delay or lag. But UiPath is very stable because they release updates very frequently.

We use it for day-to-day purposes. The tools are working on different jobs, daily. We have plans to automate more scenarios and we are working on a PoC for them. If they go well they will be implemented in UiPath as well.

Their support is very proactive. When we reach out to them, they fix our problem within a day. We can also use the Portal to have a chat about any issues that come up. Customer support is good and the community support is also great.

The fact that we don't have to worry about future installations and upgrades of Orchestrator, was important in our decision to go with UiPath, because those things are already built in. We don't need to worry about the infrastructure part. It is maintained by the UiPath team. They also have better community support to help us if we face any problems. That is one of the great things about UiPath.

The initial setup was very easy. The vendor was very active and the community is very active so there was no delay in communication. It was very straightforward.

We started UiPath as a desktop application and then we slowly moved to the cloud.

And in terms of the setup costs of our automation operations, UiPath doesn't have a lot of dependencies, so it is quick. We don't need to contact another party to maintain things because the UiPath community helps us with every aspect. It works. 

The pricing is good compared to other software. Based on the features that UiPath is providing, and the community support, the price is reasonable.

I have used different tools like Blue Prism and Automation Anywhere. When comparing all three, when it comes to cost, UiPath is great. It is also easy to use. Anyone can learn to use it within a couple of weeks. It is very useful and user-friendly.

The user interface and the usability of the other solutions is not as user-friendly. We also found some glitches in those solutions, things like network delays.

We haven't found any problems with UiPath. It is working great. It's a great tool. I would suggest that everyone go with a UiPath because it has helped us a lot.

We are using attended automation. I help drive a lot of products in UiPath. Now, we are using their data process mining and document understanding features. We are creating forms, then putting data on the forms, so our attended bots will work.

We use UiPath to resolve customer complaints by creating buttons that link to back-end integrations.

Employees can see information very quickly, reducing a lot of complications.

Uipth gives us as good speed and accuracy to improve all the bot la performance.

I like the document understanding feature. It gives us more accuracy. 

The AI and machine learning features are very useful for us.

UI Targets enabled us to quickly build automations within multiple applications, even without the right connectors. For example, we can drag and drop Outlook activities.

We use UiPath selector technology is a wonderful feature, especially compared to other RPA tools.

From mobile applications, we use Orchestrator where we can monitor processes and share them. 

Need more AI and Machine learning build technology and integration of 3rd party applications. Need some improvements in orchestrator

We have been using it for around two years.

5,000 people are using UiPath.

Any queries that we have, we can go onto their forums. If there are issues, we can contact their support and they will resolve them.

We have used Automation Anywhere, which is complex to understand. 

The initial deployment was not complex.

I will rate the level of expertise is 9(out of ten)

The attended automation has saved us time.

The pricing is average; it is not too high nor too low.

Its speed is better than other RPA solutions. They release more updates, details, and features compared to their competitors. 

We can learn from UiPath Academy.

I would rate the solution as a nine (out of 10).

We're mainly focused on finance for the time being so we've used UiPath for invoice processing and e-billing reconciliation. It makes sure that all of our converting information matches within our client databases. We've done a couple of solutions that track budget spend for certain clients, making sure that if the budget overruns or comes close to overrunning, then someone gets notified. If we get a new client or if a new legal case is opened, automation can make sure that all that information is then uploaded into our database. 

We've done a couple of smaller automations for the legal teams. These have been fairly basic ones though. There were a couple that download files from an email for them, and then rename them with the correct naming conventions, and saves them into correct drives. 

Another use case is to remove outdated users or information from our databases in line with the GDPR system.

In a general sense, UiPath has helped with data lineage, understanding where a process starts, who it rests with, and where it ends. It has made the process that we have automated a little bit more clear of which parts of the process are necessary, which are the parts that hold up the whole process, and which are the ones that are needlessly complicated.

For starters, it just helps give a bit more of an understanding of our processes once they're automated. Secondly, it's changed the way that we approach problems. We're tied into contracts that we might necessarily not want to be, but because we rely on the solution, we don't have a choice. Whereas, because UiPath is so versatile, we can use that to fill in gaps to take over processes, which otherwise in the past, we thought that only one specific tool could do for us. Now, we feel like we'd be less reliant on these specific tools to do a specific job. 

Third, a lot of teams are starting to understand that things can be automated. Whether it's in finance, HR, or even the legal teams, we started speaking to all the different teams and now they're bringing work to us and they're getting an understanding of things that do need to be done by a person and which don't. People aren't just doing work for the sake of it now. If they think there isn't a point to something and it can be automated, they bring it to us and we automate it. So, it's changed the way that we look at processes and don't just hardheadedly get someone to do it for no reason.

It checks our invoice stage for one of the processes that we do for e-billing. Previously, there wasn't anyone to check the financial data that we have in our systems against our clients and our recipients, and making sure that it all matches up. That process wasn't done at all so a month or two months later, a client would come back to us and say, "Hang on, you billed a strong amount or you've put our billing address wrong" which is obviously a little embarrassing. These things went completely unobserved for months. The client had to chase us, complain, and tell us we needed to fix it. Whereas now, it's more of a proactive approach rather than waiting for clients to come to us and tell us that we've done something wrong. We actually have the automation that can check and then validate those mistakes before they're even a problem and before they're spotted by anyone.

We're still in the early stages but we are starting to reach the point where UiPath is speeding up the cost of our digital transformation.

The digital transformation has made a couple of the lawyers' jobs easier by getting rid of the admin staff. It's freed up time and it makes things easier for everyone.

UiPath has definitely reduced our processing times as well. It really depends on the process but it has sped up. 

It has also decreased our error rates. At the moment we're looking to purchase an orchestration platform. At that point, we'll be able to collect more information about exact numbers and we'll actually have the analytics. 

The ability to use APIs within UiPath is really helpful. The web scraping is really great. It's so easy to use, it's very intuitive, and it's usually pretty consistent. When web pages change you need to update it, but it makes it quick. If you need to do another quick process, it's really easy to get it quickly and set something up. I can just scrape data from a website and save it somewhere.

The ease of building automation depends. UiPath makes things that are fairly simple but looks a little bit tricky in another language really easy. But if you're trying to do something really complicated, then sometimes it can be a little bit more tricky. It depends, sometimes it's really simple for fairly basic automations, I think it's fantastic. But when you want to try and get into the nitty-gritty and try and write your own code and then stick in there, it can sometimes be a bit difficult to use.

The documentation can be a little bit lacking. I think they improved it a little bit last month. Last time I checked, it seemed like they spent a bit of time trying to improve it. Sometimes some of the processes are nicely documented. UiPath offers training, which they provide on their website. They teach you how to use it, but for some processes, it just seems like the documentation isn't really there. It makes it a little bit difficult when you're using a specific process from the first time. 

If you're trying to invoke a method in UiPath, if you're trying to write a C# in there directly,  or if you need to do something which can't really be done in UiPath, but it can be done in C# or Python or something else, sometimes it's not that intuitive. It can be a little bit more complicated than it needs to be. I think that integration with other languages could be a little bit better.

We have been using UiPath permanently for around eight months, but we've been using it in-house for about a year before that.

UiPath itself is very stable because it interacts with so many different applications. I noticed in the past, at times, when using it with browsers, for example, using it with Google Chrome or Firefox, occasionally Chrome or Firefox will update and UiPath can take sometimes a week or two to update with it. For that week, you're able to use any solution that involves Google Chrome or Firefox, because it's waiting for that update. I've seen that happen with a couple of different applications, not as much recently. UiPath itself is very stable because it can interact with anything. If anything is updated and UiPath doesn't have time to update drivers to match that, sometimes you can get left a little bit stuck.

It's not really easy when you're using orchestrator to scale up and create a server, add a new bot, get a new license, and get it running. 

At the moment, it's just me using UiPath. I'm a developer and the architect for the solution as well. But we're planning to expand the team next year. 

We have a couple of processes that are running constantly, so I think we're using it as much as we can, and as much as our licenses allow. We're at a point now where we need an orchestrator to keep track and run everything at the same time. We're in the process now of purchasing that. I'll see where we're moving to, to expand quite far beyond that after we've got it. We're just at the point of ramping up.

I've sent a couple of requests to support when we needed licenses and when we changed to a different computer or a different user, and they got back to us really quickly and solved it within a day or so. I've been pretty happy with UiPath so far. I think every time I've sent a request to them, it's been resolved pretty quickly, and even if they couldn't resolve it super quick, the response times are usually within 24 hours or so, which is really good. I can't remember a time where we've been stuck in the dark with them.

I've used Automation Anywhere, but I haven't really used it within my work.

The initial setup was pretty straightforward. I implemented UiPath for a couple of years before I came to my current company. It was quite easy, but even the first time it's always been quite easy and quite simple to implement.

The initial setup only took a couple of days to get it all installed properly and cleared with IT. In terms of getting the first process up and running, it took about a week or two because we already had a couple of processes that were available. That's just a case of tweaking them, making sure they're all okay, and then just getting them set up and getting more packaged up.

Our initial strategy was mainly to focus on finance and to try and reduce the outsourced headcount with a couple of the finance teams. We outsource a lot of our work to a couple of other companies and we want to reduce the cost of that, so I automate it in-house. Our other strategy was to try and free up as much time for our lawyers as possible to make sure they weren't bogged down with work. It gives them more time to focus on the clients and work up better relationships with them.

We're still looking at the process that we've automated and seeing how much time and money we're saving with this crisis, but we don't have that information at the moment.

The pricing is pretty fair. Sometimes the pricing can be a little bit strange. There are different prices if it's for a specific user, a specific PC or if it's an attended bot or unattended bot. The price can be quite different, but I think when you talk to UiPath or when you look at the pricing sheets, there's not always a justification of why a certain license is more expensive than another. 

Licenses are more expensive than another but I wonder why there's such a big difference, why attended is four times more expensive, and that sort of thing. In terms of the orchestrator, I think it was a bit too much. It used to cost about 20,000 pounds a year. Now, they are ramping up costs. If you get an orchestrator but with just a few blocks, it's cheaper and then you can add up more parts to the orchestrator. So the cost goes up, which I think is better.

Definitely to try and get as many teams involved as possible to open up the conversation about RPA within the business. It works best when you've got lots of teams who have an understanding of RPA and how it works. They can come to you with their potential projects and you can filter through them and see which ones are going to be the most helpful.

It's hard if no one else in the business really knows RPA or how it works, or if there's a bit of a wall there. It's important to introduce RPA to as many different teams as possible and to encourage people to get involved, think about the processes that they do in it, and try to identify what can be helpful.

It's important to keep RPA close to the applications and the IT teams because if you're using RPA or UiPath you're going to need to be able to be speaking to your team who need permissions or admin privileges, or you need apps to be updated. It's important if you're going to put it in, have it as close to apps and development as possible.

It's a case of understanding that it's not a case of trying to get everything automated that you possibly can. The goal shouldn't just be to automate everything. If you've got a process and you can do 99% of it automated but you can't automate the last 1%, you can but it's going to be really fairly inefficient. Understand that it's fine for a process to have some bits that are automated, some of which are done by a person. The hybrid workforce, rather than going into the strategy of just automating everything is ideal. I've learned that trying to find that balance and getting that communication between the two is good.

I would rate UiPath a nine out of ten. 

We are in healthcare, and the supply chain can be a fragmented process, and now with the Pandemic quite fragile. In recent years, companies have been implementing leaner supply chains to reduce their costs. We found that our best approach to dealing with supply distributions was to create a partnership with a distributor who could provide us with a very large percentage of our day-to day-supplies. We have Central inventories in each of our hospitals; however, we use a stockless operation Monday-Friday. This means we fill supplies for our nursing units on the weekends, but during the week, the distributor is picking, packing, and shipping those supplies in a low unit of measure. Orders are placed electronically by noon daily, and start arriving by late evening. A 'back order' list is sent to us each workday in the late afternoon - too late to do anything with it. 

We did work with our distributor to develop a more customized spreadsheet that detailed each item, by hospital and delivery location. Each following day we would break the file down so that we could e-mail it to each area, to get feedback from them on critical needs.  This took our resources time to prepare and send the next morning. Staff getting the information didn't have much time to review and respond. In addition, we would update each PO line item with the revised 'due date', for back-ordered lines - this was a manual process.  This same resource would then use a tool to send each requestor a 'delayed delivery' e-mail notice.  The overall PO update and communication process took an additional 1-2 hours a day in staff resource time.

With the robot doing this work for us, the vendor sends a file to an address by a certain time. They send it in at about 3:30 PM every day. The robot now takes that file and works that file, which it has ready for us usually by 4:30 PM. Now, it still may be too late for us to work, but the first thing in the morning, we have the file, and the Bot has already sent out notifications to all the users of any backorders. First thing, when they walk in the morning, they know what their backorders are. They didn't know that until halfway through the day before. Now, they get the information first thing in the morning so they can react. Now, we are getting the information first thing and have the time to work with the manufacturers and distributors to come up with other products so that we might backfill or get a branch transfer.

Our end goal was to make sure that we had a daily tool that was 100 percent accurate and could be deployed across a broad spectrum of healthcare workers. Then, they could get information faster and more accurately with as much information to eliminate a lot of extra calls and communication. That is what we embarked on. We dissected our current process and looked at all its different triggers to see how we could turn this into an automated tool. We broke down our process and identified everything that we were doing, then UiPath helped us identify what we needed to modify. We worked that into a tool where a Bot could come along and process it every day, then deliver every afternoon. That was our end result, and it's been extremely successful. We started using the tool last December.

We combined some automation that we already had in this process into this tool to make it a whole automated process, rather than partially bringing it under. We have a vendor who delivers us a report daily of all their backorders because we use the main distributor, so they deliver us a backorder report. Therefore, we made sure that they aligned it in a way that the robot could read it. Then, we wanted to break that down in a way so each of our hospitals could see their section. So, we added some data to this tool which allowed the robot to see that record, and say, "This belongs here, and this belongs here."

Our staff have been reassigned to more value-added tasks. We haven't eliminated anyone because it's been very challenging for us to keep up with the COVID-19 issues. Now, we have resources who have the time to contact vendors, and find out, "When are we getting this? Can we get ourselves pushed to the top of the list?" They can actually be a voice on the other line, a human voice, who communicates. When you're sitting there doing all this other work, you don't have the opportunity to spend it on being a voice for the health system. So, we put people back on working back orders with other vendors and doing other things that needed to be done. We have not eliminated staff because we are using them in more productive ways, getting more work done.

Our staff can now do the things that we need them to do. It has given us the agility to pivot and move to other things, because we are not trapped in trying to work these files every day.

Our customers are getting information about 12 hours earlier, which makes it much faster to resolve back order concerns for their areas. If they have procedures, or certain kinds of cases coming up, and see that they have a back order, then they have much more time to react and try to address their shortage.

It provides information to people by automating that information in a much faster time.

Since we are getting information out to folks faster, they can spend the resource time needed to determine the best approach for what to replace it with, or if we need to work with a sales rep. It ensures that our staff have the best tools to do their job faster.

We have not seen it do OCR, and that would be helpful. Right now, the tool will not read a PDF file, and we can't use PDF files. We want it to able to take an image, then take that image and put the particular field out in the right spot in a table. We have not seen it where you can scan a document in, then it reads fields and places those in a table.

We began our journey last Fall - 2019 

It is very stable. Once we got all the kinks worked out, there hasn't been any maintenance. 

We had a little problem with getting it to run at night. We moved it off of one platform and put it on another one, which fixed that problem. These are things that we encountered early on that went away as we figured out how to resolve them. Most of those changes that we made were internal to our process and caused by some slow responses within our Citrix environment. Once we resolve those, we have not had issues with the tool itself.

I have one person in IT doing deployment and maintenance. We also have a second person under contract if we need support.

The solution is scalable. 

The robot processes the file in an unattended mode, then sends out an email with a link to its output file. From there, all the users, and there are probably about 20, get this file and react to it. They review it from their perspective because there are many hospitals involved. Each one of them has their own tab because the robot creates a tab for each. This makes it easy for them to go right to what they need. There are a lot of folks reviewing the results of what the robot has produced.

I have not used their technical support.

We were passively looking at some tools to automate some of our procurement processes. We are highly automated in our department, but we are always looking at ways to take the things that are not already automated, get into those, and see what parts of those we can streamline.

We met with UiPath last Fall. At that time, we went through a company by the name of Speridian, UiPath is a partner with them. We came to the conclusion that we had a manual process where the right components could be automated. Therefore, we made that our focus and started answering all the questions around the process to ensure that we had everything necessary for a robot to be able to answer the questions and keep moving the process forward.

The initial setup was very straightforward. We outlined what we do and what our end result needed to be. They asked us some questions, then sat down with our resources and walked them through it (or did it through Webex). I don't think there was ever any confusion on what was being discussed.

We didn't spend that much time on the process. Overall, as far as our work, the deployment was 10 to 12 hours, if you look at the meetings and such. Most of the time was spent on their side, because they had to go back and do all the development. So, I thought it was very painless.

We worked with the UiPath team and Speridian to ensure that the bot would know how to handle each aspect of the data and where apply it. As we tested it, we saw that we needed to go back and reconfigure this or this isn't how this is handled. We were kind of working through the things we forgot until we got to the point where, "Yes, this is it. We can do this every day." 

We had the robot tied into an automated tool that we were already using to send notices out. They were able to pull up that tool and have these automated components to all this stuff that we had a manual person sitting there doing every day. She was sitting there taking this data and sending it out, and now the robot was like, "I got the data. I'll send it out." So, we just ran it through the whole process. However, it does take having resources who can ask the right questions. What I found with this team was they were good in actually asking the right questions and helping us with what the robot would need in order to make decisions. Because that's what the robot is doing, it is automatically looking at a value, and saying, "I do this. I have that." 

We learned with it: How we need to respond and how we need to give the robot the feedback. It was quite an interesting process for us. Although you're always thinking you can automate so many things, there are components that you do need a person's brain to figure out. We found those pieces in this tool. We found some areas where, "Here's the exception." So, it even writes off the exceptions for us. While I do still need to have a person looking at exceptions, rather than the 100 lines that they used to have to look at, now they look at two, three, or four lines, then make decisions on those.

They gave us the opportunity to create a tool which would automate as much as possible, then provide us the data that we needed to act on. It has basically filtered out all the things that we didn't need to deal with. It has taken care of those, leaving us with everything that a human being needs to respond to.

I felt very comfortable with the UiPath person who was doing the programming, though I never really met him. I was very impressed. We talked on the phone a time or two, but they just seemed like they got it. They understood. It didn't take a long time for them to figure out what it was we wanted to do. They were able to tell us, "This is what we're going to need. Can you get it?" So, they were easy to work with. They also acted quickly. I thought the whole process of developing everything that we did went very quickly. 

They were able to link into our tools. They made suggestions to us, "Well, these are exceptions. We can put these here. We can do this. We can give you all this." They were providing us with ideas on how we could even expand on this. I found that to be very helpful. I really thought that they did it very quickly. They did not take long to understand what we were trying to do before getting in and really learning the impact. When we needed a change, the changes have come very quickly. 

It has gone so well that we will be doing a few more enhancements. Now that we've worked with the tool for a while, and know that the ability of UiPath and what they can do, we can enhance it even further.

We are doing things at a much earlier time in the day. The robot compressed the time it takes. We are getting our users' information earlier in the day. Now, it may take five to 10 minutes, where processes used to take half an hour or 45 minutes to go through everything. 

With COVID-19, so many supplies have been impacted. Our line items expanded and grew, so it would have been very difficult management manually. Thankfully, we had this process in place last December. It really came to our aid in March, April, and throughout this year, because it has streamlined the process. It has given everybody more time to pivot and make decisions.

The UiPath tool takes redundant processes away, and says, "Let us handle those, then you do all those creative things." It has given us back a lot of staff resources that were being used up by mundane, redundant processes. That's how it worked in our world. In other areas, anytime you fill out a form or answer a question, a robot can post that to a table. There are all kinds of things it can do. However, for us, it took these manual processes that we were doing day in, day out without a lot of thought and gave us that time back to be more thoughtful of what it is we need to be doing to be more thoughtful of what it is we need to be doing, in order to ensure that our health system has the products that it needs to support the community. In my mind, that is what it is about: Giving back your resources to use them in the way they were intended and using a robotic tool to do those things that you can eliminate, like mundane, redundant processes.

Start with processes that happen over and over every day. Something that you have to do, like data entry, whatever it is. Peel back the onion, then look and see how you can automate some of that through a tool. You have to look at what your processes are and understand how those are getting done today. Maybe even share that information with somebody outside your area, because people from the outside might say, "Well, why don't you do it this way?" Because you've lived it so long, you don't even know why you wouldn't nor do you know the questions to ask. Therefore, look at your base processes that you're doing day in, day out and see how you might be able to automate any aspect of those that doesn't require human thinking. I'm sure you will uncover many things.

It is a learning process for everyone, but I thought it was a very fast track learning. Sometimes, you think, "Well, this is going to take six months," and it didn't. In a very short time, we were seeing samples of what we were going to get. Therefore, I was very impressed with the amount of resource time that it took. It was beyond what I expected.

Some tools we are working on will reduce the purchase order build, but we haven't implemented that yet. That's a whole other project that we're working on with them, and that piece goes into procurement.

It is very doable. I was probably fairly skeptical, but once we started thinking about it, it became very clear that this would be just a slam dunk. You have to open up your mind to it, but it was something that when they said, "Well, we want to use some robotics." The fear is you're going to take my staff away. There are some cases of that, but it is not so bad. I don't have to worry about the robot taking days off, getting sick, having a mother in the hospital and needing to be with them. I don't have to pay it scale. I just don't have to do any of those things. Now, the robot can't automatically think outside the box, but sometimes it can depending on the questions I ask it. 

Everybody just needs to take a breath step back, and say, "Yeah, maybe it can replace this." However, that doesn't mean we won't use this resource in another way.

I would rate this solution a 10 out of 10. I'm not the type of person who just gives a rating of 10 all the time, but this solution has just been a phenomenal tool for us.

Originally, we were using UiPath to draft documents and send emails on mass to where we had large communication exercises. We used a robot instead of a small army of paralegals to generate the documentation and draft up the emails where we had to communicate with 2,000 to 3,000 people. It was a little bit more involved than just doing a standard mail merge, but we were able to use UiPath to create a number of documents and email it to an individual customer, all through a central email address.

Fast forward to where we are now, we have a few of these things focusing in on what we call post-completion activity, like the things you do after you sign a contract. So, it may be you're uploading it to the client's contract management system, applying stamps, or registering the contracts in an official register. The robot is able to do that for us post-completion. Those are our primary use cases at the moment. We're looking at more data integrity type stuff, like comparing our internal data sources against public record.

The ability to displace some activity that was traditionally on our paralegal team has improved my organization. We're an outsourced managed legal services provider. We're primarily a people-based business and UiPath displaces some activity off those paralegals and brings in automation. For me, it becomes an additional type of resource. The long and short of it is that we are able to move work that was traditionally done by people and would be charged at a rate, off to automation where we can bring the costs down. It enables us to reduce our running costs of our clients. A single bot running post-completion has saved as two FTEs.

UiPath has helped to speed up case resolutions in a couple of ways. It's focused on doing particular jobs, so it achieves the job faster. People don't need to complete an entire task end to end. They can stop at a certain point and the robot takes over. That allows a person to get through more work. Also, the fact that the robots are able to do this stuff overnight 24/7, means that we have more capacity to do stuff.

It gives us the ability to respond to clients. It gives us an option in how we're going to automate work for clients. It's hard to say if it has reduced the cost of our digital transformation because we deal with all the people. I suspect it hasn't done it internally, but suspect that has made some things cheaper for our clients. It enables us to deliver digital services cheaper for our clients. 

UiPath had an effect on our legal staff. It takes work that people don't want to do at the moment, having to download the document, take some details off the top and the bottom of the document, apply a stamp, and then re-upload, it's not what our paralegals and new trainees want to be doing on a day-to-day basis. So we are able to shift activity nobody enjoys onto a robot and let them focus on the stuff they've been trained to do.

In terms of how much it has reduced the processing times, the task itself still takes as long but we've got a robot doing it instead of a human. I don't think that the impact isn't that dramatic on-site processing times. At the moment, humans are only involved in 80% of the transaction and 20% has been held by robots.

These automations have decreased errors but it's hard to quantify by how much. They've inserted 20,000 transactions a year. I have no doubt that the error rates improved. It's just a hard thing to quantify.

The most valuable aspect of UiPath is the fact that it's a low-code platform. Being able to use a low-code platform really lowers the barrier entry of introducing automation. Normally, you fill in a request to go to IT to get a development resource allocated, and then you spend six months trying to do a project. Because UiPath is a bit of a platform, you can quickly, within weeks, start to knock off automation and get it checked and then successfully deployed. The low-code development environment is key for us.

Now that we're scaling up and taking advantage of Cloud stuff, it's become a lot easier to use. When we started our journey, we just bought a couple of bots and had them sit around on machines. It was a bit chaotic and we thought that if we take advantage of their wider platform, the orchestrator environment, it would make life a lot easier because we have all the monitoring and management. We have access to that in one platform rather than having to watch the individual robots, which is where we started.

We're going to use the solution's AI-enhanced document understanding feature. It's something we're looking at to help us with invoices and incoming bills that come in. It's on the backlog. We haven't got to it yet.

UiPath enables me to free up capacity for people to work on new work because they are involved, they're less accessible. At the moment, the majority of our staff is focused towards the end time making sure that things are filed correctly. It's more about focusing resources rather than being more responsive.

As things become more and more data-heavy and accessing other people's products and managing things, like obtaining the data through APIs, it feels like there could be a lot more for them to do, to make interacting with data or manipulating simple things like text strings. You need quite a strong development background or a reasonable level of understanding to achieve that. I think that could be made a little bit more achievable.

Three years ago we started using UiPath relatively small and we are looking to scale up significantly this year. Originally we started on-prem and as we're scaling up, we're going to move towards the cloud instance.

So far the stability has been good. With all of the low code platforms, it's actually more of a problem of what we've developed and deployed. It's how well we make our own software so that the platform will provide. It seems to stand up very, very well. I have not really had an issue. Anytime we have encountered a bug or whatnot, it's something we've introduced to ourselves, but thankfully there's a strong community where we can post questions and queries to get a response within a couple of hours.

I don't see scalability as being too much of a challenge. If we need more capacity on the robots, we're able to buy more licenses and additional VMs on the machine. If we need to expand or scale, it's just about deploying more machines. I don't feel it's that complicated. I suspect there are some constraints on how you build your applications, but that's more of an internal decision rather than UiPath's.

There are three people who are responsible for how to put a source of business analysis as well as development. Their role is to work with SMEs or people within our business units to understand a customer's process, get them deployed, and work with them to do it. The stuff we've taken on tends to be the easier, quick wins. We have three internal developers who were able to break down processes. We're a large organization. We have a large IT function that helped us with virtual machines and data centers, etc. We're not directly involved with them.

It's very easy to build an automation and just let it run. One of the key lessons we learned is the fact that you have to keep an eye on these things and that things change in the environment. Passwords run out and expire, folders may move as people move things around the network and a robot is just as susceptible to everything else that our user is. In terms of when you're designing any solutions, you have to pay a little extra attention to things that may cause you problems in six months' time. The simple fact that a password that you were using has been reset or is expired or something else, could cause the robot to failover. While the robot can tell you it's got a problem, you still have maintenance effort to keep an eye on. There is a maintenance commitment that you need for everything that is put on it. You need to spend a bit of extra time detailing exactly how you are going to respond to those things. Just because it's easy to deploy stuff, it doesn't do away with the fact that you have to keep an eye on it.

There are three analysts who are respondents to book fixes, etc. We have people in the business who we work with to automate these processes. They take a level of responsibility and keeping an eye on anything we try to automate. They're the first line of support. If anything's going wrong or something they can keep an eye on it and then if it is a technical book fix or something that needs to be resolved, that's then escalated to one of those three developers.

I only had one issue which was to do with the proxy setting when deploying some of the software. I raised the ticket on the website, got a response within half a day and it explained what I needed to do to fix it. That's my only experience of having to deal with them. I raised a ticket, I got the answer, and it worked. My experience so far has been fairly good.

We decided to use UiPath three years ago when RPA was starting to become a bit of a buzzword. We took a look at it and realized that it would be a very, very good solution for the right project by allowing us to automate mass activity all at once. One of those projects came around and we had to communicate it to a large audience. The process once agreed upon and nailed down could be very heavily scripted. We looked at a way that we would communicate it to the 30,000 people, all with documents that are pretty much the same but with a slight variation. We knew we wanted to try an RPA solution. UiPath was a very strong contender in those days and it was easy to access. That's why we ended up with it. We're able to achieve something with a single bot. All of those things make the software easy to test out. And then from there, you're able to make a decision.

The initial setup was really straightforward. In such a large law firm that has high data security obligations, we set these things up, appoint the orchestrator, and it just works. I have not encountered too many problems. 

It doesn't feel like a heavyweight ERP system or some larger workflow tool. These things are deployed onto a desktop and they speak to a server. It's not heavy. It doesn't feel like a piece of software with a heavy footprint.

The deployment took a week. It took us longer to end-to-end to get the invoice approved.

We've taken advantage of the architecture. Our IT team set some ground rules about where the virtual machines need to be hosted and deployed, but it's not that heavyweight. We increase some standards with IT and then install the software on those machines. We're using the Cloud version so there's not a lot to worry about.

We were able to do the deployment internally. 

Some of our ROI is quite dramatic. We have to email lots of stuff out to different people and our projector will require this to have a team of six or seven staff working solidly for a couple of weeks. The robot was able to get it done after a couple of weeks of configuration. This thing was able to pay for itself in a matter of hours once it was done. One of our post-completion robots took a week or two to develop and get stable enough to deploy. It's able to offset seven or eight hours a day. If we target the use cases correctly, we are able to get a return on the automation we deploy.

Take advantage of the Cloud-based implementation. You'll have to handle the Orchestrator licensing costs. It's obviously different for every organization. It's beneficial to get away from the on-premise installation. Also make sure that your business case justifies whatever the license cost is for an unattended or attended bot. 

Show your business case and that the automation will help you to exceed the license cost. You want to look at things that are going to give you a return on investment in about six months' time. Take advantage of the Cloud-hosted version so as not to pay the cost for Orchestrator. Then for your bots, make sure you will see a six months ROI in terms of how much automation you've gotten and how much you can get the robot to get done.

We also looked at BluePrism and Automation Anywhere. We took a quick look over the top three solutions at the time. UiPath seemed to be one of the leaders in the area.

We partnered with an organization to help us deliver it. We got some consultants in and sorted out what they were comfortable with using and what they recommended. For us, it was the size of the platform. We were looking at Automation Anywhere or BluePrism. It just felt like it would be a bigger project to implement when in reality all we wanted was one robot to do one job for us at the start of the project. It was more about the barriers of entry to getting started.

I would rate UiPath an eight out of ten. It feels like nothing deserves a 10, and I highly recommend every organization has a handle on RPA. There are still a huge amount of features we're still yet to explore.

We are a UiPath customer, working with them to develop some products. It is a bit of a mixed thing where we are developing some products with them from scratch, but they are acting as the provider. We develop things, and if they're useful for others, then others can use them.

We are doing some pretty bespoke things to help us develop some solutions, but also help them develop their UI solutions in the legal area. We are working on a few things with UiPath to develop some search robots, some solutions to automatize subcontracts, and some timekeeping entries. These are several things that we are doing right now.

We are doing three things with them:

1. A robot to help us with software for time management, automating time entries. 
2. A robot to help us with filling in our engagement letters (contracts). 
3. A robot to help us with various public searches, i.e., the automation of searches of the public record.

We are adjusting robots from similar things that they do. The robots are not yet in production. 

The most valuable feature is its ability to save time with a task. In general, it improves accuracy as well.

UiPath's ease of use for automating our company's processes is a five out of five. We have found it very easy to talk to them, identifying what can be done along with the potential use cases. They have been very good at guiding us through what is realistic at this point, how their robots could help us save time and improve accuracy, and how our users can engage with their robots, e.g., ensuring that users engage with the robots and use their product. 

When we started to talk about practical implementation, their team was extremely switched onto identifying and fitting their product to our needs. They explained to us how we can use their products, what can be done to adapt their product, and what may happen sometime in the future, not necessarily now. I found this very helpful and straightforward.

What we have in mind in terms of what the robots could do for us is significantly more than what UiPath does now, but it takes more work. From my perspective, there is just a wide scope of implementation that goes beyond what we're starting right now. That is essentially the improvement. While I have nothing negative to say about our experience with them so far, I think we can work to develop more complex products with them. They are already working to develop something for our use cases, but what I would like is if we could develop more things for more complex needs, e.g., where we start with simpler stuff, then we can add things to what we're doing now.

We are in the development phase.

It is too early. We are still in development.

During the development phase, there are five people involved in the development phase. The users will be about 100.

We have not used their support.

We were not previously using something in this area. 

We have been thinking about ways to streamline our activities using technology. It happens that we knew UiPath, so we started to engage with them about what they could do for us. We had something like 20 ideas that we could implement, then we just started the easier ones which were closer to the products that they have. As things go, we will see whether we expand to other things.

We have known UiPath quite well and for a long time. They are also the leaders in the field, so it was a very easy choice.

The initial setup was quite straightforward. We started to discuss potential solutions, then we met with parts of their team, developing that business area. After that, we met with the technical people designing the product. We had a couple of initial conversations and did some testing. It has been extremely simple and straightforward.

We are supposed to review some of their proposals and provide feedback. We are probably a week or two away from production.

UiPath could have probably implemented the solution in a couple of weeks. We had some delays on our side.

We did the initial setup ourselves.

It is important for whatever we implement that it's cost effective in a sense that the robots will replace some human time. If human time costs less than the robot, then that's not a good deal. Normally, human time will cost more than a robot, and that's what we're trying to displace: the human time. We want to replace it with a cheaper robot. 

We only looked at UiPath, because we know them quite well.

So far, the experience has been excellent. I would rate the solution 10 out of 10, but we haven't finished the implementation.

Look internally what your needs are. Try to identify what you could improve with software robots, ensuring these needs are clearly identified and the product is fit for purpose. Also, you should make sure there will be buy-in in the organization, so people will actually use the product.

We have developed a product for a court of arbitration. UiPath provides the automation engine behind it. Our product is a platform that is live online. It allows a party to provide some contract information, and the robot assembles a document and communicates with DocuSign, our signature provider. It then sends out a correspondence to the other party and manages the signature process for a bespoke contract for an arbitration agreement.

This is a service that we provide to the world, pro bono, as it were, to promote arbitration and the adoption of a particular arbitration clause. It's accessible to all. Parties can log in and it helps them to negotiate and conclude an arbitration agreement in a mediated fashion. The robot sends out email on behalf of a third-party, a court of arbitration, and it helps the parties get that agreement done.

It's about concluding an arbitration agreement before the dispute goes any further.

It helps us in providing added value to the clients and to the community at large. It's a marketing thing for us, in the widest possible sense, rather than something that we use in our practice.

But in terms of reducing the cost of digital transformation, if a person had to do what the robot does, it would probably be impossible. It would be impossibly costly. If one person had to handle the communication, instead of the robot, and try to negotiate each addendum, nobody would do it because it would take days or weeks for a lawyer to manage, and it would be prohibitive. Yet, all of a sudden, we have this service that is so cheap in many ways that it can even be provided for nominal user fees. It's quite dramatic.

I would also imagine that processing time is reduced by many orders of magnitude. As a professional, if I had to manage an addendum like that, it would take me weeks. And it takes about seven minutes or so, if all goes well.

What I have found interesting is that our product acts as a human would but it's not intrusive. It doesn't require any real integration or interface with one's own systems, in any meaningful way. Obviously, you need access, an account to log in, but it otherwise acts as a human, and that makes deployment quite smooth. It doesn't require you to change anything in your system. I found that very useful.

Regarding the ease of building automations, I'm not sure how it's done because I'm not a programmer myself, but it's great. Just looking at how fast they moved once we had the program settled in — it was quite fast. For this particular process, which is assembling a document, talking to DocuSign, sending out emails, and so on, the deployment of production was like "today." It was quite quick.

In terms of the ease of management of automations using UiPath, I don't dare poke into it, as a non-technical person, but it looks manageable. I have someone who does not do RPA normally, who doesn't do this type of programming at all, but that person knows where to look for errors and doesn't get lost. It's reasonably accessible.

I could use more standardized features, retail-style, things that I could use off-the-shelf. Right now, all this requires quite a bit of adaptation in bespoke work with UiPath, which they've done very well. But looking at it after having used it, I would get stuff that is prepackaged from them, if they were any.

We launched with UiPath in June.

The stability of the solution is okay. 

The downside of the upside, when I said that it works like a human, is that in some cases, if it interacts with a website that is changing, then it's like a human. You need to adapt it to the changing environment in which it works. That's an inevitable fact of life, that it interacts with other apps. It can also interact through APIs, but you want it to be very flexible, you want it to be an agent, like a human. The downside of that is that if something changes with a website, then of course, you have to change the robot and tweak it a little bit. But that's the only issue that has required our attention so far.

Our product is a public-facing instrument and we have had no problem with the number of users, so we have not seen any issues with scalability.

In terms of potentially increasing our use of UiPath, we're exploring a number of solutions actually, for practice management and actual lawyer work. These would be in-house solutions, rather than public-facing. We have a few ideas that we have run by them and we are waiting for feedback.

We've had no problem with the customer support. We were in direct contact with the whole team. They have always been quick to respond. I would rate them a 10 out of 10.

We would use regular Microsoft automation features. I would have a flag on a particular correspondence, or a particular rule for attachments. We would use little bits and bobs of automation that are available, but we did not have any bespoke solution.

We went with UiPath because they made themselves known in the sector and it was a question of the vision that they communicated. There was a modest vision of providing solutions to very discrete problems, not revolutionary solutions to everything. Rather, they focused on whatever helps in a particular organization. We liked that. It matched our understanding of legal tech as well. It needs to be supportive of whatever little bit of help you need, rather than providing you with an environment that engulfs you with everything. We liked that approach, and when we approached them they were very receptive.

The initial setup process was okay. I'm a non-technical person, but I was able to manage it. 

It took quite a bit to figure out what we wanted from it, the flow and the logic of it. After we agreed on that, on the concept, actual production took two or three days. Of course, somebody had already done a proof of concept, although that was not based on a final brief. We danced around and changed it a bit.

For maintenance, we have somebody in tech that we pop questions to, and our maintenance of the server is done in-house as well.

We have realized return on our investment. It was a joint project with UiPath so we had special arrangements in terms of licensing, but it was very well received in the market. It was very beneficial for us.

Our product is something that we launched in June, and the robot has been featured in general business publications, in the Kluwer Arbitration Blog, and the Resolver, which is the Chartered Institute of Arbitrators magazine, as well as the Romanian Arbitration Journal. Essentially, everybody knows about it. It is one of the most popular UiPath robots out there; the most featured and interviewed robot in the wild. We were quite pleased with the publicity.

My advice is to think about it very carefully and know exactly what everybody is doing every day in the office, the little bits and pieces. Really look at that seriously, because there are so many things that we do in a software environment that are very amenable to automation, and it saves a lot of time. Think very carefully about the particular needs of your office and look into it, because it can save you a lot of money.

It's clear that this is the future.

We use it to automate searches in public databases. We have lawyers who need to search for various companies. For example, we are searching insolvency files for a list of business partners, so we use the robot to perform the search and notify clients about its results. Thus, it helps us with our work in searching public registries.

We have the Studio license and attended robots.

It enables us to provide new services, e.g., our use case is something that we could not have delivered manually. Now that we use the robot, it is something that we can offer to clients. Therefore, it has helped us expand our scope of services and offer to clients more competitive fees. We are now trying to get more clients.

If we were to do this manually, it would take us one day for 200 companies. Now, it takes about half an hour. So, it has reduced our time to process information. Before, we didn't offer these services on a mass scale. We just often did it for a couple of companies. Now, we can offer it on a larger scale.

One of the departments in our organization does use UiPath for compliance purposes: To send reminders to our clients. We have to ensure that clients are compliant when they submit financial statements. We use the robot to send them reminders to update the steps of compliance, i.e., if it's done. This is not my team, but another team who uses it for compliance purposes. It has increased their level of compliance because it's timely and there are no errors in the reminders.

We mostly value the fact that it easily interacts with existing systems. We don't have to go to a complex interface to access public information to send the emails, etc. This is the good part.

Its ease of management is okay. Our attended robots have some Excel files that we use to manage and configure the robots. It is quite straightforward.

It has helped relieve the legal staff of the burdensome task of searching on the public registry. For them, this has been a big improvement. It saves time and also the risk of human error has been reduced, because now the robot does the work. So, you don't get bored when you check 2,000 companies on the portal. The staff is overall more satisfied because they can do more value-added tasks than performing this search.

The pricing for Orchestrator and unattended robots could use improvement. If we plan to roll out and implement more robots, then perhaps lower costs on Orchestrator and unattended robots would make adoption even easier. 

For roughly a year and a half.

So far, the stability has been good. We haven't had any issues.

If you have an attended robot, then it is scalable to a certain extent, but this is because of the price tag. If you think through your use cases, then you can use the same license for multiple purposes. If we think of scalability in the sense of changing the process, then this is something that can be done, but it requires extra development time. So, it's rather scalable.

We have two lawyers using this robot. Their role is to monitor the robot and make sure that the robot works fine. For example, if there are any complaints from the clients, then they can respond.

We, in legal, are among the first to use this robot to my knowledge. Other than a couple of robots that I've mentioned in this review, I'm not aware of other robots.

The technical support is very good. They were very responsive. We had a question about the license and they replied very quickly.

We did not previously use another solution. We decided to implement an RPA solution because we wanted to streamline our processes. We also wanted to be able to offer and develop new services for our clients. For these particular use cases, using other technology solutions would have been more expensive and complicated to set up.

The initial setup was a bit complex. We are a very big company with a lot of IT centers. I think the complexity was on our side. The initial part of setting up the virtual machine and installing the licenses took roughly two months. After that, the development time was very short: one week.

Our experience, as administrators of the platform, is quite good. Once the robot is set up, it is very easy to see the results, reports, and if there are any errors. It is quite easy to use.

The robot that searches for insolvency cases was built in one week. After that, we have been testing it and making adjustments, but the construction and development time were very short.

It speeds up digital transformation because it's easy to implement and have it live. Therefore, it is something that we can use very easily to streamline our operations. 

I handled the project and managed the discussion with our IT. We had several infrastructure teams who set up the virtual machines and helped us install the licensing. We had a third-party developer who developed the robot. We also had an internal team who tested the implementation. I oversaw everything.

We were happy with the third-party developer.

Now, there are several providers/developers who can build UiPath robots quite easily and at affordable prices. So, in our case, it was quite a straightforward process of building the robot.

Our processing time was reduced to half an hour. Something that would have taken up the whole day (eight hours) was reduced to half an hour. This has freed up our legal staff’s time to focus on more important and strategic tasks.

What we have managed to do is to offer a completely new service. It is something that we did not offer on a regular basis or big scale. Using RPA, we can offer it to a larger scale with the reduced costs.

The pricing is okay, but I recommend to build a business case before going live. Ensure that you really use the license and building the robot makes sense. Try to think of multiple use cases, because one license can be used for several robots.

There are additional costs for using third-parties. We also have internal costs with the infrastructure and for the virtual machines where the robot operates.

The costs are quite affordable. It is a solution that makes sense from a business perspective.

We didn't do a very formal business review process.

I think the platform is very good.

Have a good consultant advise you on the processes of automations: How to build the use case and business case. You will need a bit of knowledge around RPA and business processes to be able to have a successful implementation. 

Have a stronger technical partner tool to help with developing the robot, making adjustments, testing, etc. Testing is very important. It is important that you allocate resources for testing.

Robots can do things in a different manner than we can and more efficiently. We have to be creative and think of processes, even if only part of them are repetitive, that we can automate and a human can work with the robot. Then, the overall the process is improved and our experience as humans is a lot better.

I would this solution a 10 out of 10 because they are very good at what they do. It's very important that you understand what the solution can do and its limitations. However, for this type of product, I think they are the best.

RPA - Novigo Automation Framework Solutions - Setup an Automation Factory Model.

Automation Focus has been Productivity, Quality, Cost, Process Optimization, and compliance.

Focused on delivering Process Automation for Oracle EBS ERP application for various departments including IT, Finance, Operations, Engineering, Sales .etc 

1. Manufacturing: Master data maintenance & monitoring Inventory transactions, BOM error fix & transfer, WIP issue & complacent
2. Finance: Financial closing, IC transaction, security & FA master & transactions, Master data, duplicate check, auto-CM creation & auto-payment, Customer Master, running letter, print errors & auto-receipts
3. Supply Chain: Sales order Integration with the portal, shipment, RMA, digital shipping & backorder, item cost update & inventory interface, procurement, receiving & monitoring
4. System Admin: Access provisioning, - Creating responsibility, Monitoring pending transaction & analyzer.

RPA Automation has accelerated heavily within the organization. 

It started with task automation and ended up with process automation.

• Increased Operational excellence - With multiple FTE savings every month.
• Lowered operational cost with a minimum saving of 780+ Man hours every month.
• Overall $1 million annual savings through improved process efficiency.
• Increased Shipping Order execution velocity by 2x times -At least 10,000 orders in every 4 days.
• Amplified shipping process efficiency and employee productivity by 100% - with one click execution.
• ABCDi (AnyBody Can Do it) technique enables Zero dependencies on SME requirement to perform the task and Zero dollars spend on training the Shipping operators.
• Prevents human error, increases data accuracy, standardization, and quality of data for the shipping process.
• Excellent ROI with investment cost recovered in 1.25 months timeline and an Annualized ROI for 5 years is 68.50%
• Built from LTI Novigo Automation Framework, it provides the agility and speed required to customize and deploy the solution quickly.

• Attended Bots have been star cases as it totally removes dependencies of user literacy to know the application. 
• ABCDi (AnyBody Can Do it) technique enables Zero dependencies on SME requirement to perform the task and Zero dollars spend on training the Shipping operators.
• With Novigo Automation Framework, the implementation lifecycle is accelerated by about 25%-to-32%, while drastically reducing the implementation services cost. Identification of possible use cases along with efforts required, time involved, and cost savings can be easily envisioned by using NAF.

• RPA AI capabilities - UiPath is leading in this area.
• UiPath should focus more on recommendations of process automation based on ERP Applications like Oracle, SAP etc. They should also provide a list of possible RPA cases as per departments, processes and based on various industry domains. 
• More on RPA Governance features to be provided out of the box. 
• RPA Capabilities with IVR Channels to address voice commands will be a game changer for Customer call center cases.                                                                               

We have been using UiPath for two years.

Excellent in stability. 

Easily scalable in a few minutes.

No.

UiPath Cloud Orchestrator setup is pretty must straightforward, we manage to do a complete setup in a matter of a few hours time.

We deployed it in-house - SI - LTI.

>30% ROI  - we recovery of overall investments recovered in seven months' time.

UiPath is very cost-effective.

Yes, we have evaluated all top RPA products like Automation Anywhere and Blue Prism.

I am using it for a project that we did for our client e.g HR automation in which we create, update, and delete the employee the database which includes master data management, active directory, and SNOW as the used environments for the solution.

UiPath helps our clients achieve their goals like with RPA. Now, with UiPath they get their work done within half of the time that it is done manually. They have more accuracy in their tasks and it has become easier to maintain. Before they reach the office they already have all the work done by the bot in their desk.

The tech support that UiPath provides to the licensed user it is really helpful. There were some scenarios when my issue was resolved within 24 hours. Also, I like the constant updates that UiPath provided to us.

As in my opinion, debugging needs more improvement. Also, if we get any other tool or technology which helps extract information from the scanned or handwritten document than that will be really helpful as a user and for our clients as well.

I have been using UiPath for two years.

We primarily assist clients in deploying UiPath within Finance/Accounting and Internal Audit but have also realized the benefits of deploying it within our accounting function to assist with expense reporting and invoice processing.

We have also successfully complemented our technology solutions practice, which deploys ERP systems such as Workday and Coupa, where we have built some specific automations to accelerate deployment and assist with normal processing.

We have been able to save several hours each month allowing our staff to focus on more value-added efforts. For just downloading expense reports, a staff accountant can save between four and five hours each month. A lot of the prep work needed to send out invoices to clients is now being completed through automation.  

The most valuable features are the flexibility of the tool, ease of use, and training. We spend more time documenting the process and exceptions, wherein the build component doesn't take too long. Our consultants have been able to go through the training videos and pick up the ability to build their own automations.  

I would like more incorporation of Artificial Intelligence (AI) features to allow for intelligent character recognition which can account for different formats and unstructured data. Specifically, the ability to not have to create templates for various formats to account for variation and rather intelligently extract key data regardless. There are some AI-like features in beta, but we are very interested in deploying now. 

We have been using UiPath over two years.

If built and deployed correctly, the solution is very stable.

The scalability is great! There are several use cases already and an endless possibility of areas where UiPath/RPA can be leveraged. 

I haven't had to interact with technical support, as of yet.

We did not use another solution prior to this one.

The initial setup is straightforward, both from interaction with systems and security. 

We deployed this solution in-house.

We have been able to avoid hiring more staff accountants, so more cost avoidance.

Plan for the future! Don't just focus on trying to buy a license to meet your current need, but look to have the right infrastructure in place to help you scale. The investment is relatively small compared to the potential in qualitative and quantitative benefits that can be achieved.

We do have past experience, but when it came to deploying in our internal operations team, we focused on UiPath. We have found UiPath to be the most flexible to deploy.

We are excited to see the new game-changing features with UiPath!

Our primary use of this solution, as a company, was to eliminate or at least simplify and reduce the number of boring, repetitive administrative tasks that take our precious time.

We are a business consulting company and lots of clients try to contact us on multiple channels that we are available on. Our company, in partnership with UiPath, implemented an unattended robot that saves our time and energy. We call it our colleague that works independently, full time and helps us without requiring emotional support.

As employees, we no longer have to waste a significant period of time each day by copying data from one part to another. Instead of that, we can focus on more important things like customer satisfaction, consulting our partners, delivering business plans, etc.

This product improved our employee satisfaction rate, improved the sales department performance in general, and created a gap in the marketing department that can be covered by more complex projects like website updates, social networking with customers, etc.

I found the UiPath Academy very valuable and it has helped us to understand the product we are working with. I attended the course and I am about to complete more courses so that I can benefit from this brilliant opportunity. It is free for everyone who is interested.

UiPath Community Forum and UI Connect are free and can be accessed by anyone as well. There, I could find all of the information that I needed. The most interesting part was accessing UiPath Studio, where you can try to improve your technical skills and try building a robot.

The platform that shows the reports and errors is not too transparent. I experienced it at my workplace when showing the reports, where the platform looks unfriendly and it is not very transparent, especially compared to the other features of the product.

The monitoring period should be shortened as soon as possible, as most companies won't have one to two months available to implement and test the RPA. People want results instantly when talking about an investment.

I would also like fewer errors, please.

I have been using UiPath for between four and five months in the company I work for.

Technical support has been responsive and helpful. 

This is my first experience with RPA software.

The initial setup was as transparent as it could be.

We implemented through a vendor team and they were pure experts.

This solution is worth the investment.

We did not evaluate other options before choosing UiPath.

We are a company that provides technical services and this is one of the solutions that we implement for our clients. One of our use cases is to help automate simple processes for banks.

In all of our processes, the time to complete them is still improving. We are always trying to minimize the time that each one takes. Our system automatically compares the performance between the robot processors and the manual processors.

UiPath is easy for the clients to use. We have an Excel file that contains the parameters and this is used to start their applications.

I would like to see some artificial intelligence for UiPath that would help us with OCR and other things like computer vision. AI would be helpful for us to implement those kinds of solutions.

We have been using UiPath for a year or two.

We have used the Community Edition and the Enterprise Edition, and we have not had any problems with stability.

Technical support for UiPath is great. When we look for something, we usually find it on their website. They also get back to us rapidly and provide responses to every request, even when we contact them by email.

Deploying a process that is simple or of medium complexity takes between one and two months.

This solution is not cheap but the price is worth it because by following the documentation and using the support, you get good robotic processes that are stable. Overall, we are satisfied with the pricing.

Overall, I would recommend UiPath. My advice for anybody who is considering this solution is to look at their website because it is very helpful and it can help them to make a decision about implementing it or not.

I would rate this solution an eight out of ten.

We have a system to create a multiple orders to perform automation testing. Here, UiPath helps us to create a bunch of orders without the hassle of creating a separate automation suite for this need.

When creating orders manually became a tough job for the user then it needed a benchmark for us to resolve this kind of situation to make teams more agile at work. This motivated us to find a solution to counter this problem in our organization. Definitely, it has helped to make us more agile. 

UiPath has helped us to achieve our goal as we are able to do what we intended to with automation. We are now dependent on UiPath to create the orders instead of having to do this manually. Earlier, this used to happen in a very traditional way and it was time-consuming, but UiPath has helped to perform this task with lightning speed. Now, we have more focus on implementing other things smoothly. 

Scraping data from the application using OCR and other text validation features is amazing in UiPath. These have helped us to create a reliable solution for our needs.

UiPath support needs to be a bit quicker than it is currently. They need to be very quick when they see a customer is struggling with something and taking the step to contact support.

The UiPath team needs to put some effort into improving the support section online. They should also improve the UiPath community forum so that beginners can receive help with activities that they require. 

I have been using UiPath for the past eight months.

Stability is a part where I would definitely rate UiPath a five out of five. It is really the best among all RPA products in this regard. 

We have a small flow that we have automated, but I feel UiPath will not let us down if we increase the capacity.

This is a part where I really think that UiPath needs improvement. They need to take up the issues from customers very quickly and resolve them on the highest priority.

We had not used any other RPA solution before UiPath.

This solution is very easy to set up. There is a bit of a hassle if support is expected from the UiPath team.

We have implemented using our internal team.

Significant manual efforts put into tasks have been reduced and a good amount of time is being saved. Overall, our time savings results in ROI.

The setup cost is minimal as far as other options are considered. 

We did indeed evaluate other options before choosing UiPath. We thought to use Automation Anywhere for our RPA needs but after doing some research, we chose UiPath.

During the evaluation process, we found significant failures when performing tests on exactly the same tasks.

UiPath is the most amazing RPA solution available in the market. Certainly, this gets plus points when it comes to feature versus cost ratio. Therefore, I would highly recommend UiPath because it comes with more stability and reliability than other solutions.

There are some features like different types of recorders. For example, Citrix and desktop are the variants we have in UiPath to solve our problems.

Other than the issues with technical support, I think that UiPath is a complete package for automating solutions in a rapid and fast environment.

I started using UiPath version 2017.1 and currently, I am using 2018.4.6.

We had a requirement of fetching emails, which are basically requests from clients filled on our website form. We read those emails and process the data filled by the user in the form. There are different forms like a request to provide reports, a request to add or delete a user, etc.

After reading these emails, the bot has to take the necessary action on our Primary CRM application. Depending on the request type, the bot will navigate to the necessary module in the application and perform the request as defined in the email request. 

Earlier, we had a team of around 20 people working in one shift to handle these requests. We were able to scale back on 15 of these team members and utilize them for other work in the organization.

Five people are still required to process exceptions that the bots are not able to process due to multiple reasons. Additionally, the UiPath bots helped process the requests for the entire day, compared to the processing happening only during business hours. 

We were also able to reduce the time taken to process each request from approximately ten minutes to two minutes.

There are many RPA tools available in the market.

The most valuable feature that UiPath has is the ability to be able to use .NET functions. Basically, all of the data manipulation functions and classes available in .NET are accessible in UiPath and this makes it easier to cast data and use it correctly. 

Apart from this, the Queue is one of the best things that other tools do not have. This enables us to have work items queued and then run multiple bots to pick up items and work on them simultaneously.  

As more and more organization units are trying to use RPA, there might be a need to have separation of data within multiple tenants or organizational units. Not only on the front-end but also the ability to have a separate database for each Tenant. This will leave no room for the enterprise security team to raise questions on data separation. 

I feel that a Host Admin, being a master Admin, should be somehow able to login to different tenants. 

I have been using UiPath for the past two years.

UiPath is quite a stable product. I haven't seen many issues and I rarely had to contact the support team for reporting issues.

UiPath is completely scalable. Right from giving you an option to segregate processes between different organizational units to expanding to multiple robots.

Customer Service is prompt and the technical support team is highly efficient and knowledgeable.

We used Automation Anywhere earlier, which is a more user-friendly and less complex RPA tool compared to UiPath. We finally had to switch due to certain capabilities that were restrictive in AA. Stability was also a factor.

I think the setup cost is quite nominal, but the licensing might be on a higher side when compared to Automation Anywhere. However, we should not forget about the features and flexibility which UiPath has.

We did not evaluate any other options. We moved from Automation Anywhere to UiPath.

I think that for the most part, this product has all of the required features.

We use robotic process automation to automate the business process of the company.

We are using the Oracle JD Edwards. We have automated the HR process for the payroll and payslips.

We used UiPath for the scanning of attachments and uploading/attaching them in the Oracle system automatically. Previously, we used to take a day or two in doing so. Most of the daily human errors are minimized.

We used this for automated internal requests including automatic reconciliation instead of several clicks from the user and automatic correction of the master records or any change required.

It has improved the work process of a task that used to take two days and is now done during the breaks of the employees. This means employees can do other tasks.

It has improved the time it takes to do the bank reconciliation from the system. It now matches the value based on the common transaction number and the reconciliation is done.

Secondly, the attachment of documents to the invoice, which is sometimes missed, is a very basic process to do. It used to take a lot of time, so instead, employees can now do productive work rather than attaching the PDF file to the transactions.

The most valuable features are the UiPath studio tools with the recording feature to capture the navigation of the process on the screen.

The Excel data, which takes a lot of time to upload in software like Oracle and SAP, can be done through the screen instead of the back end.

I personally use the features of uploading the massive records from the front end through the UiPath studio instead of uploading them through the interface table, which sometimes gives an error resulting in having to troubleshoot and check the logs of the application. It has benefits of its own but sometimes in such cases, UiPath is very handy.

It's a very powerful tool but it can still be improved in many ways. In most cases, the results from the software are the same and not variable. This means that we have to define the variable by editing the flow chart. This case happens when we are recording the navigation from the web. Moreover, sometimes there are lots of screens in the process and decision making is required.

I believe in the future this process will be handled by the click of a button or automated in a better way, with minimum human intervention.

I have almost one year of hands-on experience with the product.

UiPath studio and orchestrator are pretty stable unless some human intervention is required within the process workflow.You might face hang or freeze but very minimal.

It can be case to case for the system you are using while i did install it i faced.

The scalability is fantastic.

The customer support is amazing.

We did not have such a process in place before this.

Coming from an ERP background, I did not find the initial setup to be very complicated.

The configuration is easy to do.

We implemented this solution using our in-house team.

We have not calculated ROI to this point.

UiPath is not very pricey. If you purchase an Orchestrator then it's pricey but you receive the benefit that it runs many processes simultaneously.

I did not evaluate other options before choosing UiPath.

I can't wait to have automation with every human in portable devices. It will automate not just the business process but daily life activities.

My primary use case of this solution is automation. Where there are tedious tasks, we use the automation in those areas or sectors. I am a trainer and learner. It also helps others because it does not involve much coding.

UiPath was recently implemented and we have started migrating to this technology. From my perspective, it's useful for solving any repetitive tasks in any field.

The features that are most valuable are Excel Automation, Web Automation, Web Scrapping, and CV Automation. We had small tasks so we used these types of automation. As a trainer, these automation types are useful.

I would like to see improvements made in OCR, Captcha Automation, and PDF extraction. There should be a clearer way of performing web scraping, such that it is simpler to do.

Overall, more add-on features would improve UiPath.

I have been using UiPath for four months.

I'm working at a computer software company, where we're bringing digital transformation using UiPath. All rule-based and mundane tasks are identified and automated using RPA. We have about 25 bots in production now. Data processing, file handling, email automation, and related activities are running in production.

The most valuable features are the ability to interact with almost all applications in Windows, ease of programming, excellent forum support for developers, free academy training, Orchestrator capabilities for BOT handling, and Citrix-supporting features during development.

Robotic process automation should mold and grow into intelligent process automation where a BOT can handle more than just robotic and simple tasks. I'm sure UiPath is working towards it.

A self-coding robot can be a very useful tool in the future.  

We have been using UiPath for three years.

The ROI was quick and measurable. The employee's productive hours increased and they were able to handle more transactions and focused on better quality work that needs human intelligence. Some processes were developed in human-BOT collaboration as partial automation.

The R&D focus of UiPath is really impressive.

I have worked in many industries and domains like healthcare and finance. I have automated web-based applications and Email automation.

Automated an end-to-end process that starts with the user raising a request in BMC Remedy. It handles requests for respective Roles in the GRC System of SAP. This process includes identifying the Request number from the BMC remedy Ticket. The BOT identifies respective control owners for requested roles and requests the controlling owner for their approval. Then BOT performs the Approval/Rejection process accordingly.

UiPath has improved my organization in many ways. With the help of UiPath, we were able to automate our mundane and repetitive tasks and this has saved us lots of time. Also, it has enhanced our productivity and reduces the error rate. We were able to complete our tasks as per client requirements.

Orchestrator is the feature that allows making use of robots for remote location systems. The work queue is the added advantage to maintain the bot data.

The inbuilt RE Framework makes development easier and fast.

UiPath helped me to automate the various complex and mundane processes. You can also run your Python and .NET code in UiPath, which makes the development easy.

The UiPath interface is very user-friendly and also it is easy to learn and use.

There are many online certifications in the UiPath Academy, so it helps the user to become a certified developer and learn everything from the online courses.

Support from the UiPath community is very good.

There are some problems with selectors and in PDF extraction so it could be improved a little bit.

There is a bug in UiPath that occurs when the URL of the web page changes. We are unable to scrap the data from that application page.

The Community Edition is not stable, so end-users working on the Community version may find some errors or issues when using this tool. Also, debugging is not as expected. A lot of issues occur during debugging.

I have been working on UiPath for one and a half years.

UiPath is good stability-wise. I have had a great experience with UiPath.

I find that the scalability of this tool is very good.

Support from UiPath technical community is very good and the response time, I would like to say, is very prompt.

We did not use another RPA solution prior to UiPath.

I was not involved in the Setup part. I had a team for this but as per my understanding, this tool is easy to setup.

I have implemented this through the in-house team.

We did not evaluate other options.

UiPath is a very complete software and allows you to make different robots depending on the system. Its main function is to save time and automate project management, which it does very well. It allows you to remove software and in this way, you will return to Create them but automated so that artificial intelligence (AI) can work correctly. It collaborates with employees.

It is possible to automate, for example, Excel files so that the forms can be filled automatically and not manually.

Overall, I am very happy and I recommend it.

I actually went for a powerup automation hackathon conducted by UiPath, which gave me the idea to implement this in my organization. I used the product, experienced it, and I'm here. UiPath reduced a lot of manual work and I am getting positive reviews from the company.

UiPath has helped with automation to categorize emails, text capturing to get detailed information about the organization, and reduced manual work a lot which can't be said explicitly. We even tried to used UiPath as a testing tool, and it helped speed development for the project.

The most valuable features are Excel Sheet manipulation operations and the Data Scrapping Wizard.

It provides for easy implementation of the project, where we can easily develop without coding, and there is well-defined process management in the orchestrator.

I can easily get support from the UiPath forum and through the mail.

I would suggest that UiPath be released for use on other platforms.

Almost a year I am using UiPath, well developed.

Previoiusly, we did not use any other solution, this is the first.

The new version is good. It met all of the requirements and more features have been added.

UiPath Studio has improved a lot, testing the custom activity. Previously, UiPath would get a few errors while developing the project, but now it's completely gone.

The new user interface is integrated with Orchestrator and it is awesome.

I use it to provide training on UiPath.

In the past, I have used UiPath to automate the debit card activation web portal. The task is to read data from Excel and put it into the web portal.

I used it for DMS portal automation as well, after reading scanned PDFs and updating data in the DMS portal.

Currently, I work as a trainer, and the community edition has helped me train many developers in Uipath.

The most valuable feature is Orchestrator Queues, as it comes in really handy when processing large sets of data.

I find the great GUI of UiPath very appealing.

The training available in UiPath is really awesome and the material makes you automation-ready so that one can work on real-time projects. 

Below are the three features that need improvement:

• Allow "Wait for task" to be used in XAML files other than Main.
• Allow mail-type variable to be stored in Orchestrator queues.
• I would like a way to add priority to the outgoing mails from UiPath studio.

I have been using UiPath for one year.

I would rate stability at 90%.

Easily scalable by buying licenses from platform.uipath.com.

The technical team at UiPath is really very helpful.

I did not use another RPA solution prior to UiPath.

The initial setup is straightforward.

I would rate my vendor team a nine out of ten.

My advice is to use the community edition first to automate a small business process and then go full-on with UiPath.

I evaluated Automation Anywhere.

 Its great software. Just download UiPath and try for yourself.

In our organization (Global Business Services), we do a lot of automations in the Windows environment. In the past, we've used a lot of VBA macros and VB scripts but maintaining support for more than 1000 macros has become a very difficult task. UiPath, as an end-to-end RPA solution, solves many issues and limitations of the previous setup.

We were managing more than 1000 VBA macros and we knew there's even more out there in the business. By deploying UiPath bots, we have standardized the automation approach and it also gave us a centralized view and control of all automations deployed on the platform (Orchestrator).

The drag and drop interface of Studio is very valuable as it minimizes the development time. The Orchestrator is also a very integral part of the package as it allows us to deploy, monitor, and manage all of the bots in the platform.

The capability of creating and using high-density robots makes management simpler and straightforward.

The Studio can be improved by adding certain features like color-coding the activities. By letting the user change the color of the activity box (or by having different default colors for each type of activity), it's easier to identify activities especially when they are nested together.

The Orchestrator can be improved by making the landing page dashboard customizable based on what information and stats we want to see as an organization. The stats shown in the Orchestrator dashboard are very basic. Today, we had to make a separate web app that uses the Orchestrator API just to see the data that we want to see in a format that we prefer. Our business needs visibility on which country the failed/pending bots are servicing and how many jobs were completed based on tower assignments. These stats are not available out-of-the-box in Orchestrator.

My organization has been using UiPath for more than a year now.

The system is pretty stable, the only limitation could be the hardware setup. If there is not enough RAM or CPU power on the machines where the bots are running, then it could result in system crashes.

It's very scalable as you can start with one bot and make it do multiple processes. Adding the next bots is easy too.

We have an assigned Customer Success Manager and he has been very helpful. He used to be a senior developer in UiPath and he's very knowledgeable. 

UiPath is our first official RPA solution.

The initial setup was straightforward. We had to build virtual servers and install UiPath in the machines, then opened up a couple of ports in the firewall and we were ready to go.

We implemented using a vendor team and it took longer than expected despite the initially assessed simple approach. Getting the paperwork done and giving the vendor team access to the system probably took longer.

I don't have direct visibility on the ROI as a different team takes care of it, but since we started using UiPath, we have been more stringent on what kind of automation projects we take in as a developer team.

UiPath has a Community version that is totally free (including Orchestrator) and has all the features. Any organization that wants to get into RPA should try that out and then look into the paid version.

We've had a demo by Blue Prism but ultimately we chose UiPath based on the support we received, as well as its capabilities.

My advice for anybody who is considering this solution is to use the free Community version extensively and make use of the community forums. The RPA Academy is also a great resource, a one-stop shop to get educated in using UiPath and it's also free. Once your organization is ready to scale and go beyond free, UiPath offers reasonable pricing.

The primary use case for this solution is to reduce manpower and achieve the best result with minimal time compared to doing tasks manually. This is a great advantage of this product because when doing tasks manually it takes many minutes of time but when the bot does it, it is finished in a few seconds.

I have several examples where UiPath has improved our organization. For example, our organisation was supporting a Japanese customer for handling tickets. Resolving those tickets manually usually took them 10 to 15 minutes but the bot was able to complete the task in four seconds. This is the great achievement.

There are many cases where UiPath reduces our work time and effort.

In our organisation, we have integrated with SAP HANA tools, which makes handling various situations easier.

The features like Data Scraping, Excel Automation, Mail Automation, System Automation, Secure credential activities, User events, and App integration are valuable to us. The integration like ABBYY OCR and Tesseract OCR are helpful. ABBYY OCR is a very good activity that can identify handwritten text, but to use this requires a licensed version.

UiPath requires less code writing and is user-friendly compared to some other solutions. The standard things can be automated very easily. The drag-and-drop activities make life easier.

The most beautiful activity is sentiment analysis, where we can predict the good reviews and the negative reviews. This gives us a great advantage.

Integration with different tools makes easier by using APIs.

1.For example: If two members are working in one project but different xaml files.

In one xaml file suppose i did few changes and if any more changes are required to do in the same xaml file the next member can see what changes has done in the activity and do the required changes.

Basically i mean the changes whatever we do there should be some place where we can see the history like Modified By, Modified Date and Modified Activity.

Which makes easy to track who is the last member to modify the xaml files.

2. There should be a global search mechanism for variables in the process flow and if the search is found then it should indicate that activity.

3. There should be activity/some mechanism where we can revert back the code of that particular date.

I have been using UiPath for one year.

I have used Salesforce, ServiceNow, and Frontend developer. Now, I have switched because this product makes the life of developers easier with respect to code implementation.

I have evaluated Salesforce and RunMyProcess products, which are cloud platforms.

I have found this to be a very good platform to work on. It's in high-trend in the market now and very much a great thing.

I am responsible for developing and improving RPA-software bots in my organisation. The processes we work on improving are in the field of finance. We started using UiPath and RPA as a technology about two years ago and are still improving and growing.

It is implemented within a larger strategy of optimizing processes in our organisation. The tasks which have been identified and thereafter automated with UiPath are now more efficient, achieving savings in personnel and improving quality in some fields.

The most valuable feature is the UiPath Studio, the graphical coding software, which has high usability and modern appearance. The number of functions is very good and is still being improved upon. These features allow you to fastly implement automation projects. Furthermore, it is quite easy getting started.

The attended bot functionality is in need of improvement. The use cases are rare and the licences are quite expensive (in relation to the use possibilities we see) for attended bots - Therefore we are currentlying neither using or planning to use them.

I have been using UiPath for nine months.

I have to say that I am overall very happy with the software and do see little need to give them advice. They have implemented a lot of new things over the past months.

We use UiPath for:

• Financial domain
• Excel automation
• SAP automation
• Citrix automation
• Usage of Orchestrator queues
• RE framework
• Automating password resets
• Security and governance
• Rule-based exception handling
• Large group deployment
• Centralized repository for version control
• Execution logs and credentials

This solution has improved a lot in our organization. Many departments have started automating their daily manual tasks, which involve repetitive and rule-based jobs.

Cost-Effectiveness: There will be no lunch breaks, holidays, sick leave, or shift time allocated for robotic automation. It can be set to work on a repetitive cycle, and as long as it is maintained correctly, it will continue to do so until programmed otherwise. This eliminates the risk of RSI occurring.

Increased Productivity: Using robotic automation to tackle repetitive tasks makes complete sense. Robots are designed to make repetitive movements. Humans, also by design, are not.

Giving staff members the opportunity to expand on their skills and work in other areas will create a better environment in which the business as a whole will benefit. With higher energy levels and more focus put into their work, the product can only improve, which will also lead to extremely satisfied clients.

The most valuable features for us are:

• Citrix recorder
• UI Explorer
• I used to connect using remote desktop and automated it using image automation.
• The cloud deployment option is particularly attractive to some customers for its flexibility and scalability, along with customary thin client advantages.

The user access management could be improved such that we are able to set up user rights in a more sophisticated way. In the current version, if you grant, for example, Execute access to a user, it can execute all robotized processes in the given environment. You cannot specify the rights at the process-level.

I have been using UiPath since August 2016.

Before using RPA, we did the work manually. Once we became aware of this solution we tried to automate our work and achieved success. This has made our lives easier.

The increase in production at a lower cost produces obvious benefits for any manufacturer. The cost of investment can be recovered in a relatively short space of time and the gains from that point onwards are exponential, to say the least.

The initial investment cost is expensive, but I promise you guys this will be very helpful as we can easily automate applications and our productivity has increased.

I didn't evaluate any other option, rather I directly chose UiPath and started working. It proved my decision correct and I can say it's the leading RPA tool in our market now.

I am using UiPath RPA for my ERP entry where I update hundreds of data elements within minutes by RPA robots. UiPath gives you the degree of freedom in these robots to work according to your requirements. It is very easy to use even without coding knowledge, and it can be implemented with little knowledge of RPA.

In my organisation, we have 5000 students and 350 professors. To update their profile regularly, we need between five and eight people spending lots of time and after many reviews, there are always typing mistakes. Now with UiPath robots, we can complete this task within hours and without error.

UiPath RPA needs very little coding knowledge, as designing software robots is done largely using drag-and-drop. We can run these robots without installing them in our system, using the cloud-based system instead.

The attended robot that works in conjunction with an operator is very valuable. 

They still need some improvement in their new version of UiPath Studio, called StudioX, to improve design for Excel and email automation work.

The OCR functions need to be improved.

We have been using UiPath for one year.

UiPath is my first RPA experience.

The initial setup is very easy to use and install.

The best thing is that the UiPath Software is available as a Community Edition that is free and sufficient for personal use or small business.

I did not personally evaluable other RPA options. I heard only about UiPath because my company assigned me to learn UiPath RPA.

I have been using UiPath for more than a year and find it very comfortable to use.

I am an RPA developer and I am primarily using this solution to fill up timesheets in an internal portal. I use Windows 10, 64 bit. My team uses a mix of Windows 7, 8, and 10. It is suitable for daily and weekly tasks, which pretty much don't change over time, and is what I choose to automate parts of my team's work.

We are an IT company that works on both products and services. UiPath has helped to automate tedious data-filling jobs for test data creation (Testing), and data extraction jobs from public websites (HR). It has added a new capability which we can showcase to our clients.

Data Scraping is definitely a unique and useful feature that we had not known about before.

Smooth integration of OCR, which is very quick, is a useful feature.

Manage packages to get more packages.

Save as a Template feature.

Snippets are really useful as a reference for logic.

Plus button between activities & Ctrl+Shift+T is very useful in adding activities quickly.

Having the ability to run the bot from a single click will help to democratize the RPA.

Currently, I am running the XAML file from command prompt mode and this is causing inconvenience every time I update the XAML file.

The regular update of the Community Edition means that the UiRobot path is constantly changing on every update.

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

There are not many complaints on the stability of this solution. Though the regular updates of the Community Edition have given me trouble at times, it has been quickly resolved in the subsequent updates. I think that the UiPath Forum portal is one reason for this.

According to me, on one side it is creating a buzz and everybody wants to be part of it. On the other side, there is resistance to embrace new technology in their process. Only over time, this can be scalable and it cannot be done quickly.

This was my first RPA tool.

The initial setup is straight forward. This got better after integrating the Chrome extension setup in the UiPath studio itself.

I did not evaluate other RPA tools.

The UiPath product team is doing an awesome job. Keep it up.

UiPath is the go-to tool if you need to automate tasks that can be combined to create an automated process. We provide services to customers using UiPath. They come to us with their needs, be it to improve performance, accuracy, or reduce costs, and we help them by automating processes that, most of the time, consume too much in terms of unnecessary human resources.

We have many successful cases where the customer has noticed an important reduction in processing time while also maintaining excelent quality.

This solution is especially efficient if the process being automated involves legacy applications that do not and can not be automated using APIs.

UiPath is great for desktop automation because it integrates well with applications and we are able to tailor selectors to our needs. 

One scenario where it is not great is on remote desktop automation, where applications are not directly accessible. It does, however, have some features to facilitate this kind of automation and definitely stands out from the competition because of things like that.

I have used UiPath for the last nine months.

The product is very stable and no weird behaviours should be expected.

This solution is extremely scalable. It has a cloud platform to manage the workforce and can work with parallelism.

The support team responds fast and seem to be interested in solving problems.

I have used Kryon.

The initial setup is not really complex.

We implemented UiPath through a vendor and they seemed to be experts.

Our ROI varies from project to project.

There are different licensing options and you should study which one better suits your company's needs.

We did not evaluate other options because we work with the tools that our customers buy and we do not get a say in what they acquire.

There is no doubt why UiPath is the market leader, it is very robust, flexible and has great learning material and documentation. The team and community behind this product are amazing.

Our primary use case is RPA Consultancy for clients. We have been building robots for our clients in many environments. These include attended and unattended robots that are on both web-enabled machines and local machines (Due to Security Concerns). They span across many industries as well. 

UiPath is by far the best RPA platform on the market. We have been building robots for our clients and saved many manhours and have very satisfied clients. As the best RPA Platform, it has provided lots of value through both our internal projects and for our clients.

The most valuable features are the helpful community and the ease of use. The fact that the community is responsive and willing and able to help is wonderful. Features that allow for convenient data handling are very useful as well. Simple things like being able to manipulate data in memory are not available in most competitors.

Quality of life improvements such as the multiple assign activity and more recently, the ability to change arguments to variables and vice versa are very appreciated. It shows that UiPath has been taking feedback from the community and acting on it to improve the platform.

More quality of life improvements like automatic argument inheritance would be an improvement. Also, have more courses, maybe for more prominent packages like enhanced REF, and the others released together with 2019.4. I also hope that UiPath can be closer partners with us.

We have been using UiPath for one year.

UiPath is a stable solution. 

It is scalable, especially with the use of Orchestrator.

We use Automation Anywhere as well.

The initial setup is relatively simple, but I have not personally done fancy stuff with installations thus far.

Our in-house team builds the bots and deploys them.

Our ROI is high enough.

UiPath is a good deal all round.

We have worked with both Automation Anywhere and Kryon.

It is the market leader in RPA and my go-to software when looking at automating business processes. Kudos to the team.

We primarily use this solution for one of our business use cases. 

We are building robots with Safyr CRM. They are scheduled by Orchestrator and we are handling every step: Solution, design, followups, stacks, consulting, and finally implementation. Nowadays we are using robots internally but we will start with third-party clients in 2020 Q2.

UiPath has helped to make all of the internal business processes lighter, enabling my company to save costs in time and speed for all of them. Also, we are researching all implementation models to get the resources for a quick and agile response to all business cases within several markets.

Orchestrator is the definitive feature for me as it has the real meaning of robotic automation. The Orchestrator in UiPath has a lot of similarities with every RPA tool I have used, both for automations and machine managing. They remind me of tools like Jenkins or OpenShift UI. Simple and cool.

Since I am not an expert, I am looking to the training lessons. The training could be improved by clarifying more and more at every step.

We would like better integration with custom environments and external inputs like forums or integrations with other robotic frameworks.

We have been using UiPath for two months.

We did not use another RPA solution prior to UiPath.

UiPath is very useful and easy to implement.

I've used UiPath Studio to develop Automation projects that help me automate repetitive and manual tasks. This lets me focus on other, more important jobs to do.

I've been able to automate some tasks and projects both for me and my colleagues to help us with boring repetitive work. From jobs that require reading and processing emails, to jobs that require scraping information from web pages, this tool allows us to do anything that can be done by a human. 

UiPath studio recorder allows us to automate jobs very quickly and very easily.

The tool is intuitive and precise. It is easy to use with not a lot of programming knowledge needed. Also, there many built-in activities that let us automate tasks. If there is no activity available then it is probable that somebody has built one already.

Definitely, the machine learning engine should be improved so that we can process more invoices and purchase orders in PDF format with ease. There is a beta version but it is not stable. This is the only place where UiPath needs to improve because their competitors have this option and it is useful.

I've been using UiPath and UiPath Studio for more than a year.

Our primary purpose is to automate our internal processes so we can increase our profits and reduce our headcount. We are an IT service provider, so our main focus so far has been our Service Desk but we are starting to work with our Finance, Payroll, and HR teams in 2020.

So far, we have not realised much in terms of benefit because we have only just begun our RPA journey. However, we have approximately four FTE of savings in our pipeline. It has improved our business so far by creating an innovation-based way of thinking amongst our teams.

Personally, I find that Explorer Expert and StudioX appear the most valuable to my role as an Analyst. Explorer Expert allows me to easily "record" processes and gives the developer the skeleton of an automation project. StudioX allows me to build simple automation projects without the need to engage our development team.

StudioX could use some improvement to broaden the range of automation projects suitable. At this stage, it is limited in terms of the functions that are available and I would like to see a lot more options added to this tool so that our business users can get even more benefit.

We have been using UiPath for three months.

There have been no concerns with stability as of yet.

It appears to be very scalable but we have only had the tool for a few months.

Customer service has been great so far. We have received answers to all of our questions quickly.

This is our first RPA solution.

We had some issues with the licenses at first, but we were able to communicate with UiPath to get this resolved.

We used an in-house team to implement our solution.

So far we have not had a return on our investment, but this will change in 2020.

Pricing is quite reasonable with UiPath and there are some tools which are free to use.

We evaluated a range of options on the market including Blue Prism.

So far, I highly recommend UiPath. They are constantly introducing new tools and features and they all seem to provide extra benefit.

One of my primary use cases is invoice processing.

In this process, there are two applications including one for data and the other for the main application. The main application needs to take invoice data from the data process and match it with invoice details that it has. After this, the status needs to be recorded in the data process.

UiPath is growing day by day. We began with one unattended bot and we now have approximately 20 bots in production.

We are using the RE framework and it's very helpful for delivering the product on time.

The image-based automation is working as expected, using different levels of accuracy.

OCR-based activities should be improved to handle larger amounts of text.

UiPath does not recognize Google and Microsoft OCRs.

Sometimes UiPath will not work properly, even though it worked the previous day. Also, it may suddenly not work when we switch environments from development to QA. This happens approximately one out of ten times.

I have been using UiPath for the past two years.

Technical support has been helpful for debugging and fixing issues that we have had in production.

I did not use another solution prior to this one.

I began looking at Automation Anywhere, but when I saw how user-friendly the interface in UiPath was, I started learning it instead. I find it very comfortable to work with and develop processes.

I am proud to have UiPath on my resume as it is valuable for career growth. I plan to continue as a UiPath developer.

I have been using UiPath in the healthcare area and right now, I am developing a healthcare project. I have also used it in retail projects and we have automated entire retail systems for vendors and customers. This has given them more reliable action and product services that are beneficial for both the organization and the user.

UiPath helps us in the execution of processes that need to be done repetitively, like data entry or content migration. It is fast, affordable, efficient, and easy to use.

Healthcare is also an important project that we have running. It saves time for patient eligibility. 

The most valuable features of UiPath are its activities. There are a number of activities available in the UiPath Studio, which are enough to automate all types of tasks.  Since UiPath is new in the market, it is constantly being updated every day, and new features are being added accordingly to the user requirements. 

I would like to see the computer vision activity updated.

There should be a click-event-update activity present in the UI Studio where we can click a link and the result should act as a button. Right now, this feature is not available in such conditions.

The OCR should be made faster to save more time.

If I am buying production licenses from UiPath it should provide at least two or three nonproduction licenses for further use.

The Studio should be made interactive like Orchestrator.

The debug option in Studio is not working on breakpoints, which is an issue that I have already highlighted in the forum.

I have been using the UiPath and its services for the past year. 

I would rate the stability of this solution and eight out of ten.

With respect to scalability, I would rate it at seven or eight out of ten.

I would rate the UiPath technical support a ten out of ten.

Prior to using UiPath, we used both Automation Anywhere and Blue Prism. We have found UiPath to be more reliable, easier to use, more stable, and 100% accurate while performing actions on any element or running automation anytime.

The initial setup was straightforward.

We implemented this solution with our in-house team.

ROI for automation depends on the projects, timing, scope, and reliability.

Primary use cases involve the following automation environments and processes:

1. Oil and Gas Domain: Automation of various applications specific to this domain such as Gopher, Tow, Toad, Excel, and various browsers.
   
2. Finance Banking: Here we have to deal with various legacy applications with a lot of PDF and Excel-based automation. UiPath comes with a lot of reliable solutions here.
3. Healthcare: Automation is a big challenge because the Healthcare domain is not a simple thing to automate. The ML extractor and Intelligent Automation activities are best to use here.

UiPath has improved the reputation of our organization in an exceptional manner. Our clients are happy with the solution that we provide them as a part of the automation. They are happy that robots are there with a helping hand, where they can learn RPA and give some time for their personal life as well.

UiPath helps them with saving their time, FTEs, and ROI.

Following are the most valuable features of UiPath:

1. Every month, there are new features released. These are all next-level and can disrupt the automation industry.
2. Vision for RPA and ML work together including ML skills, ML extractor, and Python activities.
3. UiPath is easy to use with very simple drag and drop functionality that allows you to automate processes without knowledge of coding.
4. Covering automation in all possible applications including SAP, G Suite, Salesforce, etc.

Possibility of improvement:

1. Exception handling and exception details can be much better and more user-friendly.  Many times, details of exceptions are not understood by somebody with a non-coding background. Example "Object Reference not set to instance of object", this is the exception message that we got and log from UiPath. For a developer it makes some sense and meaning but for a SME or User it is very complicated to understand the meaning if this exception
2. User interface in the coding area can be better and more compact: Some times expanding seq. cause the code to look very big and difficult to undertsand the scope of container

I have been using the UiPath Platform for automating various processes for the past three years.

It is extremely awesome. customer service/technical support used to assist with in an hour of raising services issue ticket on portal

Automation Anywhere

We switched to UiPath as it provides a lot of functionality than another tool in market

We use this solution to automate business processes and save millions of dollars in operational efficiency. We are developing new automated solutions for our clients and partners, and also training new developers to use this tool to deliver great results by the end of the year.

The business has saved million worth of dollars in cost savings.

The user interface is intuitive and it is easy to develop workflows.

The community is what I like most in UiPath and I think that without it, the solution would be hard to learn like Blue Prism was in its earlier years.

There could be improvements made in in terms of debugging. Troubleshooting is hard.

I hope there can be more major improvements in Orchestrator, such as the ability to have session variables other than assets.

Being able to filter work queues, just like what Blue Prism has, would be a helpful addition.

There are some limitations like the UiPath Executor becoming stuck when running 10GB text files, which is something that really needs to be fixed.

The training is difficult and should be made better.

We have been using UiPath for almost two years.

UiPath is a very stable solution.

This solution is very scalable.  Our UiPath team has grown from 10 to more than 50 developers, including business analysts, process analysts, developers, senior developers, and solution architects. Hoping to grow our organization more as new clients are coming in.

Customer support is great but not that fast.

Prior to UiPath, I used Blue Prism. I switched because my company switched.

The initial setup is not straightforward but also not complex.

I set up UiPath on my own.

More than a million dollars.

UiPath is more cost-effective than any other tool.

I did not evaluate other options. Aside from Blue Prism, UiPath is the best.

Overall, UiPath is the best in providing a community for all developers.

I use it professionally to build software robots for an international company.

My organization is spanning across multiple countries so it's hard for me to see UiPath's influence. However, in my office, we are yet to implement the first solutions.

The most valuable features of this solution are:

• Custom components that can be found on UiPath Go!
  
• Debugger with variable watch capability.
• The UI Explorer can examine the underlying structure of the application's user interface.

I would like to see the replacement of VB.NET with some more popular programming language as the program's backbone.

I've been using UiPath for around one year.

My primary use case of this solution was to automate BMC Remedy and SAP use cases. I used UiPath to automate various tasks in SAP. I developed several bots in client virtual machines using UiPath and then connected the virtual machine to the UiPath Orchestrator. Once connected, I scheduled the Bot.

The manual effort of employees for repetitive tasks has been tremendously reduced and thereby the employees are concentrating on different fields. Furthermore, human error is completely wiped out because of the Bots. The tasks that used to take a lot of time to get finished by humans are now accomplished in a short span of time by the Bots.

I found the Library option as most valuable because first, we can avoid the development of the same task again by developing and publishing a task as an activity into the Orchestrator, and second, in case of any changes required, the developer can make the required changes and republish in the Orchestrator with the new version. At this point, others can download that task as an activity and can use it with their Bots.

Apart from the library, I like the API activities and the activities which we can call Python scripts from.

The area that must improve is while releasing a new version, it must be capable of running the bots developed in the older version.

It would be nice if we can develop an intelligent bot that can make the right decisions.

Please include the option to select the time zone while scheduling the Bot in orchestrator.

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

We primarily use UiPath to bridge process gaps between various pieces of software. Overall, it is a cost-effective tool to quickly move data and reduce repetitious tasks. For example, we use UiPath to produce SAP reports, format the data and then enter it into reporting tools.

In the departments that use UiPath, they've been able to reduce man-hours spent doing manual processes. This allows our team members to provide value through analytical thought, direct customer interaction, and reduced errors. Overall, it has allowed us to reduce FTE costs while also improving the quality of work the team produces. 

The most valuable feature is the simplicity of the Studio software. It has allowed us to quickly rollout processes. For example, we've been able to train users in as short as one or two weeks and have them produce a usable process within two additional weeks. While many of these processes have been simple "quick wins", they still show the value. 

The setup and licensing process are somewhat cumbersome. Additionally, the Studio publishing is somewhat antiquated within Orchestrator. Overall, it should be a much simpler process to move a process from Studio to production, specifically as an attended Robot. 

We have been using UiPath for more than one year.

Stability isn't a concern with UiPath.

This solution is very easy to scale.

Customer service has been FANTASTIC. Very quick.

We did not use another RPA solution prior to UiPath.

Setup was complex and we had to outsource the IT portion. This may just be because our internal IT team was somewhat unfamiliar.

Our in-house team was assisted through outsourcing.

With our proof of concept, we had already doubled our ROI from the initial year-one cost.

The cost is small compared to the benefit. Licensing can be cumbersome and makes overall pricing needs somewhat hard to forecast, but not too difficult once the tool is scaled. 

We did look at Automation Anywhere but chose UiPath due to it's better Studio software.

We're confident that we chose the best RPA tool.

We use UiPath for a lot of different scenarios including recording daily time capture, ordering meals for teams, and more technical work related to tax and audit. The most common uses for me personally are for drafting and sending emails. This has saved a countless hours of time. Basically, if it can be automated then we are automating it.

UiPath has opened up a lot of opportunities in our organization to save time through automation, but maybe even more importantly, it has created jobs and opportunities for many who want to work in the tech space. This work is highly satisfying and makes a real impact on the quality of life for those involved.

My favorite features and upgrades that I have found the most valuable are the ability to create custom activities specific to our organization's needs. This ability to customize what we need has really opened up opportunities to automate programs that otherwise would not work properly. Legacy systems can be finicky, but this feature makes it possible to use APIs and get the work done that we need.

I work in a highly regulated field and so many of the features offered by UiPath are not allowed because of one reason or another. I would definitely appreciate efforts to be made to build useful tools that meet regulatory standards in different fields so that we can all get the most out of automation.

We have been using this solution for two and a half years.

We use many different solutions, but I am personally most familiar with UiPath

If you are a smaller organization, use the free community version of the software to get a feel for its features and abilities. Then, once you are comfortable with how it can be applied, work with UiPath to implement it. It will take sacrifice, but the returns are great.

We evaluated all options and decided on different tools for different scenarios. These tools include Automation Anywhere, Blue Prism, etc. 

One use is in our corporate tax accounting group. Our environment includes systems such as SAP, Vertex, several homegrown, and of course Excel. Other use cases include automating a timekeeping system and performing cell phone bill analysis. Environmentally, all use cases involve different systems.

For corporate tax accounting, we use UiPath to pull data from multiple sources (i.e. SAP, Vertex, etc), and then use multiple pivot tables in Excel. They were doing this manually, and it consumed about 40 man-hours per month. With UiPath, we have that down to about five hours per month.  

The most valuable feature is the ability to stop the process after it has been started by an individual user. This allows for some dynamic events, but still gain the automation. The underlying architecture (i.e. Elastic stack) is decent, but there probably needs to be better ties there to maintain at least an n-1 version on the Elastic stack.

Improvement should definitely be made in the area of screen capture, where Adobe Flash is still being used. Trying to 'read' a screenshot (vs looking at HTML) was a challenge, and even when Flash goes away, there will always be a need to do a screenshot and then get data from it.

We have been using the product for about two and a half years.

In general, at least for us, product has been very stable, but we are not doing extremes with it.

It will scale somewhat both vertically and horizontally. The basic solution for that will be to add more servers.

No other solutions were tried.  

The actual UiPath install was somewhat complex. We did have a learning curve on the elastic stack.

We implemented this solution in-house.

You need IT support in installation and operations. This is not the job of 'just' plug and run.  Costing and licensing were generally in line with expectations of this type of software.

We looked at the top three providers in this space, including Blue Prism.

Overall, the product is good, and we are happy with it. There is always a concern about the company's business viability, but that is a risk with any software company

I am using UiPath for automating finance processes. One example is AP invoice processing. I am integrating ABBYY with UiPath so that we can easily extract information from an invoice with different templates. Then once done, the UiPath robot will input the information into an Oracle system.

UiPath has improved the finance department. Most repetitive tasks are being handled by the robots already and they are focusing on value-adding tasks such as analytics, continuous improvement, and customer experience. With that, the employees are happy because they are doing what they are actually trained for.

The most valuable features are the UiPath platforms. I am having a fast and convenient automation journey because of it.

I am able to get answers on issues regarding UiPath in the Forum and I can also automate faster because of the reusable components available in UiPath Go!

I would suggest that they improve the UiPath Connect Enterprise because the planning stage is the most crucial in the RPA life cycle.

Right now, the UiPath Connect Enterprise has little analytics on computing the ROI and the complexity of the automation idea. Maybe there should be more fields on the form to fully get all the details to really compute for a concrete ROI or complexity of the idea.

I have been using UiPath for one year.

It is stable if you are using the Enterprise Edition.

When using the Community Edition, once there is a release, there may be issues arising in your current setup.

Scalability is great! UiPath Academy taught us the best practices to easily scale up the robot.

With respect to the deployment, it is easy because of Orchestrator.

The technical support is fast. They will get back to you within 24-48 hours. However, we normally rely on the UiPath Forum because it answers most of the issues.

I have used Blue Prism and WinAutomation before.

I stayed with UiPath once I got a grasp of it because it has a user-friendly interface and awesome platforms.

We had ROI in nine months.

I hope in the future the costing will be trimmed down, especially on Studio.

We evaluated Automation Anywhere but the interface is not good as UiPath.

I am currently happy and content with what UiPath has to offer. They are always providing what is needed. With respect to UiPath Connect Enterprise, it is still in its early stage so I am looking forward to it improving.

We work with third-party recruiting software to organize candidates and track applicants. We utilize the bot to pull information from these pages and organize it and run actions.

Utilizing the bots to screen resumes helps prevent time being wasted on initial tasks around recruitment.

It has saved countless hours of manual review which frees up resources for other internal initiatives. We are able to better recruit candidates, which makes us a more efficient organization from the ground up, with better resources at our disposal for different projects. 

The most valuable feature is the ability to extract structured data, as this is an essential part of the bots that we create.

UiPath is intuitive and easy to use. Other systems don't have the ease of use that UiPath has. My organization has worked with its competitors and have not liked the results.

The ease of sharing the bot to different users is something that should be improved.

Something of "cloud" capabilities would be a useful inclusion. We live in a time where remote work is essential and we should be able to access and run the bot from anywhere.

Typically, you can run these processes in the background but it slows down the computer. 

We have been using UiPath for less than a year.

There are lots of updates but it is a stable solution.

In terms of scalability, this is the best automation system I have worked with so far.

My suggestion is to use the forums at https://forum.uipath.com/

We did use another solution prior to UiPath but it didn't have the functionality that we were looking for. Also, it was not intuitive. 

The initial setup is straightforward. Buy the license, download the software. 

My advice is to try the system out with the Community Edition first.

We have looked at a wide variety of automation tools.

I have been using UiPath to develop automations for my company. We are a manufacturing company that uses SAP as our primary enterprise application. We are currently meeting with many different business areas and hearing about all of the different processes that they would like us to automate for them. Since UiPath works within SAP, it should help us get some easy wins!

UiPath has allowed us to remove tedious work from our daily process, saving us hundreds of hours. We are currently using it to process separations for people leaving the company. This was a 100% manual process before UiPath and it was required to be completed hundreds of times each month. The team doing the work was extremely overworked and UiPath has allowed them to see a little bit of light at the end of the tunnel. 

Orchestrator is essential, but I love how Studio includes so many activities that are pre-programmed to do what is needed.

Who doesn't love the recording feature? A recording is great to use when doing the first build of new automations!

The most important feature of all is the UiPath community and the forums, as they have helped me with countless questions!

One of the problems with UiPath is that it doesn't interact with some programs, such as AD and Chrome, and it would be great to have even more included!

We have been using UiPath for six months.

So far we have not had any issues with the stability.

We have not scaled, but from what I've read it should scale easily.

We did not use another solution prior to UiPath.

Understanding how everything connects was a little difficult, but UiPath offers classes that walk you through the setup. With the classes it was much easier. 

We implemented using our in-house team.

Do your research, the infrastructure piece is important to understand before purchasing. Also, you need Orchestrator to implement UiPath properly, so don't let anyone tell you different!

Finally, you don't need to start with 100 bots... my advice is to start small and then scale. 

We looked at Automate Anywhere and writing scripts, but UiPath seemed like the best path.

There isn't much that I don't like about the product. I love all of the new features and products they are releasing this year, and I can't wait to see where this goes in the future.

The primary use case of this solution is to automate the repetitive tasks in the workplace. UiPath is connected to the Orchestrator to centrally manage the robots. Mobile Orchestrator is what we use to control the robots using Android and iPhone mobiles.

UiPath has saved us many FTEs. 24x7 working robots have helped us in saving a lot of time and have reduced human mistakes. Robots take care of tedious and repetitive tasks, where humans concentrate on critical decision making.

We can run and stop the robots at any time using the mobile orchestrator, which has helped us while we were on the go.

We can develop own activities using Visual Studio and integrate them into the UiPath Studio.

We have found the following features valuable:

1. UiPath Studio for developing robots.
   
2. Orchestrator is used to centrally control the robots and view the visual statistics for each one.
3. UiPath Academy provides free courses to learn the solution.
4. The UiPath Community Edition is a free version of Studio that helps everyone to learn and practice with the tool.
5. UiPath Connect & Go offers custom activities developed by people around the globe.

The aspects that we feel can be improved are:

1. Sometimes the tool is not stable with the selectors that are used to identify the different windows within the Windows operating system.
2. Backward compatibility is missing. After upgrading to the new version, some activities won't work.
3. It would be nice to have this tool support other operating systems too.
4. C# is missing and it currently supports only VB.Net. We would like to see C# support in the next release.

We have been using the UiPath tool for more than three years.