For two years, I have focused on automating workflows related to processing documents in formats like PDF, Excel, and CSV. Using the document understanding feature, we have handled forecast orders and purchase order invoices.

If you use input files like Excel, PDF, and CSV, we can automate file validation, such as checking data accuracy, format compliance, or missing information. It's integrated with Boomi, so after the files are validated, they're sent to Boomi for further processing.

Boomi provides us with the RTF file, and we use UiPath to validate its contents and correctness. It automates the process of converting the RTF file into an Excel file. Another process is remittance, where we can get files from clients, validate them, and submit them to the credit managers for correction.

UiPath reduces human error by eliminating manual work and intervention. Some human intervention is still necessary, but it has been reduced. Realizing UiPath's benefits takes some time because you may have some issues after the initial deployment. The UiPath Academy was helpful. I took some courses and achieved developer certificates. I'm still learning.

It hasn't saved time in my work because I'm still spending a lot of time learning the software. It was new, so learning and implementing those things in my work takes time.

My favorite feature is Document Understanding. I haven't used most of the new features, such as AI-enhanced document processing and process mining. The document understanding feature is especially valuable because I can use it to extract and process invoice data efficiently. It enables the quick and accurate handling of structured and unstructured data.

The flexibility to work with templates and machine learning models for document extraction has been helpful when dealing with various invoice formats and forecast orders. Data extraction from PDF has been smooth, especially with UiPath's capability to handle scanned documents using OCR and AI-based models.

The taxonomy manager lets you define the structure and categorize data from multiple document types. AI center integration allows continuous improvement in document extraction accuracy by training models based on historical data. I have utilized AI and machine learning models in UiPath specifically for processing complex PDF and Excel documents.

UiPath's AI capabilities, such as pre-trained invoices and receipts models, have effectively extracted structured and unstructured documents. For example, when processing purchase orders, the AI model identified key fields, such as invoice numbers, dates, line items, and currency details, with high accuracy. I have found the machine learning models to be especially useful when working with documents that have different formats. In some cases, additional training or validation was required to fine-tune the models for complex or irregular documents. Overall, AI models and document understanding are my favorite features.

UiPath is highly user-friendly because it has drag-and-drop functionality to design and develop complex workflows without much coding knowledge. This has been particularly beneficial when working with different document formats. UiPath's built-in tools and integration capabilities simplify the automation process, leading to greater efficiency.

We have end-to-end automation and integration with other applications. For example, we have portal automation that's end-to-end. We use it to log in to the website and sign in to different accounts. It enters the CAPTCHA, downloads the files, and logs out. It can complete the automation without human intervention.

UiPath has many resources online. We use its academy and online documentation. If we face any challenges, we can find an answer on the forum or one of these resources. I've never had a problem finding solutions to problems. They have the best resources.

I would love more integration with Third-Party applications. Expanding the library of pre-built, plug-and-play connectors to include more industry-specific applications.

I have worked with UiPath for two years.

I've never experienced lagging or crashing with UiPath. The app has never given me trouble.

Installing the community version of UiPath was easy and only took five to ten minutes.

I am using the free community version. The enterprise version is obviously a little expensive.

I piloted the introduction of UiPath to my team with two projects. The first, domain monitoring, automated our ten-plus Pega applications' quarterly security and health checks. We designed an architecture that could be mapped across all domains, streamlining the process to run weekly instead of quarterly. This provided timely reports on application health via Webex. The second project was a more straightforward test suite automation for another UI-based application. These two successful pilot projects showcased the capabilities of UiPath, with the domain monitoring still in use today.

Building automation with UiPath is straightforward, but it's essential to be familiar with the target application and have a basic understanding of coding and if-else statements. This knowledge will help troubleshoot any unexpected errors. Overall, I'd rate the ease of building automation with UiPath an eight out of ten.

While working on the projects, we used two versions of UiPath: the enterprise and cloud versions. The orchestrator that comes with the enterprise version is different from the cloud version. The cloud version had better end-to-end automation, and the ease of use and accessibility were superior to those of the enterprise orchestrator, which is the on-premise version of UiPath. Although the enterprise version lacks a few features, the cloud version provides a complete solution.

I was impressed by UiPath's user community. We used an open-source library that someone else had built and generously shared with the UiPath community. It ideally suited our needs. The user community is also very responsive, and we readily receive answers to our questions.

