Refresh Impacted Services - Impacted Services/CIs | Business Applications related lists

[Dan Brown2]

Hi 

When I add the Application Service within the red box to the Change form as the configuration item, and select the 'Refresh Impacted Services' UI Action - the ticked Application Service gets added to the 'Impacted Services/CIs' related list and the ticked Business Application get added to the 'Business Applications' related list, but the Business Application with the red cross doesn't.  I would have thought it would, does anyone why that might be the case?

But if I add the Server to the list then all 4 are added, as I would suspect.

[Christian Prob2]

Dan, What are the relationships between the Business apps and the app services? Christian

[Dan Brown2]

Hi Christian - it is Consumes::Consumed by

[Barry Kant · Accepted solution]

Hi Dan, 

I guess this is due to the (default) property setting for refresh impacted services for change:
com.snc.change_request.refresh_impacted.include_affected_cis (default = TRUE)

the side-effect is that it validates snc_ci_assoc relations rather than cmdb_rel_ci relations.
you can verify this to change the setting to FALSE. Then I expect it will be populated. 

What you can do if you still want the default setting (TRUE --> then it also takes the Affected CIs related list as input) is to reclassify the Application Services (cmdb_ci_service_auto) to Calculated Application Services (cmdb_ci_service_calculated). what this does is that for each cmdb_rel_ci record from a Calculated Application Service it creates a Manual Endpoint in the svc_ci_assoc table (keeps it in sync) for a certain nr of levels downstream (default = 3).

it behaves then similar as Mapped Application Services but it doesn't require ITOM Service Mapping. 

There are good articles in this community that explains this part in more details:
Application Services : How to use them
Application Services : Tips and Tricks

hope this helps.

Good luck,

Barry

[Dan Brown2]

Thanks Barry - I think you are right - after testing it does appear that the property is best set to False to get it working better for us.