Oracle Commerce Cloud
What's New
  1. APRIL MAINTENANCE PACK FOR 19A
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Major New Features
    1. Publishing
        1. Edit Prices on Storefront
        2. Publish Filtered List
    2. Audiences and Personalization
        1. Geolocation
  5. Additional New Features and Other Changes
    1. Browser Support, Language, and Currency Support
        1. Language and Currency Support
        2. Browser Support
    2. Storefront and Agent
        1. Customize Emails for Saved Carts
        2. Changing the Status of Contact Registration Requests
    3. B2B
        1. Customizing Countries and Regions in Addresses
    4. Webhooks
        1. Manage Failed Event Webhook Messages
        2. Retry Functional Webhook Failures
    5. Payments
        1. Add Card to Profile
    6. Experience and Design
        1. Preview Enhancements
    7. Search Admin
        1. Dynamic Curation Preview
  1. Update 19A
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Major New Features
    1. Storefront
        1. Buy Online, Pick-Up in Store
    2. Payments
        1. Stored Credit Cards
    3. Search Admin
        1. Boost and Bury
        2. Facet Ordering
    4. Integrations
        1. Content and Experience Cloud: New "Channel" to Site Mapping
        2. Content and Experience Cloud: New Content Listing Widget
        3. Content and Experience Cloud: New Content Item Layout
        4. Content and Experience Cloud: API for CMS Integrations
  5. Additional New Features and Other Changes
    1. Browser Support, Language, and Currency Support
        1. Browser Support
        2. Language and Currency Support
    2. Agent Console
        1. Agent Console Customization
    3. B2B
        1. B2C to B2B Profile Conversion
    4. Publishing
        1. Publishing of Individual Design Assets
    5. Experience and Design
        1. DCU - Stack and Element Support
        2. DCU: CCProxy Substitution
        3. HTML Snapshots: Mobile Support
    6. Search
        1. Type-Ahead Framework
    7. Audiences and Personalization
        1. UTM Query Parameters
    8. Recommendations
        1. Collection Override
    9. Experiments
        1. Custom Goals for Widget Experiments
        2. New Goal Type: Commerce Events

April Maintenance Pack for 19A

Revision History

Date Feature Notes
03 MAY 2019 Add Card to Profile Updated document. Delivered feature in April Maintenance Pack for 19A.
24 APR 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Commerce Cloud April Maintenance Pack for 19A 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 April Maintenance Pack for 19A What’s New in the body or title of the email.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Major New Features

Publishing

Edit Prices on Storefront

Publish Filtered List

Audiences and Personalization

Geolocation

Additional New Features and Other Changes

Browser Support, Language, and Currency Support

Language and Currency Support

Browser Support

Storefront and Agent

Customize Emails for Saved Carts

Changing the Status of Contact Registration Requests

B2B

Customizing Countries and Regions in Addresses

Webhooks

Manage Failed Event Webhook Messages

Retry Functional Webhook Failures

Payments

Add Card to Profile

Experience and Design

Preview Enhancements

Search Admin

Dynamic Curation Preview

Major New Features

The April Maintenance Pack for 19A of Oracle Commerce Cloud includes substantive improvements and changes to the product.

What follows is a brief summary. For more details about each feature and improvement, please review the April Maintenance Pack for 19A What’s New document and the official Oracle Commerce Cloud documentation in the Oracle Cloud Help Center.

The major new features released in Oracle Commerce Cloud April Maintenance Pack for 19A include:

Publishing

Edit Prices on Storefront

For merchants who make high-frequency price changes, OCC now allows for editing prices directly in the storefront, bypassing the publishing process. Merchants can edit product and SKU prices in the OCC Admin UI or use CSV file import.

Search is automatically adjusted to use an automated frequent indexing schedule to update, so that the updated price is presented to shoppers. 

NOTE: Cannot be used simultaneously with price edits that must be published. Merchants should select the price editing model that best fits their business needs. 

