Cloud Readiness / Oracle Buying Experience Cloud
What's New
Expand All


  1. Update 22A
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Industries Framework Common
    1. Industries Framework
        1. Configure API Timeouts
  5. Buying Experience
    1. Buying Experience
        1. Make Pricing Adjustments at Component Level
        2. Price Roll-Up and Alterations Breakup
        3. Additional Options for Asset-Based Ordering
        4. Modify Quotes
        5. Additional Outbound Events

Update 22A

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
23 DEC 2021     Created initial document.

Overview

Digital Experience for Communications Buying Experience provides an API first approach to support digital omni-channel subscription buying and ordering solution for communication and media service providers. The solution simplifies the overall buying process by delivering pre-built and pre-integrated capabilities that covers every aspect of the customers buying journey from unified product catalogs to alignment of commerce experience to subscription management. The comprehensive industry specific processes support both assisted and unassisted buying. Key capabilities include:

  • Modern and personalized user experience: Supports contextual customer acquisition journey, personalized catalogs for different markets, and data-driven user experience.
  • Digital omni-channel buying experience: Enables consistency across channel journeys, allows subscriber channel hopping, and introduces both traditional and new digital channels.
  • Customer 360 and subscription management: Provides context-aware customer 360 dashboards and guided subscription buying experiences.
  • Adaptive customer data mastering: Maintains data consistency across applications in a deployment and enables agility.
  • TMF Open Digital Architecture: Drives channel engagements and system integrations efficiently and effectively.

This guide outlines the information you need to know about new or improved functionality in this 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.

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*

Industries Framework Common

Industries Framework

Configure API Timeouts

Buying Experience

Buying Experience

Make Pricing Adjustments at Component Level

Price Roll-Up and Alterations Breakup

Additional Options for Asset-Based Ordering

Modify Quotes

Additional Outbound Events

Industries Framework Common

Industries Framework

CX Industries Framework serves as a platform for seamless integration of applications. You can use this platform to integrate your application with other Oracle applications and third-party applications, which includes cloud services and on-premise systems. In addition, you can leverage data from various sources, use TM Forum Open APIs and REST APIs to configure and extend tailored experiences.

CX Industries Framework supports both synchronous and asynchronous interactions between the integrated applications. It hosts all the TM Forum Open APIs on Oracle Cloud Infrastructure API Gateway to secure and optimize the API interactions. It also ensures high availability and resiliency by using the Oracle Cloud Infrastructure Load Balancing service.

Configure API Timeouts

You can configure API-level timeouts for the read operation to avoid unnecessary delay caused by slow or unresponsive client applications. You can configure it using the API and Routing Configuration section in the Topology Manager UI.

Improves user experience and make the system more fluid by timing out API calls to avoid delay by slow or unresponsive applications. 

Steps to Enable

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

Role Information

  • DX4C Configuration API Timeouts

Buying Experience

Buying Experience

Make Pricing Adjustments at Component Level

You can do pricing adjustments at a component level for any customizable product, such as a commercial bundle or a service bundle.

This feature is supported as part of TMF 620 (Product Catalog), TMF 663 (Shopping Cart) and TMF 622 (Product Order) API responses.

The business benefit of this feature is that you can provide pricing adjustments at child offering levels of a package.

Steps to Enable

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

Price Roll-Up and Alterations Breakup

Price roll-up and breakup of alterations such as discounts and penalty are now supported for first-time purchases as part of TMF 663 (Shopping Cart) and TMF 622 (Product Order) API responses.

These discounts include package-level and component-level discounts, such as commercial and service bundles.

The business benefit of this feature is that the user can know how the final price for a package and its components have been determined.

Steps to Enable

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

Additional Options for Asset-Based Ordering

You can use the Patch method of the TMF 622 (Product Order) API for asset-based ordering scenarios, such as suspending, resuming, terminating or upgrading assets (products). You can also use this method to modify assets, for example, adding a new optional product or changing the asset characteristics.

Also, you can use the Patch method of the TMF 637 (Product) API to update group name and alias of a product (asset). This generates the ProductAttributeValueChange event to indicate the change in the product attribute value. You can enable or disable this event using the Configuration API.

The business benefit of this feature is that it provides alternative options to:

  • Handle asset-based ordering
  • Easily update specific product (asset) attribute values

Steps to Enable

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

Modify Quotes

You can use the Patch method of the TMF 648 Quoting API to update quote information, which includes:

  • Account details
  • Packages
  • Optional items
  • Devices and services
  • Header-level notes
  • Email address

You can also save the quote with the enterprise buyer email address and retrieve it later.

The business benefit of this feature is that you can now easily update quote information and also save and retrieve them later.

Steps to Enable

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

Additional Outbound Events

The QuoteAttributeValueChange event is generated when there is an update to the quote, for example, account details, email, addition or deletion of line items.

The CancelProductOrderStateChange event is generated when order cancellation is processed by the downstream applications.

You can enable or disable these events using the Configuration API.

The business benefit of this feature is that you can notify the external applications about the quote attribute value changes and cancel product order state changes.

Steps to Enable

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