I use UiPath for work projects that involve various applications, including license rebate processing and healthcare licensing. I develop reusable components for these projects.

Specifically, the process involves launching different licensing websites and extracting essential information such as license number, status, effective date, expiration date, and any disciplinary actions. This data is collected from providers like physicians, dietitians, opticians, and speech therapists. We validate the extracted information against existing databases or applications, updating records where necessary.

This validated information is crucial for determining the approval or denial of applications, such as those related to provider enrollment. Essentially, my work centers around creating processes with defined inputs and desired outputs.

Currently, I'm focused on a project within the manufacturing sector, specifically a constant bidding branch. Here, we gather order information for stakeholders, including tracking numbers, tracking statuses, and approximate order values. We store this data in an Oracle database, generate a CSV file from it, and distribute this file to stakeholders via email.

Building automation using UiPath is easy for developers. It is easy for them to manage and start building with the automation.

UiPath empowers organizations to improve their staff's time management and become more cost-effective. By automating routine tasks, it frees up employees' valuable time to focus on higher-priority work.

UiPath enables end-to-end automation. Our process begins with meeting stakeholders to determine which processes are suitable for automation. We assess if existing tools are sufficient or if new ones need to be implemented. We also identify applications that automation could potentially replace. If all requirements are met, we obtain sign-off for automation and prepare process documentation, such as Process Definition Documents. We then consult with business stakeholders and obtain managerial approval on the Solution Design Document. This phase can take several weeks and involves outlining the specific solutions and applications required for the automation. Next, we create a video demonstrating the automation workflow and explain the process to stakeholders. After securing sign-off from management and SMEs, we begin the development phase. The completed development is sent for UAT and then moved into production. We typically monitor the automation in production for one to two months. Any errors trigger email notifications, allowing us to promptly address issues within UiPath Studio and re-deploy to the live production environment.

The UiPath User Community is a valuable resource for developers. It allows us to share knowledge and find answers to questions or issues we encounter, without needing to submit a support ticket.

It has significantly improved our efficiency by automating many manual tasks, leading to a noticeable benefit for patients. Now, thanks to automated benefit processing, patients receive instant approvals or denials from their insurance providers.

Our company encourages us to complete UiPath Academy courses to further our understanding of Robotic Process Automation. These courses equip us with the skills and knowledge necessary to solve complex problems encountered in real-world scenarios. Completing the Academy courses and obtaining certifications can be beneficial not only for career advancement within our company but also for understanding new features and process flows implemented in future updates. Additionally, these certifications can be valuable when transitioning to other companies as they demonstrate our expertise in UiPath products.

Human error is minimized by utilizing exception handling.

UiPath helps free up our time.

The most valuable feature is the easily accessible tool, such as the ARI framework, which I have used extensively. My interest in the ARI framework has grown significantly because the templates are built directly into UiPath, making it possible to automate more complex processes, while also simplifying the development and understanding for developers.

The UiPath Community Edition lacks some key features that developers find essential for learning and building their knowledge base before transitioning to the paid Enterprise Edition. To provide developers with a more comprehensive evaluation experience, UiPath could consider including all features in the Community Edition for a limited trial period. This would allow developers to fully test the solution's capabilities before making a purchase decision.

I have been using UiPath for four years.

UiPath operates reliably around 80 percent of the time. However, automation speed can sometimes be hindered by internal applications.

I had to contact their support once and they were extremely helpful in resolving my issue.

While I have experience with Automation Anywhere, I find UiPath to be more user-friendly and offer a more robust orchestration tool. Although Automation Anywhere offers child bots and AI IQ bots, it is not as well-suited for handling complex automation scenarios.

The initial deployment is straightforward. We can sign up with UiPath and set it up on our local desktop, or we can deploy it from our cloud cluster.

I would rate UiPath eight out of ten.

The amount of maintenance required depends on the project and the bots being used. On average maintenance is done monthly.

We are developing processes with UiPath for clients in the government and banking sectors.

UiPath is flexible and has various automation capabilities. I like PDF automation, and we have multiple other tools, such as the AI Center and Document Understanding. There is more than one way to automate the same process. We can broaden our experience and use our imagination.

