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

How to Populate CIs with Their Respective Classes Based on Subcategory

KrushnakumaT
Tera Guru

I want to automatically populate Configuration Items (CIs) based on the appropriate CI classes, where each CI class is determined by the selected Subcategory. Kindly suggest the best approach or recommended solution for implementing this functionality. Thank you in advance.

3 REPLIES 3

Dr Atul G- LNG
Tera Patron

Hi @KrushnakumaT 

 

I think the question might be incorrect here. From what I understand, we populate the category/subcategory based on BS and SO, or CI based on BS–SO, not vice versa. To address this part, I suggest using that decision table.

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************

Hi @Dr Atul G- LNG ,
Actually, the question is correct. We have a requirement where the stakeholders have provided specific Incident Subcategories, and based on those Subcategories, we need to populate only the relevant CIs belonging to their respective CI classes.
For example:
If the Subcategory is "Operating System", then the Configuration Item field should display only CIs from the cmdb_ci_computer class.
Similarly, for other Subcategories, we need to restrict the CI list according to the mapped CI class.

Hi @KrushnakumaT 

 

Thanks for the clarification, mate. Looking at the background, I would say this isn’t a viable use case. There are over 1,000 classes in SN for the CMB side — are we really going to create that many subcategories? It’s better to follow the recommended “vice versa” route, which is best practice.

Otherwise, you would need to map 1,000+ classes to subcategories and then display them here. From a work perspective, that’s not a big issue if you set up dependencies correctly. You can also create decision tables for this — it’s something I worked on yesterday.

 

 

https://www.servicenow.com/community/incident-management-forum/field-dependency-between-two-fields-i...

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************