How 'Impacted Services/CIs' related list works on Incident form based on affected CI?

[Suggy]

How exactly 'Impacted Services/CIs' related list works on Incident form based on affected CI??

Official docs link - https://www.servicenow.com/docs/bundle/xanadu-it-service-management/page/product/incident-management...

I understand there are certain system properties based on which this gets controlled.

I also read on few posts that, with Service Mapping vs without Service mapping, the way Impacted services related list gets populated varies. but still I did not get clarity.

Whoever is aware of this topic, can you please share the details as to how exactly 'Impacted Services/CIs' related list works on Incident form (like from which table refers the data? what happens when multiple CIs are added in impacted CIs?) etc

NOTE - PLEASE dont give link to docs or other community posts. I have already gone through many and none of them provided concrete details.

PLEASE share the details if you are really clear on this topic 

THANKS a lott in advance!!!

[Suggy]

No one?

[Prabu Velayutha]

@Suggy check these two BRs runs on the task table to sync the impacted services and affected CIs.

Sync BS with Impacted Services
Sync CI with Affected CIs

If you add affected CI(cmdb_ci) single/multiple CIs manually in the Incident record it creates a record in m2m table "task_ci_list" similarly if you add Service/Impacted service (business_service) it creates a record in m2m table "task_cmdb_ci_service" the above BRs will trigger on the task table to create/delete records in these two m2m tables to key the incident record in sync with affected CIs and Impacted Services based on the user updates. 

[Suggy]

Hi @Prabu Velayutha I wanted to understand - 

How exactly 'Impacted Services/CIs' related list works on Incident form based on affected CI?

[Chae]

This topic can help to understand ;).

Solved: Difference between Affected CIs and Impacted Servi... - ServiceNow Community