UiPath Platform Reviews

We do product downloads, accounts, updates, maintenance, a lot of operation stuff, reading emails, responding, organizing stuff to send, etc.

It's definitely added some efficiencies. It's added the ability to do jobs without having to worry about error handling and process tasks on a daily basis without having somebody having to be responsible for it.

We see UiPath as a money-saving solution. It also saves us man-hours and human error. It affected our ability to automate processes that are more complex.

The Academy courses are good. That's usually what I start new developers with; to do those and then have them try to do courses periodically to stay up to date and especially when a new release is coming out. The hands-on training is the most valuable part of it. 

We use the solution's error functionality. 

There's a little bit of a learning curve to build automations, especially in the citizen developer world. Usually, the technical people are busy a lot of times, so it's hard to get them trained. But as far as developers, they usually come along pretty well, from my experience.

We could use a little more interaction with users, like with UiPath, the vendor, and support.

I have been using UiPath for two and a half years. 

We had a vendor that kind of offered to do a few, like bring you the UiPath and do some automations for us. We dipped our toes into that and liked what UiPath has, so we kept them.

I would rate UiPath an eight out of ten. 

Our primary use case is to scrape our database to get data out, create audit files for our tax team, and then take that data and go to websites for each state and submit our taxes online.

Time-saving is the biggest area that has improved for us. We had users spending lots of time trying to get data from a system and then creating a file that was going to be used for our auditing purposes, which then gets submitted online. We definitely found some issues where an end-user was pulling data from different sources and then storing that data with lots of human touching that created issues.

UiPath created a better atmosphere of better data quality. Time management was also much better, and now the user actually has a better experience doing that process because now it's a click of a button. They can spend their time doing the actual work that they want to do.

Instead of having to go back out through those websites and make corrections when they paid for the wrong taxes. In some states, it's a lot harder to make those corrections, especially if it's one where you overpaid. Now, they're accurate and they don't have to go back and make those changes to try and get that resolved.

We have seen cost savings from the time it has saved us. We save around 40 to 50 hours a month. Over the course of a year, it's quite a bit, and it adds up.

Web trading services are the most valuable features. 

It is easy to build out automations. I have an IT degree, but I was not doing the dev work within our department. I came from a data quality background and transitioned over to this because the low code has been great and all the online resources that they've provided us have been very beneficial.

Other members of my team have used the Academy. It helps to get a jump start. Now, luckily, we have a couple of us that do it. It's much easier to train and show them what we have already built and then say, "if you have questions, you look here." It's just been great.

They have the robotic enterprise framework that I wouldn't have used if it wasn't for the Academy. When I first started automating, I wasn't utilizing that process at all. That actually made a huge difference in how I programmed and how I even looked at building my automations to start with. I feel like learning that course specifically for me, was great, was like the best benefit for me.

Since we've been with them, they've changed their licensing structure. It would be nice to have one set structure where they're not changing the structure on us because we were set with what we had, but now we are changing. I understand there's a lot of changes and reasons for it.

I have been using UiPath for a year and a half. 

I haven't had much issue with stability.

It doesn't seem to have a limit. Scalability has been great. Everything that we've run into that we've needed it to do, it's been able to do.

Even being a smaller consumer as we are, when we've submitted tickets, they've been very responsive even to the point of when we couldn't get our deployment deployed because we had an issue. They were responsive and within a couple of emails of them understanding our issue, we were on a phone call and had everything resolved over a phone call

The initial setup was straightforward. A different part of our IT department did the setup and they seemed to do okay with it. We had some hiccups with it. When I did some upgrades with that, I had a couple of hiccups, but I was able to actually work with UiPath and they were able to help us resolve our issues.

My first deployment took a couple of weeks.

When we did our original deployment, it took a couple of weeks just to research and understand exactly what we needed to do for the on-prem plus the other daily work that we had going on. It wasn't the highest priority because at the time I was using the community addition to get started.

Our very first project was the biggest return on investment.

For bigger businesses, pricing doesn't matter as much. It has the right packages. But for a smaller company, it's really tough. There could be better package options that suit smaller companies. 

A consultancy called Agility Partners came in to help us. We had the tax automation we wanted to do and they gave us some options of different things and then they pointed us in the direction of UiPath thinking it would be the best benefit for us.

As soon as you can, do it. You're not going to believe how well the automation will save you time, your company time, and even quality issues. This has been great.

I would rate it a nine out of ten. 

We're a revenue cycle management company for medical billing. We've reallocated our charge entry employees. We're using bots now to do the charge entry on medical claims and then also payment posting along with eligibility and AR. We've been able to reallocate about, just within this last year, probably eight employees. They've been reassigned to more valuable work - things that the bot can't do and actually requires a human to do. We've been understaffed, so it's actually worked out great for our company.

