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


  1. UPDATE 21D REVISION 8
  1. Revision History
  2. Overview
  3. Feature Summary
  4. B2B Commerce
    1. Admin
        1. Improvements to Access Control for Registered Applications (API only)
  1. UPDATE 21D REVISION 4
  1. Revision History
  2. Overview
  3. Feature Summary
  4. B2B Commerce
    1. Promotions
        1. Limit Use of Promotions with Coupons
  1. UPDATE 21D REVISION 2
  1. Revision History
  2. Overview
  3. Feature Summary
  4. B2B Commerce
    1. Integrations
        1. Integration with Oracle Unity
    2. Publishing
        1. Publishing: Save Conflicts
  1. Update 21D
  1. Revision History
  2. Overview
  3. Feature Summary
  4. B2B Commerce
    1. Open Storefront Framework
        1. OSF Account-Based Shopping - Unbranded Reference Store
    2. Recommendations
        1. B2B Account-Wide Recommendations
    3. Integrations
        1. Integration with Oracle Content Management (OSF)
        2. Punchout Enhancements
    4. Admin
        1. Page Tags

Update 21D Revision 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 Product Feature Notes
06 DEC 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*

B2B Commerce

Admin

Improvements to Access Control for Registered Applications (API only)

B2B Commerce

Admin

Improvements to Access Control for Registered Applications (API only)

This Commerce release introduces improvements to access control for registered external applications.

A registered application is an external application that is registered in the Settings > Web APIs > Registered Applications area of the Commerce Administration Interface (Admin UI). Registering automatically generates an application ID identifying the application internally and an application key used to authenticate the application.   Once authenticated, a registered application can access Commerce functionality via REST APIs.

With this release, there are now three types of registered applications:

  • Custom application
  • Commerce internal application
  • Commerce integration application

You can create, update, and delete custom applications –not the other types.

Capability highlights

  • You can use APIs to view and manage the set of roles assigned to a registered application.
  • You can restrict a registered application to accessing only specific endpoints (for a small, selected set of endpoints). 
  • Registered applications that are predefined and provided by Oracle are protected - you cannot update or delete them.
  • There are two new privileges introduced that provide backward compatibility.

With this release, the privileges within an application's roles are checked when the application tries to access Commerce functionality.  You now can control which roles are assigned to a registered application.  A set of "endpoint privileges" lets you restrict a registered application to access only specific endpoints.   Note:  An application cannot have a role containing the Administrator privilege.

New: Role management for registered applications

  • To assign a role containing the Administrator privilege to a registered application, you must add the Administrator privilege to a role that is assigned to a registered application. 
  • Managing an application’s roles is currently API-only functionality.
  • You can now use APIs to:
    • View the roles assigned to a registered application
    • Assign roles to a custom registered application 
    • Unassign roles from a custom registered application

Example use case:

To create the application "My Application" with a custom role whose ID is customRole1, you would POST to /ccadmin/v1/applicationIds as follows:

{

"name": "My Application",

"type": "application",

"roles": [ "customRole1"

]

}

New: Endpoint privileges

  • Endpoint privilege is a new type of privilege that confers access to a specific endpoint.
  • Like other privileges, cannot be given to a user or a registered application directly, only via a role.
  • Useful when a registered application needs to have access that is limited in a precise way to only certain specific endpoints.
  • If an endpoint has an associated endpoint privilege:
    • With the endpoint privilege, a user or registered application can access the endpoint - no other privilege is required.
    • Without the endpoint privilege, a user or registered application is subject to the usual access control rules.
      • If access to the endpoint requires a different privilege, the user or application needs that other privilege to gain access.
  • You cannot create an endpoint privilege.
  • You can add an endpoint privilege to a custom role, assign that role to a registered application, and remove other roles from the application, thereby limiting the scope of its access.
  • Endpoint privileges are currently available for these Admin endpoints:
    • Bulk export*:  POST /ccadmin/v1/exportProcess
    • Get export status:  GET /ccadmin/v1/exportProcess/{token}
    • Abort export: POST /ccadmin/v1/exportProcess/{token}/abort
    • Get shopper type properties: GET /ccadmin/v1/shopperTypes/{id}
    • Get item type properties: GET /ccadmin/v1/itemTypes/{id} 
    • List promotions: GET /ccadmin/v1/promotions
    • List sites: GET /ccadmin/v1/sites

NOTE: When a bulk export of profiles is done with access conferred by the endpoint privilege, the export omits PCI (credit card) data.   Therefore, endpoint privilege for bulk export is useful if you need an export of profiles for PCI compliance.

You can use registered applications with more confidence. This update introduces a more granular access control for registered applications.  An application's access can now be limited to specific functionality.

Steps to Enable

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

Update 21D 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
08 NOV 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*

B2B Commerce

Promotions

Limit Use of Promotions with Coupons

B2B Commerce

Promotions

Limit Use of Promotions with Coupons

With this Commerce enhancement, you can now limit the number of times a shopper can receive a promotion.   This feature is designed to work with promotions granted by coupons and is for registered shoppers only.

