population of impacted service/CI under change request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2019 09:57 AM
HI Experts,
I would like to know the detailed process on how impacted service/ci related list is getting populated under change request. I can see there is a script include and refresh impacted service UI action(OOB).
can anyone explain in detail, how the impacted service/ci related list is being populated as I can see for one CI, there are 680 impacted services are being populated(but I dont see 680 direct relationships) and for one CI, there is only 1 impacted service/CI is being populated.
please suggest. its very urgent.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2019 08:40 PM
Hello,
If you look at that UI Action, you'll find that it triggers the following code:
new CIUtils().refreshImpactedServices(current);
On checking the script include CIUtils, you will see that it initializes the following values to be used in the functions:
You can see the highlighted line, it retrieves the value of the glide.relationship.max_depth property to determine how deep to check the relationships. If the property is not defined in the instance, it will take the default value mentioned, i.e., 10. Meaning it is going to do a nesting till 10 levels to find the related CIs (it doesn't just look at direct relationships).
Hope this helps!
Cheers,
Manish