I often use ActiveDocs for team building materials. During the day to day rush, we really like to use the models provided, we can be agile with that ease. And the team can share different documents. We no longer have to spend hours in front of the computer typing up a document that can easily be created in minutes.
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.
Difficult to fix flows that are in process (such as re-assigning a task for someone that is OOO or has left the company).
Nintex support team does not have resolution SLAs (only acknowledgment SLAs). Occasionally this has led to key issues taking weeks to resolve.
The number of integrations available is impressive, however, sometimes key methods are not available within an integration. This has been improving significantly in the past 2 years as the platform has matured.
Renewal is mainly on the fact that Nintex is so widely used and it would be impossible to migrate all of these existing workflows to another engine. Third-party lock-in within SharePoint is pretty strong, which makes it difficult to move to something else. Our Nintex database is well-over 100 GBs. Nintex email support is very good, and I've been impressed. The Community however is non-existent and filled with unanswered questions.
Very good usability overall. Any user can pick this up and run with it. HotDocs, the closest competitor, has similar end-user usability, but from a designer of templates perspective, ActiveDocs definitely has the edge in this regard. I would recommend this for any company that mass produces documents from templates as deliverables.
Nintex Workflow does exactly what it is advertised to do: make workflow development fast and easy. It doesn't provide very much new functionality, but it isn't really supposed to. When I am working with a client on a SharePoint project, I am always happy if I hear that they use Nintex Workflow, as it makes workflows much easier.
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.
The software overall is very excellent. It responds quickly and produces documents well. The integration with systems makes data input easy. Questions can be designed to allow further expansion of template creation/customization. The rules section is very useful for complicated If/Than/Else style templates. Although experience and training help, the software is very user-friendly out of the box.
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.
ActiveDocs can be a considerably complex product because your use cases can be potentially endless. In our experience, when we have come across a problem or issue with the product ActiveDoc's support has always responded to our queries within 24 hours. Support is only provided via email in 95% of cases. Each year your support and maintenance includes support hours. These are used when you contact support and your issue is not found to be a bug or problem with the product (completely fair and understandable). When we've identified or discovered bugs (mainly with the latest version of Word) it is patched by the next release. They typically release about 4-5 updates per year.
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.
ActiveDocs and HotDocs are very similar. HotDocs requires training or a technically savvy mind to pick up and run with. ActiveDocs seems much more user-friendly and easy to use. HotDocs, however, can produce some very intricate documents based on the templates. Both use rules and question-based information intake. Another benefit of ActiveDocs is its integration with numerous systems including Office 365.
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. because it is less automated and more flexible.)
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.
