UiPath Reviews

Our primary use case is to document image processing. We're six months in, so our first case was sorting and filtering the data, extracting the image, and determining if it's a certain type of document. If it is, it starts putting it into different buckets, which ultimately we'll run something to extract and put those into our data source. 

Our second use case is for the healthcare industry. We're looking at catalog data and a customer might want to know about a product. Is this product safe? Who provides this product? Is it on a contract somewhere? We go out to multiple different web sources to look up information about that document, put it back in our database, save it for that customer, then save it for any future customer that asks the same question.

We're looking at other things like taking snapshots of the image of the product. We also want to automate other basic automation, low-hanging fruit type functions, like automating uploads of data to sites, spreadsheets, contact-center, and Salesforce.

Longer-term, we want to take what we're doing in the document image and apply it to other areas of our business. We have purchase orders, invoicing, shipping documents, compliance documents, credential documents, a lot of images in this particular space. We'll go as deep as we can in the data processing side of things.

We're going through a culture shift to get to an automation-thinking platform as opposed to a lot of our business relying on BPO humans to do the work. Making that paradigm shift is taking time because we're only a week-plus live. If we prove the value, they'll give us more opportunities to make those big changes. But it's good that the business is thinking that they need this. Now it's just getting the community aspects of it.

The automation cloud offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates. 

Although we don't use it, document understanding for our use cases is very compelling, but it was a little cost prohibitive just out the gate. We are looking at it long-term now that we have the data filtered if we can more strategically apply it to the best data to fit it. But overall, the platform is very innovative. I don't think I can call out one particular feature. The ease of use of integrating to and from Amazon components, being a cloud-native application ourselves, has been really helpful in the development and the ease of transferring documents between our internal systems and platform.

The ease of building automations using UiPath depends on the use cases. Overall, the development is really easy. Where you run into challenges is in workloads that are highly rule-based. So we abandoned one use case where it had 50,000 different decision points. It wasn't worth the time. It wasn't a product thing. It was just too time-consuming of a process, something like that.

There have been some limitations as far as how do we execute our bots, when? This new release that they just mentioned today actually addresses a lot of our concerns around the integrations component that they recently released. If we could find an email instead of waking up and checking the email inbox. That's a big improvement we're looking to, but it wasn't a limiting factor.

I have used the Academy. It was really just myself and as well the one IT guy who's supporting the platform. Our office partner came in with the knowledge, but the course was really good. We came in with no RPA experience, and it covered everything from the basics of RPAs to the processes of identifying.

They recently addressed a major problem of kick-off processes for the integration function. That addressed a lot of the community concerns around that. If you are using queues, their queue system isn't as reliable as I would like it to be. 

One of our concerns is that we were not a Microsoft shop at all before bringing this in. That was actually my limiting factor in bringing in the software. We lost it below the party lines. The ability to address other workloads, Mac, Linux, etc., is going to be a game-changer.

From a new customer, new investment perspective, there are a lot of cost-prohibitive aspects that we decided not to add to our initial investment. We weren't sure if or when we'll figure things out for use cases.

I have been using UiPath for six months.

We want to triple our capacity and triple our workflows. 

I've only had to use support once, and it was more of a documentation problem. I didn't understand what I was seeing, and they worked it out within an hour. So far, they've been good. 

The cloud was up two days after we signed. Then to get our bot infrastructure up because it's Windows and we're in a Windows environment, it took us about a month to run through that and get the IT people and security.

Cloud solutions will save you a lot of headaches and time. We broke halfway through and decided we're going to cloud, not on-prem.

Reputation was a big reason we went with UiPath, as well as the growth and the ability to integrate specifically to the cloud which was missing in other solutions. That was a big plus. The ability to use something like document understanding and the ability to interact with internal APIs were also key features. It's not just web scraping and doing things in Excel or other things like that. We wanted it to work with our internal native applications.

UiPath has not yet saved costs for my organization. We're still going live and we're anticipating about a two-year ROI.

Make sure to understand your use cases before you sign your agreement. That way you're not idle for six to nine months trying to figure out what it is you're trying to automate.

I would rate UiPath an eight 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.

We are a UiPath customer, working with them to develop some products. It is a bit of a mixed thing where we are developing some products with them from scratch, but they are acting as the provider. We develop things, and if they're useful for others, then others can use them.

We are doing some pretty bespoke things to help us develop some solutions, but also help them develop their UI solutions in the legal area. We are working on a few things with UiPath to develop some search robots, some solutions to automatize subcontracts, and some timekeeping entries. These are several things that we are doing right now.

We are doing three things with them:

