IRE- Support for non-cmdb tables--- Any use case on it why we required IRE for non cmdb table?

[Akash Kadam]

IRE- Support for non-CMDB tables--- Any use case on it why we required IRE for non-cmdb tables?  

[Community Alums]

Hi @Akash Kadam ,

 Please refer to the this Well explained Article :https://www.servicenow.com/community/now-platform-blog/how-to-configure-identification-rules-for-non...

Also, the doc :https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/configuration-managem...

[Community Alums]

Hi @Akash Kadam ,

[Amit Gujarathi]

Hi @Akash Kadam ,
I trust you are doing great

One potential use case is when you have data stored in external systems or non-CMDB tables that you need to synchronize with your ServiceNow instance. By leveraging IRE, you can enrich the data in these tables and make it more useful within ServiceNow.

Let's take an example to illustrate this use case. Suppose you have an external HR system that stores employee data, including employee records that are not part of the CMDB. You want to bring this employee data into ServiceNow and make it accessible to various processes and applications within the platform.

In this scenario, you can create an integration between ServiceNow and the HR system to synchronize the employee data. Using IRE, you can enrich this data by adding additional fields or transforming it to fit your ServiceNow instance's requirements. For instance, you might add a "Manager" field to each employee record by looking up the manager's information from another source or perform data mapping to align fields between systems.

By utilizing IRE for non-CMDB tables, you can standardize and enhance the data within ServiceNow, enabling better visibility, reporting, and automation across your organization's processes. It helps in maintaining data consistency and improving the overall efficiency of your ServiceNow implementation.

[Kiran_T]

Hi @Akash Kadam 

The main intention is to prevent the insertion of duplicate records in to that table ,so that existing records can be updated if the Identifier attributes that you have configured matches.

Also, configuring the Reconciliation rules helps only the authorized data sources to update that table.

If you are extending the custom class from any parent class you can fallback to the parent's IRE rules configured .

Please ,mark helpful if it answers your query.