Update 23C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

B2B Commerce

Admin

Site Preview as B2B Account User

Preview By Account is an enhancement to the Commerce Cloud service that allows a page developer to preview how their site’s pages will appear to a user from a certain account with a selected set of roles. Prior to the introduction of this feature, the page designer would have no way to preview how changes would appear to a customer of a given account and roles before the pages were published to production. Preview by Account is available for both Storefront Classic and Open Storefront Framework sites.

Catalog and Promotions

Limit the Child Array Properties of Certain Catalog Endpoints to Reduce Response Payloads

Oracle Commerce now supports limiting the number of elements of array properties of certain catalog endpoints to improve the response time and payload size of these endpoints.

Capability Highlights

• Set a maximum count value to limit the number of elements of array properties of certain catalog endpoints.
• Endpoints: getProduct, listProducts, getCollection, and listCollections in Admin, Agent, and Storefront.
• The limited properties are childProducts, childSKUs, and filteredSKUs.

• Reduces the response time of these endpoints.

• Reduces the payload size of these endpoints.

Server-Side Extensions

Support for OAuth Authentication in SSE and CPQ interactions

SSE apps cpq-configurator-app-store and cpq-configurator-app-agent now support OAuth based authentication for CPQ interactions. Merchants can choose to use either OAuth or Basic Auth authentication in these apps. To take advantage of this feature, the merchant must use 23.7.0 version of cpq-configurator-app-store.zip and cpq-configurator-app-agent.zip. OSF uses cpq-configurator-app-store for the OOTB OSF-CPQ SSE based integration.

Node 18 Upgrade for Server-Side Extensions

With this release, the version of Node.js used by server-side extensions (SSEs) is being upgraded to the latest long-term support version of Node.js 18LTS. In our testing, we have not found any incompatibilities. But, there are steps you should take to prepare ahead of time. The main risk for incompatibility is outdated npm libraries that may be used by your SSEs. Before your sites are upgraded to 23C(or beyond), you will need to verify that you’re using the latest version of each npm library and identify any changes that need to be made to your SSEs. If you have determined any issues with your SSEs as a result of the update to Node.js 18LTS, you should address them before the update. It is your responsibility to test your updated SSEs locally before your non-production update and push the updated code to non-production and production as part of the update process.

Open Storefront Framework

Node 18 Upgrade for Open Storefront Framework

With commerce 23.08 version upgrade, there is an upgrade of Node version to 18LTS. Open Storefront Framework is also being upgraded to the latest long-term support version of Node.js 18LTS. With this version of Node.js we did not find any incompatibilities in OOTB features.

React 18 Upgrade for Open Storefront Framework

With OSF 5.0.0, the version of React used by Open Storefront Framework is being upgraded to the latest long-term support version of React 18. React 18 includes major out-of-the-box improvements like automatic batching, new APIs like startTransition, and streaming server-side rendering. With this React update, there are a few backwards incompatible changes made in Server side rendering, Client side rendering and hydration functionality.

Enhanced CSS Loading Techniques for OSF

With this feature, merchants can define CSS at page and widget level in addition to making them site-specific. This is enhancement to existing site-specific CSS feature.

Support for Uploading Selected Assets in An OSF Application Deployment

Previously when an OSF developer updated assets or added new assets, they had to upload and deploy  the complete application. With this feature, developers can update existing assets or upload new assets by uploading only the selected assets instead of the whole application. A new CLI command and a REST API was introduced for this feature.

Support For Updating Existing OSF Assets in OSF Application Deployment

Previously when an OSF application was deployed without the reset option, only new assets would be created and existing assets would be left untouched. This meant that in order to promote updates to existing assets, every deployment needed the reset option to remove the existing application and its assets first.

With this feature there are the following two new options supported by the OSF deploy command and uploadApplication endpoint that the deploy command uses:

• updateExistingAssets – The ability to update existing assets. Its set to false by default for backwards compatibility purpose.
• keepUnpublishedChanges - The ability to skip updates to an existing asset if it has unpublished changes. Its set to false by default for backwards compatibility purpose.