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.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Open Storefront Framework Reference Implementation for SSO using SAML 2.0 |
||||||
Reduction of OSF deployment time by optimizing Virus Scanning |
||||||
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.
- A shopper can seamlessly transition between environments authenticated using the same SAML provider
- Reduce the time to implement SSO integration using SAML.
Steps to Enable
- In OSF, the “SSOLogin” component needs to be added to the "login-responsive" container on Log in – Default page layout
- Refer to the Oracle Commerce product documentation ‘Implement Storefront Single Sign-On’ in ‘Extending Oracle Commerce’ section for details on steps to setup the feature.
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
- Developers can now keep track of the changes made by business users in Design Studio.
- Determine which assets require translation processing following asset changes made by business users in Design Studio within a given date range on preview or live.
Steps to Enable
You don't need to do anything to enable this feature.
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 feature will reduce the time taken for an OSF deployment (yarn deploy command) to complete.
Steps to Enable
You don't need to do anything to enable this feature.
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 |
|---|---|---|---|
| 05 APR 2023 | Server-Side Extensions | Improved performance in Design Studio for Component and Widget Instances Listing | Updated document. Revised feature information. |
| 05 APR 2023 | Server-Side Extensions |
Preview for Server Side Extensions | Updated document. Revised feature information. |
| 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.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Support for compressed interactions between Oracle Commerce and Oracle CPQ |
||||||
Improved performance in Design Studio for Component and Widget Instances Listing |
||||||
Improvements to Server Side Extension Server Restart Operation |
||||||
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.
It is not currently possible to import orders using this approach.
This feature allows merchants to easily export large volumes of orders for offline processing, and reporting.
Steps to Enable
Use the Export plugin with "id" in the request payload set as “Orders”.
Tips And Considerations
Similar to other bulk export plugins, Order export supports 'q' parameter to filter records from the total record set. URI and Sample request payload can be found below.
URI: GET /ccadmin/v1/exportProcess
Payload:
{
"id": "Orders",
"fileName": "Orders.json",
"format": "json",
"mode": "standalone",
"params": {
"q": "state eq \"SUBMITTED\""
}
}
Refer to the Oracle Commerce product documentation Perform Bulk Export and Import section for details more information.
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.
Oracle CPQ experiences delivered from Oracle Commerce are now more performant, and capable of supporting much larger configuration models.
Steps to Enable
Use 23.1.2 version of cpq-configurator-app-store.zip.
Tips And Considerations
Customers should uptake the version and gzip changes in their Custom SSE Implementations.
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.
Use the new lastModifiedDate property in the SCIM query to export changes on or after the specified time.
E.g., To export products created/modified after 1.55 PM Dec 12th 2022 using the below URI and payload.
URI: GET /ccadmin/v1/exportProcess
Payload:
{
"id": "ProductsV2",
"fileName": "products.json",
"format": "json",
"mode": "standalone",
"params": {
"q": "lastModifiedDate ge \"2022-12-12T13:55:00.000Z\""
}
}
Large catalogs can be more easily managed, and changes used for downstream integration and reporting are more readily accessible.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Merchants can also filter entities based on combination of properties that can be queried, e.g., List of Products based on child SKU last modified date that are discountable.
URI: GET /ccadmin/v1/exportProcess
{
"id": "ProductsV2",
"fileName": "products.json",
"format": "json",
"mode": "standalone",
"params": {
"q": "childSKUs.lastModifiedDate gt \"2022-12-12T13:55:03.000Z\" and discountable eq true"
}
}
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.
Merchants will experience faster page loads for Component and Widget Instance Listings in Design Studio.
Steps to Enable
You don't need to do anything to enable this feature.
Improvements to Server Side Extension Server Restart Operation
Merchants can now optionally choose not to restart SSE server when uploading or deletion extensions.
- When uploading/deleting extensions, merchants can avoid the restart of the SSE server until all changes are made.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- When an SSE is uploaded or deleted, Merchants can choose to avoid restart of the SSE server by passing a query parameter restartExtensionServer. If not set or set as true, SSE server is restarted.
- To manually restart the server, use the /ccadminx/custom/v1/servers/restart endpoint.
Please refer REST API documentation for more information on above endpoints.
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.
- Merchants can test an extension in preview before promoting it to live environment.
- Merchants can prevent accidental actions (like delete) on live environment.
Steps to Enable
- Preview feature can be enabled using endpoint API – POST: /ccadmin/v1/serverExtensions/preview.
- Preview environment can be enabled using endpoint API – POST: /ccadmin/v1/serverExtensions/preview/enable.
- Promote feature can be used to promote changes to the live using API – POST: /ccadmin/v1/serverExtensions/promoteFiles.
- Status of last promote operation can be viewed using API – GET: /ccadmin/v1/serverExtensions/promoteStatus.
- Merchants can disable the preview feature by contacting Oracle Support.
Please refer REST API documentation for more information on above endpoints.
Tips And Considerations
- If the preview feature is disabled, then there will no impact or changes to the server side extension (SSE) related traffic and they will be served by live server side extension server as usual.
- If the preview feature is enabled, then server side extension (SSE) related traffic will be routed to either preview or live server side extension server based on the query param ‘environmentType’. Possible combinations are listed in the table below.
| Base URL |
Environment Type (query param) |
SSE Server (which serves request) |
|---|---|---|
| <admin_host>/ccstorex/custom/<SSE PATH> |
N/A |
Preview SSE Server |
| <store_host>/ccstorex/custom/<SSE PATH> |
N/A | Live SSE Server |
| <admin_host>/ccadminx/custom/<SSE PATH> |
preview |
Preview SSE Server |
| <admin_host>/ccadminx/custom/<SSE PATH> |
live |
Live SSE Server |
| <admin_host>/ccadminx/custom/<SSE PATH> |
No param (default) |
Live SSE Server |
| <admin_host>/ccagentx/custom/<SSE PATH> |
preview |
Preview SSE Server |
| <admin_host>/ccagentx/custom/<SSE PATH> |
live |
Live SSE Server |
| <admin_host>/ccagentx/custom/<SSE PATH> |
No param (default) |
Live SSE Server |
- All the existing OOTB Admin SSE endpoints support “environmentType” param to perform operations on the preview SSE environment. Please refer to the REST API doc for more details.
-
When an extension (e.g., dummy.zip) is deleted in the preview environment, its name is suffixed with the _deleted keyword (e.g.dummy_deleted.zip). The _deleted keyword specifies that the extension has been deleted from the preview environment. One cannot access the APIs provided by the deleted SSE’s however it’s renamed copy (e.g dummy_deleted.zip) is present in the preview environment till the point it is successfully promoted to live environment. Once the deleted copy (e.g. dummy_deleted.zip) is promoted to the live environment, both deleted copy (dummy_deleted.zip) on the preview environment and the original extension (dummy.zip, if present) on the live environment are removed.
-
Merchant cannot upload extensions whose name is suffixed with _deleted keyword (e.g. dummy_deleted.zip) as it signifies a deleted copy of the extension.
-
SSE specific environment variables have two values – "value" and "previewValue". "value" is used on the live SSE environment and the "previewValue" is used on the preview SSE environment. On Upgrade, all the existing SSE environment variables will be updated to have the "previewValue" same as the "value". Later on, the "previewValue" can be updated to have a different value.
-
While creating an SSE environment variable, if "previewValue" property is not specified in the payload, then the "value" property is used to populate the "previewValue" property.
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.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
OpenID Connect for authentication on Storefront applications |
||||||
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.
Capability Highlights
- Any OpenID compliant identity provider can be used
- Fully supported in preview mode(except IDCS).
- Configurable for B2B
- Scopes can be configured separately
- Redirects the user back to the page where Login was initiated
Steps to Enable
- The following endpoints are used to set OpenID configuration and scopes:
- /ccadmin/v1/merchant/openidSettings
- /ccadmin/v1/merchant/openidScopes
- In OSF, the “OpenIDLogin” widget needs to be added to the "login-responsive" page layout.
- In Storefront Classic, the “OpenID Connect Login/Registration” element with-in the Header widget needs to be added to the Header widget layout.
Tips And Considerations
- Configuration is not site specific.
- An OpenID Provider account must be created prior to configuring the feature. Refer to the OpenID Provider documentation for configuration details.
- CORS configuration needs to be updated to allow redirects to Storefront from the OpenID Provider URLs.
- Users are redirected back to the home page if they initiated logout on a profile specific page like Account or Order Details.