Steps to Enable

This feature is not turned on by default and must be configured using the updateDirectPriceEdit API endpoint.

Publish Filtered List

OCC Admin users can now filter the change list and publish items without explicitly selecting checkboxes (selecting items one by one or page by page).

Steps to Enable

No steps are required to enable this feature.

Audiences and Personalization

Geolocation

Merchants now have the ability to build audiences of registered or anonymous shoppers based on their location as reported by the CDN. Audiences can be built based on Place (country, region, city), Latitude and Longitude, and Time Zone, allowing merchants to present personalized content, products, and offers to shoppers in different areas of the country, for example, to present cold weather products to people living in the Northeast, show special promotions to people living in a city where the merchant has a physical store, or display targeted content to people in a specific location and time zone timed to coincide with a time-dependent on-air television spot, radio ad, and/or social media campaign.

Geolocation-based audience rules can also be combine with other existing rules, making personalization capabilities even more powerful.

Steps to Enable

No steps are required to enable this feature.

Additional New Features and Other Changes

There are also a number of additional new features, changes, and improvements included in Oracle Commerce Cloud April Maintenance Pack for 19A. By functional area, these include:

Browser Support, Language, and Currency Support

Language and Currency Support

Languages: No new languages are supported.

Forty languages are currently supported: Arabic (ar) (Storefront only), Bulgarian (bg), Catalan - ca (Storefront only), Chinese—Simplified (zh_CN), Chinese—Traditional (zh_TW), Croatian (hr), Czech (cs), Danish (da), Dutch (nl), English (en), English-GB (en-GB), Estonian (et), Finnish (fi), French (fr), French Canadian (fr_CA), German (de), Greek (el), Hungarian (hu), Indonesian - id (Storefront only), Italian (it), Japanese (ja), Korean (ko), Latvian (lv), Malay - ms (Storefront only), Norwegian (no), Polish (pl), Portuguese—Brazil (pt_BR), Portuguese—Portugal (pt_PT), Romanian (ro), Russian (ru), Serbian - Cyrillic (sr), Serbian – Latin (sr_Latn),,Slovenian (sl), Spanish (es), Swedish (sv), Thai (th), Turkish (tr), Ukrainian (uk), and Vietnamese - vi (Storefront only).

Currencies: No new currencies are supported.

Sixty-one currencies are currently supported:  AED (UAE Dirham), ARS (Argentine Peso), AUD (Australian Dollar), BGN (Bulgarian Lev), BOB (Boliviano), BRL (Brazilian Real),  CAD (Canadian Dollar), CHF (Swiss Franc), CLP (Chilean Peso), CNY (Chinese Yuan Renminbi), COP (Colombian Peso), CRC (Costa Rican Colon), CZK (Czech Koruna), DKK (Danish Krone), DOP (Dominican Peso), DZD (Algerian Dinar), EGP (Egyptian Pound), EUR (Euro), GBP (British Pound Sterling), GTQ (Guatemalan Quetzal), HKD (Hong Kong Dollar), HNL (Lempira), HRK (Croatian Kuna), HUF (Hungarian Forint), IDR (Indonesian Rupiah), INR (Indian Rupee), JPY (Japanese Yen), KES (Kenyan Shilling), KRW (South Korean Won), KZT (Tenge), LBP (Lebanese Pound), MAD (Moroccan Dirham), MXN (Mexico Peso), MYR (Malaysian Ringgit), NGN (Naira), NIO (Cordoba Oro), NOK (Norwegian Krone), NZD (New Zealand Dollar), PAB (Panamanian Balboa), PEN (Peruvian Nuevo Sol), PHP (Philippine Peso), PKR (Pakistani Rupee), PLN (Polish Zloty), PYG (Paraguayan Guarani), QAR (Qatari Riyal), RON (Romanian Leu), RSD (Serbian Dinar), RUB (Russian Ruble), SAR (Saudi Riyal), SEK (Swedish Krona), SGD (Singapore Dollar), THB (Thai Baht), TJS (Somoni), TRY (Turkish Lira), TWD (New Taiwan Dollar), UAH (Ukrainian Hryvnia), USD (US Dollar), UYU (Uruguayan Peso), VND (Vietnamese Dong), XAF (CFA Franc BEAC), ZAR (South African Rand).

