UiPath Reviews

We are an auditing firm who has a certain level of tasks that are open for automating. These are complete steps, which can be performed by anyone, standardized, and do not involve any human intelligence. These are just basic human tasks. It is a long process, where in-between there are certain validation and verification steps as well as certain steps that involve a lot of documentation to go through. The organization is targeting all these tasks, which are completely static and can be automated, so they can get rid of them. Then, employees can work on something more useful as well as more productivity-oriented tasks.

Currently, I am dealing with our internal COE, providing RPA solutions to internal and external clients. UiPath is a driving force in our COE.

It is on-prem. There are a couple of discussions going around upgrading UiPath because there has been so much advancement with the solution.

Document Understanding was a game-changer. One of our clients has manual billing that needs to be processed. With the help of Document Understanding and UiPath Action Center, we created an excellent workflow for our client. It also gives us better accuracy. Now, there are hardly any exceptions in the client's billing documents that are being processed.

In my previous role, I presented some clients the end-to-end installation design of UiPath, e.g., building a PDD using Task Capture, going to UiPath Studio to build the actual solution, and then later going to post-production Insights. 

UiPath has helped to minimize our on-prem footprint. Most organizations prefer on-prem because it reduces the risk of compliance issues.

Attended robots have been very beneficial for our users. UiPath saves one robot for every user. We have a couple of clients who are using attended automation for their day-to-day tasks.

From an organizational point of view, the most used feature is Orchestrator because that is how we manage more than 100 users. When there are more than 100 users, it is important, and probably better, to have some place to manage them. Orchestrator is doing that for us very well. 

The most exciting new feature is UiPath Apps. I have explored it in-depth to get a better understanding. I think this product will be a game-changer for my organization as well as for my clients. It will revolutionize the way that we are providing licensing and proper access to a user. It also revolutionizes the way people are using it. Everything will be on the cloud, which I think is the most interesting feature of UiPath Apps.

UiPath Apps will definitely help to reduce the workload of our IT department by enabling end users to create apps. If you are creating an app and sharing it over the cloud, that removes the dependency of having UiPath installed with the correct version as well as Internet connectivity. Or, you might have a global server in the background that is not functioning very well. There are multiple issues related to connectivity of the UiPath robot when deploying it on a user's machine. 

If you are giving access to a group of users and adding Azure container or any other container provided by UiPath, then this reduces 10 to 15 hours of work from the IT or support guys who are manually doing all these things by themselves. Not every user must have the new step of getting the UiPath license and software installed, it is really static. You are eliminating that task completely by having UiPath Apps on the cloud. This is definitely convenient for users to use.

We are not using UiPath Apps in my current organization. About two to three months ago, I created UiPath when I was at TCS. It was there that we demonstrated the power of UiPath Apps versus normal, conventional methods. It reduced our work through scalability. It helped us to easily scale and was more convenient, because giving new or temporary access can be a pain. 

It is very easy to share UiPath Apps. When you want to start or remove it, you can do it with a simple click within the cloud. It is not that complicated. Also, the usage is better in UiPath Apps compared to the conventional UiPath robot. In UiPath Assistant, you can access the portal and simply run it over there. Therefore, you will not have a problem with the background functioning of the UiPath robot or even connectivity issues. Scalability and ease of use are favorable for users when they are using UiPath Apps.

Recently, I have been exploring Automation Hub. Its idea to pipeline a feature will be very useful for our guys managing RPA products on a large scale. 

When it comes to debugging, there is some improvement needed for UiPath compared to other RPA tools. There are features to edit the workflow or content of the automation file while we are debugging. For example, we have 10,000 lines of code that we have integrated by 10 different users. So, there is one integrated code and you are debugging it. After some time, you might find a line which is not an error. You may have forgotten to remove it or change the value to your desired criteria. It is really a pain to stop the entire debug session and just edit it, then start again at zero. It will do the same steps again just to reach that level or step where you were actually stuck previously. Whereas, in different automation tools, whether you are on the findings step or in-between a debug session, you can actually edit that information. This is good because sometimes the developer also forgets to add or remove certain values in-between a long code. I think this should be improved in UiPath. This should already be in consideration because I have been in touch with UiPath a couple of times because of this.

My current company is currently looking at the end-to-end solution. However, Insights and Task Capture are major concerns. Task Capture will give you a skeleton of the PDD, then you have to edit it. The skeleton is only there for simple automation, and we have complex scenarios. It is so complicated that the PDD generation using Task Capture will not give you even 20% of the output. While Task Capture is something promising, people are looking at it with greater expectations than it provides. People are not using Task Capture or Insight because of their limitations. These features could use improvements and enhancements.

I have been using UiPath for three years. I recently switched companies. I worked with Capgemini and TCS prior to this company, where I was in their COEs and providing solutions to clients. This is the first time that I have been on a project for PwC. Since the start of 2018, I have worked mainly in COEs and have interacted with around 30 clients up until now.

PwC, as a firm, has been using this technology for four to five years.

I have been using UiPath on a different powerful system that has high-end RAM. Sometimes, it crashes due to the use of multiple components at once. For example, when I was using Druid with data service and another UiPath product. Developing was quite easy. However, when debugging, sometimes it would freeze. I don't know whether it was because of my system and its compatibility, my system's configuration, or the fact that we were using so many high-end tools and products at once. 

The robustness of the tool, when it comes to using high-end products, is something that I am currently exploring. This is something that is currently a bit of concern for other developers as well. I have been interacting with a lot of developers around the globe. As a part of that, I tend to share my experiences. They have shared that it will sometimes freeze, even with simple automation. Because we are using new features or products all at once, it freezes. I think this should not be the case. If you are using long, heavy code, and it gets frozen at one point, I can understand that. However, 10 simple lines of code, while using three or four products at once, is getting frozen. That should be taken care of or improved.

To troubleshoot the system crashing, we contacted UiPath. They were kind enough to reply and have a discussion. They are working on this and trying to make it more convenient so future releases will solve this problem.

As a part of a COE, we get clients who expect us to present the entire proof of concept as well as a PPT or presentation. For example, why they need to go with UiPath, what are the advantages/disadvantages, if any, and why we should not go with another tool or solution as a whole, not just RPA. The main point for us when presenting UiPath is the ease of usability and scalability. We don't need major infrastructure changes, just two or three URLs to be widely fitted. Then, they need to decide if they want unattended or attended robots. The scalability is the major driving force which excites our clients and us, because there isn't a need to have media-heavy software or heavy processes changes.

Clients don't want every user in their organization who joins to have a long process to get through the start up. Automation Cloud is something they were very much interested in exploring because of the scalability. They find it very easy to use and scale, because not all the clients have a certain set of users using robots. 

I have seen user usage explode from zero to a bigger audience of 22 users.

