UiPath Platform Reviews

We are working with automation, and it is very useful for my enterprise and our clients. We are using UiPath for building applications for automation purposes. Some of our clients are in the banking industry. They ask us to create applications to automate their processes, and we use UiPath for that.

Our overall productivity has increased because the bandwidth of our people has increased. Previously, when we were manually doing a particular task, it used to take us two hours, and after building the application with UiPath, the same task is taking around 10 seconds. From two hours, the time has come down to 10 seconds, which increases our bandwidth and productivity.

We are moving into robotics, and in robotics, advanced NLP and AI are being used. As tasks move from being manual to being automated, it definitely reduces the effort and improves productivity. The saved time can be utilized in a better way.

Its ease of use is valuable. For building an application, if I give this product to a newbie, he or she would be able to easily use it and build an application with minimum knowledge. No extra training is required. Its features are self-explanatory, and anyone can understand them, which is the main feature of this product.

I extensively work on the automation part, and I like the drag-and-drop functionality for workflows. Its graphical workspace or visualizations make it a unique product. It provides good visualizations, which are helpful in understanding the workflow. I am very impressed by its drag and drop functionality, and I would recommend it to everyone.

It can be improved in terms of platform integration. It is platform-independent, but it should be easy to integrate with different platforms, such as Windows, Linux, Cloud, etc. If I am using AWS for my server response, I should be able to integrate that into UiPath. 

If I can get some manuals along with the product, it will be good to see all the features that are available in it.

I have been using this solution for the last eight years. I have been in the software industry for about eight and a half years, and I have been using UiPath very regularly for my day-to-day work. 

Its stability is good. In the last couple of years, I didn't have any problems. I would rate it a nine out of ten in terms of stability.

We have a team of 30 to 40 people who use this solution. At this time, we don't have plans to increase its usage. If the usage of this tool grows, it would definitely be better. It will increase productivity and more efficient use of our company.

I would rate them a nine out of ten.

I have used Visual Studio previously to build applications. I switched to UiPath because I like its interface and the drag-and-drop functionality. When I am building an application using this, it's very easy to edit the flow. I am very impressed with UiPath.

I'm involved in the development and deployment of applications. I have the knowledge, so for me, it is straightforward. Most of the features are self-explanatory, but there are certain features for which a newbie might have to refer to the manual.

The duration varies from application to application. It can be anything from 30 minutes to six hours. For the development of applications, we use the SDLC model. When our testing is complete, we deploy the application. We have a team of six to eight people for implementation. They are from the product team and the support team. They are software developers at different levels.

In terms of maintenance, it requires upgrades. It is a timely activity, and it happens once or twice a year. We do not have a separate team for maintenance. The same team involved in its deployment takes care of its maintenance.

We are able to build applications for our clients, and they are also buying them. So, we have definitely seen an ROI.

We are an enterprise. So, its price is bearable for us,  but I am not sure about the small industry. It might be expensive for them.

It is a promising tool. It is very helpful for my day-to-day work. For automation applications, this is the best solution. Its drag-and-drop functionality and visualizations make the work easy. It is a very good tool for me.

I would rate it a nine out of ten because I'm very impressed with this tool.

My previous company was in the banking sector, and we had done automation with websites, UI, SAP, Excel files, and PDF. In my current company, it is being used for finance and HR. We have ERP, CRM, chatbots, etc. We are using this solution to integrate different systems.

I use UiPath Studio to develop the code, and I use UiPath Orchestrator to publish my work. We have our own UAT systems to test the code. We can install the UiPath in the test environment and find all the compilation errors in the debug mode and fix them. We also have version control. If we upload a version and it doesn't work, we can downgrade the version. Everything is tracked in UiPath Orchestrator.

We are using it on-premise. In my previous company, it was on the cloud, and we accessed it through the cloud. 

UiPath Academy courses have been helpful for me. There were lots of activities that I didn't know about, and UiPath Academy was helpful for that. There are multiple ways to do an activity, and UiPath Academy helps you to find out those activities. When you start using it, you can find out which activity will work the best for you. The courses are interactive and not boring with just videos or PDFs. They have a mix of PDFs, videos, and interactions. It is fun and interesting if you have a passion for it.

