What advice do you have for others considering UiPath?

I would rate UiPath seven out of ten. I recommend UiPath due to its robust user community, which provides valuable feedback that contributes to the continuous improvement and development of the product with new features.

I would rate UiPath ten out of ten. I have used UiPath in my last three companies.

I would rate UiPath a nine out of ten.

I rate UiPath 10 out of 10.

I would rate UiPath a ten out of ten.

I would rate UiPath a seven out of ten.

I rate UiPath 10 out of 10.

I would rate UiPath an eight out of ten.

I rate UiPath an eight out of ten.

I would rate UiPath a nine out of ten.

Always explore using AI first, as it is often a cost-effective and simple solution. UiPath's integration of AI workflows in a user-friendly way brings a lot of potential for automation.

I rate UiPath eight out of 10.

I rate UiPath nine out of 10.

I would rate UiPath a nine out of ten.

I rate UiPath 10 out of 10. I'm incredibly impressed with the pace of new features that have come out. I have been working with UiPath for six years since I graduated college, and I'm blown away by what's coming out every year.

I rate UiPath nine out of 10.

I rate UiPath eight out of 10. I enjoy working with it, and it seems to have everything we need. They're adding new features at a reasonable rate while not deprecating old stuff too fast. It's a smooth transition from classic to modern activities.

I would rate UiPath an eight out of ten.

I rate UiPath 10 out of 10.

I rate UiPath eight out of 10.

I rate UiPath eight out of 10.

I rate UiPath 10 out of 10.

I rate UiPath 10 out of 10.

I rate UiPath eight out of 10.

I rate UiPath eight out of 10.

I rate UiPath 10 out of 10.

I recommend using this automation tool based on the specific needs of the industry or organization. I'd rate the solution seven out of ten.

I give UiPath a seven out of ten. The advice I'd like to give new UiPath users is to first understand their specific use case for UiPath. I've noticed some teams try to adopt UiPath by first figuring out a solution and then trying to retrofit it to their existing problems. Instead, I suggest thoroughly understanding the problem before creating a solution. Many teams see others using UiPath and assume it's a cool new tool they can simply apply to their existing issues. This approach rarely leads to optimal results. You might be able to build a solution, but it won't be the most efficient. For first-time users, I recommend understanding your problem, then exploring UiPath's capabilities to determine the best solution. There are plenty of resources available, like forums and YouTube, to help with the building process. Remember, understand the problem first, then build the solution.

I would rate UiPath seven out of ten. We have 55 UiPath users in our organization. Code maintenance is necessary for UiPath due to the bot's interaction with external applications and websites. The bot must be adjusted accordingly if any of these applications or websites are updated. The primary challenge encountered during UiPath implementation is the disparity between development and production environments. Often, code is developed in a non-production system where access to certain applications, such as a client's portal, is limited. This necessitates dry runs in the non-production environment to ensure the bot functions correctly without making any unintended changes. Once the bot is moved to the production system, multiple controlled tests are required before it can be fully operational. The unavailability of a complete testing environment mirroring production conditions significantly hinders the development and deployment process. I recommend UiPath to any user because it doesn't require a hard-code programmer to be an RPA developer. This makes it easier and more cost-effective to hire resources. Other tools on the market require good programming knowledge, which means you need to hire someone who knows both the tool and a programming language, making resource hiring expensive. Secondly, UiPath uses minimal coding, which makes debugging very easy. UiPath is also adding AI and ML features and upgrading the OCR features regularly.

I'm an end user. We didn't have too many challenges integrating the solution into our existing systems. It does require some training. I'd recommend the solution to others. I'd rate it eight out of ten. If it had an offline mode, I'd rate it higher.

I would rate UiPath eight out of ten. We currently have around 130 active bots, though, in the past few years, we decommissioned a larger force of 300. We also boast a user base of over 80. The maintenance is handled by UiPath. For a successful RPA implementation, establish a strong framework and conduct a thorough analysis to guarantee the stability of your bots. In the long term, a well-run COE is invaluable. Additionally, explore the range of tools available to enhance your RPA capabilities.

UiPath is a strong contender, earning a rating of nine out of ten. However, its high price tag prevents it from achieving a perfect score. Automated processes require maintenance every three to six months. Additionally, training a robot using hypercapnia elevated CO2 may take three to six months. To ensure successful implementation, we need to identify potential robot failure points and mistakes. We'll simulate these scenarios during training to refine their character responses and behaviors. Following the training period, we'll transition to periodic monitoring. This monitoring will gradually decrease as we analyze data logs and the overall system performance through the central management tool.

I would recommend UiPath to others because it is the most user-friendly. It is also developer-friendly because of the community. It also works across systems. These are the three reasons for recommending it. We run a roadshow across the organization to understand which processes are redundant. We try to understand which part of a process can be automated by using the general RPA automation and only one tool. We also categorize them in terms of what can go under intelligent automation where a certain amount of decision-making is required. Another category is hyper-automation where we try to understand how to include different tools, such as machine learning code, AI code, NLP data set, or data mining set. If we have an existing tool for data mining and process mining, the final steps can be automated. These are three major criteria. For basic automation, we try to assess the type of automation. Is it desktop automation? What kind of resources are required? Do we need an attended automation or an unattended automation? Based on my experience, almost all of them are unattended automation. We then try to pull in the use cases, prioritize them, and start automating. UiPath keeps on enhancing its product. Four years ago, there was no AI Fabric or Automation Hub, and now, we have all those things. They help a lot in delivering the project and having a prototype view for all the projects that are running. Overall, I would rate UiPath an eight out of ten.

I would rate UiPath 8 out of 10. I recommend UiPath to others.

UiPath's implementation depends on the process and budgeting. If clients have a good budget, we proceed with UiPath. Otherwise, we suggest some other solutions. Sometimes, we need to minimize the time frame to do the repetitive task. Manually, people take a longer time to process any files. We are automating the processes to streamline them and minimize the team members' costs and efforts. If we have multiple tools involved, we have to put a lot of effort into analyzing them. If we directly go to development without thinking or analyzing, we lose time and effort. That's why it is very important to analyze the tools in depth. If the processes are straightforward, we suggest some improvements, which would be much easier. If multiple applications are involved, it takes a longer time. The complex process also requires some improvement, and based on that, we suggest whether to go ahead with UiPath or not. The solution enables us to implement end-to-end automation for 90% of the processes. End-to-end automation is always important for us because it creates business for us. When we implement UiPath for the client, each client will be satisfied and happy with us, and we can get more business. UiPath's user community is very helpful. We learn about different technologies and aspects when we get involved with the user community. Sometimes, we interact with problems that we have never worked on. We learn about such challenges and their solutions because of the solution's user community. If you are struggling somewhere, you can post the issue on the user community forums and get an immediate response. With UiPath support, we have to wait for 24 hours to get a resolution. We get quick responses in community forums because experts respond to us. Compared to other solutions, UiPath's community forum is much stronger. Most of our resources are first going ahead with UiPath Academy courses. After that, we give training because that is a basic point to start with. We are even onboarding the freshers. We ask them to go through their Academy courses, and after that, we allocate an in-house mentor. It will be much easier for us after they have an outline in their mind regarding the processes they have to go through. Once they finish it, we have an internal assessment and a training team that will assist in complex use cases. The biggest benefit of UiPath Academy is its proper outline and structure in terms of education. Anyone who can follow will at least get 40% to 50% of the learning from there. After that, they will learn a lot based on their practices. They can practice some examples from there if the basic concept is clear. The courses are structured in such a way that even kids can also start with them. The courses in UiPath Academy are well structured and planned. We cannot add the solution's AI functionality for every project. Around 50% of the projects we have done so far are related to AI. AI is helping a lot in terms of AI Center. The AI functionality helps connect with each application and for documenting. The solution’s AI functionality has enabled us to automate more processes overall. Other than licensing costs, the solution reduces the cost of digital transformation. Our complete business depends on UiPath. As a solution-based company, we are automating the processes. We don't have manual resources except the project manager and business analyst to analyze the processes. Our complete business depends on the solution's automation or the AI model. UiPath has freed up employee time for us. We have delivered two projects to a European-based client. UiPath has freed 90% of employee time in one of the processes and 85% in the other. It was a very big logistic company where we implemented UiPath using a Document Understanding to extract all invoices and feed them into the application. Earlier, they used to allocate these tasks to nine resources. Now, one resource can handle everything. We have been expanding into other tools for the last year, but UiPath has been beneficial and has saved us overall costs. We don't have any licenses with us. We just provide the solution. We deploy UiPath on-premises or on the cloud, depending on the end user's requirement. UiPath is usually deployed across multiple locations and departments. Maintenance will be required for UiPath in terms of new functionality during upgrades. I would recommend the solution to other users. We always suggest to every client and whoever reaches out to us not to proceed with UiPath without having proper knowledge. We say this because of the licensing cost and several factors involved. If the processes are just one time, it's not recommended to use them. Overall, the learning is good. If anyone wants to try UiPath, they should first explore smaller processes and then proceed to the bigger ones. Whenever new upgrades are available, sometimes they break the functionality, which we have faced a few times. If you are using version 12, stick with that and disable the updates directly from UiPath. First, try on the smaller instances, then proceed with the bigger ones. Otherwise, some production activity might fail. Overall, I rate the solution an eight out of ten.

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.

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 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.

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.

I would recommend starting with some simple or classic processes, such as reading data from an Excel sheet and a database. You will find it easy. My advice is to not start with something difficult. I would rate UiPath an eight out of ten.

I would rate UiPath nine out of ten. We have UiPath deployed in one location. Maintenance is only required when changes are made to the website. I recommend UiPath to others.

I would rate UiPath nine out of ten. I recommend UiPath as the leading RPA technology, considering the current market trends.

We're an end-user of UiPath. Currently, we aren't using AI technology in our solution. However, I like the idea of it. We'd maybe be able to resolve redundancies with it in the future. It may be on our roadmap in the future. I'd recommend UiPath. It's very accessible. I use a lot of products and this is the best product to give to customers overall. I would rate the solution nine out of ten.

I would rate UiPath a nine out of ten. Previously, we distinguished between Automation Anywhere and UiPath based on their bundled offerings. Automation Anywhere included category two AI capabilities with their RPA solution, while UiPath focused solely on RPA and didn't have much presence in the AI space at the time. Although UiPath could integrate with other AI vendors, this wasn't a significant interest for our clients. Most deployments we completed for our clients were central.

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

I rate UiPath nine out of 10. It helps to learn a little coding in languages like SQL and Python. You should also take time to learn the platform with hands-on experience, instructor-led training, and online resources. You can start with a foundational UiPath course if you're new to the platform and learn about the fundamentals of RPA processes. Then, you can create a simple automation project to reinforce what you've learned. I also recommend joining the UiPath community and asking questions on the forum. Once you have the basics down, you can try some of the more advanced programs on UiPath Academy.

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 would recommend UiPath to others, and I would give it the best rating. I have used other tools, but UiPath is my preferred tool. I would rate UiPath a nine out of ten.

I give UiPath eight out of ten. The cost brings down the overall rating. Maintenance is required when running UiPath on-premises for the server, OS, and DB. On a bi-weekly and quarterly basis. We also have to implement tools for the firewall. I recommend UiPath for large-scale and multinational organizations because they can afford the licensing costs. Organizations should explore UiPath before embarking on a transformation journey, as transformation requires significantly more cost than automating existing legacy applications. UiPath is flexible and can integrate with all applications.

