Oracle Commerce Cloud
What's New
  1. UPDATE 19B WEEK 13
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Experience and Design
        1. Lazy Loading of Images
    2. Experiments
        1. Enhanced Navigation Flow
  1. UPDATE 19B WEEK 11
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Integrations
        1. Content and Experience Cloud Integration Improvements
  1. UPDATE 19B WEEK 9
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Catalog and Promotions
        1. Non-Discountable Products and SKUs
  1. UPDATE 19B WEEK 8
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Audiences and Personalization
        1. AddThis Support
    2. Experience and Design
        1. Cross-Site Hreflang Support (API Only)
  1. UPDATE 19B WEEK 7
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Publishing
        1. Publishing UI Improvements
        2. Search for Scheduled Events
    2. Promotions
        1. Shipping Discounts on Shipping Groups (PMDL/API Only)
  1. UPDATE 19B WEEK 6
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Catalog
        1. Default Parent Collection: API Support
  1. UPDATE 19B WEEK 5
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Audiences and Personalization
        1. Custom Query Parameters
        2. Landing Page and Referring Site

UPDATE 19B WEEK 13

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 JUL 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 19B Update 13 (19.3.13) 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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Experience and Design

Lazy Loading of Images

Experiments

Enhanced Navigation Flow

Experience and Design

Lazy Loading of Images

Our new lazy loading of images enhancement helps increase the speed of meaningful content paint and perceived page load by recognizing which images are in focus and loading them first. It allows pages with more content to be presented without necessarily paying a price in page performance. It also allows the ability to configure a delay so that images that are out of focus can be loaded in the background later.

This feature is turned off by default and can be activated via the API. We’ve also included a new image tag that can be combined with existing image features, such as ccimageResize. All existing image bindings will support it. Note that the image bindings provided by OCC allow the merchant to specify alternative CSS class names for the parent element of the img element and the img element respectively while the image is waiting to be lazily loaded and for the img element after it has been lazily loaded.

Steps to Enable

  1. Activate via the API - New loadImagesLazily option is in ccadminui/v1/merchant/cloudConfiguration. This is switched off by default and has to be activated.
  2. Once activated, any of the existing image bindings will work to load images lazily (e.g. ccImageResize).
  3. New Image binding is also available which supports all existing image features.
  4. You can add a delay before loading the out of focus images:

"loadImagesLazily": true,

"delayBeforeLoadingOutOfFocusImages": 10

You can specifically disable lazy loading on less image intensive pages: <img data-bind="image: {src: <yourImageSource>, disableLazyImageLoading: true}, ...">

Tips And Considerations

NOTE: Lazy loading is useful for sites that are image heavy. Sites with few images may not benefit and we do not recommend turning on lazy loading of images for image-light sites.

Experiments

Enhanced Navigation Flow

We've made it easier to access Experiments within the Admin UI by adding a direct link to Experiments from the Marketing area. This is especially useful for users that do not have permission to access Design Studio, but need to be able to view A/B testing results, create, edit, stop, and rerun experiments. Previously, business users had to be granted access to Design Studio and navigate through layouts and slots to access Experiments.

We've also made it easier to get back to the Design Studio layout a user was on when launching Experiments by adding a "Return to Admin" deep link in the Experiments navigation.

Experiments Navigation Improvements

Steps to Enable

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

UPDATE 19B WEEK 11

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
17 JUL 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 19B Update 11 (19.3.11) 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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Integrations

Content and Experience Cloud Integration Improvements

Integrations

Content and Experience Cloud Integration Improvements

We've made a few improvements to the Oracle Commerce Cloud integration with Oracle Content and Experience Cloud, including:

  1. Merchants can now set up the integration within the Oracle Commerce Cloud Admin by using their Oracle Content and Experience Cloud account credentials.
  2. Viewport support has been added for Content Layout Type, making it possible to develop viewport-specific content and improve the mobile experience.
  3. A Sort by Date option has been added for the Content Listing Widget, allowing most recently published content to appear first. New instances of the Content Listing Widget will now sort by most recent first by default.

Setting Up the Oracle Commerce Cloud Integration with Oracle Content and Experience Cloud in the OCC Admin UI

Steps to Enable

  1. Go to Oracle Integrations in the Oracle Commerce Cloud Admin UI under Settings, and select Content and Experience.
  2. Enable integration and add the server URL (just the basic URL no /documents, for example).
  3. Enter the channel ID and token you want to add for the current site.
  4. Click ”Add user” to add your Oracle Content and Experience Cloud user name and password.
  5. Repeat for any further sites/channels you want to map.
  6. You can now add content listing widgets to any layouts and should see pages appear under the content item layout when you publish content items to the mapped channels.

Tips And Considerations

If you already have the Oracle Commerce Cloud Integration for Oracle Content and Experience Cloud enabled, these improvements are available automatically. If you do not have the integration already enabled, you can now enable it right in the Commerce Cloud Admin Settings UI.

