UiPath Platform Reviews

We are mostly using it for HR processes. We have two departments: Accounting and HR/Payroll. However, we mostly use it for payroll and travel.

We are only using Unattended Robots. We need to start talking about Attended Robots more.

We moved IT to a business unit, so the business now knows more about IT than before.

The automation technology at our organization is not so mature.

The platform is open, and we can connect it to other technologies. We connect it to SAP using the SAP Connector. We are also using intelligent OCR technology to read receipts.

While the product is easy to use, it is not easy for all business people to use. It needs to be improved to be like Excel, since everybody should have an RPA tool. So, it needs to be easier to use.

It can be stable, if you build it stable. However, you have to know the tools or activities which make it stable.

It can be scaled. We have it scaled for all our customers. 

We are a shared service center. We have scaled to run task by task, which we find easy to scale.

Working with the customer support is easy.

There is a lot in the UiPath Academy. It should be divided into smaller tasks and smaller certificates. 40 hours is a whole week, which is a lot, and most people need more time than 40 hours to complete the Academy. As a baseline, the training is helpful, but not anymore than that.

We did not use a solution prior to UiPath.

The initial setup was not straightforward. With some of the technical infrastructure that we deployed in 2017, we were an early adopter, so there wasn't a lot of product experience. We made a lot of mistakes with it.

We used a consultant for purchasing the licenses and deployment. While we still use them for licenses, we now do everything in-house.

We don't have a money saving initiative. Our goal is to do more with less, e.g., we have taken on more cases without scaling up with people.

We have eliminated human errors and saved our organization time.

We did a PoC of UiPath with our main processes, and it showed good results. 

We did try Blue Prism before during ramp up. They were quite similar at that point, but UiPath seemed like a more open platform with the better possibility of using the best technology available and integrating with it, instead of having an all-in-one system.

We are in the public sector, so we had a public bid, and there were only two.

Just do it. Start with a PoC and do the trial. It's easy for a technical person to look into it. Every person that can do programming can learn RPA in a short amount of time.

It is an open platform where you can do a lot of stuff.

We don't use Citrix. We run the application on virtual machines. The implementation was good. 

The primary use case is to have a platform which allows us to scale rapidly without adding a lot of human labor. We are looking to go global without being dependent on recruiting heavily on back office functions.

We combine this RPA solution with predictive analytics. We are in the hairdressing industry, so we predict the amount of haircuts that we get every month in advance. Based on that prediction, we set up our work shifts based on it. We do that predictably, then we use UiPath RPA to fill in the work schedules for each employee in advance and measure it, since it is really important for us to get an accurate number of shifts based on predictive analytics.

It is fairly easy to use. We are using it with a lot of integrations with separate tools to get the flow of data going.

Valuable features include rapid development and the scale of solution. The most valuable feature would be accuracy: The ability to perform the same job accurately and consistently.

We use UiPath only in virtual environments. If it came out of the box like a software as a service, it would be a whole lot better, especially in our case. All our internal systems are cloud-based systems, so we have no dependencies or legacies in terms of installed software in any way. We could be completely in the cloud all the way through.

I would like to see direct integration with the Google BigQuery platform. 

I would also like an Orchestrator self-service desk.

The stability is as good as the developer makes it.

The scalability looks pretty solid. We haven't been working with it too long, or long enough to see it really scale yet. 

Orchestrator should have better scalability with a better payment model in terms of number of processes that you want to use. Instead, you have one product which covers this size with this fixed price. You're getting a box of options, but you can't really scale it.

We have not really used the support. We did spend a bit of time on the community forum, but that's about it. The community forum is pretty good. This is one thing which differentiates UiPath from the pack: It has a community and access to information.

We did not use a previous solution. We went straight to UiPath right from the get go. 

I have worked with automation before. We saw a rapid gain in terms of automation where we couldn't automate in any other way. 

The initial setup was a bit complex. It could be better, especially with Orchestrator. 

Orchestrator should be a separate solution, straight out. Just sign up and have a heavy solution for it. Instead, we spent a lot of paid consulting hours setting it up on our Google Cloud platform and virtual server in the cloud. That was just wasting money for our organization. It should be its own software as a service. 