We didn't see immediate benefits from UiPath because it was a new tool I was piloting. We had to prove to upper management that it saved significant time, and we eventually eliminated manual testing. It took until the project's end to demonstrate this, as management focuses on results, not processes. However, other teams adopted UiPath after completion, so benefits appeared after two or three months. It took time to get people on board, but they eventually embraced the idea.

UiPath has significantly improved our efficiency by automating domain and application monitoring, saving valuable time and working hours. These tasks were previously quite intensive and repetitive, demanding considerable focus and effort from our employees. With UiPath handling these processes, we've freed up our workforce to take on more engaging and strategic responsibilities.

My favorite aspect of UiPath is its user-friendly interface, as it's a no-code, low-code platform that eliminates the need for extensive coding. Its drag-and-drop functionality, coupled with UiPath's comprehensive library suite, simplifies automation tasks. For instance, the Microsoft Outlook and SharePoint libraries allow seamless integration with those platforms, streamlining processes like connecting to SharePoint in Microsoft 365. In essence, the combination of UiPath's robust infrastructure and versatile tools significantly enhances its usability and effectiveness.

I found the UiPath Academy courses to be a bit rigid in their curriculum. It was more beneficial for me to learn from the forums and YouTube videos. Their courses were tailored to particular roles, with a course on UiPath in data science being heavily focused on Excel. While it was a well-structured course, it didn't align with my job's limited use of Excel. Overall, their courses are well-built, but I found YouTube a more suitable learning platform for my needs.

UiPath Studio provides comprehensive tools and libraries for building automation, but it lacks a built-in feature to generate consolidated reports after automation runs, detailing successes, failures, and operational features. This absence of detailed logging information makes it difficult to troubleshoot issues and identify whether the problem lies within the application or the automation itself. While UiPath's orchestrator website provides some information, it's insufficient for demonstrating automation runs and accomplished features to stakeholders. Although a future release may address this, the lack of robust reporting capabilities remains a significant area for improvement. Additionally, UiPath's diverse suite of licenses can confuse end-users, making it challenging to determine the most suitable option. While the company has improved features, the increased number of licenses creates a knowledge gap between what's available and user understanding. Clearer explanations of each license would simplify decision-making for potential users and streamline adoption.

I have been using UiPath for one year.

Once we have the licensed version of UiPath, we don't anticipate issues with caching. We were using the 2021 Studio version because it was stable. Although the UiPath team suggested upgrading, I'm not certain about the reasons. I can't comment on the latest models, but the 2021 version was reliable.

The scalability of UiPath depends on the number of licenses. To deploy our automation, we need to utilize robots responsible for executing the automation we've built in a user-less environment. Scalability is directly proportional to the number of robots we have, which is, in turn, determined by the number of licenses. Therefore, more licenses translate to greater scalability.

The initial onboarding of UiPath was straightforward, but the only challenge we encountered was connecting UiPath Studio to the Orchestrator. UiPath Studio is where automations are built, while the Orchestrator is where they are deployed and run. This required some back-and-forth with the product team and my technical lead. However, this issue only arises during the initial setup. Once someone familiar with the process sets it up, it becomes easier. There were some challenges connecting and deploying the first automation, specifically between the Orchestrator and Studio.

Three people were involved in the deployment: my technical lead, who liaised with the product team to discuss progress and challenges; myself, responsible for building and deploying the automation; and one of my junior colleagues, who assisted me. In short, we had a three-person team.

We used UiPath and built and deployed that project, which ran successfully for approximately two quarters while I was away. However, the cost and licensing associated with UiPath became an issue. The license we were using offered excellent features specific to our needs, but it didn't provide much beyond that. It didn't make sense to continue spending much money on UiPath, even though it saved us time and money. The savings were essentially being reinvested back into purchasing the UiPath license. While UiPath licenses offer valuable features, they are expensive. For our single-use case, investing that much wasn't justifiable. We switched to Selenium, an open-source automation tool. Although it took additional time to deploy the same solution with Selenium, and it might not be a 100 percent match in functionality, it allowed us to save on costs.

The cost of UiPath is justified for organizations with many use cases but not for one or two use cases.

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.

We use the tool for robotic process automation to automate mundane business processes prone to human error.

