The following types of content can be updated as part of a content update.
- Publishers
- Product names
- Product types
- Product classifications
- Discovery maps
- Suite definitions
- Categories
- Software model life cycles
The SAM - Apply latest content changes scheduled job runs and processes the content updates.
After the content download is complete, the updated content is pulled into the staging columns
of the Software Publishers (samp_sw_publisher), Software Products (samp_sw_product), Discovery
maps (samp_sw_entitlement_definition), and Software Product Definitions
(samp_sw_product_definition) tables. A query runs and identifies what transactional data in your
instance must be updated with the new content. After the changes are identified, the changes are
then propagated to your instance.
Another scheduled job, SAM - Create lifecycles and suites for a software model, runs and
propagates suite component and lifecycle changes to your software models. If you don't want
content changes applied to specific software models, you can clear the Allow
automated content updates flag on the Software Model form. By default, the flag is
selected to allow automated content updates to all software models.
Note: If a content update adds lifecycle data, it can't be deleted from the software model, but
you can deactivate it. Any lifecycle data that is added as part of a content update will have
the source set to Servicenow.
Use the Software Models with deactivated discovery maps report to show software models that
are pointing to any deactivated discovery maps.
To see changes that have been made to the software library, review the SAM Content Audit
(sam_content_audit) table.
Note: Content updates don't have an impact on any custom products or custom discovery
maps.
For more information on how to send your content to ServiceNow and include it in the content updates, see Enable the Software Asset Management content service.
