When completing a form I'd like users to answer "yes" or "no" to particular questions. This information then get embedded in an email and gets sent out to multiple departments. But instead of the "Yes/No" field showing as "Yes" or "No" it instead shows as "True" for yes and "False" for no. This is not helpful, especially when emailing non-techie people within the company. Thank you.

Actually Task form properties view is a global setting defined at the farm level (in Global Settings in CA), could be very useful to set it at the task level, so each task, even in the same workflow, could have a different view

How come we've never had a "multiple lines of text" workflow constant type?

Reason i'm asking is because I've used workflow constants in my nintex forms to put in snippets of javascript code (for example hiding the sharepoint ribbon on my SP 2013 forms) and adding it in as a reference in the javascript section on my nintex forms designer and showing some of my process owners how to resuse this.

In an extranet environment, we are allowing anonymous users to submit items to SharePoint lists.

We wish to have workflows start on these items, but at present workflows set to "start on creation" will not start when anonymous users have submitted.

To get around this, we must comb with a site workflow and run list level workflows pretty much hourly.

I would love to see the link to Create a new workflow, and the direct link to edit the workflow added back to the Workflow Inventory (WorkflowGallery.asp) page.

The standard Nintex workflow version used to have both features, and they were removed in Enterprise version for some reason? It used to be really nice not only having all options on one page, but to be able to create or edit the workflow just 1-click away. Now you have to click on workflow name, then click on edit for example.

People Picker people only validates after the item has been submitted. In the legacy people picker, the validate is triggered as soon as you have entered in a value.

Right now my Nintex workflow tasks dont show up in MySite Tasks area. Nor in the Workflow settings can you set up the Task list to create items in a SP Tasks App that you have created.

It seems like the same template but it is not.

If you have multiple 'Run If' and/or 'For Each' in one workflow, it would be easier to identify them if they were each a different color.

what would be great is to allow for the Nintex Designer to AutoSave forms and workflows every 10/15 minutes, so in case the browser freezes or you accidentally press back, you can go back to the most recently saved design. similar to how MS Word autosaves documents...

When minimizing a switch or other "parent" style action so you can more easily view a complex workflow, there's no indicator to show you that it's been minimized. Maybe change the container border into a stack of containers so you can see it's actually multiple actions.

I often lose all the changes I made when designing a workflow and pressing Ctrl+W unintentionally. Ctrl+W closes the current tab (in IE) and there's no message that is displayed asking us if we are sure to close the current window or tab.
Adding this kind of message would be really great when closing the tab using Ctrl+W (there's maybe other shortcut that closes the current window or all tabs)

New inline functiions for Nintex Workflow to encode and decode a URL, similar to the fn-xmlencode and fn-xmldecode, however for urls as well.

The only good editors I have ever used have been desktop applications. Visual Studio, InfoPath.
These offer far more advanced user experiences to author solutions.
They are inherently built for offline and they are more stable and offer great keyboard support to build robust solutions.
The Nintex web based designer is terrible to work with and no developer should have to deal with the design experience you offer in 2016.

Often times, within a workflow, changes need to be made to item properties. If there were a way for Nintex to recognize changes made by Nintex (system), that could make conditional start options much easier for other workflows on the same list/library. In other words, a wf update to a field won't trigger a change that starts another workflow. Being able to add conditional starts that EXCLUDE changes made by Nintex, versus a human, would be very, very helpful.

Infopath can be used to create workflow start forms, however it does not have the nwcontext xml resource file necessary to use an item's metadata, unlike task forms customised using Infopath.
Whilst variables such as approver comments are not applicable, it would be very useful to provide the basic fields such as item ID, creator and item url.
I've been told by Nintex support that this discrepancy is intended functionality and to raise the request on here. Infopath is still a much stronger form designer than Nintex forms, for things such as multiple data connectors or unique values in dropdowns.

The workflow is limited to 500-600mb which means fewer actions and all forms must be very simple and have very few rules. The only way around this is to have multiple workflows that start the next at the end of each one. A workflow should be able to encompass a whole procedure in one workflow instance.

At the very least it should warn you the workflow has exceeded the memory space and not allow you to continue to work.