UiPath Reviews

I use UiPath to reduce any data entry, report generation, or anything where UiPath can help avoid human errors.

The solution is very user-friendly and easy to use. It comes with pre-built automation. The tutorials are very helpful. 

I have been working with the product for six months. 

The tool is stable. 

UiPath is scalable. 

The tool's support is helpful. 

I use UiPath to reduce human errors during report generation or data entry. Simple errors can cause delays down the stream. 

The product has helped us save hours, which can range from a few hours to tens of thousands of hours. 

UiPath has helped us increase accuracy. It is helpful in data validation. 

I rate it a ten out of ten. 

I use it for RPA in bank reconciliation, credit card operations, retail banking, vendor invoice management, purchase order matching, and employee onboarding.

It helps to minimize the on-premises footprint and speeds up and reduces the cost of digital transformation. It also reduces human error and that reduces costs and makes systems more reliable. 

UiPath can also free up employee time. It depends on how many automation initiatives you run, but you can probably automate 20 to 30 percent of tasks.

Overall, the most valuable aspects are the automation, UI navigation, and orchestration.

It's fairly easy to use and automation can be done by relatively junior people. It's a low-code platform, so it requires a little bit of scripting but nothing too crazy. A business analyst can use it in most cases.

We're an implementation partner, so we don't use it for ourselves because we're too small. But for our client base, it enables end-to-end automation. That's a very important aspect, especially in banking where there is a lot of competition, the margins are low, and operating costs are high. They can't make any mistakes. That requires them to have an automation solution that does manual and repetitive tasks for them. It's a cost imperative.

And being part of the UiPath user community is a positive. I have also done a couple of the sales-oriented UiPath Academy courses. They are really easy to consume and they are free for partners and they're very business oriented.

UiPath is not easy to work with, as a vendor, from a partner perspective. They are difficult to deal with.

I have been working with UiPath for two years, not as an engineer but in business development.

It's very stable. I've not heard of any major issues where the system collapses.

It's scalable. You can throw more and more robots at it.

Technical support from UiPath is slow but good enough.

Neutral

ROI depends on the customer and what they need, but you can definitely have a return on investment of 300 to 400 percent within about three years. It's a relatively quick payback.

They are the biggest RPA vendor with the highest market share. They have a good product and the company seems really innovative. They're branching out into AI and process mining, et cetera. Generally, as a vendor, they're the strongest one in the mix.

My advice is to start sooner rather than later with RPA.

There is a lot of hype around the topic of RPA and customers are exploring it, but they can't do it without partners; at least not the first couple of projects. Deployments with our customers take about six weeks.

We maintain the solutions we create. We normally have a support contract in place for at least the first couple of years. Maintenance, on our side, involves two or three people.

The solution has provided assistance with the removal of repetitive human transactional activities; document to text solutions; complex data extractions; cut and paste operations; information content management. This is either supported in promoting strategies with our business partners, or implemented at our clients, or included in products we develop for our clients. 

We use it in our own operations that have been migrated to other products or solved with coding or third-party software offering solutions to specific needs. Solutions are based on client sites and our clients pay for their own licensing.

The costs involved and the licensing model have forced us to recommend other solutions to our clients and to stop using UiPath internally due to constraints imposed on small businesses (specifically around the community edition). 

For our clients who can afford the licensing costs (Blue Chip Clients), the benefits have been to remove some repetitive activities from the target areas. 

In most cases, where there is a high-value resource impacted by these repetitions, there has been a cost-benefit in doing so, however, where the labor cost is below a certain threshold, the benefits are contained to error avoidance and reliability only with (additional) costs being migrated to support the technology and increasing overall IT OPS costs - particularly now with the increased fees and current licensing model.

The product as a whole is a valuable contributor to efficiency improvement. It integrates with ease (although some coding experience is required for higher/involved functions). We use it to streamline and support our customer operations primarily, but also to do internal acceleration on human-dependent (simple) tasks.

Simplification of complex task creation by introducing pre-coded objects is the single most attractive feature of the product. The choice between attended and unattended Bot applications with similar functionality is an advantage. 

Features are on track, however, service and cost models need to be reviewed to be market sensitive and related to the industry. Providing a great product at the wrong price without consideration to the economic conditions of the markets within which it is being offered, creates barriers and another product is sure to fill the void.

