My Nintex WorkFlow experiences
Updated August 20, 2018
My Nintex WorkFlow experiences
Score 9 out of 10
Vetted Review
Verified User
Software Version
Nintex Workflow for Sharepoint
Overall Satisfaction with Nintex Platform
Our organization uses Nintex Workflows for document management, task assignment, coordination, accountability, continuity and to ensure the end product is delivered to the customer.
It is being used by the program I work for with a government customer.
- Unlike SharePoint Designer WorkFlows, I enjoy the ease of use with Nintex WorkFlow drag & drop actions and how easy it is to configure them with SharePoint artifacts.
- Errors are not as difficulty to address after trial and error. I have encountered errors in SharePoint Designer WorkFlows. Based on my experience, Nintex WorkFlows are lot easier to work with and troubleshoot.
- The multitude of actions, that can be configured to create various Nintex WorkFlows, are endless. These actions can be mixed and matched to meet your customer requirements.
- Use of use with CSS and customizations.
- Though Nintex WorkFlows are great for administrators, they are not designed for developers who have to utilize workarounds in order to accomplish simple actions.
- For SharePoint migrations from 2010 to 2013, it appears that Nintex may not issue migration licenses as quickly as your customer may expect.
- Nintex is not a cheap product to purchase. Customers must assess their needs, requirements and budget before investing in Nintex licenses.
- Nintex offers process automation that simplifies business solutions. Learning how to use all of the actions is not as time consuming as other WorkFlows I have configured before.
- The learning curve on creating, maintaining and troubleshooting Nintex WorkFlows heightens productivity. Plus, I can appreciate the online courses offered on their Nintex community site along with live support assistance if and when the occasion rises.
- I have noticed less WorkFlow bottlenecks; This improves efficiency, controls expenditure of time, money, resources and drives process improvements.
I use Nintex WorkFlows in SharePoint 2013 on-premise. Nintex platform serves as a base for all of our program WorkFlows. We don't use the default SharePoint WorkFlows nor SharePoint Designer WorkFlows. They don't meet the customer's requirements.
Nintex Workflows are being used by non-IT personnel as well as for IT personnel who maintain it. Non-IT personnel use Nintex WorkFlows for task assignment and document accountability for each sub-dept that works on in-bound and existing documents. Nintex WorkFlows delivers our work to our customer seamlessly.
Nintex WorkFlows seems to be a lot more user friendly, contrast to using SharePoint Designer. I had to spend a lot of time learning SPD and even more time troubleshooting SPD WorkFlows and InfoPath Forms. Though Microsoft offers lots of information on knowledge base (kbs) and "Tech Net" articles that can be an eye sore to read, Nintex has a lot of easy to understand online courses that empower administrators how each action works, WorkFlow terminology and mitigating errors. I appreciate the Nintex online community that also zeros in on troubleshooting when admins are stuck.