UiPath facilitates our digital transformation. We have an auditing team for our client that was manually collecting data every month from eight websites across different Indian states. We also have to validate the files we get. It takes a person three days to do that manually, but UiPath automation allows us to complete the process in a day, and it's more accurate. There were no errors, which is what the audit team requires. The banking sector is undergoing changes, and by using automation, the banks are improving.

The solution reduces human error in cases where we have Excel automation invovling some formula that needs to be copy-pasted, or we need to fetch the data from PDF to Excel in a particular column. It's easy to make a mistake when both keys are next to each other. For example, we may make an error while writing "S is equal to A," and we might ignore it. A UiPath bot will perform that without making an error. If the process is properly designed and trained, we'll get the correct output.

I appreciate UiPath's ability to automate complex processes. It's the best thing. The Action Center, Document Understanding, AI Center, and all the other components of UI Path are also good. I prefer UiPath over other automation tools.

It's easy to build processes in UiPath. I am from an engineering background, but UiPath is a low-code solution, so it's easy for a user with a nontechnical background to understand. It's simple to explain things to business users. If I need to explain things to my clients, it's easier for them to understand how UiPath works.

I have developed multiple end-to-end processes, including SAP, web automation, Excel, Outlook, PDF, and directory automation. For example, we might extract the information from the PDFs in a folder. A recent one involved invoice process automation. Invoices for rent and expenses needed to be processed for nine websites, which were automated in UiPath. It included SAP, web, and Excel automation.

The UiPath community has been helpul in cases involving clomplex logic. By getting in touch with the UiPath community, we could see all the new things that have been developed or released in the latest versions. We have community meetings.

I've also obtained multiple certificates through the UiPath Academy. There are foundational and advanced courses. I was certified in solution architecture, fundamentals and methodology, SAP automation, administrator automation, AI Center, and Document Understanding

The time needed to learn UiPath depends on how much time you're willing to spend practicing. I completed the UiPath foundational and advanced courses in a month because I was working on it day and night, practicing with the different tasks we got online. Some of my colleagues took three or four months.

We use UiPath's AI features for Document Understanding. We have to train the AI model repeatedly so that it extracts the data correctly from the PDF. We correct it when there are mistakes so that it trains the model. Similarly, we have the AI Center, where we can choose from different models available from the UiPath or create our own.

A lot of the UiPath processes are capturing information from government websites. It's difficult to capture the correct format, so we need to use a third-party application to capture the information correctly. It would be better to have that capacity with UiPath, so we don't need another product.

I have used UiPath for more than two years.

I rate UiPath seven out of ten for stability. The stability varies from machine to machine. If you have enough RAM and CPU, it should be fine. Sometimes it lags on computers with older processors. I'm using an i7 11th generation, and it works perfectly fine. Also, sometimes there are issues in new versions, but it runs smoothly in the latest stable version.

I rate UiPath support seven out of 10. The response speeds and the solutions they provide are excellent. I have contacted them multiple times to open up cases. Recently, a URL was not working due to some architecture issues, and they responded within two hours.

I have done one process on Automation Anywhere, but it was only an Excel automation.

The implementation varies from process to process and the availability of the process team. I have done processes on various timelines. It sometimes takes a week if the process is small. A few took around three or four months because the scope was larger. It covered 10 to 12 human steps and involved manipulating data in SAP and Excel. It doesn't take as long if it's a simple process that involves moving a PDF, copy-pasting, or bulk emails. It depends on the process length and the testing needed before we can move the process into production.

I handle the deployment because the infrastructure team does all the installation and orchestration. I have admin access, so I can publish and upgrade packages and maintain the licenses, machines, bots, queues, etc. It is all published in the Orchestrator and run on the production machine. Maintenance is required of ther are changes in a URL or some input.

I rate UiPath nine out of 10. UiPath's license costs more than other tools, but once it is all set up, it's easy to use and is effective at multiple types of automation. If you don't have experienced developers, you can learn to use the UiPath Studio to develop some basic code.

