1. Introduction Last updated: 10th October 2025

1.1. Scope

This document provides an overview of the CMP 8.20 release with specific focus on the additional functional and non-functional enhancements with respect to CMP 8.19.

1.2. Audience

This document is aimed at internal and external audiences familiar with CMP, to explain the key features of the release including any changes in how existing functions or processes are working.

2. Overview of Changes

With respect to CMP 8.19, CMP 8.20 introduces new functionality as well as changes to existing functionality and non-functional improvements. These changes can be summarised as follows.

2.1. New Functionality

2.1.1. NetEngage – Out of Bundle Charging

CMP 8.20 introduces support for enabling and disabling Out-of-Bundle (OOB) data charging for prepaid subscriptions. With this feature enabled, subscribers can be charged for data (and, when configured, voice and SMS) directly from their prepaid balance. By default, subscriptions are created with the feature disabled, i.e. they are opted out of OOB charging and must either purchase an allowance, e.g. a bolt-on package, or explicitly opt in to the OOB feature.

The feature can be configured through Configuration Centre and then enabled or disabled for individual subscribers via AgentView or the POST feature REST API.

2.1.2. Dynamic Bolt-On Purchases

CMP 8.20 adds support for dynamic bolt-ons. Bolt-on packages can now be configured to accept variable allowance amounts, and client systems can purchase these by supplying the desired voice/text/data allowance values in the REST Purchase request.

This change affects both Configuration Centre and the REST Purchase API.

Fixed-amount bolt-ons continue to be supported unchanged.


2.1.3. Bulk Action Console – Maintain Porting Requests

In order to better support the donor-led porting process used in the UK, where PAC and STAC codes are used to port to a new network and users also have the option of taking their existing mobile number with them, CMP 8.20 introduces a new bulk action option which allows operations teams to close, cancel, or revise porting requests in bulk.

This new bulk action option feature has role-controlled access and template-driven validation. Results can be viewed in the Bulk Action Console and include a full audit of successes and failures per batch.


2.1.4. Aurora Console

A new Aurora Console has been introduced as CMP’s product catalogue application. It enables bulk upload of product offerings from spreadsheets, operator approval/rejection of batches, and publication of approved offerings to external systems (e.g. the WebShop). Aurora manages products/specifications, resource templates/attributes, and offer prices within the CMP Product Catalogue.

2.2. Changed Functionality

2.2.1. Business Configuration

Some Business Configuration panels have been updated in the areas of orders and networks; highlights include:

  • Completion of CRUD (Create, Read, Update, Delete) coverage for key panels (e.g. Network, combined managed/non-managed numbers; Number Change Rules and Group (Tariff) Change Rules) with standardised dropdowns, validation, and labels.
    • Users can now add new Networks as well as view, edit, and delete existing ones.
    • From the Network List → Serial Numbers, users can add new serial numbers and view, edit, and delete existing serial number records.
    • From the Network List → Change Rules, users can add new Number Change Rules and view, edit, and delete existing rules.
    • From a Subscription Group → Links, the Group Change Rules tab allows users to add, edit, and delete existing Group (Tariff) Change Rules, as well as add new ones.
  • Consolidation under Orders (Manufacturers, Models, Warehouses, Sales Channels, Resource Templates/Attributes) and relocation of Products to this area, including a new Add Product panel.
  • Terminology and panel updates (Item Type has been changed to Product Type throughout the application).
    • The menu entry under Orders is now labelled Product Types (formerly Item Types).
    • Panel fields such as Item Type Code and Item Type Name have been renamed to Product Type Code and Product Type Name.
    • The panel now includes two additional fields: Product Type and Activation Type.

See section 3.4 for further details.

3. Impacts on CMP

The functional and non-functional changes highlighted in section 2 above have had an impact on CMP in the following areas:

3.1. AgentView

3.1.1. New Screens

No new AgentView screens have been introduced as part of CMP 8.20.

3.1.2. Changed Screens

3.1.2.1. Customer Structure – Display of Price Plan Description

