We've updated the ServiceNow Community Code of Conduct, adding guidelines around AI usage, professionalism, and content violations. Read more

Discovery Pattern Serial Number References

hcallen
Tera Contributor

How come most of the OOTB patterns that create a reference to the cmdb_serial_number table set the column name "configuration_item" when the column doesn't exist on the table (the reference is named "cmdb_ci")? Am I missing something?

 

hcallen_0-1769381465920.pnghcallen_1-1769381506322.png

 

3 REPLIES 3

Vijaya_Mnpram
Tera Guru

@hcallen Can you please provide the exact Pattern you are looking at? When I checked the 'Windows OS - Desktops', the mapping is to cmdb_ci.

 

hcallen
Tera Contributor

@Vijaya_Mnpram 
I'm looking at the "Next Generation Palo Alto Firewall" pattern. Also, when looking at the "Windows OS - Desktops" pattern, the column name is "non_ci" (which doesn't exist on the Serial Number table too). As far as I know, these patterns have never been touched.

hcallen_0-1769459117209.png

 

@hcallen I guess, these column names are for the Result tables created ($serial_computer in the screen shot). They are not the column names of neither parent nor child.  

I entered debug mode with a Windows Desktop IP address, and the Serial number is picked even before establishing this reference. When 'Generate Playload' button is clicked on, the serial number is already picked ( in the step 2.14 Library).

VijayaMannapura_0-1769489909602.png

 

 I guess for the 'Next Generation Palo Alto Firewall' pattern also, you can enter the debug mode with a sample value and check where exactly the Serial number is picked up. I don't have any sample to check it.