The ease of building automation isn't a problem. It seems to be very easy to do to a point. Our challenge is we work in a live environment. We're not able to use a test environment when we build things out. We have to go very slowly.

I'm not that familiar with the product, with the solution, however, the UiPath apps feature and OCR are great. That said, we're not using any of the apps currently.

The biggest benefit we've seen is the accuracy. Even just with employees calling in sick or not having enough staff. We’ve been able to fill those roles.

The robotics piece has been a huge thing. We're doing medical claims. We're always worried about claims not getting paid. This has been able to capture those claims so that people get paid the first time. One of the other things we track is how many times we touch a claim. For example, how many clicks. We couldn't do that before. That's been very valuable to us.

We’ve improved our efficiency in a way for sure. Even just our cost analysis has improved. When we do new contracts, we know what it's going to cost exactly.

I don't know if it's UiPath as much as just what we do is really complicated. Even the consultants that we've used with UiPath, even they've said, wow, this is very difficult what you guys do. There are a lot of moving parts, so it's not as much of a UiPath problem in terms of limitations. It's just our own processes.

Right now, I don't think I've been on there long enough to know if there are missing features or functionalities I’d like to be added.

I’m talking to people right now, to see how it can do things better or how we could use it more effectively. We’d like to discover what worked for other people.

We've been using UiPath for about maybe a year and a half tops.

I haven't had any problems or concerns right now concerning stability. The biggest concern I do have is that we've already invested six people in this. We're going to have a lot more that will, more or less, not have the robotic piece as part of their job. That work will be reallocated. I have about a hundred employees that UiPath could technically reallocate.

When I look at that, I worry about if something does happen or it doesn't work or there's no backup. Then, suddenly, I don't have employees. Right now, we can jump in and some humans can do the work if necessary. My concern is that in the future they won't exist. This hasn't happened yet. I hope it doesn't.

Scalability hasn't been a problem at all. We can just continue to add bots every time we need them. It's been easy.

We started with two. Three months later, we added another two. After another three months, we add another two. From our standpoint, it's great. My UiPath rep was shocked that I keep adding more, so that's good.

I have not used technical support.

That said, we had one issue with UiPath where something didn't work. We talked to them and it was taken care of within a couple of days.

My vendor is working with them. They mentioned there was an issue with insights that they are working through. Insights are still not quite functional, or there are some resources we need. However, the vendor is dealing with it directly. It's a work in progress. 

We did not previously use a different RPA solution. 

The initial setup was pretty easy. We didn't have any challenges with that. I contacted one of our vendors and they ran with it. We didn't have issues at all.

With the vendor, it took us about 30 days to deploy UiPath. After that, in terms of implementing bots, the first bot took us about three months. Once we did the first one, it just went really quick after that. We could reuse some processes which made it faster. There was a lot of reusing of the same. We were also internally understanding what information they need and how it works.

It was all new to us. I'm still learning the acronyms they use. We need to learn what they are talking about. We’re not IT-based at all. It's definitely different.

We had the solution implemented by a vendor. They implemented it all. We didn't have any challenges as far as that goes.

Our experience with the integrator was good. I would say that they didn't realize how challenging it was going to be or, at least, the person who integrated didn’t. At the same time, they know almost everything about my business now.

UiPath has saved costs for our organization. For example, we’ve allocated six employees that are paid around $40,000 a year and we've implemented six bots to do those same functions and they're around $8,000 a year. In a way, we’ve doubled our staff, and almost tripled our ROI.

We had a problem before with the pricing, however, for the most part, it's fine where it is now. My ROI is fine. It works great. I have zero complaints.

You have to do a package at a time. That's my only challenge, where sometimes I don't need that many licenses. 

When you first sign up, it's a package that can renew every five years. I don't necessarily need everything. I'd prefer just to pay for certain pieces. 

We did not evaluate any other options. We started using UiPath due to a referral at a neurological healthcare conference about four years ago. The speaker suggested UiPath. I actually didn't know of any other company until after we were on UiPath. We've since talked to others who have used other solutions and they mentioned that we made the right choice when we chose UiPath.

We started on-premise for the first six months and then we actually moved to the cloud.

We do not use their UiPath apps feature as of right now.

We are mostly using unattended automation.

We haven't really calculated the reduction in human error. We're just moving on to our Insights app. We're just getting ready to launch that, so we're not there yet. We don't know what that turnaround will be.

We do not use UiPath's AI functionality in our automation program right now.

Our teams have not yet used the UiPath Academy courses.

I'm a little concerned about having to bring on more people that are not in this industry. We're going to have to start them over from the ground up, which takes time.

When we first started, we wanted to know if it really worked. We got a certain budget and just started using it, and now I can say that yes, it does work. We can see that now that we've stepped back. We should have done it earlier. That's what I would tell people. I would definitely tell people to look at it first, before anything else. 

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

