Access the DataSync for ServiceNow DataSync Settings page at Perspectium > Control and Configuration > Properties > DataSync Settings.

Please note that the following settings are only available once you have installed and configured DataSync for ServiceNow. 

Your DataSync Settings page contains the default encryption and decryption keys that are used for shared and subscribed data, as well as various configuration options for your bulk shares and inbound messages. Here are the settings you can change from this page:





Share display values for reference fields and choice lists

Display values are resolved display values of referenced records in the current record being shared. By default, ServiceNow display values for reference fields and choice lists will not be shared out in your dynamic shares and bulk shares. You can change this setting in order to enable the sharing of display values for these fields.

This feature is useful if you're sharing tables that do not need to include referenced records. The display value may contain enough readable information for your report.

Here's how to change the setting:

  1. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  2. To enable this feature, turn on the toggle under Enable DataSync to add display value fields for reference and choice fields (prefixed with 'dv_' by default)

  3. Scroll to the bottom and click Save.

  • Display values will NOT be shared in schemas to ServiceNow instances.
  • Display values do not ensure referential integrity when used to join with other tables. To ensure accurate joining between tables, always rely on the actual sys_id value in the reference field instead.
  • With DataSync Agent, the columns for the display value will be sent to the database as a separate column, e.g. a state column have the numerical value and a dv_state column will have the actual value.


↑ Go to top of page



Use a percentage of workers to run concurrent scheduled bulk shares

In some cases, you may find that scheduled bulk shares are impacting the performance of your ServiceNow instance, as they use too many of the instance's available scheduled jobs (workers). If this happens, a good troubleshooting practice is to specify a percentage of the workers on your ServiceNow instance's nodes that will run scheduled bulk shares concurrently. Here's how:

  1. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  2. Use the dropdown labeled Percentage of workers used to run concurrent Scheduled Bulk Shares to select your desired percentage. 

  3. Click Save. 


↑ Go to top of page



Save Perspectium properties in the sys_properties table

This feature lets you improve the overall performance of your Perspectium integration by saving all properties related to your Perspectium integration to ServiceNow's System Property (sys_properties) table. By default, this option is disabled, and your Perspectium-related properties are saved in the Perspectium Properties table (u_psp_properties). If you enable this option and then make changes to your Perspectium properties, you can then copy those properties to the Perspectium Properties table by disabling this option again.

Here's how:

  1. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  2. To enable this feature, turn on the toggle under Save Perspectium properties in the sys_properties table.

  3. Click Save. It may take 2-3 minutes for this change to be applied to your instance, as the system saved all Perspectium properties over to the sys_properties and rebuilds the system cache.

  • Enabling this feature will write all of Perspectium's application properties to ServiceNow's sys_properties table. The application will then use this table to access all of its properties, increasing the frequency of access to this table and its caching. Please disable this option if you run into issues.  
  • If, after enabling this option, the u_psp_properties table is deleted, you can regenerate the u_psp_properties table at Perspectium > Control and Configuration > Finish Install > Confirm.
  • If enabling this option, be sure NOT to enter a value higher than 15000000 for the com.perspectium.output_bytes_limit property or a value higher than 8000 for the com.perspectium.output_row_limit property.


↑ Go to top of page



Disable inbound messages

By default, DataSync for ServiceNow allows your ServiceNow instance to receive inbound messages. However, if your ServiceNow instance is to be used for sharing purposes only (and not for subscribing purposes, or the receipt of incoming messages from other apps or data sources), you have the option to disable inbound message functionality. Here's how:

  1. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  2. To enable this feature, turn on the toggle under Disable inbound messages.

  3. Click Save. 


↑ Go to top of page



Enable multiple jobs to process messages in the inbound table

