Page History

From the Properties page, click General Settings (Perspectium > Control and Configuration > Properties > General Settings)

On the General Settings page, you can:

• Change/view your Perspectium Integration Mesh username, password, and/or URL
• Allow the sharing of incidents to Perspectium Support
• Delete error messages older than one day in the Outbound Messages table (via datacleaners)
• Generate debug logging
• Limit bytes/records for Outbound Message jobs
• Limit the maximum number of messages in the Outbound Messages queue
  
  

From the Properties page, click DataSync Settings (Perspectium > Control and Configuration > Properties > DataSync Settings)

Your DataSync Settings contain 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.

On the DataSync Settings page, you can:

• Share display values
• User a percentage of workers to run concurrent scheduled bulk shares
• Save Perspectium properties in the sys_properties table
• Disable inbound messages
• Enable multiple jobs to process messages in the inbound table
• Skip updating the sys_domain_path field when subscribing to records
• Alert before bulk sharing a large number of records
• Generate unique names for business rules associated with dynamic shares

Listed are a few of the Perspectium properties needed for the application:

ServiceNow table maps are typically used in Perspectium Service Gateway integrations to handle the mapping of fields in certain ServiceNow tables as data is shared out of your instance. You can include a table map as part of your ServiceNow dynamic share or bulk share to help with field mappings and data transformation.

 NOTE: When using a table map with a dynamic share, the dynamic share will trigger based on trigger conditions (i.e. create, update or filter conditions). So this may result in a dynamic share being triggered when a particular field is updated that is not in the table map. As a result, the table mapped record shared out may not have any updated content since all the fields mapped have not changed. To avoid this scenario, use the Share or ignore on specified field updates option.

 NOTE: If a table map is set, records with an attachment or message size greater than 5 MB will not be shared out due to ServiceNow platform limitations with how large one particular record can be.

Instructions

Prerequisites:

• First, you will need to commit a Perspectium update set containing table maps to your ServiceNow instance.
• You will also need to create a ServiceNow dynamic share or bulk share.

Instructions:

1. In your sharing ServiceNow instance, go to Perspectium > Perspectium Core > Shares > Dynamic Share or Perspectium > Perspectium Core > Shares > Bulk Share.
   
   
2. Click View Dynamic Shares or View Bulk Shares.
   
   
3. From the available shares, click on the one that you want to add a table map for.
   
   
4. In the Data Enrichment tab, click the search icon next to Table map.
   
   
   
   
5. From the resulting list, select the table map you want to add
   
   
6. Click Update (top right corner) to save your changes

By default, data replicated from existing tables will automatically create the same schema at the replicated database. The targeted database schema of replication needs to be flexible and customized in certain situations, such as: 

• An existing schema that the replicated data need to fit in
• A need to rename the field names or transform the field values using script at the source
• The resulting field types need to be modified to a specific type or field length

Customizing target database schema is done by using table maps in your dynamic share or bulk share. 

Prerequisites:

• Set up and configure DataSync for ServiceNow

Instructions:

1. In your sharing ServiceNow instance, go to Perspectium > Control and Configuration > Table Maps
   
   
2. Select the table map you want to use, review the information in the fields, and check the Generate schema box
   
    WARNING: If there are multiple table maps with the same Target table name, the agent will return the first record when querying against ServiceNow for the schema.
   
   For the purposes of these instructions, we'll use the table Incident to Common Incident.
   
   NOTES:
    
   
   • Checking the Generate schema box is required in the initial sharing of your records.
   • Specifying Field Type and Field Length is optional except for designating at least one field as Sys ID (GUID). This is required for the target database table to be created and queried for updates and deletes. 
   • The value specified in the Target table name field will be used as the name of the table in the database.
     
     
     
     

3. To share the table map output, you need to crate a dynamic share or bulk share and select the table map from step #1 in the table map field. The generated payload can be subscribed by an agent and the scheme created dynamically.
   
   In this example, the common incident table map will result in the following table schema, if consumed by a database agent for MySQL.
   
   

   Code Block
   language sql theme Eclipse
   mysql> describe common_incident; +---------------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------------------+--------------+------+-----+---------+-------+ | state | mediumtext | YES | | NULL | | | short_description | varchar(160) | YES | | NULL | | | description | mediumtext | YES | | NULL | | | priority | mediumtext | YES | | NULL | | | attachments | mediumtext | YES | | NULL | | | category | mediumtext | YES | | NULL | | | correlation_id | varchar(100) | YES | | NULL | | | number | varchar(40) | YES | | NULL | | | correlation_display | varchar(100) | YES | | NULL | | | caller_id | mediumtext | YES | | NULL | | | caller_email | varchar(100) | YES | | NULL | | | caller_full_name | mediumtext | YES | | NULL | | | comments | mediumtext | YES | | NULL | | | sys_id | varchar(224) | NO | PRI | | | | work_notes | mediumtext | YES | | NULL | | +---------------------+--------------+------+-----+---------+-------+ 15 rows in set (0.00 sec)

    NOTE: Even though we specified the number field as the required Sys ID (GUID) field in the table map, the number field does not become the GUID. Instead, the sys_id field is created as GUID (PRI key) and contains number values to be used for lookup during updates/deletes. This is consistent with replicating database views.

Here's how:

1. In your ServiceNow instance, go to Perspectium > Control and Configuration > Table Maps
   
   
2. Click New. 
   
   
3. Select the table map direction (Outbound or Inbound) from the Direction dropdown. The fields available will change depending on whether you choose Outbound or Inbound.
   
   Refer to ServiceNow table maps for more information on the difference between Outbound and Inbound table maps. 
   
   
4. Complete the required fields:
   
   • Enter a Name
   • (For Outbound table maps only) Select the table you want to create  table map for from the Source table dropdown
   • (For Outbound table maps only) Enter the name of the target table in the Target Table Name field (e.g. incident)
   • (For Inbound table maps only) Select the target table from the Target Table dropdown
     
     
5. Click Submit.