The current behavior: The close button returns you to the default list view.

The desired/expected behavior:
- When form is opened in full page:
The close button redirects you back to where you came from OR redirects you to the redirect URL specific for the cancel button in the action panel settings, if available.
- When form is opened in dialog:
The close button should close the dialog.

We use date fields in our Nintex New Responsive forms. Many enduser don't like that the week of the calendar popup view starts on Sunday. It would be nice when it is possible to set Monday (or other days) as first day of the week.
It would be also great when there would be an option to edit the "Today" button label? In our case we would like to use this word in another language.

It would be awesome if we could have a past time option for the date/time action.
Just to limit entering times earlier in the day.
Similar to what is already configured for the limiting past date options.

I can't find any table format in nintex rich text column. Please allow this table feature in order to make the form more user friendly rather then using html code.

When i am creating a form that has a multiselect choice column allow me to spilt the choices into columns to take less real estate on the form. Right how I have like 30 check boxes for a check list, allow me to make them into columns (2x15 or 3x10 to condense them visually).

Can we have option to select buttons like not to show EDIT button in display form ?

Save and Continue button currently does not run the Validations (Rule and Form). In our scenario we are assigning actions to a secondary SharePoint List that needs the Item ID from the Main List. Save and Continue should run the Validations the same way as the Submit rules.

The new responsive forms are great, but still has some limitations that older versions of controls had.
When using a lookup control, you can filter the values by searching for values by typing. It has however a 5000 items limit.
This value is hard-coded in the request, but Microsoft has implement paginated requests in their API.

This is a pity to have a search for large lists, but not large enough, please remove the hard-coded limit.

Allow multi-line fields to have more than 4,096 characters

Lookup field is the only way to implement a cascading dropdown in Nintex. Since lookup fields doesn't support, setting a default value or a value based on rule, the same cant be done to cascaded dropdowns. IMHO this is a much needed feature for a form development tool and I wish to see this in Nintex.

Users have complained about their browser autocomplete suggestions hiding the drop choices for a field. I explained to them this was a setting in their browser and they could just hit escape to close the suggestions from Chrome. But, it would be nice to turn off autocomplete for the form like shown here: https://www.w3schools.com/howto/howto_html_autocomplete_off.asp

If you want to fill the value of an integer (like 1.1) on a tablet/phone it doesn't work correctly if your standard language is not us/uk. We have a out comma and period which we can't use (they are greyed out).

The workaround is using text fields with a Regex validation, but this is not how it should work.

Would love to have Auto save feature enabled. This will particularly help those users who have to fill long forms.

ref:00D90q6Cb.5002v2sDK6T:ref

Can we prevent the need to disable "Cross-Site-Tracking" in Safari Browser for MacOs, as it can make the browser less private.

All browser have built-in spell check. This feature works great on classic forms. However if you build a form using the new Responsive Designer, the spell check suddenly stops working. Seems that this type of form is not compatible with built-in browser spell check.

Since CSS is not available in the New Responsive Forms we will like to have an option to hide the "Close" Nintex buttons showed in the header when the form is open as we have an option to hide the Print to PDF.

.nx-sp-form-runtime-header {
display: none;
}

It would be good if you could either set the collapse functionality to collapsed by default and or apply a rule in the rules engine to collapse a group automatically.

Allow users to enter their custom submission successful page.

The ability to relocate the action panel to the top of the form.