Some of UiPath's best features are its ability to interact well with applications and its less proneness to errors. It allows us to implement end-to-end automation, which is very important for our organization since we have many time-consuming job runs.

The tool has improved our organization by reducing operational costs through process automation and cutting FTEs. We can do more regression testing for test automation, leading to better products. It's helped minimize our on-premises footprint to some extent and aided organizational restructuring.

We've used the academy courses, which are good for beginners and advanced users. UiPath has sped up digital transformation, allowing quick fixes without building entire new solutions. It reduces human errors by 60-70 percent and saves us around 2500 hours.

UiPath is pretty easy to use for small—and medium-scale automation. However, maintaining the code becomes a bit more difficult when building large-scale, enterprise-level automation. Areas for improvement include versioning for collaborative projects and reporting features currently lacking.

I have been using the product for six years.

As for stability, I'd rate it as six out of ten. Once a project is built, we face many issues, and we often have to go back to UiPath. So, in my opinion, stability could be improved.

My company has 10-15 users. Based on my experience, I would say UiPath is a scalable solution. I'd rate its scalability around seven or eight out of ten.

The user community for UiPath is great. We can ask about any issues we have on the community forum and usually get them resolved. Regarding technical support, it's amazing that they respond quickly. However, their level one engineer could be better educated on the tool before moving to level two support.

We previously used an open-source Java Selenium solution but switched to UiPath for better security and platform capabilities.

We have the tool deployed in the cloud version. The deployment process was straightforward—it was pretty easy, mostly just drag and drop. Because of the number of projects we have, the initial deployment took days to months.

We use UiPath in multiple locations globally, including the US and India. The solution requires maintenance, particularly from a coding perspective.

I'd estimate UiPath has helped us save around 10-15 percent in costs.

UiPath is a pretty expensive tool compared to what the market offers, including open-source alternatives that can do similar things.

Overall, I would recommend UiPath to other users. The main reasons I like it and would recommend it are that it's very user-interactive and its capabilities are really good.

On a scale from one to ten, I'd rate it overall around eight.

We use UiPath to automate ERP and CRM portal processes, integrate them with SAP and various external applications, gather data, and perform functions to generate reports. UiPath enables us to carry out numerous activities, and its usage is not limited to a single variable but rather multiple ones.

UiPath's primary goal is to enhance the scalability and accuracy of daily tasks within any organization. The core concept behind UiPath is to boost productivity by mimicking human actions, automating repetitive tasks and freeing up time for individuals to focus on other activities.

Compared to other RPA tools in the market, such as Blue Prism, Automation Anywhere, Worksoft Certify for automation testing, and Selenium, which uses high-level coding, UiPath is a low-to-no-code automation platform. This makes it user-friendly and provides a comprehensive library built into the tool, enabling developers to automate various tasks and processes efficiently.

UiPath enables end-to-end automation. A negative side of this automation is that it replaces a human already doing that specific job. A human previously did any automation implemented through UiPath. However, by automating through UiPath, we free up that employee's bandwidth, enabling them to focus on other tasks or housekeeping activities instead of repeatedly performing the same repetitive task.

The UiPath user community is extremely active and knowledgeable.

I recall a situation where a business had to generate quarterly reports. Before automation, they could only produce 200 to 300 reports per quarter. However, after implementing bots, productivity increased to around 900 reports. Additionally, UiPath's logic query feature allows for Excel calculations to be done in a fraction of a second, a task that would typically take a human around an hour. Many bots have reduced business processing times from one hour to five minutes, and tasks that used to take one to two hours are now completed in five to ten minutes with high accuracy.

To learn UiPath effectively, we need a reliable source that provides accurate information. UiPath Academy serves as the ideal platform for this purpose—additionally, companies value certification as proof of UiPath proficiency. If we aim to become UiPath certified, UiPath Academy is our best option, as its courses are specifically designed to help us succeed in the certification exam. While other platforms like Udemy or Coursera offer UiPath courses, we may need more preparation for the certification, which involves a mix of theoretical, conceptual, and practical questions. We can learn practical skills elsewhere, but UiPath Academy is the best resource for mastering the theoretical and conceptual knowledge required for certification.

UiPath helps reduce the cost of digital transformation by around 30 percent.

UiPath helps reduce human error by 95 to 99 percent. The bot doesn't make mistakes. Because of the high accuracy, we started with ten bots and now use 200 bots.