1. A robot to help us with software for time management, automating time entries. 
2. A robot to help us with filling in our engagement letters (contracts). 
3. A robot to help us with various public searches, i.e., the automation of searches of the public record.

We are adjusting robots from similar things that they do. The robots are not yet in production. 

The most valuable feature is its ability to save time with a task. In general, it improves accuracy as well.

UiPath's ease of use for automating our company's processes is a five out of five. We have found it very easy to talk to them, identifying what can be done along with the potential use cases. They have been very good at guiding us through what is realistic at this point, how their robots could help us save time and improve accuracy, and how our users can engage with their robots, e.g., ensuring that users engage with the robots and use their product. 

When we started to talk about practical implementation, their team was extremely switched onto identifying and fitting their product to our needs. They explained to us how we can use their products, what can be done to adapt their product, and what may happen sometime in the future, not necessarily now. I found this very helpful and straightforward.

What we have in mind in terms of what the robots could do for us is significantly more than what UiPath does now, but it takes more work. From my perspective, there is just a wide scope of implementation that goes beyond what we're starting right now. That is essentially the improvement. While I have nothing negative to say about our experience with them so far, I think we can work to develop more complex products with them. They are already working to develop something for our use cases, but what I would like is if we could develop more things for more complex needs, e.g., where we start with simpler stuff, then we can add things to what we're doing now.

We are in the development phase.

It is too early. We are still in development.

During the development phase, there are five people involved in the development phase. The users will be about 100.

We have not used their support.

We were not previously using something in this area. 

We have been thinking about ways to streamline our activities using technology. It happens that we knew UiPath, so we started to engage with them about what they could do for us. We had something like 20 ideas that we could implement, then we just started the easier ones which were closer to the products that they have. As things go, we will see whether we expand to other things.

We have known UiPath quite well and for a long time. They are also the leaders in the field, so it was a very easy choice.

The initial setup was quite straightforward. We started to discuss potential solutions, then we met with parts of their team, developing that business area. After that, we met with the technical people designing the product. We had a couple of initial conversations and did some testing. It has been extremely simple and straightforward.

We are supposed to review some of their proposals and provide feedback. We are probably a week or two away from production.

UiPath could have probably implemented the solution in a couple of weeks. We had some delays on our side.

We did the initial setup ourselves.

It is important for whatever we implement that it's cost effective in a sense that the robots will replace some human time. If human time costs less than the robot, then that's not a good deal. Normally, human time will cost more than a robot, and that's what we're trying to displace: the human time. We want to replace it with a cheaper robot. 

We only looked at UiPath, because we know them quite well.

So far, the experience has been excellent. I would rate the solution 10 out of 10, but we haven't finished the implementation.

Look internally what your needs are. Try to identify what you could improve with software robots, ensuring these needs are clearly identified and the product is fit for purpose. Also, you should make sure there will be buy-in in the organization, so people will actually use the product.

I have been using UiPath to develop automations for my company. We are a manufacturing company that uses SAP as our primary enterprise application. We are currently meeting with many different business areas and hearing about all of the different processes that they would like us to automate for them. Since UiPath works within SAP, it should help us get some easy wins!

UiPath has allowed us to remove tedious work from our daily process, saving us hundreds of hours. We are currently using it to process separations for people leaving the company. This was a 100% manual process before UiPath and it was required to be completed hundreds of times each month. The team doing the work was extremely overworked and UiPath has allowed them to see a little bit of light at the end of the tunnel. 

Orchestrator is essential, but I love how Studio includes so many activities that are pre-programmed to do what is needed.

Who doesn't love the recording feature? A recording is great to use when doing the first build of new automations!

The most important feature of all is the UiPath community and the forums, as they have helped me with countless questions!

One of the problems with UiPath is that it doesn't interact with some programs, such as AD and Chrome, and it would be great to have even more included!

We have been using UiPath for six months.

So far we have not had any issues with the stability.

We have not scaled, but from what I've read it should scale easily.

We did not use another solution prior to UiPath.

Understanding how everything connects was a little difficult, but UiPath offers classes that walk you through the setup. With the classes it was much easier. 

We implemented using our in-house team.

Do your research, the infrastructure piece is important to understand before purchasing. Also, you need Orchestrator to implement UiPath properly, so don't let anyone tell you different!

Finally, you don't need to start with 100 bots... my advice is to start small and then scale. 

We looked at Automate Anywhere and writing scripts, but UiPath seemed like the best path.

There isn't much that I don't like about the product. I love all of the new features and products they are releasing this year, and I can't wait to see where this goes in the future.

We use this solution for our business purposes. We use it from the back end all the way to the front end. That's where we are looking to use this, although we haven't fully implemented it yet. We are exploring more processes to use it for.

