Notification "Subscribable" option

spike
Mega Sage

Can someone please help me understand the notification "Subscribable" option?

 

I've read through the forum and through the ServiceNow docs but nothing seems to explain what I'm seeing or how it is meant to work.

 

I've created a new notification that triggers an email when a certain incident field is changed. This works fine and my teams channel gets the email.

 

I want people to be able to subscribe to this notification so they get the email as well. Therefore I've selected the Subscribable tick box. Looking at a user's notification preferences the notification appears in there, and "Primary Email" is true. Therefore I'm expecting that user to get it. They don't. The user doesn't get the email regardless of the Primary email setting.

 

If I untick the Subscribable box, and look at that users notification preferences, the notification is still there, and still has a toggle against "Primary email" that can be on or off. And the user doesn't get the notification under any toggle setting.

 

Can someone explain to me how this is meant to work? At the moment I can see no point to the Subscribable option. The only solution I can see is to add the users (individually or via a group) to the notification to ensure they get it.

 

Surely I'm missing something?

 

Many thanks!

6 REPLIES 6

XvE
Tera Contributor

Good day,

 

Not sure if you found the reason for this not working as you expected, but to me it seems like the following line explains the issue:

 

"Administrators should create subscription-based notifications when they do not want to specify users for a notification and want to let users proactively subscribe to the notification."

 

I tested this in one of our sub-production instances and the personal notification did not get sent if I added a group through "User / Group in Fields" to the notification, whereas when I left that field empty it did send to my personal notification (subscription).

 

The test notification I created, ran off a fired event, I am not sure what would happen if it triggers off of a condition.

 

btw, if someone could explain to me what in the world the field "Affected field on event" does...
Whenever I set that to either Parm1 or Parm2, the notification did not send at all 😞

Craig Tinsley
Tera Contributor

Same situation here .. User reported NOT receiving a notification while the rest of his team did. I checked the "cmn_notif_message" table, and there was an entry for him on his "Primary Email" (message went to the team he was on BUT he didn't receive it). I checked his preferences, and he did NOT have this notification  selected. Upon selecting it, he began receiving notifications, BUT the entry in the "cmn_notif_message" table didn't change (ZERO fields were updated).

 

That said, is there a different table to see which notification preferences are actually activated for individuals?