How exactly Dynamic Application Service works?

[Suggy]

Hi, How exactly Dynamic Application Service works?

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

This doc says: "Dynamic application services get automatically populated when they’re connected to other CIs with CMDB relationships."

Q1 - I have created a Dynamic Application service. Now where /how to add the CI's? I am not understanding.

The doc also says "Entry points are automatically created when a relationship between a dynamic application service CI and other CIs is created."

Q2 - Tried to open a Infra CI, linked to Dynamic app serivce.. entry point is not added.. What am I missing?

Q3 - Why do we need Entry point for Dynamic Application service? Entry point is needed when we are ready to add Service Mapping right?

[Sumanth16]

Hi @Suggy ,

Please refer to the below thread:

https://www.servicenow.com/community/common-service-data-model/application-services-how-to-use-them/...

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

Thanks & Regards,

Sumanth Meda

[Suggy]

@Sumanth16 I have already gone through that. I have asked specific questions. That article does not answer my questions.

[Barry Kant]

Good day Suggy, 

the Dynamic Application Service (cmdb_ci_service_calculated) is a popluation method that syncs x level of CI relations (dept) to from the CI Relations table to the CI Association table. For all relations made it creates a Manual Entrypoint. 
The behavior (CI Relations or CI Associations might be important for the Incident/Change settings.). 
ootb Change is using CI Associations for the impact analysis, and Incident is using CI Relations for impact analysis. In my opinion that should be the same so I change the property for Incident for that reason. Side effect is that it is using Affected CIs as input for impact analysis. The CI Association table is the flat version and therefore a more cost efficient way to calculate the impact. 

Not sure how you make the Dynamic Application Service. The best option is to navigate to :
Configuration > Application Service.
Create a new Application Service (cmdb_ci_service_auto) via the wizard and select in step 2 the population method. 
Now it changes the class from cmdb_ci_service_auto to cmdb_ci_service_calculated. 
It also adds a type (5) value a service_populor (a reference to a script include) and a dept (metadata). Technically you can update the record this way:
"

gr.sys_class_name='cmdb_ci_service_calculated';   

    gr.service_populator='11f01e3dc3f23300daa79624a1d3ae32'; 

    gr.metadata='{"levels":"5"}';

    gr.populator_status=1;

    gr.type='5';

    gr.update();
"
if the attributes are not written somehow then it will not work. Meaning if you have a scripted creation to create an Dynamic Application Service then the above needs to be part of the script.

BR,

Barry

[PeterH2]

I just created a Relationship [cmdb_rel_ci] with my Parent as the Application Service (with Dynamic Service mapping) and the Child any CI (I chose a Java App), then I recalculated by Application Service and BOOM ! a service map.