Nintex Forms and Workflow - solve your forms issue in the company
May 04, 2020
Nintex Forms and Workflow - solve your forms issue in the company
Score 7 out of 10
Vetted Review
Verified User
Software Version
Nintex Workflow for Office365
Overall Satisfaction with Nintex Process Platform
We use Nintex in our company in several departments. We created a health and safety form in Nintex Forms. Several employees had to complete the form with several tabs. When ready the form was stored on SharePoint and the Nintex workflow with approval steps started. After reviewing the second phase the last approval step started. Used by 6.000 people.
Second one is a purchase request form for all our centres +/- 4000 to request small purchases. This is a complex form with several tabs. Approval steps built in with budget thresholds.
Second one is a purchase request form for all our centres +/- 4000 to request small purchases. This is a complex form with several tabs. Approval steps built in with budget thresholds.
- Forms: Easy to build, user friendly and can reduce the usage of paperwork in the company. Can replace easily all of your forms in the company.
- Workflows - MS flow can be used for a lot of standard workflows. The complex ones with calculations are more easy to build in Nintex.
- You can assign admin rights to the more advanced users easily.
- Standard connections and actions can be shared with other workflows in the tenant.
- Complex workflows need developers' knowledge.
- Lack of standard templates for standard processes.
- Nintex for O365 is very expensive compared to the on prem version.
- We needed to rebuild Nintex workflows from on prem into the cloud with other tooling. Licenses are very expensive for all workflows. Impact was that we had to invest a lot of money for external consultants to rebuild everything.
- With forms and flow we saved money by replacing the health and safety software.
We use it in Office 365. It is very important to have the flexibility to turn Nintex on and off on all SharePoint site collections.
We are in control of what department can use it.
We are in control of what department can use it.
Several employees had to complete the form with several tabs.
When ready the form was stored on SharePoint and the Nintex workflow with approval steps started.
After reviewing the second phase the last approval step started. Used by 6.000 people.
Because the user interface is very user-friendly no end user training was needed.
When ready the form was stored on SharePoint and the Nintex workflow with approval steps started.
After reviewing the second phase the last approval step started. Used by 6.000 people.
Because the user interface is very user-friendly no end user training was needed.
- Microsoft Power Automate (formerly microsoft flow)
Last year October some actions in the workflows were not possible in Power Automate.