Steps to Enable

No steps are required to enable this feature.

Browser Support

Browser support is up-to-date.  

Steps to Enable

No steps are required to enable this feature.

Storefront and Agent

Customize Emails for Saved Carts

For stores that support saved cart functionality, it is now possible to add the cart name property to email templates to display the name of a saved cart to emails, such as the abandone cart email, to remind customers about items in their saved cart. 

Steps to Enable

No steps are required to enable this feature.

Changing the Status of Contact Registration Requests

In the Agent Console, agents acting as delegated administrators can now change the status of a contact request (Accept, Reject, More Info Needed, Review, New) improving workflow efficiencies.

Steps to Enable

No steps are required to enable this feature.

B2B

Customizing Countries and Regions in Addresses

New Admin API endpoints at /ccadmin/v1/countries now let merchants add, delete, and update countries and regions available to their store, making it possible to manage a list of countries and regions that have assigned abbreviations for region and display names.

NOTE: Each country and region added must match a valid ISO 3166 code.

Steps to Enable

No steps are required to enable this feature.

Webhooks

Manage Failed Event Webhook Messages

Merchant administrators can now view and resend failed messages using the Admin UI. (Previously, this capability was available via API only.) Includes ability to:

  • View a list of event web hook messages that have failed to reach their destination after a maximum of five attempts.
  • View additional failure information, such as the error message and failed target URLs.
  • Resend failed messages (allows for five more attempts).
  • Ability to permanently delete failed messages.

Steps to Enable

No steps are required to enable this feature.

Retry Functional Webhook Failures

Allows for the ability to retry functional web hook failures where a failure is defined as any response other than 2xx (e.g. 200 OK), as well as the ability to configure the number of retries for each web hook or disable retry altogether. This is useful in instances where there are intermittent connection failures and a retry is necessary.

Retry is currently supported for the following functional web hooks: Shipping Calculator, External Tax Calculation, Catalog and Price Group Assignment, Order Approvals, Return Request Validation

NOTE: There is a one minute time limit to complete retry attempts.

Steps to Enable

No steps are required to enable this feature.

Payments

Add Card to Profile

Shoppers can now add a saved credit card to their profile without having to place an order. Once saved, this card can be used as the payment method for future orders. 

To implement this feature:

  • Update storefront widgets: Enable shopper to enter new credit card information
  • Invoke new SF endpoint to save the card: The storefront endpoint will trigger the generic payment webhook with action to tokenize the card.
  • Update the generic payment webhook service: The service will receive the tokenization request and return the reusable token (Validate the card as recommended by gateway).

Steps to Enable

No steps are required to enable this feature.

Experience and Design

Preview Enhancements

In Design Studio, customers that are using specific layouts or targeting content to specific Audiences can now preview the shopper experience for a specific audience or combination of audiences without having to test on a test site and set up Shopper profiles that correlate to a specific audience rule. 

For instances where multiple Audiences are applied, Preview applies the same log as the storefront would, to ensure that the correct content is being previewed and the experience matches what a shopper would see in production.

Also now includes the ability to preview by viewport. When a viewport is applied, the preview window is resized to give a better indication as to how the storefront would look.

Steps to Enable

No steps are required to enable this feature.

Search Admin

Dynamic Curation Preview

It is now possible to preview a rule that has a read-only, complex "destination,” allowing merchants to preview the effects of rules created via API for “destinations” other than a product collection or search terms. 