We've got mostly finance use cases including a lot of accounts receivable and stuff like that. Then, there is a lot of work where I do trading settlements, so a lot of settlements as well. The back office automation's there, too. We're still getting used to it and still getting started.

We've been able to expand up to citizen developers, and have been able to show them how to do various things. It's easy to pick up, so a lot of citizen developers are learning it now, and with little to no coding experience. It's been great.

The recorder has been great. Just being able to really start your automation there, and just modifying them a little bit and then getting them really in production has been helpful.

The solution has saved costs for the organization. For example, I used to do back-office stuff, and I was able to move to more of an IT role. That was definitely a savings there, and obviously, no one had to automate it after me or do it manually after me.

We have found that the solution has reduced human error as now it's a bot doing it. It's really reduced errors due to the fact that no one has to check each time to ensure the work is error-free, and, in general, there are a lot fewer errors. 

The solution has freed up employee time. For example, as I mentioned, I myself have moved off of back-office tasks and, in doing so, the company did not have to hire someone after me. We've likely saved 10,000 hours in a year. We're really happy with that result. The additional time has enabled employees to focus on higher-value work. People can now just quickly audit it and then move on to something more important.

The Academy is great to use. We've been able to learn a lot from there. That's what our citizen developers will look at as they get more familiar with the product, and as we show them how to develop items. It has positively affected the process of getting employees up to speed on the solution. A lot of them have little to no coding experience and the Academy has helped by showing them what they need to learn. The biggest value is if they have little to no coding experience, it'll really start from the basics and teach them from there. You don't have to teach them all the variables and stuff like that.

While I like the Academy a lot, it could maybe go deeper into some of the topics. The basic ones, such as Excel, which is already a decent course, could maybe go into more specifics. My issue is that, while the basics are good, getting into the weeds a little more could be very helpful. It's hard to specify exactly what is needed, however.

We've used the solution for about a year now. We're still getting used to it. 

Our stability is great. You rarely have any downtime, once you build it. There's obviously the support, however, I'd say it's pretty minimal.

We're trying to work on scalability at the moment. It's there, however, we have a lot of different departments that do a lot of different things and that's where we need to really work on scaling. It has nothing to do with UiPath. It's just about getting everybody trained up on everything on our side. That said, we can see how it is possible to scale in the future. We do plan to increase usage.

Currently, we have about ten users who are familiar with UiPath. It's not too many. They are either developers or just everyday users that support it.

In terms of technical support, from the perspective of tickets, et cetera, I would say they are pretty good. We've only done a few upgrades so far. We've only had it for a year, and so far, in that time, support seems great. They have been helping us out on everything.

We did not previously use a different RPA solution.

I can't speak to the initial setup, as we had an outside party handle pretty much everything. I actually joined after they onboarded us and everything, and therefore wasn't a part of the process at all.

We have two to three people that handle maintenance tasks, on top of the AI.

We had an outside party do the deployment. It was a consultant. They did it for us.

I don't have any insights into the licensing process. 

While I joined after UiPath was implemented, my understanding is the company did look into a couple of other options, just to see their capabilities.

I would advise potential new users to go for it. The Academy offers a great starting point. It's a great tool. I would recommend UiPath.

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

Our primary use cases are for invoice processing and some legal intake use cases.

The benefits we see from UiPath are always time savings. I've never seen another benefit. It's always that people don't have to do manual tasks anymore.

The automation cloud offering helps to decrease UiPath's total cost of ownership, by taking care of things such as infrastructure, maintenance, and updates, if security isn't a big issue. 

With the cloud offering, you don't have as much control of where the data is and how it's protected versus the on-prem. If you're dealing with very sensitive information, you could introduce a compliance risk if you're using the cloud offering. But with the customers that we partner UiPath with, that's not an issue, so we use the cloud offering.

The screen automation features are the most valuable. There are some things, in an automation process that is complicated, that UiPath isn't very good at. And there are some things that are very repetitive and UiPath is good with it. For those repetitive aspects, it's obvious why it's valuable. It's replacing the amount of time that a human being would have to spend doing it.

We have seen that our clients have freed up time for their employees.

Our clients utilize AI functionality from UiPath. UiPath is really good at simple repetitive processes, but not as much at complex processes. The more complicated it gets, it breaks down because if it's less repetitive, it's less automatable.

AI functionality enabled our clients to automate more processes overall. It helped with end-to-end automation in the way that if you automate more processes, you save more time, and save more money for the company.

It is not very easy to build on automations. That's a problem with UiPath. I don't think it's very easy to build automation on top of it. 

Accessibility needs improvement. It would be easier to build on UiPath if they would have more employee-level users as opposed to consultants. Then that would increase the value of the product and the platform.

