Rule Synopsis
These are the rule/s that control whether CI Sync overwrites both the Discovery Source and the Correlation ID Attributes (or not) on each record during CI Update Operations (as distinct from CI Insert Operations).
Rule Details and Default
-
By default, CI Sync does not overwrite the following Correlation Attributes during a CI Update Operation:
-
Discovery Source
-
Correlation ID
-
-
The context of this rule is restricted to CI Update Operations (i.e. when CI Sync is updating an existing CI in the CMDB).
-
In all cases CI Sync writes (sets) the two Correlation Attributes as part of creating (insert) a CI in the first place.
Override Options
Context
Customers may consider overriding the default rule to have CI Sync overwrite the two Correlation Attributes (Discovery Source and Correlation ID) to meet their specific ServiceNow requirements. This rule (i.e. this overall topic) should be considered when customers have multiple CMDB integrations inserting and overwriting CIs from multiple source systems containing overlapping assets.
Override
-
The rule can be amended so that CI Sync does overwrite the two Correlation Attributes during CI Update Operations (as distinct from CI Insert Operations).
Overriding via Connection Settings
Also, 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 Overwrite Correlation Fields on Update in ServiceNow.
For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.
Additional Information
N/A
Related Rules
-
Rule 9 - Correlation ID and Correlation Prefix Value for AWS
-
Rule 8 - Value used for Discovery Source Attribute for Azure
-
Rule 9 - Correlation ID and Correlation Prefix Value for Azure
-
Rule 9 - Correlation ID and Correlation Prefix Value for GCP
-
Rule 6 - Value used for Discovery Source Attribute for InTune
-
Rule 8 - Correlation ID and Correlation Prefix Value for InTune
-
Rule 14 - Value used for Discovery Source Attribute for Lansweeper On-Prem
-
Rule 15 - Correlation ID and Correlation Prefix Value for Lansweeper On-Prem
-
Rule 13 - Value used for Discovery Source Attribute for Lansweeper Cloud
-
Rule 14 - Correlation ID and Correlation Prefix Value for Lansweeper Cloud
-
Rule 7 - Value used for Discovery Source Attribute for Defender for Cloud Apps
-
Rule 8 - Correlation ID and Correlation Prefix Value for MS Defender for Cloud Apps
-
Rule 7 - Value used for Discovery Source Attribute for Defender for Endpoint
-
Rule 9 - Correlation ID and Correlation Prefix Value for MS Defender for Endpoint
-
Rule 8 - Value used for Discovery Source Attribute for Nutanix
-
Rule 9 - Correlation ID and Correlation Prefix Value for Nutanix
-
Rule 6 - Value used for Discovery Source Attribute for Omnissa Workspace ONE
-
Rule 8 - Correlation ID and Correlation Prefix Value for Omnissa Workspace ONE
-
Rule 8 - Value used for Discovery Source Attribute for SolarWinds
-
Rule 9 - Correlation ID and Correlation Prefix Value for Solarwinds
-
Rule 8 - Value used for Discovery Source Attribute for VMware
-
Rule 9 - Correlation ID and Correlation Prefix Value for VMware
Support Model for Rule Overrides
Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?
Answer: Yes (via self-service in the CI Sync UI)
Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule
Answer: Either a Bronze Plan, Silver Plan or Gold Plan (for customers wanting Syncfish assistance to perform overrides of this rule)