I found the UiPath community very helpful. At the beginning of my career, I had lots of doubts, and I posted them in the community. We had got an unknown error, and we posted our query there thinking that there must be at least one person who has had the same issue. They solved the issue quickly. It was a quick response. If you post a question, sometimes, you can also get a response within five minutes.

I use attended automation, and it has helped to scale RPA benefits in our organization for processes that require human-robot collaboration. We have a process for reconciling bank statements. When the finance department is done with their files, they send them over to me by email, and I have to start the process manually from UiPath Orchestrator. It needs human interaction. It is a monthly process, and we don't want to automatically trigger based on something.

We use its AI functionality a little bit. We have automation for processing invoices that are in different formats. We are using an ML model to train and replicate the output based on the incoming PDFs. We don't have to manually identify the PDF format and process it. Its AI is very helpful in the case of dynamic files where when a PDF is in one format, we want to process it in a certain way, and when it is in another format, we want to process it in a different way. We have automation to automatically identify the fields and then process the documents accordingly. It is helpful in the case of dynamic files. 

It has reduced human errors. We have a process to send emails to the end-users based on the training they complete in our LMS. I did the automation, and the SME was very happy with that automation. She used to have lots of manual errors where she might miss one email id or put an incorrect email id. With the bot, we automated it and added exceptions, etc. It is more stable now, and there are fewer human errors. It is also very helpful for data entry work where there are lots of chances of human errors. All this can be avoided with a bot.

It has freed up employee time. The time saved depends on the complexity and the length of the process. For our LMS use case, the SME used to take around one hour every morning, and now, she doesn't have to do that. Even if she is on leave, our bot is available 24/7/365. 

The UI Explorer in the UiPath Studio is valuable. We can get a unique and dynamic selector for every element in the UI, which is helpful for me in finding out a particular UI element. Most of my automations have had UI interactions. So, I found it the most helpful feature.

It is pretty easy to build automations. I am from an engineering background, but even if you don't have much coding or programming knowledge, you can easily learn and use this tool. I used UiPath Academy to learn about this tool, and they have got a detailed explanation about everything. So, even if you don't have prior experience, you can easily use this tool.

They give updates every year. Before the new features go live, they put them out in the Community edition. When the features are stable, they release them. They have got a helpful community forum. If you have any roadblocks, you can post your question there and you will get a response, sometimes even within five minutes, depending on the complexity of the question.

When I started working with UiPath, there were no activities for SAP, but in the version that I'm using right now, there are SAP activities or SAP modules. Previously, I had to code everything from user login to user logout, but now, all the activities are available. I just have to drag and drop and give the username and password. I don't have to do it from scratch. It would be great if they can include activities for all of the most common CRMs and ERPs. They can integrate it with different activities for the most common systems.

I have been using this solution for around five years.

It is mostly stable. We recently upgraded our UiPath Orchestrator, and we stopped receiving the emails that we used to receive in the morning about the status of our bots and jobs. I created a ticket, and they said that the particular version or update that I had wasn't stable. They provided me with a different version that was stable.

It is great. In my previous company, one single bot was doing all the processes. In this company, we have six bots, and every day, around 50 processes are running. So, it is scalable.

For the email issue that we had, we created a ticket, and they responded the next day. The response time was less, and they also provided me with the correct solution.

Positive

When I started my career, I started working in Python and website development with Django. When I heard about UiPath and RPA, I felt that it is going to be the future. So, I switched to RPA. UiPath is the first tool I used, and I'm still using it.

I have used Power Automate from Microsoft, but I found UiPath much better because it has a single package with UiPath Orchestrator, Studio, etc. It has everything in a complete package.

I have also used Blue Prism. Blue Prism is more expensive. I used its Community Edition recently because I wanted to explore other tools, and I felt that its UI is not as good as UiPath Studio. They both have drag-and-drop functionality, but Blue Prism is not as user-friendly as UiPath. I have never used Automation Anywhere, but I have heard from my peers who are from the same background that it needs programming knowledge.

It was a bit complex because we have two virtual machines, and each one had three robots in it. We had to do remote desktop on the virtual machine to run the automation. We have recently improved all the processes in our company. They are now dynamic, and they can run in the background. Even if the virtual machine is closed, they will run.

It was implemented in-house.

