Rule Synopsis
These are the rule/s that control whether or not CI Sync automatic creates/inserts new locations into the ServiceNow Location (cmn_location) table.
Rule Details and Default
-
By default, CI Sync does not create/insert new records in the ServiceNow cmn_location table when an incoming location value from Azure cannot be matched to an existing record in the table.
Override Options
Context
Customers may consider overriding the default rule so that CI Sync extends the cmn_location table to include new locations read from Azure (i.e. to maintain referential integrity between the CI Location attribute and the cmn_location table entries).
Options
-
This Data Sync Rule can be overridden so that CI Sync does create/insert new cmn_location records.
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 Location Data Handling for Azure.
For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.
Additional Information
N/A
Related Rules
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)