How "Requires verification" value on cmdb_ci classes populate.

[Jay Jav]

I have a question about the "Requires verification" attribute on cmdb_ci and other cmdb classes.

I don't see any consistency about populating this attribute on different instances. I want to understand under what condition it gets true and false values.

I have a script to generate the CIs like discovery payloads, but in my PDI, "Requires verification" is true the same code on a different instance populates false value.

Could you please give some more information about "Requires verification".

[MaxMixali]

ServiceNow – What “Requires verification” Means on CMDB CIs (and why it differs by instance)

Field
------
- Label: Requires verification
- Table: cmdb_ci (and subclasses)
- Purpose: Gate between CI creation and Asset creation / CI merge when **Enforce CI verification** is enabled.
- Typical UI actions shown when TRUE: **Create Asset**, **Merge CI**.

How it’s set (OOTB behavior)
----------------------------
1) **Driven by Model Category setting “Enforce CI verification”**
- When this checkbox is ON for the CI’s Model Category, newly created CIs (e.g., by Discovery / import) are flagged **Requires verification = true** and do NOT auto-create an Asset. You must either:
- **Create Asset** → flips Requires verification to **false**, or
- **Merge CI** → resolves duplicates and typically clears the flag.
- When the checkbox is OFF, CIs may auto-create Assets (depending on your asset strategy), and **Requires verification** is generally left **false**.
(Refs: ServiceNow community explanations and docs)

2) **CI created from an Asset**
- If a CI is created from an Asset (depending on properties and IRE), the flag is typically **false**. Some customers report exceptions due to customizations or timing.

3) **Buttons logic**
- “Create Asset” action sets **Requires verification** to **false** after creating the asset.
- “Merge CI” workflow also typically results in the flag being cleared on the survivor record.

Why you see different values across instances
---------------------------------------------
A) **Model Category config differs**
- The same code that generates CIs may land in different Model Categories where **Enforce CI verification** is on in one instance and off in another.

B) **System properties differ**
- Example: **glide.asset.create_ci_with_ire** (controls creation/linkage via IRE). Different settings change whether assets are auto-created and whether verification is needed.
- Other HAM/SAM/Discovery properties influencing asset/CI linkage may also vary.

C) **Data path differs (CI → Asset vs Asset → CI)**
- If one instance creates CI first (Discovery) and the other creates Asset first (procurement feed) the verification outcome can differ.

D) **Customizations or Business Rules**
- Some orgs add rules that force or clear the flag under certain conditions.

E) **Model / Asset strategy**
- “Don’t create assets” on the Model, or different **Model Category** assignments, change behavior.

How to diagnose on your instances
---------------------------------
1) Open the CI’s **Model Category** record and check **Enforce CI verification**.
2) Verify the **Model’s** “Asset tracking strategy” and linked **CI class**.
3) Compare **system properties** (notably **glide.asset.create_ci_with_ire**) between instances.
4) Check for **Business Rules** / **Script Includes** on cmdb_ci or on the **Create Asset** UI Action that manipulate the flag.
5) Review the **creation path**:
- Was the CI created by Discovery/import? (Expect verification if Enforce is ON.)
- Was the CI created from an Asset? (Typically verification is OFF.)
6) Turn on **Debug** during a test creation (System Logs → set debug + note which scripts run).

Typical scenarios (expected)
----------------------------
- **Enforce ON** + CI created by Discovery/import → Requires verification = **true** (no automatic Asset).
- Click **Create Asset** → Asset created; Requires verification → **false**.
- **Enforce OFF** → CI may auto-link/create Asset; Requires verification usually **false**.
- CI created from Asset (with IRE linking) → flag typically **false** (asset already verified).

Recommendations
---------------
- Decide per Model Category whether you want to block automatic asset creation and require verification.
- Keep **Enforce CI verification** consistent across environments for repeatable outcomes.
- If your import/discovery “feels” inconsistent, include a post-step that sets/clears the flag explicitly to match your policy.
- Avoid manual toggling; use the standard UI actions (Create Asset / Merge CI) or controlled logic.

References (summaries)
----------------------
- Community thread: Enforce CI verification turns **Requires verification** ON for new CIs so you can **Create Asset** or **Merge CI**.
- Docs/KBs: Model Category drives behavior; “Create Asset” turns the flag OFF; property **glide.asset.create_ci_with_ire** influences CI/Asset creation & linkage.

TL;DR
-----
“Requires verification” is primarily controlled by the **Model Category → Enforce CI verification** setting and the **direction** of creation (CI→Asset vs Asset→CI). Differences between instances usually come from different Model Category setups or properties like **glide.asset.create_ci_with_ire**. Align those and you’ll get consistent true/false outcomes.