24.4 Release

Business Manager now supports configuring eCDN for staging environments. eCDN settings are specific to each instance (development, staging, and production), and you manage them individually. When you create a proxy zone in production, the zone doesn’t replicate a corresponding proxy zone in your development or staging instance. The new eCDN configuration feature simplifies onboarding new sites for staging instances, making it easier to mimic your production instance. Because the configuration uses the existing CDN-API, you can use either Business Manager or the API to manage your eCDN configurations.

The default setting for auto-correction for searchable attributes added after the B2C Commerce 24.4 release is now set to No. This change affects searchable attributes added through the Business Manager UI or via import. Existing configurations aren’t affected. Previously, when you added a searchable attribute, the default setting was Yes, which could cause issues in instances when search functions shouldn’t correct values, such as the product SKU, ID, or ISBN. Additionally, the auto-correction dictionary’s size can incrementally increase over time, leading to search noise.

How: To change the setting in Business Manager, select Merchant Tools | Search | Searchable Attributes.

See Also:

• Configure Searchable Attributes (The documentation at this link will be updated when the release notes are published)

The Page Designer image and media picker now supports up to 1,000 images per folder. Previously, only 200 images within a folder were accessible in the image picker, even if more existed. The increased image limit improves the user experience for merchandisers and content creators and avoids workarounds, such as creating subfolders for extra images.

See Also:

• Upload and Manage Files in the Content Library for Page Designer

To enhance security and align with the SLAS JWT session handling, we updated how the OCAPI JWT handles password changes. Now, if your customer changes their password, all previously issued active OCAPI JWTs are invalidated. The OCAPI client receives an HTTP 401 response, accompanied by a body message that indicates an invalid access token. Previously, the JWT remained valid until its normal timeout.

"fault": {
    "arguments": {
        "accessToken": "Customer credentials changed after token was issued. Please Login again."
    },
    "type": "InvalidAccessTokenException",
    "message": "The request is unauthorized, the access token is invalid."
}

Two new SCAPI response headers are available to check for custom requests and resulting hook execution errors.

1. fdc_customization - indicates whether customization has been applied during the request execution. Currently, the only possible value for the header is “HOOK”, which indicates that a hook execution was registered.
2. sfdc_customization_error - if the value is "1", an error occurred within a hook execution.

To protect customer instances and associated services from outages, B2C Commerce restricts rogue queries that produce 200 thousand results or more. To better protect Salesforce B2C Commerce, Salesforce plans to limit the allowed offset value from 200 thousand to 10 thousand.

When: The new limit will be implemented in the 24.5 Release in May 2024.

How: A generated rogue query returns an error message when using the APIs.

application failed to invoke [search_protocol.search()] on server, responding with
    fault. exception was [com.demandware.core.rpc.server.InvocationException: exception
    while invoking operation], cause [org.elasticsearch.ElasticsearchIllegalArgumentException:
    Search request offset  is greater than offset limit 200000 for tenant '_, type 'order']

To learn more, see Rogue Query Timeouts in the Commerce Cloud B2C Platform