- Revision History
- Overview
- Feature Summary
- Industries Framework Common
- Launch Experience
-
- Launch Experience
-
- Improved Troubleshooting Experience for Handling Publish Job Failures on Initiatives
- Configure Common Business Configurations Via UI
- Define Location Based Promotions Using Geography Hierarchy
- Support Multiple Draft Versions of Entities
- Design Time Restrictions Supporting Run Time Capabilities
- Package Level Component Actions
-
- Launch Experience
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 16 DEC 2022 | Created initial document. |
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.
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 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 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 |
UI or |
|
||
Improved Troubleshooting Experience for Handling Publish Job Failures on Initiatives |
||||||
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.
In this release, Developers (at Tenant or Partner) can find, extend, test, package, and deploy required business logic extensions to the tenant workspace, which are upgrade safe.
The most common examples of business logic extensibility are:
- Validation & Enrichment of an attribute value
- Calculation or generation of an attribute value
This feature enables Tenants to implement after-market business logic extensions without making any code changes. For example:
- Ensure Government ID is valid using a Government Service API:
- Developer can configure relevant entity with validation API and enriches the extended Government ID entity.
Steps to Enable
You don't need to do anything to enable this feature.
In this release, CXIF provides the ability to discover which APIs are registered and configured inside CXIF. This API can be used by any application that shares the environment with CXIF. For example, you can use this API to discover which TMForum or Open APIs are available to applications in the CXIF environments.
This provides benefit to application developers to determine what APIs are available at runtime.
Steps to Enable
You don't need to do anything to enable this feature.
Improved Troubleshooting Experience for Handling Publish Job Failures on Initiatives
You can now view the published jobs and its status when an initiative is published to the various spoke systems. In case of unsuccessful publish, you can download the execution log of published catalog items for troubleshooting purpose.
Example - You have published initiative PSPUsageInit to the spoke systems for testing and you want to see the status of these published jobs.
The following figure shows you the Publish job summary and the published job details.
Publish Job Summary
The business benefit of this feature is that you would now be able to troubleshoot the published job failures, analyze the reason of failures, and fix them.
Steps to Enable
You don't need to do anything to enable this feature.
Role And Privileges
- Communications Catalog Administrator
Configure Common Business Configurations Via UI
You can now configure and manage the common business configurations required across the DX4C ecosystem centrally via Launch UI.
The following figure shows you how to manage the common business configurations
Common Business Configuration
The business benefit is that common business configuration required across DX4C can be managed from one central repository via Launch and launch specific configurations continue to exist outside this.
Steps to Enable
You don't need to do anything to enable this feature.
Role And Privileges
- Communications Catalog Administrator
Define Location Based Promotions Using Geography Hierarchy
You can now use fusion geography hierarchy in promotion profile specification and define location-based promotions.
Ex - Configure a 10% discount on New Zoom In More promotion applicable for product offering Supremo Zoom for subscribers from the country US and state of California.
The following image shows the configuration of the promotion profile specification via Workbench
The following image shows the configuration of the promotion event and criteria group.
The feature allows you to model location attributes such as Country, City, State for Promotions based on the Country setup.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Configure the common business configuration parameter Country attribute.
- Configure the promotion profile specification to have a geography enabled attribute.
- Create the promotion with the above promotion profile. As part of criteria parameters choose the country attribute. Now you will be able to view the geography hierarchy structure which can be used to setup the location-based promotion.
Role And Privileges
- Communications Catalog Product Manager
Support Multiple Draft Versions of Entities
You can now define multiple draft versions of catalog entities like product offering, specifications, and promotions. This enables you to manage major and minor release changes happening for a catalog entity.The objective of this feature is to support the need for running parallel releases with changes to the same entities.
There are planned and unplanned releases that every CSP goes through. These are synonymous to Major releases and Minor releases. Per definition new launches targeted for an event with a multitude of offers and promotions to be launched are classified as Major releases, often times having quarterly or half yearly schedules. While fixes to released ones or any incorrect configurations that has been released to be addressed as bug fixes or to quickly release offers to plug churn or in response to competitive launches are classified as Minor releases. In essence, within a Major release window while changes are happening there is always a need to have Minor releases that require working on the same catalog definitions.
Example 1 - Version 2.0 of Supremo Internet 400 Package has been released to the market as a part of Supremo CSP's Q2 quarterly release. Sam, the Product Manager has a requirement to lower the monthly charge for the package by 5% as a part of Supremo's Q3 release.
Example 2: Version 2.0 of Supremo Internet 400 Play Package has been released to the market as a part of Supremo CSP's Q2 quarterly release. Sam, the Product Manager has a requirement to lower the monthly charge for the package by 5% as a part of Supremo's Q3 release. While Sam has started to work on this task, the Vphone 13 128gb variant that is part of the package is reaching low inventory levels and new inventory of the 256gb variant of Vphone13 has come in and is to be promoted with immediate effect. Sarah, another Product Manager is tasked to make this package change, test and release it to production ASAP. Sarah goes onto make the necessary changes on the released offer to remove the 128gb variant and add the 256gb variant and releases to production for subscriber to start ordering. Since the device has discontinued the 128gb variant, the 256gb variant should be continued going forward.ie., Sam should be made aware of this change for it to be factored into his Q3 planned release. Sam uptakes the changes from a bug fix release while a planned release is in progress.
Example3: Version 2.0 of Supremo Internet 400 Play Package has been released to the market as a part of Supremo CSP's Q2 quarterly release. Sam, the Product Manager has a requirement to lower the monthly charge for the package by 5% as a part of Supremo's Q3 release. While Sam has started to work on this task, the Vphone 13 128gb variant that is part of the package is reaching low inventory levels and new inventory of the 256gb variant of Vphone13 has come in and is to be promoted with immediate effect. Sarah, another Product Manager is tasked to make this package change, test and release it to production ASAP. Sarah goes onto make the necessary changes on the released offer to remove the 128gb variant and add the 256gb variant and releases to production for subscriber ordering. However, the inventory shortfall is short term and would only last for few weeks that starting Q3 the 128gb variant will be available and the 256gb variant is being pulled off the market.i.e., the changes made by Sarah doesn't need to be up taken by Sam as Sarah's change is only a temporary change. Sam rejects the changes from a bug fix release while a planned release is in progress
The following image shows multiple draft versions the product offering catalog entity.
The business benefit of this feature is CSP's can now run parallel releases with changes to the same entities.
Steps to Enable
You don't need to do anything to enable this feature.
Role And Privileges
- Communications Catalog Product Manager
- Communications Catalog Administrator
Design Time Restrictions Supporting Run Time Capabilities
The modelling capabilities between design-time and run-time applications are pretty common regardless of publishing to Oracle or non-Oracle runtime apps. There would exist a gap between what can be modeled at design time vs. what an application can consume at runtime based on service provider's ecosystem. You would be able to set modeling rules around which design-time features are available for a service provider ensuring the design-time application respects and enforces any such restrictions as defined to have an error-free publishing to runtime applications. Such restrictions are based on CSP ecosystem and not for individual runtime applications. One restriction for the ecosystem and not one per runtime application.
You can now define the entity profile restrictions using the REST API.
The business benefit of this feature is you would be able to set modeling rules around which design-time features are available for a service provider ensuring the design-time application respects and enforces any such restrictions as defined
Steps to Enable
Review the REST service definition in REST APIs for Launch Experience, Doc ID 2725039.1, on My Oracle Support.
Tips And Considerations
Use REST API to define the entity profile restrictions endpoint.
https://{FusionAppsHost}/crmRestApi/atcProductCatalog/11.13.18.05/productCatalogReferenceManagement/v1/customProfileSpecification/PO_AGGR_ENT_PROF
Key Resources
- REST service definition in REST APIs for Launch Experience, Doc ID 2725039.1, on My Oracle Support.
Role And Privileges
- Communications Catalog Administrator
Package Level Component Actions
A package containing multiple services can be ordered together while allowing the subscriber to modify or disconnect individual services. There are runtime scenarios that allow a subscriber to cancel or modify one or more services with applicable rules and penalties. You can now configure what kind of action the runtime order capture application should take upon such situations by specifying the component actions in the package. The available actions are modify, disconnect and prompt.
The following figure shows action Modify on the PSV-PSP_Wireless Line component of the package Superemo Zoom New
The business benefit of this feature is the ability to configure what kind of action the runtime order capture application should take upon in situations like subscriber cancels or modifies the services by specifying the component actions in the package at design time.
Steps to Enable
You don't need to do anything to enable this feature.
Role And Privileges
- Communications Catalog Product Manager