---
title: "Additional DataSync for ServiceNow Features and Customizations"
canonical: "https://docs.perspectium.com/space/Iodine/1704357/Additional%20DataSync%20for%20ServiceNow%20Features%20and%20Customizations"
format: markdown
---
In addition to the fundamental features of DataSync for ServiceNow included in the  various modules  that are accessible throughout the platform, there are a few other customizations you may want to make use of. For example, you may want to clone an instance or uninstall DataSync for ServiceNow. Explore these additional features/actions below! Switch UI versions There are two user interface (UI) versions you can choose from for the   DataSync for ServiceNow   application:   Legacy UI   and   New (He20) UI .  The   New (He20) UI   version features an improved UI designed for the newest Helium release. It has minor changes here and there to make your experience more efficient and seamless. The   Legacy UI   version contains the previous (UI) style use in Gold release and earlier.  The UI version that you use is completely based on your own preference. However, please note that most of the instructions included throughout this docs site for our Helium release, and future releases, are based on the  New (He20) UI .  Want to switch between the two versions? In your ServiceNow instance, simply click the button at the bottom of the left-side panel—it will say either  Switch to Legacy UI  or  Switch to New UI , depending on the version you're currently using.   NOTE : Another way to check what UI version your instance is using is to check the heartbeat outbound message. The attribute field will contain the UI version, i.e. ui=He20, ui=legacy.  ↑ Go to top of page Clone an instance Cloning an instance is done via the ServiceNow interface. Please visit  this page  for information and instructions on doing so.  When cloning an instance, we have provided default exclude and retention definitions which work for most. Some of the information below is concealed—follow the "click to reveal" buttons to expand and reveal the contents! Clone exclusion The following are tables that are marked for the   clone   to exclude: Table Display Name Short Description Component u_psp_table_map PSP Table Maps Definitions for inbound and outbound table mappings DataSync u_psp_table_field_map PSP Table Map Fields Fields included in table maps DataSync u_psp_queues Queue Definitions Queue definitions for Sharing/Subscribing to Perspectium Message Bus queues DataSync u_psp_imp_alert Import Alert Import Set table of inbound alerts DataSync u_psp_alerts Alerts Perspectium Alerts DataSync psp_replicate_conf Replication Configurations Configurations for Dynamic Sharing and Subscribing DataSync psp_out_message Outbound Messages Outbound Message Queue DataSync psp_in_message Inbound Messages Inbound Message Queue DataSync psp_bulk_share Bulk Share Bulk Shares DataSync u_psp_scheduled_bulk_share Scheduled Bulk Shares Scheduled Bulk Share definition DataSync u_psp_log_message Logs Perspectium Log Messages DataSync u_psp_message_set_activity Message Set Activity Message Set transactions DataSync u_psp_properties PSP Properties Perspectium Properties DataSync u_psp_data_cleaner Perspectium Data Cleaner Perspectium data cleaner rules DataSync u_psp_sit_template Situation Template Observer Alert Situation Templates Observer u_psp_situations Observer Situations Situation transactions generated from alerts Observer psp_follow_transaction Follow Transaction Definitions Observer Follow Transactions Definitions Observer psp_event_subscription Event Subscription Definitions Observer Event Subscription Definitions Observer u_psp_actions Perspectium Actions Observer Action Definitions Observer Clone preservation The following are tables that are marked for the   clone   to  preserve on the target instance: Table Display Name Short Description Component u_psp_table_map PSP Table Maps Definitions for inbound and outbound table mappings DataSync u_psp_table_field_map PSP Table Map Fields Fields included in table maps DataSync u_psp_queues Queue Definitions Queue definitions for Sharing/Subscribing to Perspectium Message Bus queues DataSync psp_replicate_conf Replication Configurations Configurations for Dynamic Sharing and Subscribing DataSync psp_bulk_share Bulk Share Bulk Shares DataSync u_psp_scheduled_bulk_share Scheduled Bulk Shares Scheduled Bulk Share definition DataSync u_psp_properties PSP Properties Perspectium Properties DataSync The Perspectium Properties are retained, so connectivity to the Message Bus works when the cloned instance is brought up. Script execution When cloning an instance, we recommend for you to  Stop All Jobs . This will stop any data from being posted during this   clone . It should also prevent Scheduled Jobs from kicking off on the target instance until you manually enable them. Exclude audit and log data When  requesting a  clone   of a ServiceNow instance , you will need to select the  Exclude audit and log data  option to not  clone  Perspectium tables and their data. Though the Perspectium tables are listed in  Exclude Tables  list, per the  Exclude audit and log data  option's   description, this option also needs to be selected for this list to be honored. Post clone steps Once you have cloned an instance, we highly recommend that you follow these steps to ensure that the clone did not impact any Perspectium replication:  Make sure your Perspectium properties are in order by going to the table directly ( u_psp_properties ). Reset dynamic share business rules to ensure that they are cleaned and recreated as necessary. Verify data cleaner records exist. If they don't,  run Perspectium finish install scripts  again.  Additionally, if you have made any changes to these records in your original instance, add them in your cloned instance. Restart jobs in order to re-enable the Perspectium application for sharing and subscribing to data. Validate data transfer by performing a small bulk share or dynamic share to make sure that the data is leaving the instance. Protections against cloning for Perspectium properties The   PSP Properties   table will have a field called   Instance Created On . This field will be automatically populated when  finish install  is executed with all the other default Perspectium Property fields. The finish install script will also clean up any duplicated properties and keep only the properties that belong to the current working instance. A Post   Clone   Cleanup Script will automatically run after your instance has been cloned. The script will query the existing Perspectium Properties table and delete any of the records that do not have an I nstance Created On  field matching the current instance. ↑ Go to top of page Uninstall DataSync for ServiceNow The   Uninstall   module ( Perspectium  >  Uninstall ) ensures easy and secure removal of Perspectium application functionality from your ServiceNow instance. When uninstalling Perspectium application, all scheduled jobs, queues, bulk/dynamic share configurations, subscribe configurations, business rules, and script actions related to DataSync will first be deactivated to prevent unwanted actions and then deleted. All DataSync tables, modules, and UI pages will also be removed from your ServiceNow instance. In order to run this module and uninstall DataSync for ServiceNow, you must  install the   Perspectium Uninstall  update set in your ServiceNow instance.  You can request the download link for this update set by contacting   Perspectium Support . Once you have the update set, here's what you do: In your ServiceNow instance, go to  Perspectium  >  Uninstall . This will only appear if you have successfully installed the  Perspectium Uninstall  update set. On the resulting page, click  Confirm .  You may need to log out and then log back into your ServiceNow instance to ensure that all Perspectium modules are removed from your left side list display. Also, if any Perspectium modules were marked as favorites prior to the uninstall process, you can remove the modules by selecting the   -   icon on to the right of the module. Records created by the Perspectium application in the sys_dictionary and sys_documentation table may remain after Perspectium application is uninstalled. They  WILL NOT  interfere with ServiceNow functionality. This feature does not uninstall the   Common Document   import set tables.  ↑ Go to top of page Share knowledge articles when view count changes ServiceNow keeps track of the  views  for each Knowledge Base ( kb_knowledge ) article by updating the View Count ( sys_view_count)  field on the article's record each time it is viewed. However, this update is done such that no other fields are updated on the record (including system fields such as the  sys_updated_on  field) and as a result does not trigger business rules or flows (including those created by dynamic shares) to fire. Since article views fire a  kb.view  event  each time an article is viewed, you can create a ServiceNow  Script Action  that is triggered when this event happens. This will allow you to dynamically share out Knowledge Base articles when the view count is changed.  This is an advanced configuration, and is NOT part of standard functionality. Contact  Perspectium Support  for assistance if you experience any issues with the configuration.  In order to use this feature, you must  install and configure DataSync for ServiceNow  and  create a shared queue . You must have a shared queue setup since you'll be creating a new dynamic share with a script action to carry out this task. Now, you're going to  create a new dynamic share using business rules , and set it up with the following configurations: Go to  Perspectium   >   Perspectium Core  >  Shares   >   Dynamic Share  >   Create New Dynamic Share . Select  Business Rule   as the dynamic share type and click  Submit . On the resulting New Record page, find and select the  Knowledge   ( kb_knowledge ) table from the  Table  dropdown, as seen in the image below. Check the  Active  box. Check the  Update  box. Complete the rest of the dynamic share setup to meet your needs, and reference  this article  if you need assistance doing so. When you're done, click  Submit . Now, go to  System Policy  >  Events  >  Script Actions  (type  Script  Actions  in the filter navigator at the left . On the resulting  Script Actions  page, click  New , which will bring up a New Record form. Type  Perspectium Share Knowledge  in the  Name  field. Select  kb.view  from the  Event name  dropdown. Check the  Active  box. Then, fill in the  Script  field with the following: pspShareKnowledge();
 
function pspShareKnowledge() {
    var pspR = new PerspectiumReplicator();
    var tableName = "kb_knowledge";
     
    var kbgr = new GlideRecord(tableName);
    kbgr.get('sys_id', event.instance);
    kbgr.query();
    if (!kbgr.next())
        return;
     
    var qc = new GlideRecord('psp_replicate_conf');
    qc.addQuery("table_name", tableName);
    qc.addQuery("sync_direction", "share");
    qc.addQuery("action_update", "true");
    qc.addQuery("active", "true");
    qc.query();
    while(qc.next()) {
        pspR.shareRecord(kbgr, tableName, 'bulk', qc.sys_id);  
    }
} Click  Submit . ↑ Go to top of page