The Customer Structure view in AgentView has been updated to improve clarity. For each subscription on an account, the displayed description is now sourced from the price plan, rather than the underlying tariff.

3.1.3. Changed Functionality

3.1.3.1. AgentView - Out-of-Bundle Charging (Features)

Although Features is an existing CMP function, CMP 8.20 sees the introduction of the ability to enable or disable Out-of-Bundle data charging for prepaid subscriptions. When the feature is enabled, the subscriber will be opted in to a NetEngage Rating Campaign that allows data usage to be charged from their prepaid cash balance after their data allowance has been exhausted.

Key points:

  • Based on default behaviour configured on the OCS, subscriptions are created with the Out of Bundle option disabled by default, i.e. subscribers cannot be charged for usage out of their prepaid cash balance.
  • Based on the CMP configuration outlined in section 6.5.2.1 being in place, this can be seen in the Features bottom panel of AgentView for each subscription. The setting can also be enabled and disabled for each subscription in this panel.
  • This can apply to the three usage types independently (voice/text/data); each needs to be configured separately, i.e. an OCS rating campaign and a CMP feature per usage type.

3.2. Bulk Actions

3.2.1. New Bulk Actions

3.2.1.1. Maintain Porting Requests

A new Maintain Porting Requests bulk action has been added to the Bulk Action Console to manage porting request updates at volume. This enables support for the UK donor-led porting process where PAC and STAC codes are used to port users to a new network with or without taking their existing mobile number with them.

Actions

  • Close
  • Cancel
  • Revise (optional Port In Date)

Rules & validation

  • Close requires a Recipient Network selection.
  • Per-row validation for PAC/STAC, MSISDN, and pairing; status checks prevent invalid state transitions.
  • Option to process all MSISDNs in a PAC (structure expansion) or specific PAC–MSISDN pairs from the upload.

Template: MaintainPortingRequests.xlsx (columns: Auth Code Type, Auth Code, MSISDN, All MSISDN, Port Date, SIM Activation).

Outcome: Detailed audit of successful and failed records per batch.

Access control: via WSO2 role bulk-porting-requests (see section 6.5.1).


3.2.2. Changed Bulk Actions

No existing bulk action options have been changed as part of CMP 8.20.

3.3. Admin Console

3.3.1. Daily Operations

3.3.1.1. New Jobs and Daemons

The following daemon and job have been introduced to support the new Maintain Porting Requests (PAC/STAC) bulk action in the Bulk Action Console.

  • Load Bulk Action Porting Requests daemon – This daemon is responsible for loading and validating uploaded driver files for bulk number porting requests.
    • The bulk action is initiated in the Console by uploading an Excel driver file - an existing daemon transforms the file into CSV format and places it into the directory specific to Bulk Action Porting Requests.
    • The new Load Bulk Action (Number Porting Requests) daemon monitors the inbound directory for new files and validates the file against the generic CMP file format. The Manage Number Porting Requests batch job is automatically triggered when loading and validation has completed.
  • Manage Number Porting Requests Batch job – The job processes validated rows from the bulk upload file to apply PAC/STAC changes in bulk.
    • The data provided in Excel files uploaded via the Bulk Action Console and transformed to CSV format by the Bulk Action Transformation Daemon is processed by the job with updates applied as appropriate. An audit of the records updated by the job has done is then available in the Bulk Action Console.

3.3.1.2. Changed Jobs and Daemons

No jobs or daemons have been changed as part of the CMP 8.20 release.

3.3.1.3. Deprecated Jobs and Daemons

No jobs or daemons have been deprecated as part of the CMP 8.20 release.

3.3.2. System Management

No changes have been made to any of the options within the System Management menu option in CMP 8.20.


3.3.3. System Monitoring

3.3.3.1. Add Probe Alert Recipient

The Add Alert Recipient option in System Monitoring → Probes → Recipients has been updated to support selecting individual users by User ID as alert recipients in addition to teams.

  • The panel now provides two dropdowns:
    • User – select an individual alert recipient.
    • Team – select a team to receive the alert.
  • Only DISE User records that have a populated Email Address are listed for selection as an alert recipient.