UiPath is used extensively in my current organization on a large scale. There is also a plan to scale it to more users.

PwC has their internal teams providing a "help center" sort of infrastructure to them. If there was a need for any help, or some basic doubt, it is solved internally. PwC's internal help center exists already. However, for major issues, we reach out to UiPath, as a customer, so that we can receive a response and clarity on issues.

The technical support is really great. I have been in touch with all sorts of UiPath support because I was in the COE and our clients were completely global until my latest assignment. I think UiPath India, France, Belgium, and Canada are timely. They provide a very precise support experience. They were kind enough to let us know the actual reason, because just saying that it is a bug is not something that we can comfortably accept or digest. Also, they have been kind enough to follow back up on updates and bugs that we have reported.

As a whole, I have reported more than 25 bugs across all their products. They were kind enough to reach out to the same forum where we raised the ticket. They were kind enough to reply that these are the updates that they will roll out in the next version. It is good to have this interaction as well as a heads-up regarding your bug reports. I think the technical support is on the mark and doing their job really well.

The learning tools and support are really great. They have the most engaging forum across the globe, compared to other RPA tools. The learning and engagement are really up to the mark. That also brings confidence to our clients and us. We are a part of their global community forum, which is a benefit for us. 

Their marketplace has grown tenfold in the last year. It is because of the developer's involvement as well as involvement from people in the community. UiPath is creating their own statements and usable components, which adds value to our presentation. The tool is growing, and developers and community members are growing with them. 

My previous companies migrated from other RPA solutions, like Automation Anywhere, Blue Prism, and NICE Robotic Automation, to UiPath because of the value of its features and the quality of the overall solution. I migrated my clients from those companies so they could have a better ROI and reduce the cost of maintenance. We also migrated from scheduling tools, like AutoSys, to provide better accuracy and ease of use.

My current company was not previously using an RPA solution.

The initial setup and implementation are standard, simple, and user-friendly. UiPath just requires basic adjustment, then it is plug and play. It is very easy for everyone to understand, e.g., non-technical clients can understand what has been changed.

If the deployment is done properly, you will see better data accuracy with UiPath than manual entry. If the deployment is done by someone without much experience, it will affect the quality of the solution due to bad coding. You can't just leave it to the tool.

Using Automation Cloud makes it easier to deploy.

It takes almost two weeks for us to implement from scratch because we must understand the client's infrastructure, create a solution design, and then present it to them.

We present our clients with a PoC, including a document that justifies the work and costs. We also give them a standard robot that we created for demo purposes. This way, they can visualize how it will be implemented and mapped in their organization.

For deployment, one or two people are sufficient: one from an infrastructure background and another from a technical background. Sometimes, it is complex or hard to understand the client's needs when it comes to the deployment of Azure, Nvidia, or AWS servers on their VPN connection.

The amount of staff needed for maintenance depends on the size of the solution, e.g., the bigger solutions will need more people. However, the maintenance and support activities can also be automated and that reduces the need for support and maintenance. Three or four support team members are enough with the help of a robot.

The last ROI calculation that we did for a client showed that they saved 25% of their time by automating a manual task with an unattended robot for a single machine.

Overall, the cost remains the same to the client and us, when using Automation Cloud, because of the amount of money spent on the cloud migration and cloud usage.

At my previous company, in the best scenario, we removed almost 200 hours per month of client usage, making it automated with almost zero errors. So, about 32 employees were freed up from their work per month, and now there are only two. This has enabled employees to focus on higher-value work that involves human-base interaction. This saved the client money and provided a recruitment benefit.

UiPath has been useful for improving employee satisfaction. Employees are now spending time on more value-add work instead of something static, whether it is boring or hectic, that they have been working on for ages. This gives employees a sense of advancement.

I would rate the pricing as seven out of 10, where 10 is the most expensive. The pricing increased with the latest release. It used to be cheap. Now, it is expensive. However, it does come with supported features, which almost justify its cost.

Building automations is very easy. I have used multiple RPA tools. Developing automation with UiPath is very convenient compared to other tools. 

Development is very easy. I have been exploring certain markets based on the marketplace component and its native integrations with ServicesNow for the chatbot. I think development is where UiPath stands out as a winner compared to other tools because starting to automate is very easy.

Compared to other RPA tools, UiPath is leading with new feature additions every quarter. Obviously, all the new features will not be incorporated into the solution or be helpful for the client. We see the organization putting in efforts to grow at a rapid pace, including ML, scaling, and everything on the cloud, like data servers. UiPath gives us the confidence to present a tool that can be relied on because it is constantly growing. It constantly has certain new features added which can be beneficial.

With UiPath, not everyone needs to understand the code, which is great. This makes it superior over other tools because it is easy to understand. This contributes to profits because clients prefer UiPath over something else because they have more confidence using it.

Blue Prism has the ability to edit in the middle of a debug. As far as I have explored, Blue Prism is leading on the debugging front and stands out against UiPath. Debugging in Blue Prism gives users a lot of usability to edit the workflow. This makes it easier for developers to run things once and get things done. Otherwise, debugging multiple times can sometimes be a pain.

People migrate to NICE Robotic Automation because they were having difficulty maintaining their software with a limited number of staff. 

It is easier to become more proficient with UiPath than other RPA tools, especially Blue Prism. Training can be done at almost no cost.

I would suggest automating a policy that is not a requirement and follows a process. As an RPA user, it is your responsibility to get things done in an efficient way. If a user is doing A, B, C, D, it might not be required that the robot do the same thing. There might be a shorthand that can take you from A to D directly using the robot. For example, it can go directly to a page and not have to click 10 things like a human.

If you use it properly and consciously, it can increase accuracy and reduce error. If you don't, then it will be the other way around.

As features are concerned, it is reasonably priced compared to any other heavyweight tools in the market.

It is beneficial that there is a SaaS option because this offers a diversified cloud environment. If we expand and explore more cloud options, then having a SaaS solution for UiPath will be beneficial for us. Right now, SaaS comes with a certain amount of compliance issues for my company. 

UiPath AI Center is very useful. I think it is a game-changer when it comes to better usage. However, I haven't had much of a chance to explore it on an enterprise level. Not many clients are using it because of the exposure risk. Once a lot of developers start exploring and developing on it, then more companies will have the confidence to say, "Yes, we can push to that," which will increase the usage of UiPath AI Center.

Everything on the UIPath Cloud is a template. It is just a starting point. You have to dig into it and do more exploration to make it better.

Using Automation Cloud would be very beneficial for us, as a COE, because we are getting rid of the mundane tasks of infrastructure, maintenance, and upgrades, which we do not think are our primary job.

Biggest lesson learnt: UiPath has the fastest growing community with the quickest learning tools. It is easy to automate. It requires basic understanding and effort to get started. 