We are primarily automating business processes from SAP applications and a few from a web-based application.

UiPath reduces the number of human employees needed to do repetitive tasks. A person can only work during normal business hours, whereas a bot can work 24/7 without making mistakes.

UiPath is user-friendly. Building automations isn't complex, and it doesn't take many days to learn. If you have basic knowledge of any programming language, you can start building small projects in 30 to 45 days.

If it is a fixed process instead of a dynamic process, we can do end-to-end automation. Automating this kind of process is easier. If it's a dynamic process, we need some kind of external integration.

UiPath's community forums were helpful in my early stages, when I was learning the product. When I got errors, I was sometimes unsure what they meant, so I could go onto the forum and find answers easily.

They also have these UiPath Academy courses. I've taken the foundational course and the advanced courses on Document Understanding and data manipulation. I still haven't had a chance to work on Document Understanding, but the data manipulation course has been helpful. I learned to do some queries that simplify the workflow and make it faster.

I have fewer issues with the user interface when I'm using Blue Prism or Automation Anywhere. For example, if you want to perform an action in UiPath, it's a little tricky because you must click on a particular icon. When you click on that, some selectors are generated. That will change whenever the application updates, so you must change the selector again after the update. When we are dealing with Automation Anywhere, we'll not get any selectors if we are using that action once.

I have used UiPath for more than two years.

I had an activity crash once when the permissions failed. When we were using that activity, it automatically created multiple activities. Even though we dragged it and used it only once, it created multiple activities. That only happened once.

I have tried Blue Prism and Automation Anywhere.

UiPath is deployed on-premises. We only needed to download UiPath Studio off the website and install it. It took about 30 minutes.

I rate UiPath eight out of ten. I recommend taking the UiPath Academy courses first. Take the foundational course. It has some hands-on exercises with small automation processes. Later, they can complete the advanced course.

I have worked on multiple use cases with UiPath dealing with SAP, SharePoint, or a web application. We had to extract the data and do some automation of data processing. We were taking data from one environment, such as from an Excel sheet, and processing it. These were the use cases for which we used UiPath extensively.

In addition to app integration, there were use cases related to various frameworks such as REframework and State Machines. We used the REframework at the enterprise level to be able to handle exceptions and bot failures and make automation healthy, robust, and steady.

We have also done automation for a healthcare department for claim processing.

UiPath saves the execution time of processes running in the production. If a process was taking three to four hours previously, with UiPath automation, it can be completed within an hour with better exception handling capability and less dependency. It saves 50% time.

UiPath is capable of handling the complexities involved in taking data from different environments. It is also capable of exception handling. If any application has limited functionality, we can use UiPath for automation with that particular application. With advanced selectors and linked queries, we can get the data from the application or interact with the application.

UiPath Document Understanding has helped to reduce the data entry work and physical copies of documents.

UiPath enables us to implement end-to-end automation. For every organization, it is very important that automation is robust enough.

UiPath can help minimize your on-premises footprint. It depends on whether you plan to deploy your automation on the cloud or on-prem. On-prem has various challenges and restrictions, but it also has benefits.

UiPath speeds up digital transformation without requiring expensive or complex application upgrades, or IT application support. App integrations are advanced and robust. It is plug-and-play. You can integrate with Excel, Outlook, SharePoint, SAP, and various databases. There are pre-loaded activities. You can integrate with GitLab or GitHub. It has inbuilt activities for enterprise-level applications.

UiPath reduces human errors, but it also depends upon the process. It depends on how much interaction is required and what exception rates are there. When everything has been identified, it can reduce errors by more than 70%.

The first feature that I like is the exception-handling capability. The second feature is the REframework provided by them, and the third feature would be the Orchestrator functions. There is also the feasibility provided to monitor the ports and deploy the code. There is monitoring, retrieving, and all those things. We can use the web or mobile application. These are the key features of UiPath.

For handling complex scenarios, REframework is good. It has good exception handling and in-built mechanisms.

The certification can be made more affordable.

