Affected CI subscription notifications - What triggers them?

[JGilman]

Apologies if I missed this on the Wiki or in this forum; I see lots of discussion regarding the ability to subscribe to individual CIs, but I don't see **what** triggers the notification?

I see the business rule "Affected CI notifications" but there is no condition on it.

On a Change request, when are the affected CI notifications issued? When the CI is first related? When the Change is submitted for approval? When the Change is approved?

Thanks in advance.

[Brandon Grimes]

From my understanding, the business rule "Affected ci notifications" runs asynchronously every time a record on the "task" table is updated. Since this rule runs on the "task" table, then all tables extended from task are included.

This business rule will query the "task_ci" table (aka find all CI's related to the task record). An event called "ci.affected" is fired for each affected CI. "event.parm1" contains the CI sys_id, and "event.parm2" contains the CI display name. The parent CIs of each affected CI are also queried and the same event is fired for them.

An email notification called "CI affected" and type "Subscribable" will pick up this event.

[rakesh18081989]

Hi Brandon,

Thanks for your response I have one query who is the notification sent to.

So will all the user who subscribe to the CI will get the notification irrespective of the affected CI.

If yes, is there a way a user get notification for those CI for which he is primary owner or he subscribe that CI.