My advice would be to begin with a small-scale approach and construct your automation incrementally. While it might be tempting to automate an entire process in one go, it's more practical to break it down into smaller components. This way, you can adapt and refine each piece as you go, reducing the risk of issues arising or changes occurring before the entire automation is completed. Overall, I would rate UiPath eight out of ten.

My advice is to encourage exploring the platform, although it might be overwhelming due to its rapidly expanding features. While there may be initial confusion regarding UiPath's focus on AI, recent events have clarified its core message. It empowers users to deliver the models they create, integrating smoothly with enterprise systems. It enhances automation capabilities while incorporating AI elements, ultimately putting you in control of the AI within the platform. I would rate UiPath ten out of ten.

If you are trying to do in-house development, the user experience is much better than any other platform that we have evaluated. It is easy to pick up. The UiPath academy, training, and forums are great. The biggest selling point for me is that you can pick it up as a business user and learn the platform in a matter of days or weeks as opposed to months or years. I would rate UiPath a nine out of ten.

Overall, I would rate UiPath ten out of ten.

I rate UiPath nine out of 10. There are still many other RPA solutions we haven't tried, so I can't say it's the best.

Overall, I would rate the solution an eight out of ten. UiPath is an RPA solution that is very easy to use and local. It's a good choice for companies that are new to RPA or have limited resources for training.

The ease of use depends on whether you're a developer or someone who mainly uses automation. Nowadays, it is much more user-friendly compared to when I first started using it back in the day. The landscape has evolved significantly with a wider range of solutions available today and they've made substantial improvements, especially in terms of document standards. Overall, I would rate it eight out of ten.

Overall, I would rate UiPath eight out of ten.

Overall, I would rate UiPath eight out of ten.

My recommendation is to thoroughly assess use cases and choose the right tools to prevent possible setbacks. Overall, I would rate it nine out of ten.

It doesn't have many direct competitors that offer a comparable blend of advanced automation features and competitive pricing. What sets them apart is their commitment to continuous improvement and innovation, evident in their advertising and technology enhancements. Overall, I would rate UiPath nine out of ten.

My advice would be to keep your problem-solving approach simple and avoid the urge to plan every detail. One common issue I've observed is people tend to overcomplicate the deployment, strategy, and overall decision-making process when adopting a new software platform. Instead, I'd recommend that if you can identify one or two use cases where the tool's benefits outweigh its costs, you have a solid starting point. Keep it straightforward, and you'll be on the right track. Overall, I would rate it ten out of ten.

Overall, I would rate it ten out of ten.

I would rate UiPath ten out of ten. I have used five other automation solutions and UiPath is the best. No maintenance is required. The development, scalability, and reliability of UiPath are the best, and I recommend the solution 100 percent.

I would recommend UiPath. I would recommend starting with very simple processes. Do not go for a very big end-to-end process. Start with a part of it, gain confidence in it, and then start building on top of it. Many times, the process that people want to implement is too complex, and they do not put it down on paper. They do not do a cleanup of the process, and most of the discussion is happening while developing, which makes it complex, so I would recommend starting with something small, seeing the results, and growing from there. Overall, I would rate UiPath an eight out of ten.

I'm a customer of UiPath. Whether building automation in UiPath would be easy or difficult depends on the application interface or the website. You first have to check if the application, interface, or UI is going to change over some time. If it won't, you must check whether the selectors are stable enough or if there are runtime changes. This is the initial check you must do to determine if it would be easy or challenging to build automation in UiPath. In terms of UiPath minimizing the on-premise footprint, my company doesn't have anything on-premises except for SAP systems, so most of it is on the cloud and a portal. I cannot exactly see currently if company costs were reduced or not by UiPath. In terms of my organization's implementation strategy, the team started with one bot for development, which was the attended bot, and then scaled it into ten or twenty bots and also used bot operators for the implementation, and then after COVID, switched the automations to unattended. The number of people required to deploy UiPath depends on the number of deployments your organization has. UiPath requires some maintenance, but since my organization moved to the cloud, the maintenance part is only secondary and only involves updating the firmware, so there is no maintenance from our side. Overall, UiPath is an eight out of ten for me. My advice to others looking into implementing UiPath is to deploy it at a medium scale rather than deploying it at the start, as that would be a bit expensive.

I'm a customer and end-user. I'd rate the solution eight out of ten. I'd advise people to try UiPath, depending on the size of the project and the business processes. It's important to calculate the expected ROI at the outset. Based on this calculation, you'll be able to gauge if it will be a product worth your time. If the volume of work is low, it may be better to go with an open-source option.

I would rate UiPath eight out of ten. UiPath is deployed across multiple locations. We have around 45 people that are currently using the solution. The cloud deployment of UiPath does not require any maintenance. I recommend UiPath for organizations with multiple daily tasks that can be automated. However, I would not recommend it for just one task.

I would rate UiPath nine out of ten. UiPath allows me to create automation solutions that are perfectly adapted to my business needs, making my work more efficient. Fifteen people in our organization use UiPath, and they are also responsible for maintaining the solution and ensuring that it is up to date. UiPath is used remotely within our organization. I recommend UiPath to others as it truly saves organizations a lot of time.

I rate UiPath eight out of 10.

The solutions we provide to clients to automate their business processes need maintenance. They can usually take on a few processes on their own, but if it goes beyond 10 processes, some level of bot admin is required. We don't need a proof of concept for a product that has been on the market for a long time. In the past three or four years, UiPath has been a proven solution. Customers can rely on the solution. We just have to make sure that their requirements can be met by the solution, and the other aspect is the cost. If these two aspects are taken care of, we can recommend that people go with UiPath. UiPath is one of the leaders in RPA technology, and we get more business from it. Customers either want UiPath, Automation Anywhere, or Power Automate. But most of our business is with UiPath. They keep on updating it and are building their own RPA ecosystem. That makes it very easy to convince clients to stick with this one platform for multiple solutions.

We are using a virtual machine and running the UiPath bots on that virtual machine. A little bit of cloud is involved, but mostly, it's on-premises because it's a sensitive environment. From my end, UiPath does require some maintenance. A dedicated team oversees all the existing processes that are running live. In some cases, there will be some maintenance required. For example, if the bot's accuracy level has reduced because of some internal applications being updated or changed, the bot has to be recalibrated to adapt to the new environment. In some cases, the bot will stop, and it has to be monitored and fixed. A dedicated team is monitoring and maintaining the bots as of now. I advise users to consider the environment where the solution will be used, the features of UiPath, and the challenges. They should consider how much UiPath would benefit that environment and how much benefit the end user will receive by implementing UiPath. UiPath has its own challenges and benefits. Do the proper research, and if you believe UiPath will be a good solution, go for it by all means. I will say it's fairly easy to do the automation. It's fairly straightforward and easy to use. Everything is simplified to the basic ground level. Everything is in the UI elements, and using those automation tools in UiPath is quite simple. I believe UiPath can do some automation for a good cause. Since most transactions running today are digitized, UiPath can automate all those transactions and activities, usually in an efficient environment and workflow. That would, in turn, have a huge impact on everything around it, like the environment or supporting NGOs and other organizations. UiPath can be used in such situations and will be very productive. Since we are a UiPath vendor, we have been doing all those end-to-end automation for our clients. We have been implementing end-to-end automation for a long time now. For each case, we are supporting businesses to move from a manual workforce to a digital workforce. I can share a few live scenarios where we implement the automation for the client. Currently, there are some cases where the customer has to replenish an ATM for a banking corporation. We are automating it end-to-end, starting from the request to replenish the ATM until the replenishment has been done. Then, the data has to be reflected in the internal application related to the bank. We start with taking the request, passing it to a third-party vendor who will do the replenishment, and we'll take the reports from them. Then, we'll do the data entry in the internal application, which will, in turn, be stored in the organization's back end. It's a huge database where all the data is monitored closely. So, we have implemented this solution of automating their ATM replenishment. Another use case is fraud calls, which some clients receive from outsiders. We are helping the bank mitigate all the risks and reduce the damages caused by those fraudsters by automating all their required actions, as proposed by the bank's policy, in dealing with all these fraudsters. I cannot disclose more since there is an NDA between me and my clients. The UiPath's user community is very helpful. There is the forum, and there is the UiPath support. Most of the time, we reach out to the UiPath support for any concern we have related to the UiPath's functionality. The forums are also a great help. They have many topics, and a lot of knowledge can be gained from those forums, with everyone sharing their knowledge. So, both have different uses and different scenarios to reach them. One is the support, and one is the forum, but both are very helpful in everything they provide. As a vendor, we are supposed to develop and maintain the solutions we provide, including UiPath. The on-prem footprint is increasing as we implement more automation. However, the on-prem footprint has been reduced from a manual workforce because everything is automated and fully digitalized. So, there are two different angles to this. The on-prem footprint is increasing from the vendor side and reducing from the manual workforce side. We have been using UiPath Academy courses for different roles. As a vendor, we are required to take these courses as and when they are available or updated. So, my team members and I take those courses on a frequent basis, at least once a year. UiPath's AI functionality is something we are exploring now as a vendor. We have not implemented it in any client-side projects, but we are exploring that angle to see the possibilities of combining UiPath and AI. We plan to use AI along with UiPath in the foreseeable future. UiPath does increase the speed of digital transformation because we are digitalizing the workforce and all the transactions carried out internally in the bank. It incurs a cost, but I wouldn't be able to answer whether it has increased or reduced the cost of digitalization. A mid-level to senior-level management employee will be able to answer it. As of now, I'm a consultant, but we are not aware of such commercialization details. UiPath has greatly helped reduce human error by a huge margin, up to 80% to 100%. One of the huge advantages of UiPath is that it frees up a lot of employee time by taking a huge workload from the employee and passing it to the bot. The main aim of implementing UiPath automation on any project is to reduce the workload on human users. Overall, I rate UiPath a nine out of ten.

UiPath is deployed on our company’s internal cloud. It is not that difficult to build automations using UiPath. UiPath does enable us to implement end-to-end automation. While implementing automation in your company, UiPath gives many benefits, like minimizing FTEs. Many of the employees are doing repetitive jobs on a daily basis, which can be done by robots or automation. Time reduction and error reduction are the main benefits we get from implementing UiPath. UiPath has freed up employee time for our organization. UiPath’s user community is very nice. Whenever you have some problems, you can get help from UiPath’s user community. UiPath is also very user-friendly, with many options to search on your own for YouTube videos that will help you. UiPath has helped minimize our on-prem footprint by decreasing the FTEs and saving employee time, which is important to us. We have used the vendor’s UiPath Academy courses. The solution speeds up digital transformation, and it does not require expensive or complex application upgrades to do so. It depends on your work system because sometimes, you have to implement the whole automation system into your computers. UiPath has saved costs for our organization. Overall, I rate UiPath an eight out of ten.

I would rate UiPath nine out of ten. UiPath's AI functionality can be used to help developers build automation processes, but it can be expensive. We use the open-source TensorFlow technology from Google, which is the same technology that UiPath uses. Our developers are willing to build and manage this technology themselves, which is a cost-effective solution. However, if we use UiPath's AI functionality, it will be managed by them. I am an architect. I have worked as an integration architect, infrastructure architect, and network architect. When I first saw UiPath, I thought it was just for scripting the front end, but it is much more powerful than that. I really like it because it allows me to find slow, expensive, and inefficient business processes and automate them. This can lead to real savings for the business. With traditional applications, there is often a business case that needs to be made before the application is built. But with RPA, we can see the savings every day. For example, if we automate a process that used to take ten full-time employees, we can see that we are saving ten FTEs every day. I enjoy using UiPath because it is a real solution within IT that can drive out real costs from the business. I recommend that those who want to use UiPath do not treat it like any other IT system. Do not simply implement it and expect it to be of high value. The most important thing is to understand the business well enough to use the tool to its full potential. In other words, automate high-value or high-benefit processes.