NOTE: If you preview a rule with multiple “OR” clauses, you are taken to the destination described in the first clause.

Two other smaller enhancements have been made:

  1. Merchants can no longer select the same product for both Boost and Bury to avoid the confusion that could result when the same product was mistakenly selected to be both boosted and buried. If a product has been boosted after it has already been chosen to be buried, the product is simply boosted (and vice versa).
  1. An informational message is now displayed if more than 500 rules have been configured for search terms. For text searches, Searchable Field Ranking is applied first, then Dynamic Curation, so it’s best to configure Searchable Field Ranking to return the most relevant results first, then refine your ordering in special cases with Dynamic Curation, which serves as a tie-breaker. 

Steps to Enable

No steps are required to enable this feature.

Update 19A

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
04 MAR 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Commerce Cloud 19A 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 19A Update in the body or title of the email.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Major New Features

Storefront

Buy Online, Pick-Up in Store

Payments

Stored Credit Cards

Search Admin

Boost and Bury

Facet Ordering

Integrations

Content and Experience Cloud: New "Channel" to Site Mapping

Content and Experience Cloud: New Content Listing Widget

Content and Experience Cloud: New Content Item Layout

Content and Experience Cloud: API for CMS Integrations

Additional New Features and Other Changes

Browser Support, Language, and Currency Support

Browser Support

Language and Currency Support

Agent Console

Agent Console Customization

B2B

B2C to B2B Profile Conversion

Publishing

Publishing of Individual Design Assets

Experience and Design

DCU - Stack and Element Support

DCU: CCProxy Substitution

HTML Snapshots: Mobile Support

Search

Type-Ahead Framework

Audiences and Personalization

UTM Query Parameters

Recommendations

Collection Override

Experiments

Custom Goals for Widget Experiments

New Goal Type: Commerce Events

Major New Features

The 19A update of Oracle Commerce Cloud includes substantive improvements and changes to the product.

What follows is a brief summary. For more details about each feature and improvement, please review the What’s New 19A document and the official Oracle Commerce Cloud documentation in the Oracle Cloud Help Center.

The major new features released in Oracle Commerce Cloud 19A include:

Storefront

Buy Online, Pick-Up in Store

We now support Buy Online, Pick-Up in Store (BOPIS) via API and out-of-the-box Storefront widgets. Allows a shopper to order online and choose a store location to pick up the order from. Payment can be done online or in-store. Includes an "online-only" flag for products and SKUs to differentiate items that can be picked up in-store from those that cannot. Also includes API support to associate sites with lists of store locations, as well as distinguish store locations that are inventory locations from ones that are pickup locations.

This feature provides a mechanism to capture BOPIS-specific data, including pickup location, inventory location, contact details of the person picking up the order, available pickup dates and time, and shopper preferred pickup dates and times. Admin API and webhooks have been updated to support all BOPIS data.

New widgets and widget versions have been created to accommodate BOPIS as well, including new versions of the Product Details widget with a new "in-store pickup" element, Shopping Cart widget that includes support for a mixed cart model, meaning a cart can have items delivered to a home address and also in-store pickup, Checkout Order Summary widget that displays a list of shipping groups (e.g. home delivery, pickup in-store), Payments widget with ability to pay for in-store pickups in-store or online, Order Confirmation and Order Details widgets that display all BOPIS-related details, as well as a brand new Shipping Options widget which supports split shipping, new BOPIS-related emails (i.e. Goods ready for pickup, Goods have been picked up confirmation), and out-of-the-box staged checkout layout specially designed for this feature. A new "pay in store" payment group type has also been added to support the "in-store pickup" option.

NOTE: For externally configurable SKUs (CPQ), shoppers will not be able to check store availability until they add the configured item to the cart.

Steps to Enable

No steps are required to enable this feature.

Payments

Stored Credit Cards

