Has anyone a use case for using population methode "dynamic Service" in Application Services?

[Marcel Leu]

Has anyone a use case for using population methode "dynamic Service"?

If Yes, can you explain what the steps are and how can i get the service map with Ci's; for example 3 Levels.

Thanks for help, Marcel

[KN8]

Hi Marcel, 

This is a Quebec description of this UI action: Convert legacy manual services into dynamic application services (servicenow.com)

This is the actual script performing the conversion (thoroughly commented code, easy to follow btw, kudos to devs): <INSTANCE>.service-now.com/sys_script_include.do?sys_id=1f39af45c31303003e76741e81d3aee9 

So in my PDI with the CMDB demo data I tried this scenario, see if it is close to what you are trying to deal with:

1. Create a Manual service, and used an entry point SAP-SD-03. Open Service Map - you'll see just this CI as an entry point.
2. Add another CI to the map manually (right click on the Map - Add a CI) - CMS App FLX. There are now two CIs on two levels on the map (apologies for a crude screenshot, it's the green ones). 
3. Open SAP-SD-03's dependency view, and CMS App FLX's dependency view. Note the downstream relationships of the two.
4. Return to the AS form and clicked the UI action 'Convert to Dynamic Service').
5. Open the Service Map again. Observe the new CIs added to it (in red on the screenshot).

So I guess the benefit of conversion is that you automatically have more CIs on your map (ie inherited from dependencies) than you initially had 😃

Please see the links above for some limitations of this approach, e.g. no discovered CIs allowed.

I'm guessing ServiceNow offers this (Dynamic Service) population method for specific type of long-term customers, who used to build manual dependencies a lot, and now wish to reduce rework when implementing Service Map-dependent products, such as Event Management.  

Perhaps someone from ServiceNow might step in to confirm/comment.

Hope this helps.