- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12 hours ago
We have recently noticed that any time a change request is submitted - regardless of model used - a Sidebar discussion titled "Refresh Impacted Services" is started. This is not a discussion that we need displayed and users are finding that those messages are cluttering their sidebar and causing them to miss other important messages. Is there a way to stop that event from creating a discussion?
Solved! Go to Solution.
- Labels:
-
Change Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
According to ServiceNow docs/community, com.snc.change_request.refresh_impacted.event controls whether the impacted services refresh is done via an event rather than inline in the user transaction.
I won't have any impact on the functionality.
- If it is false, the logic runs in the user transaction instead (synchronously).
- if it is true, the “refresh impacted services” logic is queued as an event.
please refer link Automated Change Impact Assessments
Thanks,
Vignesh
"If this solution resolves your issue, kindly mark it as correct."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
To stop the "Refresh Impacted Services" message while keeping the functionality:
Go to System Properties (sys_properties) in the Application Navigator.
Search for the property:
com.snc.change_request.refresh_impacted_services.message.showSet its value to false.
Refresh impacted services properties
Thanks,
Vignesh
"If this solution resolves your issue, kindly mark it as correct."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
Thanks @vignesh parthib - that property was already set to false, we were still getting the notifications. I also set this one to false - com.snc.change_request.refresh_impacted.event and that seems to stop them, but I'm now trying to confirm that there is no negative impact with that setting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
According to ServiceNow docs/community, com.snc.change_request.refresh_impacted.event controls whether the impacted services refresh is done via an event rather than inline in the user transaction.
I won't have any impact on the functionality.
- If it is false, the logic runs in the user transaction instead (synchronously).
- if it is true, the “refresh impacted services” logic is queued as an event.
please refer link Automated Change Impact Assessments
Thanks,
Vignesh
"If this solution resolves your issue, kindly mark it as correct."