A UiPath bot can save one full-time employee's time per year.

UiPath is highly versatile, offering multiple automation options for various applications. For example, UiPath can automate email, PDF invoices, images, Excel documents, and websites. This flexibility extends to its OCR feature, enabling the automation of any invoice or PDF invoice. Secondly, UiPath's exception-handling capabilities greatly simplify the automation process. Lastly, UiPath utilizes minimal code, making it a low-code or no-code platform. Consequently, even individuals with limited programming knowledge can automate tasks using UiPath after completing a basic course.

The Excel operation needs some modifications. Image processing is also crucial. For example, if the image is clear, UiPath can easily read it. If the image needs clarification, UiPath can't read the object easily. To some extent, Excel automation, especially handling macros, needs improvement. UiPath needs a comprehensive feature set for automating Excel and has limited options. In some cases, we must use macro-enabled Excel files. Therefore, Excel automation and OCR require enhancements.

I have been using UiPath for four years.

Bots rely on numerous third-party applications, and several factors can impact their performance, including the virtual machine's capabilities and the responsiveness of the applications the bot interacts with. Therefore, UiPath isn't solely responsible for failures; issues could stem from your server or the third-party applications UiPath connects with. UiPath's stability is rated at eight point five out of ten.

I'm a delivery lead. As organizations grow, they add technology and features to their ERP applications. This requires frequent modifications to automation bots developed for specific functions. UiPath's scalability feature allows me to implement change requests easily at any time. Instead of extensive development, I can lift and test the desired changes within the existing code. UiPath also incorporates AI/ML features, which are in high demand in this generation. This addition of AI/ML capabilities will likely enhance UiPath's scalability.

I would rate the scalability of UiPath seven out of ten.

I used Worksoft Certify for automation testing, but it doesn't compare to UiPath due to its limited features. Exception handling is not well-defined in Worksoft Certify, and I find flowchart programming much more complex compared to UiPath. In many ways, UiPath is superior to Worksoft Certify, which has many limitations.

The initial deployment is straightforward because the UiPath team will be available throughout the process, participating in calls and meetings to provide comprehensive assistance with the deployment.

The deployment takes one to two days, provided all approvals are in place. Approximately 12 people are involved, including five from our team, as well as members of the server and networking teams.

We implemented it in-house with the help of UiPath.

I don't handle the costing aspect as it's not within my scope. However, I understand that initially, businesses or clients might perceive UiPath as expensive. While this is true to some extent, the features and flexibility UiPath provides often lead clients to realize its value in the long run.

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.

UiPath is our platform for automating tasks and processes within our manufacturing environment, to boost productivity and streamline overall operations.

UiPath utilizes a hybrid deployment model, where our virtual machines reside in a federated cloud environment, while the UiPath orchestration engine itself remains on-premises.

UiPath stands out for its user-friendly development environment and minimal programming requirements. Building automation with UiPath is a breeze, making it a strong selling point for those looking for an easy-to-use RPA tool.

UiPath offers end-to-end automation, but there's a catch: it requires full access and control within the target environment. This means UiPath needs security permissions to interact with and potentially run other applications, which can be a challenge to set up. While achieving end-to-end automation is valuable, this access requirement can be a hurdle.

UiPath has reduced our on-prem footprint, freeing up resources that were previously dedicated to maintaining that infrastructure. These resources can now be used for other tasks.

We saw the benefits of UiPath immediately upon deployment.

The UiPath user community has been a valuable resource for quickly solving problems. By interacting with other users, we've been able to share insights and find solutions to specific programming issues.

We leverage UiPath Academy courses to prepare developers for certification exams. These courses serve a dual purpose: getting new developers acclimated to the platform and providing foundational knowledge for citizen developers who want to learn UiPath quickly.

UiPath accelerates our digital transformation, but integrating legacy systems can be a hurdle. While UiPath excels once deployed, the process of granting it access to legacy data for proper functioning can be time-consuming in our environment. This may be specific to our setup, but it's worth considering nonetheless.

UiPath significantly reduces human error by automating tasks and allowing for faster turnaround. This means that even if users make mistakes in their submissions, UiPath can quickly catch them and provide feedback so the user can fix the error and resubmit the issue.

UiPath has helped free up our employee's time for other projects.