3.3.4. System Configuration

No changes have been made to any of the options within the System Configuration menu option in CMP 8.20.


3.3.5. System Administration

3.3.5.1. Outages Panel – Label Updates

Minor label updates have been applied to the Outages section of the Admin Console for improved clarity:

  • List view title is now Batch Job Outages (previously Global Outages).
  • The “Schedule Global Outage” and “End Global Outage” buttons have been updated to remove the word Global.

These changes are cosmetic only and do not impact underlying functionality.


3.3.5.2. Add & Edit User

A new radio button has been added in both the Add User and Edit User panels for Aurora Console. When ticked, the user can access the new Aurora Console.

A new tab is also available in both the Add User and Edit User panels - this is used to determine the level of access allowed in the Aurora Console when the radio button has been selected.

3.4. Business Configuration

3.4.1. New Business Configuration Screens

3.4.1.1. New Network Configuration Panels

CMP 8.20 introduces full CRUD support in Configuration Centre for managing Network configuration and associated serial number rules. The following new panels have been introduced.

Network Panels

  • New Add, Edit, View, and Delete panels allow management of network-level properties.
    • From the Network menu in Business Configuration, select Networks to access the list of networks.
    • The Add button allows users to configure a new network.
    • Selecting a network from the list and using the Edit button allows maintenance of various elements of how the network is configured.

Managed and Non-Managed Numbers View

  • From the Network List, selecting a network and using the Serial Numbers button presents a combined list view of the serial numbers configured for the selected network.
  • The view presents a single row per serial number for the selected network.
  • New managed and non-managed serial numbers can be configured using the Add option.
  • Existing managed and non-managed serial numbers can be maintained by selecting any record and using the Edit option.
  • For each serial number (managed or non-managed), users can maintain:
    • Long and short descriptions
    • Subscription, order, and change rules
    • Field type and min/max length
  • For managed numbers, additional serial number management settings are available, including:
    • Number management on/off
    • Use-by/reuse-by days
    • Reservation settings

Note: Prefix configuration and porting workflows are out of scope for this release and will be delivered separately.


3.4.1.2. Number Change and Group Change Rules Panels

CMP 8.20 introduces full CRUD panel support for Number Change Rules and Subscription Group Change Rules (Tariff Change Rules) in Configuration Centre, along with refinements to improve usability and data accuracy.

Number Change Rules

  • New Add, Edit, View, and Delete panels, accessed via the Change Rules button from the Network List view.
  • UI components for event types/codes and action types/codes follow standard conventions (dropdowns with description and code).
  • Several unused columns from the Number Change Rules table have been removed from the panels to streamline the layout.
  • Serial number components (e.g., S1–S5, P1–P9) are shown only if defined for the network and are labelled “Allow Change of [component]”.
  • Validation prevents entering network/non-network action codes without a corresponding event type and code.
  • The only mandatory field is now Description; other fields are optional depending on rule type.

Group Change Rules

  • New Add, Edit, View, and Delete panels available in the Group Change Rules tab via the Links button on the Subscription Group List view.
  • The list view in this tab presents a single row per number change rule for the selected subscription group.
  • Panel labels and dropdowns follow the same conventions as Number Change Rules.
  • Redundant fields from the Tariff Change Matrix have been excluded for clarity.
  • Label correction: Network Action Code → Non-Network Action Code on the View panel.
  • Labels updated to use the hyphenated form Non-Network.

Online help will be updated to cover these panels and behaviours.


3.4.2. Changed Business Configuration Screens

3.4.2.1. Propositions – Allowances – Dynamic Allowances

Configuration has been extended to allow bolt-on packages to be configured as dynamic—meaning that the value required is set during purchase rather than being a pre-configured static amount of voice/text/data.

A package is considered dynamic when its associated voice, text, and/or data allowance values are set to 0 in Config Centre; therefore configuring a dynamic allowance is much the same as configuring a static amount allowance. In the Add Allowance panel, populate all other fields as required, select the unit type, and set the value to 0. The amount of the allowance is then specified during purchase.

