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


  1. UPDATE 21C REVISION 12
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Commerce
    1. Admin
        1. Page Tags
    2. Integrations
        1. Integration with Oracle Content Management (OSF)
  1. UPDATE 21C REVISION 4
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Commerce
    1. Open Storefront Framework
        1. OSF Account-Based Shopping - Unbranded Reference Store
  1. UPDATE 21C REVISION 3
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Commerce
    1. Recommendations
        1. B2B Account-Wide Recommendations
  1. UPDATE 21C REVISION 2
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Commerce
    1. Integrations
        1. Punchout Enhancements
  1. Update 21C
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Commerce
    1. Multisite
        1. Multisite Cart
    2. Integrations
        1. Shipping Method Update - External ID Property (API only)
    3. Promotions
        1. Shipping Method Internal Name Property Exposed in Admin UI
        2. Promotions Advanced Filters
    4. Experience and Design
        1. Preview by Date and Time
    5. Open Storefront Framework
        1. Open Storefront Framework (OSF) Configure-Price Components
    6. Publishing
        1. Worksets
    7. Storefront and Agent
        1. Custom Properties on Purchase List Line Items (API Only)

Update 21C 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
06 OCT 2021     Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

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.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Commerce

Admin

Page Tags

Integrations

Integration with Oracle Content Management (OSF)

Commerce

Admin

Page Tags

With this release, Oracle Commerce customers can now easily add new plug-in services, both Oracle and 3rd party, to their storefront using page tags.  Examples of plug-in services include analytics, chat services, and A/B testing.

This feature provides a centralized area in our Commerce Administration UI to both add and manage the pages tag for a site.  Previously, this required that a developer make code changes to the storefront to add these page tags.

Key benefits

    • Centralized control of page tags running on a site.
    • Basic validation of script tag syntax for tags added.

Capability highlights

    • Add Javascript page tag to the <head>, top of <body>, or end of <body> sections.
    • Re-order the page tags for each section.
    • Enable/disable and delete tags.

Example use case

If you want to be able to use Oracle Maxymiser for A/B testing, you can generate a page tag within Maxymiser and use the Page Tags UI in Commerce Administration UI to paste this tag in and add it to the <head> section of your site.

This feature enables tags to be loaded in the head section prior to anything else, including adding the Oracle Maxymiser page to your Oracle Commerce site to perform A/B testing.

Steps to Enable

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

Integrations

Integration with Oracle Content Management (OSF)

This Oracle Commerce integration update with Oracle Content Management now allows you to create and maintain the appearance of content pages within Design Studio using our new content item container and content field widgets.

NOTE: This integration applies only to sites using Open Storefront Framework (OSF).

Capability highlights

Improve Search Engine Results Pages (SERPS) with dynamic meta fields in the Content layout template:

  • Select a content field to be used for page title.
  • Add other meta fields and map to fields in Oracle Content Management.

Display targeted, more relevant content on a page with a query-driven content listing widget.

  • Display relevant content listings by adding a search query to the content listing widget.
  • More flexibility in content types – now you can use a generic content type, such as a blog homepage, with all blogs listed or independently posted category listings, as well as target relevant blog posts using a keyword in the query, such as a brand name.
  • You can combine queries and choose “all” or “any.”

Use the new content item container and content field widgets

  • A widget is now a container in OSF with new content field widgets that can be added and arranged on a layout in Design Studio with three new widgets:
    • Content Text
    • Content Data
    • Content Image
  • Business user can map Oracle Content Management fields to common SEO meta tags and add additional ones into the headers from the content layout.
  • Business users can select and arrange Oracle Content Management display fields in a template.

Enrich product detail pages with the new “product aware” mode for the content item widget:

  • Bring in relevant content associated with the product ID.
  • Configure product ID field from the content type.

Key benefits

Richer customer experience:

  • Enrich products with additional content, media, and documentation using the new product mode for the content item widget.
  • Display relevant content to the page context with the new query-based content listing widget.
  • Improve search engine results pages with dynamic metadata.

