What previously stood K2 apart from Nintex was purely the ability to have workflows executed outside of SharePoint. Nintex are due to release a product that resides in Azure that provides this feature as well. K2 should really look into redesigning the development GUIs they are …
Automation Anywhere is well suited for automating repetitive or complex tasks that can be performed on a timeline such as data processing, data extraction, and file transfers. Automation Anywhere also has capabilities for integration with legacy applications and APIs to automate more complex data flows. Automation Anywhere is also ideal for automating document processing, form filling and other web activities since it has both image recognition and image-based automation capabilities.
On the other hand, Automation Anywhere is less appropriate for tasks requiring high levels of system intelligence such as machine learning or natural language processing as these require different types of technology. Additionally, if a task requires manual elements such as validations or reviews then Automation Anywhere may not be the most suitable solution either. It can be possible to set up automated validations but that might not always result in an ideal solution due to its limitations.
The Nintex K2 platform is not only efficient and developer-friendly, but the support provided by the vendor is also highly commendable. The platform's ease of use and robust functionality make it a preferred choice for developers, while the vendor's exceptional support ensures smooth implementation and ongoing assistance, enhancing overall user satisfaction.
Now I easily generate the invoices and quotation generation is an easy task now. Previously it was very time consuming as we have to drag the data from the excel sheets.
I will praise its integration with other software that has facilitated us to make amendments in the data across those platforms.
Automation Anywhere doesn't come with easy installation, We need to install Java, IDEs and Databases in an orderly fashion which we are not able to do.
Automation Anywhere has no workflow design which is not making us to understand the process.
Automation Anywhere has no fit to size object cloning.
Adding Machine learning features like the "Image and Text Automation" component, which allows bots to extract data from unstructured sources like scanned documents or PDFs.
Natural language processing (NLP) features to understand and interpret human language, which can be useful for tasks like customer service or data entry. mostly for middle east countries where Arabic language is used.
Integration with external systems where many industries uses their own legacy systems and they need RPA bot to interact with their systems as well.
Adding More OCR tools for Document data extraction and dynamic content.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
On more complex use cases, Automation Anywhere requires technical background like knowledge on network protocols and database language on task creation, and even people with technical background might have some trouble in the beginning because of the product particularities on how variable manipulation works, or how to get the object cloning (a more resilient screen manipulation command) to work as intended. The scheduling of tasks on the Control Room and the autologin feature isn't intuitive as they should, so much of this works requires documentation analysis to get it done on the first time.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
Automation Anywhere is a great tool for a low cost, fairly easily scalable, and quickly learned. The company is growing by leaps and bounds and continually pushing the automation boundaries. The problem with fast expansion is that sometimes you can grow more quickly than you can appropriately support your products. While Automation Anywhere has an excellent support structure in place, every company and situation is different, and they often struggle with why problems arise in the system and how to fix them.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
Automation anywhere scores well with respect to other solutions when we look at bot implementation, bot management, and basic automation. From a security perspective as well, AA fares well as compared to other solutions. UIpath is better suited when we operate using VPN systems and integrating with homegrown solutions.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
Highly reliable once you start experiencing the results. It helps you to have a clear cut results with better productivity numbers and financial savings
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
