Documentation and community move
In May, a significant change is the decommissioning of the CCDC (Commerce Cloud Developer Center).
But do not fear! All documentation has been safely migrated to the primary Salesforce Developer Center!
The communities that were part of the CCDC have also been migrated into the existing Trailblazer Community, so all of that information (questions and answers) is not lost!
This is, in my opinion, an excellent move to integrate the Commerce Cloud community more into the Salesforce Ohana.
Encryption at Rest
To improve the platform’s security, a new PILOT program was started. This program aims to encrypt all customer data on the Salesforce B2C Commerce platform stored on the POD (servers).
This is achieved using Host Disk Encryption offered by the OS and Volume Encryption provided by NetApp.
Another great move to ensure all sensitive data stored on Salesforce servers are protected from “prying eyes.” 2022 is undoubtedly a year with a significant focus on improving the platform’s (already solid) base.
Note: Salesforce is actively looking for customers in the AMER region who deal with highly sensitive data (health information). If you are already an active customer, a realm move will be required.
As On-Demand Sandboxes have become the new standard for Salesforce B2C Commerce, the UI of the Control Center is being revamped as well.
We already had the option to schedule our Sandboxes uptime through a REST API, but a UI is now available to make life a little easier.
A beta program is available to test an integration between B2C Commerce Cloud and Tiktok. This Beta aims to create storefronts and advertise products on Tiktok using products and shopper activity data.
Currently, recruiting for this feature is paused until further notice!
Even though recruiting is currently on hold, it is good to see the Salesforce team is actively investigating integrating with social channels.
PWA Kit v1.5.x
As with SFRA, the first years will see quick releases with new features added. Besides the major “2.x” release currently in the developer preview, improvements are being made to the “1.x” version concurrently.
In this release, these new features and improvements were added:
Shopper Context API
The Shopper Context API will enable customers to build headless storefronts with personalization. This API is currently in the BETA stage, so you may opt in at your discretion.
Want to make use of this API? The documentation is available here!
SLAS Password-less Login
This new addition to the SLAS APIs will allow registered customers to log in without using a password.
Instead, it will allow you to log in using a private link sent to your email (and later through SMS or a TOTP application).
The documentation is available here:
This change gives us more flexibility in providing login options to customers.
Note: This API is only available for private clients
, and the email login templates only support plain text. For now, styling the e-mail for the password-less login option is out of the question.
Update: It turns out that HTML is supported; the API determines if it is plain text or not. Be sure to validate your HTML on different email clients, as the service does not do any validation of the template!
Dynamic Categorization is a recent addition to the Salesforce B2C Commerce Cloud feature list, allowing the automatic (job-based) assignment of products to specific categories on configurable criteria.
Over the past months, a lot of feedback has been provided on this feature. And in this release, two new updates are announced:
- Ability to create exclusion rules for products
- Maximum conditions for a rule have been increased from 5 to 20
Having the option to set more than five conditions will give merchandisers more flexibility when organizing their categories.
Salesforce Payments Credentials Storage
Salesforce Payments is getting some love in this release. The first addition is storing payment card credentials for:
- Future off-session use: Support for recurring subscription payments or delayed payments (pay when order is fulfilled)
- Save for on-session use: Store payment options for a quicker customer check-out (only available in a shopper session)
It is good to see these features being added to the “native” payment option within Commerce Cloud. Storing payment methods will open the door for new use-cases and allow customers to place orders faster and have a better user experience!
Klarna for Salesforce Payments
For most, Klarna is a well-known payment method. This option has now been added to Salesforce Payments giving shoppers the ability to use the three different pay-later options that Klarna provides:
- Pay Later
Another advantage for merchants is that no additional agreement needs to be signed with Klarna. But as always, with payment providers, check the costs per payment that are part of your existing agreement with Stripe.
Note: The merchant receives payments according to a payout schedule even though customers pay the amount later.
Custom Job Steps Context
Jobs that store non-primitive data types of values in dw.job.JobExecution.getContext() now fail. Previously, the job logged a warning, ignored the invalid value, and continued.
Known Issue Bugfixes
I have looked at the recently updated issues but found that they are still “In Review,” and none have been updated to resolve for this release.