We have definitely seen an ROI. It replaces the manual work and allows us to do other productive tasks rather than doing repetitive and manual tasks every day. If someone costs $50 per hour, and we are able to save one hour of manual work every day for that person, it is a substantial saving.

It is a bit expensive, but it is cheaper than Blue Prism. We have six robots in total. There are no other costs in addition to the standard licensing fees.

I love this tool. They have been improving it every year based on the user experience, or they have been releasing a stable version for any bugs.

I would rate it a ten out of ten.

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.

Currently, we use UiPath in multiple types of use cases and build innovations for our clients to improve their system operations. We don't plan to implement AI in our automations in the near future. We're interested in that market, but it's a long journey, and it's a little advanced for us right now.

UiPath is helping our organization with its environmental, social, and governance automation space. Though it's currently at a beginner stage, it is progressing, and we expect to see improvements. UiPath has helped us free up staff for other projects. We have engaged our employees in working with UiPath through presentations. 

UiPath's integration features are highly valuable to us. We are able to achieve a lot with them.

For the moment, I don't see any explicit areas for improvement. However, having UiPath come up with unique features or advancements would be beneficial.

I have used UiPath for five years.

I don't see any drawbacks because our content is not down over time. We keep it updated consistently.

As our environment has grown, I haven’t encountered any specific issues or limitations.

I rate UiPath support nine out of 10. It's great, but sometimes we see delays. We ask a question, and they have to get back to us later with an answer. Otherwise, I don't see any drawbacks.

Positive

We previously tried out another automation app, but it didn't meet our expectations for handling exceptions and managing complex workflows.

Deploying UiPath was straightforward.

UiPath is the best tool, but the price is challenging from a management perspective. The cost-benefit equation might not work out favorably for some smaller organizations.

I rate UiPath 10 out of 10.

We use UiPath for backend office automation and website integration. 

UiPath increases the dependability of our operations team and simplifies the coding process for novice developers.  It has freed up your staff time to work on other projects.

It's easy to automate rote tasks with UiPath. 

UiPath Studio could offer alternative coding methods. You could invoke the code with VB or C#, but I'm unfamiliar with either of those languages, and I don't have time to explore them. 

I have used UiPath for a little over a year.

My impression of the stability of UiPath is decent.

The scalability performance is yet to be fully assessed as the environment grows.

The documentation is not impressive, warranting a rating of five out of 10. It is neither bad nor great.

Neutral

I did not use a different solution before UiPath. The acquisition happened before my time.

I do not know of any alternate solutions evaluated as the acquisition was before my time.

I rate UiPath five out of 10. 

We use UiPath for our accounts receivable and accounts payable. We are a wood company that uses it primarily for customer care and finance.

UiPath helps us to reduce human error and eliminate some repetitive tasks involved in processing invoices, so our employees can focus on critical work. We have been able to assign users to different tasks. These tasks are done faster with fewer errors, and our customers our happier. 

The task recording is awesome. I love being able to see the processes and find out the issues a lot better.

I can't really say about the pricing and licensing.

I rate UiPath nine out of 10.

Our use cases for UiPath AI and automation are diverse and cover a number of functional areas within our business. We are doing everything from building simple to medium to complex RPAs. 

We have started utilizing communication mining and have a unique use case leveraging document understanding. Essentially, we are getting our feet wet across the board.

UiPath has allowed us to free up time for our employees so that they can engage in more value-added activities. Although cost has not been a significant driver, we focus on being more efficient and consistent throughout the organization. 

It has enhanced the overall experience for our stakeholders, including employees and customers, by streamlining processes and improving engagement.

Document understanding has been immensely valuable due to the breadth and depth of its application. Additionally, the potential of Generative AI is expected to drive significant value.

Since we are still in the early stages of using UiPath, identifying areas for improvement is challenging. We anticipate that some aspects may emerge as time progresses.

We have been using UiPath for close to a year, approximately ten months.

The solution has been stable so far.

UiPath has proven to be scalable.

We have received excellent customer service and support from UiPath. We have a good Technical Account Manager (TAM) and a strong relationship with the team managing our account.

Positive

We previously used Power Automate and other solutions. Most automation has transitioned to UiPath. We switched due to the fact that UiPath offers a broader range of functionalities and addresses our speed-to-delivery challenges.