UiPath significantly reduces our transaction processing costs. Previously, transactions took days to complete, but now they're done in minutes. This efficiency translates directly to cost savings, and it's just one example of how UiPath can optimize internet-based processes by streamlining workflows and minimizing processing time.

A key feature of this solution is its built-in VM orchestration capabilities, allowing us to manage virtual machines without additional setup. This includes basic functionalities like starting and stopping VMs, as well as integrating queues into our orchestration workflows. Additionally, we can leverage built-in Insight reports to extract transaction and volume data for analysis.

The biggest hurdle in UiPath Academy courses has been completing projects, especially for advanced certifications like RPA developer. With everyone juggling work and deadlines, dedicating significant time to capstone projects becomes difficult, leading to course completion struggles for many.

UiPath could improve its services and account management. Specifically, greater interaction with the services team would be beneficial to understand their capabilities better. This could involve trial runs where the services team demonstrates the value they can provide before being engaged. Additionally, providing sample automation, such as starter automation for SAP workflows, would give users and teams a starting point to build upon instead of starting from scratch.

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

Our daily automation runs smoothly, and weekly ones seem stable for users. However, I get frequent alerts about downtime, potentially due to VM configuration issues. Since we have multiple VMs and I might receive alerts for others, some get unintentionally ignored without impacting functionality.

We've found UiPath easy to scale by adding virtual machines to handle more automation. As we expand our automation to support more users and environments, we anticipate needing another bot. Adding a new bot to UiPath is straightforward - we can simply assign an existing automation to the new bot and keep it running. The only additional cost is for the new VM. Overall, UiPath scalability has been positive for us.

The quality and speed of the answers from UiPath technical support are good. We have a good support-level contract with UiPath that gives us enterprise-level support.

I would rate UiPath eight out of ten. It is a good solution but it wasn't made for ambiguity.

We primarily focused on UiPath for automating desk-level processes without initially considering other solutions. However, before implementing any automation, we assess its suitability for UiPath and whether a workflow tool like ServiceNow might be a better fit. In essence, we compare these two technologies for workflow automation needs.

UiPath took longer to use at first due to the learning curve, but now we're more experienced with the software, so creating automation is a breeze.

UiPath requires annual maintenance, which involves upgrading to the latest version. This process includes migrating virtual machines and thoroughly testing existing automation to confirm their functionality after the upgrade.

New UiPath users should consider two main factors: process type and system compatibility. UiPath excels at automating well-defined, repeatable processes that can be observed and coded. It's ideal for desk-level tasks and works well with Microsoft applications and many browser-based systems like SAP. However, custom systems may require additional effort as pre-built UiPath packages might not be available. By focusing on deterministic processes and compatible systems, new users can identify the best use cases for UiPath.

We have an online report, and our management tasked me with recreating it, but they don't allow bots to create things on the website. I'm responsible for the automation and engineering work, and they wanted me to evaluate the performance of our systems and solar panels. I need to go to the manufacturer's website and download the monthly report corresponding to our factory site.

Each month, I need to go to the site, get their readings, and create a report. It's a repetitive task that takes about four or five hours. UiPath enables me to automate the finance side of the report.

Generating all these market analyses and data reports from various websites can be time-consuming. It might require a whole team with its own manager to check and update the docs. However, when UiPath came into play, we could automate a lot of that work from different platforms. That was the start of a digital transformation at our company. It saves about eight hours per report.

UiPath decreases human error. A lot of the reporting on product quality was done through manual data entry into the database system. There is potential for human error. Now, we can a lot of that information automatically and perform the data analysis with UiPath. Since we no longer need a designated person to do the data analysis, we can save around $200 to $300 monthly.

UiPath is easy to use and learn. With some experience in automation, I could learn the solution in three or four hours. It's easier to build automations in UiPath compared to other tools. UiPath has a feature that allows you to build automations quickly. You can build your workflow in under 10 minutes. In UiPath Studio, you can do browser automation by recording it. You can set up flows where you click through the buttons on a website. For example, there's a button where you have to click to verify that you're human. That's something you can add to the flow.

Having a workflow is beneficial. At our monthly meetings, we rectified the revenue generation, etc. We analyzed all these systems' performance and costs to create a plan and saved a lot of money doing that.

We're developing a use case for automated communications mining using Salesforce for one of our teams. It will be helpful, but we haven't implemented it yet. We have several reports and a script to perform this automatically. We will rate the responses from our team members and the outside groups we are using.

