Convert to Tag-Based population method

[Ronald Lucas TA]

We have manually created Application Services and now want to use Service Mapping to populate these using the Tag-Based population method.

Has anyone converted a manually created Application Service to a Tag-Based Application Service?

[Community Alums]

Hi @Ronald Lucas ,

You can refer to this ServiceNow doc , which should help you :

https://docs.servicenow.com/en-US/bundle/sandiego-servicenow-platform/page/product/configuration-man...

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[Ronald Lucas TA]

Hi Sandeep. 

That document doesn't cover how to migrate a manually created Application Service to a Tag-Based Application Service.  I am able to create new Tag-Based Application Services as the document explains.

Thanks,

Ron

[Philip Hulshize]

I too have found the documentation lacking, and converting from a business service to an application service leaves me stuck at manual. I cannot find any way to convert. In addition, my thought is, what if you mature from Tag based and want to go top down discovery (or the opposite way around)?

Sorry this is not an answer but more of confirming what you are seeing.

[Ronald Lucas TA]

In our case, we have been creating Application Services which were being stored in the Mapped Application Service (cmdb_ci_service_discovered).  Our method of relating CIs to these Application Services didn't utilize the CSDM Application Wizard to select a population method.  Instead, we used the tradition relationship manager do maintain relationships.

It seems once an Application Service is in the cmdb_ci_service_discovered table, you cannot select Tags as a population method in the CSDM Application Wizard.  My workaround was to manually reclassify a Mapped Application Service to an Application Service (cmdb_ci_service_auto) via the list view.  Once this was done, I could open the record in the CSDM Application Wizard and select Tags as a population method for that Application Service.

So far my tested has been positive.  No previous relationships were removed when the Application Service was reclassified.  And once Tags have been processed, no duplicate relationships were created.