This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 08 MAR 2023 | Created initial document. |
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.
Ability to list changes to Design Studio Assets
It is now possible to list the changes made within Design Studio using the Open Storefront (OSF) command line (CLI) tool.
The below command lists all changes made to assets by business users and also developers.
yarn list-changed-assets <app-name>.
This command can take the below arguments:
- --since <startTimestamp>, if not specified, uses time of last deployment
- --until <endTimestamp>, if not specified, uses current time
- --live, if not specified shows assets changed on previous, otherwise shows assets changed on production
startTimestamp and endTimestamp should be specified in following format ‘YYYY-MM-DDTHH:MM:SS’ and in UTC time.
e.g. yarn list-changed-assets core-commerce-reference-store --since 2023-1-20T12:50:00 –live
Open Storefront Framework Reference Implementation for SSO using SAML 2.0
Oracle Commerce enables you to integrate customer logins on your storefront using an external customer data store or identity management tool.
Open Storefront Framework now provides a reference implementation for Single Sign-On (SSO) using Security Assertion Markup Language (SAML) 2.0, which is an open-standard XML-based data-exchange format.
Reduction of OSF deployment time by optimizing Virus Scanning
With this release, the time needed to deploy an Open Storefront (OSF) application is reduced by optimizing the amount of virus scanning done as part of the deployment.
Prior to this feature, Virus scanning took place when the deployment zip file was uploaded and when creating Design Studio assets in the asset file system, such as locale-specific resource files. With this change, a second virus scan when the Design Studio assets are created is eliminated..
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 08 MAR 2023 | Created initial document. |
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.
Oracle Commerce allows merchants to export Orders in JSON format. Exported data includes Order properties like Order Id, Creation Date, State etc. along with sub entities like Shipping Groups, Commerce Items, Payment Groups etc.
Support for compressed interactions between Oracle Commerce and Oracle CPQ
The Oracle-provided Server-Side Extension (SSE) for CPQ now uses an updated version of the underlying Oracle CPQ API. The new Oracle CPQ API, in conjunction with the updated SSE code, provides for faster throughput of configurations and layouts by enabling compression of raw CPQ requests.
Date-based delta export from Product Catalog
It is now possible to export changed Catalogs, Collections and Product data from the core catalog based on the property lastModifiedDate.
Improved performance in Design Studio for Component and Widget Instances Listing
The following improvements have been made to Design Studio:
- Merchant Administrators using Design Studio will see improved performance when navigating through the Components tab. Performance of Widget Instances Listing on the Component details page has also been improved.
- Pagination and Search functionality has been added for Widget instances on the Widget Instances popup which is shown when adding a widget to a Layout.
- On the Component details page for Storefront Classic application widgets, Merchants can filter widget instances and extended Java scripts.
Improvements to Server Side Extension Server Restart Operation
Merchants can now track the progress of the Server Side Extension (SSE) server restart operation and can optionally choose not to restart SSE server when uploading or deletion extensions.
Preview for Server Side Extensions
Oracle Commerce now supports a preview environment and release process for Server Side Extensions (SSE).
Once enabled, SSE Upload and Delete operations can be performed only on the preview environment. The changes can then be promoted to live environment after completing the necessary validations.
Note that this feature is disabled by default.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 30 JAN 2023 | Created initial document. |
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.
OpenID Connect for authentication on Storefront applications
Oracle Commerce merchants can now configure OpenID Connect for authentication on Storefront applications. This feature works for both OSF and Storefront Classic applications.