UiPath Reviews

We use it for unattended automation. Most of it is centered around finance for various reporting purposes. We also use this solution to move data between systems.

The biggest improvement is giving people time back in their day. We're still not where we'd like to be with our automation journey, so we don't have the time savings that we would like at the moment. However, we are continuing on that journey and helping to free up users and allowing them to work on things they want to work on.

The Excel integration is definitely good. We use that a lot because our finance department uses Excel. Overall, I really like Studio and unattended automation. Automation Cloud is very good as well. The platform as a whole has been good for us.

I like the UiPath user community, and the forums are really good. Most of the time, I can find answers there to any issues I'm having. The UiPath forums are very active, and I like seeing the employees in there as well.

We onboard any new developers that we have for RPA using UiPath Academy. It reduces the amount of training time in which the RPA team is involved because the Academy courses can take care of a lot of the fundamentals on UiPath.

Integration is an area for improvement. I still encounter issues with it, like getting errors when I try to use a connection.

We've been using it since 2019.

I have no complaints regarding the stability of UiPath. We have never had any issues with regressions or weird bugs.

We're still in the early stage of our journey with UiPath. Right now, we have six unattended robots and about 25 processes running on those, which is not at a scale where we might see issues. However, I have no complaints with regard to scalability so far.  Also, achieving the scalability we may need seems pretty straightforward.

UiPath's technical support is on par with that of other companies. We seem to spend a lot of time sending logs back and forth, and because of that, I would give technical support a rating of seven out of ten.

Neutral

The initial setup was not too bad. We started in the finance units since they were the ones pushing for RPA, and they've been our biggest internal customers so far.

We worked with our reseller who guided us through the entire setup. They did a few automations for us until we had that practice in-house.

In terms of ROI, we are saving more than what the platform costs us. We are at about 1.5 million in savings due to recent automation. It was a little less than that before. These are soft savings and don't show up on balance sheets. We're trying to work toward automation that actually do lead to hard savings. We've saved about 43,000 hours in a year so far.

The licensing makes sense, but it does lead to a few adoption issues when a lot of the licenses are per user. Convincing some of our business units to pay for user licenses for either Action Center or attended robots can be a roadblock.

We looked at Blue Prism. The biggest reason for going with UiPath is that we are a heavy .NET shop. Therefore, the fact that UiPath is based on .NET and that we can write our own custom activities in C# bar and Visual Basic were big factors for us. It meant that we would be able to adopt UiPath faster and that it would fit with our current Microsoft stack as well. We also liked where the UiPath platform as a whole was going, becoming not just RPA development but integrations as well. In comparison, Blue Prism seemed to have stuck with RPA and not expanded much beyond that.

Take a look at UiPath's platform as a whole and what it can do aside from just RPA automation. I would also advise you not to discount the tech stack. Overall, I like the platform, and I think it's headed in the right direction. Because of that, I would give it a rating of nine on a scale from one to ten.

Our primary UiPath use case is reconciling data and getting data from the web and writing to either Excel or our system. The automations are very reliable. 

Task Capture is quite a helpful feature because it is easy to design a process flow with it. All you have to do is just capture it and then do the manual process. It then gives you the process flow and the process definition document, PDD, so it saves you a lot of time.

The database connectors I found are not fully free and expire after 30 days. That is something I would like looked at for MongoDB specifically. With regards to this, I was working on a project that needed a robot to read data from a MongoDB database. To achieve this, I used the CDATA ODBC driver because I couldn't find a direct Activity to achieve this from Studio. See the link to the CDATA ODBC driver for UiPath here https://www.cdata.com/kb/tech/...

It would also be great to have UiPath Insights included in the free Orchestrator. The Insights module is currently only available for paid licenses. It would be great for developers to have it included in the free version because then we could try it out. 

I have been using UiPath since May 2018, and have recently worked with UiPath Process Mining. I am currently not very actively using this tool because the projects I'm on at the moment are using Power Automate. However, I do look at it once in a while.

