Cloud Readiness / Oracle CX Commerce
What's New
Expand All


  1. UPDATE 19D WEEK 10
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Storefront
        1. Shopper Profile Registration Completion with Secure Email Link
    2. Integrations
        1. Telco/Services: Direct Configuration (Bypass iFrame) Asset Operations (API Only)
  1. UPDATE 19D WEEK 9
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Catalog
        1. Dynamic Properties on Collections (API Only)
  1. UPDATE 19D WEEK 7
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Catalog
        1. Catalog Export – Improved Filtering
    2. Inventory
        1. Search for a SKU Within Inventory
  1. UPDATE 19D WEEK 3
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Reporting
        1. Near Real-Time Dashboard
    2. Integrations
        1. Telco/Services: Upgrade Assets
        2. Telco/Services: Direct Configuration (Bypass Iframe) API Only
  1. UPDATE 19D WEEK 1
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Payments
        1. Additional Properties for Payment Webhook Requests
  1. Update 19D
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Search Admin
        1. Site-Specific Keywords
    2. Experience and Design
        1. 301 Redirect API
    3. Storefront
        1. API Improvement for Large Number of Product Types with Variants
        2. Related Products API Improvement
    4. Guided Search
        1. Enhanced Search Response
    5. Experiments
        1. Export of Experiments Results and Improved Navigation
    6. Catalog
        1. Enhanced Product Search for Merchandisers
    7. Integrations
        1. Improved Bulk Import

Update 19D Week 10

Revision History

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

Date Feature Notes
30 JAN 2020 Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Commerce Cloud and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

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. Please indicate you are inquiring or providing feedback regarding the Oracle Commerce Cloud What’s New for 19D Week 10 (19.5.10) in the body or title of the email.

Feature Summary

Column Definitions:

Features Delivered Enabled

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
(Features Delivered Enabled)

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.

Action is Needed BEFORE Use by End Users
(Features Delivered Disabled)

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
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Storefront

Shopper Profile Registration Completion with Secure Email Link

Integrations

Telco/Services: Direct Configuration (Bypass iFrame) Asset Operations (API Only)

Storefront

Shopper Profile Registration Completion with Secure Email Link

We’re now including an optional new shopper registration flow that makes the account registration process even more secure and helps avoid malicious profile registrations. It applies to both individual Storefront shopper profile registrations and creation of new B2B users and organizations as well. In this new flow:

  • The shopper enters Name and Email Address and submits registration request.
  • Our system creates shopper profile with an auto-generated password.
  • Our system sends the shopper a New Account email that includes a secure tokenized reset password link.
  • The shopper selects link and enters new password details to complete registration.

If the email address entered is already in use, the shopper will receive a New Account email advising the shopper that there was an attempt to register with the email address entered on the site and if s/he has forgotten the password, it needs to be reset. The email will include the forgotten password link, so the shopper can reset the password.

If shopper selects to create an account at Checkout:

  • The shopper will enter registration details (Name and Email Address) and submit registration request.
  • Our system will display a message informing shopper that s/he will receive account activation details via email.
  • Our system will display a login form with pre-populated email address and message advising shopper to check his or her email to complete registration and enter login details.
  • The shopper can either complete registration using the email link and login or select to continue checking out as a Guest.

When this flow is enabled, shoppers will no longer automatically be logged in after registration, as the shopper must complete the registration via email and then actively log in.

Steps to Enable

To implement this feature, we’ve added a new site level shopper setting called EnableProfileRegistrationEmailCheck on the merchant/profilePolicies API to enable/disable this new secure shopper profile registration process, as well as a New Account email in Admin settings and updated header and login-checkout widgets.

Tips And Considerations

NOTE: To comply with security requirements, this feature is enabled by default for new customers. To ensure backwards compatibility, feature is *not* enabled for existing customers. Merchants have the option to enable/disable as desired.

Integrations

Telco/Services: Direct Configuration (Bypass iFrame) Asset Operations (API Only)

For Oracle CX Commerce customers using Oracle CPQ and selling configurable products, we’ve made available new Storefront and Agent endpoints that enable asset modifications and upgrades — modification or upgrades to a shopper’s current service — via direct calls to Oracle CPQ, removing the need to include an iFrame in the shopper experience. This feature is limited to API support and customers need to build their own UI elements to invoke the new endpoints.