We used PwC for the deployment, who was very good.

We've been in production for about two months, and we have seen tremendous ROI. The accuracy of the job was far more valuable than the man-hours spent.

It has helped to eliminate human error by a huge amount.

While it has saved us time, we're a small staff business, so there's not a whole lot of time to save.

Licensing costs are high, but still well within a positive return on investment.

We like the hybrid model, but it would be very costly for us to have one Attended Robot for each person in the organization. Although, it would be nice to have, we don't do many mundane, repetitive tasks in entire our organization. We actually have UiPath to do all the work that we don't do, which means we can think about it differently from the start. If we can consolidate all those tasks on Unattended Robots from the start, then we save on licensing money, which we try to keep as tight as possible.

The main cost driver is developing and maintaining the software. Ensure that you don't spend unnecessary time implementing something you don't know. Get someone who knows it to get it up and running. Let that be the basis of your tech choice. I like UiPath roadmap, and the roadmap of the product should also be very important.

Getting the ROI, which we expected within one month, would be impossible to do with another tool.

We did not look at other solutions. I am managing the system, not developing it. I am a self-service manager for the operations, and I only knew UiPath. Therefore, the cost of implementing something that I didn't know would be higher than the cost of implementing something I did know. Plus, it works for work we need.

The automation technology at our organization is pretty good. We use a set of combination batch/cron jobs for a Google Cloud platform together with some AI automation tools, like Dialogflow, in combination with the RPA tools, like UiPath.

It is a very good product and very much stable. I love working with it. Though, it still has some limitations when it comes to integrations and development. Sometimes, you find yourself in a situation where have to add a bunch of code to make it work faster, or you will be stuck with it dragging and dropping. While this works in most cases, for the 20 percent where you want to add code, it does becomes annoying.

I'm not using it myself. I'm working around it with consultants. I am in network IT. I have seen the product at work and tried it myself. It is sort of easy to use.

From our main systems, it integrates a platform for our citizens, sending them notifications.

We have released on time from the staff for IOPS, which is what they are going to focus on. We are leading in our country in this area. It is supposed to change our thinking about how we should work with newer process and how systems are thinking.

You can integrate it to do many things. We have a lot of different data that comes into it.

Studio needs to be more user-friendly, maybe it could be integrated with an AI.

We want to see more ways that we can use the product. We want to see more actual cases.

We haven't had that many problems. We have had more issues with the products integrating into it.

It does what it is supposed to do. We haven't had any complications in the less than two years that we have used the application, which is quite good.

Scalability-wise, it should meet our needs going forward.

I am planning to use the UiPath Academy going forward.

The application setup is easy, but the process can vary. 

We only use the technical support when we were renewing our license. The process could be easier, as there are a lot of steps.

We are set up for annual licensing and will be taking the time to renew.

We have multiple use cases. We are a distributing company, so we are moving containers around at sea. There are a lot of things that you need to do around that. We are trying to automate to help with our bookings created, etc.

It has not yet routinized our company. While people are at first a little afraid of the product, when they see the benefits, they want more. Right now, we can't keep up with the demand.

I'm not that technical, and the product is easy to go into and use. It is also easy to get started using UiPath. 

There are a lot of powerful box components with the possibilities of creating your own.

The stability needs improvement.

Within Studio, if you are holding down variable buttons (50 or more), then our entire application slows down. So, basic performance could improve.

UiPath could do some optimization of how you search through your process flows. Right now, you have like a small box in the corner, and you don't have an overview when you're searching. Then, you receive this list which you can click around in. That's fine, but it needs to be more visible when you are searching for your components.

We have had some issues regarding stability. The software crashes sometimes, giving us string errors.

The product is very stable out-of-the-box. However, we are in a phase where we are changing our platform, as well. Therefore, we went from a Windows PC setup to Windows Server setup. We went from being one guy to two guys developing this, so we had to do quite a lot of restructuring. 

We aren't on the latest version of UiPath right now. We want to be there, but we are facing issues right now where sometimes our robots can't be rescheduled. The schedule just fails. We have some tickets with UiPath right now. Thus, we are not using the most stable version and are working the issues together with their support.

