What is the real difference when setting 'change.refresh_impacted_ci'' it to TRUE or FALSE when impacted services are refreshed?Issue When system property 'change.refresh_impacted.include_affected_cis' is set to TRUE, only the first level of dependent application services are listed while when it is set to FALSE all dependent CIs (Continuous Integration) are listed. ReleaseSupported environmentResolution As per our documentation:https://docs.servicenow.com/csh?topicname=r_ChangeManagementProperties.html&version=latestchange.refresh_impacted.include_affected_cisLists the impacted CIs or Services with any service supported by a configuration item identified in the Affected CI related list.Note: This requires any business services identified to be converted to an application service. For instructions, see Convert a business service to an application service. For information about application services, see Application services.When change.refresh_impacted.include_affected_cis is false it only looks at one CI record attached to the Change Request (and then walks the tree to find impacted services which means using the Affected CIs related list of more than one CI has potential performance issues. so the team that owns this functionality changed to a different approach, i.e. using Application Services.When change.refresh_impacted.include_affected_cis is true, the Impacted Services must be converted to Application Service (and this conversion process requests the user to select the dependency depth - so yes there is a depth limitation chosen by customer), this has a flat table structure, so no walking the tree and therefore scales much better. Related Linkshttps://docs.servicenow.com/csh?topicname=r_ChangeManagementProperties.html&version=latest