How to use CMDB Identification and Reconciliation rules in scoped application?

[Kaushal283]

If we are using IRE for inserting data into CMDB, do we still need to handle duplication using coalesce field in transform map? Also, can we add our custom identification rules on existing CMDB tables if we have custom identification requirements? 

My use case is as follows: 

I've to import some data from a REST API and ingest into already existing CMDB tables. Now existing CMDB CI tables (like cmdb_ci_computer, cmdb_ci_unix_server, etc.) do not have all the fields (columns) which I want to map from my data, so I've created new columns as part of my scoped application. 

Now I'm first ingesting data to staging table (import set row) and written a transform map in which I want to use IRE features. But for identification, I need an identification rule on computer table (or any OOB CMDB CI table) but it's not allowing to create these rules as part of the application(custom rules are created in Global scope). However, I can create these rules on my custom table which extends to cmdb_ci. But this is not useful in my case. For identification (determining uniqueness) I only see a single possible option, that is to use coalesce fields without using IRE.

So in such cases, how can I leverage the IRE capabilities of ServiceNow? 

[Pradeep Sharma]

Hi Kaushal,

Please find my response below.

• Coalesce field is not required in this case as it is already taken care of by IRE API.
• You cannot ship IRE rules for the global table in a scoped app. Please note your customers can manually create IRE rules subject to ServiceNow approving this during the certification process.
• I know sys_choice can be captured as part of demo data but there was some issue where the choice values were getting overridden that is why I don't recommend that step. Please document this as part of the installation document so that your customers can manually create those choice records.

https://community.servicenow.com/community?id=community_blog&sys_id=7e3fb6d5db5afb00fece0b55ca9619e3

- Pradeep Sharma