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


  1. UPDATE 20C REVISION 12
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Integrations
        1. Integration with Subscription Management
  1. UPDATE 20C REVISION 3
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Catalog
        1. Edit Catalog Directly on Storefront
  1. Update 20C
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Catalog
        1. Product Listing Enhancements
    2. Platform
        1. Store Extension APIs
    3. Promotions
        1. New Property in Order Payload: itemDiscountInfos
        2. New Property in Order Payload: orderDiscountInfos
    4. Integrations
        1. Bulk Import of Prices (Prices Plug-In)
    5. Audiences and Personalization
        1. Supporting Custom Property for Rich Text Fragments
    6. Search
        1. Facet Management API
        2. Machine Learning for Search
        3. Search Autosuggest (API Only)

Update 20C Revision 12

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 Product Feature Notes
03 NOV 2020 Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

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 CX Commerce What’s New for 20C Revision 12 (20.3.12) 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*

Integrations

Integration with Subscription Management

Integrations

Integration with Subscription Management

With subscriptions becoming an increasingly popular way to buy products and services online, businesses are looking to strengthen customer relationships and evolve their strategies by taking advantage of a solution that also supports complex products and services.

With the release of the Integration with Subscription Management feature, CX Commerce customers now have access to new functionality for generating loyalty and long-term customer relationships while simplifying the commerce experience.

Key benefits:

  • Self-service for managing the entire life cycle of subscription management
  • Self-service capability for subscription management of complex configurable services
  • Subscriptions can be created and modified seamlessly across CX Commerce, CPQ and Subscription Management applications.
  • Enables subscriptions of configurable services to the shoppers.
  • Capability highlights:

Integrating with Subscription Management, shoppers are now able to:

  • Create subscriptions of complex configurable services with recurring prices and flexible durations as defined in the CPQ application.
  • Modify configurations, change quantity, upgrade/downgrade the service as defined in the CPQ configuration.
  • View all subscriptions in Commerce that are created across Commerce, CPQ and Subscription Management applications.
  • Pay via credit card and invoices.
  • Modify, upgrade/downgrade, suspend/resume anytime through self-service Commerce application.
  • Renew subscriptions at the end of period of their original subscription date.

This integration makes it easy to set up subscription services with flexibility for the needs of your product.

For example, as a distributed remote workforce becomes the norm, video conferencing and remote working technology has become a necessity. This example scenario illustrates options that may be offered when selecting the right service for your business needs and shows the kind of complex offering that can be set up using this integration.

Video Conferencing solution for five users:

  • Device: Panoramic 360° 4K output camera - $1,200 one-time charge
  • Installation service - $0
  • Subscription: web conferencing $50 per month/user
  • Options: unlimited data recording - $5 per month/user

Users can choose any of the above options with flexibility to subscribe for 12, 24 or 60 months and ability to modify user / devices, upgrade/downgrade service options, terminate or renew the subscription at any time.

This is an API only feature with sample widget codes provided in the Integrate with Oracle Subscription Management product documentation.

Business benefits:

  • Increased customer satisfaction and loyalty, resulting in long-term relationships that drive revenue growth

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

