In the 'Assign a task' action in Nintex for Office 365 and Flexi task for Nintex for SharePoint there is an option to CC or BCC the task notification email.
Please add CC and BCC to the NWC 'Assign a task' action.
This is important as we migrate from the feature rich Nintex for SharePoint or Office 365 to NWC.
I have many users in my company requesting this functionality, can you please prioritize for your next quarterly review?
Thank you all very much for posting your feedback on Assign a Task to Multiple Users. At this time, we will not be moving this request to the near-term backlog, as we are focused on other critical initiatives. However, we reevaluate requests every quarter, so please keep the feedback coming as it is critical for our longer-term planning.
Is there an ETA for this one? Last update I received was the end of Feb by our success team. I don't see this available yet. Please advise.
Thanks for the prompt feedback and clarification on this one. Greatly appreciated. :)
Yes, that's correct - Assign a Task action is being removed this week. This functionality would be added to the Assign a Task to Multiple Users action in Nintex Automation Cloud.
Thank you for your feedback. The Cc/Bcc functionality for task notification is being targeted to be included in the next 3-6 months.
+1 to this although ideally there would be an option to assign a task as a "CC" in addition to the email aspect. Further, a task level configuration should be available to determine who can complete the task be this: the primary recipient(s), the CC recipients or both.
So, is this being added? We really need this functionality soon. Most of our users use the task email to follow-up with approvers of a task. They also don't know if the email for the task went through to specific task owners and they get a bit nervous too.
My recommendation is to use a "Run parallel paths" action, with an "Assign a task" action in one branch, and "Send an email" in the other. The email is used as the notification that a task has been assigned, and while it's not a CC or BCC, at least you have communication around the task assignment.
If you have any feedback about this workaround, let me know. While I understand this could work for some processes, everyone's needs are different. If it doesn't work for you, please expand on why, so our product team has more context about how to integrate this capability natively.