Rule Synopsis
These are the rule/s (or CI Sync feature) that causes CI Sync to vary the behaviour of other rules between a CI Insert Operation compared with a CI Update Operation.
Rule Details and Default
-
By default, CI Sync does not use split-transform. Instead, the rules and behaviour of CI Sync is the same for a CI Insert Operation and CI Update Operation.
-
While the default behaviour is as stated above (i.e. the same rules apply to insert and update operations), there are two pre-defined exceptions:
Exception 1 - The Discovery Source Attribute
Exception 2 - The Correlation ID Attribute and Correlation Prefix Value
Override Options
Context
Customers may consider adopting split-transforms to cater for processes/workflows (in your customer specific instance of ServiceNow) that require different data/behaviours between a CI Insert Operation comparted with a CI Update Operation.
Customers may also adopt split-transforms if they have multiple overlapping source data integrations inserting/updating CIs in their CMDB.
Options
-
CI Sync can be enabled to use split-transforms. This feature is enabled in response to a customer requirement for different behaviours between CI insert and CI update operations. The different behaviours can span almost all other CI Sync Data Rules and therefore a Syncfish expert will consult extensively with customers before this feature is enabled and the various other data sync rules are amended.
Overriding via Connection Settings
N/A
Additional Information
N/A
Related Rules
-
All of those included in the above table.
Support Model for Rule Overrides
Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?
Answer: No (a plan is needed - see below)
Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule
Answer: Either a Silver Plan or Gold Plan