By default, the Perspectium DataSync Subscriber scheduled job in ServiceNow pulls and processes the messages from your Mesh server's inbound queues. However, you can also have the job pull messages into the ServiceNow inbound table (psp_in_message) in a Ready state so that Perspectium Inbound Processor scheduled jobs process the inbound table. This allows you to prioritize the processing of your inbound messages by configuring the Perspectium Inbound Processor jobs to apply various filters. 

This is an advanced capability for DataSync for ServiceNow, so we recommend you enable this functionality in your test environment(s) first. Note that enabling multiple inbound processor jobs allows you to have greater control over how and when you are subscribing to data that is being shared out by other data sources/applications.

Here's how to enable this feature:

  1. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  2. To enable this feature, turn on the toggle under Allow DataSync inbound messages to go to a state of ready isntead of being consumed immediately...

  3. Click Save. 
  4. Now, go to Perspectium > Control and Configuration > All Scheduled Jobs.

  5. In the Schedule Jobs table, find and select the Perspectium Inbound Processor job. 

  6. Within the script for this job, find the addCustomQuery function on line 50 and modify the script by adding your customer queries.

    To do this, choose one of the following options:

    Add customer queries by key:

    function addCustomQuery(igr) {
    igr.addQuery("key", "=", "dev12345");
}


    OR

    Add customer queries by name:

    function addCustomQuery(igr) {
    igr.addQuery("name", "CONTAINS", "incident");
}


  7. Click Update (top right)

  8. Create a copy of the modified job so you can apply other filters to enable simultaneous processing.


↑ Go to top of page



Skip updating the sys_domain_path field when subscribing to records

This feature allows you to skip updating the sys_domain_path field on a record to keep the value as it currently is, or allow the system to update the record appropriately if the domain changes. In domain-separated ServiceNow instances (Helsinki version or later), if you update a record without changing the sys_domain field, the sys_domain_path will be updated to the default global value of “/” that comes in with the incoming record. Prior to the ServiceNow Helsinki release, the system would instead auto adjust to the proper domain path after updating the record.

Here's how to enable this feature:

  1. First, you must request domain separation for your subscribing (Helsinki version or later) ServiceNow instance.

  2. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  3. To enable this feature, turn on the toggle under skip updating the sys_domain_path field when subscribing to records.

  4. Click Save. 


↑ Go to top of page



Alert before bulk sharing a large number of records

This feature will enable an alert to pop up within your instance whenever a ServiceNow bulk share that you're trying to execute exceeds a minimum number of records. By default, the minimum number of records to trigger an alert is 1,000,000. Here's how to turn on that alert:

  1. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  2. To enable this feature, turn on the toggle under Alert me before bulk sharing a large number of records.

  3. Enter the desired minimum number of records in the field labeled Minimum number of records to trigger an alert before bulk sharing.

  4. Click Save. 


↑ Go to top of page



Generate unique names for business rules associated with dynamic shares

This feature allows you to allow newly created business rules to have a unique name. By default, the business rule created is named Perspectium Replicate.

  1. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  2. To enable this feature, turn on the toggle under Generate unique names for the business rules associated with dynamic shares.

  3. Click Save. 


↑ Go to top of page



Set receipt tracking

Perspectium's receipt (u_psp_receipt) table as used for Data Guarantee in ServiceNow is rotated to preserve your instance performance. See ServiceNow Table Rotation for more information. 

To configure how often the receipt table is rotated, follow these steps: 

  1. Go to Perspectium > Control and Configuration > Properties > DataSync Settings.

  2. Scroll to the input labeled The number of days to keep message receipts before being deleted...  
    (info) NOTE: This applies to messages in any state (success, pending, error). The number of days must be less than 100.

  3. Enter the number days you want to keep the records in the receipt table. 

  4. Below the property is The number of rotations of deleted data to keep before being overwritten...
    (info) NOTE:     If you enter 10, there will be 10 rotations of deleted data before the first instance is overwritten. The number must be less than 100.

  5. Enter the number of rotations.  

  6. Click Save.


↑ Go to top of page