We now support the ability for registered shoppers to save cards and pay for orders (including scheduled orders) using their saved cards, enabling faster and easier checkout to increase conversion. Shoppers can indicate that they wish to save a credit card during checkout and that card will be saved following a successful authorization. At that time, a reusable card token will be returned and saved in Oracle Commerce Cloud. In addition to being able to save cards to pay for future orders, registered shoppers can also set a default card, add or change the nickname for a saved card, and delete a card. It's also possible to associate a billing address with a saved cart, so the shopper does not have to enter it.

When stored cards are being used to pay for scheduled orders, a configuration option allows these orders to be processed without a CVV (since CVV cannot be stored and the shopper is not present to enter CVV for scheduled orders). In case of a payment failure, the order will be placed in a pending payment state and the shopper can return and correct errors to complete the payment. Stored cards can also be used to pay for orders that require approval. 

Cards are stored on a per gateway basis, particularly important for merchants running multiple sites, since different sites may use different gateways.

NOTE: This feature is available via API for card payments processed using the Generic Payment Framework in Oracle Commerce Cloud and is not available for out-of-the-box payment gateways. Does not currently support ability to store a card without first placing an order.

Steps to Enable

Deployment Steps:

  • Configure payment options for each gateway, such as whether to require CVV for live shopper orders and scheduled orders.
  • Create a new storefront account widget to display and manage saved cards.
  • Customize storefront split payment widget to allow paying with a stored card.
  • Update the payment gateway integration to support returning reusable token as needed:
    • If the gateway integration previously returned a non-reusable token, then it must be updated to return a reusable token suitable for storage/reuse based on a flag included in the authorization request that specifies whether the shopper has chosen to store the card post authorization).
  • Customize agent app to enable agent to place orders using stored cards on shoppers behalf.

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

Search Admin

Boost and Bury

This is a new enhancement to Dynamic Curation which allows a merchandiser to select and rate criteria to influence the ordering of a product listing that appears when a shopper enters specific search terms or navigates to a search-driven collection page.

In addition to (or instead of) specifying criteria to influence the ordering, merchandisers can now manually curate product listings to promote or "boost" specific products to the top of search results and/or "bury" products at the bottom. Merchandisers can also use this feature to better control which products appear "above the fold" -- useful, for example, to boost products to the top of relevant pages when running an advertising campaign. This rule can be applied to specific search terms or to a search-driven collection page. The results can be previewed in the Oracle Commerce Cloud Admin to verify the results before putting into production.

Steps to Enable

No steps are required to enable this feature.

Facet Ordering

Allows merchandisers to select and order facets that appear in Guided Navigation when a shopper enters specific search terms or navigates to a collection page, so that facets can be displayed in an order that reflects common shopping behaviors. Facet ordering can be done based on what will be most useful for shoppers and allows merchandisers to control the simplicity and granularity of the navigation menu for different collections. Merchants with a large number of facets may want to use this feature to limit and curate which facets appear in specific situations, both for performance reasons and to present a cleaner, simpler, more effective experience for shoppers. 

Merchandisers can define a default rule that applies where a specific rule hasn't already been defined. This rule can be applied to specific terms or to a collection page. Results can be previewed in the OCC Admin before publishing.

Steps to Enable

No steps are required to enable this feature.

Integrations

Content and Experience Cloud: New "Channel" to Site Mapping

Customers using Oracle Commerce Cloud (OCC) and Oracle Content and Experience Cloud (CEC) can now map different publishing channels from Oracle CEC to sites in OCC allowing the ability to target unique content for each site. Merchants can set up a channel for each OCC site in Oracle Content and Experience Cloud and map each channel ID and token to sites in the OCC integration settings.

Steps to Enable

To enable this feature you need to log a Service Request (SR).

Content and Experience Cloud: New Content Listing Widget

Supports creation of individual listings for each "type" of content in Oracle Content and Experience Cloud (CEC), allowing merchants to create a blog site or index a group of supporting or guidance content and easily manage that noncatalog content through Oracle CEC and present it in the Oracle Commerce Cloud site and shopping experience. 

