UiPath Reviews

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.

The first process automated by this solution was downloading reports from SharePoint and injecting them inside an Excel sheet that was filled with formulas. This was done in order to produce output files that are then uploaded back into SharePoint and sent by email using Outlook.

The environment was Windows 10 (desktop), and the process uses the user interface to do all of the SharePoint tasks, except for the Excel ones, which are made in the background.

UiPath helped automate a task that was very redundant, especially in recurrent time slots that present a heavy load (monthly or trimester). Once the robots are ready, the scaling of the workforce can be as easy as multiple clicks to add additional workforce for the same task.

As a developer, I use a lot of features included in the Studio or the robot products, but here are few that prove to be very helpful:

• UiExplorer: This proves to be helpful in the case of trying selectors without the need of starting to work on the project itself, so it helps us estimate how many days we would likely to spend on the process and help the client decide if the ROI is worth it, or we need to consider other automation opportunities.
• Workflow Analyzer: before testing to see if the process is working or not, there are a lot of checks that we have to do and a lot of rules to respect. This feature helps keep track of every element that exists in the workflow and gives us some insight into how we can alter some variables, sequences, and names to have better production quality.

The performance could be improved, and it is especially noticeable on older hardware.

We have been using UiPath for more than two years.

The enterprise solution is very stable since there are no automatic updates and the solution gets installed into the "program files".

It is very scalable, especially when using Orchestrator.

I used Blue Prism before switching to this solution. I made the switch because of the community and the support that UiPath presents to new developers, as well as to their ecosystem in general.

The initial setup was fairly simple due to the support online.

We implemented using our in-house team.

In five years the ROI will be close to 300% .

UiPath has multiple plans that suit most businesses that want to evaluate the suitability of RPA in their company before going with full adoption.

Before using UiPath, I evaluated Blue Prism and Automation Anywhere.

It's hard to spot something that should be improved or added after all the efforts made in this year. If we have to say something negative then it has to do with slower performance on old hardware. However, this is very rare in a client site.

The experience overall is just so complete, with no obvious cons.

I am a developer so I primarily use Studio. Once the bots are developed they go to Orchestrator.

We have a combination of different use cases. Sometimes it deals with Outlook, the Microsoft Office Suite, or certain integrated web applications. You build a solution to integrate all of the applications that are part of the same process.

We do not run our automations in a virtual environment at the moment, but we are currently evaluating how we can do this.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. The majority of the simple tasks are done through recording, which saves on our development time. You just record the things that you want to achieve and then customize to get it going.

Since I was new to the product, I used the training. I took the developer training, as well as business analyst training. On a scale of one to five, judging how beneficial it is, I would rate the training a five. It's truly very beneficial because you can just touch base with the actual tool and get it done.

From the point that we purchased our UiPath license until we had our first robot was approximately six weeks. This was a complex use case and it worked well, so it was a good proof of value.

Prior to using this solution, everything was running well, though users were facing challenges because they were spending a significant amount of their time correcting things that were misrepresented or not done correctly by some other part of the team. The consultant is supposed to correct or manage all of the changes, and it was not only taking a long time but not on their to-do list for the day. It is this extra time that this solution is being used to address.

In the pilot project, we have seen proof of value. However, it is not in production yet, so it is too early to see how much time this solution will save us. The people whose jobs will be affected are looking forward to this solution because we are expecting to cut their mundane tasks from eight hours a day to two or three hours a day.

In terms of eliminating human errors, I don't think that we have seen any difference.

The most valuable feature of this solution is the training that is available. You can just access the resources.

There is a Community Edition of this solution, which is a plus. Some other vendors do not offer this or have just started offering it. Accessibility is the biggest thing.

I would like to see more features included in the AI Fabric. This is the biggest thing that I am looking forward to.

With respect to the stability, on a scale from one to five, I would rate this solution a four. There are certain features that are incomplete and they are still working on, such as computer vision. 

We currently have about five people involved in the RPA team. It's the kickoff stage for us, and more like a COE.

We did not use another RPA solution before this one.

We decided to invest because necessity is the mother of innovation. We were seeing our consultants spending too much time in processing certain areas of the business, and we wanted to find ways to make their lives easier and improve the processing.

We had Roboyo assist us, and our experience with them has been pretty good so far. On a scale from one to five, I would rate them a five.

This is just a pilot project so ROI is not really in the grid. We hope to have a good ROI on the solutions that are deployed using UiPath.