Fixed-amount packages (with non-zero configured allowances) continue to behave as before.

3.4.2.2. Propositions – Panel and Menu Updates

  • Add Panel for Package Associations – The Package Associations list view now includes an Add button, allowing users to create a Tariff–Package association directly from this screen. The new panel supports selecting a tariff and a package to link. Validation mirrors the rules enforced when creating the association from the tariff panel.
  • Menu Structure Update – Thresholds – The Thresholds menu option has been moved from Pricing Configuration to Propositions, reflecting its stronger alignment with proposition-level setup.

3.4.2.3. Product Type Panel Enhancements (formerly Item Type)

Several updates have been made to the Item Type panels in Configuration Centre to improve usability and align with updated product catalogue terminology.

The Item Type concept has been renamed to Product Type throughout the application:

  • The menu entry under Orders is now labelled Product Types.
  • All panel names, breadcrumbs, view titles, search filters, and component labels have been updated accordingly.
  • Fields such as Item Type Code and Item Type Name have been renamed to Product Type Code and Product Type Name.
  • Delete confirmation messages reflect the new terminology.
  • Serial number fields (S1–S5) have been removed from the Add/Edit/View panels, as they are no longer in use.

Two new mandatory fields have been added to support future integration with the Product Catalogue:

  • Product Type – e.g. Hardware, Service, Voucher.
  • Activation Type – Immediate, On Dispatch, Activation by Customer.

3.5. Pricing Configuration

3.5.1. New Pricing Configuration Screens

No new pricing configuration screens have been introduced as part of CMP 8.20.


3.5.2. Changed Pricing Configuration Screens

No pricing configuration screens have been changed as part of CMP 8.20.

3.6. SOAP Web Services

3.6.1. New Web Services

No new SOAP Web Services have been introduced as part of the CMP 8.20 release.


3.6.2. Changed Web Services

No SOAP Web Services have been changed as part of the CMP 8.20 release.

3.7. RESTful Web Services

3.7.1. New CMP Web Services

No new RESTful Web Services have been introduced as part of the CMP 8.20 release.


3.7.2. Changed CMP Web Services

The following Web Services have been enhanced for CMP 8.20:

3.7.2.1. Subscription Feature APIs – Out-of-Bundle Charging Support

While no structural changes have been made to the existing Feature Management APIs, the following endpoints are now used to manage the newly introduced Out-of-Bundle (OOB) charging feature for prepaid subscriptions:

  • GET /features – returns the enabled and disabled features for the subscriber, including the OOB charging feature (if configured).
  • POST /feature – accepts feature actions such as ENABLE or DISABLE for specific feature codes, including the OOB charging feature (if configured).

These APIs are used to opt a subscription in or out of the NetEngage Rating Campaign that supports out-of-bundle data-usage charging.


3.7.2.2. Purchase Bolt-On - Dynamic Amounts

The existing Purchase Bolt-On REST API now supports dynamic bolt-on purchases.

When purchasing a dynamic package, the request must include non-zero allowance values for each allowance type present in the package (voice/text/data) - these should be specified in the new allowanceValues container of the request.

The provided values are captured against the purchase and used for provisioning on the NetEngage OCS.

Requests missing the required non-zero amounts for a dynamic package are rejected with validation errors.

Behaviour for fixed-amount packages is unchanged; allowance amounts are taken from configuration and need not be supplied in the request.

3.7.2.3. Create Order Product API

The TMF Create Order Product API has been updated to include a new request field: subscriptionId.

3.7.3. New Business Configuration Web Services

No new Business Configuration RESTful Web Services have been introduced in CMP 8.20.


3.7.4. Changed Business Configuration Web Services

No RESTful Web Services have been updated as part of the CMP 8.20 release.


3.7.5. New TM Forum Open APIs

No additional TMF APIs have been provided as part of the CMP 8.20 release.

3.8. Integration Adapters

No changes have been made to integration adapters in CMP 8.20.

3.9. NetEngage Adapters

3.9.1. NetEngage Provisioning Adapter – Out-of-Bundle Charging Support

