UiPath Reviews

We use UiPath for replicating manual tasks and PDF automation. 

UiPath saves us a significant amount of time and is recognized as the leader in Robotic Process Automation. It helps us a lot. It makes us much more efficient at dealing with repetitive tasks, reduces costs, and makes automating processes easier compared to other automation solutions.

The solution reduces human error; automating manual cases lowers the risk of error by over 90%, including recurrent mistakes. This keeps our clients happy.  

The product frees up a significant amount of employee time by automating manual tasks and being so user-friendly and time-efficient, meaning we don't have to spend much time using the app. 

I like how easy it is to automate tasks and how time-efficient the product is.

UiPath is very user-friendly, so even employees with no coding experience can use it, which adds value to staff with less experience in coding.

Building automation using UiPath is easy; creating scripts for automated test apps and PDFs isn't difficult.  

The solution enables us to build end-to-end automation, which is important to us, and it's one of the only automation apps that can provide this.   

We use the platform's AI functionality in our automation program, which has significantly contributed to our end-to-end automation. It's cost and time-efficient, and that's what we want from an automation app.   

UiPath speeds up and reduces the cost of digital transformation without requiring expensive or complex application upgrades or IT support. It provides features in a cost-efficient way.  

The interactive selection could be more accurate.

The customer support could be faster. 

We've been using the solution for between three and six months. 

UiPath is a stable app; I give it nine out of ten for stability.

The solution is scalable; I can't see any ways in which there would be a problem or limitation with scalability.

We contacted technical support, and they have solved most of our issues lately. Sometimes we don't get the solution we want and are dissatisfied, but overall, I rate them very highly.

Positive

UiPath is the only automation solution I have used. 

I wasn't involved in the solution's deployment, and apart from keeping the version up to date, it doesn't require any maintenance. 

The solution saves costs for our organization, though I'm not aware of precisely how much.

We didn't evaluate any other options, the company provided UiPath, and we didn't have a choice in the matter. It's an excellent product, and we don't have any problems with it. No solution is perfect, but that's to be expected.

I rate the solution 10 out of 10.

We use UiPath to automate processes that deal with a ''good cause'' we are involved in; specifically, we use it for employee diversity.  

The product's automation helps a lot in achieving the results regarding our ''good cause''; we encounter fewer errors compared to other automation apps.

Being a part of the UiPath user community is valuable.  

I recommend the solution and have recommended it to many of my friends who work in the same domain. 

We have yet to use any UiPath Academy courses, but we plan to in the future.

My organization is an outsourcing company. We work with various clients. So, we have many use cases. The current use case I'm working on is related to invoice processing.

We don't use attended automation. We use its AI functions a bit. Usually, we work with document understanding.

Currently, I'm using the latest version. It is deployed on the cloud and on-premises. It is the UiPath cloud.

It is easy and fast to build automation using UiPath. All of our automations are created with UiPath. Usually, we do automation for SLA purposes. Most of the time, the clients don't have enough resources or humans to do the job, and they need automation to improve the SLAs.

It enables us to implement end-to-end automation, starting with the process analysis, robot building, and monitoring of automations. It is good for my company. With these benefits, we can implement it and help with the monitoring.

It has reduced a lot of human error. For example, in the project that I'm working on, people were putting the invoice information on a daily basis. There were more than 20 invoices per day, and each invoice had more than 100 line items. Humans would do a lot of mistyping on the number of packages or the number of items in the package. After we applied the document understanding solution there, we can handle around 90% of invoices, and all of them are correct.

It has absolutely saved us time. It has probably saved us more than 20% of the time. People now have more time.

I feel comfortable with UiPath. The thing that I like most is that UiPath has a very large community and a large ecosystem. So, it is easy to connect with other applications or platforms.

UiPath Apps is a great feature, but it still needs time to evolve. They need to add more features. It hasn't increased the number of automations we can create while reducing the time it takes to create them.

I don't like the sequence feature in the UiPath. It is difficult to analyze and read the code.

The variable management is really messy. When I look at the code, I don't know where the variable is and in which scope.

I have been using this solution for around five years.

It is stable.

It is scalable. We have had three enterprises that are really big with more than 1,000 people. The others are small companies.

In our organization, we have 12 people working with it.

I haven't contacted their support. I have been using UiPath's support indirectly. I just put a question on the community forum, and they answer it very fast.

In the previous version of UiPath, it was a nightmare to set it up, but now, it is really comfortable and convenient. Overall, it is fast, but the deployment duration also depends on the solution. If you design a good solution and follow the best practices, it is really fast. It takes a couple of hours at the most.

We always try to split a project into small parts so that we can test each part and apply it easily. I have seen that many people create very big projects, but when you complete them, you cannot test them. It takes a lot of testing from end to end, and we still can't test it completely. That's why we try to split a project into small parts. We can test each part independently, and after the integration, we can deploy with high confidence.

I am not sure how long it takes for our clients to see its benefits after we deploy it for them.

We have a maximum of five people for deployment and maintenance. We sometimes have issues with the infrastructure. In many cases, the infrastructure is handled by the client, and there is no support or cooperation between the RPA department and the IT department. Usually, they will be late, or they did not check our requirements to deploy the bot.

If you use the cloud model of the UiPath, it will reduce a lot of the total cost.

Its AI functionality hasn't enabled us much to automate more processes. Most of the time, when we propose those functions, we don't have an agreement with the client because of the license price. Currently, the license price is the major obstacle.