I would rate UiPath as 9.5 out of 10. I have concerns about the debugging capability, where if I need to edit something while debugging, I can't do it right away without stopping the process.

I have hundreds of use cases for UiPath. Mainly, it's used for AP and AR automation, outboarding, HR, and for vendors and customers. 

It's helped us reduce manual work for our employees and customers.

Having expertise in IPaaS has allowed us to create a lot of automation for our clients that they normally couldn't automate. It's a profitable solution in that sense. Also, it automates many steps that normally would require a lot of FTEs to do that work. You can ensure it's being done on time without any human errors.

The UI automation is excellent. Being able to automate clicks on desktop applications and browsers is very helpful. A lot of the other tools are very good at automating online system processes and similar things. However, when it comes to desktop UI automation, they are by far the leader.

They're just starting to add a lot of AI functionality, so there's definitely room for improvements in leveraging the latest AI technologies - like GPT, et cetera.

I've used the solution for about eight years. 

The solution is very stable. I'd rate its reliability nine out of ten.

It's extremely scalable. I'd rate scalability ten out of ten. 

Most of our technical responses are related to third-party websites changing their designs. You have to deal with those changes. The modern selectors are smarter and can adapt to change. However, if the developer changes a lot of things in the background. 

UiPath support is quite good. Sometimes they take a bit to get back to us, however, most of the time, they are pretty responsive. 

They do have a higher tier of service that costs more, and they are quite excellent. 

Positive

I use both UiPath and Power Automate. We used to use a tool called Win Automation. We switched from then due to the fact that they were prone to failure and did not have enough tools to meet expectations. They have since been acquired by Microsoft, and Microsoft Power Automate is based on that.

I'd rate the initial setup eight out of ten. It's pretty easy to implement. 

We use Azure Virtual Machines to deploy the robots and usually use a lot of the Azure services in conjunction with the robots. The cloud is on UiPath's automation cloud. That's where we have our servers - to manage the robust deployed data on multiple virtual machines.

In terms of maintenance, there are always releases and updates, and then you can usually design your own robots to watch over the other robots, which is really interesting. You have the flexibility to make your own monitoring; if it sees something wrong, you can enter a ticket and then dispatch it to the support team to respond to it. 

My whole developer team is involved in maintenance; however, I have specific support team members. There's 28 developers and seven support team members in that group.

We witnessed an ROI fairly quickly. For the cost of one developer license, you can produce a lot of automation. The robot license is a 24/7 one-year license. If you can run bots 24 hours nonstop on it when you can run many different processes, each process can save hours, hundreds of hours of time for employees. There's also a lot of savings from your customer side on being able to service things quicker as well. That you can't fully quantify; however, you find you can offer better customer service in terms of speed of transaction, et cetera. Even if you spend $10,000 to $15,000 on a robot license, you quickly recover your costs. 

The pricing is very competitive. There are some parts of the solution that are considered consumable, and as you consume more, you increase the cost. However, that's similar to other products out there. There might be extra costs for AI units, robot units, and data services. That said, what they give you out of the box for every license is usually sufficient for most enterprises.

I'm a customer, reseller, and partner.

I'd rate UiPath ten out of ten. 

I would advise new users that the biggest part is to always sync in reusable components. That will drive your ROI much quicker. If you can reuse pieces or design them in a way that they're reusable, then you can use them across multiple processes instead of redoing the work over and over. Thinking modular from the beginning is going to go a long way.

My primary use case with UiPath is to automate workflows for processes in web-based applications, such as email and Excel automation. We also use it as a task or workflow management tool, capable of assigning tasks, checking on the status of tasks, and more.

Another thing that I have been doing with UiPath is replacing repetitive tasks performed within the organization. Automating such tasks makes the related process smoother and faster. 

We are using the UiPath automation cloud offering, which is a SaaS solution. One advantage to this type of environment is that we can get updates instantly. If it were an on-premises or hybrid model then the setup and maintenance take time, but this isn't the case with a SaaS model. This instant setup is what we needed because it made for a smooth transition from manual processes to automation. 

With respect to building automations, UiPath is a pretty straightforward platform. The major reason that we choose to implement UiPath is the interface that it provides, which boosts the usefulness of the entire platform. If we need assistance then there are many knowledge base documents available. There is also in-app help, which makes it very easy to understand and start using it.

I was able to learn how to use it within a week, which shows how easy it is. For example, it does not require a lot of coding. It's more of a drag-and-drop interface, making it easier to develop programs and automate processes.

UiPath enables us to implement end-to-end automation, and it has completely replaced the manual processes that we were using. This includes analyzing the process and implementing automation to collect the data. Data fetching is done using the robots that we create.

Since implementing UiPath, we have experienced better retention of our users. This is because we have been able to make our process much smoother, as well as quicker. Consequently, we have been able to deliver at a much faster pace. This has enhanced the customer experience and in turn, has improved customer satisfaction. Overall, we have seen an increase of about 30% in terms of user retention. This has translated to increasing revenue.

With respect to automating our processes, automation has reduced our manual efforts by more than 70%. This means that we are able to concentrate more on other aspects of our business. The business is growing because we are able to do things like work on our website, customer engagement, and customer relations.

UiPath has taken care of most of the backend work for us, which is a good bonus. It has reduced our investment in manpower by about 50% and decreased our overall output time by more than 70%.

Automation has definitely reduced the rate of human error when compared to our previous, manual processes. At this point, there is minimal to zero human error. I estimate that approximately one hundred percent of human error has been eliminated.

Implementing this product definitely helps speed the process of digital transformation, and reduces its cost as well. One of the goals of our organization is to completely digitize. We want to optimize everything so that employees can focus more on the customer relationship aspect, building more value for our brand. UiPath has definitely helped in improving the overall process.

Our digital transformation did not require any external support for third-party application software. It's an in-built process and we did not need anything extra.

The specific feature I like is folder organization, and it is in the Orchestrator tenant. This is very useful because it keeps all of my folders and data in a centralized tenant.

The menu options are easily accessible in the Orchestrator tenant, which is something that I like very much.

The UiPath Academy was pretty helpful for us in the initial stages. We were able to learn more about the software and what is there. They also provide courses and certifications, which assist with learning and getting employees up to speed.

It took only a week for me to completely get a handle on the software. Taking the initial training and certification courses is a hassle-free process. It is not difficult to induct somebody and have them start using the product.

The courses that they offer provide hands-on experience, and I think that it's a good initiative that they are taking on by doing so. It helps to ease the learning curve and allowed us to learn more about the world of automation.

UiPath has a user community that is very knowledgeable and friendly. Our peers in the UiPath community are able to dumb down responses to a beginner's level of experience, regardless of what queries we have put forth. Whatever we have wanted to do with RPA, they have been able to help. We now have a good level of comfort in terms of interacting with our peers in the community.