The NetEngage Provisioning Adapter has been enhanced to support the new Out-of-Bundle (OOB) charging feature.

  • Enable OOB charging: when the feature is turned on for a subscription, the adapter invokes the NetEngage AllocateRatingCampaign SOAP service and stores the returned Unique Campaign ID against the subscription in CMP.
  • Disable OOB charging: when the feature is turned off, the adapter uses the stored Unique Campaign ID to invoke the NetEngage DeleteRatingCampaign SOAP service and updates CMP to reflect the feature’s disabled state.

No other changes have been made to the NetEngage adapters as part of this release.


3.10. Openet Adapter

No changes have been made to the Openet adapters as part of this release.


3.11. Lifecycle Adapter

No changes have been made to the Lifecycle adapters as part of the CMP 8.20 release.


3.12. UK-specific Adapters

No changes have been made to the UK-specific adapters as part of the CMP 8.20 release.


3.13. Aurora Console

3.13.1. Overview

The Aurora Console is CMP’s product catalogue, supporting bulk upload and approval of product offerings, and publication of approved offerings to external systems. The console also hosts configuration for products/specifications, resource templates, and resource attributes.

3.13.2. Batches (Upload / Approve / Reject)

A new Batches area provides an audit and lifecycle for product-offering uploads from spreadsheet templates:

  • Upload: operator supplies upload parameters (Product Type, Offering Start/End, Sales Channel, optional Marketing Segment, Place, Category) and selects the .xlsx file.
  • Audit & filters: view recent uploads (e.g. last 30 days) and filter by submitting user.
  • Approval workflow: batches are validated; on success, operators can Approve or Reject. Only Approved and fully valid batches proceed to product/spec/offering creation.

3.13.3. Batch Templates

A new Batch Templates area provides downloadable .xlsx templates per product type. Templates include built-in validation for data type, mandatory/optional fields, and maximum lengths.


3.14. MDS Webshop Adapter

3.14.1. Overview

A new module, MDS Webshop Adapter, publishes eligible product offerings from the CMP Product Catalogue. The adapter consumes offering identifiers from ActiveMQ, retrieves full details via TMF Product Catalogue APIs, flattens catalogue data to the WebShop format, and posts the result to Strapi.

A transmission daemon polls the queue on a configurable delay and queue name (default queue name is outboundProductCatalogue).

Supports non-hardware and bundled offerings alongside hardware products.

4. Product Fixes

In addition to functional and non-functional changes and improvements, the CMP 8.20 product version also addresses a number of application support issues. This section provides a summary of the issues fixed in this release.

The following issues have been addressed within this release:

Reference Area Description
CMPIS-590Service & Discount ManagementAdd Subscription Service - Non recurring per bill charges now have the expiry date set to the same date as the effective date when the service is being added. This ensures that if the service ever needs to be added again it can be, and also that the service no longer appears in the 'Active Services' view of AgentView after it has been billed.
CMPIS-2090Agent ViewAgentView - Subscription - Maintain Service - panel resized to ensure no scroll bars are required or displayed.
CMPIS-2278Agent ViewAgentView - Contact field on the account summary now shows blank instead of 'null null null' if no contact details are stored.
CMPIS-2689RESTful Web ServicesREST - Create Order - Issue with providing 'NONE' for handsetCost has been resolved.
CMPIS-2946RESTful Web ServicesREST - Create Account - Validation error now returned if forename or surname not provided in request, rather than the exception that was being returned previously.
CMPIS-3250Agent ViewAgentView - No longer fails to start if the Stock Check URL Property is missing.
CMPIS-3381RESTful Web ServicesREST - Get Subscription - Issue causing an error when retrieving details for certain prepaid subscriptions has been resolved.
CMPIS-3391CMP InstallerPersistent errors were being created in catalina.out log files - a Webswing configuration change has been made to resolve this.
CMPIS-3397Business ConfigurationPropositions - Discounts - Services tab no longer unavailable when configuring a Cross Product Discount Scheme
CMPIS-3400CMP InstallerCMP8 Installer - Issue with the installer missing certain tasks when running in Patch mode has been resolved.
CMPIS-3405Agent ViewAgentView - Subscription Creation Wizard - The Price Plan Drop Down is now only available when at least one price plan fulfils the filter criteria entered.
CMPIS-3412Agent ViewAdmin Console & Agentview - CMP logo updated.
CMPIS-3414Business ConfigurationPropositions - Allowances - Add - Issue with setting the 'OCS Allowance Name' resolved, other minor fixes applied to ensure limited and unlimited allowances can be created and viewed for all network types.
CMPIS-3420Business ConfigurationSystem Properties - Service Properties - Fix made to ensure property changes are saved successfully.
CMPIS-3424Business ConfigurationOrders - Warehouse - Delete only allowed if the record is not in use.
CMPIS-3425NetEngage IntegrationAgentView and REST Allowance Balance - Inclusive amounts now displayed correctly for recipient subscription after an allowance transfer.
CMPIS-3430Sabre ServerConsole - Add/Edit User - Minor fixes to tidy up the panel, checkboxes changed to radio buttons and some label names updated.
CMPIS-3431Aurora ConsoleCosmetic improvements made to Batches, Product Offerings, and Batch Template panels.
CMPIS-3440Business ConfigurationOrders - Products - Miscellaneous Fixes to add and view panels

