Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Service Instances vs Dynamic CI Groups

Robert Campbell
Tera Guru

yesterday

In the past we have created FKA business services (cmdb_ci_service) and added dynamic CI groups to them to take advantage of the auto-removal of stale infrastructure. There isn't necessarily any specific pattern we can use to have a completely automated service but we want to have as close to an automated service as possible. 

 

We thought of doing away with the service and only using a dynamic CI group. The problem with doing this is the structure according to the CSDM 5 White Paper.

RobertCampbell_0-1764184101009.png

This says that the Dynamic CI Group is tied to the TSO but it doesn't show a relationship to the service instance anymore (not sure if it ever showed it but that is the current relationship). From previous documentation, the service classification would determine the behavior but it doesn't seem to be that flexible anymore. I wanted to get some clarification on that before proceeding.  

 

0 Helpfuls
  • 122 Views
1 REPLY 1

Barry Kant
ServiceNow Employee
ServiceNow Employee

yesterday

Hi Robert,

Dynamic CI Groups have a dual use:
1 - To group CIs and link to TSOs (service_classification='Technical Service')
2 - A special type of Service Instance (service_classification='Application Service')

So you can still do both if you read the CSDM paper Service Instance (can be a Dynamic CI Group, like all of the extends of the base Service Instance table).

BR,
Barry

0 Helpfuls