---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Create an IRE data source rule

# Create an IRE data source rule {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

When using Identification and Reconciliation Engine (IRE), you can prevent a specific
discovery (data) source from inserting new CIs for a specific class. Create IRE data source
rules for discovery sources that you don't trust in creating CIs but continue to trust in
updating those CIs that exist.

## Vorbereitungen

Role required: sn_cmdb_admin or itil_admin

## Warum und wann dieser Vorgang ausgeführt wird

IRE data source rules have no impact when dynamic reconciliation rules are in
effect.

For example, an IP scan tool that discovers network gear but does not discover
servers and therefore creates server CIs without details. You can prevent such
discovery source from creating specific CIs, while still permitting it to update
those specific CIs if they exist. IRE data source rules are stored in the IRE Data
Source Rule \[cmdb_ire_data_source_rule\] table.  
* Child classes derive IRE data source rules from parent classes like identification rules do.
* IRE data source rules that are specified for a child class, override any IRE data source rules derived from a parent class.
{#create-ire-data-source-rule__ul_all_5r1_kjb}  
When IRE processes an insert operation that is prohibited by an IRE data source rule, the insert operation fails. This failure happens when the discovery source and CI class in the insert operation and in an IRE data source rule, match. When [CreateOrUpdateCIEnhanced()](https://www.servicenow.com/docs/access?context=IdentificationEngineScopedAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US) is used, IRE stores the failed payload in the CMDB IRE Partial Payloads \[cmdb_ire_partial_payloads\] table for future potential use.  
Hinweis:  
When an insert operation is not allowed by the IRE data source rule, then when using [createOrUpdateCI()](https://www.servicenow.com/docs/access?context=c_IdentEngineScriptAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US), the entire IRE payload fails since [createOrUpdateCI()](https://www.servicenow.com/docs/access?context=c_IdentEngineScriptAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US) doesn't allow partial commits.

If later, a permitted discovery source attempts to insert that same CI, then IRE
inserts the CI after merging it with the matching CI from the partial payloads. IRE
then deletes the partial payload from the CMDB IRE Partial Payloads
\[cmdb_ire_partial_payloads\] table, and allows future updates by the discovery source
specified in the rule.

IRE data source rules do not apply to lookup and related items, and only a single
rule can be active for any class/discovery source pair.

## Prozedur

1. Navigate to AllConfigurationIdentification/ReconciliationIRE Data Source Rule.
2. In the list view, click New and fill out the IRE Data Source Rule form.  
   {#create-ire-data-source-rule__table_wfk_yvz_jjb__entry__2}

   | Field | Description |
   |-|-|
   | Active | Activates the IRE data source rule. |
   | Applies to | The class (and child classes) that the specified discovery (data) source is not allowed to create CIs of. |
   | Data source | Discovery (data) source that is not allowed to create CIs of the specified class. |
   | Insert Not Allowed | Disables the specified discovery (data) source from inserting new CIs from the specified class, to the CMDB. |
   [ ]

   {#create-ire-data-source-rule__table_wfk_yvz_jjb}
3. Click Submit.

## Ergebnisse

If a payload item with an insert request, and in which the discovery source and the CI class match the discovery source and the CI class specified in the IRE data source rule:

1. The insert operation fails and IRE logs the following message: INSERT_NOT_ALLOWED_FOR_SOURCE Insert into \[xyz\] is blocked
   for data source \[xyz\] by IRE data source rule.

2. If using [CreateOrUpdateCIEnhanced()](https://www.servicenow.com/docs/access?context=IdentificationEngineScopedAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US), then IRE stores the payload item as a partial payload in the CMDB IRE Partial Payloads \[cmdb_ire_partial_payloads\] table.

{#create-ire-data-source-rule__ol_kz4_241_kjb}  
If later, a permitted discovery source successfully inserts a CI that matches the CI from a partial payload item:

1. The current CI is merged with the matching CI from the partial payload, applying static reconciliation rules as needed.
2. The respective partial payload in the CMDB IRE Partial Payloads \[cmdb_ire_partial_payloads\] table is deleted.
3. Later payloads in which the non-permitted discovery source updates the respective CI, run successfully.
4. IRE allows the discovery source, that was previously prohibited from inserting the CI, to update that same CI which now exists in the CMDB.
{#create-ire-data-source-rule__ol_esn_wn1_kjb}