5. Documentation

5.1. Product Documentation

The product documentation is available online on the documentation portal. This online portal requires authorised access, which can be obtained by contacting MDS Global support. The documentation is also available as downloadable PDFs as follows:

  • Installation Guide
  • Technical Architecture
  • CMP Overview
  • Documentation Overview
  • System Administration Guide
  • Security Guide
  • AgentView Function Security Guide
  • Operational Overview
  • Business Configuration Overview
  • Billing Functionality Guide
  • Communications Functionality and Configuration Guide
  • Propositions Functionality and Configuration Guide
  • Payments Functionality Guide
  • Extracts Guide
  • Purge Guide
  • Standard Reporting
  • Batch Jobs and JSON Schemas Guide
  • RESTful Web Services API Guide
  • SOAP Web Services Semantics Guide
  • Business Configuration RESTful Web Services API Guide
  • Glossary.
Document Version Document Changes
AgentView Function Security Guide 1.1 The screens have been updated to reflect the new MDS logo and branding colours in the AgentView Function Security Guide for CMP 8.20.
Batch Jobs and JSON Schemas Guide 1.1 The Batch Jobs and JSON Schemas Guide has been updated to include the changes to the jobs and daemons highlighted above.
Billing Functionality Guide 1.0 There are no updates to the Billing Functionality Guide as part of CMP 8.20.
Business Configuration Overview 1.0 Added new configuration functionality that allows users to add, edit, and view additional CMP configuration data.
Business Configuration RESTful Web Services API Guide 1.0 There are no updates to the Business Configuration RESTful Web Services guide as part of CMP 8.20.
CMP Overview 1.0 Updated the business configuration and product catalogue to include the new configuration functionality that allows users to add, edit, and view additional CMP configuration data.
Communications Functionality and Configuration Guide 1.0 There are no updates to the Communications Functionality and Configuration Guide as part of CMP 8.20.
Documentation Overview 1.0 There are no updates to the Documentation Overview as part of CMP 8.20.
Extracts Guide 1.0 There are no updates to the Extracts Guide as part of CMP 8.20.
Glossary 1.0 There are no updates to the Glossary as part of CMP 8.20.
Installation Guide 1.0 There are no updates to the Installation Guide as part of CMP 8.20.
Operational Overview 1.0 Updated the Operation Monitoring topic to include the new interactive dashboards that monitor the infrastructure and application performance in CMP.
Payments Functionality Guide 1.0 There are no updates to the Payments Functionality Guide as part of CMP 8.20.
Propositions Functionality and Configuration Guide 1.0 There are no updates to the Propositions Functionality and Configuration Guide as part of CMP 8.20.
Purge Guide 1.0 There are no updates to the Purge Guide as part of CMP 8.20.
RESTful Web Services API Guide 1.1 The REST Web Services guide has been updated based on the changes highlighted in section 3.7.2 above.
Security Guide 1.0 There are no updates to the Security Guide as part of CMP 8.20.
SOAP Web Services Semantics Guide 1.0 There are no updates to the SOAP Web Services Semantics Guide as part of CMP 8.20.
Standard Reporting 1.0 There are no updates to the Standard Reporting Guide as part of CMP 8.20.
System Administration Guide 1.0 There are no updates to the System Administration Guide as part of CMP 8.20.
Technical Architecture 1.0 Updated the Spring Framework, Spring Boot, Spring Batch, Spring Security and Tomcat versions.

