The following options are available:

Jobs

View the scheduled jobs that process inbound and outbound data to the Perspectium Integration Mesh. There are two job types:

MultiOutput Processing - The job that will run to process messages with a status of Ready in the Outbound Messages table and send them to the specified shared queues in the Integration Mesh.

Replicator Subscriber - The job that will consume messages from the specified subscribed queues in the Integration Mesh. The messages will be consumed and processed by the Perspectium application and saved into the Inbound Messages table in the app so you have the messages for reference.

When creating a new job, you have the following options available:

Description - A description to give the job for your reference (this isn't used). If no description is entered, the job type is used along with the datetime it will run or be aborted i.e. MultiOutput Processing Scheduled at 2024-02-08 14:24:15.036.

Job Type - The type of job as mentioned above.  NOTE: It is recommended to have only one job for each job type to avoid race conditions where the same messages are sent out twice.

Job Interval - How often the job should run.

Job Delay Interval - An interval to delay the job and try again if the maximum number of Salesforce jobs running has been exceeded and the job cannot be executed. For example, if the job tries to run and it cannot execute and you have the delay set to 5 minutes, it will try again in 5 minutes. If not set, it will try again at the job interval which may fail again if the maximum number is still exceeded. This option is a way to give Salesforce time to complete executing other jobs without continuing trying to run again.

Email User - A user to email if the job has connectivity issues connecting to the Perspectium Integration Mesh.

Email Interval - How long we should email about connectivity issues for. If the issue is ongoing until you fix it (such as bad Integration Mesh credentials), you will only be notified for the time specified here at which point it will no longer email even if the issue is still occurring.

Table Maps

Using table maps allows you to map a record and its fields to a JSON with your preferred field names in the outbound message that is shared out of Salesforce. This can be useful for when you want to map the record to specific fields for use by your target database/system which is already set up to get data from specific fields.

To create a table map for use in your dynamic or bulk share:

1. Create a new table map by going to the Tools tab and choosing the Table Maps option. Select the New Table Map option and the form will open to create the table map.
   
   
2. Enter the following information for the table map:
   1. Table Map Name  - A name for this table map to reference when selecting it in a dynamic or bulk share. This name is only used for reference and not as part of the outbound message.
   2. Source Table - The source table (SObject) to map from. This should match the table selected in the dynamic or bulk share where this table map is used.
   3. Target Table Name - The name of the table that will be used in the name field of outbound messages. Outbound messages have the format of <table_name>.<action> (i.e. Case.bulk) so the DataSync Agent that consumes a message knows what table the record is intended for and what action to take. So you can use this to change the outbound message to use the value specified here. For example, if you enter the value incident, a bulk share using this table map will create outbound messages with the name of incident.bulk.
      
      
3. Click Save to save the table map.  NOTE: You will need to save the table map first before you can select the fields you want to map.
   
   
4. Select the fields you want to map to include in the table map. Use the Add New Field Mapping section to add each field, choosing the field from the source table to map from (Source Field) and entering what the name of this field should be in the table map (Target Field). Source fields listed from the source table will be listed using their field labels.
   
   For example, if you will be mapping fields from the Case table to incident and you want the Description field in the Case table to map to the short_description field in your generated table map, you would do the following:
   
   
   Clicking Add Table Field Map to add this field mapping to the table map. Repeat this step for all the fields you want to mapped. Once complete, save the table map. 
   
   
5. To delete a field mapping from the table map, choose the Delete option next to each field map (under the Action column). You can use the Delete All Table Field Maps to quickly remove all field mappings if you want to redo this table map and add new fields.
   
   
6. Next create a dynamic or bulk share where you want to use this table map. On the dynamic or bulk share form, there is a Table Map where you can look up the table map you created. Select this table map and save the dynamic or bulk share after finishing any other configurations.  NOTE: You will need to use a table map that has the same source table as the table selected in your dynamic or bulk share.

For example, if you want to share Case records and want to share them to the incident table in your database that has the fields short_description, sys_id and state, you can create a table map to share out Case records as follows:

Logs

View the logs generated by the Perspectium application. The configuration for how the application logs can be found in Properties.