Closer integration with machine learning frameworks and matrix processing can be improved and will benefit low-cost/entry-level uptake and activation for some clients. Although pass-through options exist and have been activated, this is not sufficient to create encapsulated learning within the organizations and serves to improve third-party algorithms with added exposure to privacy (information systems security management) risks. 

I've been involved with UiPath since the launch in South Africa with Larc Technologies as the first UiPath solutions partner and reseller for the country.

No robotic solution can ever be classed as stable unless there are no change dependencies. It will always require more support than any other core technology - its the nature of the beast.

Running multiple robots in an environment requires orchestration, which is another expensive modality in the UiPath stable.

Consultations outside the normal service environments are strained, authoritative, and inflexible and there is little consideration for anything outside their immediate scope of vision and there is zero hesitance to move against initial strategic positioning and commitments. 

Neutral

We have been involved with and supported UiPath from the onset. We have also delivered enterprise solutions with BluePrism and Automation Anywhere. UiPath has proven to be capable, but costly and inflexible from a pricing and support model viewpoint.

It depends on the nature of the requirements and can be super complex or super easy. Supporting the bots are always a challenge and supervision (alerts, monitoring) is essential.

We work with excellent vendor implementation teams and have in-house competence in design and delivery. In most customer environments, there are competent implementation and maintenance resources for bot environments. Over the past 5 years, bot development, administration, and maintenance skills have improved, however, there is still a significant gap in proper orchestration and optimization within bot frameworks - which affects the overall cost and effectiveness of automation strategies.

At present, the ROI is negative for us as a company. For our clients, it varies. When all costs are considered (TCO) over a two-year period, financial breakeven is mostly attained with some negative ratios (if it's the wrong tool for the job). 

In most cases, there are intangible benefits. In all cases, IT operations cost increased and, in worst-case scenarios, the business benefit was short-lived as the technology costs escalated and the resource reduction potential was never attained.

HA and DR planning are essential when determining actual resource reduction potential.

UiPath is becoming expensive and will be outpricing themselves if they continue to enforce their current service configuration (model). Many clients have been impacted by the pandemic and instead of assisting to breach the gaps, there is a sense that UiPath is monetizing on the disaster.  

We looked at BluePrism, Automation Anywhere and we are now moving on to Open RPA - a viable option if you have the right skills to plug gaps. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The solution has saved costs for our organization.

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

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

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

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

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

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

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

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

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

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

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

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

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

Technical support has been pretty good. 

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

We did not previously use a different solution. 

I personally implemented the solution at my company. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Overall, I am quite satisfied with the product.

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

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

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

In our organization, we are using UiPath as a service model. It is an on-premise model where UiPath is deployed on-premise. We are not using it on cloud services. 

We have a center of excellence that has been set up to communicate with UiPath for all the licenses, for all the tools, et cetera. Individual teams will connect and will communicate with the development team to get those licenses. For the team structure, we have a COE manager, and a COE is again communicating all the relevant information to the teams.

First of all, you would have to go and submit an idea to the COE team. The COE team will review and see this is the correct candidate for our solution and we can leverage it as automation. They provide us with the required licenses and the cycle continues.

The use-cases for the UiPath are limited. For example, if you are coming from a banking background, there would be use-cases it comes from the data solutions. If you are coming from an insurance background, would have use-cases where you would have benefits that are being reconciled. Healthcare might be dealing with patient data, et cetera.

If I talk about the support teams, in general, the use-case for the UiPath is as a ticketing system, where you have a lot of data to add to the queue to remove the need to add items manually.  

UiPath has the ability to implement with multiple systems. You can extract the data from any other application, click the data to enter the specifications, and start the automation cycle. That way, you have a technology that helps you to build a fully automated enterprise.

Our use case depends on the client and their needs. It's specific to their industry. We basically use the product to build automation for them.

We have seen the benefits both in terms of cost-saving, and time-saving. If you are doing automation which a human or an entire team is doing, let's say five hours a day, and there are seven to eight people doing the same amount of stuff, then you can automate that. 

When it comes to automating your process where the company is paying for software if you can use it to make robots that take energy away from repetitive tasks, you end up saving a lot of man-hours - which helps pay for the software.

Savings are measured both in terms of active saving or cost-saving. Then again it entirely depends on the kind of automation you're organizing. 

The most valuable feature of UiPath the process mining. The half capture was a tool that was provided by UiPath in the earliest reviews which simply allowed you to record the operations

It's great for automating tasks specific to business cases. It makes it very easy to do so as well.

The solution offers pretty good analysis capabilities.

The solution ensures there is proper documentation throughout the process.

The product creates a kind of skeleton for developers to help them work faster. 

UiPath is a low-cost platform.

If you are someone who is coming from a business background, and you don't have much coding experience, and you don't want to go through the coding world, UiPath, has UiPath StudioX. With the help of UiPath StudioX you can automate your items to read emails, download specific things, and do other small automation tasks that do not require advanced coding.  

If you are a developer who is more into coding and wants to do more coding, you have Studio and Studio Tool. Based on your level of expertise, UiPath has various levels of product: StudioX, Student, and Studio Pro, for example. It is always good if you have a programming background as sometimes you might need to write a small piece of code, however, it is a comparatively very easy task compared to the other traditional programming languages where you have to write a lot of code to do simple automation.

With the application of AI in recent releases, automation such as document reading can happen faster.

The UiPath app feature has increased the number of automation you can create while reducing the time it takes to create them. Recently, we had a UiPath hackathon which was contacted by UiPath for automation. We went to an NGO, and, for that NGO, we created a solution with the help of UiPath apps. For example, we used to create the invoices that would take seven to eight minutes to manually create. However, with the help of UiPath apps, we were able to do the same path in less than one minute. We have seen a drastic change.

The solution reduces human error significantly. When you are doing a process for more than five hours, you might deal with human error. However, robots don't make mistakes and can run 24/7 without issue.

You do need some coding experience.

AI is not available on older versions. I don't know if it is available in the latest versions of this review. Most enterprises, I'm working with still are at the previous version of the UiPath studio.

UiPath needs to enable more of the features which are available. For example, today, if I have to implement an automation path for the mainframe application, I cannot do the mainframe application without the client. I cannot just do a trial. If UiPath could create dummy applications for the developers who want to try new features, that would be helpful. 

The should be more out-of-the-box models if UiPath keeps adding on. Recently they have added a model in their AI section. However, it would be useful to have out-of-the-box models direct themselves towards plugins. 

You need to continually update the solution as, if you don't, after a few months you won't recognize the product due to all of the new releases. It will be like using a completely new device.

I've been using the solution for five years. It has been a while.

Stability-wise, UiPath can handle the different varieties of stability on the applications you are automating. 

For example, if you choose to automate applications that are expected to change in the next few months, then UiPath cannot help you. That takes an entirely different form of planning. However, the more stable the process, the less likely any part of the process will change, the better UiPath can assist. 

The solution is scalable. If you have to add new functionality to the robots, you will find that is definitely scalable. Let's say you have automated a process and you are getting 1000 tickets only, and then you suddenly get an influx of 10,000 tickets. You don't have to go and run and change your code or anything. Scalability-wise it is just with the click of a mouse that you can handle the change. And, just as easily, you can decrease usage if there are only a small amount of tickets. While developers and coding will be necessary to make it happen, I would say the solution scales extremely well.

I have not contacted UiPath via the contact center. The firm I'm working for has a center of excellence. We do not, as individual developers, directly communicate to UiPath. There is a team that sits in the company that communicates with UiPath, as we're an enterprise. We don't have direct access to the UiPath team.

That said, I do interact with them on the community edition, which I also use, and I find that if I raise a ticket, they listen to my feedback and adjust accordingly. They're excellent.

I have not used any other solution.

The initial setup is straightforward. From an enterprise point of view, from the client's point of view, there are certain restrictions that the company might have in place that could affect the way it's set up. 

The company needs to have a checklist to ensure it's set up optimally.

That said, there are no drivers, no scripts, nothing. Everybody can do it. You just have to click on the approve button, select it, and the job is done, that's it.

We do our own implementation strategy, however, I am not directly involved in what exactly has to be implemented. There are separate teams for that.

While I can't speak to how much users pay for enterprise-level editions, I can say that their community version is quite good and free to use. I've used the community license for the last five years and it's been great.

I do mostly 90% unattended automation. I have created only one attended automation for a client and that was a specifically requested requirement. That was a bit difficult to automate. 

One piece of advice to everybody who is working in UiPath would be to practice and keep UiPath updated as the technology is growing and it is getting updated frequently. If you do not keep yourself updated for three or four months, you'll be dealing with a completely different tool. Keeping it updated allows for the gradual changes to come in in a way that a user can handle, as opposed to having to re-learn or re-discover the product if you have let updates lapse for months.

I'd rate the solution at an eight out of ten.

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.

We use UiPath for building business cases for customers and internally building RPA competency within my department. Our organization is just starting to implement RPA. As a business consultant, UiPath is our chosen solution for RPA implementation. 

UiPath has made it very easy to create business cases to showcase to executives the functionality and benefits of RPA. UiPath was instrumental in my initial business case, as they came in and executed the proof of concept. That was a huge help and my customer was very pleased.

I find the community most valuable as it allows you to find your solutions and people to help you.

I like being able to save components to reuse for other processes and not having to start from scratch each time.

I appreciate the simplicity of the interface as I am learning to be a developer.

I would say a better layout or interface between the Studio and Orchestrator tools would be nice.

I have been using UiPath for five months.

We did not use another solution prior to UiPath.

I'd advise others to consider sharing the costs after ensuring they understand their expectations for utilizing the capacity of the robots. Share the cost if you forecast not utilizing the entire capacity.

We did not evaluate other options before choosing UiPath.

There is already a new release and I am pleased so far. I think UiPath has done a great job making resources and tools available as well as providing opportunities for learning directly from their company and in the same quality as their employees.

I am a developer so I primarily use Studio most of the time, and when the bots go live, they move to Orchestrator.

We have a combination of different use cases. Sometimes it is dealing with Outlook or the Microsoft Office Suite. The idea is to build a solution that integrates all of the applications that are part of the same process.

We are not currently running our processes in a virtual environment but we are currently evaluating how we could make it work.

Everything was running well but the users had some challenges because they had to spend a lot of their day correcting the things that were misrepresented or not done correctly by another part of the team. The consultants had to manage the changes which were taking a lot of time but weren't on their to-do list for their day. UiPath is helping us save that time. 

It hasn't really helped to eliminate human errors. The processing time is dramatically reduced. It makes it easier for consultants to make things right. If they spent eight hours doing a task, it now takes them two. 

Compared to other solutions, training is very valuable. You can easily access the resources. There is a community edition which is a plus and something that other tools don't offer. Accessibility is the best feature. 

I would rate the solution's ease of use as a five out of five. The majority of tasks are done through the recording which saves development time. You just record the things you want to achieve, customize it, and get it going. This reduces development time. 

I have been using RPA training since I was new to the product. I did the developer training. I would rate it a five out of five. It’s very beneficial. You can just touch base with the actual tool and get it done.

It hasn't really reduced human errors but it has reduced the processing time. It's easier to make things right.

I would like to see more of the AI Fabric domain feature. 

It interacts with so many products that the robot itself becomes unstable.

I would rate the stability as four-ish out of five. There are some features that they are still working on. There will be better features in the upcoming versions.

We have around five users. We're in the kick-off stage so not many people are involved. 

I have not needed to contact technical support. 

We knew we needed to invest in a new solution because necessity is the mother of invention. We saw our consultants spending too much time processing areas of the business, so we knew we needed to evaluate new processes to make their lives easier. 

We chose UiPath because of the accessibility. It's easily available and widely used. 

It took us around six weeks from when we purchased our first license to having our first Robot in production. It was not a complex process.

We used Roboyo for the implementation. We had a good experience with them. I would give them a five out of five. 

ROI is not on the grid right now. We hope to have a good ROI. It's a proof of value and it's not in production yet. 

With the existing features, I would rate UiPath an eight or nine out of ten. Once the new features come in, I would give it a ten. They keep improvising. 

I would recommend not only automating the process but redesigning the process. It's not just about automating steps one to ten, you need to improvise your process and then try to automate that. Automating the steps as is won't really help and you can end up spending the same amount of time and money.