NOTE: When using the content item widget with the content item layout, you don’t need to select a content item as the page is dynamically created for each relevant content item.

Steps to Enable

To enable this feature you need to log a Service Request (SR).

Content and Experience Cloud: New Content Item Layout

Similar to the concept of a product details layout, but for content, this feature allows a page for a content item in a configured channel to be created when there is an integration in place between Oracle Commerce Cloud and Oracle Content and Experience Cloud. Each content item is added to the sitemap and linked where a merchant has set up content lists for that content type.

Allows merchants to create a site with multiple types of content and add a page for each content item to a page map. Also allows for mapping "channels" to different sites in the Admin settings. Creates a unique page for each content item and links from the sitemap and relevant content listings. When using a content item widget with a content item layout, you don't need to select a content item, as the page is dynamically created for each relevant content item.

NOTE: This type of layout does not yet support multiple viewports.

Steps to Enable

To enable this feature you need to log a Service Request (SR).

Content and Experience Cloud: API for CMS Integrations

Primarily built to connect Oracle Content and Experience Cloud to Oracle Commerce Cloud. New Content Map Methods and Channel Map Methods are endpoints for operations that are now available. These APIs can be used to create a site with multiple types of content and add a page for each content item to a page map. Merchants can also now map "channels" to different sites in the Admin settings.

NOTE: These APIs can also be used to connect OCC with another CMS. Out of the box, we've provided support for notifications from Oracle Content and Experience Cloud to OCC, but if integrating with another CMS, merchants will need to build a notification extension or poll for new content.

Steps to Enable

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

Additional New Features and Other Changes

There are also a number of additional new features, changes, and improvements included in Oracle Commerce Cloud 19A. By functional area, these include:

Browser Support, Language, and Currency Support

Browser Support

Browser support is up-to-date.  

Steps to Enable

No steps are required to enable this feature.

Language and Currency Support

Languages: Four new languages added--all Storefront only: Catalan - ca, Vietnamese - vi, Malay - ms, and Indonesian - id

Forty languages are currently supported: Arabic (ar) (Storefront only), Bulgarian (bg), Catalan - ca (Storefront only), Chinese—Simplified (zh_CN), Chinese—Traditional (zh_TW), Croatian (hr), Czech (cs), Danish (da), Dutch (nl), English (en), English-GB (en-GB), Estonian (et), Finnish (fi), French (fr), French Canadian (fr_CA), German (de), Greek (el), Hungarian (hu), Indonesian - id (Storefront only), Italian (it), Japanese (ja), Korean (ko), Latvian (lv), Malay - ms (Storefront only), Norwegian (no), Polish (pl), Portuguese—Brazil (pt_BR), Portuguese—Portugal (pt_PT), Romanian (ro), Russian (ru), Serbian - Cyrillic (sr), Serbian – Latin (sr_Latn),,Slovenian (sl), Spanish (es), Swedish (sv), Thai (th), Turkish (tr), Ukrainian (uk), and Vietnamese - vi (Storefront only).

Currencies: No new currencies are supported.