We have experience with other communities and have found that the discussions are generally at a higher level, which may be too difficult for a new person that is just starting out with the product.

Generally speaking, I like the features that I am using and I could not really say where improvement is needed in that respect.

The product could be made a little less glitchy. Specifically, when too many users are working at the same time, it hangs a little bit here and there.

In a future release, I would like to see drag-and-drop functionality in the robot creation process within Orchestrator. As of now, it is not available there. It would be helpful because from there, it is easy to create a process flow. Instead of switching between multiple menus and multiple tabs, we can do it from the Orchestrator or the main menu.

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

I would rate the stability an eight out of ten. Sometimes, when the load is high or there are many users working at the same time, or when I'm working on different parts at the same time, it lags a little bit. There is a slight drop in performance.

Otherwise, it's very stable and secure software.

Using the automation cloud offering has meant that scaling up automations has been very smooth for us. We started out with between 40 and 50 users working on this particular tool, and now it's between 150 and 170 users.

There are two levels of roles; admin roles and user roles. The admin role is able to assign and approve tasks, using the task management module. Regular users are able to perform all of the other functions.

It is definitely a scalable solution, being cloud-based and SaaS. It is also very customizable. Customizability is the unique selling point (USP) for this particular product, given the number of customizations that are available and the number of features that can be added.

The technical support staff is brilliant. They are very knowledgeable and very quick when it comes to addressing our queries. They don't ask us to wait for long when we have a problem, and we normally have a resolution within hours.

There is also a community forum that helps us to deal with problems ourselves, without the dependence on the technical support team.

I would rate the technical support a ten out of ten.

Positive

We did not use another RPA solution prior to UiPath. Before this, we were doing everything manually.

I was not involved in the initial setup and deployment.

As we opted to implement the cloud-based model, the maintenance on our part is minimal. We just have to update the software from time to time. The amount of maintenance that we perform is not only easy but saves a lot of time for our IT team.

The team of people for maintenance consists of six or seven junior IT staff. They perform the updates and nothing more.

Using the automation cloud offering has helped to decrease our time to value. An example of where we saw the benefits of this solution was with an Excel automation that we created. This process involves an Excel worksheet that contains between 20,000 and 30,000 records. We had to manually search for particular records, and the process to approximately a week to complete. Now, with UiPath, the same process is completed within a couple of minutes. 

Once we signed up with UiPath, we instantly saw growth in our entire business. It was a win-win situation. 

The additional time has enabled our employees to focus on higher-value work, such as R&D, customer engagement, and improving our brand. It also has an effect on employees' satisfaction, specifically, mine.

A lot of time spent doing repetitive and redundant work is something that was irritating me a lot. Now that the automation is in place, I just have to set up the workflow. It has definitely increased my overall morale and satisfaction. 

One of the downsides to UiPath is the cost of the enterprise version. It is a little bit on the higher side.

UiPath's cloud offering is a centralized, all-in-one platform. It saves money because you don't have to invest as much in other software, and it's cheaper than some solutions because you don't have to maintain the platform or the database. However, because it's not cheap, the overall cost reduction is not drastic at first. Taking a holistic view, it does because overall, it will reduce costs.

There is also a Community Edition that can be used free of charge. This is an option for users that find the price to be high. One main differentiating factor with the Community Edition is the number of updates. There are fewer in the Community Edition.

Also, the support offered for the Community Edition is not as quick. People will not have a great user experience. However, it is important to remember that in terms of cost, the Enterprise Edition is a little bit pricey for small and medium-scale enterprises. 

About a month ago, we started using the AI functionality of the software to design robots and processes. At this point, we are looking to use AI for our internal applications.

One example is that we are working on security-related automation that triggers an alert when somebody inserts or removes an external hard disk from a system. Taking advantage of the AI capabilities has helped us to maintain a much safer work environment, in terms of data security.

The AI functionality has definitely enabled us to automate more processes. A lot of manual work and redundant work has been reduced. Also, the number of errors that we had occurring during our manual processes has been greatly reduced.

This solution has definitely helped to free up employee time. Tasks that used to take approximately a week, now take just 30 or 40 minutes. This is a lot of time saved, which allows us to concentrate more on other aspects of the business. For example, improved customer engagement has resulted in gathering more leads. Also, we have more time for R&D.

I estimate that we are saving approximately five hours per day, so 20 hours per week, per employee. In addition to the areas that we have more time to concentrate on, it has helped improve the value of our brand overall.

My advice for anybody who is looking into implementing this product is that it's a must. This is the go-to software that I would recommend for anybody looking to automate their business in a smooth and efficient manner.

Cost, of course, is something that has to be considered but if they can afford this solution then they should implement it. It has a wide variety of features and functionalities, which are market fit and market ready. 

I would rate this solution a nine out of ten.

I have worked with most of the UiPath use cases. From 2017 to now, I have delivered more than 400 bots. I have worked in healthcare, energy, shipping, and other industries.

When it comes to manual processes, especially IDP and the combination of IDP and automation, the journey has been a bit difficult and challenging, but it has been worth it. Most other automation is straightforward. We take input from multiple platforms, put it into another platform, and so on. But with IDP, we have to read the document, validate the data, and then integrate it with the automation tool in UiPath.

I started integrating IDP and automation before UiPath Document Understanding and the Action Center were available. What I used to do was automate the process and then create a layout in ABBYY. I would then integrate the ABBYY layout into UiPath, evaluate the data, and then automate the rest. I did this in 2018 and 2019.

Now that we have our own Document Understanding and Action Center platform, I don't have to rely on any third-party tools for IDP. The combination of automation and IDP within a single platform has made a big impact on many businesses. It has helped them to reduce their annual efforts in data entry, reading documents, and correcting small errors in data extraction and copy-pasting.

I have seen the best results when IDP is combined with automation. It has reduced manual efforts by at least 80 percent. Automation is always helpful, but the combination of IDP and automation is even more effective.

In one example, we were able to deploy more than 700 bots for a single organization in the manufacturing industry. They had around 25 servers just to run the bots, but now they are running multiple bots on a single server. They are saving millions of dollars per month by using UiPath.

Overall, I think the combination of IDP and automation is a huge game-changer for businesses. It is helping them to save time, money, and resources.

Most of the elements we have right now as activities with this do not require us to work with the norm of 100 lines of code or anything like that. It is just drag and drop, so anyone can use UiPath from scratch and be approved within a couple of months. The platform itself is very easy to learn and use. I don't think there were any challenges at any point with respect to this.

UiPath enables us to implement end-to-end automation. We have many back-end processes that run without any manual intervention. We simply schedule the bots, and they run flawlessly. We also have a bot that generates reports for us. As a result, we have had end-to-end automation in place for almost a year now. We are very pleased with how it is working, and we believe it is a valuable feature.

