Hi, What exactly Dynamic application services?
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?
Hello,
So prior to CSDM, relationships between CIs weren't very prescriptive but you could manually create a relationship between CIs especially if you knew it supported the application or service. The relationship type could be whatever you selected, runs on, depends on, etc. I believe what the dynamic service is doing, is taking an existing, manually created service map, and converting the relationships based on CSDM and also allows you to view the map in the service view.
Service View
If you don't convert it, you won't see the manually created map in the service view and the only way to see the service map relationships is in the dependency view, which will also show horizontal discovery relationships.
Dependency View
These are the same apps, two different views. This is one way to convert your legacy application services. You could also use this to manually create a map then convert it but instead manually creating relationship maps, you could use Dynamic CI groups which allows you to either manually select the items to associate to the application or use filter conditions to group CIs together whenever the conditions are met. For instance, if your organization has standard naming conventions you could use the naming conventions to pull in the most recent servers and put filter conditions for the CMDB group like Install Status = Installed, Name contains app1, and Environment = Production so if prdapp101 gets replaced by prdapp102, then it will automatically be associated to the dynamic CI group for the application service. I hope this helped.
Thanks,
Jeff