We previously released the ability to create ‘Configure’ and ‘Reconfigure’ UI elements and bypass using iFrame. This feature takes the next step by allowing the ability to create ‘Modify’ and ‘Upgrade’ UI elements as well, so merchants can deliver seamless and consistent user experience even when allowing shoppers to modify or upgrade complex products or services. The Configuration UI experience is derived from existing themes and styles. And merchants can customize the UI experience by adding their own UI controls.

This feature allows merchants to choose to move away from the iframe UI experience and instead implement direct API which enables shoppers to execute configuration of complex customizable services seamlessly in CX Commerce without being redirected to an Oracle CPQ hosted iFrame which may have a separate and distinct look and feel, and potentially present a disjointed user experience. The UI experience owned by CX Commerce can now be customized both at the global level (e.g. brand-specific configuration UIs and controls) and at the product level (e.g. a specific UI experience for individual customizable products).

Steps to Enable

1. Download and install Server-Side Extensions:

  • New - CpqConfiguratorStoreApp
  • New - CpqConfiguratorAgentApp

2. Create any necessary UI elements:

  • Create UI ‘Modify’ element which can be be coded into the asset details widget, which is not elementized. 
  • Create UI ‘Upgrade’ element which can be be coded into the asset details widget. 

Full guidance on implementing the Direct API Configuration feature will be included as part of the 20A Help docs and an updated version of the integratingOracleCommerceCloudandOracleCPQCloud.pdf  in the Oracle Support Document 2214316.1 (Integrating Oracle Commerce Cloud Service and CPQ Cloud Service) MOS article will also be published.

Tips And Considerations

NOTE: Current feature is API only and requires the merchant to build their own UI elements to invoke the new endpoints.

Update 19D Week 9

Revision History

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

Date Feature Notes
23 JAN 2020 Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Commerce Cloud and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

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. Please indicate you are inquiring or providing feedback regarding the Oracle Commerce Cloud What’s New for 19D Week 9 (19.5.9) in the body or title of the email.

Feature Summary

Column Definitions:

Features Delivered Enabled

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
(Features Delivered Enabled)

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.

Action is Needed BEFORE Use by End Users
(Features Delivered Disabled)

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
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Catalog

Dynamic Properties on Collections (API Only)

Catalog

Dynamic Properties on Collections (API Only)

Merchants can now define collection-specific data by extending collection attributes to include dynamic properties. They can create the following dynamic property types via API:

  • Checkbox (boolean)
  • Date
  • Number
  • Rich Text
  • Short Text
  • Long Text

Merchants can view and update these dynamic property values in the collection editor in the Catalog section of the Admin UI once they have been populated via API. API supports ability to create and update dynamic properties on collections.

Dynamic properties can be used individually or in combination. Using dynamic properties on collections provides flexibility and enables the ability to drive a number of merchandising enhancements, including property-based messaging and promotional content on collection landing pages, inclusion of media from a third party data asset manager, ability to display selected SKUs on selected collections (e.g. display only online-only colors of a product), excluding certain collections from typeahead search, and Shop the Look.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

NOTE: This is an API only feature in that the values must be populated via API first before being able to view or update them via the UI. There is currently no UI support for creating or deleting dynamic properties on a collection.

Update 19D Week 7

Revision History

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

Date Feature Notes
20 DEC 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Commerce Cloud and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

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. Please indicate you are inquiring or providing feedback regarding the Oracle Commerce Cloud What’s New for 19D Week 7 (19.5.7) in the body or title of the email.

Feature Summary

Column Definitions:

Features Delivered Enabled

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
(Features Delivered Enabled)

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.

Action is Needed BEFORE Use by End Users
(Features Delivered Disabled)

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
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Catalog

Catalog Export – Improved Filtering

Inventory

Search for a SKU Within Inventory

Catalog

Catalog Export – Improved Filtering

The filter on the catalog export dialog has been replaced with a new and improved rule builder enabling users to export a specific set of products quickly using custom rules. This allows merchants to work on a more targeted set of catalog items in export. It provides a number of new capabilities, including:

  • Ability to filter products and SKUs being exported by all base properties, including any dynamic properties of the base type
  • Ability to create single/multiple rules which are grouped together with ("AND"/ "OR" ) also known as ("ALL"/ "ANY")
  • Ability to find and return products based on the following additional properties:
    • Parent collections (parentCategories)
    • Ancestor collections (ancestorCategories): For example, filtering by "Ancestor collections contains women" brings back everything in the collections under the women's collection.
    • Creation date (creationDate): Creation date > 24th Oct
  • Ability to find and export recently added items, as well as export based on specific or missing values, such as the following examples:
    • Return products with no product images across all catalogs --> Filter by: Product Images does not exist
    • Return products with certain brand names across all catalogs: --> Filter by: Brand is one of [brand name X], [brand name Y]
    • Return all inactive products across all catalogs --> Filter by: Active = False
    • Return all products that don’t have a brand name --> Filter by: Brand does not exist