The ease of building automation depends on the developer, the size of the process that is being automated, how many applications there are, and how many systems there are. Compared to high-code environments, we can build the product much faster in a low-code environment. Automation can be done ten times faster in a low-code environment than in a high-code environment due to the number of syntax errors that we have to encounter in a high-code environment. All these things are completely eliminated in a low-code environment. We drag and drop activities. It's like a prebuilt code. We just have to fill in the gaps. On average, the tool is five to ten times faster than other RPA platforms. UiPath does not do digital transformation. It works more on process automation. However, it does contribute toward digital transformation. From the face of it, everything looks end-to-end. I have used AI Center to learn machine learning skills and build training datasets and evaluation datasets. I have developed ML skills and used them in bots. UiPath Academy has a whole set of courses on AI Center. I want to complete the courses diligently. The solution has reduced human error and increased the speed and quality of our work. It reduces the time taken to get things done. I use UiPath Academy courses all the time. If we go to similar content on YouTube or Instagram and try to find videos, the information might be right or wrong. It depends on the experience of the person in the videos. The content in UiPath Academy is official. UiPath creates the videos. We can be assured that the information is correct and reliable. There could be a lag between the product released and the videos on Academy. Sometimes, video creators on unofficial channels like YouTube and Instagram come out with videos faster than UiPath. However, UiPath's videos are complete, authentic, and reliable. I assume UiPath uses professional training software in the platform. The format of the courses is similar to those of The Wharton School. The community is excellent. People help each other out. UiPath encourages users by welcoming new joiners, incentivizing answering questions, providing links to external or internal documentation, and celebrating anniversaries. The solution has a wide variety of topics that the forum members can take advantage of. We can learn about Studio, different parts of the platform, and different functionalities. If we have a question, Google will show all the relevant links to UiPath with just a single word search. We usually find a good answer to our doubts in the forum eight out of ten times. I like the forum and encourage people to use it. People looking to buy the solution must try it out. They must look into the documentation if they cannot do it with the tool. They must also visit UiPath's forum. The forum is more helpful than the documentation. UiPath also has a search facility to search for activities. They can also look for UiPath Marketplace. If we face bugs, we can go to the forum. Overall, I rate the solution a nine out of ten.

The ease of building automation using the product is fantastic. The product speeds up and reduces the cost of digital transformation. I haven't seen many major upgrades to the customer's infrastructure or applications. I design and modernize the processes. If we can’t extract the data from databases, the customer will put that data in a flat file or Excel sheet and add it to a folder. We pick them up and do the processing. We are not supposed to touch the core system in the banking industry. So we may get it with APIs. Sometimes, APIs are not available when we do the implementation. It takes some time for the banks to build those APIs. UiPath is equipped with different integration tools, whether it is native or not. The solution has helped to minimize our on-premise footprint. It is very important to many of our customers. To minimize the cost and provide more streamlined processes across different customers, we have created a shared pool Orchestrator to connect multiple customers to the same Orchestrator. They pretty much share the same processes, but they have different system endpoints. We can clone the processes and modify the endpoint interactions and input data. Sometimes, they use flat files. We change the configuration minimally. The rest of the processes are cloned, enhanced, and supported. The solution enables us to implement end-to-end automation. We can automate end-to-end based on the scope, expenses, and processes. The implementation could be lengthy or short, based on the processes involved. End-to-end automation provides an edge to us as a consulting company to provide our customers with very advanced automation tools. We have different services and products that we can integrate UiPath with. We have a content management system. When we use Document Understanding, we relieve the users from indexing documents. UiPath would do the indexing using Document Understanding and archived document repositories. We sometimes do integrations with archives, too. It depends on the context of the implementation. Sometimes, we can automate 60% of the process because some are not UiPath-targeted processes, but we can automate the other process with other systems. We do not use AI much. We rely on Document Understanding, which is part of AI. In the next couple of years, because of AI's popularity, I believe UiPath will provide more features and enhancements related to AI. The tool has freed up employee time by 70 to 80%. UiPath has saved costs for our organization. A couple of weeks ago, we had a case about HR contracts in the Ministry of Labour in Saudi. By the end of this year, they want to digitize their contracts and link them to their official portal, where employee contracts are issued. They currently rely on Excel sheets to do the entry. UiPath processes that we support have proven that there are zero percent errors in them compared to human data entry errors. The as-is process was that an HR personnel must log in to the platform and do the data entry so the contract would be issued and sent to the employee. The HR personnel would interact with four or five pages and provide data like employee ID, mobile number, date of birth, position, salary, and increments. If there is an error in the data, it has a negative impact on the company. It's an official contract that is issued to the employee. If there are any discrepancies, they would have to rectify the whole process again. Besides, it would affect the company's reputation in the market. For example, if the HR personnel enters 50,000 instead of 5,000, the employee can claim that money. To avoid this, companies can export the HR master data into Excel sheets and put it in a folder. We can program UiPath to pick all the information and paste it into the Ministry of Labour portal. We can verify the data, do a quality check, and post it to the system. This process used to take three to five days to finish, along with an error margin. With the help of UiPath, we shorten the time by 80% with zero error margin. We have subscribed to UiPath Academy. All our engineers are certified in different UiPath certifications. I am a solution architect. I have done a lot of courses and certifications. In addition to the certification courses, UiPath Academy provides us with resources, information, built-in demos, and process standards. We deal with all the stakeholders in the customers' company. The product must empower localization. People who want to use UiPath must ensure that the processes they are targeting to automate are fulfilling the conditions for automation. Sometimes, a customer would expect to automate everything. We need to ensure the processes we are targeting to automate are repetitive. We also need highly skilled people to manage the automation. We must automate the high-value processes of the organization to see the results and recognize the return on investment immediately. Overall, I rate the product an eight out of ten.

We get the input files from emails. We read the input files, extract data from the template, and open it in the browser. We worked on an engineering product. We used UiPath to get information about the testing and the model's integrity. Certain information was in the Excel file. We had to extract information on whether the model had to be tested with plastic or without a plastic cover. There were drop-down messages. We captured the values and injected the JavaScript modules to autofill the data. Once the testing was created, we created a sample order. We filled out a form from the input file, gathered all the details into a summary, and wrote an HTML code for it. Then, we sent it to the client and informed them that the test had been created successfully. For SAP, we did an auditing type of automation. For example, we automated payments and filled in all the information from the template. Then, we had to propose, settle, and release the payment. In SAP, we are using VBScript also. It has some complex scenarios. If it is a PDF type of automation, I would recommend the latest technology called Document Understanding. I can define and train the fields using certain anchors and then go with extractions. Machine learning models are also possible. It would be the best way to do a PDF automation. Calling an API would be the right choice if it is an API approach. If we have been asked to download certain files from SharePoint, we create a custom Azure application. We define secret keys, certificates, and IDs. We define certain API permissions. Then, through UiPath, we install Microsoft 365. We can then download the file. If the process is more complex, ABBYY is the best choice. Building automation using the solution is easy. We need a little bit of programming knowledge for complex or hybrid automation. For easy automation, plug-and-play connectors and activities are readily available in the solution. We just have to get trained and use them. UiPath speeds up digital transformation and reduces the cost of digital transformation up to a certain extent. We required a ticket-tracking system where we needed additional third-party software like OneDrive and Office 365 to be installed. For Box drive, we had to install SDK. We also had other solutions like Google Drive, spreadsheets, and Zoom APIs. The solution has helped a lot to minimize our on-premise footprint. It enables us to implement end-to-end automation. It is important for customers because they want to avoid repeated tasks. If a customer wants to search for an email and upload it in a different portal, they might have to open multiple pages. However, if we choose end-to-end automation, things can work in the backend. The Picture-in-Picture mode in UiPath allows the user to work parallel to automation. So, while the robot runs, the user can do their work parallelly. I have not used the AI functionality much. I have used AI for a POC of a custom model where I had to identify objects from an image. There were many questions like how many people were in the image, how many cars were there, how many street lights were there, and how many fruits were there. I had to find the count of the people or objects and their confidence scores. It was a small POC with the object detection model built with Python. The product has helped to stabilize standard and structured processes. If the data is unstructured or unorganized, we use ABBYY as a third-party application. We have to train and classify all the assets and forms. The robot trains the modules using the connector and converts the semi-structured data into structured data. We can make automation more scalable using third-party applications. The cost is very high, though. UiPath is not that stable. I have used the Academy courses. I have also completed enterprise training and acquired a certificate as an RPA developer. UiPath has a very good community. If we get stuck on anything, we can get solutions for our problems. Currently, ChatGPT is also helping us in many ways. My UiPath skills are really good. I keep doing R&D on AI Fabric, automation, and other features. The community helps me to learn. A little bit of programming knowledge is a must to use the tool. A level one automation or a straightforward case with repetitive tasks does not require much programming knowledge. The user can use the solution if they have knowledge about the dynamic selector and wildcards. They should have a little bit of fundamental knowledge of computers and automation. Overall, I rate the solution an eight out of ten.

I'm a developer and an architect. The ease of usability and implementation for UiPath as well as the wide array of products that they have to support their automation journey make it a great product. The amazing support they have is great. The community that they have is bigger than all the other options, so you're going to find more resources when it comes to needing help with any type of issue. I'd advise those considering the product to look at the ratings and pertinent reports to get an overview of who's the best. I'd rate the solution ten out of ten.

The most important thing is to follow the best practices from UiPath in building the bot processes. What happens is, when application upgrades happen, if you haven't done it in the right way, your applications will fall apart. You have to make sure that the screen-grabbing methodology and referencing are done according to the best practices of UiPath.

From the business analysis angle, refine your use cases and make sure you are identifying the right ones, before deliberating about any automation platform, whether it is UiPath or not.

We have four people involved in deploying automation: one developer, a team lead, and two DevOps developers. My recommendation is to learn flow development.

I would rate UiPath nine out of ten. UiPath requires proper maintenance which is outlined in the user manual.

I would rate UiPath eight out of ten. Currently, we are handling approximately 20,000 units of data on a daily basis. Our focus is on efficiently processing this data and integrating it into the scaled servers. We utilize the scale servers for data connectivity, verification, and storage purposes. We are currently not using the AI functionality, but our company is anticipating a new project. The assignment of this project will happen very soon, and the company is considering the use of AI for it. However, this decision will ultimately depend on the user and the environment. If we determine that using AI functionality is necessary, we will integrate it into the project. At present, we have not encountered any users who explicitly require AI in their business logic. Therefore, we are not utilizing AI at the moment. Nevertheless, if any future clients request it, we will be prepared to integrate AI functionality accordingly. Our organization has started using automation with UiPath. Before implementing UiPath, everything was done manually. If the initial development is done correctly, then the maintenance would actually be significantly reduced. As a developer, we need to ensure that the code is always reviewed by developers, and they should always be available for this purpose. If the initial development is not carried out correctly according to the requirements, then imagine the consequences in the future. The development might need to be revisited for up to 15 years, or at least five years. If it is not done that way, the maintenance cost would be very high because the business processes keep changing. Therefore, to keep the system functioning well and the applications up-to-date, as they are not static, we need to continuously maintain the code. For instance, in the past six months, we've had to make two changes to the application we are working on. Many alterations occurred, such as UI element changes, shifting locations, and complete interface and navigation changes. Hence, it's essential for developers to always keep the code protected and up-to-date. I recommend conducting a proof of concept using UiPath to ensure that the budget and return on investment are sufficient to implement the solution within an organization.