My advice would be to contact the UiPath sales team directly. I know that they have different license models for different clients and regions.

I would advise following the UiPath Academy and their best practices. That is enough.

They provide very valuable templates for automation purposes. It depends on your purpose, but you can apply the ones that are already there.

I would rate it an eight out of ten.

We have a variety of projects we use it for. We have automated about 72 processes within six verticals, including sales, finance, HR, and purchasing.

It has helped our client save thousands of dollars, for sure. That is really what they have found to be the biggest benefit of using UiPath. The cost of the product is low because they're using it continuously. It saves cost and it helps them gain more returns.

Our main projects are mostly around SAP and Excel. We have used most of the features available, especially the ones that support SAP and Excel activities. Those are the ones that we have found to be most useful.

UiPath is easy to use and there is less coding. That is very helpful for the development team when it comes to building projects. It's very flexible and really makes our team more efficient. The turnaround time of development is good. 

There is some scope for improvement, especially in the area of variables. Some variables are used in specific workflows and some variables are global. It would help if there was a repository that would showcase which variable is global and which is local to a workflow.

UiPath should also help us whenever we are changing versions. Whenever we make those changes, UiPath should help by documenting the versions and sending us comments on the changes made in UiPath. If that were available, that would really help.

I would also like to see something related to auditing. That would really help the development and peer review teams to identify the gaps, instead of going through the sequence one by one. If there were an auditing tool that clearly brings out issues, that would really help.

We have been using UiPath for four years.

UiPath is a stable solution.

They are plugging in a lot of features that are really helping our teams. It is scalable.

For this year, we don't have plans to increase our usage of the solution, but it depends on our client.

The technical support is good and they respond to us all the time. Whenever we require support, they are with us.

They have a standard questionnaire that we have to complete and send in, and they come back with standard responses. At critical times, instead of the standard response, if they could do a direct call that would really help us. Instead of one or two levels of questionnaires, if they could directly get on a call, that would help us. Hence I rate them eight out of 10.

Positive

I was not part of the initial setup, but I am involved in the renewals.

The renewals could be easier. The documentation is lacking. When you are renewing your licenses, you might encounter errors but there are no proper documents available to explain how to handle these errors.

In terms of maintenance, our automation processes require some attention but UiPath, as an application, does not, other than updates.

There is ROI over a period of years. From the second year onward, it would be around 25 to 30 percent.

The pricing and licensing are okay. It's quite affordable.

There are a few things that come with additional cost. They are mostly features. For example, Document Understanding is an additional feature that you have to pay extra for.

I would recommend it to new users who are choosing among automation tools. 

Also, if a company is new to it or the users who are setting up are new to it, they should be aware of the preparations involved in setting up the environment and setting up UiPath. That can be a little challenging if they are not aware of certain things.

I rate UiPath at eight out of 10. There are a few features or approaches they could enhance, such as an option to view all the variables, as I mentioned earlier. Also, since the code can be very big, we might be searching for certain things that are not available. I'm more concerned about the debugging and evaluation parts. 

And in Orchestrator there are a lot of features they can enhance.

We use the solution to speed up automation. We were looking to overcome the challenge of handling vast amounts of data, and we use UiPath to create bots to handle that. Tasks can be automated, and human error is reduced.

UiPath improved our organization as it has many benefits; it's straightforward and quick to use, has excellent third-party integration, and simplifies all our task automation.

The software has an excellent UI; it's very user-friendly. The drag-and-drop options are some of my favorite tools, as they speed up the process, and I find that UiPath offers a solution for all kinds of automation.

The solution saves a lot of time via automation; a task that took over an hour now takes around two minutes, and it's all handled by bots.

We use the drag-and-drop options, and they speed up our workflows.

The pricing could be more friendly. 

We have been using the solution for one year. 

The solution is stable, it's a reliable software. 

The product is scalable; it has very good third-party integration and scalability options within the software.

We use the solution in our office, so there are slightly under 100 total users.

The community support and documentation are helpful. I required some training initially, and was able to learn using UiPath websites and YouTube videos. 

Positive

I wasn't directly involved in the initial setup, but it took our team one to two months to get to know the product well.

I'm not directly involved in the financing, but the IT team considers this product costly.

I would rate this solution a nine out of ten. It's an excellent product, but there is always room for improvement. 

I highly recommend UiPath as it's easy to learn and offers significant advantages for all kinds of automation. 

The solution is perfect for our requirements. 

The solution has provided assistance with the removal of repetitive human transactional activities; document to text solutions; complex data extractions; cut and paste operations; information content management. This is either supported in promoting strategies with our business partners, or implemented at our clients, or included in products we develop for our clients. 

We use it in our own operations that have been migrated to other products or solved with coding or third-party software offering solutions to specific needs. Solutions are based on client sites and our clients pay for their own licensing.

The costs involved and the licensing model have forced us to recommend other solutions to our clients and to stop using UiPath internally due to constraints imposed on small businesses (specifically around the community edition). 

For our clients who can afford the licensing costs (Blue Chip Clients), the benefits have been to remove some repetitive activities from the target areas. 

In most cases, where there is a high-value resource impacted by these repetitions, there has been a cost-benefit in doing so, however, where the labor cost is below a certain threshold, the benefits are contained to error avoidance and reliability only with (additional) costs being migrated to support the technology and increasing overall IT OPS costs - particularly now with the increased fees and current licensing model.

The product as a whole is a valuable contributor to efficiency improvement. It integrates with ease (although some coding experience is required for higher/involved functions). We use it to streamline and support our customer operations primarily, but also to do internal acceleration on human-dependent (simple) tasks.