UiPath is quite stable. I have not seen any inconsistencies come up because even exception handling is well set up in case of bad themes. Transformational processes are well managed, including exceptions, so that adds to the stability. Also, you can scale out from one bot to tens of thousands, so automation is quite easy with UiPath.

Very scalable

The initial UiPath setup is straightforward. You just go on the cloud, create an account, and you get the Orchestrator right away. From there, you can download the Studio. So once you build the automation, you just publish it from the Studio and you can run it. It's a very seamless process.

There is no need to hire an external team. You can do everything yourself. Also, the forum is quite busy and active. You can get a lot of helpful material there.

I cannot give actual figures, but I have seen a return on investment especially in processing invoices. It used to take us a week to read certain invoices into Excel but now it takes us only a day. So we are saving five Mondays in a week and 30 or 40 a month. 

From what I hear, UiPath's licensing costs are a bit high, but I can't evaluate that information because I haven't actually experienced the cost. We are using a free version at the moment. A good thing about the Community Edition is that they allow you to deploy even as a company as long as revenues are below $5 million I think.

I recommend automating the small processes in the Community Edition. This is the best way to evaluate how scaling would go within your organization. 

It is also important to fully understand what you want to automate. I also recommend trying the Process Mining feature to make sure you are able to pick up areas of automation within the organization's processes before committing to paying for automation. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The solution has saved costs for our organization.

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

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

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

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

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

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

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

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

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

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

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

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

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

Technical support has been pretty good. 

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

We did not previously use a different solution. 

I personally implemented the solution at my company. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Overall, I am quite satisfied with the product.

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

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

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

UiPath is the go-to tool if you need to automate tasks that can be combined to create an automated process. We provide services to customers using UiPath. They come to us with their needs, be it to improve performance, accuracy, or reduce costs, and we help them by automating processes that, most of the time, consume too much in terms of unnecessary human resources.

We have many successful cases where the customer has noticed an important reduction in processing time while also maintaining excelent quality.

This solution is especially efficient if the process being automated involves legacy applications that do not and can not be automated using APIs.

UiPath is great for desktop automation because it integrates well with applications and we are able to tailor selectors to our needs. 

One scenario where it is not great is on remote desktop automation, where applications are not directly accessible. It does, however, have some features to facilitate this kind of automation and definitely stands out from the competition because of things like that.

I have used UiPath for the last nine months.

The product is very stable and no weird behaviours should be expected.

This solution is extremely scalable. It has a cloud platform to manage the workforce and can work with parallelism.

The support team responds fast and seem to be interested in solving problems.

I have used Kryon.

The initial setup is not really complex.

We implemented UiPath through a vendor and they seemed to be experts.

Our ROI varies from project to project.

There are different licensing options and you should study which one better suits your company's needs.

We did not evaluate other options because we work with the tools that our customers buy and we do not get a say in what they acquire.

There is no doubt why UiPath is the market leader, it is very robust, flexible and has great learning material and documentation. The team and community behind this product are amazing.

We are using Studio and Orchestrator.

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

We run automations in a virtual environment.

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

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

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

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

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

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

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

The user interface is good.

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

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

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

We have about six people involved in our automation program.

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

For my processes, everything was done in-house.

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

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

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

I would rate this solution a nine out of ten.

We use all of the products in the UiPath platform.

We have use cases ranging from back-office to manufacturing, which include large project management, accounts payable, accounts receivable, and treasury management. Most of the areas in the company have processes that we have automated.

We run our automations in the Citrix virtual environment, although we are unhappy with Citrix. It is pretty bad, and it's very difficult to keep up the performance. AVS or Azure do not offer a good service yet, but we are looking for alternatives with respect to the virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. We have been using UiPath for quite a long time, and we have seen this evolving. It has been getting better over the last few years.