I have been using UiPath for two years. 

The stability is good. 

It's very scalable in our organization. The hardest thing is getting in and getting someone to build their first five automations and their first five robots in the first place. After that, it's very hard to rip out. Once you've already automated something and you've done all the in-depth work to set it up, it's pretty sticky.

There are around ten users and they're almost all solutions architects.

We've used Blue Prism and Automation Anywhere, but I think UiPath is the market leader right now.

Even though UiPath is hard to use, it's easier to use than Blue Prism. And it has more features than Automation Anywhere.

The initial setup is never straightforward. There are always bugs. It doesn't matter if it's UiPath or any other company, it's always complex. It's never easy the first time.

The implementation takes around three months. 

Ideally you don't want to take someone's job, but if you free up the time that someone was spending doing something, you don't have to pay them to do that anymore, or you can reinvest their time somewhere else.

It's expensive, but it saves a lot of money too.

My advice to someone implementing UiPath would be to hire someone technical to do it. It's not as easy to use as they say it is.

I would rate UiPath an eight out of ten. To get it to a perfect ten, it would need to be easier to use. 

Our primary use cases are in our financial department. We had a bit of a downturn, but we still had work that needed to be completed. So we developed several automations to manage a lot of the financial work and a lot of our payment processing systems. We expanded that out to include more of our traders' work processes, just because we saw there were a lot of workloads coming in and a lot of repetitive work. So we used UiPath to eliminate a lot of that for our commercial traders, then we did the same thing for our operations and production teams so that they have their own automated processes.

We plan on scaling it and using it in more functions.

Our biggest metrics are in our financial org, they have more of a cost avoidance where we don't have to backfill those positions. It's around $2 million a year because we don't have to bring in personnel to complete the processes.

It has helped solve certain human errors but that's an unintended bonus because we're automating a process as it is that a machine is going to repeat. We don't really have a person to do it.

UiPath has helped to free up employee time. The additional time enabled us to focus on higher-value work. By removing a lot of the repetitive work, it's given them the ability to do more analytics and to dive into the data science realms of their job to do more data-driven analysis of what they're doing.

The ability to do citizen development is the most valuable feature. That initiative has helped us to expand it because that gives folks that are closer to the business the ability to develop their own solutions that are tailored to what they need to do, as opposed to waiting for someone in IT to contact them to build it out. Or to wait for a business analyst to provide some type of value metric, but they can actually go and build it themselves.

My job is to actually be the evangelist to these groups. I'd say we've been pretty successful. My developers are working with the citizen developers who help to guide them and to teach them how to build their own automations for their business process.

It's pretty easy to build automation. The no-code process has really driven the adoption by the business people so that they don't have to skill up and learn how to code anything. They only need to know how to click a button and build it out. That's the best component.

We used the UiPath Academy course. It's our training regimen for our business users. We have to introduce them first to the platform and understand how to work through the platform. It's a pretty straightforward and easy course. With our citizen development program, we also have the Academy where they can either do hands-on learning or use the Academy to get some video training as well.

The biggest value of the Academy is the ease of being able to access the training. 

Governance has room for improvement but that's more of a cultural thing. It depends on your company. We have the reference architecture that we have in place, but it's easy for someone to say, "Okay, I need to make an adjustment here outside of that reference architecture." Because it's so easy for them to do that, they leave the company now that a non-compliant bot is out there running a production process, we need to be able to rank that in. There needs to be footwork that we have to do as an organization for my team as opposed to a true problem with the platform.

We have been using UiPath for around five years now. It's the on-prem version, but we have it deployed in the cloud in our Azure tenant. We started on-prem then we migrated it about three years ago.

It's pretty stable. It's more of the architecture and how it runs because it has to leverage VDIs and as Microsoft releases an update, we have to be watching that process because it'll make the box really brittle. Any change to the UI anywhere will break and that's where we have to step in and fix it.

Every corner of the business except for folks out in the field uses UiPath. It's around 200 people or so.

We've had a little bit of back and forth whenever we have an issue and some of the solutions we got back were pretty boilerplate-type answers. We had an issue with a Microsoft update. They said, "Well, could you potentially reach out to Microsoft and have them let you know." 

They're just going to release the update. We need to be a little bit more proactive on the software side. Our account executive took care of it for us. He stepped in and enabled us to not have that response again. 

I wasn't there for the initial setup but I heard about it. It was complex, but that was more of a cultural thing.

The deployment took around a year to get that through planning, discovery, and implementation.

Our biggest return is our cost avoidance and not having to backfill personnel.

I think the pricing is comparable. It's fair pricing for the size that we're deploying.

My advice would be to make sure that you have a really good understanding and a really good culture in your company that understands and wants to get on board with automation because it will require that type of mindset of understanding what you're doing before you do it.

