Adding CIs (another entry points) to Application Service Service Mapping after tag-based discovery

[Marcin Musiol]

Dear Community Members,

I'm facing a problem in relation with CSDM and proper Service Mapping.

We already discovered a lot of CIs and Application Services from Azure Tag-Base and that works fine, we can see all CIs in Service Mapping.

The challenge is to manually add CIs (because we know that some services are running both Cloud and On-Premise) but the 'Add Method' button is greyed out.

I've red in the documentation that this is a normal behavior https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/service-mapping/task/... but we need to make it done.

I can create classic relationships in cmdb_rel_ci table but the CIs are not visible from Service Map perspective.

Did someone got stuck with a problem like this?

Thanks in advance for help and have a great day!

Marcin 

[Marcin Musiol · Accepted solution]

Hello all,

I want to share my solution for this problem. I get also a response from NowSupport and from the functional perspective there should be no impact when following this approach.

1. Check your Application Service tags (below is real environment but I will present the approach on my Personal Developer's Instance). 

Any Ci needs to have 3 entries in cmdb_key_value table: ENVIRONMENT, COUNTRY, APPLICATION.

2. Add necessary entries in cmdb_key_value

3. From the Application service's related links choose Recalculate service. 

4. View results in Service Map

5. cmdb_rel_ci table entries will be autopopulated

This approach enable user to add CIs to already defined Service Map that was populated by Tag-Base.

Take care!