What exactly are Dynamic application services? When to use them?

[Suggy]

Hi, What exactly Dynamic application services?

https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...

As per the docs, it states "Use this method to transform legacy business services into application services that other ServiceNow products can utilize."

Q1 - So is that to be used only when you want to convert legacy servics to Application services?

Q2 - If so, then why there is an OPTION itself to create Dynamic Application service?

[Satoshi Tsuboi]

Here's a good explanation of a Dynamic Service. https://youtu.be/0UYFbVErr84?t=252.

[Suggy]

@Satoshi Tsuboi I have already gone through that video. After that only I posted this question.

If you could answer/reply specifically to my quetions, that would be great 🙂

[Satoshi Tsuboi]

You can use it to convert legacy (manual dependencies) services or create new application services based on the relationships created in the CMDB and will be reflected in the Service Map automatically. You could create application service using the manual option; however, you would need to add each CI relationship manually each time between the CMDB and the Service Map. ServiceNow recommends using the Dynamic Service approach over the Manual option.

[WayneOdom]

I'll take a shot at question one, as we're trying to circle back to mature our current use of service mapping.    We have a number of manually created services.   Back when they were created, this dynamic service concept didn't exist.    So the understanding was that the relationships were there, the analysts when in and "pruned" out the things that we didn't want to consider part of the services, but at that point this was what your service looked like and it couldn't dynamically add new components without cuasing a lot of manual pruning to occur again.   It sounds like this dynamic aspect is supposed to close that gap and allow you to detect new addions to the service.    I don't think it's only for legacy services, although that seems the most common case, but it's definitely to be used for services which you already have relationships defined and you desire dynamic CI's and relationships being added to.