← Home
🔥0 DAY
⚡0 XP
Discovery hub·Relationships & Dependencies

Relationships & Dependencies

How CIs relate and how impact propagates.

5 questions loaded · 4 definitive · 1 scenario

Definitive questions

Scenario drills

  1. Impact analysis returns nothing

    “Change on 'db-prod-01' shows no affected services. What's wrong?”

    Approach

    • Check cmdb_rel_ci direction — the DB must be the CHILD of 'Depends on' relationships from applications.
    • Verify a path exists from the DB up through applications to a business service.
    • Confirm 'operational' status on intermediate CIs; retired CIs break traversal.
    new GlideRecord('cmdb_rel_ci')
      .addQuery('child', dbSysId)
      .addQuery('type.name','Depends on::Used by');

    Alternate approach

    Alternate: use the BSM map or 'Impacted Services' related list on the CI — visual traversal often exposes broken links faster than scripting.

    Pitfall

    Reversing parent/child on custom relationship types silently breaks impact analysis.

Grow this section

Generate more unique questions on demand — the AI sees the titles already on the page and avoids repeats. Repeat until you reach the depth you need.