I would rate it a seven out of ten. 

There are lots of use cases. Mostly, there are many gaps in organizations that buy a lot of software and a lot of automation platforms like ERPs, however, they don't know how to actually create an end-to-end process and connect those systems. In those cases, they end up like small islands in a big organization. What I started doing was filling those gaps. After that, we use the RPA to fulfill that. For me, a lot of processing in Excel or some processes that needed multiple users to interact is what we use the solution for. We just capture those tasks and convert them to RPA bots. Basically, we've automated a lot of manual tasks.

We do not use UiPath in the contact center environment. In our case, contact centers here are really dependent on CRMs. Even using chatbots in contact centers is still very new in Iran. These foreign branches, these foreign companies that are in Iran, do not see any potential to use RPA in this scenario. 

Mostly, UiPath has improved my career. I am an RPA Developer, and without UiPath my job wouldn’t exist. UiPath changed my career. Due to UiPath (not Automation Anywhere or not Blue Prism), there’s a noticeable increase in the speed of development. I was a C# Developer and it's helped me a lot. Generally, UiPath is in the top 10 and has offered a lot of new technological shifts and people are talking about it more. When people are talking, there are great opportunities. There are now new voices that can be heard. 

UiPath is constantly listening. That's a good point for UiPath - it's always listening from its community to its top customers and interacting with comments. Due to the fact that it listens, it integrates new software, goes into end-to-end automation, and changes for the better. Someday they will have Autonomous RPA, a real Autonomous RPA that can actually decide like a true robot, not just a robot that works on a script. One day they will offer a true robot that can finally decide what to do in certain situations, not by just using something like document understanding that we call Machine Learning. UiPath is very, very good at giving true innovation to people. It’s a win-win for everyone.

RPA is actually something that can be executed, that can be used side by side with many programming technologies.

The speed of development in UiPath is very fast. For example, sometimes you want to do many frameworks and the budget is low, with the timeline being very crucial. With UiPath Studio and with the whole UiPath platform, it can be very fast to develop and deploy. That's the main advantage for me personally - that the speed of development is great.

UiPath enables us to implement end-to-end automation starting with process analysis, then robot building, and finally monitoring. They are all there. The one exception I’ve noticed is that end-to-end automation is still lagging, I have reasons for that. However, the monitoring of the robots or even using insights is there. They are the prerequisites for an RPA platform. They are great suites. They are necessities.

I like parallel processing. I like that a robot can do some parallel stuff while the user continues to do their own thing. If it needs interaction, we can just pop up a clear window or apps, for example, or through email, in order to inform the user about the robot's request.

AI Automation overall has enabled us to automate more processes. However, when we go forward and move forward, we see that we can digitalize those documents before it needs to be processed by an image machine-like OCR or even Machine Learning. For example, there are still handwritten documents. We’ve convinced many organizations to drop those handwritten documents and use digital products for us. Those are immediate time savings for the process. We are not using document processing anymore, for example, in a specific organization. For processes that still need to have handwritten or printed out documents, document understanding could be fine. I really hope, however, that they shift to AI, which is what RPA lacks. RPA lacks Autonomous Automation, that's something that everyone is waiting for. We’d like to have a robot that's actually using the computer with its own mind, not just the workflow we give it.

For end-to-end scenarios, UiPath is still growing. I'm not saying that UiPath isn’t good. There is a lot of potential. They're using UiPath Actions or Apps, for example. Dashboards ensure that end users can interact in a new way with robots or with the whole end-to-end automation. RPA is a technology that hasn't maxed out yet.

Someday, there will be no legacy software or very intelligent processes that will use APIs. It’s my understanding that UiPath bought some company that specializes in API Automation. For end-to-end automation, UiPath needs to integrate all those components, rather than task automation to process automation, real process automation. With RPA, if you read the HFS report, you see that the process version is actually not a process. It's tasks. Perhaps in their next LTS release, UiPath will actually gain to that point.

There are minor bugs. Every major software has bugs. That said, all are solvable, all are resolvable, and it's not a very bad thing.

Mostly, licensing must be improved somehow. Licensing is very expensive. Even in many industrial countries such as the USA or UK, UiPath is still very expensive. For example, Microsoft now owns its own RPA, Power Automate, and the pricing is much more reasonable than UiPath. UiPath licensing is very vague and expensive. There are some ways that they can reduce the cost to make everyone benefit from an RPA.

UiPath needs a lot of maintenance. Every RPA vendor, every RPA on-premise software, needs a lot of maintenance. The cloud version has reduced that, as far as I know. It’s resolved the maintenance issue so that users can focus more on other things. Every new feature will be first on the cloud version and eventually, we can benefit from that.