The UiPath User Community is great. I am proud to be a part of the community, where I have earned the Community Moderator badge, the Bylaw badge, and the MM VPA badge. I have witnessed the incredible journey of the community, from a group of people who didn't know each other to a community that meets in person at least once a month. The quality of the answers in the forum is amazing. I have seen a few companies create internal competitions to see who can answer the most questions in the forums and receive prizes. These small gestures from the community make a big impact. I would say that the community has played a major role in the growth and deployment of UiPath. UiPath has never failed to surprise and value the community members. The company has never disappointed us, and it continues to support our efforts.

When we join the UiPath Community and become an MVP, we gain direct access to the company's product engineers. We can provide our feedback and reviews for every product and release, and we also have beta access to all products when we are eligible as an MVP. Every review, opinion, and idea that we provide to the product managers is taken seriously and reviewed. If it is valid, the product managers implement it. I think this is the best thing about being a part of the UiPath team, both as a team member and as an individual. I really like the core UiPath team very much.

We have UiPath both on-premises and in the cloud. I think we were able to make significant savings when we upgraded to the cloud, especially in terms of infrastructure costs, deployment, and upgrades. The dynamic nature of cloud computing has helped us to reduce costs and save time.

We often use the UiPath Academy courses. I believe that 80 to 90 percent of my team uses the Academy, and it is the main platform where we have learned to use UiPath. I recommend that everyone take the Academy courses. For anyone who wants to learn UiPath, the Academy is the best place because it has everything we need to know.

UiPath accelerates our digital transformation and reduces costs. We did not need to upgrade to expensive or complex applications to accelerate our digital transformation.

UiPath has reduced up to 70 percent of the human errors.

UiPath has helped free up staff time. We have citizen developers from UiPath who are using UiPath Studio X to save almost 70 percent of their daily time on email automation. Especially when it comes to process mining, they don't have to do the same update task; the processing is ready, and everything is ready to be given to the developers. Even the developers are saving time when using the RA framework for SAP or ERP applications, such as by creating and using libraries of common screens, selectors, and steps. This saves them at least 50 percent of their time, so they can focus more on research and development and new features.

Document Understanding and Action Center have added significant value to UiPath, especially for the IDP process.

There are a few businesses that are failing to generate their ROI. I think that's where UiPath needs to educate businesses so that they can choose the right product for them, whether that's the entire automation solution suite or just the individual products that they need. I think that educating businesses about this will help them a lot and make it easier for them to succeed.

When integrating with third-party tools, UiPath gives us the freedom to write our own code and integrate it. However, if we could get a repository of at least a few of the layouts for the GUI or AI Center, where we would only need to make minor changes, that would be helpful. For example, the files have a template that extracts all the information. I would just like to change a few things, but I don't want all of that. I know we can just hide it, but that won't help because processing the whole document extraction will still take the same amount of time. If we could get those codes in any of the repositories where we could make small changes to the existing code and then import them into our processes, that would be helpful. We do have all the code. We do have all the activities, but none of them are accessible or modifiable. We have to use them as is, or we have to create our own. Those are the only two options we have. If we could get the codes in the report that we want, and then we could make the changes and use them in our own code, I think that would help us more.

I have been using UiPath for seven years. I started my journey in December 2016 and we started delivering projects to clients in 2017. I have been impressed with the evaluation of the UiPath products from 2017 to 2023. The features that we have been receiving in recent years are very good.

When I started as an automation engineer in 2017, people at companies like Sony and other networks and large companies were scared to share their processes and credentials due to security concerns. I have seen this challenge firsthand. However, now, companies of all sizes, including national banks, are looking at automation.

I have seen an incredible journey from 2017 to 2023. I am happy to have been a part of it.

UiPath is stable.

UiPath is scalable. We are able to upgrade anything.

Whenever we have a challenge or similar issue, in rare cases, such as when there are multiple questions assigned to a support ticket, there may be a slight delay in technical support responding.

Positive

The initial deployment is straightforward.

The deployment time depends on the complexity of the project, ranging from six weeks to four months. For a very simple UiPath automation project with multiple applications, we can complete the development, UAT, and deployment within six weeks. However, if the project involves IDP, validation, and other complex features, it may take three to four months to complete.

The number of people required for deployment depends on the complexity. I always suggest having proper planning. I would not let any of the junior developers deploy to production at any time. I would always have two different teams. This is my preference. Instead of having junior developers deploy to production with only one person, even if they are capable of doing it, I would suggest not giving access to everyone to deploy to production. Instead, they should reach out to the production support team, and the production support team should do a code review before the deployment. Once the code is reviewed, the production support team can publish the package to production.

I have seen organizations that have been able to generate an ROI of almost 100 percent, as well as organizations that have struggled to generate even a 10 percent ROI. Some companies are very good at knowing what licenses they have bought and how to use them, but I have also seen companies that have a whole suite of automation tools that they are not using, including process mining and test suites. They are still paying for all of these tools, but they are struggling to generate an ROI.

The main complaint I receive about UiPath is the pricing. Many people purchase the entire suite, which can be expensive, even though they don't need all of the features. The pricing is also somewhat opaque for businesses of all sizes. Unless a company is a UiPath partner, it is difficult to customize the solution to pay only for the features that are needed.

I would rate UiPath eight out of ten. We have experienced some automation processes that did not turn out as expected, especially with legacy applications, which can be challenging.

I have not seen any challenges with UiPath upgrades, but there are a few things to keep in mind. Consider a client with an on-premise deployment. The developers have returned their code, which is very old. After two or three years, the client is finally upgrading. During this time, a few activities may have changed drastically or been removed from UiPath because they have been merged into other activities. In these cases, we need to do some maintenance to ensure that the upgrade is successful. We need to check that everything is ready and that the upgrade looks good. This may take some time, but it is the only maintenance that is required.

In the past, we have used UiPath to automate repetitive manual processes for companies in the finance and banking sectors, but healthcare is our current focus. This industry involves processing tons of data from patients, customers, and doctors, so it's a huge field. 

Previously, I developed bots for compliance at financial companies. I've also created processes for reading PDFs, sending emails, Excel automation, logging, and exception handling. We have also contracted with insurance companies that need to pull data from emails into their main enterprise application.

The healthcare companies cannot provide us with direct access to their systems for security reasons. We are currently accessing their network through a middleware system so it doesn't compromise their security. UiPath doesn't work on that third machine and cannot retrieve the values as it should. If we scrape data from the web, it will get to the HTML that is behind the site. 

When we are accessing the third PC, we cannot get to it because it is a desktop machine. We are using the completed version activity, which is working mainly on the image image-based activity. This capability is available in UiPath, but I don't think Power Automate or Automation Anywhere can do this. It helps because we don't need to do any coding. 

