List of preservers and exclusions tables for cloning
Summarize
Summary of List of preservers and exclusions tables for cloning
When installing Service Exchange on a cloned ServiceNow instance, specific tables must be preserved or excluded to maintain proper connectivity and functionality. Using the default system clone profile may result in loss of critical Service Exchange data. To avoid this, customers should create a custom clone profile tailored to Service Exchange requirements.
Show less
This involves removing certain cleanup scripts and validating the inclusion of key Service Exchange tables within the profile’s preserver and exclusion lists. After cloning, connections must be reestablished and Capture Definitions reactivated to restore full Service Exchange operations.
Clone Profile Configuration for Service Exchange
- Create a custom clone profile via All > System Clone > Clone Profiles and select New.
- Remove the Remote Process Sync Disable Records script from the Cleanup scripts list.
- Ensure Service Exchange tables are properly included in either the Preservers or Exclusions lists according to the provided specifications.
Impact of Preservers and Exclusions on Clone Behavior
The clone operation’s effect on tables depends on their inclusion in the preserver and exclusion lists:
| Preserver Table | Exclusion Table | Result on Target Instance |
|---|---|---|
| Included | Included | Existing data on the target is retained; no records are copied from the source. |
| Included | Not included | Target retains existing records and adds new records from the source; existing records are not overwritten. |
| Not included | Included | Target table is emptied; no data copied from source. |
| Not included | Not included | Target table is replaced entirely with source data, overwriting existing records. |
Preservers and Exclusions Tables for Service Exchange
Customers must update their clone profile’s preserver and exclusion lists to exactly match the Service Exchange tables specified. This includes various catalogs, sync definitions, error codes, tasks, connection settings, and user criteria related to Service Exchange provider and consumer roles.
The tables are categorized into Global, Provider, Consumer, Remote Process Sync, Transport, Transporter, and Employee Profile groups, each with designated preserver and exclusion lists to control cloning behavior.
Practical Examples
- snsbservicebridgesettings (in both lists): preserves connection settings on target without overwriting them from source.
- snsbconentitlement (preserver only): target retains existing entitlements and adds new source entitlements.
- snsberror (exclusion only): target’s error records table is cleared and not populated from source.
- snfdsoffering (not included in either list): target table data is fully replaced by source data.
Key Outcomes
- Customized clone profiles ensure critical Service Exchange data is maintained or refreshed appropriately during cloning.
- Maintaining accurate preserver and exclusion lists preserves connectivity, configurations, and data integrity post-clone.
- Reestablishing connections and reactivating Capture Definitions after cloning restores full Service Exchange functionality.
When installing Service Exchange, certain tables must be preserved or excluded to maintain connectivity after a clone.
- Remove the Remote Process Sync Disable Records script from the Cleanup scripts related list,
- Validate if the following Service Exchange tables are included in the custom profile.
Service Exchange tables to preserve and exclude
The following scenarios describe how clone operations affect table data based on table configuration in the preservers and the exclusions tables list.
| Preservers tables | Exclusions tables | Result on target instance |
|---|---|---|
| Included | Included | Target table retains existing data. The system preserves existing records and copies no records from the source. |
| Included | Not included | Target table retains existing records and receives additional records from the source table. The system does not overwrite existing records. |
| Not included | Included | Target table is empty after the clone. The system discards existing target records and copies no records from the source. |
| Not included | Not included | Target table contains only source table data. The system replaces all pre-existing target records with records from the source. |
Update the Clone Profile Preservers and Exclusions lists to include only the Service Exchange tables specified in the following preservers and exclusions tables. Add any missing tables from the specified lists and remove any Service Exchange tables that are not included in these lists.
| Preservers table | Exclusions table | |
|---|---|---|
| Global |
|
|
| Base |
|
|
| Provider |
|
|
| Consumer |
|
|
| Remote Process Sync Transport | sn_sb_rps_connection (Provider only) | sn_sb_rps_connection (Provider only) |
| Transporter |
|
Na |
| Employee Profile |
|
"*" - Applicable for both provider and consumer.
The following scenarios describe how clone operations affect table data based on table configuration in the Clone profile preservers list and the Exclude tables list.
The following examples use tables from this page to illustrate each scenario:
sn_sb_service_bridge_settings (included in both lists): The system preserves connection settings you configured on the target instance after the clone. Settings from the source instance do not overwrite them.
sn_sb_con_entitlement (included in Clone profile preservers only): The target instance retains existing entitlement records and receives additional entitlement records from the source instance.
sn_sb_error (included in Exclude tables only): The error records table is empty on the target instance after the clone. The system discards error records that existed on the target and copies none from the source.
sn_fds_offering (not included in either list): The system replaces the target table with source data. Records that existed on the target instance before the clone are replaced by source instance records.