The CreatorCon Call for Content is officially open! Get started here.

Side Bar discussion - Refresh Impacted Services messages

Beth Clingenpee
Giga Guru

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?sidebar discussion.png

1 ACCEPTED SOLUTION

Hi @Beth Clingenpee 

 

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."

View solution in original post

3 REPLIES 3

vignesh parthib
Tera Guru

Hi @Beth Clingenpee 

 

To stop the "Refresh Impacted Services" message while keeping the functionality:

  1. Go to System Properties (sys_properties) in the Application Navigator.

  2. Search for the property:
    com.snc.change_request.refresh_impacted_services.message.show

  3. Set its value to false.

Refresh impacted services properties

 

Thanks,
Vignesh
"If this solution resolves your issue, kindly mark it as correct."

Beth Clingenpee
Giga Guru

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. 

Hi @Beth Clingenpee 

 

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."