UiPath Platform Reviews

It is for automating tasks that are not meaningful for people to do, tasks that are menial and repetitive. The University of Copenhagen, where I work, is an old institution and we have a lot of different legacy systems that don't work well together. So, we have a lot of people doing administrative tasks that depend on moving data from one system to another. We use UiPath to automate these repetitive tasks and make the robots carry them out, so our people don't have to.

For example, in the case of our most recent robots, there were a set of tasks where three people had to print out 3000 PDF pages, then sort them into seven different piles, then sort those different piles into three different piles each. Afterwards, scan them and send them to different systems. We made this better. Instead of three different people taking a whole day, we did it in three minutes. This is an example of a very concrete, administrative task based on legacy systems, and we made it simpler. This was a huge improvement and positive thing for our company.

It is very easy to make beautiful, clear, well-documented workflows that clearly reflect the process. This is an achievement that is not always feasible with regular code. Even though each activity in UiPath is like a line of code, the user interface in Studio and the use of states, flowcharts, and sequences make it so easy to understand the overall process and get an overview of what is actually happening.

UiPath is easy to use, and it CAN be used by non-programmers, but it is even better to use for programmers. It allows us to make very robust and effective solutions because we have all the functionality of the powerful .NET Framework library within reach, all while the UI makes it possible to create truly beautiful solutions.

I would like UiPath to have a build-in method which informs the robot's process owner how it has managed its transactions and performed through the night. If the robot had a process that was set up for a 100 transactions, and two of these transactions had an application error, four had a business error, and the rest were fine, I would like a straight up method for the business owner to login somewhere and see what the robot managed to do and not do. There should be a method for accessing and logging into Orchestrator and see the logs for only one process, and this log should be presented in a way that makes sense for non-technical people. 

The stability is good, I've never encountered any major problems. UiPath works with websites and systems which are famously unstable, but it gives you the tools that are necessary to deal with hiccups and if something is not stable. So, if you add proper error handling to your robots, it works.

Out of the robots that I have built, three or four have had to perform on several machines at the same time. I haven't encountered many scalability problems, but then again I haven't built robots to perform on a 100 machines or anything near that. 

The initial setup was quite complex. I was not in charge of the task, but my colleague set up the whole infrastructure and mentioned some problems. He corresponded with the support team, and they did figure it out, but the setup guide was definitely more complexly written than it should have been, and some things were written in the wrong order. So, there were some hiccups in the implementation.

In our company, RPA doesn't necessarily mean less people will be hired or people will be fired. We probably won't see the ROI in cash. It will help with workplace productivity, and job satisfaction, though.

We were looking at Blue Prism and UiPath. 

UiPath is nicer to work with. The developers especially wanted to work with UiPath, but the business team was looking more at Blue Prism. However, UiPath was better for the slightly larger robots, which is good for a lot of Unattended Robots.

From what I have seen of Blue Prism, UiPath is both more aesthetically beautiful and stable. Based on .NET, UiPath makes sense as a solution.

Start small and make time to do things right from the start. The infrastructure and developer culture can vary massively from one RPA team to another, and it is really important to establish healthy code guidelines, test and operation manuals, etc. from the start. At my current company we are just starting up, getting everything right, which is very exciting, and I can see how different (and better) we are doing things that at my previous employer.  

Most of the time, I am a developer. I also have to develop some best practices, but a lot of the time, I'm working on the application and creating Unattended Robots. We have a large amount of old school manual processes which we need to automate, because we have a lot of full-time employees just doing boring stuff. 

I started last year, so I am a bit fresh in the organization. We have two people: One who analyzes and other develops.

I am using version 2018.4, which I find easy to use. We can see some major changes with each version. The IT department sort of hates that I come by every quarter of a year and want an upgrade, but it is very much worth it. There is a lot of stuff happening out there, and it's dangerous to be left behind by a few versions. 

We have a few people who are very happy to be relieved of their (almost) full-time job of processing customer applications, then processing those applications further along into the company and having that be their full time job. Now, these employees are able to do some more enlightening stuff.

The automation technology is mainly in the financial involvement. We also supply a lot of the power for users. We have a lot of documents which have to be signed and processed, and in those areas, it's nice to have automation and easy to see the benefits.

The seamless integration with programming underneath, so if you choose to, you can get a bit technical with stuff. If there is something missing, you can make it yourself. 