More efficient content creation:

  • You can reuse the same content types in different combinations with the query-based content listing widget.
  • Create content that can be reused in different display contexts by using content field mapping to display the relevant content fields for the context.

Faster implementation:

  • Implement and configure the integration entirely through the Commerce Administration UI.

Example use case

As a content writer or merchandiser, you want additional content for product detail pages to automatically display any additional content published relating to the product id of that product listing.

How to use:

    1. Create a content type in Oracle Content Management with a field you will use as Product ID.
    2. Add the content item widget to your product detail page template and select the content type and content field you want to use for product ID to link the relevant content to the product page.

This update provides a richer customer experience, more efficient content creation, and a faster implementation allowing users to configure the integration entirely through the Commerce Administration UI.

Steps to Enable

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

Tips And Considerations

  • You'll need an Oracle Content Management account and connect to it in the Oracle Integrations section of the Commerce Admin UI 
  • You can use queries on the content listing widget to target different content within the same content type and create multiple unique listing pages using the same content.
  • You can create search metadata fields in Oracle Content Management, so new articles map these fields in the content layout, and the blog pages have full metadata.

Update 21C Revision 4

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
12 AUG 2021 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 21C (Revision 4) in the body or title of the email.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Commerce

Open Storefront Framework

OSF Account-Based Shopping - Unbranded Reference Store

Commerce

Open Storefront Framework

OSF Account-Based Shopping - Unbranded Reference Store

With this release, Commerce is introducing an unbranded reference store that provides a starting point to help accelerate Open Storefront Framework (OSF) deployments.  Leveraging best practices, the reference store includes a starter store for account-based shopping flows in addition to a ” blank” starter store.

The reference store template includes a large library of React-based page components (widgets), across a wide variety of Commerce functionality.

Capability highlights

  • OSF reference storefront application is built using ReactJS and leverages the core technologies of HTML, CSS and JavaScript
  • Supports responsive design for mobile and desktop
  • Fully featured platform with drag and drop experience tools
  • UI layer provides a clean separation between presentation layer and state model
  • Features available as part of the account-based store:
      • Account/contact self-registration
      • Login for account-based commerce
      • Purchase list and sharing of purchase list
      • Scheduled orders
      • Quick order and copy order
      • Order capture (volume pricing, account specific shipping and payments, invoice payments)
      • Order approvals
      • Manage account-level addresses and inherited addresses in profile and checkout

List of OSF Account-Based Shopping Widgets 

Developers and implementers can deliver a faster, more responsive and richer user-experience; allowing the focus to be on the last mile to deliver their unique experience.

Steps to Enable

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

Tips And Considerations

Account-based-commerce-reference-store has been added to the list of application template options in the command-line interface (CLI).

Update 21C 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
30 JUL 2021 Created initial document.

Overview

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

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Commerce

Recommendations

B2B Account-Wide Recommendations

Commerce

Recommendations

B2B Account-Wide Recommendations

With this release, Oracle Commerce’s machine learning-driven recommendations engine now uses account-wide relationships to drive recommendations to buyers.  The behavior of all contacts within a B2B account is considered.  While recommendations continue to be generated for an individual buyer, the system also factors in key information on other buyers within the same account.

Capability highlights

  • Shared account behavior ensures that buyers now see relevant recommendations based on interaction from all buyers across an account.
  • Decision science determines commonality between buyers in the same account and uses this information to enhance recommendations.
  • Works in harmony with AI Recommendation Strategies and Exclusions, released in Oracle Commerce 21A revision 3.

Use case example

In many of your accounts, buyers within the same account are viewing and purchasing the same products. To enhance the quality of recommendations, the machine learning engine aggregates information on related purchases and customer behavior to optimize the quality and breadth of products being recommended.

Shared account behavior ensures that buyers now see relevant recommendations based on interaction from all buyers across an account.

