Assign a task without sending notification email
Currently, Nintex Workflow for Office 365 does not provide any out-of-the-box functionality to assign a task without sending notification email to the assigned people in the workflow. Can we have this feature to choose not to send email to the assigned people in the Workflow Tasks which was previously available in Nintex 2010 as option - "None".
So here are our use cases:
1. We are using "Office 365 update item permissions" to control who has the ability to edit list items. We only want the user who has been assigned a task to edit the item. Afterward, they only have read access. Default permissions are Add & View Items. Because the task id takes a while to get assigned and update the permissions, when the user clicks on the url in email notification to complete their task, it doesn't allow them to do so for several minutes. It would be great to be able to set the initial email notification to None and add the Send an Email node after the permissions take effect (task id found).
2. One of our workflows goes through 9 levels of approval. At level 5 of the approval process, a team reviews all of the open items. Then one of the team members needs to go in and mass approve/reject all of their open tasks for the items discussed in the meeting. They don't want to get all of the email notifications... just approve/reject through Workflow Tasks list.
Understanding the idea of not sending an email. Have you thought about instead of assigning a task(s) which uses the email, using the create an item action and then creating a task action in the workflow task list?
While this does not bind the original workflow and task automatically, it is possible to do this and thus create a parent item and a child task.This would allow the user to view their task as normal from the list, and avoid the email issue. They can also complete the task in the workflow task list.
However, in order for this to work as it does using Nintex, you may have to create a child workflow that monitors the status of the task(s) and updates the parent item when the task is approved/rejected, or completed. Again completely doable but not as easy as using the assign a task action within Nintex.