We use document understanding. For English documents, it helps, however, for Persian documents, due to the fact that the models, the Machine Learning models, that are pre-built, are based on English or other common languages. If we want to actually use Persian, we need to use AI Fabric and build our own models. It's now out of our budget to do something like that here.

It's almost been three years since I first started using UiPath.

I don't like the stability very much as it has minor bugs.

You see that processes break without any reason. When you check the system, check every log, even view robot logs or logs in the network level and you see that it has, it's only then that you realize the issue was a bug from the UiPath platform. Once that happens, you must go to the community and explain the situation to each other. The good thing is, there is a community right there and you can learn from each other. 

Scalability is great. UiPath has many capabilities. Anyone, via a simple search, can go through UiPath and even try the enterprise version and just see for themselves that there are many, many, many capabilities. You can use .NET and there are many NuGet packages that you can use or you can even design your own custom package. There are many great platforms, such as Insights, Action Center, UiPath platforms, and so many different types of robots.

In terms of technical support, I do not have the opportunity to speak with them, as we are in Iran, and, due to sanctions, we do not have a direct opportunity to speak directly to UiPath's support. Therefore, I cannot have an opinion on their services.

I'm familiar with other RPA solutions such as Automation Anywhere and Blue Prism.  

I saw a lot of people that are going to RPA. I put myself in their shoes. However, from my perspective, UiPath has a great community. The UiPath forum is very good compared to Automation Anywhere and Blue Prism. Every technology can be learned, sooner or later. That said, the first thing that any kind of technological software needs to have is a good community to facilitate that learning. Without community, you cannot spread the word, you cannot spread the knowledge. It's the first thing that UiPath has over both of these other solutions. 

And the second thing is, as a technological matter, UiPath is much better. The other two lack the connection, lack the integration. The user interfaces of both Automation Anywhere and Blue Prism are terrible. I do not like them. They're not very intuitive and they are not easy to learn. UiPath is using Workflow Hosting Foundation from Microsoft and great integrations with .NET, which is so much better than the other ways that other vendors are approaching things.

I'm typically involved in the setup. I'm involved in every phase of the process. 

The setup is straightforward. They're using .NET Core now and before that, they were using ASP.NET's Standard Framework. The company has relied on default application configuration as far as, for example, in web.config or .JSONs. Most configuration must be done in the UI itself. I don't really like to just manipulate files at the system level just to do something. I believe that's the way now, however, that can be improved. It could be just in the UI and the certainty would be much better.

The length of time it takes to set up a robot deployment depends on the project itself, however, for a small project, it can be in one month to 45 days.

The initial deployment of UiPath is not more than three days.

Setting up UiPath doesn't have any standard process. There's just documentation. We are always using its documentation.

We do not have any relationship with UiPath directly. We are just a contractor doing RPA for foreign companies that are based in Iran.

Iran has sanctions against it, and there are a few companies that are local branches of foreign companies, and those that have licenses from UiPath all use on-premise deployments. We're always using the latest versions of the solution. Right now, we are on version 19 and it's in the 2010 LTS.

I didn't have the opportunity to use UiPath Cloud. I'm in Iran and I don’t have access. There are some capabilities that are still in the cloud version, like Apps.

While it depends on the project requirements, much of our work is on attended automation. I see attended automation as a gateway to an RPA solution as users are very busy and we cannot just pop-up in some programs, random programs, and stuff so they end up having to wait. I do not believe that attended automation helps users as much as an unattended version can help. This is due to the fact that at some point, someone still has to be involved in the process.

RPA is a new technology and a new shift that there's no good book on how to manage. Maybe there are some, however, they can be obsolete rather quickly, as the technology is changing and with every new version. That's why hands-on experience is the best way to learn. Even for UiPath, without any practice, without any hands-on experience, and without any good community, you cannot do anything.

If someone wants to learn UiPath, first they must sign up within the community and then go to UiPath Academy. Start there. Practice. Get in touch with people in the community, and then create a small use case and do some hands-on work. Practice is very crucial in RPA. Don't forget to review official documentation as well, as it will save you lots of time. 

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

I've created an app for conversions and exchange rates. Every day I need the exchange rate of a certain currency and I use the API free exchange and UiPath.

It's also used for the reconciliation of invoices.

I've used it for the creation of an onboarding bot for employees to be onboarded onto a website with a remote system. I used AWS and a virtual machine and created a Google Form from there, and used UiPath's computer vision to do onboarding activities and extract data from files. PDF files can then be entered into the remote system. UiPath can be used to fill the forms.

It can be used for web extraction tasks as well, for example, for booking flights, where you can extract the flight details for particular search criteria and place them into an Excel sheet.

It can also be used to extract data from invoices in order to populate an Excel sheet, for a portable format. I've created a process that used documents as a learning model and extracted the invoices, using logic to output the transactions. 