I would rate UiPath a seven out of ten, mainly because of its high cost.

I would rate UiPath a nine out of ten. UiPath is reliable and accurate. The maintenance is easy. We only need one person to monitor and maintain UiPath. I recommend trying the free community version first to ensure that it meets the organization's requirements and then consider upgrading to the premium version in order to handle larger projects.

To those who want to use UiPath, I would advise understanding what digitization is and how RPA can help with their digitalization journey. Before using RPA, they have to standardize their processes in terms of the process flow. We encourage people to identify those gaps before using RPA. They should also select processes that provide a good return on investment. They can use the community version of UiPath to identify the processes. Overall, I would rate UiPath a nine out of ten.

I give UiPath a seven out of ten. Maintenance is required. We need to make changes to the code due to updates in the systems on which the automation is running. There are updates in the IT environments, such as operating systems, and also in the UI part. The newer features in UiPath bring new updates, and its components necessitate modifications to the code.

My advice is to start sooner rather than later with RPA. There is a lot of hype around the topic of RPA and customers are exploring it, but they can't do it without partners; at least not the first couple of projects. Deployments with our customers take about six weeks. We maintain the solutions we create. We normally have a support contract in place for at least the first couple of years. Maintenance, on our side, involves two or three people.

UiPath definitely speeds up digital transformation but whether it reduces the costs of doing so depends on a number of factors. Over the years, UiPath has done a pretty good job of continuously improving its product by adding robot capacities and changing versions. In terms of features, they have everything covered, with AI features, data mining, process mining, and all that was done quite ahead of everybody else. I would say that UiPath, as a company, was better in the past. Nowadays, I have less confidence in the company's situation, not that I don't think it's stable. And their ability to improve is a 10 out of 10. My advice is to study your use cases and go to the UiPath Academy. You'll find everything you're looking for and there is a big community. UiPath is easy to use, but you have to understand your work processes thoroughly and not just depend on the application to help you.

I rate UiPath a ten out of ten. We have implemented UiPath across multiple departments, including HR and Finance. No maintenance is required.

I give UiPath an eight out of ten. Some of our team members have utilized UiPath's Academy courses, and although we train using unofficial courses, the Academy courses are beneficial. 5,200 end users use it in our company. Five DevOps professionals are required for UiPath maintenance. My advice would be to take a look at the new features, particularly those related to AI. Many people discuss the old features that don't have much impact, but it's the new features that truly matter. I have learned that not everything can be automated, especially in complex scenarios where we must exercise extra caution in our environment.

I rate UiPath an eight out of ten. We deploy UiPath in multiple locations. The maintenance level depends on the criticality of the process and the Service Level Agreement for each client. Some clients may require 24/7 maintenance, while others may only need it during their work hours each week. I recommend familiarizing oneself with UiPath and then moving to an integration partner when ready.

We are quite happy with the solution as it is. If I were to go for UiPath again, I would not choose Digital Workforce as a supplier. I do not have any experience with any other solution, but we have had some glitches, so I would rate UiPath an eight out of ten.

There is a big learning curve if someone is new to programming. It would be better to have gone through some basic data types or to have an understanding of how logical sequences work. But apart from that, it is easy to build automations. Once you understand how to use logic, it's easy. In our company, people are still adapting. It's not 100 percent done. We are asking many teams to start learning UiPath and automating simple things first. There is a desktop studio and any citizen developer can develop an automation without learning much. It's quite simple to use. When you want to share something with other team members, you just publish it to Orchestrator and share it with UiPath Assistant. That is quite helpful for any team looking for automation. The UiPath Academy has different certifications and, on my team, everyone has done some kind of course there and received certification. They know what they're doing and understand how RPA works. I would suggest developing a basic understanding of how to use UiPath Studio, which is the IDE. Try different things and, then, if you're stuck, go to the UiPath forum for help. If it requires more detailed knowledge, then go with a video course in the UiPath Academy. But most of the time, we Google an issue and find answers on the UiPath forum or documentation. Sometimes a YouTube video will help. It's not necessary to go through the video learning process in the Academy to start using automation.

We are using the Enterprise version. We are exploring using it in the cloud, but some of our banking clients do not accept the cloud because of security issues so we go for on-prem only in those cases. We are not fully using UiPath's AI functionality but we are doing some PoCs, based on our clients' requirements, to check the feasibility. For that, we are using the Community Edition. As for UiPath speeding up digital transformation, I'm not sure. It depends on the process involved. Overall, I don't see a need for any additional features. I don't have any difficulty using UiPath.

To those evaluating this solution, I would recommend seeing it as one package. Before implementing it, the organization should also be ready for it because, with automation, people have concerns about losing their jobs. Organizations should have a clear understanding that robots are coming to save time. Overall, I would rate UiPath an eight out of ten.

I rate UiPath a seven out of ten. I would recommend it to others, but I can't give it a higher score because I'm not happy with the licensing model. That's what bothers me the most about UiPath.

I rate UiPath a seven out of ten.

I give the solution a ten out of ten.

I'd advise going with the cloud version of UiPath instead of the on-premises environment because it'd save the development effort and the setup time and cost. In the cloud environment, you can also run the bots on a usage basis. Going with the cloud version of UiPath would save a lot of time. Overall, I'd rate UiPath a nine out of ten.

The time it takes to set up an automation depends on the project size or complexity. It can take 15 or 20 minutes, and sometimes, it takes hours or a whole day. Sometimes maintenance is required because it slows down due to new features or an upgrade going on. We have about 10 to 15 people maintaining things, doing testing or helping when anyone faces an issue. We have 200 to 300 end-users in our organization.

I rate UiPath a nine out of ten. It automates manual tasks with accurate results. UiPath has been great for us.

I rate the solution 10 out of 10. We use UiPath to automate processes that deal with a ''good cause'' we are involved in; specifically, we use it for employee diversity. The product's automation helps a lot in achieving the results regarding our ''good cause''; we encounter fewer errors compared to other automation apps. Being a part of the UiPath user community is valuable. I recommend the solution and have recommended it to many of my friends who work in the same domain. We have yet to use any UiPath Academy courses, but we plan to in the future.

Go for it. I will give them an 8/10 because they met almost all of our needs and expectations.

I rate UiPath a nine out of ten. We have a few issues here and there, but they've done an excellent job overall. It's an innovative product. This is an excellent tool if you want to save time and money by automating repetitive tasks.

I would definitely recommend it to others. Automation is going to be a part of everything in the future. So, every company should start adopting UiPath for any internal or external needs. Automation is the best way to go ahead. We used to do the entire process manually, and we found a lot of errors. It was a time-consuming process on the whole. With the introduction of UiPath, we definitely saw the benefits of automation and a smooth process with fewer errors. I would rate it a nine out of ten. It's one of the best RPA solutions out there. I'm reducing one point for the AI features. Apart from that, I find it great.

The time it takes to see results depends on the task. Sometimes tasks are bigger and sometimes tasks are smaller. Sometimes it gives your results within a minute, and sometimes it takes time. On average, it takes a few days. I'm fully satisfied with this great tool. It is the best solution for all types of businesses, both small and large. I recommend it to everyone who wants to become an RPA developer. It is a fantastic tool and plays a vital role in RPA.

It is the customers who have to identify the things that they can automate. We have to promote our tools and RPA capabilities and when they understand these things they can come back to us and use us for what they need. Most customers don't know what automation and an RPA automation bot are. But when I do my first bot and show a demo, they understand: "Oh, this is how it works." And then they come up with more processes for us to work on. Regarding UiPath Academy courses, I have done some but I haven't had a chance to do the paid certification course because I'm continually working on projects. I did a couple of basic RPA developer courses and then the SAP, Document Understanding, and Action Center courses. I haven't had a chance to explore the new features there. To use UiPath there are no coding requirements, like knowledge of Python, but you need to have good problem-solving skills. You need to understand loops, flowcharts, and how to develop conditional actions.

I would recommend UiPath for IT-related implementations because it can save a huge amount of time. Whether you are a small business or a large enterprise, all kinds of companies can use it for automation. It reduces costs and helps with efficiency. If you are considering any other AI-based solutions, I would still prefer the UiPath Community Edition. It has a large set of features and is free. If you like it and it suits your organization, you can then go for the paid version.

Overall, I would rate UiPath at eight out of ten.

I rate UiPath eight out of 10. UiPath is the leader. It's the best automation software I've used. UiPath has rich documentation and a large user community. Developers can always find help in the forum. UiPath is a robust software solution that yields a high return on investment. I recommend first trying UiPath Studio and UiPath products in general to experience all the features. Sometimes, we don't realize all the available features to help us solve our problems.

To anyone considering UiPath, I would advise checking out the trial version of UiPath before going on to the actual version. Before you start using UiPath, there are a lot of things you need to get your head around. People who generally use UiPath have zero or minimal coding skills. This is something that you definitely need to know. You can try out the UiPath Academy as well. They provide certification courses. I have not used UiPath Academy, but I have seen my team using it for the certification program they offer. I have heard that it's very good. I would rate it a nine out of ten because I have not faced any issues with the product. Whatever we wanted to achieve with this product, we have been able to achieve.

I rate UiPath an eight out of ten.

In terms of implementing end-to-end automation, it depends on the process. We can do more with the advancements that I've mentioned, but every business process is different. I always say to my team, "This isn't about the tail wagging the dog. It's not the technology, it's the business process, and whatever tool is right, whatever fits." There are still exceptions that need to be handled by people so we're probably not there yet with end-to-end automation. Most good-sized business processes have business exceptions that require involvement from people. It's what we call "human in the loop." Two or three years ago it was 80/20 between automation and human involvement. We're now probably at 85/15 or 90/10, with more of the process being automated without human involvement. That's because there are smarter bots using AI—the brain—to execute automation tasks that previously had to be handed back to a human for decision-making or some other activity. On its own, UiPath doesn't speed up digital transformation. It's a tool. It helps, it's a contributor, but as a standalone, it doesn't. It needs other things. I had a quick look back at what their offering was in 2019 and what it is today. That's a good way of looking at how well they've listened to their customers. They've been smart in not just providing RPA. All their components now are far more than just RPA. They've recognized one of the biggest areas is process identification, that whole journey of identifying an opportunity and taking it through the life cycle, with things like Automation Hub. Generally, the response I get from my customers is they're impressed with the number of solutions that are available under UiPath's Enterprise platform.

I utilized Academy courses to understand the solution's full capabilities but haven't yet used many of those features such as AI. I am currently learning about OCR and plan to use AI in the future. Learning the solution is a case of "I don't know what I don't know" so it is important to become aware of all the tools at your disposal. I rate the solution a nine out of ten.

Academy courses have been very helpful in preparing our developers for certifications. I rate the solution a nine out of ten.

So far, we are happy with the solution. It seems very stable and scalable with many different uses. We are still in the early stages of using the solution, but things look promising. We are not yet using the solution's AI function. I rate the solution a nine out of ten.

They are always trying to look for, as much as possible, in-house creation of back-end processes. This means less clicking and tapping on the keyboard for the robot, which is always better. UiPath definitely blends all that together, which is great. It is literally bridging all our platforms together, which is what I love about it. With UiPath and RPA, the sky's the limit. There is potential for a bunch of things that you can do. When we started, as a construction company, we were thinking that RPA might not be as useful as we might think and make a bigger difference than our in-house solutions. When RPA came out, we thought it was mostly for companies like EY and PWC, e.g., more for financial auditing since there is so much data. However, we definitely benefit from it as a construction company. There is so much potential, whether it is low-hanging fruit or high complexity. It is definitely a win-win for any company, whatever industry you are working in. I would rate UiPath as eight out of 10.