Steps to Enable

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

Tips And Considerations

  • This feature applies to B2B customers only.
  • This feature is automatically enabled.  As a result, any existing recommendations will automatically be upgraded.

Update 21C Revision 2

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
30 JUL 2021 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 21C (Revision 2) in the body or title of the email.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Commerce

Integrations

Punchout Enhancements

Commerce

Integrations

Punchout Enhancements

With this Commerce release, enhancements to punchout make it quicker and easier to integrate punchout capabilities with key purchasing systems, such as Oracle EBS or Fusion procurement systems.

Capability highlights

  • New Admin APIs (available on storefront via /ccapp) to cache objects against an auto-generated key.  Can be used as a session ID for punchout flow with OAuth token.
  • Updated server-side extensions (SSE) to:
      • Use above endpoint to cache OAuth token and session id.
      • Provide new redirect endpoint to be returned to ERP. This endpoint picks up OAuth token from the Commerce cache before redirecting the user to Commerce home page.

This following information describes the APIs and endpoints used for this enhancement.

  1. Created a new Admin endpoint available on Store server at /ccapp context, which can cache any object against an auto-generated key. The key can be used as a session id in the punchout flow. The cache is stored in coherence cache.
  2. Updated punchout server-side extension (SSE) to:
      • Call the above Admin endpoint to cache the OAuth token and add the session id to the URL returned to ERP as part of punchout setup response.
      • Use a newly created endpoint which redirects the browser to Commerce home page with OAuth token. This endpoint is returned to ERP instead of Commerce home page in the URL in punchout setup response. 
      • Handle the same in re-punchout flow.

Example use case:

Oracle’s B2B Commerce merchant customers want to allow their end consumer to integrate their EBS procurement system with the merchant.  Integration is now simpler and requires fewer changes in EBS to implement.

  • Improves existing punchout capabilities to reduce effort to integrate with key purchasing systems, such as Oracle EBS.

Steps to Enable

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

Tips And Considerations

  • This enhancement requires existing customers to use new SSEs and update their existing punchout integration to use these new capabilities.
  • The punchout enhancement focuses on Oracle EBS and Fusion applications as examples of external systems and does not assert to be an EBS integration or integration with any other procurement system.   

Update 21C

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
13 JUL 2021 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 21C in the body or title of the email.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Commerce

Multisite

Multisite Cart

Integrations

Shipping Method Update - External ID Property (API only)

Promotions

Shipping Method Internal Name Property Exposed in Admin UI

Promotions Advanced Filters

Experience and Design

Preview by Date and Time

Open Storefront Framework

Open Storefront Framework (OSF) Configure-Price Components

Publishing

Worksets

Storefront and Agent

Custom Properties on Purchase List Line Items (API Only)

Commerce

Multisite

Multisite Cart

The release of the Commerce Multisite Cart feature enables customers to implement a shared cart strategy across their sites, providing a single seamless cart experience across multiple sites.

For merchants with multiple sites, a merchant can use the feature to share the shopping cart, allowing a shopper to have a single shopping cart across sites. This means that shoppers can add products from multiple sites into a single cart and purchase all products in the same order using a single set of shopper credentials (login name and password).

NOTE: Customers who want to use Multisite Cart must have a storefront built on Open Storefront Framework (OSF).

Capability Highlights

  • Customers managing multiple sites in a single environment can set up a site group that is configured for cart sharing.
  • Applicable for both B2C and B2B customers
  • Supports site-specific promotions, as well as promotions that apply to sites that share a cart.
  • Agent Console can be customized via API to support Multisite Cart.
  • An administrator can easily set up and manage a shared cart via API.

SiteGroups API

Use the siteGroups API to create a site group and configure it for cart sharing by setting the following properties.

  • displayName: name of the site group
  • ID: a unique identifier (can be specified; if left null, is auto-generated)
  • sites: a list of sites that are included in the group
  • sharedCart: set to true to indicate that this site group is to be used for cart sharing

