The Pendula Settings tab controls settings specific to the Pendula Salesforce app, such as activity history and which objects message recipient records should be created for.
You shouldn't need to update or change these settings too often once initially configured.
Define the URL where this tenant redirects external links to, in order view messages, experiences and flows within Pendula.
By default, you shouldn't need to change this unless you have been provided with a customised URL.
Create native events (in Activity History)
Pendula tracks key message events (such as an SMS failing or an email being opened), and will Salesforce events for each of these if this setting is turned on.
These events are associated with the Message record and visible in the Activity History of a recipient or triggering record.
If selected, you have two options regarding how Pendula should treat subsequent message events relating to the same Message record within Salesforce.
Update existing event
Updates the original Event with new incoming Pendula Message Events (only one native Salesforce Event is created per Message record). Select this if you only want to view the most recent message event within the activity history of a record.
Create new events
Creates a new Event for every incoming Pendula Message Event. This means there can be multiple native Salesforce Events for one Message record. Select this if you would like to view all message events within the activity history of a record.
Create Message recipient record
Create a Message Recipient record that associates the Message with its known "Recipient Id". This can either be a contact, lead or user.
If selected, Pendula will automatically match the Message with the relevant recipient record within Salesforce.
If no recipient Id is available, it will match based on the mobile phone or email address of the message. If this occurs and there are multiple records sharing the same contact details, multiple Message recipient records will be created.
If selected, you can determine which recipient records should be included in the message recipient matching process (at least one must be ticked).
Match all potential Contacts
Create a Message Recipient record for any Contact that matches the email address or mobile phone number associated to this message.
Match all potential Leads
Create a Message Recipient record for any Lead that matches the email address or mobile phone number associated to this message.
Match all potential Users
Create a Message Recipient record for any User that matches the email address or mobile phone number associated to this message.
Update messages upon process completion
This should be selected, and remain ticked by default.
This allows for processes within Pendula and other external packages to trigger off of a new message record being created after it the syncing process has been completed.
If this is unticked, some processes (such as the creation of Inbox records) will stop working.