The increasing amount of possibilities in Orchestrator to control robots and schedule them, with the possibly of a dynamic schedule in the future. In addition, there is API access to Orchestrator.

I've seen the roadmap. It looks like some of my wishes are in there, such as the debugging of the last X amount of savings before the robot fails. 

I would also like more script access to the flow of activity, so we can try to see a text version of what we have in the user interface.

Most of the time, the product boils down to making something that works by itself. 

I haven't encountered any real issues with the stability of the product. It is hard to evaluate since it works through so many systems.

We haven't had that many scalability questions arise yet, because we are still in the process of getting people to adopt this new technology. I have looked at the features, and it looks promising.

We have a plan for licensed upgrades, which is a straightforward, easy procedure. This is based on our knowledge from migrations of earlier versions.

We started out by going through the few basic certifications which were in the UiPath Academy a year ago, though there are more now. Even though my coworker is not a developer, he just wanted to have insight into how you use software, so we both did it. 

The UiPath Academy was very good. It tries to help and provides a sort of education not from where somebody is attempting to sell you something. While you are sold product, you push yourself to pass the courses to get to the juicy stuff, and it is on your own accord.

This was a new product for the company. Leadership though this was a good place to start.

The initial setup was complex, which was done by the consultants. After that, we adapted the product a bit, and it has been pretty easy.

The initial setup for our virtual environment was straightforward, as was the installation with it. Afterwards, we were up and running with our virtual machines.

We originally used a consulting company, Deloitte, but then decided that we wanted the knowledge to be in-house.

It has helped eliminate human error. Data quality is a concern, and it helps to alleviate some of our data quality issues.

It has saved the company time.

We use the performance benefits of it to make a case for future hiring of people, so I have great expectations from it. I would rate the current ROI and performance benefits as an eight out of ten.

I heard that they also evaluated Blue Prism. The leadership went with UiPath because it had more transparency, had a better cost, and was more risk-free. They decided to give UiPath a shot before deciding on a long-term solution.

Get buy-in from your leadership early on, because it's very hard to get stuff done without it.

We are only using Unattended Robots at the moment. However, we are very excited about Attended Robots getting a foothold. It is something that we want to investigate more, since Attended Robots are feasible in our organization.

We automate mostly finance processes, which is our largest area. We also automate some HR and logistic IT processes.

We hear from the process owners that they are very happy with the lead time and data quality, which keeps getting better. 

It is very easy to use, and you still have a lot of possibilities to modify what you are trying to do and achieve. 

We would like more API integrations, especially more API connections to SAP. While this is on the roadmap already, activities and packages with more automated API connections to other software or platforms would really help us.

Documentation-wise, UiPath could get a little better.

The support that we are receiving from UiPath is superb.

We are using the UiPath Academy. We also have our own development standards. When we are recruiting new developers, we first have an introduction of our own that we make. It's mostly to Orchestrator and our environment, then we set them free at the UiPath Academy to do training there. Afterwards, we do some additional training to our standards and best practices. So, part of our training is in the UiPath Academy, and we are using it. We have been very happy with it. It's evolving all the time, which is really good

One place that we struggled was when we were uploading the software. UiPath was helpful with getting started, setting up the server, and installing the robots. All that went pretty smoothly. Every time, when we have upgraded, except for the last time, we have struggled. We did not do it right once. We always had to retry, get some support with it, and the documentation was a little lagging. Therefore, we really struggled with upgrading. It's getting a lot better now, but this has been one place where we have struggled.

Annually, the product saves us 25,000 hours. Everyone is satisfied with that.

We have had our contract with UiPath since November 2016. 

We have had a few presentations from Kapow. They have dynamic licensing, which is something that we would really like to have, so we could scale up at peak hours or peak times of the month. This is when we really need to throw more robots at some processes. To my knowledge, that is not possible with UiPath at the moment. Though we are not considering switching at the moment.

There are multiple use cases:

Automation of manual Excel workflow: Previously, our account support executive used to manually prepare client Excel sheet using a variety of third-party integration. Data flows manually into Excel and is then exported manually to a different system. What a fantastic work done by UiPath using integrations and webhooks. We almost saved 24 hours of weekly effort per employee and imagine we have to do this every time of the year and for hundreds of clients.

Automated data entry: Automated data entry of generated invoices was made so much easier with OCR recognition that we are trying to explore it in more departments like human resource and support systems.

It helped us in achieving the following efficiency and compliance:

• Cost management
• Drive innovation
• Creating internal/operational efficiencies
• Improving business process outcomes
• Improving business process agility.

I am an automation expert responsible for creating utilities which help support systems in easing down their business and saving lots of money with redundant efforts. Earlier, it was done using software code, but once I latched on to UiPath, I was overwhelmed with the ease, flexibility, integration, and support provided by it. 

Along with that, UiPath provides the best learning material and easiest learning curve making it one of the popular tools in the market. 

I also found the UiPath community forum very helpful which is a big plus for developers like us. The latest version of UiPath (Community Edition, v2019.2.0) contains a beta version of AI computer vision which we have just used, and I am sure that it's going to kill in the market with such an ease of recognizing UI elements. 

Additionally, now we can also retrieve the header of HTTP requests which was a must use case for our project, and it eased out a lot of re-work.

• I really like to see improvement in IDE for UiPath. There is still a lot of space where the user flow could be made more intuitive. 
• Enterprise support for UiPath is still spotty and is not fully capable of solving queries in a single session. They still require some time to get back on the issue. 
• I also have a suggestion: Don't try to overburden your product, with the early release of so much integration, with bugs. Do thorough testing, make sure it is bug-free, make sure there is proper documentation and make sure tech support is up and ready with known issues.

• Automating web applications is the primary use for my organisation.
• Also, data scrapping is another main usage.

• Improvement in the way of quick and fast automation development.
• Functional testers have changed as an automation test engineer.

• Web automation is the most valuable.
• Locating an element and adding the conditions are very easy compared to other tools.

• Everything is awesome; no improvement is needed at this stage.
• One word to say about UiPath is, it is simply great.

Excellent.

Excellent.

It has the best service.

Earlier we were using Selenium for test automation in our organisation.

The setup is simple, nothing complex to understand.

I didn't implement it through vendor teams.

Good.

Reasonable pricing. If there can be a decrease for individual learners/developers.

Before taking part in UiPath, I have used the trial version of Automation Anywhere.

If mobile automation is included in UiPath, it would be great.

I have tried the RPA tool for the first time and I already love it. How easy it is: you can do all of the daily tasks which you repeat at one click. 

Primary use case: educational purpose and automation for content writing.

Secondary use case: additional content writing and data scraping.

 In our institution, we have to submit a weekly report for the tasks we perform daily. It is very easy to scrape the tasks we do from our academic portal and embed to the report.

Now we can make more assignments and content. On running a robot with a keyword, it writes the content and we just have to sit back.

• Data scraping and web automation
• Citrix automation
• Easy integration with all windows applications.

1. Community
2. Own software stack exchange platform
3. UiPath Go! should be more reachable to developers.
4. Incentives should be given on publication on UiPath Go!

As a system administrator, I have to create a roundup report before the office begins and at the end of the day. The report consists of statuses of each thin client we have. The robot does all the stuff in just 2-3 minutes, saving our 1-2 hours of time done by a dedicated person.

• We can now run multiple robots remotely and easily so as to prevent daily checkup failure. 
• There are multiple testings run on each console by UiPath.

Orchestrator, data scraping and academy by UiPath are the best of all, for someone having cloud knowledge can exploit the technology.

• Linux environment is needed.
• RHEL/Ubuntu support is needed
• More academy and learning tutorials are needed on Udemy or edX.

I have been using UiPath for quite some time now, and I have realized that it is one of the best automation tools out there. We primarily use this tool for automating our business processes and removing repetitive work with the help of automation. The most interesting part about this (easy-to-learn) tool is that it is accepted almost everywhere in the RPA industry. There are a lot of activities in this tool which will help you automate processes easily.

It has been quite some time since we started using UiPath in our organization and it has done nothing but help us. Everyone in the company now is learning how to use UiPath. It has helped us to automate a lot of menial tasks, such as salary processing and resume organization. There are areas where the employees can focus more on now. All of these things help us manage our organization better. 

The most valuable features of UiPath are its activities. There are an immense amount of available activities in UiPath. These are the building blocks of your process. Since UiPath is new, it is constantly being updated, and new features are being added accordingly. 

As of now, UiPath is headed in the right direction, but in the future, it needs to introduce its users to the field of AI and machine learning. These are the new features that should be added in the next version of UiPath. As for the drawbacks, UiPath should really add an option to change the toolbar options which would make it more user-friendly.