Software Component Model table
The Software Component Model [cmdb_software_component_model] table stores component model records that serves industries and use cases across different solutions on the ServiceNow Platform.
Overview of Software Component Model table
The Software Component Model table extends from the System Component Model [cmdb_sw_component_model] table that resides in the Data Foundation Model (sn_cmdb_foundation) application. The Software Component Model table can consist of various entities.
- Is normalized with a normalized version set.
- Is manually normalized with a normalized version set.
- MAJOR
- FULL
- BOTH
- NONE
Two records are created in the Software Model Component table when a FULL version and a MAJOR version exist for the normalized discovery model. However, only one record is created if only the MAJOR version exists.
You can also manually create a software component model record in the Software Component Model [cmdb_software_component_model] table. If you have the Software Asset Management Foundation plugin or the Software Asset Management Professional application while creating the record, you can reference the Software Product [samp_sw_product] table. If you are not using the Software Asset Management application, you need to type in the software product name.
Upgrade information
When you upgrade to Zurich release and later releases, the scheduled job, SAM - Generate software component model does a one time run to generate component model records for all existing normalized discovery models which are then stored in the Software Component Model table.
Discovery model considerations
- System property changes: When a system property preference changes, the existing software component models retain their original settings. Only newly created version models adopt the updated system property.
- Model deletion or modification: If you delete or modify a software component model, the system won't recreate it from the original discovery model.
- Manual re-normalization: When a discovery model is manually normalized with new values, the existing software component model remains as is. The system creates a new software component model only if one does not already exist.