What actually happens when setting product model class on a model category?

Jacob Saaby Nie
Tera Contributor

Hi everyone.

 

So, I read this docs page: https://docs.servicenow.com/bundle/utah-it-service-management/page/product/product-catalog/task/t_Cr... 

 

One of the things I'd like to understand better is what happens when you set a product model class? As it is, we have a model category Computer. Assets are created as they should, however with a product model class of Product Model.

 

The Model Category has no Product model class set. I'd like to set that to Hardware.

 

What actually happens if I make that change?

The docs page says this, but that doesn't tell me very much.

 

Product model classClass table where the models are stored. The default values are:
  • Application
  • Consumable
  • Contract
  • Facility
  • Hardware
  • Service
  • Software
After you select a value, the table content, form views, and overall functionality of the models created in the model category gets impacted.
1 ACCEPTED SOLUTION

Punit S
Giga Guru

When you set a product model class for a model category, you are essentially specifying the class table where the models for that category are stored. This will impact the overall functionality of the models that are created within that category.

For example, if you change the product model class for a model category from "Product Model" to "Hardware," the models that are created within that category will be stored in the "cmdb_ci_hardware" table instead of the "cmdb_ci" table. This will affect the form views and the functionality of the models created within that category.

In general, changing the product model class for a model category will impact the way the models are managed, tracked, and reported within the ServiceNow platform. It is important to carefully consider the implications of making this change and to thoroughly test the impact on your system before making any changes in a production environment.

 

Please mark my answer as a solution/helpful in case it adds value and moves you a step closer to your desired ServiceNow solution goal.

Thanks,
Punit

View solution in original post

2 REPLIES 2

Punit S
Giga Guru

When you set a product model class for a model category, you are essentially specifying the class table where the models for that category are stored. This will impact the overall functionality of the models that are created within that category.

For example, if you change the product model class for a model category from "Product Model" to "Hardware," the models that are created within that category will be stored in the "cmdb_ci_hardware" table instead of the "cmdb_ci" table. This will affect the form views and the functionality of the models created within that category.

In general, changing the product model class for a model category will impact the way the models are managed, tracked, and reported within the ServiceNow platform. It is important to carefully consider the implications of making this change and to thoroughly test the impact on your system before making any changes in a production environment.

 

Please mark my answer as a solution/helpful in case it adds value and moves you a step closer to your desired ServiceNow solution goal.

Thanks,
Punit

major li
Tera Contributor

hi,

I don't think the model will go to cmdb_ci.list. Instead, it should go to cmdb_hardware_product_model.list