We are finding the new Run If fields awkward. We think that the first two fields should be swtiched with the last field. I have an image attached as a sample of what it looks like today.

O365 Nintex workflow doesn't support those domains not managed by us. For example, some other organizations have their own O365 accounts so now when those users come on board, we need to create a Security Group in SharePoint group, add the external user into the group after he accepts the invitation. Then we need to add the user to the Security Group. Then re-run the workflow to grant permissions to the user. A lot of manual steps.

What's equivalent action to Retrieve data in Nintex online? If none, then what's alternative?

I have multiple site collections which store controlled master documents (Word format), once approved a PDF copy needs to also be made available from one central library location (open access for all staff). Copy to SharePoint action is sorely missed in O365.

What's equivalent action to Store data in Nintex online? If none, then what's alternative?

DocuSign actions should include support for Single Sign-On between DocuSign and Office 365. Currently, to authenticate a DocuSign user that utilizes Single Sign-On they must be added to an exceptions list, and it is unrealistic to add all users to the exceptions list as this defeats the purpose of using Single Sign-On.

The current 'Wait for Event in List Item' runs every time an item is added or changed in the current list. The GUID in that action is an output.

It would be great to have an action where the GUID is the input, so the action only runs when an item with that specific GUID is changed.

Currently the Update Item Permissions action does not support modifying permissions on external users (reason here:https://community.nintex.com/thread/12513). It would be great if this action could be updated to support external users, or if another action could be developed specifically to interaction with externals users who have been added to the SharePoint site.

In Nintex on-prem there is a function to decode XML values, so that special characters are no longer encoded, but shown as correct (eg. é, è, à,...).
In Office 365 this is not available, but you have to convert each value via a replace action (for each known special character). Is it possible to have an action which can decode the XML an easier way?

Allow the DocuSign Action "download document" to download all of the documents associated with the envelope. The difference would be to append Combined to the REST call that is already being sent. It would be and easy fix.

https://docs.docusign.com/esign/restapi/Envelopes/EnvelopeDocuments/get/

Example: GET /restapi/v2/accounts/1703061/envelopes/44efc9e6-915e-4b1d-9b54-801410d6922d/documents/combined

We moved from SP2010 to SPO and we need global task delegation back. When one of our employees goes on vacation, they need the option to delegate ALL nintex tasks to another user for a set date range. This "upgrade" to SPO and Nintex Online has been a nightmare for end users. Missing way too many important features.

Would be great to have the ability to pass the Start Workflow action values as start parameters.

Currently, none of the Nintex live actions support any multi-factor authentication. More and more clients are switching to this level of security and the lack of this support greatly inhibits our feature offerings. None of the live action advantages are available and clients can't switch to multi-factor authentication without breaking workflows that utilize these features.

Set workflow variable to able to set variable from the list lookup in another site.

The Update Item or Office 365 Update Item action should be able to set a Date/Time column back to a blank value, which is currently not possible.

If InLine functions are not being replaced in 0365 (which I really hope they are), how about more actions to help with common functions like padding out variable for use in Document title etc..

Would be great to have more workflow actions for site collection administration. Thinking about actions like "Set site collection administrator" or "Set sharing capabilities"