Before searching anywhere else, just go for the UiPath Academy training. You will get all the things there. After finishing the training, you can switch to YouTube and other resources. The UiPath Academy is sufficient to teach you about any launched product. I would rate UiPath a 10 out of 10.

I rate UiPath 10 out of 10. I recommend trying it for a month. We tried it, and now we are hooked and still use it. I don't think anyone on my team or my boss wants to switch solutions anytime soon.

I would rate this solution seven out of ten. My advice is that depending on the business domain where you want to implement the solution, it's more feasible for document processing and ingesting data in applications, not for executing commands in various application servers or infrastructure. Stability is an issue. In large deployments where you have a lot of robots, these issues can cause a lot of intermittent problems with the operation of the robots.

The solution is cloud-based, but you have to have some components deployed on the local computers. That is the architecture of UiPath, but the base of the infrastructure is in the cloud. My advice is to just implement and begin automating. You don't have to even learn something before it, because everything is very intuitive.

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 rate UiPath eight out of ten. UiPath has excellent features, but you need to be patient enough to learn.

I would rate this solution a nine out of ten. It's an excellent product, but there is always room for improvement. I highly recommend UiPath as it's easy to learn and offers significant advantages for all kinds of automation. The solution is perfect for our requirements.

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.

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.

I rate UiPath a ten out of ten.

We will make use of UiPath's artificial intelligence and machine learning capabilities. We have been planning to adopt it and are in process of adapting. We are currently working on the pricing and the overall API conditions. I'd rate the solution ten out of ten overall. If any organization or prospective buyer is looking for some kind of solution for automating their work, then UiPath is a great choice. They can simply go with that. I recommended this to prospective buyers.

Because I have worked in all the major RPA tools, I can say confidently that UiPath is very developer-friendly. If you are coming from a non-technical background, or you don't know coding, they have a separate portal for you to develop in, called StudioX. It's a low-code platform, a "citizen-developer" platform. Anyone who wants to use UiPath can use it without any background. From the development, design, and testing points of view, I rate UiPath higher than other RPA tools for automation. Go directly to UiPath, rather than trying all the other tools. UiPath is number-one for development and testing. It is mandatory in our company to use the UiPath Academy to do RPA certification. Almost everyone has completed advanced professional certification in UiPath. The Academy covers every topic extensively, as far as what developers need. I don't come from an IT background but I learned it. UiPath teaches everything from scratch. With a little bit of coding knowledge, it's very easy to learn development using the Academy portal. The major advantage is that, since it is a video-based series, you get a clear idea of the modern-day functionality. They explain everything with an example and they give you use cases for practice. If you want to be an architect, they have a course for that. If you want a developer diploma, they have a course for that. And if you want to learn a specific topic, like deployment or testing, they have courses for them. For anyone with experience in another technology who wants to learn UiPath, or wants to do RPA projects, it's a matter of 10 to 15 days to go through all the videos and you can start working. That's a big advantage of UiPath. The Academy makes learning easy. They also have a Community Forum. If we have any doubt, we can interact with other developers around the globe. It's very interactive and we can learn what things are intended to do. About 90 percent of the time, you can find a solution using the forum. Other than the Computer Vision cost model, the features of UiPath are pretty awesome to use. As a developer, there aren't any drawbacks or difficulties when using UiPath.

We do not really have clients in healthcare, however, my previous company has mainly evolved into what I can say is a pharmaceutical supply chain. The company is an ordering platform for pharmaceuticals. I'm not sure whether I can consider that as a healthcare pharmaceutical or supply chain use case. I had done some trial POCs around the UiPath Apps feature. We did some basic trials within our team, however, we do not have any end-users who actively use UiPath Apps. We're still at an early stage in terms of using AI in our automation via UiPath. We tried out some POCs, and I'm also just getting training on that as well. We do not have any production use cases right now that go into full AI or ML. In general, they have a good ecosystem of developers. It would be easier to set up and use it. However, if a new company has heavier workloads and needs scaling capability based on time, they’ll need to calculate their requirements. For example, if I process 1,000 to 2,000 transactions per day and I need ten robots to do this and it's fixed every day, then it's fine. That said, if I have varying workloads, where the workload is the last week of the month and the workload is very high, maybe I’ll need twenty or thirty bots to accommodate this workload, while, for the rest of the month, I’ll just need around five bots. That's twenty-five bots that I’ll need to purchase, with many idle most of the time. That is one issue that needs to be planned correctly during the initial stage. Overall, I would rate UiPath eight out of ten.

UiPath doesn't require any maintenance. We are able to build workflows very quickly and it doesn't take that much coding knowledge to learn and understand UiPath. Beginners are able to learn it quickly and get into the businesses. Choose UiPath. It is more helpful than any other tool for implementing solutions quickly and creating customer satisfaction. Based on my experience, UiPath is the best tool for automating RPA projects and repetitive processes.

We do not use the solution's Automation Cloud service. We do not use this solution as much as we would like to, however, we use monitors with the Automation Hub to gather all different types of automation IBS in one place. All of our products are hosted on the Automated Cloud. At this point, we do not use the solution's UiPath app features or the AI functionality in our automation program. I'd advise users to follow best practices in regard to populating automation. It's a good idea to follow people's advice. You aren't going to make the wrong decision if other people have done it before. I'd rate the solution a strong seven out of ten. The only lacking parts I can mention are the monitoring and statistics.

I have not personally used the AI functionality when creating automations, although some of our clients use features such as Document Understanding for invoice processing. They also use the ML Trainer. These features help them to automate processes that are more complex. For example, when they have 20 or 30 invoices coming in each day, the bot is trained to look at them and it makes the job very easy to do. Also, when the accuracy drops, the bot can wait for input in an attended fashion. This has helped a lot of our clients. I would rate this solution a nine out of ten.

UiPath did a good job. Before going into production, we needed to make sure that every test scenario and every case was handled. That's where we took advantage of the UiPath. We would run UiPath again and again and there were no breakages in our code and nothing was falling apart before going into production. I was working for an investment bank and every record was important.

I have used the cloud deployment at well. Now I use the on-premises version. If anybody is going to evaluate UiPath, first, I would say, you need to look into what kind of automation you are going to do. If it's ERP, I would definitely recommend UiPath. If it's something, like a PDF or insurance kind of use case, then I wouldn't recommend UiPath. From my experience, what I understand is that UiPath is good for SAP. However, you can use it for any other kind of ERP as well. I'd rate the solution a seven out of ten.

I would rate this solution a six out of ten.

UiPath has a lot of free training and a lot of free processes ready to go. You have to see the best practices in order to receive the best way of development. It is important to see the best practices guide. I rate UiPath a nine out of ten. UiPath is great because it's highly stable, it's fast to develop, and easy to configure. However, there are some improvements to be made.

If you are working in the RPA domain as an automation developer, you should look at UiPath because it gives you many functionalities. Also, the education aspect of UiPath is a very cool feature because you don't need to rely on other software to learn it. Thirdly, the bot-building process is very smooth. UiPath is a fast, time-saving, money-saving, energy-saving solution. Using UiPath has been the best experience. I would recommend it. You can choose this software without any second thoughts. It can provide a good return on investment to your business.

I would highly recommend this solution to prospective buyers. If you are looking to fully automate manual tasks and save your organization time and cost, go with this solution.

For us, in some use cases, end-to-end automation means a need for Human in the Loop. There are certain points where the bot is not able to validate things and a human is needed to verify whether the bot has done things properly or not. But bots are able to process 90 percent of an end-to-end process. For monitoring, UiPath has Orchestrator. If any error occurs, the data is immediately updated in Orchestrator and you can easily see the error and the cause, and you can easily resolve it. In the UiPath Academy, UiPath offers the best content for each module and, after each video, there is a quiz so that we can show we have understood what we have learned from the video. There are also activities and a practice session where we can implement the use cases by practicing them in Studio. If we are stuck at any point after the practice, they have a solution area where they explain the steps you need to implement in Studio to get the desired results. They give sample workflows as well. I don't think any other software tool does this. They even provide detailed, step-by-step videos for third-party integrations.

I would advise doing the homework upfront and seeing what the full impact is going to be. You should not just look at task automation; you should also look at the full process. That's because when you make a change in one area, you need to consider how that's going to affect another area in your organization. You may get a big benefit in one area, and then all of a sudden, you have to change the way you're doing business to take advantage of that. If you correct a bottleneck in one area, you might still have another area that's a bottleneck, so you need to look at the full process. This is something that we learned in general from our experience. As we were fixing different things and automating different things, there was another bottleneck down the road. We went from doing 10 a minute to 100 a minute, but when we went to the next process, we could only do 10 a minute. It didn't really make a difference unless we fixed that one too. That's why you have to look at the full end-to-end process. I would like them to work on the process mining solution that they have to give us a better picture of the full end-to-end process. That was what was really missing. They do have a process mining solution that you can run up front, but it wasn't very good. We ended up running into things thinking why didn't we know that. If we had a better tool upfront to give us the bigger picture, it would've saved us a lot of time and effort down the road. I would rate it an eight out of 10.

I recommend automating the small processes in the Community Edition. This is the best way to evaluate how scaling would go within your organization. It is also important to fully understand what you want to automate. I also recommend trying the Process Mining feature to make sure you are able to pick up areas of automation within the organization's processes before committing to paying for automation.

We do not yet use the Uipath apps feature or their AI functionality in our automation processes. That said, with AI, we're bringing it in and we're definitely planning to use it in the future. I'd advise new users to make sure you have the controls and governance structures, first and foremost, and you want to make sure those controls are going to be in place and understood before you start deploying licenses to users. I make sure that everything is going to be done and compliant with the audit. As somebody who works in financial services, which is a very heavily regulated industry, that's something that really needs to be kept in mind. You don't want to develop what are essentially just user tools that are not going through the proper controls and treat it like a lightweight software development lifecycle project. You need to make sure those controls are in place, and yet, don't do it too much to the point where it's going to deter the users. At the end of the day, we're not making software, however, we still need to strike that balance. I'd rate the solution at a nine out of ten. Nothing is perfect. I know you UiPath wants to improve the stuff that has not been perfected. I'm not going to say it is a ten out of ten, even though I'm struggling to think of what I don't like. Something that would be very helpful for UiPath is to go back to try to build OCR in StudioX. That would be ideal. Also, being able to implement different types of loops in the Studio would be great. Right now, you can only do a four-loop in a repeating loop. If we could implement wall loops, that would be nice.

We are customers and end-users. While we're using the on-premises deployment, we are open to moving to the cloud. There are a lot of cloud solutions that we already use in our organization. However, with UiPath, we have stayed on-prem out of concern for security. We don't have clarity on if a cloud solution is going to work securely. The other concern is around how we are augmenting the capabilities of core RPA. We know that process mining is going to help us, however, whether process mining is already added into the RPA, do we have any solid use cases that we can start with. I'd rate the solution at an eight out of ten.