Another use case I tried was extracting data from Amazon based on exact data. The same can be done on Linkedin using the Linkedin API. I'm fine-tuning and extracting data, putting the outputs on Google Sheets.

I've experimented with many use cases and automated many processes. 

It's low code/no code which makes it very easy to work with. 

Building automation using UiPath is easy. If I see a video or some instructions, I can do it. Things are doable. You learn. If there are use cases or there is information online, you can replicate the process.

Adding activities is easy. All of these partners are integrated into UiPath now - including AWS and G-suite. You have activities already built right into UiPath and they are working to make everything as low-cost as possible.

Then you have OCRs which offer the Document Understanding. I can do a PDF extraction using just OCR in a normal way.

I love the Document Understanding. You can see whether a document is valid or not. You can accept or reject. I came up with a .NET background. I used to write so many lines of code for doing a certain thing. Here, you have a for a loop. You don’t need so much code.

I remember when I used to work for a UK client, a gas utility, and at that time we used a read-through data driver, and got the Excel data, and again validated everything. However, for that, we used to write around two, three pages of code. Now, using UiPath, you just do a real Excel activity and you get the entire sheet. Automation has made our lives easier.

I can scale automation without having to pay attention to infrastructure. Now, since the cloud has come into the picture, everyone is going to the cloud and everything is easier but with the new cloud partners like Google, AWS, Azure, and Oracle. A company may not have its own on-premise orchestrator.

Earlier, you needed three servers for production, testing, and development. Since UiPath has both cloud orchestrated and on-premise, it's easier for organizations to use less physical space. For smaller organizations, they can go to the cloud. For larger they can have their on-premise orchestrator. It’s flexible.

UiPath enables me to implement end-to-end automation starting with process analysis and then robot building and finally monitoring of automation. There are many process mining tasks, capture tasks, mining, et cetera. More things have to be automated - such as deploying, managing, and enhancing for continual improvement. It has all the components.

For a beginner, end-to-end coverage may not be essential. When we talk about automation, we should know what can be automated so that we ease our lives and that doesn't mean we have to remove the resources. You don’t have to involve the employees. You just need to simplify the task so that there is continual improvement. Users should consider not only, how to automate but what needs to be automated. If it is automated, how it can be improved gradually and what are the returns? Sometimes that doesn’t necessarily mean you need end-to-end. You just need simplicity.

I do use the attended automation. For some processes, I use the attended automation for testing purposes. I use the attended if I'm using UiPath assistant, otherwise, it's normally background processes that are unattended.

Attended automation will be for Document Understanding when I'm training a robot, for example, for what is the format or validating the time I'm using attended one. If I'm asking a user for particular search criteria, or for currency exchange it's mixed but mostly unattended.

Both attended and unattended work together - the human as well as the robot. However, it depends on the scenario. Unattended means you are not dependent on any human resources.

The orchestrated cloud, which is a SaaS, it's quite helpful. If I just want to install UiPath studio in my system and I'm least bothered about what environment it should be, what infrastructure should be, where I'm going to deploy, it is quite useful and quite easy when there is a SaaS option available.

I’ve used the AI functionality for sentiment analysis such as getting reviews from the websites about a particular product or service.

UiPath offers great object detection where you have a magistrate and you can detect whether you want to detect the people. If you want to extract how many people are there in that image, for example, during a social distancing sort of event, that can be used for object detection. I've used object detection for images in terms of extracting a number of people.

I’ve trained the system to read different types of invoice formats. I've used the email or Document Understanding that can read separate invoices, receipts, utilities, et cetera. I’ve used the solution to create processes for invoice reconciliation.

The AI functionality is quite easy to use. For tollgates, for example, when they charge for tolls, the solution can be utilized for seeing the number plate, and through the image, get the data, extract the number of data from the numbers plate, use the driver information from the number plate of the car, et cetera. It becomes a very easy AI model. Without any type of knowledge in AI, you can use those out-of-the-box functionalities.

The more training you do with machine learning, the better results you get in the end.

I use the automation cloud feature.

We are not bothered about any patches or any work that has to be done to maintain the infrastructure; the vendor does it.

The automation cloud offering has helped decrease time to value, however, since I have not deployed real-time projects, I cannot give exact numbers on the decrease. That said, from my experience, I feel that it is true.

It’s my understanding that the automation cloud offering helps to decrease UiPath's overall cost of ownership, however, at this time, I just use the free version.

The solution enables you to be better and better with cloud features that are quite accessible.

In terms of UiPath Apps, I have used them, however, just for my own purposes, for my own training purposes, as I was learning. It is easy to use and pretty much drag and drop. For the basic things, the user can do a lot with minimal training. You can do everything with low code and less coding knowledge as well. A person may not be technically sound, however, even with minimum knowledge, they can create apps using UiPath apps. That's the interesting part of UiPath apps.

