When closing a site workflow designer please make it return to the Workflow App home page instead of site homepage. It is annoying especially when you have to check scheduling etc. after closing the designer, when you have to come back to the Workflow app the long way.

When we use the actionnable message in the task validation we can't customize the message in appearance or langage. I wish i can change the Nintex logo by the enterprise logo, use the enterprise graphic charter, use the langage of the enterprise country... for creating a custom message with actionnable message

Would like the ability to create, modify and manage email message templates on Nintex Workflow for Office 365, for the Task Process and Assign a task workflow action(s).

This is already available on premise, and is a very useful feature, but for people making use of Nintex Workflow for O365, this would most definitely make workflow design quicker if designers could choose an email template, perhaps containing some html and rich text/images (maybe even an email signature) where all they would need to is insert their metadata where necessary.

Can we have waiting until "Is Not Empty" or "Not Equal To" as options, as in the OnPrem version. Many times I have actions that are waiting until a fields IS NOT EQUAL to the current value.

Include a "Log to History" check box in all actions so we do not have to create a separate Log to History Action item in the workflow to record the current status.

My application with dynamic html structure containing checkbox and table structure was working fine while render to Control Content title but now, even though Rich text field support html conversion, It does not render my table, styling and the controls like checkbox,radio button

I would really like to see the previous value field reinstated in Nintex workflows, for example when selecting a value, being able to choose "created by (previous value)" as an option.

Need a way to indicate that the email is of High Importance

Need to have the option to include attachments for email notifications that are sent from the task actions.

Nintex Docusign function needs be able to send documents to multiple users at once.

As described - this is a key function for simple tasks like updating status. What is the O365 workaround?

When using the 'Start a task process' action the Outcomes have to be added/updated one at a time. It would be nice to provide one Workflow Variable as a delimited string with the Task Outcomes as the outcomes may depend on item properties. You could then add your own conditional logic for each expected outome. Key is to make the action more dynamic and versatile.

It would be nice that date and time function come as two separate functions. Because even if I select date only as the format; the output in the email body show both date and time.

Then renaming Task outcomes they are reformatted by the designer with the following rules:
first character will get uppercased
all other words will get lowercased

Sample
let deplartment Research&Development decide
will lead to
Let deplartment research&development decide

In german this leads to mal worded choices. I'd like to have control over casing of task outcomes

it would be awesome to be able to tag document generation documents with metadata so when we save them in a document library we can tag them appropriately so then views, etc can be created off the metadata.

Having worked with Nintex On-Prem for a number of years I have FINALLY started working with Nintex for O365. I cannot find anything! All the actions that do the same thing have completely different titles... Why? I am so totally lost.
Can you consistently name the actions in your workflow products regardless of the SharePoint environment they are working on? This goes for NWC too?

Hello

I'm studying a workflow and it would be such a great feature the ability to print a entire workflow as a picture, so it will help the discussion with my team about streamlining the process

Thanks
Miguel

We need this utility to come from Nintex itself rather than we are calling third party web request to encode/decode. It's quite simple, we need a utility to encode/decode URL.
This will help when we call REST API to SharePoint with special characters.