---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Customize a Discovery pattern for Software Asset Management Foundation plugin

# Customize a Discovery pattern for Software Asset Management Foundation plugin {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Software Asset Management Foundation plugin automatically leverages SQL Server, Exchange, and Oracle Database Discovery patterns, but you can
perform steps for Software Asset Management Foundation plugin to
utilize additional Discovery patterns,
if needed.

## Before you begin

Role required: sam_admin

## About this task

Discovery uses a series of scripts and operations (probes, sensors,
and patterns) with the base system to collect data, process it, and update the CMDB.
Although Software Asset Management Foundation plugin is already set up to utilize three
common patterns ([MSSQL server
discovery](https://www.servicenow.com/docs/access?context=mssql-data-collected-pattern&version=australia&pubname=australia-it-operations-management&ft:locale=en-US), [Exchange MailBox
discovery](https://www.servicenow.com/docs/access?context=r-ExchangeMailBox&version=australia&pubname=australia-it-operations-management&ft:locale=en-US), and [Oracle database
discovery](https://www.servicenow.com/docs/access?context=c_OracleDatabaseDiscovery&version=australia&pubname=australia-it-operations-management&ft:locale=en-US)), you can perform a
configuration procedure to include additional patterns.

This customization automatically copies the records from the discovered pattern to
the Software Installation \[cmdb_sam_sw_install\] table so Software Asset Management Foundation plugin can utilize this data for reconciliation.

For more information on pattern customization, see [Discovery patterns used by
ITOM Visibility](https://www.servicenow.com/docs/access?context=c_MappingPatternsCustomization&version=australia&pubname=australia-it-operations-management&ft:locale=en-US).

## Procedure

1. Configure a post processing step in the discovery pattern.
   1. Navigate to Pattern DesignerDiscovery Patterns.
   2. Open the pattern record from which you would like to collect data for Software Asset Management (for example, the discovery pattern for MySQL).
   3. Select and copy the Class Name field value.  
      You will need to paste this class name value into a record field in the Software Installation Name Mapping \[cmdb_sam_sw_name_mapping\] table as part of this configuration procedure.
   4. Click the Pre/Post Processing related link.
   5. In the Sync Installed Software section, select the desired software from the list to add it (for example, MySQL).  
      Data discovered relating to the software you select is automatically copied into the Software Installation \[cmdb_sam_sw_install\] table as part of the discovery process.
   6. Click Update.
   {#t_CustomPatternSAMSAMF__substeps_wdx_m1r_11b}
2. Add the pattern data to a new record in the Software Installation Name Mapping \[cmdb_sam_sw_name_mapping\] table.
   1. Create a new record (see table for field descriptions).  
      {#t_CustomPatternSAMSAMF__table_hst_4w3_b1b__entry__2}

      | Field | Description |
      |-|-|
      | Class name | Class name of the discovery pattern. Paste the value that you copied from the class field in discovery pattern. |
      | Publisher | Publisher of the product (for example, Oracle). |
      | Product | Product name (for example, MySQL). |
      [ ]

      {#t_CustomPatternSAMSAMF__table_hst_4w3_b1b}
   2. Click Submit.

   {#t_CustomPatternSAMSAMF__substeps_akk_h2r_11b}  
   When discovery is run, the records for the software product relating to the customized discovery pattern are utilized by Software Asset Management.

   No further configuration is needed unless you know the software product
   consists of an edition that is not being discovered automatically.

## What to do next

If the software product has an edition that is not being discovered, [Manually override SAM Foundation edition value](https://servicenow-prod.fluidtopics.net/4avEAvXZTFSnHQr6uZy8xg "When the edition of a software install is not automatically discovered, you can specify the edition on the Software Installation form with the correct value (if known) so the software can be successfully reconciled.") so the software can be successfully reconciled.

*[\>]: and then