How does 'subscribe' notification work for CI?Issue Overview Subscribe CI feature is to let user know that if any incident is reported for CI or not.This is useful for asset or ci owner to monitor if any critical incident happened for their CI. How does 'Subscribe CI' feature work? When user subscribes to CI, it creates a record in the "sys_notif_subscription" table. sys_notif_subscription table stores details about user, notification, device and table. If incident is submitted for the CI which the user is subscribed to "Affected ci notifications" business rule will fire to an generate event "ci.notification.for.task". This event does not have any notifications against it. But it has a script action i.e. "Handle Affected CIs for Task". This script will call Script Include "CMDBAffectedCINotificationsUtils" method "handleTaskAffectedCIs" with parameter as sysID of the task record. Now the method "handleTaskAffectedCIs" has all the logic to get the affected CIs and subscriptions from table "sys_notif_subscription" and "cmn_notif_message" to generate "ci.affected" events. "ci.affected" event parameters will have ci's name & sysid of the affected CI which will eventually trigger the notification "CI affected" "CI Affected" is a subscription notification. Notification engine will trigger notifications ( email or sms ) for all the user who are subscribed to the affected CI. Additional Information -Search "Subscription-based notifications" in the doc site to know more about subscription feature. Subscription-based notificationsRelease-allResolutionMake sure BR "Affected ci notifications", Script Action "Handle Affected CIs for Task", Script Include "CMDBAffectedCINotificationsUtils" and notifcation "CI affected" is not customized.