I look forward to trying the better features that will be released in upcoming versions.

My advice for anybody who is implementing this solution is to not only automate the process but redesign the process. If you have steps one through ten then you don't simply automate them "as-is". First, improvise your process and then try to automate that. It will save time and money.

This is a good solution and I am looking forward to the new AI features.

I would rate this solution a nine out of ten.

We are using Studio and Orchestrator.

We use this solution for financial analysis, accounting, invoice processing, and other menial tasks.

We run automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. The ease of use comes from many things including the user interface and the coding.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. I feel that you can have people who are directly thrown into the training, but sometimes it is difficult for people to pick up on topics that are not related to the processes that they are dealing with.

From the point that we purchased our UiPath license until we had our first robot was approximately two weeks. The implementation was straightforward both on the setup and the development side.

This solution has a big impact on what we do. It gives us a bigger impact on a decreased employee base.

I can't say exactly how much time we have saved across the company, but I can speak to my own processes. We save about one hundred a twenty hours per week. This savings comes in part because it is making people's jobs easier.

In terms of eliminating human errors, our error rate has improved since automation. I would estimate we have twenty-five percent fewer errors.

The most valuable feature of Studio is the ease of use for developers who do not have a technical background.

The user interface is good.

I would like to see anything that can increase the reliability of the processes. It can be a really challenging task and there is certainly room for improvement.

I would like to see more selectors included in the next release of this solution.

With respect to the stability, on a scale from one to five, I would rate this solution a four. It's fairly stable and it's making good improvements. In some cases when you get an upgrade package, you can lose functionality that previously worked with some processes.

We have about six people involved in our automation program.

The technical support for this solution is good, but seeing the functionality break that worked in previous versions can be frustrating.

For my processes, everything was done in-house.

We have seen ROI with this solution. We began to see some in about a month, but a lot more after two months and greater.

My advice to anybody who is considering this solution is simply to do it. Dive right in. Gather as much information as you can about the processes, then use the community in place to help.

This is a good solution, but there is always room for improvement.

I would rate this solution a nine out of ten.

We primarily use the solution for insurance processes where we have redundant activity and we have pain points for our customers. It allows the employees to do more insightful work.

As we are mostly using unintended robots right now, the main value we see is the ability for the solution to take away the redundant tasks. That's the key value. But there's tremendous potential in the attended or hybrid model. The value I see there is allowing people to automate partially or at a time. Whether that's something that we've identified clearly now or something that we look at in the future, I think that lives in the attended or hybrid piece. It would be nice to just see what more we could do and what more value we could add to the business there.

On a scale of one to five, I would validate the ease of use to maintain our processes almost at five now that the solution has introduced Studio X. Studio X has the potential of empowering people to prototype and then pass along more qualified information. It's a game-changer.

Right now just being able to capture process, even without Studio X, let's say we video it or we capture it by way of a traditional Vizio diagram, enables asking work instructions, etc. It allows us to capture and standardize what people are doing as well as take steps toward optimizing processes in general. It's all good stuff.

I wouldn't know without looking at the actual metrics, but I would say in general our pay projects probably cut time by factors. Simply because people do things more slowly, more inefficiently. They're interrupting where the bot is not. That's the reason why we love it so much. The potentials of cost and time savings and the possibility of really having people get some of their time back is great.

We haven't had any problems that make the solution look unstable. I'd give stability a rating of four out of five.

As far as stability is concerned, I'm not sure what people who have deployments of hundreds or thousands of bots are seeing in terms of stability. We're small. For a small implementation, we've had a few hiccups and a few concerns where I would say, how can we triage more quickly, or how can we understand what we've caused more quickly? How can we implement strategies for redundancy and business continuity management? What guidance is there from the company on that and how can we be very transparent to our customers to be clean, concise and clear about that? 

I've talked to a lot of the technical support team. They all know that we're really happy with their responsiveness. We were really happy with the product and we're really happy with them. Just continuing to get the guidance, meeting with them, considering strategies and having them support us has been great. 

In this day and age, RPA is the appropriate tool for certain issues where a lot of times I think a lot of firms, not just ours probably go, "Hey, we don't need a longterm solution that will last forever, but we do need something that's going to automate this process and is going to take this pain point away from the business and this appeases that need." I'm not sure if that's specific to any one certain company; that's just the way that people approach it.