We haven’t been using an orchestrator. It’s a bit like having your hands tied behind your back, as you're not using some of the features that are available with that. However, it still provides these workarounds. You are able to still do some really robust work. It's been great. We are using, more or less, the more recent versions of the solution. Before starting with UiPath, a company needs an understanding of the culture at their company. You need to ask if your employees are resistant to change. Certain companies where people are entrenched in their ways, or scared of bots taking their job will be worried. A company needs to lean in and give them an understanding of expectations and pay attention to them before starting. Just pushing it might throw people off. The personalities of people are the biggest factor. I used to come from a lean Six Sigma background. When companies bring in these Six Sigma programs, it's the same thing - resistance. People say “oh, you're the job cutter.” People throw that out as automation, and I say, "Hey, people have been automating since steam engines. It's been consistent. It's just the face has changed a little bit. It finally hopped back onto computers. However, automation has been nonstop." You just have to realign and adjust yourself. You can’t be resistant to change. Change could be a good thing. Not all things are, however, workers need to be rational and think about it. If your company doesn't move faster, adapt quicker, then your company's going to go away, and everyone will be gone. It’s competitive. That's sports. That's business. Overall, from what I've used, and what I've touched, and some of the things I've seen without actually putting my hands on it, I'd give UiPath a nine out of ten. I'm just not the type to give out tens so freely. I haven't gone deep and wide enough to touch everything. From what I've seen before, if you span that out overall, I'd probably put them up in the nine range, personally.

We have everything on-prem in our demo environment and the customers I work with typically have the on-prem offerings as well. I have used UI path apps in our demo environment. I do not have any clients that are using it. We have an AI center in our demo environment, however, I don't have any clients that are using it. I do have a client that's actually in the process of installing it right now and getting it through their governance model. That's as close as it would've come for our customers using the AI center. To those considering UiPath, I would say, just go ahead and do it. RPA is pretty awesome. It's easy to get solutions out. There still needs to be a good bit of work done on the Citizen Developer Model, however, at the same time, as far as getting a team of engineers in there to automate things, if you get good RPA developers, you can get things automated really quickly. People can help you with your standard development life cycle. You just need to jump in. I would rate UiPath solutions at a nine out of ten. The only reason I wouldn't give it a 10 is that, in terms of the installation of the product, sometimes the documentation leaves a lot to be desired. Sometimes it's tough to work through installation issues without actually contacting support. I do wish that was a little bit more streamlined.

The customers that use the on-premises version tend to use the latest version of the solution. While those using the cloud version of the UiPath apps feature are in the UK, the US users are not using that functionality. Mainly most of our focus has always been on RPA and then expansion. From what I've seen, we've mainly been using UiPath. At least on the North American side, it's been relatively new. That's why they aren't using apps yet. We don’t have any clients that are using the solution's AI functionality in their automation program yet. I’ve only played around with it myself. From a road mapping perspective, I'd advise potential new users that your key is the business case. If there's no business case, then this solution doesn't make sense for you to get involved or do anything else. The first part is to really understand the business case. Just to substantiate getting it into the company. Once you have that, that's basically your low-hanging fruit. That said, the key is not to hang everything on one process, not to sit there and bank it, as the concept is a program approach. Over time, it is going to sustain itself. Companies need to be ready to look at a process and think if it's a good idea first. And as you move through the steps, you're basically doing additional checks. As you learn about the process, you're also learning what it's like behind each process and what the value add is. At each stage, users need to ensure that it makes sense to continue. I'd rate the solution at a nine out of ten. While there's always room for improvement, market-wise they are at the top of their game.

The ease of building the automations depends on the process, but overall I would say that UiPath is intuitive. If you understand some basic functions of logical expressions or loop functions, UiPath is intuitive enough to help you build some impressive automations. It is easy to pick up. We have a few people who have completed UiPath Academy courses and are now going for advanced certification. I'm not planning on building any bots on an enterprise scale myself, but I am going through the training as well. UiPath Academy is excellent because it is intuitive. Of course, you have to have some development or SDLC knowledge, but it helps tremendously. You get so much insight on the features. You also get to build a small automation. I dedicated 30 to 40 hours to the trainings and was able to get some knowledge from it. The trainings are even easier for people from accounting, for example. They are used to macros, automations, and file transfers. Conceptually, they are already there and with a tool like UiPath Academy, they can start using the solution. It's important to just stick with it.

My advice is to first build a good team that you can trust. Because great tools are useless if you don't have any builders or people that know how to use the tools. That is what we have been focused on. Also, have very specific support for your team.

It is usually not easy to build a complex automation. The whole process takes about four to six weeks for a complex automation. Most of the time is spent on gathering the requirements. The development itself does not take much time.

My first bit of advice is to ask questions of customers. It is helpful to build a community around you of individuals that you can call upon and just ask questions. In Columbus, we started an intelligent automation user group that brought together customers. It wasn't necessarily UiPath-specific. We talked about different topics and challenges that we are having. For me, that was helpful, especially in terms of governance because I got a lot of good ideas from different people in regard to how I should set up my governance or how to handle certain security issues. I highly recommend connecting with other customers and leveraging the experience and knowledge that they have rather than trying to figure it out on your own. We love UiPath Studio and we have done a little bit with StudioX. We have not had a high level of success with them because our business has been taxed. Trying to find business resources to put towards those efforts has been our biggest hurdle to getting a citizen developer program off the ground.

Start your journey with UiPath. Engage someone from UiPath and have them go through the journey with you.

UiPath has not yet saved costs for our company. However, we're just in the investment phase. That's why I want to do that reporting so that we can see the savings if any. The decisions we make now affect the next 10 to 20 years. Everyone gets too short-term-focused. We need to instead think about where we want to be five years from now and go backward. We need to ask: what are we doing today that's going to make a difference in five years? It's an investment in the future right now. I'd advise those considering the solution to give it a try. It can't hurt. Even if they didn't go forward, the basic principles that are revealed can probably fix other things. Some people just have bad processes. Once you get your processes aligned and make them to the point that they're standardized and understood across the different units using them, it will become easier to automate. I'd rate the solution at an eight out of ten. In order to rate it higher, I need more experience. I've got to learn, got to understand it better. Then I've got to utilize it. Like many software that I've dealt with, there are always three ways to do it, however, there's the best way. I always wish we'd just teach the best way. That said, I understand that you want to make people agile and to understand fully by exploring different ways. When you learn, learning all the different ways is very cumbersome, and yet, better in the long run.

My advice would be to make sure that you have a really good understanding and a really good culture in your company that understands and wants to get on board with automation because it will require that type of mindset of understanding what you're doing before you do it. I would rate it a seven out of ten.

I would definitely recommend it to my colleagues and others. It is very user-friendly. In terms of reducing human error, it is not up to the mark. It detects human errors, but it waits until we place the correct files for processing. For example, when comparing files, a human can detect two almost-similar addresses as the same, but a UiPath bot cannot do that. So, in some cases, it won't work as humans. It cannot decide. It works on predefined rules. Considering its areas of improvement and the cost of certification, I would rate UiPath a nine out of 10.

I started my UiPath journey using the Community Edition, version 2018.4. After I spent some time learning UiPath personally, I began using it full-time in my company. We have several different teams that use UiPath in different ways. First, we have the developers, who do the coding and create the bots. Then, we have the testing team, who ensure that the bots perform correctly. Next, we have the deployment team and after that, there is the support team. My advice for anybody who is implementing UiPath is that they need developers who are good with logic. They should come from a coding background with experience in logic, algorithms, have some knowledge of C#, and have some knowledge of HTML tags. The biggest lesson that I have learned from using UiPath is that technology can be made more efficient by using these tools. UiPath has all of the features that are required to make automation successful. It is currently just ahead of other similar tools on the market and if they continue to add features then it could be the market leader. I would rate this solution an eight out of ten.

The company I work for is a UiPath partner. There have been multiple companies that I've been working with. Two remain the same. I've been using different tools as well. It's been on and off with UiPath. We are not using the latest version of UiPath. The latest version is 2021. We are using 2020. This is due to the fact that the client that I'm working with has a stated policy as to using a minus one version. They believe it could not be a more stable version for any product. At this time, we don't use the SaaS solution or the AI functionality. However, I have enrolled in AI training to better understand it. We do not yet use the automation cloud or UiPath apps either. In terms of employee satisfaction, from the experience I had from interacting with the client and different users, they are happy as well as sad. They are happy in terms of moving away from the mundane work that has been taken off from their hands. They are, however, both sad and afraid that they could lose their job. I'd advise users, if they're a layman, to go with the training. Just start with the training from the UiPath website itself, in the RPA Academy. That is sufficient for anyone to start with. They have all the courses that start right from scratch for every role, be it business analyst, solution or product developer, et cetera. In six months, even starting from scratch, you can excel on this product. With UiPath, it really is possible to optimize so many things. I'd rate the solution at an eight out of ten.

I specifically have been using the community version of UiPath. The company has been using the enterprise version. We do use the Automation Cloud offering. We do not use the SaaS version of the solution. I'd advise users to give it a try. I started my career in UiPath and since then I've been loving it. I became a UiPath MVP as I really enjoy working with the product so much. That automation does not need to be very complex, so you don't need very complex tools to automate any software. Tools like UiPath can do most of your job. I'd rate the solution at a nine out of ten.

We are customers and end-users. At this time, we do not use the AI functionality within UiPath. Our solution is not impacted by anything generating artificial intelligence. The automation speeds up the time to value and we see very quickly how much the solution is able to positively affect the business aspects. It's been really helpful for us overall. The processes have been profitable. I'd advise users to really focus on their input and output size. You'll be able to validate your data. It will help you transform your processes. You just need to figure out where you want to simplify and where you want to maximize value. We've learned how to standardize processes. We've realized how important it is to always try to be very clear when creating automation. I'd rate the solution at a nine out of ten.

Anyone who wants to automate processes should understand the process, its complexity, and the volume of the processing or the number of transactions to be processed. You should do proper analysis before you select the tool and licenses. UiPath provides a lot of benefits and reduces the cost for an organization. It is one of the best tools in the market. The support that we get from UiPath is one of the best, and most of the features provided by UiPath are simply amazing. Initially, people are hesitant to use automation because they don't know what automation can do. Anybody who uses the technology in the right way will get lots of benefits from any technology. Your implementation strategy has to be proper. You should check the feasibility of using a particular technology with existing processes in the organization and the benefits you can get. It helps us in reducing the time, and we are also able to bring more business to the company. By making my processes digital, I'm bringing more revenue to my company. We visit a customer's site and try to find out the processes and pain points. After that, we analyze the entire solution within UiPath and tell the customer about the best solution and what would be the reduction in time as compared to the normal process. I would rate UiPath a nine out of 10.

Apart from the FKUs or the licensing that UiPath provides, if you are implementing an on-premise kind of solution for a client, you have to look at all the things that would be required, such as the virtual machines and the user IDs that the robot might use. We mostly deal with SAP, and if you are using SAP, the robot would have to log into the SAP system to get some data. So, the username that you would create within SAP is also licensed. There are a lot of other costs and related things that you need to focus on. There are a lot of things around UiPath that you need to deal with. I would also advise using best practices while implementing the solution. Every developer has his or her own way of developing automation. A lot of times, we have seen a gap in the understanding and the kind of deliveries that teams do. So, it is very helpful to understand the skills and capabilities of a developer and see how that could impact the final deliveries from an automation perspective. We provide solutions depending on our customers' use cases. For on-premise or cloud deployment, we follow the same sort of process and project plan. There is no huge difference in whether we use cloud automation or on-premise automation. At the end of the day, a robot has to do what is expected as per the objectives. We don't use UiPath's AI functionality in our automation program. So far, we haven't seen any use case where we had to use any sort of intelligence or incorporate any sort of machine learning. We haven't had a necessity for that. We are going to use UiPath apps in a new project that is coming up. We haven't used it so far. We did a PoC to see if we can connect the cloud apps to an on-premise orchestrator and if it is feasible, but that's about it. It is going to be implemented soon. I would rate UiPath a nine out of 10.