The UiPath community is very helpful. When I started using UiPath, I had no clue about it, so I watched a few videos and learned how to do most of the integrations. I also reached out to some colleagues on LinkedIn who directed me to the Sri Lankan user community. They were amazing.

I would love to see UiPath create a reporting application that you could deploy on the side and feed data directly into it. That would be an amazing tool to have. Microsoft has this data migration interface, so if you create an automation, it checks everything going into it.

I tried UiPath a couple of years back for another project and worked with it for about a year and a half. I also worked with it more recently, and the experience is different.

We had some performance issues in the first few weeks. Apart from that, UiPath has been running okay.

The cloud component of UiPath makes it scalable.

I rate UiPath support seven out of 10. You can contact enterprise support. They're always ready to receive our calls and provide recommendations.

We previously used Microsoft Power Automate. Since we are using Microsoft ERP and CRM systems, all of our automation systems need to be compatible with Microsoft. We could use Power Automate for free, so it made sense to stick with one vendor.

UiPath is easier to understand and use because we can record actions, and it has an amazing support community. It is also competitive in terms of cost. If you are sending information to databases with Power Automate, you need some subscriptions to PowerApps and Power BI. It costs you about a hundred dollars to get started. You can download and use UiPath Studio for free.

Compared to our older platforms, UiPath is easy to install and integrate. On day one, you can deploy it to your system in a few minutes. Our previous solution required more infrastructure to do the automation. UiPath has UiPath Studio, so you can play the flow and record all your inputs. The main advantage is that you can build a solution in minutes. It's effortless to get started.

UiPath is reasonably priced.

I rate UiPath eight out of 10.

Our UiPath automations primarily focus on web applications but also include tasks like extracting data from Excel for queuing, automating transactional processes and desktop applications, and even populating CRM and ERP systems with data extracted from PDFs.

The recording feature allows us to capture a manual process as a starting point for automation. We can then customize the recording based on the specific transaction, including how often variables need to be initialized and whether data needs to be passed between workflows. This way, the recording serves as a foundation to automate the core functionality and build new processes within the framework.

UiPath offers end-to-end automation for many applications, but I encountered challenges with NetSuite, an ERP web app. The connection kept failing due to NetSuite's slow loading times. While UiPath has built-in connectors for these situations, the lag prevented interaction with the NetSuite interface entirely.

The UiPath user community is a large and active resource for users of all levels. With community pages dedicated to specific countries, users can easily find information relevant to their needs. The community fosters knowledge sharing and learning, allowing users to stay up-to-date on the latest UiPath features. Beyond traditional documentation, users can access demos and connect with motivated developers to enhance their skills.

UiPath, a market leader in automation solutions, comes with a higher price tag due to its wider range of features. However, the return on investment takes time as initial costs cover development team setup and licenses. It can take between six months to a year to determine if the number of automated processes justifies the cost savings for our customers.

UiPath reduces our physical infrastructure needs by eliminating server management, maintenance, and database backups that are handled by the cloud provider. On-premises deployments require a disaster recovery plan for database backups and regular data maintenance to prevent performance issues, which are burdens eliminated by cloud-based UiPath.

I honed my skills through UiPath Academy courses. Their learning portal proved valuable for exploring new features and pursuing certifications.

UiPath is a helpful tool for digital transformation, but its applications vary depending on an organization's needs. While many companies focus on automating tasks with PDFs like purchase orders or legal documents, UiPath can also handle images and perform sentiment analysis. Processing large, complex documents can be challenging manually, but UiPath can convert them into digital formats and quickly extract the necessary information, saving significant time. For example, a telecommunications client used UiPath to classify images from cell towers, while another client in the legal field used it to analyze contracts and identify key details like timelines and disputes. This eliminates the need for manual processing of large volumes of documents.

UiPath helps minimize human errors by automating tasks. It even allows us to create extensions in plain English. For instance, instead of writing complex code to find a phone number in a document, we could say "Fetch phone number" and UiPath would generate the necessary code for us. This makes automation development more accessible, even for those without extensive coding knowledge.

UiPath helped our clients save money by automating tasks. This meant they could reduce the number of employees needed. For example, a repetitive four-hour daily task could be eliminated. In a large call center with 100 employees, automation might reduce staffing to 20, saving the company the cost of 80 FTEs. This approach has been used in many industries, including airlines where manual searches in contact centers were significantly reduced.