5.2. Online Documentation

Online help is available in AgentView, Business Configuration, the Administration Console, the Bulk Actions console, and the Pricing Configuration console. The table below summarises the current versions of the online help and the changes since CMP 8.18:

Online Help Version Document Changes
AgentView 1.11 Updated the Spend Caps topic to include that the prepaid balance available to prepaid subscribers controls how much they are charged for overage (out-of-bundle usage).
Business Configuration 1.24

The following updates have been made to the Business Configuration help in CMP 8.20:

  • Thresholds: moved from the Pricing Configuration console to the Propositions menu.
  • Serial Numbers: new topic explaining how to configure serial numbers for a specific network.
  • Number Change Rules: new topic covering how to define which subscriber numbers can be updated for a given network.
  • Package Associations: an Add button has been introduced to associate a tariff to a package directly from this screen.
Administration Console 1.22 The Users topic has been updated to include the Aurora Console tab (for assigning Aurora roles and access rights) and the new Monitoring Alerts tab (for adding users as alert recipients to the relevant probes).
Pricing Configuration Console 1.10 Thresholds have been removed from this console and now appear under the Business Configuration console.
Bulk Action Console 1.14 A new Porting Requests topic has been added for the bulk action that supports the completion, cancellation, or revision of porting requests (PAC/STAC).

6. Release Upgrade

The CMP 8.20 installer includes the capability to upgrade a CMP 8.18 installation without the loss of configuration or customer data provided that the software, file system and database structure of the installation in question are at no point manually modified.

Important

The CMP 8.20 Installation Guide, and the details below, should be read before attempting the upgrade to CMP 8.20.

It is important that the following sections are read prior to performing the upgrade, specifically the Configuration Changes section, as it may be advisable to backup relevant configuration prior to performing the upgrade to ensure the configuration can be replicated, if necessary, post upgrade.

6.1. Upgrade Notes

The following notes and known issues apply to the CMP 8.20 upgrade.

6.1.1. Known Issues

6.1.1.1. Intermittent AgentView Login Issue

Logging into AgentView can intermittently result in an Authentication Failed, Try Again error. This issue is under active investigation and will be resolved as soon as possible.

Workaround:

  • Click Try Again, then refresh the browser tab to return to the base AgentView URL.
  • When prompted with Please select an application, choose the CMP AgentView icon to proceed.

6.2. Installation Configuration Tool Changes

There are no updates to the Installation Configuration Tool as part of CMP 8.20.

6.3. Third party libraries

6.3.1. Java 21 Compatibility Refactor

As part of the CMP 8.20 release, several backend modules have been refactored to ensure compatibility with Java 21. This ensures long-term support, improved performance, and alignment with platform-wide dependency upgrades introduced in recent releases.

The following modules have been refactored:

  • Content Sensitive Help
  • Number Porting Services
  • Voucher Management Services
  • Shared Services

6.4. Database Changes

6.4.1. New Tables and Views

The following tables have been added in CMP 8.20:

  • Table productOfferingBundle – Defines a product offering bundle by linking a bundle product offering to its member product offerings, with a sequence (1 = primary). Includes standard audit fields.
  • Table purchaseAllowance – New table introduced to support the Dynamic Packages functionality - stores Purchase ID, Allowance ID, and the Allowance Value.
  • Table Product upload interface batch header – New staging table to support batch uploads into the product catalogue - holds batch level information.
  • Product upload interface batch detail – New staging table to support batch uploads into the product catalogue - holds row-level data for each batch.
  • Product upload interface batch detail attribute value New staging table to support batch uploads into the product catalogue - holds name/value pairs for for each row per batch.