Steps to Enable

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

Tips And Considerations

NOTE: We currently do not support the ability to filter by a specific catalog, search on dynamic properties of a collection, search across subtypes (e.g. product type = tables), or create nested rules.

Inventory

Search for a SKU Within Inventory

Merchants can now search for SKUs within catalog Inventory based on product name and/or SKU ID. Searching enables merchandisers to find a specific SKU quickly, so that they can view the current state of a SKU and check its accuracy, as well as modify the inventory level if necessary. (Just double-click on the inventory count or stock threshold fields to update inventory values.)

The search box supports the following:

  • Ability to search for a specific SKU ID or a list of SKU IDs (comma separated)
  • Ability to search by product name or a list of product names (comma separated) 
  • Ability to search using a mixed list of product names and SKU IDs (comma separated)

Steps to Enable

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

Tips And Considerations

NOTE: Pagination is no longer supported. Merchants can further refine results by typing into the search box.

Update 19D Week 3

Revision History

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

Date Feature Notes
26 NOV 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Commerce Cloud and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

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. Please indicate you are inquiring or providing feedback regarding the Oracle Commerce Cloud What’s New for 19D Week 3 (19.5.3) in the body or title of the email.

Feature Summary

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
(Feature Delivered Enabled)

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
(Feature Delivered Disabled)

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
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Reporting

Near Real-Time Dashboard

Integrations

Telco/Services: Upgrade Assets

Telco/Services: Direct Configuration (Bypass Iframe) API Only

Reporting

Near Real-Time Dashboard

The reporting homepage is now based upon data updated in near real time, enabling merchants to:

  • Review key sales and traffic figures from the last twenty four hours, broken down by hour
  • Review product and promotion sales performance from the last twenty four hours
  • Refresh the data for the homepage report from a settings menu option

This feature is especially useful for reviewing performance of a promotion or sales and orders in conjunction with other marketing and merchandising events that require more-real-time analysis, and quick response adjustments and optimizations to a campaign.

Reporting Dashboard

Steps to Enable

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

Tips And Considerations

NOTE: Only the homepage of reporting is based on real-time data.  All other sections of reporting continue to be based on data that is updated daily.

Integrations

Telco/Services: Upgrade Assets

For Oracle CX Commerce customers using Oracle CPQ (or another asset master system), merchants can now define and display all of the available upgrade options for any existing service.

Shoppers can take advantage of the upgrade and check out, as well as be alerted to and prompted about upgrades as soon as they are available. Upgrades can be pushed out to customers right away and the upgraded asset is ready to be added to the cart with a single click.

This feature is especially useful in presenting better upgrade options for customers and getting those in front of them in the shopper experience in a more effective way. And it makes it easier for shoppers to take advantage of those upgrades as well.

Steps to Enable

  1. Create the upgrade table in CPQ.
  2. Update Layouts
  • Assets Layout - Upgrade
  • Asset Details Layout - Upgrade
  1. Update Widgets
  • Update - Asset List
  • Update - Asset Details
  1. Download and install Server-Side Extensions
  • Updated version of - Services-store
  • Updated version of - Services-agent
  • New - Services-products-lib
  • New - Services-actions-access-checker
  • New - cpq-assets-punchin-url-lib
  1. Implement OIC Flows
  • New- OCC_CPQ_Get_Asset_Upgrade_Options

Key Resources

Full guidance on implementing the upgrade feature will be included as part of the 20A Help docs and an updated version of the integratingOracleCommerceCloudandOracleCPQCloud.pdf in the Oracle Support Document 2214316.1 (Integrating Oracle Commerce Cloud Service and CPQ Cloud Service). MOS article will also be published.

Telco/Services: Direct Configuration (Bypass Iframe) API Only

Shoppers can now configure complex customizable products seamlessly in Oracle CX Commerce without being redirected to an Oracle CPQ hosted iframe.

For Oracle CX Commerce customers using Oracle CPQ and selling configurable products, this new feature allows merchants to implement a direct API configuration using new Storefront and Agent endpoints and removes the need to include an iframe in the shopper flow, thereby improving the overall user experience.