The first thing to consider within your organization is whether it's easier to deploy it on-prem or via the cloud version. Then focus on how to structure your development team. It can be either entirely a third-party service provider, or in-house developers, or it could be a hybrid. The third thing to consider is what the cost center will be for RPA implementation in your company. The marketing side of how easily you can build automations with UiPath is a bit exaggerated. You definitely need some programming skills to do very powerful automations with it. But it still provides various levels of development tools, meaning that you could have zero programming experience and still automate some processes in your company. UiPath is definitely the market leader in RPA. The biggest lesson I have learned from using it is to start with the low-hanging fruit, and then go on to more complex stuff.

I have attended a lot of UiPath's webinars. We are in the initial stages of using the AI functionality. The RPA technology is part of our digital transformation. For example, we are doing digital transformation by automating the Salesforce application. They roll out an update every three months. With every update, we see a lot of new features. We are always exploring using those features so we can automate the stuff. Don't rely completely on the UiPath tool to achieve automation. You should have some background and knowledge to understand what can be automated. There isn't a magical algorithm for building robots. You educate the robot on what can be automated. We always rate a product based on other products. I would rate this product as nine and a half out of 10.

We use some third-party tools in conjunction with UiPath. For example, to maintain the code and for versioning control, we use Git. We have two or three years of experience with Git and not only is it compatible with UiPath, but it is also easy to use. My advice for anybody who is implementing UiPath is to start with the documentation. There is a lot of good documentation that includes best practices and plenty of examples. Using the documentation, one can easily learn UiPath. I would rate this solution a nine out of ten.

The length of time it takes to develop and deploy bots for a process depends on its size and complexity. We categorize processes as simple, medium, and complex. Based on how they are classified, we estimate the deployment lifecycle from one month to two months. My advice for anybody who is planning to implement RPA is to begin by doing research on the vendors. You need to speak with each vendor and start planning, but don't think about clients at that moment. Rather, think about yourself. Consider that you want to implement internal automation, and consider the ROI you would garner during the first year or during the second year. Once you choose a vendor, as we did when we chose UiPath, you need to make sure that at the very start of your project, it begins with low-hanging fruit. Don't start with all of the complex processes; start with some simple processes. That's why we have divided ours into three sets of processes. Then, don't think that you will achieve a hundred percent automation because that will never be the case. My thinking is that if you achieve more than 70% automation, that is a very good target. Keep your expectations clear. Another thing to make sure of is that you secure your bot at the workflow level. UiPath provides very good security features that you can use, such as assigning permissions for who can access your workflow. Also in terms of security, be sure that you have all of the required certifications. Once you have implemented some basic processes and you are getting good results, hyper-automation is something I suggest. Start expanding it to different technologies, such as AI. Also, engage all of your employees as much as possible. Start with the community version of the software. Although this review is based on the licensed version, the community edition is free and you can create your bots for free. I always say that even one hour saved because of automation will yield a good return annually, and your results will be very quick. If you keep all of these things in mind then RPA will be fruitful for you. I would rate this solution a nine out of ten.

I do mostly 90% unattended automation. I have created only one attended automation for a client and that was a specifically requested requirement. That was a bit difficult to automate. One piece of advice to everybody who is working in UiPath would be to practice and keep UiPath updated as the technology is growing and it is getting updated frequently. If you do not keep yourself updated for three or four months, you'll be dealing with a completely different tool. Keeping it updated allows for the gradual changes to come in in a way that a user can handle, as opposed to having to re-learn or re-discover the product if you have let updates lapse for months. I'd rate the solution at an eight out of ten.

We are customers and end-users of the solution. We use the enterprise edition of the solution. At the moment we are not using the newest version. It's 2019. It was not my choice to use UiPath. At the beginning of my automation career, it was chosen for me. However, I was able to test other automation software and give my feedback to the employer and UiPath was the winner for me. At that time I was a finance worker. I was not a developer, a professional developer yet. For me, it was the user-friendliness and the way that you could very easily start your adventure with it, and then learn as you go. I have to say that the training packages for UiPath were very good and are enough to make you start working with it. In my experience, I would say that it is the best platform for people who are willing to learn to automate. Also, if you want to use automation software, you have to consider hiring someone who has experience in it. Even though UiPath is so user-friendly and so intuitive, you still need to have a professional who has some experience. It's very important to educate people to make them aware of what the RPA is. To be honest, from my experience, humans are the weakest link here, and people who are submitting, for example, input data for robots, cause the most problems. It is important to invest in the education of people and to raise awareness about RPA. I'd rate the solution at a ten out of ten.

If you are a new organization looking at automation tools and don't have any resources who can easily do the automation, choose UiPath. It is easy and helpful to use. Out of 172 live processes, we are using the AI functionality with Document Understanding in just one process, as of now. UiPath can easily judge the value of the customer document. So, if we can identify good use cases, then we plan to use it more in the future. I would rate UiPath as a nine out of 10.

We have conducted a proof of concept using UiPath's unattended robot capability to enable a self-service chatbot. Specifically, we used the unattended bot to speak with our S3ND (messaging) solution, which is a chatbot. The scheduling was done via APIs and the communication was done through the chatbot. This is something that we have tested, but not yet deployed. We do think that this is an important next step for us to look at. We do not use the Document Understanding and AI Fabric features at this time but we are already testing it in some of our customers to implement them as soon as possible. Another feature that we do not yet use, but we are looking into, is using the AI Center to drag-and-drop machine learning models into RPA workflows. We recently had some discussions with the technical specialists at UiPath about the newer features that are available, and we are looking into arranging for training and webinars that will teach us how to use these new features correctly. Once we have a better understanding of how to implement them, we will begin looking for specific use cases. The biggest lesson that I have learned from UiPath has to do with our customers and their operations. The most difficult and important challenge that we have is changing the mindset of our customers such that it is in line with digital transformation, and this is something that UiPath helps us with. They provide us with everything we need in terms of security, implementation, and high availability. Really trusting that these bots are doing the right thing is the biggest advantage that UiPath provides for us. There are three main points that I would make for anybody who is considering UiPath. The first is the cost, in terms of money. The price of investment is high but the benefits are uncountable. Next, it requires that you look into what you really need, and whether it is all of the features that UiPath offers or just some of them. It is also very important that you look at your infrastructure because it has to be able to handle all of the bots. For example, we know that our processes need a lot of computing power and a lot of memory, so the hardware is important. This has to be built in advance of purchasing the software. The final part is the team, including the developers and architects. It is very important that they all be certified by UiPath. There is training and courses available, they make everything clear, and it includes learning the best practices, frameworks, and models to assure that you're doing everything right. If the company is audited and you are doing it properly then you won't have any headaches. I would rate this solution a nine out of ten.

There is a trial version available. You can go for the trial version first and then buy it and scale it per your needs. Try this tool. Go for it. It's definitely worth a try. If yours is a large organization, try the Community Edition first to get the hang of it. After that, move on to its Enterprise version. What I learned from using UiPath is that there are tools available in the market that can essentially make your life a lot easier. You don't have to worry about doing certain tasks, maintaining them, continuously updating them. Their backups are always available, even if you lose something. They are always easily accessible on any device.

If you want to complete your processes and repetitive tasks quickly with accuracy, then you must think about automation tools. If you are thinking about automation tools, UiPath is one of the best tools that can be used. Other tools are good, but not compared with UiPath. I didn't use UiPath Studio very deeply since I just manage my team. Most of the time, I just observe how my team is working. So, if they can see the data and some other conditions are working well, then we are happy with it. Most companies using UiPath won't see an effect on their pricing, but we have seen a lot of pricing benefits. That is why we are using it. I would rate this solution as nine out of 10 because it has some room for improvement.

Go for it. It is a pretty good tool, which is straightforward and easy to use. They have training in place. Even if you are new to it, you can go ahead and learn to do it. They are bringing in new things. You can automate, integrate, and test things. It is even used for mobile testing. It is pretty good in that case. For most of people's use cases, UiPath will suffice for their use cases. I would rate the solution as an eight (out of 10).

It's a very useful application compared to others. If I look back on the past two or three years, I'm in no doubt that automation, and this application, has helped me to grow my career and expand my mind as well. This is a next-gen application and solution. This is life in the future. Any company that is interested in making its environment digital must use UiPath. And why UiPath? Because other solutions are not equal to UiPath. They don't have as much compatibility. It's easy to learn, easy to manage, and easy to develop. These three points make it fantastic compared to the others. I would particularly advise using it rather than the others. Attended bots are a good thing for small companies. But if you have a large company and you have very long processes, you cannot sit in front of your desktop to see how your process is going. We prefer unattended because people can spend more time on other activities while robots are working on things in the background. That's why we prefer unattended bots in the cloud platform. We are a huge company and we have a lot of processes and we don't have time to watch what is going on.

We are getting into AI now, because we haven't worked with that yet. Right now, we are 100 percent familiar with Orchestrator. We didn't have to install a lot of features with this infrastructure. We just download some activities to work with everything, and it works fine. We don't have a lot of infrastructure for using data. Our first step is getting Orchestrator because we really want to have the entire bank involved in UiPath. The solution is great. It can reduce costs, especially with all that stuff that people do. We have big plans for UiPath going forward. I would rate this solution as 10 (out of 10).

It really depends on what you are looking for and what kind of budget you have. If you already have the Microsoft Office suite, you get Microsoft Power Automate which is also an automation platform. You need to decide how extensively you want to go into the automation journey and whether you are really planning to expand it. If you are planning on going big with Automation, UiPath is the way to go. But if you just want to experiment and try out automation, and you already have Microsoft Office suite, you should try the Power Automate platform.

If you are going to implement UiPath, my advice would be to look at how you are going to gather the requirements and how you're going to manage the requests for UiPath. Also, get some low-hanging fruit first, before going into the complex automations. That way, if you are new, the low-hanging fruits will generate confidence in the solution. Once that kind of confidence is generated, you can move ahead with the complex automations and complex solutions. Go through the UiPath Academy extensively. They provide good training materials that I don't believe are available elsewhere. So I really recommend that. I recently attended a dev conference and I learned a lot about this stuff. I work in a closed environment where I don't have much of an idea of what's going on in RPA. This conference helped me keep in touch with the current trends in RPA and UiPath. I rate UiPath at eight out of 10. For me, that's a very good mark. The two missing points are because there is scope for improvement. Overall, I'm pretty happy with UiPath.

It is the best product. It is an automation product. At the end of the day, it is software development. If there is anything that is important in software development, it is that you have a defined process from beginning to end, from the birth of the idea until it has been put into production and eventually retired. So, you need to have a defined process for different stages in the lifecycle that you need to be in control of. The product somewhat helps us do this with Automation Hub and the Robotic Enterprise Framework, but we are looking forward to even more tools for stuff like that. So far, we are still in the meat and potatoes space. We haven't really gone into the AI or Document Understanding stuff yet. UiPath Portal is good overall for enabling administrators to work with Orchestrator. I have seen a lot of improvements, even in the last six or 12 months. We are learning as we go. For the first few months, we were working in a classic folder. Now, we are adopting modern folders in order to better be able to scale our efforts. UiPath provides granular, role-based access control and management. Right now, that is not so important to us because we do everything unattended. So, we have a couple of service accounts that run everything. However, once we move into attended scenarios, then it's really important that we have that granular control. I know that there are some new features coming out in regards to deploying automatically and elastically, but we haven't looked that much into them. We don't expect them to be a problem. We are looking forward to doing attended robots, but that will probably be in the second half of this year when we start looking into that. For the size of our company, we started fairly big. We went all in, buying licenses, consultancy hours, etc. We have spent a lot of money this first year. I would probably advise someone to start small but still be ambitious. Do a lot of PoCs and see how it fits into your organization. There needs to be a lot of disciplines surrounding it, e.g., if you just stay with five or 10 automations, then things are good. However, once you build 100, you start running into maintenance problems and things like that, so there needs to be a discipline. You don't need to spend a million dollars to sort of get off the ground, so I would advise people to start small. I would rate this solution as an eight (out of 10).

