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.

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.

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

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.

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"

Create a tab that lists favorite actions. This would allow to easily access actions that you use a lot (like log history), instead of having to scroll through all those tabs.

It would be very handy to include the ability to send a Task email to a mailbox. I understand that a task needs to be assigned to users, but the ability to send the task email to an email address and not to assignee's would cut down on email clutter when a task is assigned to a group of users but only needs to be completed by one user.

Create an action that automates the provisioning of Office 365 groups.

I think it's extremely important that Nintex Workflows can perform cross site actions such as updating items in another site using the standard actions. Nintex Workflow, being the leading SharePoint workflow add-on, really should provide this no-braining functionality. Thank you.

Hello,
Is there any chance to prepare something like [FileData] from on-prem version?
I would like to use document content as Base64 in Nintex Workflow for O365 but without success right now.

Thank you

Should be able to copy a SharePoint file to a network fileshare location.

It would be great to add simply "current Item" to the "Items to update" scope for the Office 365 Update Item Permissions online workflow action.

This would greatly simplify the action and make it clear that the item permissions being affected are only the item permissions that correspond to the item the workflow is currently running against.