Encoding for basic auth when provided with user and pass doesnt work in the Web Request action.

Also, change the storage options for the response of Web Request to something other than choice/http/text. Text doesnt allow enough room to capture entire tokens for auth.

Please allow running workflows from console

Errors when publishing a workflow can be difficult to troubleshoot since the error messages are generic.

For example
"Error publishing workflow. Specified data type does not match the current data type of the property"

It would be helpful to know what property it is talking about, the data type it is expecting, what is trying to send it the incorrect value and what value it is trying to send.

Often times I have to go over several actions of the same type in mi workflow changing their config. It would be useful to have the last selected action be highlighted in some way so as to keep track of my progress. Now I do this by centering the action in the window but this is not ideal.

Option to select multiple actions to delete, disable or move them all at the same time.

The ability to set a "Default Value" for most variable types is not available. It's available in the on prem version.

The label just view part of text, when label more than 5 characters

Each time export file, the file content no change, But the file content is not same, when using md5 check it.
If possible export JSON for readable format is very Good.

Allow for a Collection Variable of file URLs to be attached like on-prem. We rarely know how many attachments we need to attach and attaching a number of string variable limits this number.

While most options appear in English language, occasionally some stuff are displayed in Spanish. WTF? Please unify the localization, instead of mixing it up, because later on is hard to use the search box (should I search in English or in Spanish?)

If I save a workflow under a different name - to create a copy - the original workflow seems to disappear. It would be better if the original workflow remained with the old name.

From the governance perspective, personal connections should be disabled by default. Currently it must be manually disabled on each site/sub-site.

Recommended path:
1. Personal connections must be disabled by default
2. Need basis site owners may decide to enable it
3. This would encourage the use of shared connections

When creating a site using the "Office 365 Create Site in o365" action, and creating unique permissions, there is no option to create and the groups i.e owners, members, visitors etc

It would be better if Nintex for Office 365 will also have the "Common Reference" feature like the "Approve" and "Reject" link for fast and easy approval. It's also work on both PC and Mobile version.

I have a parallel approval scenario whereby I have a number of assignees. If one of the assignees rejects the task the approval process should direct stop and the outcome should be rejected, if all assignees approve the approval process becomes approved.

PS: In the on-premise version of Nintex this can be done with a flexi task.

Kindly advise

Ability to add notes to a variable describing it's overall purpose (not just for within an action)

Add a description box in workflow actions, so we can describe in detail, what the action does and why. This will help when transitioning workflows from development to support teams.

Create a centralized location where values can be assigned to constants for use across the tenancy or Site Collection by all workflows. Allows the use of consistent values for parameters. The values can be centrally managed so that all parties use consistent values that can be easily updated and immediately applied to wherever they are used. An example could be a discount rate used for financial calculations or a department cost center code.