For the beginner the UiPath Academy has a lot of training available. It's important to go through the training. After the training you can easily work on any project in UiPath. So first of all, follow the training. For intermediate-level users, UiPath is the correct solution. These users just need to keep up to date, day by day, because the UiPath team is rapidly updating the features. The Picture in Picture functionality for attended automations is a new feature. Up until now we have not used PiP, but we have some use cases for an internal project we are doing and are looking into it for the future. We are using UiPath Automation Cloud, but we have not yet migrated our on-premises UiPath instance to it. We are thinking about the on-premise because it fully depends on our own enterprise. If we go to the cloud, we will be able to collaborate better with our team and what others, because it is "public."

The solution is single sign-on, so the authentication is done for us, because it is difficult to remember all our passwords. We have a ServiceNow ticketing tool for reporting issues related to UiPath. UiPath is very good for developing web-based applications, especially for SAP and the web. For these two applications, you can go with UiPath without any doubts. I would rate this solution as an eight (out of 10).

We use UiPath Assistant to run processes about 10 percent of the time. Most of the time, we are using Orchestrator. UiPath releases new features every 15 days to a month. They have already come up with AI and machine learning. If scanned documents are coming in for some of the work, we are also using Python language for this. If you already have a technical team, then you can ask them to look into UiPath Academy. If they have basic knowledge of programming or coding, then even in seven days, they can easily learn UiPath and start applying it in their organization. You don't need to hire outside developers. Overall, the solution is a nine (out of 10).

One of the newest upgrades that we had was in respect to payments getting added. New functionalities are getting added. They also work on the feedback that they get from interviews conducted by sites, like IT Central Station, who take unbiased reviews. They work off this feedback, which is why they are upgrading their products out in the market. I haven't used the AI Fabric solution as of yet because we don't have a business case for it as of now. If you are ready with your own business process that you want to get automated, then I would recommend UiPath for its intuitiveness. You should consider the intuitiveness of the UiPath as one of the parameters in your solution decision. For example, if you have the business process ready, then that is half the job done. The other half will be taken care of by your RPA developers or solution architect. So, if you are using UiPath, the learning curve is very small. You don't need to invest a lot of time. They have their UiPath Academy learning website, where you can go in as well as ask your team members to learn based on their roles. There are different series of educational videos based on job roles and how that particular role should look at UiPath as a solution. For example, as a manager, if I'm going in and looking into the UiPath, I do not want to be bothered about how I'm going to pull in activities and develop the automation bot. As a manager, I am going into Orchestrator to see how many bots have executed successfully or failed. If I was a solution architect, then I need to know how to design the service lines if they are located in different geographical regions. Everybody is really looking for some kind of solution that eases our life since we are working from home. It takes a toll when we are working from home. When we have these RPA bots coming to our rescue, then it makes a difference in our day-to-day life. Then, we can spend more time with our loved ones rather than spending more time in front of our laptop screens. I would like to rate it as nine (out of 10) because I believe no one is perfect and all the bots are being developed by humans. Going forward, I read on a forum that UiPath is developing an AI feature where the bot will autoheal itself. Once the autohealing feature is implemented, I would rate the solution as 10 (out of 10) because there would be no manual intervention.

For developing our attended automation, we began by coding the bot to our requirements, and then made modifications to it for attended automation. My advice for anybody who is considering UiPath is to be sure of what your needs are regarding an RPA product. If you're looking for something very small-scale, very easy, then there are a lot of options. But if you're looking for a long-term, feature-rich solution, which has access to third-party integrations, then choose UiPath. You will require a development team, at least to some level. UiPath is now simpler with the Studio X products, but in the past, it was a bit more challenging to dive deep into UiPath directly. It required some training but now, things have definitely improved. One of the major lessons that I have learned from using UiPath is to make sure that everything is documented well. There is a lot that needs to be tested before bots are put into production because a lot of things that work on your local machine may not work on another. It can vary from machine to machine and where something works on one, a change in environment for another may cause it to fail. This means that you should change from machine to machine during the testing phase. Overall, I feel as if now UiPath is on the right path with its competitors. It is a very good long-term solution. I would rate UiPath a nine out of ten.

UiPath is known for a certain number of products, and the role of our team is to use all of them. On the topic of the UiPath Cloud, the new products that they have come out with, like the possibility to create your own applications for your internal customers, or host certain data services from the same platform, were things that were not available in the past. These capabilities are useful. In general, all of their products are pretty important for us. For UiPath as a company, we like the availability that they have and the fact that we can try and test all of their products beforehand, without paying. For a relatively small project such as ours, or even for a big company, it's pretty useful to be able to access this type of information and not be burdened with extra budget requirements. This is a product that I recommend because the starting point is completely free. That's one of the great points of UiPath. My advice is that when it comes to scaling the project, it's really important to clearly set up goals and expectations. Otherwise, there will be an eternal loop of PoCs and non-viable products. I would rate this solution an eight out of ten.

We haven't found any problems with UiPath. It is working great. It's a great tool. I would suggest that everyone go with a UiPath because it has helped us a lot.

We can learn from UiPath Academy. I would rate the solution as a nine (out of 10).

Definitely to try and get as many teams involved as possible to open up the conversation about RPA within the business. It works best when you've got lots of teams who have an understanding of RPA and how it works. They can come to you with their potential projects and you can filter through them and see which ones are going to be the most helpful. It's hard if no one else in the business really knows RPA or how it works, or if there's a bit of a wall there. It's important to introduce RPA to as many different teams as possible and to encourage people to get involved, think about the processes that they do in it, and try to identify what can be helpful. It's important to keep RPA close to the applications and the IT teams because if you're using RPA or UiPath you're going to need to be able to be speaking to your team who need permissions or admin privileges, or you need apps to be updated. It's important if you're going to put it in, have it as close to apps and development as possible. It's a case of understanding that it's not a case of trying to get everything automated that you possibly can. The goal shouldn't just be to automate everything. If you've got a process and you can do 99% of it automated but you can't automate the last 1%, you can but it's going to be really fairly inefficient. Understand that it's fine for a process to have some bits that are automated, some of which are done by a person. The hybrid workforce, rather than going into the strategy of just automating everything is ideal. I've learned that trying to find that balance and getting that communication between the two is good. I would rate UiPath a nine out of ten.

I would rate UiPath an eight out of ten. It feels like nothing deserves a 10, and I highly recommend every organization has a handle on RPA. There are still a huge amount of features we're still yet to explore.

My advice is to think about it very carefully and know exactly what everybody is doing every day in the office, the little bits and pieces. Really look at that seriously, because there are so many things that we do in a software environment that are very amenable to automation, and it saves a lot of time. Think very carefully about the particular needs of your office and look into it, because it can save you a lot of money. It's clear that this is the future.

I think the platform is very good. Have a good consultant advise you on the processes of automations: How to build the use case and business case. You will need a bit of knowledge around RPA and business processes to be able to have a successful implementation. Have a stronger technical partner tool to help with developing the robot, making adjustments, testing, etc. Testing is very important. It is important that you allocate resources for testing. Robots can do things in a different manner than we can and more efficiently. We have to be creative and think of processes, even if only part of them are repetitive, that we can automate and a human can work with the robot. Then, the overall the process is improved and our experience as humans is a lot better. I would this solution a 10 out of 10 because they are very good at what they do. It's very important that you understand what the solution can do and its limitations. However, for this type of product, I think they are the best.

Start with processes that happen over and over every day. Something that you have to do, like data entry, whatever it is. Peel back the onion, then look and see how you can automate some of that through a tool. You have to look at what your processes are and understand how those are getting done today. Maybe even share that information with somebody outside your area, because people from the outside might say, "Well, why don't you do it this way?" Because you've lived it so long, you don't even know why you wouldn't nor do you know the questions to ask. Therefore, look at your base processes that you're doing day in, day out and see how you might be able to automate any aspect of those that doesn't require human thinking. I'm sure you will uncover many things. It is a learning process for everyone, but I thought it was a very fast track learning. Sometimes, you think, "Well, this is going to take six months," and it didn't. In a very short time, we were seeing samples of what we were going to get. Therefore, I was very impressed with the amount of resource time that it took. It was beyond what I expected. Some tools we are working on will reduce the purchase order build, but we haven't implemented that yet. That's a whole other project that we're working on with them, and that piece goes into procurement. It is very doable. I was probably fairly skeptical, but once we started thinking about it, it became very clear that this would be just a slam dunk. You have to open up your mind to it, but it was something that when they said, "Well, we want to use some robotics." The fear is you're going to take my staff away. There are some cases of that, but it is not so bad. I don't have to worry about the robot taking days off, getting sick, having a mother in the hospital and needing to be with them. I don't have to pay it scale. I just don't have to do any of those things. Now, the robot can't automatically think outside the box, but sometimes it can depending on the questions I ask it. Everybody just needs to take a breath step back, and say, "Yeah, maybe it can replace this." However, that doesn't mean we won't use this resource in another way. I would rate this solution a 10 out of 10. I'm not the type of person who just gives a rating of 10 all the time, but this solution has just been a phenomenal tool for us.

So far, the experience has been excellent. I would rate the solution 10 out of 10, but we haven't finished the implementation. Look internally what your needs are. Try to identify what you could improve with software robots, ensuring these needs are clearly identified and the product is fit for purpose. Also, you should make sure there will be buy-in in the organization, so people will actually use the product.

UiPath is the most amazing RPA solution available in the market. Certainly, this gets plus points when it comes to feature versus cost ratio. Therefore, I would highly recommend UiPath because it comes with more stability and reliability than other solutions. There are some features like different types of recorders. For example, Citrix and desktop are the variants we have in UiPath to solve our problems. Other than the issues with technical support, I think that UiPath is a complete package for automating solutions in a rapid and fast environment.

I think that for the most part, this product has all of the required features.

Overall, I would recommend UiPath. My advice for anybody who is considering this solution is to look at their website because it is very helpful and it can help them to make a decision about implementing it or not. I would rate this solution an eight out of ten.

I can't wait to have automation with every human in portable devices. It will automate not just the business process but daily life activities.

My advice for anybody who is considering this solution is to use the free Community version extensively and make use of the community forums. The RPA Academy is also a great resource, a one-stop shop to get educated in using UiPath and it's also free. Once your organization is ready to scale and go beyond free, UiPath offers reasonable pricing.

UiPath is a very complete software and allows you to make different robots depending on the system. Its main function is to save time and automate project management, which it does very well. It allows you to remove software and in this way, you will return to Create them but automated so that artificial intelligence (AI) can work correctly. It collaborates with employees. It is possible to automate, for example, Excel files so that the forms can be filled automatically and not manually. Overall, I am very happy and I recommend it.

So far, I highly recommend UiPath. They are constantly introducing new tools and features and they all seem to provide extra benefit.

I am proud to have UiPath on my resume as it is valuable for career growth. I plan to continue as a UiPath developer.