Mainly, this solution has reduced the need for manual intervention. That's the main thing. It has saved us time. We can now increase our ROI.

We run a few automations in a virtual environment, but not all of them. I've been using some other automation tools, like QTP/UFT.

I would rate the ease of use of the platform for automating our company's processes as four out of five.

Its intuitiveness is great. This solution is very user-friendly. There is almost no need to have programming knowledge.

The solution has helped us eliminate human errors, by about 40%. It also saves us time.

The solution is fairly stable. I would rate it as four of five for stability.

So far, we have almost 50 people in our organization involved in our automation program.

The initial setup was in between simple and complex. As even my colleague was fairly new at that time, he came across a few challenges. However, he could overcome them and now I'm in three of the processes that are in products.

It took about three months from the time we purchased a UiPath license until our first robot was in production.

We used a consultant. I would rate them as four out of five.

We have definitely seen a performance benefit. Now that it is in the production processes, we are able to see ROI, in terms of saving time on repetitive tasks and the manual effort saved. That's our return on investment.

I would rate this solution as eight out of ten because it has saved us a lot of manual intervention, as well as time and money. We may have not yet explored the full horizon of what this solution can do for us.

We are using Studio and Orchestrator.

Our primary use case is automating data processing for clients translating into other systems.

We do not run our 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 three. I think that the technology that we use in the printing industry is a little more difficult to automate.

I am currently involved in the UiPath Academy training. We have third-party contractors who have been doing the development, and I am the first internal employee who will be developing. I find that the training is good in the first step, and also in the second step where we're learning about Orchestrator. However, when it moves to the third step and they are talking about the framework, I think that it is a pretty big leap and that is where I'm struggling. This is the section that I am in right now.

There was one project that was completed before I started, at my understanding is that from the point that we purchased our UiPath license until we had our first robot was less than six months. For my project, it has taken two months.

Using this solution has allowed us to enter a lot of customer data into our system in a much quicker and more efficient manner.

In terms of eliminating human errors, this solution has definitely helped. I would estimate an eighty percent reduction in the number of errors.

With respect to saving time, automation has taken a process that used to take two or three days to perform, down to several minutes.

The most valuable feature for us right now is being able to automate our process applications.

In the training, between steps two and three, there is a pretty big leap in terms of how difficult the material is. Moving right from the basics into the framework is causing me to struggle a little bit, and I think that there is room for improvement here.

With respect to the stability from a bot perspective, on a scale from one to five, I would rate this solution a four. It has been pretty stable for us.

We have less than fifty people involved in our RPA program at this time.

We have contractors who are doing our development right now. On a scale of one to five, I would rate our experience with them a three. They seem to be struggling with the PDD.

In the project that I worked on, we have definitely seen ROI. We replaced a process that was being done manually, so we began to see returns immediately.

For the way in which we are using this solution, the features have been working very well. Our company is very young in this so we are still learning. We will get a lot out of this solution.

If you have a lot of manual and repetitive tasks in your company then this is definitely a great solution for you. That said, I know that things can always improve.

I would rate this solution an eight out of ten.

We use unattended robots and the Orchestrator module. I am most familiar with the Orchestrator. We are very new to this solution and just getting into it.

We are a financial insurance company and we do VoW, Verify on Web. We have a bunch of different insurance carriers.

We run automations in a virtual environment, VMware, and I haven't seen any problems with it.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a five. For my part of it, this solution seems very useful. I have limited exposure to it because I do more of the installation, the configs, etc. I don't really work with the workloads, although I see what is being worked with. We have our in-house developers who are doing the integration into our in-house programs, so I watch what they do and it just seems that it's very easy to pick up on.

I have not used the UiPath Academy, although I think that the developers have. I did not get any feedback from them about it.

I was not involved at the time, but I think that from the point that we purchased our UiPath license until we had our first robot was approximately three to four months.

In terms of eliminating human errors, I would say that we have a twenty-five percent reduction in the number of them. However, it is hard for me to say because I'm not that clear with it prior to the incorporation of the robots.

With respect to saving time, because of the commitment to the development and the installation and the bringing things onboard, at this point, we have not saved time. In daily operations, we do save time. I would say that we save between twenty and forty hours a day.

Our organization has improved because of the time savings. We've got robots now taking ten seconds to do what people were taking four to six minutes to do. It's a whole department of people that are now free to do other things.

I like Orchestrator and how easy it is to manipulate and get your data, to see what's going on. My job is to make sure that the system is running, so it's very easy to go to the Orchestrator through the dashboards. If it's not running, you'll see through the logs what's not running and what has caused the problem. At that point, normally, I escalate it to whoever needs to work on it.

The company likes this solution because of scalability.

