Can the Identification and Reconciliation Engine (IRE) be used for non-CMDB tables.

[Sahil Chaudhary]

Hi Community,

I am looking for architectural clarity regarding the scope of the Identification and Reconciliation Engine (IRE).

When attempting to create an Identification Rule for a table like cmdb_backup_storage_information, the table cannot be found or selected within the CI Class Manager. This table resides in the CMDB application space but does not inherit from the base cmdb_ci class.

Is it correct that the IRE is strictly limited to tables extending the cmdb_ci hierarchy? If a table does not extend cmdb_ci, is the standard best practice to handle deduplication via IntegrationHub ETL Lookup Fields (RTE/coalesce) as a "Non-CMDB Entity" instead of using the IRE?

[dimitrios_l]

Yes, you can include non cmdb tables in the IRE. There is the glide.identification_engine.non_cmdb_tables property that needs to be enabled, and then keep in mind that there are limitations on OOB tables. For custom ones you can include anything.

For the non cmdb tables, you can't use CI Class Manager. Instead go to CI Identifiers under IRE.

[Tanushree Maiti]

Hi @Sahil Chaudhary 

Refer ServiceNow Documentation : IRE support for non-CMDB tables 

Identification and Reconciliation Engine (IRE) processes to supports non-CMDB tables to ensure data integrity and health of those tables.

Starting with the Australia release, IRE supports some non-CMDB tables. You can use all IRE features with some non-CMDB tables after creating identification rules (CI identifiers and identifier entries) for those tables. Non-CMDB tables supported for IRE features include:

• In an application-specific scope: All non-CMDB tables
• In the global scope: Only non-CMDB tables that are preset in the base system. In the Australia release for example, the Location [cmn_location], Department [cmn_department], Cost Center [cmn_cost_center], Building [cmn_building], User [sys_user], and Group [sys_user_group] non-CMDB tables are supported.