UPDATE 19B 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
17 JUL 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 19B Update 9 (19.3.9) 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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Catalog and Promotions

Non-Discountable Products and SKUs

Catalog and Promotions

Non-Discountable Products and SKUs

For products and SKUs that should never be part of an item or order promotion (e.g. MAP product), merchants can now set a flag once and exclude those products and SKUs, rather than having to manually exclude them from each individual promotion. Any product or SKU can be marked as discountable (the default) or non-discountable. The discountable flag is only used for consideration in item and order promotion eligibility. These items can still have a sale price set in the price list. Also, products and SKUs marked as non-discountable will still be included in shipping promotions and discounts (e.g. Spend $100 and get free standard shipping).

For item discounts, when OCC calculates these promotions, non-discountable products and SKUs will not be included, as these items are marked discountable = false.

For order discounts, when OCC applies promotions to the order total, the price of non-discountable products and SKUs will not be included, as these items are marked discountable = false.

When a product and its child SKUs have different values for the discountable flag, non-discountable always takes precedence. For example, if an item is marked non-discountable at the product level, all of its child SKUs will also be treated as non-discountable (regardless of actual discountable flag status). If a product is marked discountable, but one of its child SKUs is marked non-discountable, only the SKU marked non-discountable will be excluded from an item or order promotion.

For add-on products, only the discountable status of the parent item is considered. For example, if a merchant runs a 50% item discount on bikes, and a shopper adds to cart a bicycle (discountable) for $100 with an add-on bike helmet (non-discountable) for $20, the 50% item discount will apply to the total $120, not just the $100 bicycle.

NOTE: For merchants using the external promotions webhook: Promotions that are calculated and applied to the order from other systems do not use the non-discountable flag.

Discountable Flag

Steps to Enable

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

Tips And Considerations

An item’s discountable flag status always takes precedence over any individual promotion’s inclusion rules.

Item and Order Discount Examples

UPDATE 19B WEEK 8

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
17 JUL 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 19B Update 8 (19.3.8) 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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Audiences and Personalization

AddThis Support

Experience and Design

Cross-Site Hreflang Support (API Only)

Audiences and Personalization

AddThis Support

Merchants can now leverage Oracle AddThis data to help provide even first-time visitors (in addition to registered and anonymous shoppers) with relevant site experiences. AddThis data can be used alone or in conjunction with existing attributes and parameters to build powerful Audience rules for targeting content, promotions, and products to shoppers, driving conversion and retention.

AddThis is particularly useful for “cold start” personalization in instances where merchants do not have much (or any) data about a shopper visiting the site. This applies to first-time visitors, but AddThis data can also be useful for registered and anonymous shoppers, to help round out the picture and profile of a shopper and his/her preferences.

AddThis observes visitors anonymously as they visit one or more of the millions of sites that are partners of AddThis and determines which of approximately 400 different interests apply to each visitor. This information is made available through our out of the box OCC AddThis integration, so that merchants can do broad-based personalization for a new (or existing) shopper based on these interests. Merchants can combine AddThis interests with all of the other personalization features in OCC, to create more differentiated experiences.

AddThis Interests in OCC

Enabling AddThis in OCC via the Admin UI

Steps to Enable

To enable the integration, go to the OCC Admin UI under Settings > Oracle Integrations and opt into the AddThis cooperative agreement.    

Tips And Considerations

NOTE: Due to GDPR, AddThis is not operational in Europe, so audience rules that evaluate AddThis interests will behave as though European visitors have no interests.

Experience and Design

Cross-Site Hreflang Support (API Only)

Hreflang tags tell Google which language is being used on a specific page, so the right result can be served when users are searching in that language. For merchants with more than one site, OCC now has native API support for hreflang references across sites, allowing merchants to utilize out of the box functionality for linking these language variations. This new API allows merchants to organize site-language combinations into hreflang groups of two or more. Hreflang tags will be applied on the storefront for language versions of the same page within a group. Allows for the ability to define a default for each group (x-default).

If no group is set up, the default behavior will apply hreflang references to languages within a site. 

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: When utilizing this feature, merchants should make sure to group all new languages that are added. OCC defers the grouping responsibility to the merchant operating in this mode moving forward.

Example:

<link rel="alternate" hreflang=“en" href=" https://www.example.com/my-fancy-shoe/12345 ">

<link rel="alternate" hreflang=“de" href=" https://www.example-de.com/mein-schicker-schuh/12345 ">

UPDATE 19B 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
17 JUL 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 19B Update 7 (19.3.7) 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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Publishing

Publishing UI Improvements

Search for Scheduled Events

Promotions

Shipping Discounts on Shipping Groups (PMDL/API Only)

Publishing

Publishing UI Improvements

We've made two publishing-related UI improvements. First, we've made it easier to find items to publish in the change list. You can now Sort by Publishing Event.

Sort by Publishing Event  

