What's New

Update 24A

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.

Feature Summary

B2B Commerce

Platform

Direct Edit Cache Invalidation Debouncer

With this release, when the direct editing feature is enabled, you can configure the frequency of processing direct editing changes on Storefront. Configuring the frequency to a higher number would reduce the cache refreshes, thereby improving performance. This applies to the direct editing of catalog items and price items.

Merchants can now improve Storefront performance by changing the cache invalidation interval. The feature is designed to improve response times on Storefront when frequent changes are made on Admin within a short interval, for example, when bulk import is running.

Steps to Enable

Merchants can set the interval using the below payload.

URI: PUT /ccadmin/v1/merchant/cloudConfiguration

Payload:

{ 

"directEditEventProcessingIntervalSeconds": 10

}

Make sure you set the property to a reasonable value as it controls the delay with which changes appear on Storefront.

Note: directEditEventProcessingIntervalSeconds can take a value between 0 and 60. Property is set to 0 by default which means that this feature is disabled. Such a new property is only visible when at least one of the direct edit features is enabled.

Integrations

Native Integration with Oracle CPQ for Configuration

Experience seamless integration and optimal performance with the new native integration between Oracle Commerce and Oracle CPQ for complex product configuration.

Highlights :

• Native integration between Oracle Commerce and Oracle CPQ.
• Introduced new Commerce REST APIs for CPQ interactions.
• Takes advantage of the high availability and scale of Storefront servers.
• Streamlined experience that takes advantage of the latest version of APIs from Oracle CPQ.
• Integrates with the new “Get Configuration Layout Attribute Data” CPQ API  that provides metadata specific to the layout and it is more performant compared to the corresponding layout API in the SSE implementation.
• Leverages Coherence cache for caching layouts and also provides cache invalidation post layout changes on the Oracle CPQ ensuring optimal performance for configuration flows.
• Brand New User experience on OSF with redesigned navigation flows aligned with new reference store.
• With out-of-the-box UI and APIs implementation costs are reduced.
• Periodical updates to the integration to take advantage of new CPQ features.

Steps to Enable

1. Register Oracle Commerce as Client application on Oracle CPQ. Please invoke below API using basic authentication.

URI: POST <CPQ Host>/rest/v1/clients

Sample Payload:

{

"name": "OCCS Client Application",

"description": "OCCS Client Application",

"expires": 600,

"refreshExpires": 3600,

"clientKey": "occs_client_cred",

"grantType": "ClientCredentials"

}

2. Make a note of clientId and clientSecret from the response in Step 1 to complete the configuration in Oracle Commerce.

Steps to set-up Oracle Commerce

1. Login to the Administration Console.
2. Navigate to Settings -> Oracle Integrations.
3. Select CPQ Native Integration from the drop-down.
4. Select “Enable Integration”.
5. Enter values for CPQ Environment “Host URL”, “Client Id” and “Client Secret”.
6. Save the changes.
7. Publish the changes.

Tips And Considerations

1. Please refer 24A REST API documentation for detailed information on the new Oracle Commerce REST APIs.
2. Please refer to REST API documentation for Get Configuration Layout Attribute Data API for more information
3. This feature works for Anonymous shoppers also.
4. Customers using StoreFront Classic are required to build their own UI widgets.
5. Open Storefront Reference widgets will be made available in an upcoming release.

Improved Stability for Functional Webhooks

In this release, Functional Webhooks have been enhanced to optimize stability and resilience under high loads. One element of this enhancement is designed to limit further requests to downstream systems when a high number of pending requests is already active. In this way, the load on downstream systems is balanced and customers receive a more decisive experience.

To limit bottlenecks, third-party integrations of function webhooks should typically respond within ten (10) seconds of the request, and in no more than twenty (20) seconds of the request in extreme cases.

This enhancement is intended to provide a more performant end-customer experience and allow merchants to easily identify and mitigate bottlenecks in synchronous downstream integrations.

Steps to Enable

You don't need to do anything to enable this feature.

Open Storefront Framework

Product Configure Extension

Product Configure Extension implements Oracle CPQ Configuration functionality using Server Side Extensions on the Open Storefront Framework. This widget should be used in conjunction with 23.7.0 or a later version of cpq-configurator-app-store SSE. The following are some key highlights:

1.The new widget sends and receives only delta payload making interactions faster.

2.Added new UI elements to handle CPQ configuration elements.

3.Improved OSF widgets to be more generic to handle complex CPQ layout configurations.

4.Improved handling of auto update and ajax sensitive properties which eliminates explicit save operations from the shopper.

Product Configure Extension provides better performance and overcomes limitations of the existing Product Configure widget. The new widget sends and receives only delta payload making interactions faster.

Steps to Enable

1. Add the Product Configure Extension from the widget library to the Product layout.
2. Enable "Use the product-configure-extension widget" on the extended-cart-item-details widget.

Open Storefront Framework 5.3.0

This Commerce Open Storefront Framework (OSF) release includes new features, bug fixes and minor library updates. With this release, it is mandatory to upgrade your node version in your local development and CI/CD environments to 18LTS. Continuing to stay up to date with the latest OSF versions is important.

Capability highlights

• New reference widget for CPQ Configuration
• Bug fixes
• Library updates

Note: Please also make sure that your node modules are refreshed before deploying your application.

Continuing to stay up to date with the latest OSF versions is important to keep up with new functionality and important library updates.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Refer to the Oracle Commerce product documentation Developing Open Storefront Framework Applications for details on upgrading your version of OSF to a newer version.

Storefront

Enhanced Performance for Order APIs with externalData at Commerce Line items

With this feature, shoppers will experience enhanced performance for Order APIs when externalData is set for Commerce Line items.

Shoppers will experience enhanced performance for Order APIs when externalData is set for Commerce Line items.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

1. Before enabling "saveExternalDataToCLOB", Merchants must ensure that repositoryId for externalData is not used in any downstream processes after Order Placement in Oracle Commerce as repositoryId will no longer be available for externalData.
2. Default value for "saveExternalDataToCLOB" is false. Once set to true, it is not possible to set it back to false. So, please use it with caution.

Server-Side Extensions

Improvements to Extension server logging

With this release, the extension server logging is enhanced to provide additional context during request processing and error stack traces for the asynchronous promise rejections. Below are a couple of examples of additional context information:

1. {"clusterId":"Worker 1","endpoint":"/ccstorex/custom/v1/test","level":"debug","message":"Timetakentofindroute:0.9995","requestId":"pEDPhbGF7zODx/c4zmjGL+5jk4Y=","requestMethod":"GET","timestamp":"2024-01-03T20:32:46.300Z"}

2. {"clusterId":"Worker 1","endpoint":"/ccstorex/custom/v1/asyncPromiseError","level":"error","message":"Unhandled Promise rejection error","requestId":"pEDPhbGF7zODx/c4zmjGL+5jk4Y=","requestMethod":"GET","timestamp":"2024-01-03T20:32:46.301Z", "stack":"Error: This is an asynchronous exception\n at demo (/occsapp/custom-server/extensions/extracted/externalShippingCalculator/js/lib/calculate-shipping-demo.js:182:9)\n at”}

Extension developers benefit from this enhanced logging which provides the endpoint URL, request method, and error stack traces for asynchronous promise rejections. This feature helps to analyze, troubleshoot, and quickly fix the issues.

Steps to Enable

You don't need to do anything to enable this feature.