Once the site group is set up, the cart will be shared across the sites. 

Multisite cart with Items from Multiple Sites

As the shopper changes sites, items can be added to the cart, building one order with items from the different sites. Checkout is done on one site

Orders for Multisite Carts

  • When a shopper checks out the shared cart, the order is associated with that checkout site.
  • When a shopper views Order History from any site that shares the cart, the shopper will see all orders from all sites in the group.
  • The order is associated with the checkout site, but the revenue is allocated across the sites from which items were added to the cart.
  • For personalization purposes, the Lifetime Spend and Lifetime Average Order value is distributed across the sites.

Enables customers managing multiple sites in a single instance of Oracle Commerce to implement a shared cart strategy.

Steps to Enable

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

Tips And Considerations

Multisite Cart is not supported on Storefront Classic. Customers who want to use Multisite Cart must build their storefronts using Open Storefront Framework (OSF).

Wish lists not yet supported for Multisite Cart.

Integrations

Shipping Method Update - External ID Property (API only)

With this new enhancement, you can now store an ID generated from a third-party shipping system allowing you to map shipping methods easily across systems.

Capability Highlights

  • Allows users to store the ID from an external shipping system on a Commerce shipping method.
  • External ID is included in the shipping method information in the external shipping webhook and added to docShippingAdminEndpoints swagger.

Including an external ID as another identifier to an existing shipping method contributes to a more efficient shipping process.

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

This feature is API only and available via admin/shippingMethods.  The property cannot be set via the Settings > Shipping Methods UI and is, therefore, not displayed in the UI.

Promotions

Shipping Method Internal Name Property Exposed in Admin UI

The Shipping Method Internal Name Property API feature was delivered in Oracle Commerce 21A revision 11.  This update allows you to create an identifier on shipping methods that is hidden from shoppers, using the Commerce Administration UI.

The internal ID allows merchants to have multiple shipping methods with the same display name for shoppers but be able to distinguish between internally when managing promotions.

Capability highlights

  • Makes it easier for users to identify the correct shipping methods to add to shipping promotions.
  • Users can create multiple shipping methods with the same display name on the storefront to be used in different contexts (e.g. you may want to display "Ground Shipping" to shoppers for two different shipping methods, one on the U.S. site and one on the Canadian site).
  • Internal names automatically are displayed in the Shipping Method editor in Shipping Discount promotions editor.

Example use case

  • When creating shipping promotions, you can easily differentiate shipping methods although they have the same external display name.

Makes it easier for users to identify the correct shipping methods to add to shipping promotions.

Steps to Enable

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

Tips And Considerations

The API for this feature is available via admin/shippingMethods

Promotions Advanced Filters

With this new Oracle Commerce feature, you can create custom behavior for individual promotions when the out of the box behavior does not meet your requirements.  For example, you can control how promotions are applied at a more granular level and override default behavior regarding how promotions are combined.

Capability highlights:

  • Allow items in a cart to receive more than one item discount.
  • Specify whether items that are qualifiers for a promotion can be targets for a different promotion.
  • Specify whether items can be qualifiers for more than one condition.
  • Control whether items already on sale can receive a promotion.

New Advanced Tab on Promotions Editor in Admin UI

Use Case Example:

You want to give an extra 10% off items in the Clearance category and ensure that the promotion applies if:

  • An item was already used as a qualifier for another promotion
  • An item has already been discounted by another item promotion

You then create the promotion “Extra 10% off Clearance” and set the priority so that it will be evaluated after other promotions.

Use the advanced Offer Filters to set:

  • Include qualified items – any items that were a qualifier for a promotion can still receive the Clearance promotion
  • Include discounted items (any promotion) – any items that were discounted by another promotion can receive the Clearance promotion.

Based on the advanced filters set, the Clearance promotion was applied to the already discounted Wine Glass and the Shoulder Bag as a qualifier for another promotion.