6.4.2. New Attributes

The following table attributes have been added in CMP 8.20:

  • Table CSQ4REP (itemType):
    • Product Type – Valid values include H – Hardware, R – Price Plan, N – Serial Number, S – Service, V – Voucher, O – Other.
    • Activation Type – Valid values include 1 – Immediate, 2 – On Dispatch of Order, 3 – Activation by Customer.
  • Table COCIREP (DISE User):
    • Email Address – Stores the user's email address when a user profile is created (or updated) via the Admin Console.
  • Table Alert Recipient:
    • User ID – Stores the user ID alongside probe alerts, foreign key to the same field on the DISE User table.

6.4.3. Dropped Tables and Views

The following tables or views have been dropped in CMP 8.20:

  • Table Item Product Level – This table has been removed as part of the rework to align orderable items with the new Product Catalogue. Its function has been replaced by the enhanced Product Type configuration.
  • Table Recipient – This table has been removed as part of the rework around System Monitoring, specifically Alerting.
  • Table Alert History Recipient – This table has been removed as part of the rework around System Monitoring, specifically Alerting.

6.4.4. Dropped Attributes

The following table attributes have been dropped in CMP 8.20:

  • Table Alert Recipient:
    • Recipient Identifier column removed.

6.4.5. Modified Attributes

The following table attributes have been modified in CMP 8.20:

6.5. Configuration Changes

6.5.1. Automatic Updates

As part of the upgrade to CMP 8.20 the following configuration changes have been automatically applied:

6.5.1.1. Bulk Action Application Access

The following application group has been added to the applicationGroup table to allow access to specific bulk actions:

  • bulk-porting-requests

Important

To enable a user to have access to the Maintain Porting Requests bulk action, access to this option must be enabled through the System Administration → User option within the Administration Console, or directly through WSO2 for the specific user.



6.5.2. Manual Configuration

6.5.2.1. Out of Bundle Charging

With the introduction of Out-of-Bundle (OOB) charging, a rating campaign must be configured on the OCS for each service this feature applies to (e.g., data, voice, text). The example below assumes an OCS feature such as OOB-Data.

After the OCS campaign is configured, add the corresponding command and workflow configuration in CMP so subscriptions can be enabled/disabled via AgentView and REST.

  1. Network Commands (Business Configuration option: Network → Network Commands)
    • Add a command to enable the OOB feature for a subscription with Network Action Type = Enable Feature.
    • Add a command to disable the OOB feature for a subscription with Network Action Type = Disable Feature.
  2. Network Command Groups (Business Configuration option: Network → Network Command Groups)
    • Add the commands from [1] to the NetEngage command group.
  3. Workflow Events (Business Configuration option: Workflow)
    • Define new events to enable and to disable the OOB feature for a subscription.
    • For each workflow code, set Event Status When Raised to Pending Auto Processing and Status After Confirmation to Resolved.
    • All events must be raised at subscription level.
    • Each event shall contain one action:
      • The Action Type must be a Network Action action type.
      • The Network Action must be either Enable Feature or Disable Feature.
      • Set the Network Command to the corresponding command created in [1] (its Network Action Type must match the action’s Network Action).
      • Set Processing Mode to Batch.
      • Enable the Send to Network? checkbox.
  4. New Feature Codes (Business Configuration option: Network → Network Features)
    • Create a Feature Code for each service type where OOB will be used (e.g., Data, Text, Voice).
    • For each code, select the corresponding OCS Feature Name from the dropdown.
    • For each code, select the correct Enable Workflow Event Type & Code and Disable Workflow Event Type & Code.
  5. New Network Feature Defaults (Business Configuration option: Network → Network Feature Defaults)
    • Create a Network Feature Default entry for each new Feature Code for the NetEngage network.
    • Set the Default Feature State to Disabled for each.