Workflow & Forms for Grownups
March 12, 2021
Workflow & Forms for Grownups
Score 9 out of 10
Nintex Workflow for Sharepoint
Overall Satisfaction with Nintex Process Platform
Workflow & forms. Numerous administrative procedures which used to be manual/email/excel/impossible to track, now formalized/defined, streamlined, substantially automated, measurable, traceable, easy for people to understand and undertake, accurate data collection at the outset, signoffs if required, document generation directly [from] the captured data in some cases. Created by ICT dept and also extensively used by one business department.
- Highly configurable/[customizable]
- Extensive workflow capability
- Easy to use - most concepts presented in non-technical terms
- Perfect for a BA to use for data definition/collection/analysis/workflow
- Hide/display rules on forms rather cumbersome
- Need to be able to add comments to workflows
- Printing of workflows: the resulting format is not usable at all
- Responsive forms - not sufficient density - too much white space
- Need ON DELETE trigger!
- Considerable time saving for service department staff
- Support for health & safety prerequisites
- Process improvements, simply via the formalization/standardization that Forms & Workflow provide
SharePoint 2013. Not sure if the organization is going to invest in Nintex solutions for the 365 environment - might be expecting us to use PowerApps only. If by "deployment flexibility" we mean the use cases, then there is 100% flexibility and that is the reason we like the product set.
Yes, non-IT people can get their heads around workflow easily, especially the way it is implemented in Nintex (plain English, good graphics, all the fiddly stuff that non-IT people won't know about is already handled, etc). Whereas Flow is almost impenetrable to the average person.
[The] main thing is that it ENCOURAGES the business to automate because it's so easy to give the business something that does 95% of what they want, that they are happy to ask for the next process to be tackled.
It is easy and quick to prepare a proof of concept that helps the users understand what's possible, so then they can engage and provide their input into the next [interaction].
From the users outlining their problem statement, we can often get back to them within a couple of days with an example of what's possible. They are usually keen to get something going with 95% of requirements covered, and not have to go to IT to get something programmed, so we can often have them running with the solution within a fortnight.
Microsoft's SharePoint 2013 workflow has a number of shortcomings that Nintex Workflow just deals with effortlessly. The Nintex tools seem to be built by people who understand how [to] process stuff is done properly, whereas the MS tools are comprehensive but seem to be written by & for programmers. For 365, PowerApps seem to be taking over the world, and not having PowerApps on your CV is a problem.
Internal business processes, of which there are hundreds within any big [organization], are perfect for Nintex Workflow & Forms. They replace the usual mess of emails, spreadsheets acting as databases, ill-defined processes & permissions.
Not so good are cases where a request needs a substantial dialogue between the requester and the service provider. That dialogue is not easily captured against the 'case', so is often still just via email. Whereas the likes of ServiceNow supports the ingestion of emails and stored the dialogue against the ticket.
Nintex Process Platform Feature Ratings
Nintex Process Platform Training
I bought an old fashioned book for Workflow, and followed my nose for forms. I have done process/data schema/form design for years so already knew all the concepts, but not how to do them in the products. The workflow tool is so well designed that it is fairly easy to pickup.