Skip to main content

After the Spring '20 release that enabled queues for Tasks (@Anand Rohra), I've run into issues on ways of notifying the members of these new Task records. I understand that the help docs mention that notifications only go out when a user is assigned a Task but I'm struggling adopting this feature if I have to explicitly add in extra steps of automation to Send Email Alert or Send Custom Notification for each and every time I want to create something via Flow/Apex to a Task queue. In my small org, I've ended up creating multiple tasks assigned to different people for the same unit of work that only needs completing once. Definitely not ideal. And sadly, my users are oddly averse to refreshing list views or checking bell notifications...

From my understanding (and I may be wrong), this issue is only applicable to Tasks. It works as I would expect it to for other custom Objects (and likely standard too). I've seen this Idea Task Queue Notifications-Trigger Queue Notification Email for New Queue Records which basically covers most of what I'm concerned for.

 

  • What I'm curious is if this is even on the radar (not necessarily 'roadmap') of the product team since it's a slightly newer feature but has some real parity issues with Queues.
  • Are there ways I'm missing on how to notify users easily for Task queues? 

Otherwise, I'm leading towards having to do some CMDT table finangling to assign users individually. 

If there's a better trailblazer group to ask this in, let me know. It seems that there's low engagement here -- and most of them are advertising webinars.

3 answers
  1. Jan 24, 2023, 9:54 PM

    I used the Queue ID in my decision and Labeled each decision option as the Name of the Queue.  I then created an email alert for each queue so that I can select the users it should send to.  It makes changing queues and off-boarding a little cumbersome, but it was the best thing option I could come up with at the time.

0/9000