Ability to fine-tune promotion eligibility based on what’s in a shopper’s cart. This enhances the customer experience and brand loyalty.

Steps to Enable

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

Tips And Considerations

This feature is available on promotions in the Admin UI and through the ccadmin/v1promotions endpoints: createPromotion, getPromotion, updatePromotion.

Experience and Design

Preview by Date and Time

This Commerce update introduces an enhancement to the Preview functionality providing a convenient method for previewing future content changes. Prior to this update, you could vary store content and catalog assets by date and time, however, preview only worked on current server time. You can now apply a date and time filter in Preview and view pages as they will be on the designated future date and time.

Capability Highlights

  • This filter can be combined with other filters in Preview such as the Audience and Viewport filters.
  • The date and time filter allow you to view the following types of content:
    • Promotions and promotional content scheduled for a future date and time
    • Widgets configured in slots against a future date and time

Use Case Example:

Configure content variation slots with date and time variations and/or create promotions that apply to a future date and time.

Allows users to apply a date and time filter in Preview and view those date-sensitive changes.

Steps to Enable

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

Tips And Considerations

The only objects that can currently be scheduled for future date and time are slots and promotions.

Open Storefront Framework

Open Storefront Framework (OSF) Configure-Price Components

This Oracle Commerce Open Storefront Framework (OSF) update provides a set of out-of-the-box components used to integrate with Oracle Configure Price Quote (CPQ) in price and configure scenarios.

Capability Highlights

  • Support in OSF JS API to interface with the Commerce Server-Side Extension (SSE) that handles orchestration with CPQ Rest API.
  • Configure widget for placement on Product Detail Page (PDP) to open configuration dialog.
  • Provides UI components for common configuration types:
    • Includes selector types - radio buttons, drop-downs, toggles, date/time picker
    • Support for CPQ array set selections in a table
  • Displays updated pricing based on configuration selections.
  • Ability to add configured product to the cart.
  • Ability to edit configured product from the cart.

Example Use Case

The following image shows a laptop configuration, a characteristic illustration when describing the integration with Oracle CPQ in price and configure scenarios.

The out-of-the-box components for CPQ configure-price scenarios combined with JS API support in OSF provide a solid foundation for OSF implementations, enabling customers to execute configuration of complex customizable products.

Steps to Enable

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

Publishing

Worksets

This Commerce update introduces a significant enhancement to the publishing functionality with the release of worksets.  Worksets are a new way to selectively publish and are designed to provide teams with tools for better collaboration and visibility.

A workset is a container for teams to manage and share their work, allowing you to group items as you create, edit, or delete. You publish the workset instead of selecting items from a large list of changes, providing a more efficient publishing process.

Capability Highlights

    • Provides visibility into work in progress and any changes made by other users to same items in other worksets.
    • Groups changes for publishing as users are working.
    • Allows publishing users to easily track and select groups of changes to publish.

General Worksets Concepts

Worksets are a new way to selectively publish.

  • All users work in the context of a workset.
  • Users publish worksets, instead of selecting items to publish from one list.
  • Only users with publishing privileges can create worksets.
  • Only users with publishing privileges can publish schedule and publish worksets.
  • All users have access to all worksets and can switch between them.

New Workset Concepts for all Users

Changes Tracker

  • Users make changes in the context of a workset.
  • Users know which workset they are always working in.
  • Users know when others have contributed to the workset.
  • On login, users are returned to their last open workset or the default workset.

One List of Changes per Workset

  • Access workset list of changes through the tracker on the left navigation menu.
  • List of changes shows all the items that will be published together with the workset. 
  • Tracker shows other users who have contributed to the workset. 

Switching Worksets

  • Easily switch between worksets from the list of changes.
  • See most recently used worksets.

Workset Membership Displayed on Asset Editors

  • Users can see if an item is in more than one workset.
  • The first workset to publish will push all changes to the item on the storefront.