In terms of features, we get regular updates, and AI has recently been integrated. As of now, I do not have an area of improvement. They have already improved the functionality of Orchestrator. As compared to two or three years ago, Orchestrator now offers different functionalities and services. There is a difference, and it has improved.

I have been using UiPath for more than three years.

It is stable. Our organization has licenses because we cannot upgrade the application in sync with the Community version. The enterprise has to stick to one version for a certain period or whatever tenure has been mentioned in the license. The Community version is the playground for UiPath. They upgrade it, and all the beta version updates are there. They come to know how things are going and what are the responses and challenges.

It is scalable. It is used in multiple departments. The size of the organizations that use UiPath varies. They could be MNCs or startups.

Their support is good. After procuring the licenses, when there is an issue, there is a dedicated support team. They respond well.

The UiPath Community is vast. It provides an opportunity to get help from others. They provide good support, and the MVPs are actively engaged in responding to the queries that people are posting when facing any challenge. We can find relevant information by searching with keywords. It is good.

UiPath Academy has been useful in learning about new topics and new versions.

I am quite new to Automation Anywhere, but a better exception-handling mechanism and the ability to interact with various applications make UiPath more unique. The drag-and-drop interface is attractive to people who are not very technical. The user experience is more intuitive.

We have on-premises and cloud deployments. The deployment part takes about a week because we have to prepare the production environment. A week is good enough for the deployment.

The number of people involved in the deployment varies. Support teams are there. Developers are also there. There are also people from the change management team.

Like any other software, it requires maintenance.

I would recommend UiPath to others. Overall, I would rate UiPath a nine out of ten. It is robust and scalable, but there is always scope for improvement.

I use UiPath to automate various processes in the energy industry, including invoice processing and contract registration.

Building automation using UiPath is easy.

UiPath enables us to implement end-to-end automation. This is important for the impact of the work and the satisfaction of the client.

The UiPath User Community offers great value because it allows us to find support, ask questions, and collaborate and share with other members.

UiPath has improved our organization by enabling us to automate repetitive tasks.

UiPath has helped minimize our on-premises footprint.

We utilize the Academy courses to prepare for certification. The Academy, a structured learning environment, provides me with the opportunity to acquire knowledge systematically. While it offers a wealth of valuable information, it primarily serves as a foundation for earning the certification. To gain practical experience and proficiency with the tool, additional hands-on work is necessary. Nonetheless, the Academy courses serve as a valuable starting point.

UiPath helps speed up and reduce the cost of digital transformation. The digital transformation does not require expensive or complex application upgrades.

UiPath has helped reduce human error.

UiPath helps save around 80 percent of our client's time.

UiPath has saved us thousands of dollars over the years.

While I haven't explored all of UiPath's features yet, I'm interested in using some of them to discover potential use cases, scenarios, and projects relevant to my work. For instance, the collection center functionality seems promising. It allows clients to create tasks, fill in fields, trigger activities, and log execution process details. Additionally, verifying and managing jobs while switching between different items.

In UiPath, when debugging an issue, we cannot revert to previous steps while retaining variable values. Compared to Blue Prism, UiPath presents greater difficulty in troubleshooting bugs.

The orchestrator may occasionally disconnect and lose communication with the machine, failing to provide real-time warnings. Additionally, error messages displayed throughout the solution lack clarity and conciseness. Furthermore, workflow names cannot contain spaces or symbols, leading to complications during package download within the project. However, no warning is issued for such naming inconsistencies.

I have been using UiPath for five years.

UiPath is not 100 percent stable but it is within acceptable range.

UiPath is scalable and it allows us to build scalable solutions.

We use both UiPath and Blue Prism, depending on our client's specific needs. However, in most cases, we recommend and utilize UiPath as our preferred solution.

The initial deployment was straightforward, but it does require some fine-tuning. I use the framework for deployments and customize it according to our client's needs.

One person is enough for the deployment.

The implementation was completed in-house.

UiPath provides a good return on investment. It saves on employee costs through automation.

UiPath pricing is average.

I would rate UiPath nine out of ten.

The environments and number of endpoints we deploy UiPath in vary by client.

One to three people are usually required for UiPath maintenance.

