Shared Queue configurations are used to transfer data out of Salesforce to a named queue in the 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 and routing rules are applied. To create a new Shared Queue configuration:
An “Alias” field has been added to the Queue configuration form for use with dynamic share Apex triggers. By specifying an alias for a queue, a dynamic share trigger will be created referencing this alias instead of the queue's ID as is currently the case.
This will allow you to more easily move Apex Triggers from sandbox/dev to production. Because Apex triggers cannot be easily modified in production (Salesforce has you create/modify the trigger in sandbox/dev first and then move them over to production), you can use the Alias field so as to not have to modify the trigger after testing in sandbox/dev and before moving in production.
For example, you can create a test queue in your sandbox with the alias “db” and then create a different queue in production with the same alias “db”. Then when you create the Apex trigger in sandbox and test to verify everything works as expected, you don't have to modify the trigger again with the production queue's ID since both have the same alias.
Aliases are only relevant for dynamic shares since bulk shares are run with background jobs that do not require Apex triggers.
Subscribe Queues configurations are used to transfer data from a named queue in the Perspectium MBS into Salesforce. To create a new Subscribe Queue configuration:
Note: When sharing from ServiceNow to Salesforce, please use AES128 encryption since Salesforce currently does not support TripleDES encryption.