UiPath tends to be deployed on the cloud, so clients can minimize their on-premise footprint. We deploy on-premise and cloud-based UiPath depending on what our clients want. For some companies, uploading data to the Orchestrator on the cloud is potentially a security concern that hasn't been resolved by the UiPath developers. Power Automate has an advantage in that regard. 

Our employees use the company's credentials to get training from the UiPath Academy and obtain certifications. I have a personal account on UiPath Academy, but it has some license issues. The academy is helpful because UiPath is implementing new features every three months or so. It's all about the documentation. We can learn about new features and do more. With more knowledge, we can develop something bigger.

UiPath reduces costs by eliminating human labor. Let's use an insurance company as an example. Let's say they have employees who are responsible for reading emails. Every day, they receive information via email from the customers, and their job is to retrieve the details and enter them into the main database. The average insurance company receives 400-500 emails daily. These people will spend the whole day completing the task of manually transferring data to their main application. 

We have a bot in pre-production that can handle 1,100 emails daily for the company. It has a significant impact on the efficiency of the operation because the bot can input the details into the database quickly and without any errors. The employees who were responsible for this work are now monitoring it and also learning about UiPath at the same time. It is a great tool for increasing productivity, thereby proportionally increasing the company's profits.

The first company I worked with had 20 employees in their compliance department working on some PDFs. The company had to send emails to around 6 million customers. We deployed the bots, and five bots could do the work of 10 employees. The company kept the other 10 employees but reassigned them to monitor the bots and fix errors. They also learned to develop their own bots. They could cut 10 positions and save money while improving productivity. Those employees weren't working as fast as the bots and cost more money.

The solution also greatly reduces human error. In the financial compliance use case, they were dealing with upwards of a million rows. That was labor-intensive work, and no human could complete the task in under three days manually. Sometimes, we would have some errors in which the values were reversed by accident because humans make mistakes when they are tired. In this kind of work, we're working with digital amounts and currencies, and we are applying mathematical formulas to the amounts, like credit, debit, or some business calculations. 

UiPath doesn't have large hardware or software requirements. We only need one physical PC on the client's premises. That computer requires some minimum specifications, such as a 1 terabyte hard drive and an i5 processor. We need that computer hardware and a license for the client. 

If the client doesn't want to purchase an enterprise license, UiPath offers a community version. There are no restrictions on the features, but it can only run one bot at a time. The enterprise version can run multiple bots. If our client only needs one process, we can provide them with the community version and deploy it on their PC. 

UiPath can free up employees to work on more important things. One of my colleagues was doing some tedious work manually, but once the bot was in place, he only needed to click one button to run UiPath, which extracts all the data and updates the Excel spreadsheet in 10 or 15 minutes. Previously, he spent up to six hours preparing the data before he could complete the other tasks. The important work was being delayed every time. It increases productivity, which benefits the company. 

UiPath's most valuable features are its UI automation activities like scraping and manipulating data. We need to scrape the data before we can manipulate it or save it in another application. I think that part is very valuable and important.

Having worked with other tools like Microsoft Power Automate and Automation Anywhere, I find UiPath to be the most user-friendly because it provides all the actions on the side, and we can just drag and drop them. It's a simple interface that we can easily understand. Automation Anywhere has a more complex interface. UiPath is straightforward enough that our junior employees can easily pick it up. 

UiPath's ability to offer end-to-end automation is critical. We typically provide our clients with a simple demo of what UiPath can do. After that, they provide us with details about their end-to-end processes, which we use to determine what can be implemented through UiPath.

For our healthcare client, the initial assignment was to scrape the data from the website and put it into Excel. Later, they decided that they wanted the data in another application, so it could be stored in the main database. We constructed an end-to-end process for maintaining a million records in their primary database.

I also like the UiPath Community forum. I go there when I get stuck with anything. When I run into an error, it's easy to find the answer. The community is highly active. If I post a question, I can usually get a response from community members in an hour or two. 

I have tried a bot that uses UiPath's AI capabilities, but I didn't develop it. It's a portal for patients to make appointments and check into reception at the hospital. We implemented ChatGPT on an Android device, so customers can ask questions and get information. 

We also developed a bot that can derive the same types of data from PDFs with different structures and formats. For example, let's say the patient's name is on the first row on one form, but on the third row on another. We can configure a bot to extract the name regardless of where it is. We can train our ML module by telling it when the data is wrong and running it again. Now, it's mostly accurate.

I would like UiPath to improve its screenshot feature. It should have the option not to take screenshots unless the user specifically allows it. Sometimes, it is a security issue for companies that do not want to share screenshots of the main application. Another thing I want to see is a standalone mobile application that we can run anywhere. I would like more cross-platform application support.

UiPath can get unwieldy if the process becomes too big and complex. I had one client based in Saudi Arabia that had an application with 1,500 pages. Once the bot we were developing got much bigger, the application started having stability issues. It performs well in typical cases, but once we exceed that average, the application starts to crash or behave abnormally. 

I have used UiPath for four years.

Overall, UiPath is stable for most processes, but Power Automate is better at handling large, complex projects.

I have worked with Microsoft Power Automate and Automation Anywhere. The primary advantage of UiPath is that it's more accessible than the other solutions. You can learn UiPath without any knowledge of programming or computer science. It takes only about a month to learn the tool, even if you have no skills. For example, if you're a blogger and you want to automate posting to the website, you can do that through UiPath, so it is beneficial for personal use and commercial use. 

The other advantage is cost savings. UiPath saves organizations some money, and it's more accurate than Power Automate or Automation Anywhere. Automation Anywhere is my third choice. Power Automate comes in second place because It was developed by Microsoft, and most enterprise companies have a Microsoft subscription. If their license includes Power Automate, they prefer to use that instead of buying a separate subscription for UiPath. 

Many companies are switching to Power Automate because of this bundled licensing. The UiPath enterprise subscription is somewhat expensive. Microsoft can provide the same functionality, and it integrates with tools like Excel and Outlook. Companies can get all those tools within the same license, so that's an advantage Power Automate offers over UiPath.

Another advantage of UiPath is that you can also work with image-based processes. If we cannot get any selectors or access the HTML code behind the application, we can use image-based processes. This feature isn't available in Automation Anywhere. UiPath has the AI center, and Microsoft also implements AI in Power Automate processes.  However, Automation Anywhere cannot use AI in their product.

My current company is smaller, so I'm responsible for multiple tasks. I am the requirement gatherer, developer, and deployer. At my previous company, they had a business analyst who talked to the client and made an inventory of their requirements that he provided to us. Then, my only task was to develop the bot. It was the other team's duty to deploy the bot on the client's physical machine. 