On a scale of one to five, judging how beneficial it is, I would rate the training between three and four. The training is good, but the content doesn't have the depth required for people to go ahead and do something if they're not technical. It's still pretty high-level.

From the point that we purchased our UiPath license until we had our first robot was three to four weeks. The process is getting better, but when we started in 2016 and UiPath was small, it was good but needed refinement. I would have rated it three out of five back then.

Using this solution is enabling us to move the drive for digital transformation to the core. We can now take automation to a level it has never been to.

In terms of eliminating human errors, we have seen benefits. With humans performing, the accuracy was at approximately ninety percent. Our accuracy with automation is now close to one hundred percent.

With respect to saving time, we have seen FTE savings but the numbers are confidential.

The most valuable feature of Studio is the ease of use. It is really easy for people to learn the basics and the learning curve is not steep.

Orchestrator makes it very easy to manage the platform.

Orchestrator needs to have better integration to include business users.

With respect to the stability, on a scale from one to five, I would rate this solution between four and five. Stability has been getting better. For example, Studio used to have a lot of bugs when you were developing and when you were capturing the screens. Now it's been getting better, but there is still room to improve.

Orchestrator used to lag quite a bit when there were a high number of transactions, and there is still room to improve.

We have at least a few hundred people involved in our automation program.

The technical support for this solution is pretty good. Whenever we had trouble they were always there.

We did not use another RPA prior to this one. We were looking at improving the efficiency of processes and bringing some innovative solutions to automating tasks and processes. This is when we decided to try RPA. 

We implemented this solution on our own.

We have seen ROI but I cannot share the specifics.

We did a very extensive vendor review. We had all of the major providers of RPA solutions in 2016, and UiPath was the one that came through in terms of fulfilling all of the criteria.

Looking ahead at the features that are being released this year, they seem to be what we have been looking for.

My advice for anybody researching this type of solution is to choose wisely. There are a lot of products out there, but few of them actually work.

This is a good solution and they are releasing some features that I am looking forward to, but there is still room to improve. 

I would rate this solution a nine out of ten.

I work for the financial management office. We do a lot of manual processes. Our use case right now is that we look at all of our financial business processes, break them down, and identify the subprocesses that we can use UiPath to automate. This is very manually, so we try to find some efficiencies which have the most the value for our organization.

The most valuable feature of UiPath is we have direct access to read and write data in our applications, so we don't need to build a back-end interface.

The security needs improvement, especially in regards to managing the credentials.

I would also like to see better integration with Microsoft products.

We still have to test the final product. UiPath's recommendation is build another bot to validate the other bot's work. That is the scary part: If you make a mistake creating the bot, how can you recover from that mistake?

A lot of Elastic is not working, which is why the solution is not integrated.

While the commercial solution is successful, the government solution needs improvement. Government has so many regulation and requirements that still need to be address by the product.

It's a bit choppy, so people need to find workarounds.

We haven't deployed our first bot yet, so we are unable to gauge bot stability.

We tried to set it up in the virtual environment because we want to leverage a lot of the Microsoft features. They need to include all the API features going forward to make the virtual environment effective.

We are working closely with the UiPath technical team because we are pioneering putting this infrastructure on the cloud. 

The technical support team is responsive.

There is a big community.

We rely on our partner to identify a solution and give us a recommendation.

We set it up in Studio and Orchestrator. We are also ready to put the bot on our Amazon Cloud environment.

We had contractors, a consultancy company, help us build the system. They are a really good team, who also help deploy the solution for government agencies (DHS and DoD).

There are a couple options on market, like Automation Anywhere. UiPath is one of the leaders, so we picked UiPath.

Automation Anywhere is not on the DHS approved vendor list, so we couldn't pick them, as the approval process would take longer for them than UiPath.

Use UiPath in a more process-driven way, instead of BI-driven way.

We put everything on Amazon Cloud, even our development is cloud-based.

We haven't had a change to use UiPath Academy for RPA training yet.

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.