We use UiPath for intelligent automation integrated with machine learning models.

We previously did many of these processes by hand, and our team found that frustrating because it took a lot of time. There was a chance we could have errors in reports that are critical to the organization. UiPath processes are around 90 percent accurate. Since we implemented UiPath, it has become essential to our organization, and we cannot live without automation now.

UiPath has helped us reduce our on-prem footprint. Its AI functionality has helped us automate more processes while speeding up digital transformation and reducing costs. UiPath has saved team members' time, allowing them to spend more time on valuable tasks instead of tedious, repetitive jobs.

What I like the most about UiPath is that we can build custom activities. If we want to customize functions based on our logic or use case, we can do that.

We also like the UiPath community. It's the best help you can find online. If you have any issues, you go to the UiPath forum to find answers to existing questions. If you can't find the answer you're seeking, you can post your question and get an answer quickly. The UiPath Academy has some hands-on activities to practice, and they offer a certification. It's a great way to grow your knowledge. One drawback is that the cost of the certification exam is pretty high.

The most valuable features are document processing and integration with AI/ML models. Using the solution's AI functionality was a bit challenging initially, but once we researched how to use the intelligent automation, it was fairly simple. Overall, building automated processes is easy. The end-to-end automation capability is crucial for large organizations because it reduces time and energy.

We use intelligent automation for things like document processing. There is a validation center where the ML model extracts some values, and we can validate if it's correct. That aspect could be improved a little. The percentage of values extracted without validation could be increased. It's currently an attended process, but they should give you the option of making it unattended.

I have used UiPath for more than four years.

I rate UiPath eight out of ten.

I rate UiPath 7.5 out of 10 for scalability.

I rate UiPath support eight out of 10.

I have used Automation Anywhere. It's also a good solution that's easy to use, but I like UiPath a little more. I prefer UiPath because I've done more projects on it.

Deploying UiPath is straightforward. The implementation took a few months because our use case was so complex, and we had to optimize the processes to make them more efficient. Our development team has four people. After deployment, the bots require some maintenance. Admins need to update the automations and ensure the bots are running.

We've realized considerable time savings with UiPath. We were previously reading and inputting information from documents manually. One document took almost two or three hours. UiPath automation brought that down to two or three minutes.

UiPath is relatively expensive. It's not expensive if you only need to automate one or two processes, but if you need to use more, it's somewhat costly. There's also a free community version.

I rate UiPath eight out of 10. My advice for new UiPath users is to complete the training first. Get all the knowledge you need to implement automation before you start working on it.

We use UiPath Studio, specifically the enterprise version, for developing projects per organizational requirements.

UiPath makes building automation processes easy and accurate. It allows us to create a wide variety of feasible automations. Even complex processes can be tackled using UiPath's features, such as object repositories and document understanding.

UiPath offers end-to-end automation, which is crucial for our work. This allows me to handle various tasks. I can efficiently open any web application required by the organization or our clients. I can download documents from web applications and fill in the necessary details within them. I can extract important metadata from documents or web portals. I can store the extracted data in a designated data queue. I would rate the process a ten out of ten.

By automating tasks through the use of robots, we can achieve significant time and manpower savings. This, in turn, leads to reduced costs for the company. Additionally, automation improves accuracy, as robots are less prone to errors compared to humans performing repetitive tasks daily.

I use the UiPath Academy courses in my free time to get some diploma-level certifications.

UiPath reduces the cost of digital transformation.

UiPath helps reduce human error.

UiPath helps to save staff 70 percent of their time through automation.

The community version of UiPath has a limited feature set, which can make it challenging for users to fully explore its capabilities without purchasing the enterprise version. Offering a trial period for all features could provide a more comprehensive evaluation experience for potential users.

I have been using UiPath for four years.

While UiPath has disconnected on a few rare occasions, it has generally been stable.

UiPath is scalable 80 percent of the time.

The initial deployment is moderate.

The implementation was completed in-house.

UiPath is expensive.

I would rate UiPath nine out of ten. There are many RPA tools and UiPath is at the top of the list.

