We took a chance on Nintex--now everyone wants it.
March 13, 2020
We took a chance on Nintex--now everyone wants it.
Score 9 out of 10
Vetted Review
Verified User
Software Version
Nintex Workflow for Sharepoint
Overall Satisfaction with Nintex Platform
The Nintex workflows and forms were originally used as part of the new Document Management solution when we migrated from shared drives to SharePoint. The forms made item creation more intuitive and the workflows we created helped drive user adoption e.g. Send for Approval, Assign To, Collect Feedback, and Set the Department column (to automate metadata collection). The success of the workflows and forms was picked up by the Finance Department who then spent one year automating 80% of their processes. Now there are other departments queueing up with requests for automation using Nintex.
- Nintex forms drive User Adoption as they can be beautifully branded.
- Nintex workflows are intuitive to end-users. It is simple and easy for them to start using them.
- Nintex workflows are very scalable. We have simple Send for Approval workflows as well as highly complex workflows using multiple state machines.
- It is easy to draw a process using BPMN and then map it to the workflow steps.
- It would be good to have even more online training available.
- Some kind of on-premises version of Hawkeye would be useful--it's currently hard to monitor the on-prem usage of workflows.
- There don't seem to be any official training books available. All the training is bits and pieces. There seems to be no curriculum, which would be useful.
- Initially, Nintex drove User Adoption with super looking forms and seamless workflows.
- The initial success led to Nintex being chosen for a large project to automate 80% of the processes in finance. This has created a big positive ROI.
- We have also used Nintex as a Staff Profile solution and this was well received.
We used Nintex with SharePoint 2013 and then 2016 and we found that the upgrade process was not painful. What we could have used earlier on was some consultation about growth and scaling the databases. We have everything in one database and now we need to start another project to create more DBs and map these to the Site Collections. If we'd known more at the start, we could have saved this pain.
Yes. Most of the staff are non-IT and some are barely computer-literate but we have had no problem not only in teaching users how to use the workflows but also in supporting those users. Non-IT users use the forms on a daily basis and probably don't even realize they are working with Nintex.
We were using SharePoint Designer at first and we had to choose between installing the SharePoint Workflow solution or going with Nintex. We chose Nintex because the Microsoft deployment was complex and the UI was not intuitive, and Nintex was an easy installation and just looked better. Also, InfoPath was end-of-life and we needed a form solution to replace it so we chose Nintex forms also.