New Workset Concepts for Users with Publishing Privileges

Select Worksets Instead of Individual Items to Publish

  • Publishing users now select a workset to publish, instead of selecting items from a large list.
  • Users can move items from one workset to another if they are not ready to be published.
  • There is still a dependency review before scheduling or publishing a workset.

Creating worksets

  • Worksets are created on the publishing schedule page.
  • Workset names follow a #tag naming convention.
  • Full publish can still be scheduled.

Additional Important Information about Worksets

Upgrade to 21.2.12

  •  
  • When you upgrade and log in, you will be put in the #default workset context.
  • Any items that are already in your publishing queue before you upgrade will be put into the #default workset.

#default workset:

  •  
  • There’s always a #default workset. When it is published, another empty #default workset is created.
  • All changes made via API will be in a workset. If no workset is specified, they will go into the #default workset.

Workset behavior:

  •  
  • A workset must contain at least one item in order to be scheduled.
  • Only users with publishing privileges can schedule worksets.
  • Worksets do not persist after publishing.

Publish all:

  •  
  • You can still publish all active changes by scheduling a Full Publish on the publishing schedule. This will publish all changes in all worksets.

Relevant APIs for Worksets include:

  • listWorksets
  • getWorkset
  • createWorkset
  • updateWorkset
  • deleteWorkset
  • getPublishingWorksetDependencies
  • assignPublishingChangeList
  • publishingChangeAuthors
  • publishChangeLists

By making the publishing process more efficient, worksets allows storefront changes to be made in a more opportune manner.  This greatly benefits both publishing teams and shoppers.

Steps to Enable

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

Tips And Considerations

  • Create project or team-specific worksets to group changes more efficiently
  • Worksets do not provide change isolation. Dependencies can still exist and affect what gets published together.

Storefront and Agent

Custom Properties on Purchase List Line Items (API Only)

With this release, Commerce is introducing custom properties on purchase list line items, supporting purchase lists as a vehicle for collaborative buying where multiple contacts in an account need to view and group purchase lists.

You can add procurement-related properties to purchase list line items, allowing requisitioners to provide critical information to buyers and suppliers. Examples of such properties include notes for the buyer, notes for the supplier, budget date, charge account, funds status, and project to be charged.

NOTE: This feature is API only.

Capability Highlights

  • You can create, update, and delete custom properties on purchase list line items.
  • As a requisitioner, you can fill in the properties on purchase list line items, communicating requirements to the buyer and potentially to the fulfillment system.

This feature is API-only with the following APIs provided:

  • Admin APIs for creating, updating, and deleting a custom property on purchase list line items
  • Admin, Storefront, and Agent APIs for getting information about the attributes of the property
  • Storefront and Agent APIs for updating the value of the property on a line item

To use this feature:

  1. Use an Admin API to create the properties needed.
  2. Customize the purchase list widget to display the properties.
  3. If desired, create corresponding custom properties on order line items, and customize the widget code that copies a purchase list item to a cart to copy the values of the custom properties.

Once this is done, all those with edit access to a purchase list can fill in the properties on a purchase list line item, communicating the requisitioning requirements to the buyer.  If the values are copied to the order, the requirements can also be passed along to the fulfillment system.

With the capability to add procurement-related properties to purchase list line items, B2B business users can now support efficient collaboration between requisitioners, buyers, and suppliers.  This results in an enhanced customer experience for the shopper.

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

  • As part of the existing product functionality, you can create custom properties on the entire purchase list. The 21C Commerce product documentation includes these details.
  • As an API-only feature, there is no support for creating and managing custom properties on purchase list line items.
  • There is no out-of-the-box widget support for displaying custom properties on a purchase list line item. This can be achieved via customization.
  • There is no out-of-the-box support for copying the value of a custom property from a purchase list line item to the corresponding order line item when adding the item to a cart. 
  • This, also, can be achieved via customization.