By creating ‘Configure’ and ‘Reconfigure’ UI elements, merchants can deliver a seamless, consistent user experience even when customizing complex products or services. The Configuration UI experience is derived from existing themes and styles. And merchants can customize the UI experience by adding their own UI controls.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

  1. Download and install Server-Side Extensions
  • New - CpqConfiguratorStoreApp
  • New - CpqConfiguratorAgentApp
  1. Create any necessary UI elements
  • Create UI ‘Configure’ element which can be dropped on to the PDP widget, which is elementized.
  • Create UI ‘Reconfigure’ element which can be coded into the cart widget, which is not elementized.

Full guidance on implementing the Direct API Configuration feature will be included as part of the 20A Help docs and an updated version of the integratingOracleCommerceCloudandOracleCPQCloud.pdf  in the Oracle Support Document 2214316.1 (Integrating Oracle Commerce Cloud Service and CPQ Cloud Service) MOS article will also be published.

Tips And Considerations

NOTE: Current feature is API only and requires the merchant to build their own UI elements to invoke the new endpoints.

Update 19D Week 1

Revision History

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

Date Feature Notes
12 NOV 2019 Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Commerce Cloud and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

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. Please indicate you are inquiring or providing feedback regarding the Oracle Commerce Cloud What’s New for 19D Week 1 (19.5.1) in the body or title of the email.

Feature Summary

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
(Feature Delivered Enabled)

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
(Feature Delivered Disabled)

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
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Payments

Additional Properties for Payment Webhook Requests

Payments

Additional Properties for Payment Webhook Requests

Additional properties are now included in payment webhook requests. This helps with improved robustness of integrated payment fraud solutions and enhanced capability in support of the Payment Service Directive 2 (PSD 2).

The Credit Card Payment and Generic Payment webhook requests have been extended to include:

  • The full order, including item numbers, item descriptions, quantities, prices, currency, custom properties 
  • Shopper information, including shopper profile properties, such as custom profile properties, shopper authentication method, registration date, modification date, password change date

The added information is commonly used to perform risk assessment. The service that receives the webhook request can use this information or pass it to external services. For example, it is common to integrate payment fraud detection services into the payment authorization flow. When the webhook service receives the payment authorization request, it can forward this request to a payment fraud detection service prior to requesting authorization. The additional data can now be used by the fraud detection service to assess risk.

Similarly, the information can be used to enhance PSD 2 user experience. The PSD 2 standard – in effect in Europe and other places around the world, requires strong customer authentication which is achieved using 3DS authentication. PSD 2 attempts to improve user experience by identifying low risk orders and allowing the shopper to complete the order without additional authentication. Many payment providers recommend sending extended data about the order, such as the contents of the order and shopper information. Payment Providers use this information to assess risk and determine whether to prompt the shopper for additional authentication. The additional information improves the robustness of this risk assessment and improves the likelihood of “frictionless flow.”

Steps to Enable

This feature is enabled using a new payment gateway extension property. The ability to include the full order is enabled by setting the flag on the payment extension. Upload the modified payment extension for the change to take effect.

Tips And Considerations

NOTE: Enable this option only if you need the additional information, as it increases the size of the payload and could affect performance.

Update 19D

Revision History

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

Date Feature Notes
12 NOV 2019

Support Transient Cart Mode for Logged-In Shoppers

Updated document. Removed feature from update 19D.
05 NOV 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Commerce Cloud 19D Update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

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. Please indicate you are inquiring or providing feedback regarding the Oracle Commerce Cloud What’s New for 19D Update in the body or title of the email.

Feature Summary

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
(Feature Delivered Enabled)

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
(Feature Delivered Disabled)

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
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Search Admin

Site-Specific Keywords

Experience and Design

301 Redirect API

Storefront

API Improvement for Large Number of Product Types with Variants

Related Products API Improvement

Guided Search

Enhanced Search Response

Experiments

Export of Experiments Results and Improved Navigation

Catalog

Enhanced Product Search for Merchandisers

Integrations

Improved Bulk Import

Search Admin

Site-Specific Keywords

A keyword redirect allows merchants to send shoppers to a location on their site or another site when they enter a specific search term. For example, a relevant promotional page or product category page can be displayed instead of a typical list of search results. Or a search for “delivery” can redirect shoppers to a page with shipping information.