UiPath requires maintenance for any changes that are made.

I recommend reviewing the documentation and completing the UiPath Academy courses before using the solution to automate processes.

I am a consultant working on RPA solutions in general. UiPath is one of the solutions that I am using.

The use cases depend on the clients. I have done automation of sending mail with invoices in it. We have used it for analyzing PDF documents, getting information out of these documents, preparing in three different languages depending on the client, and sending invoices by email.

We are also checking VAT numbers on the EU side to validate the client's VAT numbers and related data. We have automated the generation of reports out of SAP for two different managers and teams. We have also automated including specific signature images within PDF documents and sending them to the related service or email address.

We have mainly used UiPath to focus on processes related to the finance department. The targeted processes are the ones that are the most repeatable and require a lot of effort but there is no real focus and attention from the user. Because of its repeatable nature, the risk is that users do not pay attention to the process itself and make mistakes.

Generally, we do not implement end-to-end automation. The idea is not to automate an end-to-end process but to automate a part of the process that takes a lot of time and resources. That is the focus point, so it is not a matter of having an end-to-end process implemented. It may occur, but often, it is a part of the process where the focus needs to be reliability or time and resource consumption.

The benefit for our clients is time and reliability. They quite often see the benefits in terms of the reliability of executing the process, even reporting mistakes or errors that happen during the execution of the process. That is something quite valuable for them.

Usually, it takes our clients at least one month to realize the benefits. If the processes are executed on a daily basis, then it is quite fast, but there are processes that are triggered every month or every quarter. In that case, it will take at least a month or a quarter to see the benefits. Once it is executed, there is quite an immediate benefit. On the other hand, it takes time to analyze the process because often processes or procedures that are written are not in sync with what is executed by the user. We have to modify them. Often, by questioning the end user, you end up finding the shortcuts and implementing them, so the analysis takes more time, and the implementation takes less time.

UiPath reduces human error. That is one of the main reasons why automation is done for customers. Two main reasons for automation are reliability and resource availability.

UiPath saves time for our customers, but it is hard to know how much time it has saved because it varies from process to process. For example, the process of validating the VAT numbers on the EU website used to take two or three resources every quarter, whereas now, it is reduced to less than half an hour. These time savings are valuable, but the added value is reliability.

UiPath has not had a lot of impact on the digital transformation because the processes that are requested to be automated are already digital. The reason for automation is to speed up the process or make it more reliable. There is no real impact on the digitization of processes.

In terms of the reduction in the on-premises footprint, I am not always aware of the eventual use of the processes that I am implementing for the clients with the bots. I see that some of the bots are not used anymore because they have their own application that includes a big part of what has been automated on their side. It depends on the way they use it and how often they use it because I have bots that are running every day, and I also have bots that are running once a quarter. The ones that are running every quarter are harder to evaluate because people are not always able to see the resources released from executing those processes. Because they are executed every quarter, they are usually not measured. Our clients generally go for automation for reliability.

Specifically in the recent versions, the ability to change the interface is valuable. One of my clients had to upgrade the SAP version and move to a web-based UI. This was handled by isolating the UI interaction within the library for the targeted SAP on the client side. I upgraded that library to handle the web-based, and the bots worked fine after that without modifying anything in them. The usage of libraries is very important for me because it helps a lot in this kind of upgrade, specifically because SAP is used across the company. It is impacting a lot of different businesses within the company.

It is quite intuitive and fully handled by a visual interface. It is no big deal for me. I have been a developer in the past, and I have used Visual Basic and C#. If I need to specify something exceptional, it can be done. It is not a big deal. For me, it is very easy. There is a competitor with an open-source solution called OpenRPA, but for me, UiPath is far better and more intuitive.

There should be the ability to customize the building blocks instead of having to specify everything in every step. We should be able to combine these building blocks to make specific processes faster.

There should also be some kind of templates, similar to Power Automate. Power Automate provides templates for a specific context.

I have been using UiPath for two and a half years.

I am absolutely satisfied with its stability.

I did not have to worry about it so much because usually, my clients want to take control of their bots. They want to execute it when they want, so I have had no experience with the scalability of UiPath.