The most valuable features of UiPath are the user-friendly UI and manageable learning curve. Their Academy offers valuable courses, and they keep users informed with clear communication and updated documentation whenever new features are released.

I've submitted feedback to UiPath, including a suggestion to improve the slow mainframe connection currently limited to a 300ms timeout. Focusing on the connector would be a user-preferred approach, allowing interaction with applications like ServiceNow, SAP, or Salesforce and future ones like Dynamics 365 or ERPs through activities instead of custom code. This reduces development time and reliance on technical expertise simplifies maintenance for future teams, and provides a user-friendly, reusable component.

I have been using UiPath for eight years.

I would rate the stability of UiPath eight out of ten.

I would rate the scalability of UiPath seven out of ten.

I've encountered various issues with UiPath products, including activity connection problems that worked fine during development but not in production, occasional defects, and personal knowledge gaps. Sometimes these were bugs addressed in later patches or releases. To find solutions, I'd first search the UiPath forum for answers shared by other developers. If unsuccessful, I'd submit technical support tickets based on our UiPath service level. Responses came quickly, and for premium support, we could directly contact our technical account managers for immediate issue resolution.

We can expect an email response after submitting our ticket. Response times for standard support subscriptions range from one to two days, with issue resolution taking up to four days. Premium support offers immediate response and prioritizes issues based on the number of affected machines and their importance in our workflow.

UiPath deployment is very manageable. With their cloud option, they handle everything and provide a URL for easy access. Even on-premise deployments are straightforward thanks to UiPath's clear documentation. While some IT team coordination is needed for on-premise security and Active Directory integration, the process is generally simple and can be done within a few days. Overall, cloud deployment is the easiest option, but on-premise is also achievable with good IT support.

UiPath deployment on the cloud is fast, but additional setup is needed for large organizations. While integrating with our existing IT directory keeps user creation a few hours, creating separate environments, machines, licenses, and folders can take a few days depending on the complexity of environments, machines, libraries, and use cases.

One admin person is sufficient for deployment from our end.

I evaluated Power Automate but UiPath has more features.

I would rate Uipath seven out of ten. UiPath's process mining feature, while desired by many users, appears to be limited in its current functionality. Since many haven't implemented it yet. UiPath still needs to refine this area.

UiPath does not require maintenance from our end when it is deployed in the cloud.

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

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

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

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

I have used it for about six years.

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

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

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

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

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

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

I use this solution for automating customer processes. I have been working with this for almost seven years and am responsible for automating various business processes across different industries such as finance, telecommunications, and airlines. I have experience working with numerous sectors and do not use it for personal reasons.

Document Understanding allows me to track information not only from structured documents but also from unstructured documents through artificial intelligence and machine learning techniques. These are excellent tools. Additionally, the process understanding enables me to track and manage document processing effectively. Ease of building automation includes utilizing tools to record the process and generate the initial process design document.

I have just generated the default pilot. I believe another option for the tool could be voice interaction. For example, similar to using assistants like Alexa, it would be beneficial to integrate voice commands with the UI to create an Excel spreadsheet and populate a data table.

I have been using the solution for seven years.

I have experienced stability issues.

I have experienced scalability issues.

I would rate customer service a ten out of ten.

The number of solutions we select depends on client needs. My company uses various software platforms without preference, and it depends on client requirements and objectives.

The initial setup is efficient if all infrastructure requirements are met, faster than Azure's requirement. It could take about an hour.

We have our checklist that describes every document. We ensure everything is checked. We are a consulting company, and we have expertise in this field.

If you lose higher Wi-Fi parameters, it saves additional time. The license cost is slightly higher compared to other providers, yet the benefits are justifiable.

The developers are very client-focused, always looking for feedback and adding additional value in every version. I was one of the first UiPath MDPs, and it enables a lot of learning opportunities. If you're keen on learning, you can benefit greatly.

UiPath is accessible with various language options, breaking down communication barriers. Many developers benefit from this, especially since it's free. Fatigue can lead to errors, but automation helps reduce such issues, particularly in financial processes. In terms of digital transformation, UiPath accelerates the process and reduces costs.

Overall, I believe UiPath is the best tool available. I rate the overall solution ten out of ten.