Where is the CC and BCC option on Assign a Task Action
We currently have multiple Task improvements planned for Q1CY20 and will include CC/BCC fields for both Assign a Task and Start a Task Process actions.
Jonathon Fung commented
CC needed for Task Reminders on O365. I've had multiple projects now where the business does not want the task to be reassigned to other users on escalation. Instead they want the escalation user to be notified instead. If a CC were available in the reminder feature, this would work for the scenario. Alternatively, allow an email option in the Escalation would also help.
Sridhar Kandadai commented
Do we have any update on this request
Since lazy approval does not have the ability to identify the individual approver (approved by SharePoint App doesn't work for audit). We have a possible work around if we can use bcc in the approval emails
The BCC would basically be to check emails have gone out. There is no visibility other wise. We can see the tasks have been assigned - but not if emails have arrived.
BCC is for a CYA scenario... as in Cover Your .... this is needed to send a copy of all notifications to a mailbox to ensure it was sent and received so we have something to back up our claims
We need this to check emails sent by our workflows. Instead of going inside SharePoint and see what happens, we can just look through our shared mailbox and look if emails are being sent out properly. If we do not see the email it means something is wrong in the workflow and we need to go inside and investigate.
Rhia Wieclawek commented
Users often need to do an "FYI" to other users but not assign them in the task.
This would be useful in ticketing systems built within Nintex where all tasks may need to be BCC'd to a manager, but not seen so that another user doesn't respond to that manager.
We use it in the scenario where the manager logs a request which the employee needs to sign-off before it can go to the next manager for approval. We would like to be able to cc: the creator in when the task is assigned so they can followup if the employee has not responded (in case there is any issues e.g. they didn't receive it, or it went to junk mail etc).
Also as per other comments, "Bcc is useful for workflow admins during the test phase of a workflow, as you can monitor the workflow in it's early stages to ensure emails are being sent without an impact to business processes."
We use it in the same way that others have mentioned (for cc'ing Managers or other staff as required, so they are 'in the loop' but are clearly not the task owner).
Bcc is useful for workflow admins during the test phase of a workflow, as you can monitor the workflow in it's early stages to ensure emails are being sent without an impact to business processes.
unfortunately none :(
We need to be able to CC other users on a task but not have it assigned to them.
Dan Beck commented
There should be a CC field on tasks so that people assigned can easily reach out a process owner if there are questions / comments that need to get captured in the form. This field is available on-prem