Does anyone know how ci.affected and location.affected notifications work?

[DrewW]

Does anyone know how ci.affected and location.affected notifications work? I can not find any business rules that trigger these events, yet I know in testing I have gotten the ci.affected notifications. I am not getting the location.affected ones thou and I am trying to figure out why not. SNC appears to have dropped it from there base build, since I can not find a notification for the event "location.affected" in the demo system.

[ayeshamubeen]

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.

[ayeshamubeen]

when you subscribe to a ci and raise an incident with the subscribed ci , that is when ci,affected is trigerred.

[Mahendra RC]

Hi Drew,

I can see the BR written for ci.affected and location.affected event to trigger the notification on my developer instance. Below are the details:

BR Details:

Name : Affected ci notifications

Table : Task

Name : Affected location notifications

Table : Task

Below is the screenshot for location.affected event:

Please let me know if you are looking for something else OR if I didn't got you correctly.

Please mark it correct, if it resolves your problem.

[Mahendra RC]

Hi Drew,

does it resolved your problem?