The process involves three steps. We need to connect UiPath and provide the logs. Our client can access the Orchestrator to see logs of what the bot is doing online. He doesn't need to physically access the machine. There is also middleware called the UiPath Assistant that we use to connect UiPath to the Orchestrator. 

The number of staff needed for deployment depends on the complexity of the processes. If it is a single process, we don't need a deployment person or team. The developers can deploy the bots. My company has five developers, so everyone is developing their own bots and handing them over to the deployment team. For every five developers, we have two deployers. If the five developers are developing automated bots daily, we need only two deployers to deploy them on the machine. Also, if we want to have a backup version, we can deploy it on GitHub to make the repository and organize everything.

The maintenance aspect can sometimes be difficult. Exceptional cases can arise during the process. When we initiate some processes, we need to monitor them for about 30 days. We don't monitor some processes because we're not seeing any errors or exceptions. We have to monitor other bots, stop them as needed, handle the exception, and run them again. After 30 days, the bot should be mature enough to handle the exceptions without intervention. 

UiPath offers an excellent return. For example, a recent client in Pakistan was scraping data from a website with 349 products. His job was to scrape the title, price, and variants and place the data in an Excel spreadsheet. He was working all week alone, so I proposed UiPath. I told him UiPath has a function called "Extract Data Table" that can scrape all the details of the products and just dump it into Excel in five or ten minutes. He was impressed, and I developed the bot in front of him. 

Now, he's running my bot and dumping all the results in his Excel sheet. He's also working on other projects, and his routine has become very stable. He has more time to spend with his family. It has surely made an impact and yielded a positive ROI.

I don't know the exact cost, but UiPath is more expensive than Power Automate and Automation Anywhere. 

I rate UiPath seven out of 10. Learning a little JavaScript coding is helpful because there are some scenarios in which UiPath doesn't help you. In some cases, you may need to write a little code to perform some actions or call some functions. I would also take advantage of the UiPath Academy so you can stay up to date on the latest news and features. 

Currently, we do not have any AI use cases. I work for a healthcare system. Our main use case is using UiPath to replicate what medical coders do. We input codes from certain medical systems into another, and it automates our billing cycle. This allows us to input the codes directly into the insurance billing cycle, speeding up our payment process.

Our hospital does not get paid if we are slow to get the codes to the payers. By automating this process with UiPath, we wanted to speed up the process of getting paid by the insurance companies. It has been amazing. Just this year, we probably saved 45 million dollars, and the next year, it will be upwards of 80 million.

In health care in America, many processes are still paper-based. Document processing is valuable as it allows doctors to have documents processed in advance, making it easier to access and ask questions. Additionally, UiPath has freed up staff time significantly, to the point where some staff had to be laid off. Our use of automation sped up the process of getting paid from insurance companies, saving us substantial amounts of money.

We're looking to add AI, specifically generative AI, but it's a matter of our organization implementing it. With autopilot features like Microsoft's Copilot or ChatGPT, users can start chatting immediately. However, with UiPath, one needs the UiPath Assistant installed on every machine, which is unrealistic as many people use the same machine in the hospital.

My enterprise has been using UiPath since 2021. My team inherited it in 2023, so it has been about 11 years.

The solution just went live yesterday, so I don't have feedback on its stability yet.

The solution is scalable. We previously had an older solution, and UiPath helped us revamp and upgrade our systems, making them more scalable.

The customer support from UiPath is amazing. We are part of the hypercare, and I would rate it as a nine out of ten.

Positive

We use Power Automate a lot and still incorporate it alongside UiPath. Some hospital systems require us to be all on-premises, so we use both UiPath and Power Automate to get our systems working as needed.

Some automations were built in-house by our team of developers. We also worked with an external partner and UiPath to implement some other solutions.

We have seen a 100% return on investment. The process is night and day when compared to paying employees over time for the same work.

It is more expensive than other automation services, but I don't deal with the financial details much.

As automation software, I would rate UiPath a ten out of ten.

Our primary use case with UiPath is to create automation software for the HR and the accounting department. Some of the automations that we do are automated attendance tracking, billable hours calculation, work hours calculation, expense reimbursements, et cetera. We have also completely automated our sales processes, such as contract building, invoice creation, etc. We do all this through UiPath automation. Earlier, all this was done manually, and it consumed a lot of time for us, but now, with automation, it's super-quick and efficient.

We are using a public cloud model. We host it on AWS.

It helps us to do end-to-end automation. The accounts and the HR department have a lot of employees to manage and a lot of queries come up. Previously, most of the tasks that we had to do were very time-consuming. For example, just attendance tracking and expense management consumed two days of the entire week, but after the end-to-end automation with UiPath, we hardly spend four to five hours per week on the same tasks. That definitely helped us.

Time-saving is the main benefit that we have got. The Build a New App feature helps us create our applications in a very quick and efficient manner. We can also share them with multiple stakeholders, which has saved us a lot of time. We used to spend two days per week on a manual task, but now, it's just four or five hours a week. A lot of time has been saved, and efficiency-wise, by introducing automation, very less errors are happening. That's one of the biggest bonuses of using UiPath.

It has definitely reduced human errors. With the end-to-end automation that we are doing, in addition to a lot of time savings, efficiency has been improved in terms of the number of manual errors. It has reduced about 95% of the errors. There are still minor hiccups here and there, but that's expected. With fewer manual errors, we are able to do things in a much quicker and more reliable fashion. Earlier, unnecessary time was being wasted on this, but now, we are completely dependent on automation. Automation and robots take care of everything for us. We just need to oversee things. That has made our life much easier.

We use the platform on the cloud. It has definitely reduced the on-premise footprint. One benefit of having a cloud product is that we need to do very little maintenance from our side. We just need to do the regular updates and install the patches that they give. It's on the cloud, so it's very easy. We just have to keep our application updated. It's very useful, and it saves a lot of time. With an on-premise model, a lot of maintenance is required.

It definitely speeds up digital transformation. We deal with a lot of employees or internal customers, and with automation, we are able to design applications that are very user-friendly. They are able to give us the data we need in a much quicker fashion. It has definitely been on the positive side for us.

For this digital transformation, we did not require any third-party or costly applications. Everything was there in UiPath itself. We just needed to subscribe to UiPath. It's a one-stop solution.

It has freed up a lot of employee time. The tasks that previously required two days per week now require just five hours per week. It has saved us that much time.

It has definitely saved costs for our organization. With the saved time, we are able to concentrate on different aspects of our work, and we are able to clear up most of our pending tasks. So, the efficiency has improved, which has been good for our business. Around 30% of our overall expenditure has been reduced because we are able to put in that much more work.

There is a feature called Build a New App in UiPath. I found that to be very good. It makes our job much easier to know how to build applications. There is also the Studio module. I am from a non-technical background. So, for me, designing and creating applications was very tough initially, but with the Studio module and the activity tab that they have, it's easy. Most of it is just drag and drop. I found that very valuable.