Sixty-one currencies are currently supported:  AED (UAE Dirham), ARS (Argentine Peso), AUD (Australian Dollar), BGN (Bulgarian Lev), BOB (Boliviano), BRL (Brazilian Real),  CAD (Canadian Dollar), CHF (Swiss Franc), CLP (Chilean Peso), CNY (Chinese Yuan Renminbi), COP (Colombian Peso), CRC (Costa Rican Colon), CZK (Czech Koruna), DKK (Danish Krone), DOP (Dominican Peso), DZD (Algerian Dinar), EGP (Egyptian Pound), EUR (Euro), GBP (British Pound Sterling), GTQ (Guatemalan Quetzal), HKD (Hong Kong Dollar), HNL (Lempira), HRK (Croatian Kuna), HUF (Hungarian Forint), IDR (Indonesian Rupiah), INR (Indian Rupee), JPY (Japanese Yen), KES (Kenyan Shilling), KRW (South Korean Won), KZT (Tenge), LBP (Lebanese Pound), MAD (Moroccan Dirham), MXN (Mexico Peso), MYR (Malaysian Ringgit), NGN (Naira), NIO (Cordoba Oro), NOK (Norwegian Krone), NZD (New Zealand Dollar), PAB (Panamanian Balboa), PEN (Peruvian Nuevo Sol), PHP (Philippine Peso), PKR (Pakistani Rupee), PLN (Polish Zloty), PYG (Paraguayan Guarani), QAR (Qatari Riyal), RON (Romanian Leu), RSD (Serbian Dinar), RUB (Russian Ruble), SAR (Saudi Riyal), SEK (Swedish Krona), SGD (Singapore Dollar), THB (Thai Baht), TJS (Somoni), TRY (Turkish Lira), TWD (New Taiwan Dollar), UAH (Ukrainian Hryvnia), USD (US Dollar), UYU (Uruguayan Peso), VND (Vietnamese Dong), XAF (CFA Franc BEAC), ZAR (South African Rand).

Steps to Enable

No steps are required to enable this feature.

Agent Console

Agent Console Customization

The Agent Console in Oracle Commerce Cloud can now be customized and extended by a merchant using the existing Design Studio framework (layouts and widgets), allowing customization of the user interface, so merchants can build their own user experience and screens for agents. All of these customizable pages or layouts for agents will contain either agent-specific widgets or even certain shareable storefront widgets, meaning that certain Storefront widgets are reusable on agent pages as well.

Includes drag and drop capability to build custom agent application. This includes all flows and pages, such as search pages, order, refund, and exchanges, and more--all now customizable.

Merchants can also now further extend the capabilities of the Agent Console and integrate with third party systems to provide a fuller customer experience.

Steps to Enable

No steps are required to enable this feature.

B2B

B2C to B2B Profile Conversion

Merchants can now perform a one-time bulk conversion of registered shoppers to account-based shoppers. B2C users can now be converted to B2B users--typically seen when an organization becomes a B2B account in a merchant's store and users should be able to act as buyers on the account. This is now achievable via API.

NOTE: Only the administrator can access the export and import APIs. Also, this supports a one-way B2C to B2B conversion only.

Steps to Enable

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

Publishing

Publishing of Individual Design Assets

Users can now select only the individual design assets they want to publish, as well as filter design assets by author, status, area, and publishing event name or find individual design items via search query. (Previously, all design assets had to be published together as a group.) 

Design assets, such as widgets and layouts, stacks, slots, text snippets, themes are all supported and appear as individual items in the publishing change list.

Dependencies are automatically determined and Oracle Commerce Cloud ensures appropriate items are published together. For example, if you delete a stack from a layout, the changes will be published together -- the stack is deleted and the layout is updated. Merchants have a chance to review dependencies before publishing.

Steps to Enable

No steps are required to enable this feature.

Experience and Design

DCU - Stack and Element Support

The Design Code Utility (DCU) tool now fully supports stacks, as well as global and widget-level elements. It now provides support for creation and transfer of all types of Design components used in Oracle Commerce Cloud.

Steps to Enable

No steps are required to enable this feature.

DCU: CCProxy Substitution

Developers using the Design Code Utility (DCU) can now speed up the loading of the storefront by limiting the file types that are intercepted by ccproxy. Includes ability to selectively enable/disable which types of design assets should be substituted in ccproxy as part of the Design preview. Developers can selectively use the handlers for Theme files and JavaScript files, for e.ample/

Steps to Enable

No steps are required to enable this feature.

HTML Snapshots: Mobile Support