UiPath reduces the cost of digital transformation. It does not require expensive or complex application upgrades or IT support.

UiPath has reduced human error. For example, let's say I'm filling a form using a document. Typos, errors, spelling mismatches, et cetera, are reduced when it is handled by automation. When we automate this process, the robot minimizes the error since a human is not involved in this case of data entry. It will extract whatever data there is in that document and it will fill in the form. Similarly, for calculating Excel data, we can avoid calculation errors.

More videos are required. There are basic videos that can help you learn about the product, however, there need to be more in-depth videos to help you through certain tasks. For example, I was trying to use an API for conversion. I was doing it for a single transaction, one by one. There can be cases where it will not go for a simple conversion or simple transaction, and it will be a bulk action. In that case, I may need to upload a file. I was searching for an upload control however, I could not find anything to assist me.  It would have been helpful to find some sort of instructional video for this task. The file upload, where you upload a file and select a file so that you can extract data all those things based on that file is a commonly used feature - and yet, that was missing. 

UiPath apps may be able to increase the number of automation I can create while reducing the time it takes to create them. However, they need to elaborate on the process. I need more articles on that. From the point of view of the person developing the automation, I need more details on writing the correct code or doing the automation, which I hope will be coming in the next releases.

They require an improvement in the IEP. I don't know whether it's a bug or something. I find that, with drag and drop, you have to drag it in a particular fashion. 

When they add new features, they should offer some in-depth sessions on them to help people get comfortable with the changes. 

It would always be helpful to have new partnerships between UiPath and different cloud vendors. 

I started using the solution in February of this year.

I am on a gap year. I used to work for an IT company, and I have taken a gap. To re-skill myself I started learning UiPath. 

The stability is quite good. You have other options, such as Automation Anywhere and Blue Prism. UiPath will be like coming out with new revisions in the coming years that will continue to compete with those.

Even now, it's quite stable and quite reliable, even if the changes which are coming, in the much of the deployment, are felt good. There are frequent revisions. I have no experience in other automation, however, from what I've seen, even as it changes, it's stable.

Scalability is quite good. It has alliances with different cloud vendors so that you can scale your robots. You can have different instances, different new virtual machines, and in the cloud. You're not concerned about what to install and you just pay as you use. The cloud vendors make it very scalable. 

Once I am employed, I do plan to increase usage.

I use the forum for any queries. I didn't face user technical problems for any robots that I am using. I have not been in direct contact with technical support.

The initial setup is straightforward. 

You just go to UiPath.com and register with your user ID or any email ID. From there, you install the UiPath Studio and you set your workflows. Once you publish, you get it in your orchestrator, attach the process, create a job. And then you run it. 

It's quite easy to create a workflow, publish it, and deploy it in the orchestrator. Next, you have to tag the correct robot, the correct machine, and the correct sponsor. In any environment you want.

For small processes, the deployment would hardly take a few minutes to deploy.

Maintenance is light for the cloud instances and really does not need much. The cloud vendors do the work, however, users need to pay for the services which they use.

I handled the initial setup myself. I did not need an integrator or consultant. 

I can't speak to the exact pricing of the product as I am using a free version of it right now. I'm not paying any licensing fees to UiPath.

I shouldn't say you need licenses for many things for today, however, for working on Visual Studio, if you want to automate something, you need a license, which costs you around 5,000 to 6,000 Rupees. If you want to do some extra Microsoft office activities. You need the maximum office license, which is 70,000 Rupees. That said, with UiPath, you need not have Microsoft Office installed. You can still read the data and extract the data in an Excel format. You can then share the data from those automation activities with no third-party license cost and no software licenses.

UiPath can help save costs in an organization. There are so many legacy systems wherein you have so much data migration, and many things which are done manually can be automated and you can save resources while doing something new. 

I'm just an end-user. 

My first experience with automation was, "Okay, which product to learn?". After all the reviews and reading, I decided to start with UiPath. My previous background was .NET web development. I was a full-stack web developer with seven-plus years of experience and I found that I really like when a product is built on a .NET framework. I realized that "Okay, it's better to do something, learn something and I have a background of the platform so let's start from there".

When I started using this product, I found the academy was quite open, and in the forum, there were people who were training as well. I found that while I may not get 100% of the answers I need, 85% to 90% of the time the answer is there if you search. 

Many people do not know RP automation, and it's great that they have these free resources - which is rare for such a product. Each region has a chapter where people working in this area come and share their knowledge and experiences.

Currently, I'm using the 2019 version of the solution. It's not the latest, however, it's not much older. I'm using the enterprise as well, which is free for 60 days. I started using UiPath apps as well. I'm learning so I use the cloud orchestrator to deploy my processors. 

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