It's straightforward to build automations. The UiPath Studio has a lot of in-built templates to choose from. Most of the functionality is just drag and drop, and it can't get easier than this. It's really straightforward.

UiPath's user community is very active and very useful. The answers to most of my queries are already in the community. It's very user-friendly, and we can also clarify our doubts and have conversations with the UiPath community.

UiPath's academic courses on academy.uipath.com are also very useful. In case you have any doubts or you want to do any certifications, you can just log in. It's free of cost. You can just log in there and do your certification. You'll learn a lot. Both UiPath Academy and the UiPath Community are very good.

I'm from a non-technical background. For me, getting my head around designing and understanding RPA processes was very tough. UiPath Academy basically dumbed it down to my level. It has made it very easy for me to know and understand RPA. I have started designing and developing applications with UiPath. So, even a person from a non-technical background, like me, can produce reliable and very useful applications with UiPath.

The reports could be improved. They could be much more in-depth. 

There are some selector issues when it comes to web automation and desktop automation. There is a robot selector. When we feed the data, it tries to fetch the UI elements from that particular data, but that's not happening 100%. That could have some improvements. Apart from that, everything else is fine. I have not faced any other major hiccups or issues with UiPath.

In terms of additional features, some integration and API connector services need to be added, especially with the CRM software. Currently, they have a limited set of API connector services. They could increase that for the CRM software.

I have been using UiPath for nine months.

UiPath is a very stable application. We haven't faced any hiccups or any major downtimes. Being a cloud platform, it's very good. The only thing that we need to take care of is our internet and our system. Apart from that, I haven't faced any downtime issues or performance issues with UiPath. 

It's scalable. It definitely has all the capabilities for scaling up, but for our department, we most probably aren't going to scale it up because we currently have a sufficient number of users. We have been able to extract the best out of UiPath from the current usage, but it definitely has all the features to scale.

Currently, in our organization, it's deployed across multiple departments. There are 15 departments in our organization, and eight of those departments use UiPath. In our department, seven of us use this application. We have seven user logins for UiPath, but I am not sure about the number of users in other departments. The majority of users are non-technical staff and developers. There is a 50:50 ratio.

I have been in touch with their technical support, but my involvement is very less. They are very friendly, and they are very knowledgeable. They could solve most of the queries within 24 hours, and for most of the queries, they also had help documents that they shared with us so that we could learn, and the next time it happens, we are able to resolve it ourselves. So far, their support has been very good. I would rate them a 10 out of 10. I don't have any complaints so far.

Positive

We did not explicitly use any other product for RPA. 

I was not involved in its deployment.

We got some training from UiPath's third-party team on how to go about using the software because we didn't have any clue. For initial installation and deployment, we did not require anyone else. We did it ourselves. We just required some training on how to go about using the software.

In terms of maintenance, it requires minimal maintenance. It's a complete cloud product, and its maintenance involves downloading the latest release or updating to the latest release. That's it. We just have one person who takes care of all of these aspects. We don't have an extensive team to take care of the maintenance of the product. It's very easy for us to do maintenance. One thing that we like very much about UiPath is that it requires very little maintenance.

We have definitely seen a return on investments on UiPath. Basically, a lot of time was saved for us. We were able to concentrate on other aspects of our work. Tasks that previously required two days now just require four to five hours. There are about 30% cost savings with UiPath. 

The return on investment is quicker with UiPath. Earlier, the output that we wanted from a task took around 15 days, but now, it just takes around a week. That's the return on investment that we are getting from UiPath.

It's fairly priced. It's not too costly, and it's also not too cheap. When you bundle it with the UiPath Academy courses and the great community that they have, it is worth the price. 

We did try out Automation Anywhere. We did a trial of that software, but that was not reliable for us. We didn't like the performance that it offered. That's why we went for UiPath, and we have been using UiPath since.

Non-technical people have this misconception that automation is only for people with a coding or development background. I would definitely suggest trying UiPath because it breaks that barrier. Anybody with a little bit of computer knowledge will be able to design simple-level applications.

You can try the community version of UiPath. It's a free version of UiPath. If you are interested, I would also recommend trying out the UiPath Academy courses that are being offered by UiPath.

I would rate UiPath a 9 out of 10. If they can bring the integrations and the API services, it would make the product the best in the market. All other aspects are very good.

In Brazil, we have some standard processes. Some companies operate in similar ways. I cannot give all the details, but there is a process for financial invoices. We normally use UiPath to automate this process.

Using UiPath is very easy. Even for new users or developers who are just starting, it is easy to use. You just need to drag and drop the activity, so it is very easy to start using. We have UiPath Academy, which is very helpful when you need to learn something. When anyone is starting to use UiPath here in my company, we recommend starting with UiPath Academy. It helps a lot in every project that we have here. 

Also, there is the community, which is very helpful. We have lots of users, and for every question that we have, we can just Google it, and then we can find the answers in the community. Almost all the questions that we have can be found in the community, which is very helpful. We also have different integrations with different services, and this is very helpful as well.

I do not have any complaints about the tools themselves. They work very well. The only problem is the cost. It was more accessible initially, and we could have more resources with the same license. Now, the license is different, and we need a license for each tool that we have, so it is not very accessible to have all of the tools for installation.

I have used it for about six years.

The stability is very good. In the beginning, we depended on our infrastructure. However, now that we have services on the cloud, it is very stable.

Scalability depends on how you are automating and using resources like queue triggers. If you use queues, it is easy to scale. You just need to change the number of robots for the process, and then it works very fast.

Every time we need support, most questions can be answered by searching on the Internet or finding solutions in the community. When we require technical support, we contact UiPath. For instance, we had trouble with the database while using UiPath on-premise and connected to support. They were very helpful, addressing the issue in three hours. Therefore, I would rate customer service a ten. It's a very easy tool to use, so normally, we do not encounter many troubles. But when we do, the answers are either in the community, or we contact support.

Positive

It depends on the customer and project. Sometimes, I am involved in the deployment process. I might be a developer, and sometimes I need to deploy in a development tenant. Another team analyzes and deploys it to production, or we deploy it to a tenant for deployment. A global team, for example, analyzes, publishes to production, and ensures they have all the documents before publishing to production. We use the process to run through.

In the beginning, the return on investment is quick. As automation scales, requiring more licenses, it becomes more expensive. At first, processes save money, but eventually, automation without cost savings occurs due to licensing costs.

Besides using UiPath Academy, having expertise in the automation process is crucial because it is not just about setting up automation. Governance becomes critical as automation scales. Planning is essential before starting the process to avoid chaos as automated processes increase. For example, restricting developer access to production is crucial. Overall, I would rate UiPath an eight out of ten because, while it is the best tool regarding resources and integration, pricing is problematic.