With this latest release, merchants can now apply keyword redirects to one or more specific sites (before this, keyword redirects were not site-specific and always redirected shoppers to the same page, regardless of the site they were on). So for example, the same search term, entered on different sites, can redirect shoppers to different pages. For example, the search term “returns” can be set up to redirect as follows:

  • /siteAreturns, when entered on Site A
  • /siteBreturns, when entered on Site B

Merchants can also filter the list of keyword redirects by site in the Admin UI.

Steps to Enable

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

Tips And Considerations

NOTE: The default setting is a “global” keyword redirect which will apply a keyword redirect to all sites. When updated to the release containing this feature, all existing existing keyword redirects will continue to be global, unless they are manually changed.

Experience and Design

301 Redirect API

This new SEO feature allows a merchant to create 1:1 redirects via API without the need for a service request (after the initial site migration). These can be created on a per site basis or as a global redirect for all sites. Supports relative 301/302 redirects.

301 redirects indicate to search engines that a URL was permanently moved to a new target location (e.g. during a site migration, permanently moving or deprecating a particular page). This type of redirection helps move SEO authority from the old URL to the new equivalent. 302 redirects should only used to temporarily redirect a page for a limited period of time.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Storefront

API Improvement for Large Number of Product Types with Variants

We’ve also added a new optional global setting that allows merchants to skip loading and using variant information and SKU properties from the product type data on the page call (Variant information and SKU Properties are still available for the product itself). Accordingly, we’ve included new versions of the Product Details and Product Listing widgets that use variant information and SKU properties from the product, instead of page information.

Using this new feature is particularly useful for merchants that have a large number of product types with many variants. It helps avoid loading duplicate data which significantly reduces the amount of data returned and speeds up response on the Product Listing and Product Details pages.

Steps to Enable

To leverage this new setting:

  • A new "skipLoadingProductTypes“ flag has been added as a global client-configuration endpoint setting.

Note that the flag has been set to ‘true’ for new customers, but ‘false’ for existing, so existing customers must manually enable this new feature in order to take advantage of it.

  • To enable "skipLoadingProductTypes“ flag :

Invoke Admin endpoint PUT  /ccadminui/v1/merchant/clientConfiguration with

{

" skipLoadingProductTypes ": true

}

  • If set to ‘true’, system will skip loading all the productTypes on page endpoint response. (If " skipLoadingProductTypes ": true, "productTypesRequired" query parameter will be set to ‘false’ in page calls.)

Tips And Considerations

Using this new feature is not recommended for merchants that have custom product listing or product details widgets that use product type data, as those custom widgets may require product type information that has been stripped from the page calls.

Related Products API Improvement

We’ve provided a new optional global setting to skip retrieving parent category details from related products if they are not needed, on product listing and product detail pages when related products are present. If used, the parent category details will be retrieved only once a shopper selects an individual product to view.

This helps avoid loading any unnecessary parent categories and reduces the amount of data returned, speeding up response on pages that display related products.

Steps to Enable

To leverage this new setting, note the following:

  • Two new flags have been added in Admin cloudConfiguration:-
  1. optimizeRelatedProductsForPageEndpoint - removes parentCategories, parentCategory, parentCategoryIdPath from Product Details page endpoint.
  2. optimizeRelatedProductsForListProductsEndpoint - removes parentCategories, parentCategory, parentCategoryIdPath from Product Listing page endpoints (i.e. listProducts, listProductsForLargeCart endpoints).
  • Both new and existing customers will need to enable the flags for the endpoints in Cloud Configuration Admin Endpoint by following the steps below:
  • To enable for Product pageEndpoint:

Invoke Admin endpoint /ccadminui/v1/merchant/cloudConfiguration with

{

"optimizeRelatedProductsForPageEndpoint": true

}

  • To enable for listProducts/listProductsForLargeCart endpoints:

Invoke Admin endpoint /ccadminui/v1/merchant/cloudConfiguration with

{

"optimizeRelatedProductsForListProductsEndpoint": true

}

  • Clear JSONStoreCache to reflect it in the Storefront.
  • Flush the JSONStoreCache via dyn admin - Go to store /dyn/admin/nucleus//atg/cloud/rest/JSONStoreCache/ and click on method named "flush."

Tips And Considerations

Merchants can customize further by stripping out dynamic properties and other data.

Guided Search

Enhanced Search Response

OCC search response is optimized for performance, returning only the most relevant SKU in the response. We have improved this further by adding configuration options that allow a developer to specify:

  • whether all SKUs should be returned: "maxChildRecords": -1
  • which product-level attributes should be returned: “attributes”
  • which SKU-level attributes should be returned: “childRecordAttributes”

