Overall Satisfaction with Nintex Platform
Nintex products were first selected for review by my company as a replacement to the out of the box SharePoint 2010 designer workflows and to also remove the burden of support for user-designed custom workflows. When evaluating products, my team was impressed with the ease of use, flexibility in workflow design and build turnaround time as well as the implementation of their products. We hand-picked a select user base that we knew were building and designing SPD workflows for evaluation as part of a pilot project. It didn't take long for them to adopt the product and eventually convert their existing SPD workflows to Nintex. SAIC/Leidos was one of the first large organizations to officially use Nintex products and we have a great rapport with our account managers as they are always looking for feedback on how they can improve their products. We've officially used all of their products to date including Nintex 2010 Workflows 2010, Nintex 2013 Workflows and Forms and the latest version of Nintex 2016 Workflow and Forms. Our SharePoint farms are all on-premise and located in our data centers in the U.S., United Kingdom and Australia with a current user base of approximately 40,000 (internal employees and external contractors) supporting over 5000 site collections.
- Nintex workflows provide a robust interface that's not only intuitive but easy to learn with little to no coding experience.
- Nintex forms are particularly powerful and provide a great alternative to InfoPath forms which is being deprecated.
- Upgrading between versions of Nintex is easy to do with their nwadmin tool and robust documentation provided on their support portal.
- The user adoption rate of their products is extremely high and doesn't require a selling point or an explanation of benefits in converting their existing workflows and forms.
- Updating Nintex to fix bugs in a production environment can be challenging at times and requires thorough testing in a QA environment first as it doesn't always go smooth.
- Separating Nintex content databases and moving site collections with large workflows can be a daunting task.
- Nintex workflow timer jobs can use a lot of server resources at times and application server load balancing should be implemented instead of running on a single server.
- Over the years, Nintex has become a very solid product requiring very little back-end maintenance and minimal end user support.
- Nintex Workflow and Forms is a true replacement for SharePoint Designer Workflows and InfoPath forms.
- The only negative impact we've observed is with educating end users on keeping their workflow history lists clean and to remove unnecessary logging (i.e. Verbose) when not troubleshooting a newly created workflow.
We use Nintex products in our on-premise SharePoint 2016 farms to support both SharePoint and Project Server in a medium-large farm with over 20TB data and growing. Being that we support almost 40,000 users in the U.S. alone, it's imperative that the products are stable and easy to maintain. Since we've used every version of their products to date, we've seen it become more robust over the years with a well thought out design and solid implementation.
Nintex products (Workflow and Forms) is being leveraged by both our internal employees and external contractors regardless of the business unit as it supports corporate as a whole. Our end users are very happy with the products and their ease of use along with a generally small amount of development time needed to generate new workflows.
As a rule of thumb, we generally don't support SPD workflows as in a lot of cases an end user will build them and then leave the company and nobody knows what they did or can truly support them. We encourage our end users to adopt Nintex products as it's much easier to cross train and reverse engineer the workflow or form design.
Nintex should consider the industry that their products are designed for in that it's not always possible to transmit data to the cloud in order to use some of their advanced features. Leidos is a defense contractor and we are under tight restrictions on what can and cannot be done outside of our data center and some of their features should be made available to on-prem farms. So in our case, Nintex Live cannot be used nor can their document conversion even though our users are constantly asking for these features.