I'm not quite sure the exact reason why our company chose to automate. It was decided before I joined the team.

Implementations from process assessment through actually bringing something to production takes about three months. We'd like to be at six weeks like everyone else. But right now, we're at about three months.

It'll be more straightforward in the future now that we have tools like explore apps and insights. 

The complexity of the project informs the complexity of the implementation. We are an IT services company. We have a very standardized kind of approach to testing and bringing things to production, so I don't think that's terribly complex. It's kind of business as usual. We recently brought a project to 10 productions that had three parts to it. We staggered the implementation that typically might be more complex than what other people are doing. The complexity of the project introduces complexity to the implementation, which is fairly straightforward.

We have a partner that assisted with implementation.

The performance benefits are usually pretty quick. The process assessment that we do that hopefully determines the processes that we would pick, allows us to see ROI fairly soon. I'm not sure what the timeline is on that exactly.

I'm sure our process probably looks like a lot of other companies. We go and look at not only one solution but also its competitors. We look at the top of any certain field and make a decision based on what fits the need the best. 

My understanding is the solution is deployed on-premises.

We also run our deployments in a virtual environment and we have the potential to do hybrid things as we have more processes that are in the pipeline that we must review to see what our roadmap looks like going forward in the future. Our experience with automation within virtual environments so far has been fine.

In terms of the UiPath RPA Training Academy, I've taken a few courses. I've also done Academy live and watched tutorial videos. The UI path engineers and customer service managers, as well as some of the directors that are local to our area, have been very helpful in providing this information. I fully intend to continue to do that and as long as it's available. If I were to rate the training materials, I would say the training materials are probably a five out of five rating. There's a lot of information there.

I would suggest others give the solution a good hard look to see if it works for them. Hopefully, for others, it will be a successful product and a useful tool.

Overall, I'd rate the solution eight out of ten.

We have two customers. One is in the insurance industry. We are implementing it within our own company to automate HR and finance processes: back office. This is the same thing with the customer: back office. That's the focus.

We are using Studio, Orchestrator, and attended bots. We are not using unattended bots yet.

For one of our clients, their intent is to create a bot because one of their key folks was retiring. This person had a lot of knowledge of the processes and how things happen. So, the idea was to create a bot that helps. They want it to do 25 percent of most of the work, and this person would just validate instead of training somebody new to do the job. Their idea was to not hire for that position anymore. Instead, if the person is just doing validation, 25 percent of that load is then spread across their current staff.

It is easy to use. That is definitely one thing that attracts people. 

I really like the feature that you get to record actions. I wish that feature was a bit more advanced where I could build more automation. Sometimes, you have to stop the robot because the robot doesn't get the level of detail that I am expecting to see in the automation. Then, you have to stop the bot, and stop or break the recording. While it's nice in creating a first sort of brush off your automation, I wish it would just go a step further.

I really like the new products that were announced here. The apps have a lot of potential. I'm interested in learning more about that in the next few months. The same thing with StudioX. Although, it would be interesting to see if they're more business-friendly or not. While UiPath is advertised as a low code platform, you can't put it in the hands of a business user. They have no idea what some of the features are. Some things, they need to have extensive training and be tech savvy in several things before they can go there.

Several of us took training using the UiPath Academy. I thought the UiPath Academy was very intuitive and easy to use. I would give it a five out of five rating.

When you are tech savvy and been trained, it is a four out of five for ease of use. Having that automation recording feature operate better and capture more of the automation that you're trying to build would make it a five. 

With the new products that were announced, UiPath closed a few of the gaps. I can see how they could expand the products into other areas. There is potential there for some workflow capability. I know this would be going beyond RPA at that point, but having one platform that does a lot of things would be nice. Because as it stands, when you need to do a workflow or approval process, you need to send this out somewhere else. There are things the bot can do, but I can see some of that functionality already showing up though with the tasks and apps. However, I would like to see more. That would be good.

Moving bots to the cloud would be the next good step. The new product has Orchestrator in the cloud. I think moving to bots to the cloud could also be next along with having Studio in the cloud where you can do everything in the cloud: Deploy and run your bots from the cloud.

It is pretty stable. I would rate it a five out of five.

I haven't used the technical support.

We learned about this stuff about two years and a half ago. We started exploring it, then we decided to take the plunge and try it out. That's how it came about.

The initial setup was pretty straightforward. 

