Microsoft no longer supports the use of IE11 for Office 365 applications but Nintex does not support Microsoft Edge. We have to browser jump between IE11 and Edge to get our work done.

Currently only hard-coded URLs can be added to rich text/labels or controls in Nintex Online. It would be great if Nintex can enable insertion of dynamic URLs

Add the fn-GetQueryString() function to Nintex Forms for O365 so a query string parameter can be used on form load. This would replicate functionality found in Nintex Forms on Prem.

The Nintex Form web part for SharePoint online has no configuration features. Ideally the form should be embedded on the page using the web part and just show the form. You shouldn't have to see the ribbon at the top of the screen or the grey area around the form. This way users can stay on the page and fill out a form without unnecessary scrolling or in page navigation due to pointless padding.

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.

Minimum solution a feature like in Nintex Workflow for O365 that allow us to restrict the use of Nintex Forms to named users.
Perfect solution see also: https://nintex.uservoice.com/forums/229406-2-nintex-forms-for-sharepoint/suggestions/35217565-forms-permission-restriction

Labels are not correctly applied to form fields - primarily choice fields with responsive forms. For a non-sighted user they don't hear what the choices are for when trying to complete the form. This is a big accessibility issue that should be corrected.

We would like to have a feature that default value is also implemented in the EDIT mode
Background:
Set default value won't take any effect for the Edit Form located in Document Library. The control will always be set to empty and ignored the default value that has been configured from the Form designer.
In the Document Library, since the file is uploaded through the UI, there is no such NEW mode.

[ ref:_00D90q6Cb._5002v2FgRXI:ref ]

In default SharePoint form when clicking on the tags to open the managed metadata picker you have the option to add new items if allowed. This functionality is missing in Nintex managed metadata control.

Currently user in SharePoint can edit an open term set if the option they want isn't there.

Please can this action be supported by forms also?

Please make all viewable properties in a list, such as "Created by" and "Version", available to place on the form as read only (disabled) connected field controls.

We need the ability to have tabs (or at least fake tabs, like in Classic forms) for the Responsive Forms designer.

There is no option to view the names of controls added to a Responsive form. It would be nice to have something similar like the controls in use tab so it would be easy to find the controls in a large form

Please also display ruled lines even if there is no data in the People picker control.

Prevent submission of form when 'Enter' key is pressed in responsive form. Expecting same feature in Nintex forms for O365.

https://nintex.uservoice.com/forums/229406-2-nintex-forms-for-sharepoint/suggestions/5974404-stop-the-submit-of-form-by-using-the-enter-key-p

Repeating sections must support Managed Metadata control

Thee is an error in the online help info regarding the expression that can be control whether a field's appearance is enabled or not. The help text states that the expression must resolve to a Yes/No value at runtime. This is NOT true. The expression must resolve to True or False. A simple expression of IsNewMode works as is.

URL to your help doc
https://help.nintex.com/en-US/O365/Default.htm#cshid=3017

Currently form variable return types are limited. Please add the ability to specify the variable output format similar to how the workflow product functions (e.g. for People Picker options are Login Name, Email Address, Display Name).

Currently Nintex Forms for Office 365 form variables cannot connect to people picker columns. Please add this feature.