We have around 450 people in our company and are global in Europe.

Sometimes, the technical support is pretty helpful. They are quick at responding, but there are times when we feel like they have a process that they go through and try to feel out the type of issues. Then, they send you a standard reply. With some of the things that we are facing, it's not like they can look it up in the handbook. Unfortunately, we have unique issues.

We would like more technical help. It would be nice if UiPath would come out to our company. If some of their more experienced developers from Bucharest could look at the problems, that would be great. 

I used the UiPath Academy a bit at the start. However, we can't keep up with our business' demand, so I don't have time to use the Academy. It was okay for learning some of the features. For example, we're starting to use the software, and it is good to have some input that you can use it in a different way.

We have an okay return on investment.

We have seen examples where a user misses stuff which was done and the robot corrects it, and the robot has seen something. So, we are seeing an elimination of human errors.

We use it to automate functions in supply, finance, and HR.

It has saved time and brought efficiencies to our company.

The licensing mechanism allows us to share licenses between different users.

The speed of development needs improvement. They need to make it easier for non-trained people to be able to develop alterations that work the first time. On the development side, the initial development processes should be a focus.

The product is not easy to learn if a person has no interest in the product.

The product is stable. We have not experienced any downtime.

We have not scaled up yet, so it is too early to tell.

The technical support is very good. They are knowledgeable. I always find the right person. It is probably the best thing about the product.

It is easy to use because we receive support from UiPath. Also, the product is easy to train people on and get people using it. You don't need a technical background to learn it.

The initial setup is straightforward enough, not too complex.

It is not oversold. It does do what it was advertised to do.

We use other vendors and find all the products quite similar.

The support that we get from the company is good, and it does everything that we expect it to do. It seems to be a very good product, so far.

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.

Primary use cases would be within the finance sector. We supply financial services for other government agencies. The main robots that we have in use right now are concerning floating of financial periods, uploading reports, commenting on these reports, and so on. We are starting to look at invoice processing, to a larger degree. Then, we have a few quality and control robots which do checks on data quality, customer information, customer carts, etc. 

We are using approximately 20 robots right now for different uses.

We've opted for professional, traditional developers and programmers to do batch robots. We don't use it in our business units. Possibly because we are a government agency, we don't necessarily get enough IT security around the users applying their own robots. 

It is not easy to use in this way because we do use traditional programming skills. We are considering moving some tasks out into the workforce for Attended Robots, etc. We think that this will be a problem for us in regards to getting it pushed out there and still maintaining good quality. However, we haven't tried it yet.

We are able to smooth out peak workloads. Because with a lot of the period closures, like monthly and yearly closures, we work in peaks. Everything has to be done within a few days. When we can prepare a lot of the data and reports through the night, the employees can start on those in the morning. Therefore, we are leveling out some of the workload features, which is one of the main benefits.

Automation technology for us is mainly a way to get around the long-term IT projects. This is the future for us, when using UiPath, to start moving into the AI part of it. In addition, the bundling of the offerings into UiPath is quite important, so we don't have to go to several different vendors. We can try it out on our own and see if this is something we want to do. Then, we might bring in another partner or vendor to do some specialized training, debug the networks, etc. We're never going to get that capability ourselves. We don't have a large IT department nor do we have data scientists. For us, it's important that one or more of these skills are getting baked into the system.

The ability to integrate between legacy systems is the most valuable feature. We use it mainly to replicate manual processes, where you just have to pull out data or pull down large volumes of customer information, in general. We work across many individual customers, who are individual entities or individual databases in our ERP system. We work across about 220 databases. Therefore, the task of logging onto different databases alone is quite cumbersome.

The main thing is to make data available to the employees when they start working mornings, instead of them starting drawing out reports to see if there is anything that they need to act upon. With these legacy systems, which work on a one-to-one basis, we tried to batch process them a lot more.

We have looked at it with Citrix, and there are problems with it. Some of the new features coming will address it.

