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. |
This guide outlines the information you need to know about new or improved functionality in this update.
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.
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, rather than the shopper creating a password during registration, the shopper fills in his/her name and email and submits a registration request which triggers a secure tokenized reset password link. The shopper than needs to click on that link, enter a password, and complete account registration.
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.
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.
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 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. |
This guide outlines the information you need to know about new or improved functionality in this update.
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.
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 and enable the ability to drive a number of merchandising enhancements.
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. |
This guide outlines the information you need to know about new or improved functionality in this update.
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.
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 additional properties, including parent collections (parentCategories), ancestory collections (ancestorCategories) and creation date (creationDate)
- Ability to find and export recently added items, as well as export based on specific or missing values, such as being able to find products with no product images.
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.)
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. |
This guide outlines the information you need to know about new or improved functionality in this update.
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.
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
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.
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.
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. |
This guide outlines the information you need to know about new or improved functionality in this update.
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.
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:
- 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
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.
NOTE: Enable this option only if you need the additional information, as it increases the size of the payload and could affect performance.
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. |
This guide outlines the information you need to know about new or improved functionality in this update.
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.
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.
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.
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.
Related Products API Improvement
We’ve provided a new optional global setting to skip retrieving parent category details from related products, 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.
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”
To leverage, download the search service using:
GET /gsadmin/v1/cloud/pages/Default/services/guidedsearch
Add properties, then upload.
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).
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, recently added items, find products with no product images, find all inactive products, find all products in a particular brand, and find all products that belong to a particular product type, but don’t have a brand name. for example.
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.