I have not contacted their support. When I am developing, I try to make a bot quite stable. I am aware of what is happening and what it is doing, and I can notify people with logs or names of different events that are occurring during the process execution. I know exactly what is happening and where. It is quite easy and fast to diagnose and fix if there is an issue, but it is not often that I have to intervene in production. If a process is designed correctly and safely, not much intervention is required. Clients look for this kind of stability because that will save the time that they will have to spend fixing things in the production environment.

They have a UiPath Community, but I have not used it often. If there is something blocking, I go over there, but generally, I find the solution to the issues through my colleagues.

It has always been on-premises. The setup is quite straightforward. If there is some kind of Orchestrator to be installed, it is more difficult, and it takes more time. Usually, they want to have someone internally to handle the Orchestrator. I am more focused on the bots and the triggers for these bots to be executed. I am not that often involved in the implementation of the infrastructure of UiPath for the operational side.

Bot development duration varies. It depends on the process, but it can take a few weeks to several months. I have bots that were developed in two or three weeks, and I also have bots that took at least six months because they were quite heavy and complex. Generally, it does not take longer than that because then it will not be as valuable to the clients. If it takes more than six months, it is better to have it developed in their own software.

Bot deployment is quite straightforward for most of my clients because, during development time, I take care of environment parameters. So, deployment is quite straightforward. It is a matter of deploying and pressing a button to have the package deployed. We then set parameters in config files, but it does not take a long time to have it deployed.

Bots usually do not require any maintenance, but if the source of data has been upgraded or modified or the UI has been modified, they might require some maintenance. Usually, once the process is running and every source is stable, there is no need for maintenance. When the data source changes or the infrastructure changes, such as the main server being moved or renamed, then there is a risk over there, but it is not a big deal to adapt.

Generally, two or three people might have to investigate the cause of the issue. If the issue is inside the bot, it is not a problem. One person is enough. If it is related to external data sources or infrastructure, it may take two or three people depending on the segmentation of the clients' people in their departments and services.

I do not know about the exact price because I am not selling anything. I propose several solutions to the clients, and the client does choose one of them. If UiPath is chosen, they contact the official reseller in the country. In one case, I had the prices in front of me, and it was not expensive for the service it was providing.

I would recommend it depending on the needs. UiPath can do a lot of things, and I have covered only 20% of UiPath functionality. Based on my experience and the needs that I had so far, UiPath has been quite valuable.

I would advise defining your use cases. That is the rule for everything. Once you have the use cases analyzed, you can specify what is needed, how you would do it, and what is the best solution to have it implemented. One thing that I am doing is that I am mixing solutions, where, for example, UiPath interacts with Python processes that I have developed. Python processes provide information in files. Web scraping is not difficult in UiPath, but it is quite heavy. In Python, it is faster to develop and use than with UiPath. It also depends on the number of iterations and resources available to execute it. It is a matter of the quality of a particular functionality in UiPath. UiPath relies on the .Net framework, and it has its own limitations. It has quite a heavy set of libraries and frameworks. It is a matter of balancing what you are expecting of it.

I would rate UiPath an eight out of ten. It is a good product. It is well-designed and well-executed.

The use cases are quite broad. UiPath is used in customer contact centers, supply chain management, operations, etc. It is useful for the intelligent automation of task-oriented processes.

It's easy to sell clients on a cloud-based solution like UiPath because it's the easiest to maintain and run. Some of the customers have already adopted a cloud-first strategy, so it's crucial for them not to have to operate their own data center. Others need to have a data center for privacy reasons.

The solution helps customers reduce costs by about 20 percent. UiPath doesn't require any expensive or complex application upgrades. It has reduced human error. UiPath has improved outcomes like SLAs and customer satisfaction scores while reducing wasted time.

UiPath frees up employee time, but the exact amount varies from client to client. It depends on your scope and your use case. You can obviously save time. It depends on how you design the process or whether you're automating one process or 10.

I appreciate the stability of the UI automation, the studio, and the development environment. I also like the platform's rich capabilities. Stability and performance are always essential when automating through the user interface. This is what they definitely bring to the table.

