What is the use of 'refresh impacted services' ui action in the context menu in Incident application

[Suggy]

What is the use of 'refresh impacted services' ui action in the context menu in Incident application?

Once the CI is selected in the Configuration item field, upon saving the inc form, will the impacted services related list automatically populate or should we manually click on  'refresh impacted services' UI action?

If it gets populated automatically automatically upon saving the form, then why that UI action is given?

[Ravi Chandra_K]

Hello @Suggy 

It will automatically populate upon saving the form. (provided the relevant properties are set).

if there are new impacted services that gets added, you can click on the ui action at a later point of time to fetch updated services.

Please mark the answer as helpful and correct if helped.

Kind Regards,

Ravi Chandra

[Suggy]

@Ravi Chandra_K 

May I know what exactly you mean by

"if there are new impacted services that gets added, you can click on the ui action at a later point of time to fetch updated services." ?

If you mean "if there are new impacted CI's that gets added", then why not again upon saving the form the impacted services get added?

or you meant something else?

[Suggy]

Anyone??

[Runjay Patel]

Hi @Suggy ,

The 'Refresh Impacted Services' UI action in the Incident application is typically used to update the 'Impacted Services' field in an Incident record.

When an incident is logged, the 'Impacted Services' field is often populated automatically based on related Configuration Items (CIs) or service relationships defined in the CMDB'. However, changes in relationships, updates to the CMDB, or manually updated incident data might make the existing list of impacted services outdated or incomplete.

Key Points:

1. If the related CIs in the incident have been modified or new dependencies were added, it ensures the latest service impact is reflected.
2. When the CMDB has been updated with new or corrected relationships, using this action ensures the incident is synchronized with the latest data.

When you click 'Refresh Impacted Services', the system executes a script or business logic to:

1. Identify related CIs associated with the incident.
2. Traverse the service dependency hierarchy to identify upstream or downstream services impacted.
3. Update the 'Impacted Services' field in the incident.

Use Case Example:
An incident is logged for a database outage. Initially, the impacted service is identified as "Database Service."
Later, it is updated that this database supports "Online Banking Service."

Solution: Clicking "Refresh Impacted Services" updates the incident to include "Online Banking Service" in the 'Impacted Services' field.

This UI action is especially beneficial in environments with complex service hierarchies or dependencies, ensuring incidents reflect accurate service impact for better prioritization and resolution.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------