Database view to get Affected CIs and Impacted Services for Changes

Serkan Yilmaz
Tera Expert

Hi SNC,

There is a requirement to generate a Report for CAB to show all the Affected CIs and Impacted Services related to Changes.

Use case if we have a Change with 4 Affected CIs and 4 Impacted Services, the report should show 8 records with unique CIs/ Services.

Information that we need in the report:

CHG00001         Affected CI01

CHG00001         Affected CI02

CHG00001         Affected CI03

CHG00001         Affected CI04

CHG00001         Impacted Service01

CHG00001         Impacted Service02

CHG00001         Impacted Service03

CHG00001         Impacted Service04

Instead of the Database view result like:

CHG00001         Affected CI01         Impacted Service01

CHG00001         Affected CI01         Impacted Service02

CHG00001         Affected CI01         Impacted Service03

CHG00001         Affected CI01         Impacted Service04

CHG00001         Affected CI02         Impacted Service01

CHG00001         Affected CI02         Impacted Service02

CHG00001         Affected CI02         Impacted Service03

CHG00001         Affected CI02         Impacted Service04

CHG00001         Affected CI03         Impacted Service01

etc....

Tech. details:

Tables:

- Change request

- CIs Affected

- Impacted CIs

Who has a way to fix this requirement with or without a database view or scripting?

arnoud?

Cheers,

Serkan

6 REPLIES 6

Josh Cooper
ServiceNow Employee
ServiceNow Employee

Rather than generate a complicated report against it, I'd add them as Related Lists on the changes themselves, one tab for Affected CIs and one for Affected Services - then you could see them as you walk through the changes using the CAB Dashboard.   If you don't want to see it every time you look at the Change Request screen, then you can tie it to a CAB view, but I think it would be good information to have in general when entering your change.



Building it into a report is nice, but only useful when you run the report.   Using them as a related list is a reminder for anyone who works with that task that this change may have more impact than just the particular piece they're working with.


Hi Josh,



It makes sense to put the Related list on the Change form and this is already in place. This was done in the Change management stream, but from Reporting perspective, there is a need for a Report to show Changes with the related CIs. The users of this report want to see the related CI directly in one overview and don't wanna go through all Changes.



Cheers!