What this masterclass focuses on?

1. End‑to‑end demo of IRE rules (Identification and Reconciliation) on a brand‑new CI class in ServiceNow CMDB.
2. No distractions from Discovery, Import Sets, or external APIs—just clean, controlled test cases directly against CMDB to understand IRE behaviour clearly.
3. The entire session is about “how the engine thinks” when it decides whether to create a CI, update it, or ignore incoming data.

Why I only use a custom CI class and direct data

1. I create a new CI class from scratch, so you see every attribute, every rule, and every decision transparently.
2. We are not hiding anything behind out‑of‑box classes, Discovery patterns, or complex integrations.
3. This makes it easier for you to map rules to actual behaviour instead of guessing what prebuilt content is doing in the background.

What exactly we build step by step?

1. Creating a brand‑new CI class in CMDB, with the attributes we will use for identification and reconciliation.
2. Defining Identification Rules on this class and explaining:
   1. Why we use certain fields,
   2. How primary and secondary keys work,
   3. What happens when a key field is missing or duplicated.
3. Defining Reconciliation Rules for that same class and explaining:
   1. How we prioritize different sources,
   2. How “winning” fields are chosen,
   3. How the engine treats updates from lower‑priority sources.

1. How I test the IRE rules in the demo
2. We add data directly into the table for this new CI class, one scenario at a time—no Import Sets, no API payloads.
3. For each scenario, I clearly explain:
   1. What data we are sending,
   2. Which rules should fire,
   3. What we expect IRE to do (create, update, ignore, or error).
4. Then we check what actually happened in the record and match it with the rules, so you learn to “read” IRE’s behaviour from real data.

Types of scenarios and cases we cover?

1. I intentionally test many different cases, such as:
2. First‑time insert: when no matching CI exists and how the identification rule decides to create a new CI.
3. Second insert with same keys: how IRE recognises the CI and performs an update instead of creating a duplicate.
4. Insert with partially matching keys: what happens when one identifier matches, but another is different or blank.
5. Changing a key field: how IRE reacts when a supposed “unique” field is modified and whether it links to old or new CI.
6. Multiple “source” values with different priorities configured in reconciliation: who wins and why.
7. Edge cases where rules are misconfigured or data is incomplete, and how that leads to unexpected behaviour.

Types of scenarios and cases we cover?

1. Design and configure Identification and Reconciliation rules on any CI class with confidence, because you’ve seen them built from scratch.
2. Predict how IRE will behave for a given set of data before you even hit “insert” or “update”.
3. Troubleshoot weird CMDB behaviour (duplicates, wrong updates, ignored data) by relating it back to the rules and test patterns from this demo.
4. Take the same approach into your own PDI or project: build a test class, create rules, and run your own controlled IRE experiments.