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.

Assigned tasks must be deleted/canceled as well, so the user can not approve/reject tasks which are already terminated.

I would like to be able to say "wait for the field to change to this value OR that value, then do this action" - there is currently no option for entering multiple values.

There should be an option to return all of the indexes, or the index of the first result, where this action finds an item in the collection. This would help greatly in processing collections and improving execution time.

It would be very nice if you could export the whole workflow to a PDF or other format, for easy documentation or printing.

The O365 Update Item is restricted specifically to documents or items, it cannot actually update a Document Set or Folder Item. There are many cases where we need this specifically with Document Sets. The CAML query used to select a Document Set does not work in Nintex, though it works in PowerShell, CSOM, Javascript, REST, etc.

As like on premise Nintex we require APIs/web services to do the following actions.

1. Start the workflow.

2. ProcessFlexiTaskResponse2.

3. Publish workflow

4. GetFlexiTaskOutcomes

5. API to delegate a task.

6. API to configure long term delegation

Same as the Run If action, but add an Else branch to it.

I recently try the Nintex Mobile App with our O365 SharePoint site. It's working well and i was surprised by the design on different devices and OS.
It could be nice to improve this app with the ability to manage his tasks from his mobile and not just be able to fill a new form.

It would be great to have a From field that supports dynamic references. Most business requirements want emails sent from a specific account, which is not supported in NW in O365!

Similar to the On-Prem action. Being able to copy List attachments to a document library with associated metadata if columns exist

The office 365 Send document to repository action should be capable of taking a document from a document library and moving the document into a repository on another site.

The ability create copies of current list items (workflow context) should be included.

Are you looking to support the management and creation of 'External Users'?

Please enable following in Email bodies so that developers can verify the true content they've configured.

1. Any hyperlink in Email bodies is shows as:
reflink="nw-stringbuilder-token-661c62d8-cd92-4f10-9273-e643486faf71" reftext="nw-stringbuilder-token-8596239b-6d13-445a-8bf0-7f58bfe9571b"

Nintex on-prem:
reflink="{Common:WebUrl}/IMPD Process Documents/Forms/Approved Documents.aspx" reftext="here"

Please enable actually inserted hyperlink. Otherwise, they only to find hyperlinks is via running workflow, which is not always possible.

2. When developer clicks on any content within email body and later clicks on View HTML, the cursor should point to corresponding position in within HTML. While it works in Nintex on-prem, in Nintex Online it points to the end of the email body.

In SharePoint On-premises a power-user have the ability to make Comments mandatory or optional for each task-outcome. This feature is not available in Nintex Online.

it will be great if Nintex can enable same for Online as this will help power users.

Pls. improve *Assign a task* and *Start a task process* and enable following:
1. Number of times to repeat to take dynamic values. Currently number of reminders must be hardcoded
2. Delivery type for actions to to include *None*. Currently it's mandatory to configure emails for assigned taks

Currently Nintex Online does not allow a way to toggle manual start for site workflows.

Case: As Nintex on-prem has this setting, any site workflow with such settings gets migrated as-is. As tools like Sharegate does not have a way to reset the flag, the migrated workflows could never be run manually.

It is fantastic that Nintex enabled its users to send email to people outside of an Office 365 tenant. However, there is no way to block/stop/prevent that from occurring, if such an action is in violation of a company's policies.

Therefore, it would be great if there was a checkbox that allowed that function to be disabled for a given customer's tenant (but still permit the option to use attachments for internal users).