It would be nice to be able to create a shorten URL for the Forms in Workflow Cloud just like your able to do with Live Forms on SharePoint on Prem. We have already had a few request from stakeholders of some Forms and Workflows we have already created on this.

Hi all, the short cut keys to access variables/fields differ between the form designer and the form variable editor.

In the form designer, if I want to access a field/variable, I type [[ (two square brackets).

In the form variable editor, if I want to access a field/variable, I only need to type a single [

I reckon these should be consistent.

All the forms (Items + tasks) are now fully public. Everyone who has access to the link can act on it. How can you be sure that your task is not going to be answered by someone who shouldn't have access to it ? You can't. So, how do you secure your workflow? You can't.

Can we have a way to secure every kind of forms? like a SalesForce / Google/Microsoft "passeport"? and the ability to only allow a list of users (or using wild searches : *@mydomain.com) to connect to this form!

We frequently have the need to include comma ( , ) and pipe ( | ) characters in our choice options. Is it possible to allow those characters? For example, we have a product whose name is "REALTY|share" and have some forms with choice options along the lines of "Yes, please contact me immediately!"

Similar to booking sites. Having the ability to have 2 date controls with the second date control not having the ability to select a date before the first date control. Or at least to fail validation is date2 is earlier than Date1

In the settings of the form (where we can set the title and description), having the possibility to type a category for the form would be really useful. So that the form can appear in a category in Nintex mobile app.

Header fields should be choices for the "When " condition on the Rule builder, to allow for easier conditionals.
Example:
When [header field] Visible (yes)
Then [another question or header field] Visible (no)

Within the Start Event: Nintex configuration window (or any forms dialog), the fact that there are no variables should be called out initially. This helps imply that there *can be* variables associated with the form.