At present when a form is submitted the people picker control is validated on user login. Can this be changed so the control is validated using Email address instead of the login name.

Would like the ability to clear unconnected fields on a Nintex Form when the form loads. Some customers have the requirement not to preserve form data to a unbound field on the form.

This control should support the ability to save to a multiple lines of text column. Currently it is able to lookup text with the lookup() function from a multiple lines of text column. It ought to be able to save to such a column as well.

This would be so useful and time-saver if we could copy control from one form to another form. Also, it should be possible that we could import a complete form let's say source form, into another form i.e. destination form while older controls in destination form are not lost. For this, user should be able to import a form in a panel sort of thing in another form.

I truly believe that the delete form button should be either moved far away from other common buttons or have further steps added to complete the deletion such as "Fill out the following word to confirm delete"; especially considering there is little to no way to bring back a deleted form.

There ought to be a control that when placed on the form will mark the end of the printable version of the form. This way you can hide any buttons or other controls from being printed if they are below this control on the form.

Notice that with responsive forms design on-premise for SharePoint that we can only have 4 columns. Can we get the same increase for amount of columns you can have to match responsive form design in workflow cloud.

Each SQL Control needs to have the database server name specified as well as the database name. Please create a global form constant functionality that can be used to specify these values. We have SQL controls on 50+ forms and in the case a server name or database name changes, it is a painful process to locate each sql control, update it, and publish the form.

Currently, there is no option to use form variables in default control values and as reference values in labels.
Examples:
* Pre-populate default values depending on the user group membership in new forms.
* Switch between different form views controlled by a drop-down depending on the user role.

Remove the lines on all controls and labels by default or make a setting, they just clutter things up and look terrible. Having to go in and adjust the CSS on every form every time is a pain. That pesky top line is a weird choice. Usability is inclusive of appearance and clutter.

Make ALL form controls the same height by default, Date inputs are shorter than dropdowns which are shorter than text inputs. Currently All (the same font) yet all different heights which looks terrible.

If you are planning to use a Nintex Forms on a "Assign Flexi Task" Workflow Action and configure that Form with a "Save and Continue" Button you will find out that this setting is not there apart from the normal Nintex Forms where this feature is available.

Nintex Workflow -> "Assign Flexi Task" Workflow Action -> Edit with Nintex Forms -> "Button" Form control -> Button action = Save and Continue is not available.

Currently the Nintex Mobile App doesn't display the Radio buttons, instead it shows the options as a drop down list.

We have built a QA process form which shows a poor design without Radio buttons.

Please include the Radio buttons in the Nintex Mobile App.

Thanks

Ability to configure the attachment control to prevent users from deleting existing attachments

Would like to have the ability to toggle if users can remove rows in a repeating section using a runtime function and a named control. Currently on both classic and responsive, nintex forms only lets you use an expression where you can use inline functions and item properties.

What could also work is perhaps having the abillity to hide the "x" in the repeating section.

Use case could be a process where users add comments or data to a form but should not delete other peoples data.

Nintex Administration --> Form Controls

Missing Ability to remove /restrict some of form control actions based on usage like we have workflow actions for workflows.

When the repeating table control is used and only one table is displayed, the X delete button is still visible although its functionality is disabled and users attempt to click it. Have the X delete button appear when there are 2 or more tables.