Nintex, when basic fails and you need to take it up a level
June 22, 2019
Nintex, when basic fails and you need to take it up a level
Score 9 out of 10
Vetted Review
Verified User
Software Version
Nintex Workflow for Office365
Overall Satisfaction with Nintex Platform
Used to make efficiencies across the organization, writing to lists, approvals, data collection. There is not enough functionality in MS Forms and Flow to fulfill all our requirements. Multiple approvals, lazy approvals, and multiple conditions are a great help. I am currently training others in our organization to empower them to find and implement efficiencies.
- Running workflows that require multiple approvals with extra information being required on occasion.
- Running approvals where it depends on other factors as to who to choose as the approver.
- Writing items to lists.
- Identifying user details from AD ie line manager and department.
- Extracting information from XML, in particular from repeating sections created in Nintex forms.
- Extracting items from repeating sections.
- Parsing information from AD i.e. e-mail addresses.
- It would be good to format columns/rows in SharePoint lists.
- Without purchasing Hawkeye this is difficult to measure however looking at lists for approvals show many working hours have been saved.
- This can help enforce procedures, for example ensuring forms are completed correctly.
- Helps to ensure data collected is correct and relevant using validation.
Currently, we use Nintex workflows in SharePoint however we are looking to reaching out to external colleagues using the Nintex platform rather than basing it all in our O365 tenant. We hope to be able to collect data from external partners and use workflows to bring this into our tenancy securely.
We have a few creators when it comes to workflows although as with Forms we keep this to a select few to ensure we can track our usage and ensure we get value for money from our forms and workflows. Nearly all staff will come into contact with Nintex as an end user. This may be filling in a travel request or approving an activity.
We use Flow for simple tasks like taking information from an MS Form and writing to an SP list. We also use MS forms for free quick data collection including externals. When processes are more difficult or forms need to have rules then we use Nintex as it is far more powerful. Everyone is enabled to use MS Flow and Forms however only a few trained members use Nintex as it is more complex and costs per form/large workflow.
In essence for the small things MS products are quick and easy but for anything more complex Nintex wins hands down.
In essence for the small things MS products are quick and easy but for anything more complex Nintex wins hands down.