Incident and Change Impacted locations

[Chaz_]

Hi,

We have a requirement to be able to view impacted locations on changes and incidents as described below. This seems to demand a high amount of processing for each change/incident, especially as unique sites are being requested. 

• Show a related list "Affected Locations" on Incident and Problem forms.

• When Configuration Items (CIs) are updated:

  • Pull unique locations (preferably site-level, not too granular).

  • Add them to the Affected Locations list

Is there a sensible way of introducing this but limiting performance impact? What is best practice in this scenario? A change could have hundreds of CIs, and viewing the location in list view could be difficult.

Thanks.

[Dr Atul G- LNG]

Hi @Chaz_ 

The idea isn’t bad, but the point is—how are you building the relationship between Location and CI?

Are you doing it in the same manner as we manage CI relationships?

[Chaz_]

Its generally stored in the location field across Infrastructure CIs. But for services, it is held in a different field. In all cases, it is held as an attribute rather than a relationship.

[Dr Atul G- LNG]

Yes, you can achieve that, but you’ll need to build a strong logic—similar to the logic used for Impacted Services/CI in the OOTB (Out of the Box) setup. That would be the better approach.