Rule 5a – Synchronization of Manufacturer, Carriers, and Vendors (including Null) on the Parent CI

Rule Synopsis

These are the rule/s that control whether CI Sync synchronizes, and therefore sets, a manufacturer, vendor or carrier style attribute on the main/parent CI in ServiceNow.

Examples include:

Setting the hardware manufacturer of equipment read from Lansweeper and other sources of hardware assets.
Setting the software manufacturer of software read from Lansweeper, InTune of Defender for Cloud Apps.
Setting the vendor (i.e. carrier) of mobile services read from InTune.
Setting the vendor (i.e. carrier) for express routes from Azure.
Setting the vendor (i.e. carrier) for WAN links from SD-WAN sources.
Setting the vendor (i.e. carrier) for all resources read from CI Sync supported cloud sources (e.g. AWS, Azure, GCP).

These rule/s also control how manufacturers, carries or vendors with a Null value in the source system are treated on the ServiceNow side.

Rule Details and Default

For the setting of the manufacturer (or carrier or vendor or similar) against the main/parent CI

By default, CI Sync does sync/set the manufacturer (or carrier or vendor or similar) as read from the source system asset record, against the main/parent CI record in ServiceNow.
This rule applies to the manufacturer (or carrier or vendor) attribute on each individual CI. That is, it applies to whether CI Sync sets a foreign key reference between the individual CI and the Manufacturer Master Data table (i.e. the core_company table) in ServiceNow.

For handling of manufactures (or carrier or vendor or similar) with a Null value in the source system

By default, CI Sync passes through a Null manufacturer (or carrier or vendor or similar) value to the main/parent CI. Therefore, the CI will have no foreign key reference between the individual CI and the Manufacturer Master Data table (i.e. the core_company table) in ServiceNow.

Also, we recommend reading the Related Rules further below for the rules related to the Manufacturer Master Data table.

Override Options

Context

For the setting of the manufacturer (or carrier or vendor or similar) against the main/parent CI

Customers may consider overriding the default rule so that CI Sync does not sync/set the Manufacturer value. This could be used in situations where another system or data source is controlling this attribute.

For handling of manufactures (or carrier or vendor or similar) with a Null value in the source system

Customers may consider overriding the default rule so that CI Sync persists a reference to the “Unknown Manufacturer” record in the core_company table (i.e. persists the sys_id of the “Unknown Manufacturer” record in the core_company table against each CI where the incoming manufacturer is Null in the source system).

Options

For the setting of the manufacturer (or carrier or vendor or similar) against the main/parent CI

The rule can be amended so CI Sync does not sync/set the equipement manufacturer parent CIs.
The rule can be amended so CI Sync does not sync/set the software manufacturer on CIs.
The rule can be amended so CI Sync does not sync/set the vendor attribute for assets that include a carrier attribute.
The rule can be amended so CI Sync does not sync/set the vendor attribute for Cloud Resources read from CI Sync supported cloud sources (e.g. AWS, Azure, GCP).

For handling of manufactures (or carrier or vendor or similar) with a Null value in the source system

The rule can be amended so CI Sync persists a reference to the “Unknown Manufacturer” record in the core_company table (i.e. persists the sys_id of the “Unknown Manufacturer” record in the core_company table against each CI where the incoming manufacturer is Null in the source system).

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 Set Manufacturers, Carriers and Cloud Vendors on Parent and Child CIs in ServiceNow.

For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.

Additional Information

N/A

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)