Second, we've made it easier to find the Publish All option which allows merchants the ability to publish everything in the change list.  

Publish All Changes

Steps to Enable

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

Search for Scheduled Events

We've added the ability for merchants to search for publishing events by name, making it easier to find specific events they want to publish or review.

Search for Scheduled Events

Steps to Enable

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

Promotions

Shipping Discounts on Shipping Groups (PMDL/API Only)

Merchants can now apply shipping discounts to shipping group totals instead of just order totals. Shipping Discount promotions can be created based on number of items in the shipping group or the spend amount in the shipping group. For example, Spend $50, Get Free Standard Shipping (items must ship together) promotion is now supported. 

With this new feature, merchants can target shipping discounts to a specific shipping group only (e.g. only overnight delivery or only standard shipping). It also allows the ability to create "items must ship together" discounts.

NOTE: This is an API only feature available via PMDL.

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

PMDL example:

<pricing-model>

  <qualifier>

    <greater-than>

      <value>shippingGroup.priceInfo.itemSubtotal</value>

      <constant><data-type>java.lang.Double</data-type><string-value>65.0</string-value></constant>

    </greater-than>

  </qualifier>

  <offer>

    <discount-structure adjuster="0.0" calculator-type="standard" discount-type="fixedPrice"/>

  </offer>

</pricing-model>

UPDATE 19B WEEK 6

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
17 JUL 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 19B Update 6 (19.3.6) 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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Catalog

Default Parent Collection: API Support

Catalog

Default Parent Collection: API Support

Oracle Commerce Cloud now includes API only support for setting up a default parent collection both per catalog and per product. Specifically, it supports setting up:

  • A default parent collection per catalog for linked collections which are visible in more than one catalog or collection.
  • A default parent collection per product for linked products which are visible in more than one catalog or collection.

Default parent collections are required to be able to use the breadcrumb functionality within Oracle Commerce Cloud. This means that if a product is, for example, returned from a search, then the collection associated to that product will be displayed in the breadcrumb. If a product is in multiple collections, the breadcrumb will display the default parent collection.

This feature is especially useful in instances where merchants have multiple sites and each site has its own catalog. If each catalog reuses collections across catalogs, but also multiple times within the same catalog, the default parent collection for collections and products that have multiple parents must be set up, so that when breadcrumbs are displayed (or when the collection or product shows up in search results), they accurately reflect the appropriate parent for the catalog being viewed. If a collection or product has only one parent, there is no requirement to set up a default parent, however this is recommended, and assigning these defaults for a single catalog can also be done with this API.

Default parent collections have impacts on URL patterns. Merchants can set up their own URL pattern for collection or product URLs using the default parent collection as follows: {parentCategory}/{categoryId}. The URL would look something like this: [domain]/shoes/womens-shoes

Default parent collections are also used to properly attribute product and category views to parents for reporting and personalization purposes.

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: Adding or changing default parent collections has an impact on the site URL pattern for collection or product URLs, as well as the site map. Any changes made require a Service Request for a server-side 301 redirect, so that the URLs are properly resolved.

Key Resources

Refer to Create/Update Collection and Create/Update Oracle Commerce Cloud Product REST API documentation on how to set parentCategory property and scope for more details.

UPDATE 19B WEEK 5

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
17 JUL 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 19B Update 5 (19.3.5) 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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Audiences and Personalization

Custom Query Parameters

Landing Page and Referring Site

Audiences and Personalization

Custom Query Parameters

In addition to being able to build audiences of shoppers based on UTM query parameters, merchants can now build audiences of shoppers based on other custom query parameters that are included as part of a shopper's visit URL (current session only).

This feature is particularly useful for merchants that do not use Google Analytics or use more sophisticated query parameters for marketing tracking.

Merchants can now ensure a consistent, personalized experience from external campaigns, such as email, PPC, or social ads, through to the commerce site. This feature also allows merchants to automatically apply promotions for shoppers visiting from a particular media source or with a specific keyterm.

Custom Query Parameter Audience Rule Creation

Steps to Enable

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

Tips And Considerations

Audience size estimates are not available for audience rules built against custom query parameters.

Landing Page and Referring Site

Merchants can now build audiences of shoppers based on either:

  • A landing page on the Oracle Commerce Cloud site
  • Referring site (current session only)

String matching can be used to select a range of landing pages to apply an audience rule against. For example, this can be used to present a personalized experience to shoppers landing on a particular set of landing pages on the site (e.g. landing page URL contains "holiday").

This feature is useful for ensuring a consistent, personalized experience from a referring site through to the commerce website. It also allows merchants to automatically apply promotions for shoppers visiting from a particular referring site, as well as provide a different experience for segments of shoppers landing directly on a particular page of the website.

Landing Page Audience Rule Creation

Referring Site Audience Rule Creation

Steps to Enable

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

Tips And Considerations

Audience size estimates are not available for audience rules built against landing pages and referring sites.