We've now added support for mobile snapshot when using the adaptive design approach by adding a new endpoint that merchants can configure to determine which user agents will receive the mobile snapshot. When leveraging layouts with XS viewports and a mobile crawler is recognized, the mobile version will be returned. This means mobile crawlers will now receive the appropriate mobile HTML snapshot. Vary: User-Agent header is now in the snapshot response. Includes known Google mobile crawlers out of the box.

Steps to Enable

No steps are required to enable this feature.

Search

Type-Ahead Framework

We've added a new framework for providing alternative type-ahead experiences, presenting type-ahead results using keywords instead of presenting matching products in a list. This framework allows merchants to:

  • Upload JSON data that reflects the information they want to populate typeahead with.
  • Have this data be automatically indexed by search as part of the regular publish process or indexed via direct API call to the admin search index endpoint.
  • Use the existing assembler endpoint and any partial matches against the keyword.terms propertywill be returned--they will be ordered based on the value of keyword.searchCount.

Use: POST /gsdata/v1/cloud/data/keywords to upload keywords that you want to have appear in your type-ahead results, along with a rank.

Use: GET /ccstoreui/v1/assembler/pages/Default/keywords/typeahead?Ntk=typeahead&Ntt=characters to generate the new type-ahead response.

This can be integrated with a search analytics solution to populate type-ahead suggestions using most popular searches, for example. Can also be extended to include additional metadata, for example, presenting recommended products for each suggestion.

NOTE: This is a headless feature, so front-end code needs to be created separately.

Steps to Enable

No steps are required to enable this feature.

Audiences and Personalization

UTM Query Parameters

Merchants can now build audience rules using UTM query parameters which are commonly used to pass context from referring sites, pay per performance or social advertisements, and other campaigns. So for example, it is now possible to present appropriate content, promotions,, products, and/or experiments to shoppers based on an ad campaign or referrer. 

Allows merchants to keep a consistent look and feel from external campaigns through to the website experience. Also enables merchants to automatically apply promotions for shoppers visiting from a referring source or with a specific external search term. 

NOTE: Audience rule size estimates are not available for audience rules built against UTM parameters. And it is only possible to build details against the UTM query parameters from a shopper's current visit.

Steps to Enable

No steps are required to enable this feature.

Recommendations

Collection Override

This feature allows merchants to specify that a recommendation set should always show products from a specified collection(s), in the case where there is no product context (e.g. marketing landing page). Also allows merchants to specify the collection of products that should be shown in a content variation slot associated with a particular audience.

NOTE: To enable, merchandisers will need to enter the ID of a collection (found within the catalog) in the widget configuration, rather than selecting from a dropdown.

Steps to Enable

No steps are required to enable this feature.

Experiments

Custom Goals for Widget Experiments

Allows merchants to track Pageview custom goals for widget-based experiments. These were previously limited to tracking of out-of-the-box commerce metrics only.

The custom goals may be added and managed via either the new Goal Tab on the Experiment slot within Design Studio or the existing Goal Tab within the Experiments configuration screen. May also select Primary Goal from within the Experiment slot.

Results are displayed in the same manner as custom goals for Layout and URL-based Experiments.

Steps to Enable

No steps are required to enable this feature.

New Goal Type: Commerce Events

A new custom goal type called "Commerce Events" is now available for all types of experiments. Allows merchants to track events as custom goals. These include out of the box commerce events (a refined list of approximately 50 pubsub events), as well as custom events (any event defined by the merchant). These events are tracked in the same way as commerce metrics and removes limitations on what can be tracked as a goal for an experiment. 

The list of Custom Events is maintained, so that users do not have to repeatedly key it in. These events are also included in type-ahead search. Similar to other goal types, Commerce Events may be added and managed within either the Experiments Slot or Experiments application itself. May be selected as an Experiment's Primary Goal. Results are displayed in the same manner as per custom goals for Layout and URL-based experiments.

Steps to Enable

No steps are required to enable this feature.

---