These additional options are useful for returning all SKUs for each product and retrieving the color from each SKU to populate a product swatch, for example.

Also provides the ability to return all price properties for each SKU, and display more complex price information, so that merchants can display “from” and “to” prices for SKUs that are in stock, for example, and to be able to list all in-stock sizes beneath each product in the search results.

This feature is automatically available to use. To leverage it:

  1. Download the search service using:

GET /gsadmin/v1/cloud/pages/Default/services/guidedsearch

  1. Add the relevant properties:
  • "attributes": ["product.repositoryId", “product.displayName"]
  • "childRecordAttributes": ["sku.repositoryId", "sku.listPrice", "sku.activePrice"]
  • "maxChildRecords": -1
  1. Upload the updated search service.

Steps to Enable

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

Tips And Considerations

Returning additional data will have a performance overhead, so if this is used, ensure that only attributes that are absolutely necessary are included in the response. Use the “attributes” and “childRecordAttributes” with “maxChildRecords” to return only the properties you need to display the results and limit response size.

Example Search Response

Experiments

Export of Experiments Results and Improved Navigation

Two new features have been added to the OCC A/B testing tool, Experiments:

  • Ability to export Experiments results in .csv format, allowing merchants to download results of A/B tests and analyze the data more easily in an external tool of the merchant’s choice.
  • Direct navigation from Experiments modal to the main application for A/B tests of all states (not just In Progress and Complete).

.csv Format Example

Updated Navigation

Steps to Enable

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

Catalog

Enhanced Product Search for Merchandisers

The “All Products” view has been replaced with “Product Search.” This allows for rule-based search by using the icon next to the search box. It provides:

  • Ability to initiate a custom search within any collection, including unassigned products and unassigned collections.
  • Ability to filter the search results by all catalogs or a single catalog.
  • Ability to search across all properties on the General and Product Type tabs of the product editor, including any dynamic properties added by a customer.

This enhanced product search capability enables merchandisers to find products quickly using custom rules and reduces the need to page through thousands of products. Merchandisers can now search for missing values and recently added items, for example. Additional examples include:

  • Finding products with no product images within the current catalog or across all catalogs:
    • Use query: Product Images does not exist
  • Finding products with certain brand names within the current catalog OR across all catalogs:
    • Use query: Brand is one of X
  • Finding all products that belong to the “Cameras” product type and have a brand name of “X”:
    • Use query: Product type = Camera, Brand = X
  • Finding all inactive products within the current catalog OR across all catalogs:
    • Use query: Active = False
  • Finding all products that belong to the “Camcorder” product type and don’t have a brand name.
    • Use query: Product type = Camcorder, Brand does not exist

NOTE: Nested rules are not currently supported.

Enhanced Product Search

Custom Product Search

Steps to Enable

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

Tips And Considerations

  1. The feature provides the ability to search across a list of properties that appear on the General and Product Type tabs of the product editor including any dynamic properties that have been added by a merchant. It also allows the ability to search across the following additional properties:
  • Parent categories (parentCategories)
  • Ancestor categories (AncestorCategories)
  • Fixed related products (fixedRelatedProducts)
  • Product Images (productImages) – search for all products where a product images exists/does not exist
  • Creation date (creationDate)
  1. Includes the ability to create a single rule which will be grouped together with ("AND"/ "OR" ) also known as ("ALL"/ "ANY").
  2. The "!=" operator will return products whose property does NOT match the specified property value, in addition to those where the property value does not exist. This applies everywhere the != operator appears.
  3. You can add a dynamic checkbox property for the type of internal review you want to track (e.g. "Categorization review needed“) and then mark it "Internal Only."
  • Merchants can check the box on any products they see that they believe someone should review later.
  • Search for products using "Categorization review needed = True."
  • When the review is complete, just remove the checkmark.

Integrations

Improved Bulk Import

We’ve improved the bulk import of high volumes of product data into and from Oracle Commerce Cloud using our Admin APIs, making it easier and faster to import and export product data from an external system. The product data can be brought into Oracle Commerce Cloud in bulk, published, and loaded into the store.

The bulk import time of products is now 3x faster than the existing product bulk plugin and can be used for all product types supported in Oracle Commerce Cloud.

The new plugin splits the total number of records into batches and processes the batch. We recommend dividing the total volume of the data into batches of 500,000 for the first batch and 250,000 for any subsequent batches, importing the data, and publishing it.

Steps to Enable

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