Breadcrumbs

Is ServiceNow SAM Pro Installed

Connector Applicability

Applies to Source Connectors

Any source system with record types containing a model attribute/value

Applies to Destination Connectors

ServiceNow

Assumptions

These instructions assume you have already setup a source connection in CI Sync for ServiceNow.

Pre-Read

Syncfish recommend customers read the following documentation before changing the Connection Setting/s described below.

  1. Understanding the use of CI Sync Connection Settings

  2. Rule 19 - Define whether ServiceNow SAM Pro is Installed when Software Licence Keys are Synchronized to ServiceNow for Lansweeper On-Prem

Locating and Amending the Connection Setting in the CI Sync UI

  1. Navigate to the Settings pageNavigate to the Settings page

  2. Under the Destination Connections heading (list), locate your ServiceNow connection (it will be either a Non-PROD “TEST” connection or the “PROD” connection depending on which one you need to amend).

  3. Click the Update link on the right hand side of the ServiceNow connection.

  4. Scroll down and locate the Additional Settings Heading and view the Individual Connectoin Setting related to this guide.

CleanShot 2025-08-05 at 14.42.33@2x-20250805-044242.png

The screen shot is provided only as sample to assist when reading this page. The state of your own CI Sync UI will depend on whether you are starting from the CI Sync default position or if you have already amended one/more of the settings.

  1. Tick the Override default box/boxes and then use the sliders related to the individual settings. The following table elaborates any further information about these particular settings.

Setting

Type

Additional Notes

ServiceNow SAM Installed

Slider

This setting indicates your ServiceNow instance currently, or in the past, had the Software Asset Management (SAM) Pro plug-in, solely to support CI Sync’s ability to synchronize software licence keys from Lansweeper On-Prem.

When enabled, CI Sync’s behaviour changes as follows:

  1. CI Sync writes additional attributes in the alm_licence table to ensure compliance with ServiceNow field validation requirements.

  2. CI Sync writes records to the samp_custom_sw_product.

Role/Permission Note

In addition to enabling the connection setting described above, please add the “sam_admin” role to your CI Sync Integration User Account so CI Sync can write to the tables noted above.

Note

This connection setting does not cause CI Sync to drive ServiceNow SAM related functionality, or cause CI Sync to begin updating any other SAM related tables in ServiceNow.

The connection setting merely indicates the presence of the SAM plug-in when customers are using CI Sync’s feature that synchronizes software licence keys from Lansweeper On-Prem.

  1. After modify the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.

  2. You can now run a sync job and the amended settings will be applied causing the CI Sync Data Sync rules to be modified accordingly.

Importantly

Make sure you consciously override the setting against either your TEST or PROD environment (i.e. your TEST vs PROD sync jobs).

For more information on how to use TEST vs PROD Connection Settings please read Understanding the use of CI Sync Connection Settings.

Syncfish strongly recommend making changes for TEST environment/sync jobs first. Only modify PROD related settings after thoroughly validating the intended results in TEST.