The initial setup of UiPath was straightforward, thanks to a good partner.

We have been using an implementation partner, and they have been great so far.

While we have not yet achieved the ROI we expect, we are on target to do so. There have been some instances of ROI, although we are still in the infancy stages.

Typically, pricing is reflective of the value provided. While more value for less cost would be preferred, we do not focus extensively on costs.

We evaluated other options before choosing UiPath. It seemed best in class and fit our needs after due diligence.

I would rate UiPath a nine out of ten.

My client is a bank, and we create bots for them. They had processes that their employees used to do manually. They gave them to us to mimic the actions that they did. We automated those processes.

UiPath has increased the net worth of our organization. From UiPath, our organization has gained much more than expected.

UiPath improves the workflow. When we automate the processes, they go into the bank environment where they are used by all the employees from all the regions or states.

UiPath enables us to implement end-to-end automation. It is very easy to build automation using UiPath.

UiPath improves efficiency. The last project I worked on had 1,200 people working on the process. We automated that process, and with automation, 1,200 people have been eliminated directly.

I have not used UiPath's AI functionality but my team has. It makes it easy to automate processes that are more complex or involved.

UiPath has not saved us costs. When we use AI Fabric, we have to implement it additionally to the production environment, and it costs more.

UiPath has reduced human error by about 70%.

UiPath has freed up employees' time. The time saved depends on the process. If a person is doing the same process the whole day and we automate that, he has the whole time for other activities.

The Excel activities are valuable. We can do browser automation through other sites or tools, but for Excel, using tools or options like Selenium or JavaScript is quite complicated because we have to import the file from the JSQL or other things, whereas, in UiPath, we get direct activities. We can directly perform the operations by using the activities. We can directly apply logic to it, and that is how UiPath makes Excel automation easy. This is why I like it.

We have been getting positive outcomes from the UiPath Community. Whenever I have any questions, I go directly to the UiPath Community. Most times, we get the answer from there.

Currently, we have to additionally implement UiPath Fabric. It would be easier if it is already integrated with UiPath rather than having to add it. We have to take the dependencies by searching them. We should be able to go for the default ones.

Its stability also needs improvement.

It has been approximately one and a half years.

The stability needs to be improved. The UiPath selector is consistently failing.

It is a scalable product. We have about 150 users using the solution. It is being used in multiple departments.

Technical support is much needed. It has to be there. 

Our team has used UiPath Academy and UiPath Community. Whenever we get stuck while building the solutions, we most often get a solution from there. It is quite efficient.

Positive

I have used Selenium. In Selenium, we write scripts. We use the Java language for automation. We have to write the code, which makes it more complex, whereas, with UiPath, we can use direct activities, which makes it easier to understand and write the code.

We work in the cloud. Its deployment is easier. For the older versions, it was quite difficult, but with the upgraded version, it is quite easy.

It takes five to ten minutes, depending on how many bots you want to implement. If you want to implement one, you can directly do it in ten minutes.

One person is enough for the deployment. For maintaining the bots, we have a team because the developers and users do not have access to the production environment.

We have seen a 100% ROI.

The price of UiPath is comparatively higher than Selenium. Selenium is a free tool, and UiPath is quite expensive. 

Some organizations make automation costlier than it has to be. They use UiPath, and while selling the products, they make it more costly. It depends on the organization.

Freshers can learn UiPath. They will get knowledge about logic building. 

I would recommend UiPath to others. I would rate UiPath an eight out of ten.

I have done the certification in Microsoft Certified Solution Associate (MCSA) and Microsoft Azure Administration. I look after the actual environment site where we can run the bots. We watch the environment's behavior, and we operate the Orchestrator, which is connected to the AI system. We run different types of processes through Orchestrator, and I am the administrator of Orchestrator. I give the rights and assign roles to the users. 

UiPath has been performing very well. It is very easy to learn and understand. We are going to move the most work done by employees to the bots because the bots get work done in minutes instead of hours. An eight-hour job can be done in three to four hours. 

We plan to bring more bots for efficiency. We would like to add more bots and reduce the time taken for various tasks.

We can design bots in a static or dynamic way. We can use the dynamic way to perform the actions in any environment or platform.

UiPath has freed up employee time. The time saved depends on the complexity of the process.