It took us about four months from the initial purchase of UiPath to putting the robots in production. With our first deployment, we made a lot of mistakes. For us, it was like the first time you do something, you don't know exactly what you're doing, you just do it. Then, the second time, you're like, "Oh, now, I can go back and do other things differently." With us, it was very much like that. We learned sort of on the job.

We did the installation ourselves. 

I didn't do it, but I know that the people that did the installation didn't have any issues with it. They didn't need to open a ticket in particular or anything like that. This tells me that it was fairly easy. 

We have saved steps and time from people doing their jobs because they're not doing all this crazy validation anymore.

We evaluated the top three. UiPath at the time was number three, Blue Prism was number number two, and Automation Anywhere was number one. So, we weighed them out.

I liked some of the functionality from Automation Anywhere. The recording feature of Automation Anywhere was much better and easier to use than UiPath. Although, I haven't seen the new Studio. In 2019, maybe they changed some things in there. Regardless, the Automation Anywhere tool seemed easier to use. But, in terms of partnership, they were not a good fit for the values of the company. Those things all go into account when trying to partner with somebody. That's why we decided to go with UiPath.

Some of the features in the software looked the same between Automation Anywhere and UiPath. Blue Prism seems very hard to use. That one we kind of killed on the spot. Between like Automation Anywhere and UiPath, it was more about how the company's vision, and where things were headed. All of that sort of helped. So, we were at that point that we were not really looking at the software anymore. We were looking at other things. That's how we ended up here.

With the new additions that were announced yesterday, I'd probably give it an eight (out of 10). I still would like to see some other features, which I know UiPath would start crossing into BPM a bit when you start talking workflows and things like that. However, that would be a good next step given their market share, customers outreach, and beyond API and some partners that they have today.

UiPath is best at its core and with the help of plugins from UiPath and community you get solutions to a lot of problems out of the box. I have tried couple of more platforms, but the easiness, diversity and flexibility that UiPath provides is unparalleled. 

In the recent top 50 enterprise application at g2crowd, UiPath is at 18th place and topmost in the automation platforms. 

I have done quite a lot of different real-time projects with UiPath. In one big project, there was a lot of loan applications from scanned documents. We used Abbyy Flexicapture for reading OCR and ICR text and we read it very accurately. It really boosted the moral and now we are automating the whole CAD department of the bank. 

Now we are looking forward to more complex processes and try using the ML and AI into it.

RPA is our bread and butter. We have implemented projects in the telecom and financial industries. 

A good example was when we implemented a network process in the telecom sector. The time for that process was seven minutes, then by implementing the RPA, we drastically reduced it to 40 seconds. The process involved worked on four different applications. Each application required a secure login, and the speed was due to the websites being hosted on the Internet. It did not require any internet connection when we implemented RPA on-premise, and used complete network and system resources.

• The ease of the processes
• There is no coding at all required to implement a complex business process. If you have some programming background, it will help you. However, if you are a business user, you can still develop simple processes.
• The automated recording helps quite a bit. You record a complete business process along with human interactions to the desktop or web application. You can easily manipulate them. Once you are done, you have a complete recording of the interactions, which you can use to tweak your requirements.

You can't write small snippets of code. If you want to do a single code snippet, this is not available by default. For example, if I want to do some date conversions, and that date conversion requires different variables to be available in the context, but they are not there. A small snippet of code change should be available out-of-the-box. This will help me in the long run. I can create activity out of it. Support for a little bit of in-line script should be there.

There aren't stability issues, though it should have better RAM and cores. When it's overloaded you get considerable problems.

Scalability is one bit which should be properly planned at the time of license and planning. For tight budget projects, you have to be very precise in the runtime execution requirements otherwise, you might face issues.  

Tech support takes time replying to queries. The more you go to the community, the more likely you will get replies. Therefore, tech support should be improved.

The initial setup was very straightforward. We were up and running in approximately 15 minutes. UiPath is the best of breed in the market for setup.

Licensing is one of the big issues when I have been doing some pre-sale activities. One robot price licensing is quite high with UiPath. They should provide some discounts to partners so we can spread the product easily in countries, like Pakistan and other areas in the Middle East. Licensing should be reduced and price should be cut down a bit.

We also evaluated Blue Prism. We went UiPath due to the community support.

It has a lot of community support with a lot of help available. It is a very mature tool.

The academy for UiPath is very good place to start with UiPath. It is easy and the learning curve is quite low.