Simplification of complex task creation by introducing pre-coded objects is the single most attractive feature of the product. The choice between attended and unattended Bot applications with similar functionality is an advantage. 

Features are on track, however, service and cost models need to be reviewed to be market sensitive and related to the industry. Providing a great product at the wrong price without consideration to the economic conditions of the markets within which it is being offered, creates barriers and another product is sure to fill the void.

Closer integration with machine learning frameworks and matrix processing can be improved and will benefit low-cost/entry-level uptake and activation for some clients. Although pass-through options exist and have been activated, this is not sufficient to create encapsulated learning within the organizations and serves to improve third-party algorithms with added exposure to privacy (information systems security management) risks. 

I've been involved with UiPath since the launch in South Africa with Larc Technologies as the first UiPath solutions partner and reseller for the country.

No robotic solution can ever be classed as stable unless there are no change dependencies. It will always require more support than any other core technology - its the nature of the beast.

Running multiple robots in an environment requires orchestration, which is another expensive modality in the UiPath stable.

Consultations outside the normal service environments are strained, authoritative, and inflexible and there is little consideration for anything outside their immediate scope of vision and there is zero hesitance to move against initial strategic positioning and commitments. 

Neutral

We have been involved with and supported UiPath from the onset. We have also delivered enterprise solutions with BluePrism and Automation Anywhere. UiPath has proven to be capable, but costly and inflexible from a pricing and support model viewpoint.

It depends on the nature of the requirements and can be super complex or super easy. Supporting the bots are always a challenge and supervision (alerts, monitoring) is essential.

We work with excellent vendor implementation teams and have in-house competence in design and delivery. In most customer environments, there are competent implementation and maintenance resources for bot environments. Over the past 5 years, bot development, administration, and maintenance skills have improved, however, there is still a significant gap in proper orchestration and optimization within bot frameworks - which affects the overall cost and effectiveness of automation strategies.

