Skip to main content

ServiceNow CMDB SyncPack v4.0.0 Release

Related products:Product Announcements
  • May 12, 2026
  • 0 replies
  • 13 views

judeEmc2
Forum|alt.badge.img

Hello, 

We are pleased to announce the release of ServiceNow CMDB v4.0.0.This SyncPack is supported for Skylar Automation (PowerFlow) version 3.0.0 and higher, as well as Skylar One (SL1) version 12.3.0 and higher, and requires "ServiceNow Base" SyncPack version 4.0.0 or later (also released today).

This much anticipated release includes the following features and updates:

  • Updated ServiceNow API endpoints to leverage GraphQL for gathering ServiceNow Configuration Items (CIs) in the following applications:
    • Sync Devices from ServiceNow to Skylar One
    • Sync File Systems from ServiceNow to Skylar One
    • Sync Interfaces from ServiceNow to Skylar One
  • Added support for the refined ServiceNow Common Service Data Model (CSDM) for services.
  • Added the cmdb_ci_service_business table to the supported tables for the "Sync Business Services from ServiceNow to Skylar One" application.
  • Updated the "Sync Business Services from ServiceNow to Skylar One" application to leverage GraphQL when retrieving services from ServiceNow.
  • Updated the creation of makes and models in ServiceNow to use GraphQL mutations. l Updated the report for the "Sync Devices from Skylar One to ServiceNow" application to display fields for creates, updates, and disconnects sent to ServiceNow.
  • Added the following configuration options to the "Sync Devices from Skylar One to ServiceNow" application:
    • ci_query_time_duration. Determines the lookback window in days for pulling CIs determined by the last scan field on the sys_object_source table. If a CI is not returned on this query, but is still active in Skylar One, a "create" request will be sent for the CI, which will update the timestamp.
    • enable_disconnects. If toggled on (blue), deletes the sys_object_source record for the CI. The "Sync Devices from SL1 to ServiceNow" application will no longer use a "monitored" field.
  • Removed the drop_sys_id configuration option from the "Sync Devices from Skylar One to ServiceNow" application.
  • The triggered application is no longer used when sending CIs to ServiceNow using the "Sync File Systems from ServiceNow to Skylar One" application.
  • The triggered application is no longer used when sending CIs to ServiceNow using the "Sync Interfaces from ServiceNow to Skylar One" application.
  • Grouped payloads are now sent to ServiceNow under a single import with a set ID number to help identify errors or warnings when importing devices
  • Updated the default mappings for the "Sync Business Services from ServiceNow to Skylar One" application to align Skylar One services most closely with the new ServiceNow Common Service Data Model (CSDM):
    • SL1 Business Services maps to cmdb_ci_service_technical
    • SL1 Technical Services maps to service_offering
    • Sl1 Device Services maps to cmdb_ci_query_based_service (this is unchanged)

NOTE: Due to how ServiceNow handles the creation of relationships between services and reference fields, you need to run this application twice in Skylar Automation. The first run of the application will create CMDB groups, while the second run will populate the new groups with CIs

  • Removed the following applications from the SyncPack:
    • Sync Discovery Requirements
    • Sync Service Requests from ServiceNow to Skylar One
    • Sync Discovery Session Status from Skylar One to ServiceNow
    • Sync Discovery Templates from Skylar One to ServiceNow
    • Sync Organizations from Skylar One to ServiceNow
    • Cache ServiceNow Companies, CIs, and Skylar One Orgs, Device Classes
  • Removed the "Sync Software Packages from Skylar One to ServiceNow" application and moved its functionality to the "Sync Installed Software from Skylar One to ServiceNow" application. l Updated the "Sync Installed Software from ServiceNow to Skylar One" application to leverage the ServiceNow CMDB Identification and Reconciliation Engine (IRE) for software package and instance creation

NOTE: If there is not enough data in Skylar One, software that is synced using this application might conflict with the output of discovery from ServiceNow or other sources that populate software information in ServiceNow. 

  • Added two new configuration options to the Device, Interface, and File System syncs:
    • disconnect_type. Enter either "flip_boolean_field" or "remove_sources_entry" to determine the behavior for disconnects.
    • disconnect_field. Acts as the boolean field on the Configuration Items table to determine "True/False" for the Skylar One monitoring status.
  • Added the "Report: ServiceNow IRE Remediation Table" application, which displays IRE errors corresponding to a run of the "Sync Devices from ServiceNow to Skylar One" application. 

NOTE: One of the required configuration options for the "Report: ServiceNow IRE Remediation Table" application is multi-import-set-id, which can be obtained from the step data of the "Post CIs to Snow" step of the "Sync Devices from ServiceNow to Skylar One" application.

To access the release, as well as the user manual and full release notes, please go to the Support Center > Skylar Automation > SyncPacks page.

Thank you, 
Release Management