Current limitations and considerations:

  • This integration currently handles one-time payment and recurring charges only. Other charges, such as termination charges and the charge structure of CPQ will be handled in later phases.
  • The delta price changes due to modification flows will be handled in later phases. Currently handled by terminating the subscription line and creating a new line with full price. 
  • Supports intangible complex service configurations with recurring prices and one-time price defined in CPQ
  • All recurring pricing must come from pricing via the CPQ configurator.
  • For credit card transactions, customers using Fusion Financials should use CyberSource which is the common payment gateway shared across CX Commerce and Fusion applications. (CX Commerce supports generic payment gateway services and customers who do not use Fusion Financials can use any payment gateway that they have configured.

Update 20C Revision 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 Product Feature Notes
28 AUG 2020     Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

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 CX Commerce What’s New for 20C Revision 3 (20.3.3) 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

Edit Catalog Directly on Storefront

Catalog

Edit Catalog Directly on Storefront

With this feature, businesses requiring frequent or high-volume catalog updates can now edit catalog items and move them directly to production, bypassing the publishing process.

Capability highlights

  • Ability to edit catalog items via Admin UI and CSV file import.
  • Ability to edit catalog items via Bulk Import API and Admin API.
  • To accommodate direct edit, a search indexing schedule is automatically created and run every 15 minutes by default.

Editing directly on the storefront cannot be used simultaneously with pricing or catalog edits that must be published.  Business users should select the catalog editing model that best fits their business needs, as the feature is not intended to be turned on and off.

Business users and merchandisers can see results of the changes immediately on the storefront, providing increased productivity whether changes are nightly or throughout the day.

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.

This feature must be turned on via API.

Update 20C

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 Product Feature Notes
05 AUG 2020     Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle CX Commerce 20C 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 CX Commerce What’s New for 20C Update 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

Product Listing Enhancements

Platform

Store Extension APIs

Promotions

New Property in Order Payload: itemDiscountInfos

New Property in Order Payload: orderDiscountInfos

Integrations

Bulk Import of Prices (Prices Plug-In)

Audiences and Personalization

Supporting Custom Property for Rich Text Fragments

Search

Facet Management API

Machine Learning for Search

Search Autosuggest (API Only)

Catalog

Product Listing Enhancements

With this release, merchandisers now have access to new and improved tools for managing and re-ordering products within collections in addition to performing operations on multiple products at one time. Products designated as inactive are now visible at a glance.

Capability highlights

  • After selecting one or more products, merchandisers can link to single or multiple collections and select preference for viewing.
  • A gear menu has been added to each row in list view and enhanced in the product listing toolbar.
  • Merchandisers can reorder multiple products within a collection using drag/drop in list view. 
  • An inactive badge has been added to the product tile.

Steps to Enable

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

Platform

Store Extension APIs

With this release, merchants can leverage new Store Extension APIs that have been added to the Store API set, previously only available on Admin. Server-Side Extensions and other integrations can use these APIs to support shopper experiences at scale.

The following new Store Extension REST APIs are now available:

  • /ccapp/v1/profiles
  • /ccapp/v1/organizations
  • /ccapp/v1/organizationRequests
  • /ccapp/v1/orders 

These new Store Extension APIs allow server-side extensions (SSEs) and integrations to access profile or order data that a merchant doesn’t want exposed directly to the shopper, such as sensitive information on the profile that shouldn’t be seen or edited by the shopper or information on the order that is used for validation.

These new APIs at /ccapp replace calls to /ccadmin/ and offer greater scalability and performance. We strongly recommend changing your endpoints to use these new Store Extension APIs, if you are using the Admin version of these APIs today.

Capability highlights

  • Added APIs previously only available as part of the Admin API to the Store API set so they can be called at storefront scale
  • New REST API on the Store servers: /ccapp/v1/profiles, /organizations, /organizationRequests, and /orders in this first phase
  • Authentication using AppID remains the same, so use the same application key. 

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

These new Store Extension APIs should not be used for widgets, since that would publicly expose the application key.

Key Resources

Review the more detailed FAQ on using these new Storefront Extension APIs in the Oracle CX Commerce forum of Customer Connect.

Promotions

New Property in Order Payload: itemDiscountInfos

A new property, itemDiscountInfos, has been added to the order payload providing a list of the item promotions and discount values applied to cart items.  The property has been added to the Admin order and SubmitOrder webhook payloads. This makes item-based promotions performance more accurate and easier to understand.

Capability highlights:

  • A new property itemDiscountInfos is added to the Admin.getOrder response and SubmitOrder webhook response.
    • The response contains an entry at the item level for each item in the order.
  • The itemDiscountInfos is returned along with the promotion id and any coupon codes used to grant the promotion.

Key benefits:

  • The information is now presented in an easily consumable format.
  • Provides more granular details about the discounts have been applied.
  • Can be used for reporting as well as sent to downstream systems (e.g. financial systems).

Steps to Enable

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

New Property in Order Payload: orderDiscountInfos

A new property, orderDiscountInfos, has been added to the Storefront, Admin, and Webhook order payloads and provides a list of the order promotions and discount values that apply to each cart item. This makes order-based promotions performance more accurate and easier to understand.

Capability highlights:

  • The value of orderDiscountShare is proportionately weighted across the entire order.
  • The new orderDiscountInfos property shows the contribution of each order promotion to the orderDiscountShare value.
    • The response contains an entry at the item level for each item in the order.
  • The orderDiscountInfos property is returned along with the promotion id and any coupon codes used to grant the promotion.

Key benefits

  • Provides more granular details about the discounts that have been applied.
  • Can be used for reporting purposes as well as sent to downstream systems (e.g. financial systems).
  • The order discount values are proportionate at each item level.

Steps to Enable

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

Integrations

Bulk Import of Prices (Prices Plug-In)

With the release of our new Prices Plug-in, merchants now have the capability to bulk import prices for products and SKUs from an external system. Existing price list groups can be updated with the latest prices from an external system as well. This is designed for instances when prices need to be imported frequently from an external source.

Product prices can be bulk exported from CX Commerce by using the Q parameters of the Plug-in to export.

  • Capability highlights
    • Supports JSON and CSV formats.
    • Can be triggered using the bulk APIs of CX Commerce.
    • All CRUD operations supported.

This feature does not replace any of the existing price upload capabilities in the Admin UI.

Steps to Enable

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

Tips And Considerations

The plug-in cannot be used to create a price list group, as it must have previously been set up in CX Commerce.

Access path: http:///ccadminui/v1/importProcess [Plug in Name: Prices]

Audiences and Personalization

Supporting Custom Property for Rich Text Fragments

With this new feature, merchants can now create Audience rules from shopper and account profile data when the customer information is provided in a lengthy XML string (e.g. through SAML response).

The fields provided in CX Commerce may not be enough to hold the XML strings sent to the merchant from an external system, like a third party loyalty, marketing, or SAML identity provider. Storing in a custom RichText property on the profile allows merchants to create rules to ensure a consistent personalized experience.

Key benefits

  • Behaves just like any other text property
  • New properties are created via Shopper Types API; properties are available in CX Commerce Audiences UI.
  • Supports both B2C and B2B.

To use this feature:

  • Create the new Rich Text Profile property via the Shopper Types API for either Shopper Profile (B2C) or for Account (B2B).
    • Ensure, as you would for any custom property, that the audienceVisibility property is set to ‘all’ for Shopper Profile properties and to ‘B2B’ for Account properties.
    • The audienceVisibility attribute determines whether a property appears as a choice in the Attributes field of the CX Commerce Audience UI.
  • The newly created property is then available within the CX Commerce Audiences UI under either Shopper Profile or Account.
  • Define rules as you generally would for any text properties, where you are matching on a value within the property.
  • Complete the customary steps for building and using Audiences to vary content.

Steps to Enable

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

Search

Facet Management API

CX Commerce search now provides developers the ability to enhance the user experience by customizing faceted navigation. The Facet Management API enables developers to manually order facet values, add metadata to facet values and create custom price range values. The feature also supports custom price navigation requirements.

The following examples describe the capabilities made possible with this feature:

  • With facet values such as sizes small / medium / large that should be ordered manually rather than dynamically, you can now sequence them using the API.
  • To associate swatch imagery with color values, custom metadata can be added to the values.
  • If the out-of-the-box price ranges are not suitable, you can create custom price range values
    • e.g. $0-10, $11-25, $26-$50, $51-$100, $101-200.

NOTE: Changes to facet values require an index to view results, therefore need to be published to take effect.

Intended for more technical users, there are a series of steps involved when using this feature.

  • For manually ordering facet values
    1. Specify in /gsadmin/v1/cloud/attributes/system/<facet-name> the new sort configuration, for example "sort": "displayOrder,desc;displayName,asc“ - to define that the facet is ordered by display order, and any undefined values are ordered alphabetically.
    2. Use /gsdata/v1/cloud/facets/<facet-name> to list the values that should be ordered, along with their relative “displayOrder” property (with 1 being first).
    3. If you want to retrieve a list of all values for a facet, you can call GET /gsadmin/v1/cloud/dimvals/<facet name>/children.
  • For adding metadata
    1. Use /gsdata/v1/cloud/facets/<facet-name> to add new key/value pairs – use a prefix of x_ as a naming convention for the keys to avoid conflicting with existing system keys, for example “x_swatchImage”: “/images/swatches/red.png”.
    2. If you want to retrieve a list of all values for a facet, you can call GET /gsadmin/v1/cloud/dimvals/<facet name>/children.
  • For creating custom price ranges
    1.  Create a new facet in /gsadmin/v1/cloud/attributes/system/, for example POST /gsadmin/v1/cloud/attributes/system/custom.priceRange (custom.priceRange is just an example in this case).
    2.  Define the ranges for this value using /gsdata/v1/cloud/facets/custom.priceRange.

The Facet Management API feature is currently API only.

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

  • For manual ordering, you can choose a secondary sort (e.g. “alphabetical”) for any values that are not explicitly listed.
  • For manual ordering and adding metadata, if the values intended for customization are not known, you can use the separate “dimval” REST API service to get a master list.
  • For custom price ranges, only one price group can be mapped to a custom price range.

Machine Learning for Search

With this release, CX Commerce Search now utilizes machine learning and decision science to determine the optimal results to present to the shopper, improving the relevance of the shopping experience and increasing the likelihood of conversion. The keyword search results are calculated using a combination of factors, including shopper behavior, shopper purchasing history, trend analysis, and view data.

This new feature works in harmony with dynamic curation and search relevancy. Manually boosted products take precedence followed by products identified by machine learning, with all remaining products ordered by relevancy and dynamic curation criteria.

This feature only takes effect for keyword search results and any subsequent navigation. It will not take effect on pages that only contain navigation results.

To use this feature:

As this feature changes the order of results displayed on the site, it is not enabled by default.

Steps to Enable

To enable the feature, simply call the API endpoint “/gsadmin/v1/cloud/configuration/services/internal-keywords” and change the property “boostDisabled” from “true" to “false”

Note that it will not take effect until the nightly process has completed.

Tips And Considerations

  • The products to promote are calculated in a nightly process, and this process must run after being enabled.
  • To identify when products have been promoted, you can access your site using the Preview environment and inspect the underlying ccstore/v1/search endpoint call. Promoted products will include an additional property of “DGraph.RankLabel.bstratify.merch.
  • To disable this feature, set “boostDisabled” to “true”, then DELETE all previously generated rules in /gsadmin/v1/cloud/content/system/rankingRules/internal-keywords.

Search Autosuggest (API Only)

The CX Commerce storefront’s pre-integrated feature set includes search autosuggest, also known as “type-ahead,” which presents products that match the characters entered by the shopper.

With this release, you can now utilize an alternative autosuggest pattern and present matching searches that are popular on your site, making it more likely for shoppers to find what they are looking for more quickly and improving the shopping experience. For example, if a shopper enters “blu,” you can show “Bluetooth speaker,” “blue dress,” “blusher,” and “Bluetooth headphones.” The automatically generated suggestions can also be supplemented with manually created suggestions.

Capability highlights

  • Search autosuggest provides intelligent suggestions to shoppers as they type.
  • The suggestions are automatically generated based on analysis of your live server traffic.
  • Popular suggestions are presented based on pattern matching and then ordered based on a relative “keyword.score.” This property is calculated using several factors, including search popularity.
  • Processing is predominantly handled server-side, ensuring an extremely fast response which is important for autosuggest as latency has a significant impact.

This is an API-only feature. A custom widget will be required to parse the JSON response and display the suggestions.

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.

To implement, follow the steps outlined in the documentation, including:

  • Use the Attributes API to ensure keyword.searchable, keyword.terms, and keyword.score are correctly configured.
  • Update the keywords searchable field ranking to ensure keyword.searchable is indexed.
  • As an option, add your own custom keywords and – if required – set up associated keyword redirects.
  • Once an index is run (this can be manually invoked by calling POST /ccadmin/v1/search/index { “op”: “baseline” }), suggestions can be returned by calling: GET /ccstore/v1/assembler/pages/Default/keywords/typeahead?Ntk=keywords&Ntt=<characters>

Tips And Considerations

The auto-populated searches can’t be changed, however additional searches can be updated using the “keywords” data store.