Is there a dynamic application service that I can build from a query?

Robert Campbell
Tera Guru

3 weeks ago

I am looking for a dynamic application service option that will allow me to use a query (or a couple) to determine which cis should be related (as depends on).

 

I would like all:

  1. windows servers
  2. begins with abcxyz1-
  3. operational status of Operational
  4. most recent discovery after 2 days ago

These should be part of the ABCXYZ application service/service instance.

I would see these as downstream cis with a depends on relationship.

 

I have tried a dynamic ci group but that has ci associations not ci relationships.

Labels:
  • 656 Views
2 REPLIES 2

Matthew_13
Kilo Sage

3 weeks ago

@Robert Campbell - 

A dynamic CI group won’t work here—it only controls membership, not relationships.

In ServiceNow, if you want CIs to show up as Depends on under an application service, you either need Service Mapping (for real, discovered dependencies) or a custom job/Flow that runs your query and creates/removes Depends on relationships automatically.

There’s no out-of-the-box way to create query-driven dependency relationships without Service Mapping or automation.

Thumbs up if this helps, Thanks!

JenniferA082772
Giga Contributor

3 weeks ago

Hi @Robert Campbell 

What you’re seeing is expected behavior.

Dynamic CI Groups are query-based, but they only create CI associations, not CMDB relationships, so they won’t populate Depends on / Used by relationships for application services.

Out of the box, ServiceNow does not support a truly dynamic application service that continuously builds and maintains CMDB relationship records based solely on a query. Application services rely on persisted relationship records in the CMDB, not evaluated queries at runtime.

The common options teams use today are:

  • Service Mapping, where applicable, to automatically discover and maintain relationships

  • Scheduled jobs or scripts that evaluate queries and create/remove relationship records (with careful governance to avoid drift)

  • A hybrid approach, where discovery-based relationships are supplemented by controlled automation

Dynamic CI Groups are mainly useful for filtering, reporting, or targeting actions, but not for maintaining dependency relationships.


So in short: what you’re trying to do makes sense conceptually, but it isn’t supported natively without automation or discovery-driven mapping.

0 Helpfuls