21.3 Release

The B2C Commerce 21.3 release occurs February 18, 2021 through March 23, 2021.

• Assign Promotions and Pricing to Specific Stores
  Merchants can now assign price books and promotions to stores. This feature lets shoppers view pricing and promotions targeted to their selected store in session.
• Text in Content Slot Fields Validate Properly
  Free-form text in the content asset, product, and category Content Slot fields now validate properly. If an entry exceeds 3,500 bytes, an error is returned. To remedy the error, consider using Add to select IDs or limit entries to just the ID, instead of the entire content.
• Change Customer Passwords with the Headless Commerce API
  To provide this functionality, we updated the OCAPI Shop API PUT customers/{customer_id}/password endpoint to change the password in the PUT call instead of in the afterPUT hook. The Headless Commerce API doesn’t allow hooks. Also, the dw.ocapi.shop.customer.password.afterPUT_v2 extension point replaces the dw.ocapi.shop.customer.password.afterPUT extension point. If you have customizations for this resource, update your code accordingly.
• Configure How Long Einstein Waits Before Recommending Already Purchased Products
  Einstein Configurator now lets you define how many days a recommender waits before recommending previously purchased products. You can choose from 7, 30, 60, or 90 days. The default setting is 30 days. Previously, Einstein Configurator provided a static 30-day wait time before recommending previously purchased products. For some customers, this setting was either too short or too long.
• Assign Promotions to Campaigns with Enhanced OCAPI Data API Endpoint
  `/sites/{site_id}/campaigns/{campaign_id}/promotions/{promotion_id}` now allows the `PATCH` method and accepts a body for the `PUT` and `PATCH` methods. This body is identical to the response of the `/sites/{site_id}/promotion_campaign_assignment_search` API, but it now supports a new `required_qualifier` property. With this body, you can set qualifiers and other properties, such as rank, on a promotion assignment when you create it. You can also update these values.
• Assign Promotions to Campaigns with Enhanced Data OCAPI Endpoints
  `/sites/{site_id}/campaigns/{campaign_id}/promotions/{promotion_id}` now accepts a body for the `PUT` and `PATCH` methods. This body is identical to the response of the `/sites/{site_id}/promotion_campaign_assignment_search` API, but it now supports a new `required_qualifier` property. With this body, you can set qualifiers and other properties, such as rank, on a promotion assignment when you create it. You can also update these values.
• Embedded Objects Not Allowed in HTML Attributes
  For security reasons, only Business Manager users with strong authentication, such as through multi-factor authentication with Account Manager, can include objects embedded with iframe, object, applet, or embed tags in the HTML attributes of a database object. A Business Manager user with strong authentication can temporarily allow users without strong authentication to embed objects in HTML attributes.
• Organize Page Designer Pages in Folders
  You can assign Page Designer pages to Business Manager content library folders. Folders keep pages organized and easy to find. Developers can write custom code that implements page navigation based on folders. For example, custom code can add breadcrumbs to the tops of pages or accordian-style page navigation based on folders. Developers can also write custom code that specifies that when a shopper performs a search, the shopper sees results organized by folder.
• No Restrictions for CONTENT_SECURITY_POLICY
  Set the CONTENT_SECURITY_POLICY in B2C Script class dw.system.Response to any string value. Previously, the only directive allowed was frame-ancestors.
• Strong Authentication Required for Some Business Manager Modules
  For security reasons, to access certain Business Manager modules, you must now use strong authentication, such as multi-factor authentication (MFA) with Account Manager.