Application Service missing Business Application for Dynamic CI (child) App Service

[lindacharles]

We are working on building out our Application Services and connecting them to our Business Applications.  In using the CSDM Data Foundations Dashboard and following the playbook for Application Services missing a Business Application relationship, we are seeing that Application Services that are formed by Dynamic CI groups and have a child relationship to an Application Service which has a child relationship to a Business Application are indicated as Missing a Business Application. https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0831503

So for example, if we have 

(Business Application) XYZ --> (Application Service) XYZ Prod  --> (Dynamic CI App Service) XYZ Dynamic CI

it is in the list of "App Service Missing Business App Relationship"

How do we resolve this?

[Barry Kant]

Hi Linda, 

not sure about the exact scenario, but why don't you do it like this:
(Business Application) XYZ --> (Dynamic CI App Service) XYZ Prod Dynamic CI

Looks to me that (Application Service) XYZ Prod  --> (Dynamic CI App Service) XYZ Dynamic CI are representing the same function (a logical representation of a stacked solution)

I only use Dynamic CI Groups as App Service level for grouping consumables or printers in a logical way. 


BR,
Barry

[lindacharles]

In our setup there may be several Dynamic CIs that are part of an Application Service, so we had them under the App Service instead of directly connected to the Business App. 

[Ed Laar]

Hi Linda,

Using a Dynamic CI group to represent a stack of infra components seems not to be the intended use case. According to the CSDM model a Business Application consumes an Application Service. When this relationship is not there for whatever the reason an issue will be reported as this relationship is prescribed by CSDM. Without this relationship certain capabilities for example in Application Portfolio Management will not work but ITSM processes will work as they do not use this info.
A Dynamic CI group is intended to be used to, dynamically following its filter criteria, group certain CIs together and relate them towards a Technical Service Offering: a Technical Service Offering contains a Dynamic CI group is the prescribed relationship here. Involved infra CIs are shown using a Related list. Use case: I have a TSO that applies to printers of a certain model in a certain region. As soon as I add a printer of that certain model in that certain region the TSO automatically contains the added printer. Synchronizing multiple groups from TSO towards CI's in the scope of the Dynamic CI group is an OOB capability. Doing that the groups on CI level can be used for ticket assignment (although I prefer to look for the groups on the TSO itself as that also works when no Dynamic CI group is used).
Dynamic CI groups are registered in the cmdb_ci_query_based_service table with Service Classification = Technical Service. Also from this point of view a Business Application related to a Dynamic CI group is 'strange'.

Hope this helps,

Ed

[lindacharles]

I opened a case with ServiceNow Support and received this information:

The basic condition for an "application service missing business application" is below:

parent is app service but child is not business app
OR child is app service but parent is not business app

A CI is considered app service as long as it belongs to below classes

cmdb_ci_service_auto
cmdb_ci_service_discovered
cmdb_ci_service_by_tags
cmdb_ci_service_calculated
cmdb_ci_query_based_service

If we use one of the CIs listed in the CSDM metric report result we can see that this CI belongs to cmdb_ci_query_based_service, which is an application service.

Next Steps:
1. Per update from DEV team, please link/create relationships to these application services with business application CIs.

I don't understand how are Dynamic CIs both an Application Service and a Technical Service?