Capability highlights

  • Allows users to restrict promotions that use coupons to registered shoppers only.
  • Allows users to specify if a promotion can be granted more than once.
  • Provides the ability to determine how many times a registered shopper can receive a promotion per grant.

Example use case

  • Provide a promotion with one coupon code for all shoppers but allow only one use by each shopper (registered only)

How to specify limits on promotions with coupons in Commerce Administration UI

When you add a coupon to a promotion in the Administration UI, the following properties are available:

  • Registered shoppers only:  checkbox
  • Grant to a registered shopper more than once:  yes/no
  • Maximum uses per grant: specify a number or unlimited

How to specify limits on promotions with coupons via API

  • giveToAnonymousProfiles (Boolean): This property is used to specify whether or not only registered shoppers are eligible for the promotion. Set to TRUE by default, which allows anonymous shoppers to receive the promotion. FALSE restricts the promotion to only registered shoppers.
  • allowMultiple (Boolean): This property controls whether or not a promotion can be granted to the same individual shopper more than once. Set to TRUE by default. Setting this property to FALSE means that even if a shopper has multiple valid coupon codes for the promotion, they cannot be granted it again.
  • Uses (integer): This property specifies the number of times an individual shopper can receive the promotion per grant. Set to 1 by default. This property can be set to any positive integer; setting it to -1 or 0 equates to unlimited use.

How shoppers are informed of promotion limits on the storefront

Reduces lost revenue by preventing shoppers from reusing coupon codes to receive the same promotion more than once.

Steps to Enable

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

Tips And Considerations

  • Applies to promotions with coupons, not global promotions.
  • Available for promotions limited to registered shoppers

Update 21D 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
26 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*

B2B Commerce

Integrations

Integration with Oracle Unity

Publishing

Publishing: Save Conflicts

B2B Commerce

Integrations

Integration with Oracle Unity

This Oracle Commerce update enables merchants to more accurately personalize shopper experiences based on the integration with Oracle Unity’s derived data elements.  You can now use enriched attributes from Unity’s multiple data sources that include not only extended profile attributes but a host of intelligent and behavioral attributes.   These attributes can be used to provide a personalized shopping experience to customers on their storefront.

Capability Highlights

  • Ability to enable Unity Integration and Unity attribute selection
  • Enrich the Commerce shopper profiles and accounts with Unity data. This data is persisted into profile and account properties and can be used anywhere that profiles and accounts are exposed.
  • Commerce to Unity synchronization: Incremental synchronization is automated for profiles.  
  • Unity to Commerce synchronization: Using the Customer360 API, user profile and account attributes are synchronized from Unity at the start of the shopper session and on login.

Example Use Case

This example illustrates how merchants would use enriched attributes from their 1st, 2nd, and 3rd party data to provide a personalized shopping experience to customers on their Oracle Commerce storefront.

  • To accomplish this, use the consolidated customer profile data in Commerce to create an audience definition.
  • Next, build an audience using Audience Builder.
    • Use attributes available under the Account category, such as:
      • Average order value at the account level
      • Lifetime value of the account
      • Number of open service requests with the account
      • Total amount spent with the company across all channels
  • This newly created audience can be used in different areas within Commerce such as audience rules, promotions, and content variation slots to drive personalization.

The storefront users, upon log in, will see a range of products, offers and promotions personalized in the context of their organization based on their data in systems used by Unity including machine learning (ML) algorithms.

APIs and Endpoints

The new API endpoint is the /enrichmentMaps endpoint, a Commerce Admin endpoint used to set up the mapping between Unity profile/account attributes and Commerce profile/account properties.

Merchants can more accurately personalize shopper experiences including cold start personalization for shoppers not known to the merchant on the storefront but known to Unity

Steps to Enable

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

Tips And Considerations

  • Using the Integration with Oracle Unity feature applies to Commerce customers with a Unity subscription
  • Unity supports list-of-string attributes in profiles and accounts.  Since this is not currently supported in Commerce, syncing this data is not possible.

Publishing

Publishing: Save Conflicts

This Oracle Commerce update provides improved collaboration for Commerce users in situations when other users’ actions can affect their work.  Our new Save Conflicts feature detects when multiple users in our Admin UI have been working on the same item and gives a warning to help users avoid conflicts.

Capability highlights

  • Gives the user information before they save and overwrite another user’s changes.
  • Prevents errors when multiple team members are working on the same items.

This feature is included in the Commerce Administration UI and in endpoints that save items in Admin.

All users benefit from this feature when editing and saving items which contributes to better team collaboration and an improved user experience.

Steps to Enable

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

Tips And Considerations

  • This feature does not present the user with the specific property conflicts and allow the ability to merge them.
  • In cases where multiple users are editing the same item, a user sees the conflict modal with the last user’s name.

Update 21D

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
07 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*

B2B Commerce

Open Storefront Framework

OSF Account-Based Shopping - Unbranded Reference Store

Recommendations

B2B Account-Wide Recommendations

Integrations

Integration with Oracle Content Management (OSF)

Punchout Enhancements

Admin

Page Tags

B2B 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).

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.

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.

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.   

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.