UiPath is easy to work with and understand. If anything is confusing, we just send our questions, and we get the answer as soon as possible. Designing a process with email, Excel, and any other application can take more than 15 or 20 days.

UiPath saves costs. By using bots, we can save the costs of services provided by humans, but I do not have the metrics. We have many departments, such as finance and global compliance management, and it is hard to know how much cost it has saved.

Orchestrator and features such as Queues Triggers are helpful in monitoring the ports and looking after the performance.

I have done the UiPath Academy course to learn how to manage the environment and Orchestrator. I was able to learn many things through UiPath Academy, and I was able to work on Orchestrator myself. The benefit of UiPath Academy is that it is accessible from everywhere. You can continue watching the videos at home or in the office. The explanation, presentation, and instructors are very good. You do not have to watch the videos again and again. You can just watch it once, and you understand everything.

For UiPath Orchestrator and Studio, if I want to watch the performance of my machines at a specific time or time range, there is no option for that. There are options for one day or week, but there is no option to specify a date such as from Nov 1 to Nov 3. This option should be there for queues and monitoring.

It has been more than one year since I have been using UiPath.

I would rate it an eight out of ten in terms of stability.

It is a scalable solution. I would rate it a nine out of ten in terms of scalability.

We do not need much support to use UiPath. We are not getting many errors.

Positive

I have not worked with any other similar solution. I have only worked with UiPath Studio and Orchestrator.

We have worked on the Python scripts to design the bots, but it was complicated. We had to write more and more scripts and make them efficient. It was very hard. With UiPath, we found a very good option to perform the activities in an easy way. We do not have to code much. We can just drag and drop things and have a solution. 

It is mostly straightforward. We just need to call IT to install UiPath. I give the license via a machine key.

We have it on-premises. We have not connected it to the cloud or third party. 

In terms of maintenance, there are certain packages that we have to download for running the activities. For example, if I am using Python with UiPath Studio, I need to download a specific library.

We implemented it in-house. For deployment, there are two or three members of the team who work with UiPath and provide the infrastructure, and then we have about 25 developers. We have a development team and an operations team.

The development team develops the processes and the operation department runs those processes via triggers or manually. They are usually run on the Windows environment. There are multiple bots working at the same time, and we have the monitoring tool by UiPath, and we are also working via Kibana. Kibana works with Elasticsearch. We have all the logs and bots' performance metrics. We can view it all with one dashboard in Kibana.

RPA is the future. Every bank and organization is looking for bots to perform their jobs because bots are more efficient than humans.

It is an efficient and easy-to-use tool. If needed, you can get a lot of support through UiPath forums and other resources on the web.

We have not used the AI functionality in our automation program, but we plan to use it.

Overall, I would rate UiPath a nine out of ten.

I have used UiPath for use cases that are both transactional and linear. It involves human resources, cybersecurity, OEM reporting, IT service management, service delivery, and examining of patents and trademarks. We work with federal agencies in the public sector. 

I enjoy the enhancement of UiPath's debugging tools. I like the IDE and integration services. There have been massive improvements. I love to work with Orchestrator. It has become more streamlined and helpful. 

UiPath needs to improve its documentation. AI Fabric's installation was an absolute nightmare. I tried to get help from the documentation portal and couldn't find what I was looking for. 

I have been using the product for four and a half years. 

We have seen ROI with the tool's use. One of my use cases involves the Patent and Trademark Office, where two GS-15 patent attorneys worked on patent suspensions. An unattended bot helped to save two full FTEs' a year's worth of work. 

We wanted to achieve less human error with AI-powered automation. We also wanted to streamline the process so that human involvement was less. Also, it helped us do more things than a human. 

AI-powered automation has increased accuracy for one of our use cases. We used AI Fabric and Document Understanding to help with reconciliations that came in PDFs. 

Automation has helped us free up our resource time by over 1000 hours. 

I last used Process Mining in 2020. 

I don't enjoy using Power Automate since its scope is limited. The environment where I use Power Automate did not purchase advanced licenses. UiPath offers more flexibility for programmers who are into API solutions. It wasn't available in Power Automate, which annoyed me. 

I run a team of developers and spend most of my time in Orchestrator. It is the best product from UiPath.