At present, the ROI is negative for us as a company. For our clients, it varies. When all costs are considered (TCO) over a two-year period, financial breakeven is mostly attained with some negative ratios (if it's the wrong tool for the job). 

In most cases, there are intangible benefits. In all cases, IT operations cost increased and, in worst-case scenarios, the business benefit was short-lived as the technology costs escalated and the resource reduction potential was never attained.

HA and DR planning are essential when determining actual resource reduction potential.

UiPath is becoming expensive and will be outpricing themselves if they continue to enforce their current service configuration (model). Many clients have been impacted by the pandemic and instead of assisting to breach the gaps, there is a sense that UiPath is monetizing on the disaster.  

We looked at BluePrism, Automation Anywhere and we are now moving on to Open RPA - a viable option if you have the right skills to plug gaps. 

Our use case is mainly for PDF automation for invoicing. Specific data from the invoice needs to be gathered, entered into, and compared within the SAP application we use. We face challenges as the formats of the invoices change and can range in length from a single page to up to 100 pages. 

We've integrated a tool called ABBYY FlexiCapture and ABBYY will help format and be used as the source of input for the UiPath bot. This bot in turn will process each and every necessary customer detail to the SAP application. If everything is correct, and the data meets the parameters, an email will be sent to the customer, attaching the necessary invoice. If there's an exception, we'll be able to look at that too.

There are some other sets of use cases as well, which include SAP or Hyperautomation. However, we also do generic workflows where we have data from multiple domains and will need to build our XML output. The XML output will contain a lot of data (such as the date, time or name of the customer) which will keep changing and is not fixed. I built a bot using UiPath that I host on Orchestrator which can monitor this data.

Another use case is placing job descriptions into an analyzing tool to search for keywords. Depending on the sort of description which we have pasted in, it will throw out a certain set of outputs, such as if the word is feminine, masculine, how many details it contains, how long it's going to take to complete the description, et cetera. This part has been done using an API key, and therefore it's not a normal cut and paste job. 

There are a lot of processes that are, even today, done manually. I can take a simple process in, for example, ServiceNow, where issues are made into tickets and put into queues. Previously, a person would have to pick up the ticket and then assign it to a variety of people, but first, before even doing that, they would have to check in on those team members and figure out who had the most or least workload to be able to address the ticket.

This process is automated now. There's no human intervention in assigning tickets. The bot will monitor the queue and when a person raises a ticket and can monitor which person is working on which ticket number, and who should get the next ticket. The turnaround tie has been reduced by a lot and is also saving us costs when you look at it in relation to the entire project as a whole. 

The most valuable feature is the API.

It's really compatible with other solutions and it got integrated when I was working with ABBYY. There is no dependency. I just need to trigger my bot and that's it. I didn't need to go and separately trigger to work on every part of it. It is really good when we talk about the integration of UiPath with any other tools.

I am currently working through the documentation to help with understanding the solution and it is really great.

From a studio perspective, I really like the feature of debugging.

It’s making automation really feasible and ensures that it takes less time.

The ease of building automation using UiPathis great, even if a person doesn’t have a development background. Just by going to the UiPath Academy and doing the basic certification, any user can start to understand the process and begin automating.

In my first organization, there were two or three developers including me, and our challenge was that we had a lot of projects. We had certain process analysts that would run on different sets of processes. We were able to train them and make sure that they understood the processes and could start developing. We saw a lot of progress in them, and, due to the fact that the tool was really easy to use and didn’t require a lot of coding, they were able to do a lot just by drag and drop functionality.

UiPath enabled us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automation. It really supports the end-to-end deployment of any project or any task and makes it very easy.

The Automation Cloud has helped decrease time to value. If there was no Automation Cloud, we would need to run the bot from the studio all of the time, or we would need to create an upgraded file and trigger it via a third-party application, like VBScript or something like that. It has reduced a lot of time. It also makes deployment really easy. For example, if I am working in a development environment, I publish to the cloud, it will start reflecting in the Orchestrator and I just need to push the package. From the Orchestrator itself, I can trigger that particular package to any other machine. That makes life a lot easier - just publishing the package and testing in any other system and understanding how the UAT is going.

The deployment in production is really easy. I have tested Orchestrator and production Orchestrator and I just need to copy the package from the studio and download the package and push it back to the Studio or Orchestrator production, and the work is done. I don't need to manually copy and paste the packages again and again.

Automation Cloud, in a way, helps decrease UiPath's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates. There’s no need, for example, to host on different servers or a defined cloud. It has definitely reduced a lot of costs due to the fact that, instead of going for a different set of applications for a different set of projects, now we are relying on UiPath for most of our work. Whether it’s invoicing, finance, or an HR process, we can rely on UiPath to automate a particular process instead of going back and forth across multiple tools.

Automation Cloud allows us to also effectively scale up automation. It is very easy to monitor any process which is running correctly, and, with automation, you don't need to have any separate application downloaded into your system. It is just an URL. You just need to have a URL and you just need to enter the URL and you can monitor from any system and easily understand how the process is performing.

On top of that, with Automation Cloud, suppose you have 10 licenses. You can see how many licenses have been consumed by how many processes and what the outcome of the processes was.

Moreover, you can integrate your cloud with other tools and create a dashboard. With a UiPath dashboard you can see, for example, the percentage of success rates, the failure rate, and how many processes have been successfully done or what quality. From the management side, we don't need to go to the logs and check what has run. We can directly look into a dashboard and we'll come to understand how many processes are running successfully and what are the outcomes, and how many licenses have been consumed.

It is important that we can scale automation without having to pay attention to infrastructure. I’d rate the level of importance at an 8.5 out of ten. It is helping a lot.

When we talk about automating a web application or we need to work on a different set of applications, we used to get integrations and we needed to have, for example, a PowerShell scripting application license. Now everything is being replaced by UiPath, or most of it is. It does not require you to have a license for a different set of tools all the time. If you have UiPath it is easy to integrate with any third-party tool and it is easy to automate a web application or desktop application or even code. If I know the coding, I can just do coding right in UiPath itself. Instead of going for multiple tools, for multiple projects, it's just a single tool for multiple projects.

We can use the infrastructure and we can also host it. Suppose there are two users who are accessing the same VM over a different time zone. They can rely on the same VM and they can use the same UiPath tool and do not necessarily need to have a separate licensing for it.

UiPath has helped minimize our on-premise footprint. Mostly now, everything is on the cloud instead of on-premise and it is making life easy. For example, suppose a person who is working on-premise, if he logs out, then the other person can log in and cross-verify the work he has done. With the cloud, now the transfer of files is easy. If a person falls sick or something happens that he's unable to make it then the other person who has a login or credentials with him can just directly go in and start working. If a code is being published in the cloud, we can just copy or download the code and cross-verify how it's working.

We do use attended automation. We use it relatively less compared to unattended. However, in certain cases, where the project is too critical and we do need to run all the time, it’s nice to have that option. Attended automation helps scale RPA and benefits our organization by automating specific processes that require human, robot collaboration. There are certain processes where you can't automate end-to-end. We have to rely on a human being occasionally, and it’s nice to have automation we can collaborate on. At the same time, we do largely take advantage of automatons where no human intervention is required.

We use UiPath AI functionality, although not much is being used in any of the projects which I have worked on. I’m just looking forward to it, as I am currently working on documentation understanding before diving in.

UiPath speeds up the cost of digital transformation and has also reduced costs. I started with Blue Prism and then I got my hands on UiPath. Now, I can see the transformation which is happening and I can see the comfort which we have with the tool. I can also see how it’s a lot easier to deploy the tools.

The solution has helped our company reduce human error by a significant amount. For example, when I automated the complete process and I put everything in GPL step by step and automated using UiPath, the best thing that happened is that there was one invoice that got stuck and I could see that the bot didn't process it. The bot has sworn an exception stating that there is a certain set of values that a bot should not process, if it is not matching, the quality is not matching, then the bot cannot process it. When the customer logged into the particular invoice and they saw that, okay, the value which is being mentioned in the invoice is below the threshold critical value. For the first time in over a period of 13 or 14 years, they came across a particular invoice that got stuck with this particular amount, which was below the threshold level. The bot captured something that needed to be dealt with, and the client was so happy it was caught as it saved the company a lot of money - around $1 billion. After catching that threshold, they have monitored all the invoices for the past 13 or 14 years and they came across a lot of differences. It has played a major role in saving a lot of money.

UiPath has freed up employee time. The faster you deploy, the better. We look at months instead of weeks when calculating time. If a ticket, end-to-end, takes 24 hours to resolve, for example, with automation, we’ve managed to reduce that time down to seven to ten hours. It will keep following up and sending emails until there is a resolution, and those reminders are quite helpful in moving the process forward. It’s definitely allowed employees to focus on more important tasks and there’s less time spent on follow-up.

In terms of employee satisfaction, when we are developing something and we have a proper outcome, it makes life easier.

The product has reduced the cost of our automation operations. Not for all the processes, however. If the process is really simple, just like 10 pages or 20 sequences or 10 activities, then the cost is high for a particular license, for a particular process. That said, when you talk about the complex process, where the process takes 48 hours or 90 hours to process a particular activity manually versus what the bot can do in just five to ten minutes, it impacts the cost. Now, a single bot is taking care of that and there is only one person instead of many who monitor the process. Likely, it has reduced costs a lot, roughly 50 or up to 70%. Overall UiPath has saved costs for our organization. Processes that needed five people can now run with just one or two running things with a bot.

When the Orchestrator got upgraded and UiPath didn't get upgraded, we started getting errors regarding the managed packages, the packages were not getting upgraded. There are little things like that where we’ve had trouble. We have just made sure that if the company is upgrading and they have a license to upgrade Orchestrator and the Studio, they do it simultaneously instead of waiting for a week or two weeks or one month. If they have upgraded the Orchestrator, and they have not upgraded the studio, it will impact the developers.

In terms of the upgrading of the on-premise orchestrator, there are organizations that are upgrading their developing environment but they're not upgrading the production environment. Therefore, now, when the bot or the particular package will move from a higher-end environment to lower activities, it is not working well and it needs to get downgraded.

While delivering or providing the license, we need to explain to clients that this particular product, if you are working on a development and production environment, they have to keep them on the same packages or they have to keep your production higher, so that if they move the packages, it won't impact anything.

I've been using the solution for the past five years.

The solution is very stable. I have not faced any difficulties at all. 

Until now, it hasn't scaled a lot. From 2018 to 2021, the tool, the overview, the look and feel of the tool have been scaled a lot. It has scalability, definitely. We haven't scaled it a lot. 

In our organization, we have between 100 and 150 users on the solution.

The vendors are really helpful. Whenever we have a concern regarding any of the issues, including if there is an issue with upgrading, it gets resolved well. For example, when we upgraded the studio and didn't upgrade UiPath’s Orchestrator, there were some issues. The board was not connecting to Orchestrator. We had to raise a ticket to our support team and it got resolved. 

I'd rate them at an eight out of ten, as we've gotten a good response overall.

In the last five years, I have worked in two to three organizations. All of them have started exploring automation tools. I've used Blue Prism as the very first tool, then I got the opportunity to work with UiPath and explore the different sets of opportunities with it. 

At this company, WinAutomation was previously used. That was four years ago.

The initial setup is pretty straightforward. It's not too complex. 

We have a server we implemented the solution on. We installed the certificate to have the application installed with the Orchestrator URL.

The deployment took around two days of full-time work for us. There were multiple servers involved.

The implementation strategy was very simple. We got onto a call with the UiPath team and they had a lot of data with them, including all of the details regarding the applications. We wanted our certificates to get installed and we had our internal team involved as well. Between the two teams, it was working properly and it got installed in less than the expected amount of time. 

We have a team of 25 to 30 people that can handle deployment and maintenance. Maintenance would be, for example, if you have certain packages missing, someone would have to deal with that. Or if something wasn't working as required. Another example of maintenance might be if we are accessing multiple applications, or if we are accessing SAP, and there were tools that the bot accessed, the maintenance team would need to go and check the particular environment on which the bot is going to get deployed.

From the very first organization, I have implemented UiPath end-to-end.

We don't use a third party for deployment now. We have our own team. There's an internal team within our current organization which deploys everything.

I don't have any details in regards to the pricing.

We did POCs in the past with WinAutomation and we also looked at Automation Anywhere. At the time, we were looking to deploy more on the cloud, which is why we went with UiPath instead.

I am just an end-user of the product.

I'm not sure if the version we are on now is the latest. It likely isn't. We are in StudioPro currently.

I'm not sure about the infrastructure side of things, in relation to the cloud, as I'm more on the side of developing and deploying the project. We have an internal team that looks into cloud deployment and other stuff. While we were working on and purchasing the license from UiPath, the very first instance, then definitely the team got integrated with the UiPath team, however, after that, the internal team is capable of handling the end-to-end part of it.

We don't use UiPath as a SaaS solution and we do not yet use UiPath apps.

In the process of UiPath, speeding up and reducing the cost of digital transformation, I have never required expensive or complex application upgrades or IT application support, however, we have a different set of teams that work on the licensing part and the management side of it. They likely worked with UiPath to get their issues resolved. I do not have much knowledge regarding this.

A person who's starting on UiPath can also up-skill himself with the tool as well as it is easy to learn. 

The best part about UiPath is that they provide a trial version. Any organization or any individual or any business looking for automation solutions can give it a try. There are a lot of things which you can explore and you have a lot of integration. If we have a module that is already running, which has been designed in almost any language, you can just integrate that in UiPath and keep that running.

It is reducing a lot of dependencies on other tools and it's making sure that our lives get easier from the deployment and monitoring perspective. From the licensing and the cost perspective, there are a lot of items that are really helpful. In terms of integration with third-party tools, they have a lot of packages which are available on the internet. You can download the packages and integrate it with any other tool. It really makes UiPath a better solution for organizations compared to any other tool.

The biggest lesson I have learned from  UiPath is that if a single step of the solution is not working, you have to keep trying. There are other ways of doing things. You have options. There are a lot of ways by which a user can understand and explore.

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

I am an API developer and I use UiPath for development. I use it to develop solutions for banking problems, like banking automation.

For example, in my previous company, I used the API for developing automated reporting solutions that take a lot of Excel files, check their data, and try to generate a web page containing many graphics based on the Excel data. It's basically translating the data on the web and it's made automatically every month. 

For my current company, it's a banking company, and I'm working on the banking solution. It's a process of verification of the user identity or the client's details. This process is based on taking the ID card of the person and digitalizing the data. It's a technology meant for reading data from documents. After reading this data, we automatically take this data and put it into the database and create accounts for the user or do a lot of automated things. 

At my current company, the use case is for the process of managing the relationship between the client account and any fees. A robot always checks if there is something to pay for the client and can take the fee automatically if that is the case. Then there is a transfer of money based on the request.

For example, when someone wants to do a transfer they add the money and sign a paper. This paper contains the information of the client's account, including details such as the client name, the account number, and the amount of the transfer. We take the data and the robot automatically takes the data and, via the web, goes to the apps of the bank in order to search for the client, search for the account, say the amount, and take the proper amount from his account, et cetera. We're able to save steps as everything is automated.

The actual company has three environments. There's one for development, one for pre-production, and one for production. Every element has two UiPath robots and one Studio. We have in total three studios and six robots, and each one has its own lessons. 

In the first, there was only one robot and one studio. They upgraded the solution from one studio one robot to three studios and six robots and they have found a good benefit in that. They know that it will give them more opportunities and more advantages within the banking environment. They made an investment in this technology to make their work easier so that they could be the best in the market of banking. It's helped them become more efficient.

There is an additional library that I discovered that allows me to work with the previous version of UiPath. There are some libraries that are new on the UiPath Studio, which are also helpful.

In terms of the ease of building automation using UiPath Studio, I must say that I used Automation Anywhere once as well. However, the way the UiPath connects the idea for development makes it so easy to build with the components that we can just drag and drop in. It's the easiest way to develop a solution and is an easier tool to use.

UiPath helps implement end-to-end automation starting with process analysis, then robot building, and finally monitoring of automation.

Being able to implement end-to-end automation is important for me. As much as they make me work, they make the work easier for me. For example, I use it to make the connection between ABBYY Studio, a solution for OCM, and writing scripts inside. I try to launch the script and take the output of the file and try to do a lot of things to make a connection between UiPath Studio and ABBYY Studio. UiPath Studio has given us a strong and new plugin, that we'll put some parameters around and we are done. It makes things easier like that. The features added into the latest update are helping a lot.

UiPath Studio has helped minimize our on-premise footprint in that there's less staff required. Previously, the company had three or four people doing the same thing. Now, only the robot does it. The four people are doing something else now. It's allowed them to focus on other tasks. The robot did not replace them, however. They still work in the same company, however, they are focused on doing different jobs - specifically jobs that can't be automated. They work on jobs that require a human operation, human intervention, and that's it.  The employees are happier too. The current company recently won an award based on employee happiness. In 2021, they were awarded excellence in employee condition. Automation hasn't made them bitter or changed their work ethic.

Robots started doing a lot of tasks that four people take one week to finish, except they can do it in one day. It's saved lots of time. For example, if we have 52 weeks, every week the robots can do a week's task in one day. A human may only be able to do 52 tasks in a year, whereas a robot can overperform by roughly 86% over the course of a year. 

UiPath speeds up and reduces the cost of digital transformation. The robots are extremely helpful, as they can work 24 hours a day, every day. They can do processes faster than people. It makes everything ultimately speed up.

The product has reduced human error. Even the robots make some errors, however, at least we are aware of them. The errors end up being fewer than that of a human counterpart. The issue with human errors is that we can't know if and when an error is made. At least with the robot, if it makes an error, the person is blocked somewhere and therefore we know that the robot missed something or it found a wrong account number, for example. The robot will notify us of an error whereas a human might miss it completely. 

Between version 19 and version 20, the Orchestrator tool interface has changed a lot. It totally changed. The menu changed, the place of the button changed. It took me a week to understand and to make myself used to this new interface. In the end, I found it's a good change and it's helping so much in understanding what the robots are doing in terms of checking logs, extracting some data there to make some analysis, and giving reports to the director.

The scaling could be better. There are so many parameters and options to check and so much to do before the solution is ready to use. Not everyone knows what to do at the outset and it's all a little bit complicated.

I've been using UiPath for one year and a month. The company may have been using it for longer than that.

While the stability is fine, with a license that needs to be paid yearly, UiPath will put out a new version annually. That way, when companies go to renew, they often need to upgrade or pay for a new license. The product does this to keep earning money year after year. 

For me, having the ability to scale automation without having to pay attention to infrastructure is okay, generally, however, even though I find that the company can use the tool to make the process automate well, I don't have so many people working with process automation. There are now just a few people developing in the APA and the licensing is still expensive and clients aren't excited to do anything even if it's a good solution for automating the process.

If you have a lot of money, you can put it all in UiPath and make the robot far bigger. I heard about a company located in Qatar that has 3600 robots. They buy it every year. It's a banking company and every year they pay for it. They are not using all of the robots, however, they've given their developers full reign of the environment.  

In my current company, I'm the only one using it. Many companies actually spend a few years testing it before they officially start using it. However, the company does plan to increase usage and does plan to add three or four more people to the team who would be working with me. I would manage them and provide training as we expand. 

There's a third party that takes responsibility for troubleshooting. They made the environment, and they are in charge of everything. Personally, I go first to the UiPath forum if I need help. I've found a lot of answers there. If I don't find something useful or helpful, I write an email to the third-party provider so that they can take charge of the problem and solve it.

They are good. There are three people who assist me typically. One is from the Middle East, one is French and the other is from India. Their way of communication, their way of giving information, and giving support have been great.

Both companies I have worked for that use this product have never used an automation solution before. 

I have worked with the solution for two enterprises. One was a Canadian company. I implemented the solution for them. I met the organization's boss, and I also put the training together too. I made the environment and I developed the solution and did the full implementation. 

The second, which I am actually working for, is a combination between Europe and Africa on the main. In both companies, the solution is already implemented and I work with it. The solution was started by another department. We don't share or manage the site of escalation or choose which kind of installation. The installation in this case is on-premise. We have constructed on our IAS, local server, and that's it. It's on the server, and we're not using UiPath's cloud.

The initial setup is good. There are no problems. Setting up the robots is also good. For the Orchestrator, sometimes I face some issues surrounding not UiPath, but the OS. For example, installing the Orchestrator on Windows 10, version 19.02, it's not the same process as it would be with Windows 10, version 20.82. Sometimes the visuals of the operating system change and it affects the installation too. This is well documented in the UiPath community. You'll find that many people face problems while working with the Orchestrator.

The deployment sometimes took me two hours. Sometimes I come across an issue and it takes more time. However, often, it can be deployed in 30 to 50 minutes if all goes well.  

With the installation for a Canadian company, I have a very simple installation experience. The environment was already prepped and ready and I just needed to start the installation. 

There is an IT team that does perform the maintenance as required, for example, if there are any updates or upgrades. I don't handle that aspect. I'm only a developer.

We might study potential ROI in the summer of 2022. We're still on the development part and therefore we still can't make reports. We don't have statistics.

There can be costs related to digital transformation. There are two ways this can happen. The first is when the robot is using an internal application, the application made by the company. There often is some modification to the interface of this app. There are some options that become available only for the robots. The second is when the robots use the websites of external companies. Internally, we made some changes to the robots to ensure they work well. In terms of the expense and how much it costs, the information is managed by another department. I don't have information about that.

I can't speak to the exact price, however, recently I heard in a meeting that one license for Studio Path costs 2,825 Euros per year. This price is approximate and may fluctuate.

The license is always per year. They don't show the pricing on the internet. You must contact the support or a seller. 

For the company I currently work with, I was in the meeting that chose the automation solution and they put the UiPath blueprint and Automation Anywhere on the table. The company wanted to choose between them. They found that, in terms of money, performance, and popularity, UiPath was the best. That is why they choose UiPath.

We are not resellers. We are customers and end-users.

For now, I am fine with UiPath Studio and I will likely keep developing automation solutions on this tool.

For the attended robots, we are not using them yet. We are only using unattended robots. First, we must make the financial employees understand how robots work. They need understanding or training as a first step before we can use attended robots in development. We are going to use attended robots in the future, however, for now, we're focused on unattended robots.

We don't yet use AI functionality. We're going to start using artificial intelligence and also the machine learning solution of UiPath via AI sensors. We'll use it to measure credit and to gauge the likelihood of clients paying, however, for now, we are not yet using AI features.  

We are also not using UiPath apps.

UiPath Studio has reduced the costs of our automation operations, although I don't have an exact statistic that reflects this.

Sometimes, when you come to a company and you tell them that you will make a robot to do their job, the first thing they will start thinking is "we're going to lose our job. They're going to fire us." With that mentality, they often aren't cooperative. 

For example, in a Canadian company I worked for when I was working on the process, the parts of the activity for Excel automation, I kept notifying them that they should keep using the same name of the file so the robots can read the file. However, I would get files in different names with letters off or symbols in them as if the staff was trying to get the project canceled by trying to show the robot wouldn't work. However, over time, as they came to understand no one would lose their position, they became cooperative. They weren't happy at first, however, they came to embrace the project.

UiPath has a huge marketing strategy, and they have been the first in the world with a lot of this technology. If a company wants to integrate automation into its processes, it will likely start looking at UiPath first.

If a company is considering UiPath, they should know exactly which process should be automated. When you know what kind of processes will be automated, they will understand better if they need attended robots or unattended robots, and then can proceed with a purchase. What one recent company did is they went and bought one studio and one robot. Then, later, after understanding which process was going to be automated, they figured out that they needed three studios and six robots. It's better to know which process to develop to make it automated, then later go to buy solutions for it.

We will still always need human workers. Of course, there are some tasks that can be automated 100%. However, in the end, and specifically in the banking domain, we always need humans to understand some things that make the work easier. if we combine automation, things like robots, and human intervention, then we can get great results.

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

In our organization, we are using UiPath as a service model. It is an on-premise model where UiPath is deployed on-premise. We are not using it on cloud services. 

We have a center of excellence that has been set up to communicate with UiPath for all the licenses, for all the tools, et cetera. Individual teams will connect and will communicate with the development team to get those licenses. For the team structure, we have a COE manager, and a COE is again communicating all the relevant information to the teams.

First of all, you would have to go and submit an idea to the COE team. The COE team will review and see this is the correct candidate for our solution and we can leverage it as automation. They provide us with the required licenses and the cycle continues.

The use-cases for the UiPath are limited. For example, if you are coming from a banking background, there would be use-cases it comes from the data solutions. If you are coming from an insurance background, would have use-cases where you would have benefits that are being reconciled. Healthcare might be dealing with patient data, et cetera.

If I talk about the support teams, in general, the use-case for the UiPath is as a ticketing system, where you have a lot of data to add to the queue to remove the need to add items manually.  

UiPath has the ability to implement with multiple systems. You can extract the data from any other application, click the data to enter the specifications, and start the automation cycle. That way, you have a technology that helps you to build a fully automated enterprise.

Our use case depends on the client and their needs. It's specific to their industry. We basically use the product to build automation for them.

We have seen the benefits both in terms of cost-saving, and time-saving. If you are doing automation which a human or an entire team is doing, let's say five hours a day, and there are seven to eight people doing the same amount of stuff, then you can automate that. 

When it comes to automating your process where the company is paying for software if you can use it to make robots that take energy away from repetitive tasks, you end up saving a lot of man-hours - which helps pay for the software.

Savings are measured both in terms of active saving or cost-saving. Then again it entirely depends on the kind of automation you're organizing. 

The most valuable feature of UiPath the process mining. The half capture was a tool that was provided by UiPath in the earliest reviews which simply allowed you to record the operations

It's great for automating tasks specific to business cases. It makes it very easy to do so as well.

The solution offers pretty good analysis capabilities.

The solution ensures there is proper documentation throughout the process.

The product creates a kind of skeleton for developers to help them work faster. 

UiPath is a low-cost platform.

If you are someone who is coming from a business background, and you don't have much coding experience, and you don't want to go through the coding world, UiPath, has UiPath StudioX. With the help of UiPath StudioX you can automate your items to read emails, download specific things, and do other small automation tasks that do not require advanced coding.  

If you are a developer who is more into coding and wants to do more coding, you have Studio and Studio Tool. Based on your level of expertise, UiPath has various levels of product: StudioX, Student, and Studio Pro, for example. It is always good if you have a programming background as sometimes you might need to write a small piece of code, however, it is a comparatively very easy task compared to the other traditional programming languages where you have to write a lot of code to do simple automation.

With the application of AI in recent releases, automation such as document reading can happen faster.

The UiPath app feature has increased the number of automation you can create while reducing the time it takes to create them. Recently, we had a UiPath hackathon which was contacted by UiPath for automation. We went to an NGO, and, for that NGO, we created a solution with the help of UiPath apps. For example, we used to create the invoices that would take seven to eight minutes to manually create. However, with the help of UiPath apps, we were able to do the same path in less than one minute. We have seen a drastic change.

The solution reduces human error significantly. When you are doing a process for more than five hours, you might deal with human error. However, robots don't make mistakes and can run 24/7 without issue.

You do need some coding experience.

AI is not available on older versions. I don't know if it is available in the latest versions of this review. Most enterprises, I'm working with still are at the previous version of the UiPath studio.

UiPath needs to enable more of the features which are available. For example, today, if I have to implement an automation path for the mainframe application, I cannot do the mainframe application without the client. I cannot just do a trial. If UiPath could create dummy applications for the developers who want to try new features, that would be helpful. 

The should be more out-of-the-box models if UiPath keeps adding on. Recently they have added a model in their AI section. However, it would be useful to have out-of-the-box models direct themselves towards plugins. 

You need to continually update the solution as, if you don't, after a few months you won't recognize the product due to all of the new releases. It will be like using a completely new device.

I've been using the solution for five years. It has been a while.

Stability-wise, UiPath can handle the different varieties of stability on the applications you are automating. 

For example, if you choose to automate applications that are expected to change in the next few months, then UiPath cannot help you. That takes an entirely different form of planning. However, the more stable the process, the less likely any part of the process will change, the better UiPath can assist. 

The solution is scalable. If you have to add new functionality to the robots, you will find that is definitely scalable. Let's say you have automated a process and you are getting 1000 tickets only, and then you suddenly get an influx of 10,000 tickets. You don't have to go and run and change your code or anything. Scalability-wise it is just with the click of a mouse that you can handle the change. And, just as easily, you can decrease usage if there are only a small amount of tickets. While developers and coding will be necessary to make it happen, I would say the solution scales extremely well.

I have not contacted UiPath via the contact center. The firm I'm working for has a center of excellence. We do not, as individual developers, directly communicate to UiPath. There is a team that sits in the company that communicates with UiPath, as we're an enterprise. We don't have direct access to the UiPath team.

That said, I do interact with them on the community edition, which I also use, and I find that if I raise a ticket, they listen to my feedback and adjust accordingly. They're excellent.

I have not used any other solution.

The initial setup is straightforward. From an enterprise point of view, from the client's point of view, there are certain restrictions that the company might have in place that could affect the way it's set up. 

The company needs to have a checklist to ensure it's set up optimally.

That said, there are no drivers, no scripts, nothing. Everybody can do it. You just have to click on the approve button, select it, and the job is done, that's it.

We do our own implementation strategy, however, I am not directly involved in what exactly has to be implemented. There are separate teams for that.

While I can't speak to how much users pay for enterprise-level editions, I can say that their community version is quite good and free to use. I've used the community license for the last five years and it's been great.

I do mostly 90% unattended automation. I have created only one attended automation for a client and that was a specifically requested requirement. That was a bit difficult to automate. 

One piece of advice to everybody who is working in UiPath would be to practice and keep UiPath updated as the technology is growing and it is getting updated frequently. If you do not keep yourself updated for three or four months, you'll be dealing with a completely different tool. Keeping it updated allows for the gradual changes to come in in a way that a user can handle, as opposed to having to re-learn or re-discover the product if you have let updates lapse for months.

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