This document provides information about Oracle Communications Launch Cloud Service Release 26A.

New Features

This release includes the following features and enhancements:

Enhancements to Initiatives

The Initiatives entity now offers additional capabilities to help business users collaborate more effectively with IT stakeholders during market releases. The following features have been introduced in Initiatives:
  1. Ability to add multiple attachments to an Initiative and view the attachment list from a user‑specified folder. All attachments are scoped within the Launch application. For example, documents related to offer design.
  2. Ability to view the publish history across all lifecycle states and destinations within an Initiative, enabling tracking of publish actions and access to historical publish details.
  3. Ability to configure alerts and notifications for Initiative events based on lifecycle status changes. You can select recipients and choose events (for example, initiative assignment, approval requests, and publish status changes). Notifications are sent to the configured recipients when the event occurs.
  4. Ability to add approvers for all offers at once through Initiatives. You can now add or manage approvers for product offering approvals within an Initiative. When approval is requested (and approval is enabled), approvers are notified for that Initiative’s offers. The existing capability to override offer approvals remains available.

These features deliver business value by enabling business and IT teams to collaborate throughout the end-to-end market release process, from requirements and validation to commercial availability.

Access Requirements: Communications Catalog Administrator

Integrate Launch with Digital Business Experience Solution

The following modeling capabilities have been introduced for atomic offerings to further automate catalog distribution to the Oracle Communications Billing and Revenue Management (BRM) application.
  1. Ability to optionally configure a beat for attribute-based pricing (usage only). The beat is the pulse measure used solely for charging usage quantities. If a beat is configured at the rule level, it takes precedence over the beat defined in the charging terms.
  2. Ability to configure rollover terms for rollover charges. Previously, only rollover charges could be configured. This release adds support for defining rollover terms using the charging terms template.
  3. Charge-share modeling is now integrated with Oracle Communications Pricing Design Center (PDC).

This feature delivers business value by expanding modeling capabilities and automating distribution to the Oracle Communications Billing and Revenue Management (BRM) application.

Access Requirements:
  • Communications Catalog Product Manager
  • Communications Catalog Administrator

New Product Offering Design Experience

The product offering creation experience has been updated to the new Redwood navigation pattern in this release. This applies to all product offering types (atomic and bundle) and provides an improved offer creation and management experience.

This feature delivers business value by providing a guided flow that streamlines and improves the user experience for offer creation and revisions.

Access Requirements:
  • Communications Catalog Product Manager
  • Communications Catalog Marketing Manager
  • Communications Catalog Administrator

Support for Channel, Location, and Market Segment for Product Offerings

The product offering now includes additional modeling capabilities for all offer types. These configurations are available only for orderable offerings.

  1. You can set up location constraints on an offering to make it available only to specific geographic or physical locations, or to a defined set of location references critical to your business scenarios. Example: Make an offer available only to a specific state in the United States.
  2. You can define ordering channels using channel references. Example: Make an offer available via online or call center channels.
  3. You can make an offering available to specific market segments by configuring market segment eligibility. Example: Make an offer available only to the student segment.

These design-time constructs enable the runtime system to determine the commercial availability of offers across multiple ordering channels, customer segments, and locations.

All referenced entities must be seeded by an administrator via Administration > Configuration before they can be used in a product offering.

Access Requirements:
  • Communications Catalog Administrator
  • Communications Catalog Product Manager

Fixed Issues

There are no fixed issues in this release.

Known Issues

This section describes the known issues in this release.

Unable to Update the Version of a Component in a Package

The UI fails to update a component’s version within a revised package. Although the version should change to the latest version and persist after refresh, selecting a new version causes the UI to refresh and revert to the previous value.

Workaround: Use the /productOffering API to update the component’s version in the bundledProductOffering array.

Delete Button Fails to Delete SKU Code Data in Product Specification

In Product Specification, after adding a SKU template, attributes, and a SKU code (ID and value), selecting the checkbox and clicking Delete results in no action. The SKU code is not removed.

Currently, there is no workaround.

Deprecated and Removed Features

There are no deprecated or removed features in this release.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customer access to and use of Oracle support services will be pursuant to the terms and conditions specified in their Oracle order for the applicable services.