Rule Synopsis
These are the rule/s that controls whether CI Sync suppresses (or not) updating the multiple ServiceNow Status Value attributes on CIs (and Assets) in the CMDB during CI Update operations.
Rule Details and Default
-
By default, CI Sync does not suppress Status Value updates (i.e. CI Sync does update Status Values during CI Update operations).
Override Options
Context
-
Customers may wish to perform Status Value update suppression to ensure the behaviour of CIs and associated Assets in ServiceNow aligns with Hardware Asset Management (HAM) processes within each organisation.
-
Customers may consider overriding the default rule so that CI Sync does suppress Status Value updates (i.e. CI Sync does not update Status Values during CI Update operations).
-
If Status Value update suppression is enabled, customers can further refine the settings so that CI Sync conditionally performs Status suppression.
Option
-
Customers may consider overriding the default rule so that CI Sync does suppress Status Value updates (i.e. CI Sync does not update Status Values during CI Update operations).
-
If Status Value update suppression is enabled, customers can further refine the settings so that CI Sync conditionally performs Status Value update suppression. Example conditions can include:
-
Always Suppress (Status Value updates) vs Conditionally Suppress (Status Value updates).
-
Suppress based one or more existing status values in either the Install_Status or Hardware_Status attributes on the CI record.
-
Only suppress if the CI record has been updated more recently in ServiceNow (compared with the last update to the record in the source system).
-
And so on.. please read this CI Sync Connection Setting guide for all possible options: https://syncfish.atlassian.net/wiki/x/pIAWkOUE
-
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 https://syncfish.atlassian.net/wiki/x/pIAWkOUE
For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.
Additional Information
Please be aware that the connection setting described above (Suppress Status Value Updates in ServiceNow) does not apply to every source system connection. Instead, the connection setting is limited to a defined set of source system connections. Please take note of the “Applies to Source Connectors” list in the connection setting guide.
Related Rules
-
Rule 5 - Mapping of AWS Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of Azure Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of GCP Status Values to ServiceNow Status Values
-
Rule 4 - Mapping of InTune Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of Lansweeper On-Prem Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of Lansweeper Cloud Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of Defender for Cloud Apps Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of Defender for Endpoint Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of Nutanix Status Values to ServiceNow Status Values
-
Rule 4 - Mapping of Omnissa Workspace ONE Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of SolarWinds Status Values to ServiceNow Status Values
-
Rule 5 - Mapping of VMware Status Values to ServiceNow Status Values