Nintex is ultra user friendly
April 08, 2021
Nintex is ultra user friendly
McKee Foods CorporationFood Production, 5001-10,000 employees
Score 9 out of 10
Nintex Workflow for Sharepoint
Overall Satisfaction with Nintex Process Platform
We are using Nintex Forms and Workflow as our primary form software for SharePoint 2016. Nintex is being used across the whole organization on a departmental basis. We are using Nintex Forms to replace the many InfoPath forms we have before the Microsoft support runs out. Nintex is also providing more options to connect to external database sources.
- Nintex Platform allows you to easily turn a SharePoint list into a dynamic and robust form that is attractive and end user friendly.
- Nintex Platform is entirely web based and requires absolutely no additional software but is feature rich.
- Nintex Platform has a large user community who will answer questions.
- Nintex installs directly on top of SharePoint instead of requiring an additional server.
- Nintex integrates with SharePoint seamlessly.
- Some of the controls for Nintex Forms are not complete or could use some refining and require additional programming to get them to work correctly. For example the SQL Request control does not allow you to easily use a text list fields as a parameter when you are calling a SQL Function. If you want to force a list field to be of the type string you would usually put single quotes around it. But it would then see the variable name as the string value rather than the value of the variable being the string value. I had to add some weird coding to work around this. Funny thing, it works if you are calling a Stored Procedure.
- There is no way to get a table back from a SQL Function like you could in InfoPath. In Nintex it only allows you to get back single values. This means that if you want to get multiple values from SQL it will require multiple SQL Requests. This works but it is very inefficient.
- In Nintex Workflow it allows you to easily get individual values from a people person field such as the Display Name, Email, Username, etc. But in Nintex Forms you can only get one value which is the username in the cryptic Claims Based version of the user ID. Therefore for each people field I have to also create a separate name, email and username calculated control that will calculate the values I need rather than being able to simply reference the people field and specify that I want the Name, Email, Username, etc.
- The Nintex Form SQL controls will only allow you to connect to text fields instead of being able to connect to multi-line text fields meaning they have a 255 character limit. But if a user needs to select more than 255 characters from a SQL Request Selection it will become difficult to write it back to a list. I had to write it to a workflow variable which thankfully could handle more than 255 characters. Then I could write the workflow variable to a multi-line text list field. Nintex calculated fields also will only connect to text fields instead of being able to write to multi-line text fields meaning that they also have a 255 character limit.
- The first project I worked on with Nintex Forms and Workflow was to replace a process that we very under developed and was not possible to do wtih InfoPath. So we got an immediate return on our investment.
- We have several forms which need to be replaced and it just adds to our return on investment.
SharePoint 2016. We intentionally want to keep our deployment in-house and on internal servers because we want to be in complete control of where the data resides. We are not interested in cloud deployment at this time.
Yes. Non-IT staff are the primary users who fill out the forms that we create. We also have several non-IT people who are developing Nintex Forms. However, everyone comes to the SharePoint Administrator to develop Nintex workflows because they are more complicated and we prefer that workflows are developed in the IT department.
It does not require a separate application to build forms but instead is built right on top of SharePoint. This has allowed me to easily train end-users to build their own form rather than everyone coming to me to build a form for them.
Huge. The user goes to a list, selects properties, and the clicks on edit form. Much faster than having to find the form buried somewhere and then figuring out how to open it in the application.