Salesforce B2C Commerce: The 22.6 Release

22.6 Release: Einstein Dashboards

Again, here we are with the latest release notes of Salesforce B2C Commerce Cloud; time flies by fast, doesn’t it? Let us go over the June 2022 (22.6) release!

Einstein Dashboards

In this release, Einstein is getting a bit of love with better insights into the performance of your recommenders!

Drill down to a single recommender

It will now be possible to drill down to a single recommender in the dashboards to see how they perform over a selected period of time.

This will give merchants a better understanding of performance trends.

These metrics include:

  • Click-through Rate (CTR)
  • Add to Cart
  • Cart Conversion Rate
  • Attributed Revenue.


View top purchased and top viewed products

With this addition to these dashboards, you will be able to see more information about the performance of a recommender.

Reports now show how specific products perform, by being recommended in a particular recommender.

PWA Kit v1.5.2

A minor release has been made for the PWA Kit, containing a few bugfixes:

  • Fix invalid refresh token by @kevinxh in #527
  • Webpack config: no longer assumes that config dir exists by @vmarta in #522
  • Fix minor typos in readme and jsdoc by @alexvuong in #531


OCAPI

Access Key Management

New endpoints have been made available to manage access keys from an external application. Although this addition is mainly for in-store agents, according to the documentation, the addition will sound like music to the ears of people in charge of DevOps and CI solutions. 

To access these APIs, ensure the user has the “Manage_Users_Access_Key” permission.

Business Manager

EPS added to Salesforce Payments

EPS is an Austria-based payment method supported by all Austrian banks. You can add the EPS option to your storefront in Business Manager Payment Settings.

Avoid Chargebacks with Salesforce Payments

Use a site-specific descriptor to help shoppers identify the source of an account charge on their credit card statements to reduce payment disputes and chargeback requests. You set the customer statement descriptor in Business Manager Payment Settings. The setting overrides the value specified in your Stripe merchant account.

Development

Log Center

Filter and find storefront implementation errors, such as broken includes, significant header errors, and large request errors with a new filter option below the “Service Type.”

How: To find storefront implementation errors with Log Center, set the Service Type filter to “jwa” (see screenshot above).

Bugfixes

Unnecessary Product Update Index Task is performed after the Full Index Rebuild

An unnecessary Product Update Index Task was performed after the Full Index Rebuild, which publishes a new
index even if 0 documents have changed. This happened only if Incremental Index was enabled, 
even if NO product change had been performed after the Full Index Rebuild. Now, after a full search index update in
done and no documents have changed, the platform is not doing an Incremental Index afterward.

Rule Based Product Categorization - UI Changes to Include SiteContext when Saving/Fetching Rules

When creating/editing a ruleset, a dropdown is now provided (similar to the Locale dropdown). The dropdown
will be auto-selected to “default” and include all valid active Sites for that instance. When the merchandiser saves
the ruleset, the API to PUT/POST rules will consist of a new field to persist the SiteContext selected.

Dynamic Categorization - Value selection for String attributes with the "is one of" selector isn't working

Value selection for String attributes with the "is one of" selector isn't working. When the "is one of" selector is chosen, the user should be able to select multiple values. For String attributes, this isn't possible because you only get a normal input field for entering the value, with no possibility of adding various values. Expected Products should be shown in the preview tab based on the categorization rule. Actual Products are not categorized when multiple comma-separated values are used.

Although the status has recently changed to “fixed,” no version/release was linked. So it might be in the next or this release.

Table of Contents

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

More From My Blog