Rule Synopsis
These are the rule/s that control whether CI sync does (or does not) set the Asset Tracking Strategy on the ServiceNow product model table when synchronizing assets from Jamf. ServiceNow uses the Asset Tracking Strategy to determine whether a hardware asset is created (or not) for a given CI.
Please read the additional information section further below for more details on how ServiceNow uses the Asset Tracking Strategy for hardware asset creation.
Rule Details and Default
-
By default, CI Sync does not set the Asset Tracking Strategy (asset_tracking_strategy) on the ServiceNow product model table (cmdb_model) and instead relies upon ServiceNow default behavior for this functionality.
Override Options
Context
Customers may consider overriding this rule to influence which CIs trigger the creation of a hardware asset in ServiceNow.
Options
-
This Data Sync Rule can be overridden so that CI Sync does set the Asset Tracking Strategy (asset_tracking_strategy) on the ServiceNow product model table (cmdb_model) to dictate whether a given Jamf asset (based on its model) creates a hardware asset (or not).
Overriding via Connection Settings
Customers can perform the override using a “Connection Setting” via the CI Sync User Interface (i.e. customers can perform the overrides themselves). Additional information for this is available via the following documentation:
-
For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.
-
For the specific CI Sync Connection Setting/s related to the rule described on this page please read Model Asset Tracking Strategy for Jamf
For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.
Additional Information
FAQ - Brief Overview of Is_Virtual (and virtual vs physical CIs) in ServiceNow
Related Rules
N/A