One of the things we're struggling with it how to project how many robots we need to do these processes, so better documentation or assistance in this regard would be useful.

With respect to the stability, on a scale of one to five, I would rate this solution a four. I cannot give it five, yet, because I have just not had enough exposure to it.

We have about twelve people working with this solution, from developers to the business side to the IT side.

The idea of RPA was brought back down to me from our VP of IT, but I'm not sure where he got it from.

We have already seen a workload that has been moved off of our employees. It was within the first two months of the bot being developed. It is not my place to say the amount, but I can say that it is substantial and six digits. 

From a cost perspective, the unattended bots are going to be a major saving for us. We have a lot of mundane, routine tasks that need to be done. I have not done very much with the attended bots, so I'm not sure how we might benefit from using them.

My advice to anybody who is implementing this solution is that knowing what it is you want to automate is the most important thing. We were kind of blind walking in on that. We had one process we looked at and now it's throughout our company. People have all kinds of ideas about what we can do with automation.

I would rate this solution an eight out of ten.

Internally, we use UiPath to automate financial transactions, specifically for invoice processing.

Externally, on the client side, we use automation in the financial space, primarily. There are various use cases from generic file uploads to transaction processing that we implement for our clients.

We have some processes that haven't been completed flushed out. Right now, there has not been an exact improvement yet.

Ease of use and speed of development are the most valuable features. 

The overall integration with Microsoft stack and a few other third party vendors, like Google, are very useful to us. Having these built into the product speeds up our development, so we don't have to code a bunch of connectors on our own.

I would like to see some sort of better implementation of the Python modules. Right now, any error code that Python throws up turns into a generic error that is difficult to track down. I would want to see some sort of integration that at least lets me debug the issue.

Its pretty difficult to do source control through the typical Git functions because of the nature of the UiPath and the visual element. Some sort of method to bring source control home for us would be very helpful. A way to systematically track which actions or activities were added and subtracted from a given process before adding to a repository would be very helpful to us right now. Our team of developers is growing, so control has become somewhat of an issue for us.

Ease of use has definitely exceeded expectations. Initially coming in, UiPath had some features that needed to be implemented that weren't quite there yet. Now, we are on 2018.4 and all of the features that we desperately needed are there. Thus, ease of use has been pretty great.

We have looked into scalability a lot. So far, we haven't done anything that involves a 100 bot. However, the scalability seems pretty easy. Scaling up to just five bots running in parallel has been very easy.

If we are going to build up the environment, we would run on virtual machines. We would connect through Remote Desktop Services, not through Citrix.

The technical support has been fairly good. I like that they pick up on interactions in the forum. However, some of the transitions from the forum to submitting a ticket are a little clunky. If a ticket could be submitted on my behalf on the forum, then have me boot over to where the ticket is, that is fine. Just kicking me out of the forum, then having me submit a ticket seems counterintuitive to me.

As a company and for our client, we see any sort of legacy system or too many individual systems as somehow needing to be integrated. This is the bread and butter for RPA, and where we started our conversation (and our clients' conversations).

The complexity of the initial setup depends on who you are. First time implementing, it seems a little complex. If you know how to develop UiPath, it is more straightforward. I had to walk somebody through the implementation setup of the environment because they had a lot of questions about where they were going. For software development is not that complex, it is pretty straightforward.

Having some understanding of database management and services is helpful, so you understand the inner workings of UiPath.

It has definitely eliminated human error in our internal process, somewhere between full production, deployment and testing. There were definitely some error prone tasks that we eliminated. If I had to give a ball park, maybe 10 to 20 percent of the process was error prone, which we were able to resolve with UiPath.

For time savings: What used to be a 15 minute task, now it takes the bot two minutes for the bot to run through, for example.

Generally, we push unattended. We think the cost savings is better with unattended. As far as ROI, when you are talking about returning man-hours or moving people off work, unattended does that efficiently. Attended doesn't always save much time. Thus, we push unattended for cost.

We have seen general platform survey before implementing RPA of the different market vendors.

Personally, I looked at other platforms, and it is hard to transition from UiPath. It does have ease of use that now I am used to.

If you are starting with development, start with the UiPath Academy. For the end user or client, start conversations about security and prevention now, while you get trained up on development.

Internally, there is not a lot of automation in place. We are using a good robotic process automation software to bridge that gap right now and get us further down the automation road. 

We use the UiPath Academy for new hires. The new training programs, both the previous and current versions, with the UiPath Academy work out for us. I have the previous videos, then the current new slide deck idea. It is pretty streamlined and high level, but it is good for getting new people started.

Also, I used Academy just last week. I used it for security because I had some knowledge gaps on security with UiPath.