subscribe to a CI doesn't trigger any events
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-17-2018 11:57 PM
Hi,
I trying to understand what the 'Subscribe' UI action in a CI does and how it differs from the 'Subscribed by' that can be added on a CI under 'Related Lists':
Clicking the 'Subscribe' link adds a does not add as Notification Subscription in table sys_notif_subscription and adding a user under 'Subscribed by' using the Edit button adds the user in table cmdb_subscriber.
The sys_notif_subscription relates to email notification 'CI affected' on the incident table triggered by event ci.affected.
However even if I activate this ootb email notification and I add a subscribed CI to an incident under the 'Affected CIs' tab no email is attempted sent and looking in the event log I don't see the ci.affected event triggered.
I suppose the Business Rule on the task table named 'Affected ci notifications' should trigger this, but it doesn't seem to work?
And what does the 'Subscribed by' adding a record in table cmdb_subscriber do?
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-18-2018 07:01 AM
Hi Kristian
I have testet in a personal developer instance, and when i click Subscribe on a CI and item is added to the sys_notif_subscription table.
If this does not happen for you, check the value of the system property "glide.notification.use_legacy_subscription_model". You might be running the legacy version.
When also remember that the business rule is running on "update" on the task form. There is no update to the incident when you add ci to the affected CI list. So the event will only be generated when you do a modification to the incident it self AND there is an affected ci AND somebody is subscribing.
I don't know what the purpose of the Subcribed by table is and others are also wondering: what is the use of table cmdb_subscriber?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-12-2019 11:49 AM
The glide.notification.use_legacy_subscription_model property recommended setting from Helsinki and later is 'false'. it is not generally documented, because its intended use is limited. It is not like other properties that can be switched back and forth without side effect.
Anyone who has set this to 'true' to keep the old subscription model can run into some interesting and subtle issues on platform notifications.
We have put together KB0750659 to provide a better understanding of the glide.notification.use_legacy_subscription_model property.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2022 11:22 AM
I know this is way old but in case anybody in my scenario - finding this legacy property still set to true - wants to find more info, Dub didn't share the KB article permalink so that link (to an old article version) is now broken. Here's the permalink to the article that works: