👋 Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you are looking for the Nintex roadmap, you can find that on Nintex Community
If you have questions about Nintex Ideas, please contact email@example.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact firstname.lastname@example.org
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.