Assigning Task to Multiple Approvers
Allowing a task to be sent out to multiple users/ approvers would be helpful in some situations. I have tried many workarounds with fiddling with variables and keep getting an "invalid email format" error. The only workaround I have found is creating email distribution groups within my org, which is a very messy workaround.
Thanks for reaching out!
You’re right, unfortunately there is no work around for adding multiple email addresses to a Task action, other than to assign tasks to an email distribution list.
The good news is Multiple assignees for Assign a Task is already in our backlog, and awaiting prioritization.
Just to get a better understanding of your scenario, to ensure we’ll satisfy what you’re trying to achieve:
- How many assignees would you typically configure in your Task action?
- Would you expect all assignees to approve the task before proceeding?
Let me know if you have any other questions or concerns!
Thanks for your patience,
Wouter Ernsting commented
I mostly agree with what Chris says, I believe in essence this should mimic the functionality of Nintex for O365 where you can pass the action a semicolon delimited list of assignees and set parallel/serial approvals, % response on a particular outcome etc.
Is there a confirmed launch date for this feature yet? It seems like after more than year this should be ready to go?
Our organization really needs this badly so we don't have to manage a growing number of google groups. For our processes groups could be as large as 10 people but I could see that growing in some cases, particularly if we move another one of our processes to Nintex.
Our processes assign a single task to a group of users and any person in the group can approved and complete the task. I would be hesitant to put a max number of supported email addresses.
I would like to see the assignee continue as email addresses, but support multiple. This is a much more flexible approach.
This would be awesome for Managers who have an Exec Assistant who assist with their approvals.
For our company, I would like this feature to allow the same task to be sent to a primary recipient, but allow for an additional person (or more than one) to be listed as an alternate that can close out the task as a proxy for the original owner. I don't want to delay the process by using escalation.
Kevin Kittinger commented
This would be highly needed, from our organization point of view we can run anywhere between 1-10 people as assignees to tasks that we need either multiple tasks created for each user or one big task. Then some we have set as all have to Approve, First response, and the majority answered.