Perspectium Replicator transfers data between Salesforce and the Perspectium Message Broker Service (MBS) via queues. Dynamic and Bulk Share data in Salesforce are written to the Outbound Message queue in Salesforce. A MultiOutput Processing Job sends messages from the Outbound queue to a queue in the Perspectium MBS.
Please ensure you have the proper credentials to create the message queue or the queue has been created by the Perspectium team email@example.com on the Perspectium MBS before creating it inside Salesforce.
Perspectium Replicator uses Scheduled Jobs to process inbound and outbound replication data.
The MultiOutput Processing Scheduled Job is used to send outbound replication data from Salesforce to the Perspectium Message Broker Service. Once scheduled, the job will run once every minute. To begin replicating shared data you must configure and activate an instance of the MultiOutput Processing job by doing the following:
The Replicator Subscriber Scheduled Job is used to process inbound replication data from the Perspectium Message Broker Service to Salesforce. Once scheduled, the job will run once every minute. To being subscribing to shared data you must configure and activate an instance of the Replicator Subscriber Job by doing the following:
Shared Queue configurations are used to transfer data out of Salesforce to a named queue in Perspectium MBS. If a Shared Queue configuration is not specified for a Dynamic or Bulk Share, the messages are sent to the default psp.in.salesforce queue in Perspectium MBS where routing rules are applied. To create a new Shared Queue configuration:
Subscribe Queues configurations are used to transfer data from a named queue in Perspectium MBS into Salesforce. To create a new Subscribe Queue configuration:
Note: When sharing from ServiceNow to Saleforce, please use AES128 encryption since Salesforce currently does not support TripleDES encryption.
Setting up bulk share allows a Salesforce instance/organization to share a pre-filtered range of data in a table data at once. The consumer or subscriber of this data can be another instance/organization in Salesforce or a Perspectium Agent. You will need to create a bulk share configuration for each table you want to share.
Bulk shares always result in an attempt to update the record before inserting it at the consumer. The update uses the Id field value when available. You can override this behavior by selecting the “Insert only” option as defined below. Selecting the “Insert only” assumes that no records currently exist in the destination table.
To create a Bulk Share click on the Bulk Shares tab. Next click New and enter the following:
Note: There is a known issue where the Submit for Approval button appears on Dynamic Share and Bulk Share forms. If you see this button, click the Edit Page Layout link in the top-right corner and remove the button from the layout.
To cancel a running Bulk Share perform the following steps:
Setting up a Dynamic Share configuration allows a Salesforce instance/organization to share table data in real time. The consumer or subscriber of this data can be another instance/organization of Salesforce or a Perspectium Agent. You will need to create a share configuration for each table you want to share.
To create a Dynamic Share configuration to begin near real-time replication of table data click on the Dynamic Shares tab. Click New and enter the following:
The Apex Trigger Details section contains a read-only version of the Apex Trigger code generated when the Dynamic Share configuration is saved. This can be used to manually create the Apex Trigger if the Tooling API is not available for dynamic Apex Trigger creation. Salesforce does not allow dynamic creation of Apex Triggers in production orgs. Dynamic Share triggers should normally be migrated from sub-production orgs using change control process. To perform this task manually, click the Go to Trigger List link and create or update the trigger using the content in the Apex Trigger Details section.