We have been looking at Attended Robots, which result in the inability to lock your screen. That is simply a no-go for ever using them in most government agencies, as IT security will prohibit us from using them. If UiPath wants Attended Robots to be used inside a government agency, it needs to be applicable on a virtual desktop.

A lot of what is coming is what we are looking towards: Both on the skill set with computer vision, but especially also on the enhanced identity management and security. The ability to debug and lock at a less complex level for us to look at. 

One to three years.

UiPath's stability is quite good. We don't see any problems with the stability of the platform application. All our problems stem from the basic systems that we operate on, which are quite vulnerable to network problems, time outs in various systems, etc. However, these have nothing to do with UiPath. Perhaps some of the things which are on the road map will help with the debugging of some of these issues.

One of the things that we are lacking right now is not stability, but usability with debugging, e.g., when you can't see what went wrong. We have to look through 50,000 pages of logs or so. 

The scalability is quite good. 

The main problem around scalability is the licensing structure and the inability to dynamically assign licenses across robots. While I know this is coming, this is our main gripe with scalability: the licensing structure. Because we are part of a larger setup with our own IT supplier, who does a multitenancy setup with Orchestrator, to have more flexibility with the use of licenses would be very valuable.

We are using virtual desktops to deploy and run the machines with robots. It is necessary, as we cannot scale it on individual on-premise machines.

We have used the customer support. Our main issue with them is they need to understand the problem that we are writing about, and not reply too soon with a standard answer.

All our developers are using UiPath Academy and are RPA certified. While they like some thing, some of the frameworks which were used in the Academy examples, the developers didn't agree with. This is probably because they are IT professionals themselves and are used to doing things a different way. Whether it's because the use case wasn't good or they were just used to something else, this was the main gripe.

The product has a lot of backing from our director, who has been pushing the agenda. To be able to stay relevant, even as a government agency, we have to reduce our costs every year by two percent. To be able to produce that, we need to be more efficient at what we do. The target is: Not to reduce staff, but keep up with the increased demand for production and costs.

I wasn't part of the very first setup.

We mostly did the deployment ourselves or with our own IT partner, who is not a partner of UiPath. So, it has mainly been done by our own IT people.

On the individual robots, we do have good return on investment. However, once you add in the governance, including when we are scaling up the solution and the maintenance of robots, then I don't think we are at a break-even point. This upcoming year, we are expecting positive ROI. For us, the return on investment is high quality data. 

It has helped us to eliminate human errors. We have a robot that is specifically requested to avoid, for example, uploading reports on the wrong customers because of GDPR cases, where data protection officers will have to get involved, even though, it's not sensitive data. We have seen problematic use cases drop from a couple of incidents from maybe 100 transactions to zero. We are looking to completely eliminate errors in some cases, not just reduce.

It has saved our organization time. We use the robots to try to address some of the peak workloads that we have. They are not there so much to address a certain number of hours that we want to save. We want to be able to use the robots to help address our customers' needs during designated time frames to reduce extra stress on our employees.

We would like to see improvement around the licensing and multitenancy. 

We also evaluated Blue Prism and Kofax Kapow. The reason that we went with UiPath has a lot to do with scalability, as our IT supplier has committed to a multitenancy set up, which was not possible with Blue Prism. 

We are quite happy with UiPath. We are not looking at other vendors at the moment. They are all offering similar solutions, but with a slightly different focus. We could use any other solution, but the development is so fast that even changing now would be no guarantee that we end up with what we want, because everybody is moving at a pace where we can barely keep up with the development of the products.

Try out different vendors and their labs. See how it fits to the processes that you are trying to automate right now. Some applications are better at old mainframe systems, and if that's what you will be focusing your efforts on, then maybe UiPath isn't the best vendor for you. There are others who focus more on that sort of environment. So, be realistic about what you want to automate, and choose your use case initially from that. 

We see the biggest benefit right now from Unattended Robots, but that's all we use. In the very long-term, Unattended versus Attended Robots will be able to generate a greater benefit. However, with the current licensing costs, they will need to change for it to be a positive business model. We have to be able to move licenses from one person to another. If we have to apply a fresh license to each person in the workforce, with our budget, it will not be possible.

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.