June 2022 Release Notes

Customer Data Activation

Salesforce Service Cloud, Balaton, Version 2.4

This new version is published to Appexchange with the following enhancements and fixes:

Customers can now be merged in SessionM directly from Salesforce

If Merge in SessionM on Parent Merge is enabled in the package configuration, then Account (or Contact) merges in Salesforce will automatically result in corresponding customer merges in the SessionM platform. Any data changes will be kept in sync from the survivor record in Salesforce to the survivor customer in SessionM. The customer survivorship in SessionM is determined based on the email or external ID (as configured) saved on the survivor parent record after the merge.

The customer data flow between Salesforce and SessionM was improved to cover multiple use cases:

1. Syncing from Salesforce to the SessionM platform can be done in the following ways:
   • Automatically by creating or editing an Account (or Contact), if Sync Customer Changes with SessionM is enabled in the package configuration and a corresponding field mapping exists;
   • Manually by using the SessionM Customer Profile component;
   • From the subscriber’s own code by using the global method smsfsc.SessionMGlobalHandler.syncToSessionM
2. Syncing from the SessionM platform to Salesforce can be done in the SessionM Customer Profile component. The sync will happen automatically on component load if Auto Sync from SessionM Loyalty is enabled during the component configuration. Otherwise, the data will be synced once the “Sync from SM” button is pressed.

The following issues have been fixed:

• Fixed the phone number mapping to allow clearing the phone number field from SFSC
• Fixed multiple issues with custom attribute mapping and non-editable fields
• Fixed a bug causing an error to display on load of the Notes component
• Fixed custom accesses and improved error handling for standard users

The following features have been deprecated and removed:

• Removed the smsfsc__SessionMUser__c.smsfsc__CallApiInTrigger__c technical field. It was previously used to enable/disable calling the SessionM APIs from the smsfsc__SessionMUser__c trigger. This behavior is now handled with static variables.
• The processing of multiple customers in batches was updated to use only one Queueable class SessionMCustomersQueue for better control over the flow, faster job chaining, and avoiding potential conflicts with existing Batch classes in the subscriber org. The Batch classes EnrollBatch and SessionMCustomersUpdateBatch were deprecated and flagged for deletion in a future release.

You can see the updated SessionM Loyalty for Service Cloud Administration Guide here.

Improvements

Timeline Enhancements

• We've improved searching for events from the timeline by adding the ability to filter using the last_id attribute, plus the search results can now be paginated. With this enhancement you can easily filter events that occurred within the same timestamp. This is available via the UI and via an API request.
• We deployed a query check to avoid unnecessary queries, thus preventing needless scans of the full timeline database tables. This was deployed to production for all clients on May 15, 2022.

Bug Fixes

Catalog – Fixed an issue that caused an incorrect 500 error to be thrown during the processing of a Catalog category with an incorrect external_id. This has been corrected to a 400 'bad request' error.

Personalized Engagement

Improvements

Customers

• Enabled editing of Date of Birth field in the Customers module. You can now change the Date of Birth of a customer by selecting Edit on the Profile tab and then either typing a date in MM/DD/YYYY format or choosing from the date picker.
• Added pagination to the Offers tab in the Customers Module. You will now see the first 10 offers in a customer’s profile wallet, and you can navigate through any additional pages to see the remaining offers.

Bug Fixes

Creative Templates – Fixed a bug where search was not working in the Creative Templates module.

Loyalty And Offers

Improvements

Offer Issuance & Offer Redemption – Added Asia-Pacific Region countries (for example, Thailand, Japan, Australia, Indonesia, Singapore, Malaysia and so on) and their time zone options to the Offer Issuance and Offer Redemption period sections on the offer setup page.

Bug Fixes

Offers API – Updated the offers/acquisition/issue endpoint in our documentation to remove the acquisition_schedule option under the ignore_restriction_types parameter because it is not honored. Adding this functionality back is scheduled for later in the year.

Reward Store – Added validation to check the status of a reward before deducting points for purchase. This fixed a bug that was allowing customers to try and purchase inactive rewards, deducting their points but not delivering the reward.

Platform Wide

GDPR Export API Enhancement to Return File Path

Previously, our GDPR API to request an export of a customer's personal data was only available as a CSV downlaod in the Customer's module on our platform. We've enhanced the GDPR Export API to now return the URL where the generated file is stored. This makes it possible to fully automate GDPR export requests with SessionM and unlocks additional workflows. For example, if the GDPR Export request is something that you let your customers do via your mobile app, our API now enables you to provide the file for download seamlessly within the app experience.

Note: A temporary (24 hour) pre-signed download URL will be generated and will grant access to only the requested customer's privacy files on our servers. You will be responsible to retrieve the file with the provided pre-signed URL and securely transmit the privacy file to your customer with a mechanism outside of the SessionM platform.

Our Data Privacy API documentation will be updated with this change soon.