Regarding the ease of building automations, I would rate UiPath nine out of 10. It's the best tool in the marketplace. It's easy to build automations, and the interface is easy to use. I like how it integrates with the Orchestrator and everything works together. There are so many different use cases that we can easily connect through APIs, databases, and user interfaces to automate all kinds of applications.

UiPath's end-to-end automation is critical. It's the most efficient way to automate. You automate mundane tasks so that people can focus on everything that requires expert skills or knowledge.

The solution's user community is amazing. There's a lot of knowledge and experience, and it's easy to access that information. It's a highly active community. The UiPath Academy also has some attractive content that gives you hands-on experience with the product. The courses are easy to follow.

I have been using UiPath for about three years.

Excellent stability.

UiPath's scalability is excellent.

I have had limited contact with UiPath support, which says something about the product.

I have used Automation Anywhere and UiPath. I've looked at other options, but UiPath is at the high end.

Deploying UiPath is straightforward. It's fast. You can deploy UiPath in five minutes depending on what you need and how everything is configured up front. You need to get a platform account and set up the machines that will be part of the solution. You also need to set up users and assign them licenses. UiPath requires some maintenance based on the types of packages you're running. One person can do it. It isn't too complex.

UiPath is relatively expensive. However, it's the leading product because it has so many capabilities.

I rate UiPath 9 out of 10. When implementing, I recommend sketching out your costs over multiple use cases and comparing them to an alternative solution.

We use it to automate repetitive processes. We are also using it to manage people and costs.

I have used it for automation in telecommunication, HR, and finance. I have also done two projects for IT. It is a combination. I have worked on all these different projects.

UiPath helps with cost savings and staff savings. We can use manpower for high-value tasks rather than for repetitive tasks.

UiPath helps with end-to-end automation. I have created end-to-end automation through UiPath. It is a high priority for our company. I have not yet worked on the AI functionality.

UiPath reduces human error. If it is a repetitive task, then bots cannot go wrong. They have already been coded with whatever is required, so human errors are generally not there, but there can be scenarios that have not been covered, and they can result in exceptions. We have to work on them and update the bots so that we do not get the same issues.

UiPath improves accuracy. The teams for whom we have done automation are happy. There are no errors. It improves their efficiency. Bots can work 24/7 or at whatever time they want. There is no dependency on time, which is not the case with humans.

The time savings vary from project to project. On average, if a human takes three hours for a task, a bot would take about ten minutes. UiPath reduces the costs, but I do not have the metrics.

UiPath is very user-friendly. There is ease of use. People can understand it very quickly.

It is very easy to use. It is very good. There are many people who are uploading learning sessions on YouTube, which are free. It is good to learn from there as well. There are many sources to learn and explore it. There is also a community of UiPath users.

UiPath Academy has complete courses for developers and business analysts. A business analyst can follow the course path created for business analysts, and a developer can follow the course path created for developers.

I have been working with UiPath for the last four years.

It is a stable solution. However, if your applications are changing, you will have to do some manipulations in the code. Now they have a feature where you can keep your UI things in your config or in the assets, which is helpful. It is easy.

I do not interact with them directly. There is a team that communicates with their support.

I know Automation Anywhere, and I have also done a certification on it about four years ago, but I did not work on it. I am not familiar with the features currently in Automation Anywhere, so I cannot compare it with UiPath. I have more experience with UiPath because we got more UiPath projects. We were going to work on a project with Automation Anywhere, but that did not happen.

I have also worked on UiPath Document Understanding, but most of my experience is with general automation.

I have set it up from scratch in one of the companies. It was not that hard. It was easy to set everything up. I was doing it for the first time, so it was a little bit confusing, but it was good. There were forums and YouTube videos. The UiPath team is also available if you need help with installation and what to use. It was good.

After the code is ready, the bot deployment takes 10 to 15 minutes. Three years ago, it used to take us an hour.

I have not worked extensively with any other tool. My experience with UiPath is good, and I would rate it an eight out of ten. I am satisfied with UiPath.