The key changes to CloudBlue Commerce 21.0 are a solid foundation for quick and frequent delivery of new features that you can get by updating just a couple of components. These key changes are:
- CloudBlue Commerce completed the shift towards microservice architecture to support cloud-native deployment.
- We EOLed some of the modules and features as planned.
Key Changes
Support of Cloud-Native Configuration
As of CloudBlue Commerce 21.0, service providers can deploy CloudBlue Commerce using a cloud-native configuration approach in which CloudBlue Commerce components are deployed in a Kubernetes cluster in a public or an on-premises cloud.
This approach has the following advantages:
-
More frequent releases and faster delivery of features.
-
Optimization, simplification, and unification of deployment and upgrade operations.
-
Horizontal scalability and fault tolerance of the core components such as OSS, BSS, and UI.
-
Cloud-agnostic deployment. CloudBlue Commerce can be deployed in public or on-premises clouds.
Note: Installations with CloudBlue Commerce 20.5 or earlier may contain services that are EOLed in CloudBlue Commerce 21.0. For an installation that has some of those services, a separate transition plan must be prepared.
Backward Compatibility
N/A
Activation
To enable this feature, you must upgrade your installation as described in the Upgrading CloudBlue Commerce from 20.5 to 21.0 guide.
Known Limitations
N/A
Learn More
For more details, refer to the CloudBlue Commerce Deployment guide.
End of Life in This Version
Classic Deployment
As of CloudBlue Commerce 21.0, the Virtual Machine-based platform deployment is no longer supported. CloudBlue Commerce must be deployed in a cloud-native architecture.CCPv1 and Hosting CP
As of CloudBlue Commerce 21.0, CCPv1 and the Hosting CP are no longer supported. Your customers must use the UX1 Panel for Customers instead.
WebHosting Linux (formerly NG)
As of CloudBlue Commerce 21.0, WebHosting Linux (formerly NG) is no longer supported. You must migrate your customers to Hostopia.
WebHosting Plesk
As of CloudBlue Commerce 21.0, WebHosting Plesk is no longer supported. You must migrate your customers to Hostopia.
Cloud Infrastructure Automation
As of CloudBlue Commerce 21.0, Cloud Infrastructure Automation module is no longer supported. Before upgrading to CloudBlue Commerce 21.0, service providers that have this module on their installations must remove it.
Online Store
As of CloudBlue Commerce 21.0, Online Store is no longer supported. Your customers must use UX1 Marketplace instead. UX1 Marketplace is a space where registered resellers and customers can buy products and services. It also provides a public storefront where prospective customers can review the product catalog and buy your products through a self-service portal.
MySQL Nodes on CentOS 6
As of November 30th, 2020, CentOS 6 reached its EOL date and is no longer supported by CloudBlue Commerce. You must migrate your MySQL database servers from CentOS 6 to CentOS 7, as described in this article.
Linux Mail Hosting
As of CloudBlue Commerce 21.0, the Linux Mail Hosting module (qmail) is no longer supported.
Service providers that do not use the module must remove it from their installations before upgrading to CloudBlue Commerce 21.0. The instructions on how to do this are provided in this article.
Service providers that want to keep mailboxes of the module to migrate them to a third-party mail service must detach the module from their installations before upgrading to CloudBlue Commerce 21.0. The instructions on how to do this are provided in this article.
Hosted Exchange 2013/2016
As of CloudBlue Commerce 21.0, the Hosted Exchange 2013/2016 module is no longer supported. Before upgrading to CloudBlue Commerce 21.0, service providers that have this module on their installations must remove it by using these instructions.
BIND
As of CloudBlue Commerce 21.0, the existing implementation of the BIND service is replaced with a new implementation. For details, see the DNS Hosting Services guide.
C++ Domain Plugins and SDK
Starting from CloudBlue Commerce 21.0, all domain registrar plugins that used older technology developed in C++ are discontinued:
- AusRegistry
- Bottle
- DistributeIT
- DKHostmaster
- DNSbe
- DomiNIC
- Enom
- Epnic
- EPP Registrar
- EURid
- GoDaddy
- InterNetX
- Irelanddr
- Joker
- KazNic
- MelbourneIT
- Nominet
- OpenSRS
- RuCenter
- SIDN
- UniForum
- WebNIC
- Whois
To ensure the smooth operation of domain registration services, we strongly recommend that you migrate all domains and TLD zones from the older plug-ins to new PHP plugins. Learn more in this article.
C++ SSL Plugins and SDK
As of CloudBlue Commerce 21.0, the C++ SSL plugins and SDK are no longer supported.
There are three options for providers with active certificates:
If the provider plans to upgrade to CloudBlue Commerce 21.0 and continue selling SSL certificates, the provider needs to develop a standalone APS application for selling SSL certificates for specific CAs.
If the provider plans to upgrade to CloudBlue Commerce 21.0 and stop selling SSL certificates, existing subscriptions can be canceled in CloudBlue Commerce, while a certificate will still be valid until its expiration date. The end customer will be able to obtain a certificate only from the email that was sent by the CA when the certificate was issued.
If the provider wants to continue selling SSL certificates without developing an APS application, the provider can keep using CloudBlue Commerce 20.5 while the SSL certificate selling service is still needed.
C++ Payment Plugins and SDK
As of CloudBlue Commerce 21.0, the C++ Payment plugins and SDK are no longer supported. C++ Payment plugins must be replaced with alternative ones based on the PHP Payment SDK. For additional information on the PHP Payment SDK, refer to the Payment Plug-in SDK Guide (PHP).Payment Cards Cannot Be Stored, Related Payment Plugins Are Not Supported
Starting with this release, payment card data can no longer be stored in CloudBlue Commerce. Now all payment cards are stored as tokens.
The following related payment plugins are no longer supported:
- ASSIST
- Bank Giro
- BBVA
- Chase Paymentech
- Paygate South Africa
- Paypal Pro
- Paypal Standard
- Quickpay
- Realex
- SHVA
- World Pay
Backward Compatibility
Payment methods that worked through these plugins before the upgrade must be substituted by other payment methods.
Activation
No actions are required to enable this feature. It is enabled automatically after the upgrade.
Known Limitations
N/A
Dummy Gate (DUMMYGATE)
As of CloudBlue Commerce 21.0, DUMMYGATE is no longer supported. The KB article with the solution will be provided.Key Administrator Service Gate (KAGATE)
As of CloudBlue Commerce 21.0, KAGATE is no longer supported. Before the upgrade, KAGATE subscriptions must be terminated.APS 1.x Applications
As of CloudBlue Commerce 21.0, the APS 1.x applications are no longer supported. The KB article with the solution will be provided.C++ Fraud Screening Plugins and SDK
As of CloudBlue Commerce 21.0, C++ fraud screening plugins are no longer supported. As a substitute for C++ fraud screening plugins, PHP fraud screening plugins must be developed using the PHP fraud screening SDK. For assistance, please contact your Technical Account Manager.
Internet Explorer
Microsoft stops support for IE11 on August 17, 2021. Starting from CloudBlue Commerce 21.0, we also stop supporting IE access to our panels and suggest that customers switch to other browsers, such as Edge, Chrome or Firefox.PostgreSQL 9.6
PostgreSQL announced that the EOL of version 9.6 is November 11, 2021. Starting from CloudBlue Commerce 21.0, we stop supporting it as well. Instead, we suggest that customers upgrade to version 11.5. The upgrade instructions are provided in this KB article.Custom Billing Containers
Custom billing containers are not supported in CloudBlue Commerce 21.0. If you need assistance with such containers, reach out your account manager.
Miscellaneous Changes
Time Zone Configuration in the Cluster
Now, the time zone used for synchronization of the CloudBlue Commerce components is configured in the Kubernetes cluster.
Learn More
For more details, refer to the Updating General Component Settings section.
The Ability to Create a Default Customer Class Template
To streamline the reseller onboarding process and reduce the number of configuration steps, it is now possible to specify the template for the reseller Customer Class. Using this template, you can, for example, select the Generate Billing Order per Subscription option for customers of all new resellers.
Backward Compatibility
If no customer class template is specified, the system behavior does not change.
Activation
No actions are required to enable this feature. It is enabled automatically after the upgrade.
Known Limitations
None.
Learn More
For more details, refer to Adding a Reseller Service Template.
The Ability to Transfer a Customer Account Between Resellers with a Different Currency
Now, a provider can transfer a customer account to another reseller who uses a currency that differs from the original reseller's.
Backward Compatibility
N/A
Activation
No actions are required to enable this feature. It is enabled automatically after the upgrade.
Known Limitations
Refer to Account Transfer Limitations.
Learn More
For more details, refer to Account Transfer Requirements and Transferring a Customer Account to Another Distributor.
Modification of Activation Parameters When Placing a Change Order
Now, it is possible to update existing activation parameters or add new ones when placing a change order using the new property changeParameters.
Attributes in Change, Renewal and Cancellation Orders
In addition to the sales order type, the attributes property can now be specified when creating a change, renewal, or a cancellation order. Values of the attributes with the Propagate to Subscription option set to Yes will be updated on the subscription.
Unique Product IDs for Billing Resources
To simplify reconciliation, stock keeping, and reporting, providers now can use automatically assigned unique Product IDs for Billing resources they sell. Product IDs compensate for the deficiencies of MPNs, which may not be unique per resource or may be missing for some resources.
For providers who have several CloudBlue Commerce installations, automatically assigned Product IDs are a simple and reliable way to identify the same product across several installations. For more information, please see Product ID Synchronization Across Installations.
Backward Compatibility
After the feature is activated, both new and existing Billing resources will be automatically assigned unique Product IDs.
Activation
To use the feature:
- Activate the Product ID functionality on the necessary installation.
- Configure Product ID Template.
Known Limitations
None.
Learn More
Product ID Synchronization Across CloudBlue Commerce Installations
Providers who have several CloudBlue Commerce installations now can ensure that product catalog resources they sell have the same automatically assigned Product IDs on all their installations. This is done with the help of the Product Configuration Manager's export-import functionality, which now supports Product ID synchronization.
During Product ID synchronization, all resources are synchronized, including resources automatically installed during the deployment of respective APS applications.
Backward Compatibility
The existing Product Configuration Manager's export-import functionality is not affected.
Activation
To use the feature:
- Activate the Product ID functionality on the source and target installations.
- Assign unique permanent product IDs to billing resources on your source installation.
- Using PCM, transfer resource configurations from your source installation to your target installations.
Known Limitations
None.
Learn More
The Billing Date Alignment
As of CloudBlue Commerce 21.0, the billing date is aligned with the subscription start date. For some current subscriptions, this change may result in the next billing date changing and two invoices being generated for one billing period.
Report Data Set Extended with New Fields
The RDE “Provisioned orders” dataset has been extended with several new fields:
Charge information
- RESELLER_ACTUAL_DETAIL_START_DATE, CUSTOMER_ACTUAL_DETAIL_START_DATE, and END_CUSTOMER_ACTUAL_DETAIL_START_DATE. They represent a first date when a service can be used.
- RESELLER_ACTUAL_DETAIL_END_DATE, CUSTOMER_ACTUAL_DETAIL_END_DATE, and END_CUSTOMER_ACTUAL_DETAIL_END_DATE. They represent a last date when a service can be used.
- RESELLER_DISCOUNT_BREAKDOWN, CUSTOMER_DISCOUNT_BREAKDOWN, and END_CUSTOMER_DISCOUNT_BREAKDOWN. Now, when several discounts are applied to an order detail, such a scenario is covered.
Invoice information
- RESELLER_ORIGINAL_INVOICE_ID, CUSTOMER_ORIGINAL_INVOICE_ID, and END_CUSTOMER_ORIGINAL_INVOICE_ID. They represent ID of an original invoice to which a correction was applied.
- RESELLER_AR_DOC_TYPE, CUSTOMER_AR_DOC_TYPE, and END_CUSTOMER_AR_DOC_TYPE. They represent the type of document. For example, Credit Memo.
Features and Changes Available as Hotfixes for CloudBlue Commerce 20.5
A New Component: SimpleAPI
SimpleAPI is a CloudBlue Commerce component that introduces an easy-to-use REST API that can be used by resellers to integrate their own IT systems without needing extensive knowledge of technical CloudBlue Commerce platform concepts.
SimpleAPI is based on the Open API Specification, which allows developers to quickly generate code samples, test their integration scenarios, and deploy their integration.
The Usage Resource Consumption Type
A new parameter, which is called the consumption type, is now introduced for a resource. This parameter can have two values: Unspecified and Usage.
The Usage resource type is intended for usage-based services and allows you to set up only the overuse fee to non-zero, while other fees are set to zero. You can use the resource of the Usage consumption type to configure postpaid (measurable, usage-based) resources because it does not allow you to change the additional limit of a resource in a subscription.
Backward Compatibility
After the upgrade, all resources will have the Unspecified consumption type. For information on whether it is possible to set the Usage consumption type for a resource, refer to this KB article.
Activation
No actions are required to enable this feature. It is enabled automatically after the upgrade.
Known Limitations
None.
Learn More
For more details, refer to Creating or Editing Resources and Notes on Usage Consumption Type of a Resource.
A New Order Type: Transfer Order
Now, when a subscription is being transferred between customer accounts or a customer account is being transferred between distributors, an order of a new type, transfer order, is created.
Backward Compatibility
Transfer orders are created only for new transfers. Transfer orders are not created for transfers that occurred before the upgrade.
Activation
No actions are required to enable this feature. It is enabled automatically after the upgrade.
Known Limitations
None.
Learn More
- Transferring Subscriptions Between Customer Accounts
- Transferring Customer Accounts Between Distributors
Asynchronous Subscription Synchronization Processing
When subscriptions are synchronized with a service plan, a separate task to update each subscription is created and such tasks are processed asynchronously by Billing.
Backward Compatibility
For the business user, the system behavior remains the same.
Activation
No actions are required to enable this feature. It is enabled automatically after the upgrade.
Known Limitations
None.
Learn More
End of Life
Upcoming End of Life
XML-RCP API
XML-RPC API is classified as private API in the v21 release line of CloudBlue Commerce. New platform features are not supported. The documentation has been unpublished and is no longer available.
In the v21 release line, API endpoints remain active and API methods keep working in backward-compatible mode. Existing integrations will also keep working, but new ones must not be built using this API.
In the v22 release line, XML-RPC API will reach its end-of-maintenance, end-of-support, and end-of-life states. API endpoints will be shut down, all integrations will stop working.
Transition path: Existing integrations through XML-RPC API must be re-done to utilize more modern CloudBlue Commerce REST API. Providers may take action themselves, hire a 3rd-party solution, or engage CloudBlue Professional Services for the development project.
Resolved Issues
Product Configuration Manager
OA-22104
Issue Summary: The process of configuration importing was stuck in PCM.
Fix Description: The issue has been fixed by optimizing the importing algorithm and removing unneeded recursion during file import.
OA-20973
Issue Summary: Deselecting a template during import did not prevent service plans from being updated in PCM.
Fix Description: Service plans are now filtered according to previously selected service templates.
OA-20790
Issue Summary: During Office 365 mass plan editing, the Plan Category assignment was not saved for all plans.
Fix Description: The code has been fixed to resolve this issue.
OA-20715
Issue Summary: Unable to edit multiple plans at once when one plan was already edited previously in PCM.
Fix Description: Comparison of plans is now more accurate according to the Billing Terms parameters. Plans with the same or default values can be edited together now.
OA-20611
Issue Summary: Unable to configure MPN settings for an application.
Fix Description: The MPN settings screen now fetches the application schema information from the latest application version.
OA-20219
Issue Summary: In PCM, "Show in CP" and "Show in Store" checkboxes did not display in the "Edit Plan" screen.
Fix Description: The "Show in CP" and "Show in Store" checkboxes have been added to the screen.
OA-20176
Issue Summary: getWizardData logging took too long in PCM.
Fix Description: Extended logging was used during data processing. The issue has been fixed by removing it. Caching has been added to reduce requests to the BUS from the UI.
OA-20175
Issue Summary: The same package is requested many times in PCM.
Fix Description: Extended logging was used during data processing. The issue has been fixed by removing it. Caching has been added to reduce requests to the BUS from the UI.
OA-20095
Issue Summary: Wrong options were displayed in the "Service Plans" step in PCM for Microsoft 365 plans.
Fix Description: The "New/Updated" column in the "Service Plans" step has been separated.
OA-22653
Issue Summary: The "Notification About Service Provisioning" field could not be synchronized for a reseller.
Fix Description: The "Notification About Service Provisioning" plan property is now synchronized during reseller product catalog synchronization.
OA-22262
Issue Summary: The BSS resource synchronization priority was ignored for large synchronization queues.
Fix Description: An APS resource for a subscription is now created before all other plan updates.
OA-21918
Issue Summary: Subscriptions were not displayed in the "Subscription" tab in UX1.
Fix Description: The mistakenly added "catalog" parameter has been removed from the configuration for Service Plans. It was also checked that there are no other persistence objects configured together with the "catalog" parameter.
OA-21040
Issue Summary: The Product Inventory list was not displayed if using PostgreSQL 9.6.
Fix Description: Product Inventory now works with PostgreSQL 9.6.
OA-20762
Issue Summary: Uploading costs for O365 failed with the error: "value too long for type character varying(40)".
Fix Description: The error on the attempt to import costs for resources with an MPN of more than 40 symbols is now fixed.
OA-18964
Issue Summary: Parallel pc/sales-categories requests could fail with the Hibernate exception.
Fix Description: The @Transactional annotation has been removed from the AccountManagementProxyBean.getPbaVendorAccount(BillingApiInvocationContext ctx) method to avoid locks when trying to read and write the same entity in different methods and different transactions. This fixes the issue when a reseller could not access the UX1 MP cart content.
OA-18949
Issue Summary: Running autoconf.py for populating resources for a new instance of MS 365 failed with the error: "Maximum number of workers registered".
Fix Description: The "Maximum number of workers registered" issue that happened during the massive invocation of XmlRpc API methods has been fixed.
OA-17708
Issue Summary: Almost 25% of Renewal Order generation time during the DBP was used by bPlanRate::getPlanRateForPeriod.
Fix Description: Performance of the daily billing process is now improved.
Application Packaging Standard
OA-23479
Issue Summary: APS 1.x application screens could get stuck when opened for the first time.
Fix Description: Specific values of the "Web-analytics Integration code" brand setting were causing legacy services to misbehave on the first render after logging in. This is now fixed.
OA-23252
Issue Summary: Apache in a branding Pod consumed too much memory.
Fix Description: The footprint of the UI deployment has been reduced for better utilization of resources.
OA-23164
Issue Summary: Unable to edit values for an application instance at the "Settings" screen.
Fix Description: The screen for application instance settings management is now fixed.
OA-21982
Issue Summary: Unable to add a PO locale file into APS applications.
Fix Description: The improper APS package version comparison that led to an internal error has been fixed.
OA-21961
Issue Summary: The UX1 interface took too long to load.
Fix Description: Obsolete data transmission that was slowing the system down has been removed.
OA-21717
Issue Summary: The APS tab was visible in UX1 after a subscription is destroyed.
Fix Description: The tab for the APS application in a terminated subscription is not displayed now.
OA-21497
Issue Summary: It took too much time to have a ready UI Pod.
Fix Description: The startup time for branding-ui Pods is now increased.
OA-21343
Issue Summary: A customer's staff members were displayed in the reseller's user list in UX1.
Fix Description: The security link update when deleting a role has been fixed to resolve this issue.
OA-21334
Issue Summary: UI performance was decreased due to frequent requests to APS Booster.
Fix Description: The APS Booster type cache is now improved to reduce redundant resets. APS2 request processing has been greatly improved.
OA-20862
Issue Summary: Unable to import an APS localization package.
Fix Description: The empty list of APS resource types is not parsed now when importing a language package.
OA-20704
Issue Summary: The process of changing a subscription owner could take too much time.
Fix Description: The process of changing a subscription owner has been optimized.
OA-20509
Issue Summary: Unable to import an APS package.
Fix Description: The length of the auto-generated icon name has been reduced to resolve this issue.
OA-20445
Issue Summary: A slow RQL query caused navigation issues when opening UX1 Cart.
Fix Description: When selecting service template resources, all APS type hierarchy was included in an underlying query, which caused PostgreSQL to use sub-optimal query plans. This issue has been fixed by optimizing RQL queries that scan resources of all existing APS types.
OA-19603
Issue Summary: The "Application resource subscriptions and total limit" periodic task failed.
Fix Description: The SQL error related to the length of the IN condition input parameter list limit is now fixed.
OA-19035
Issue Summary: Slow CORBA periodic task could block other tasks.
Fix Description: CORBA periodic tasks has been moved to a separate queue. This greatly reduces delays on usual tasks caused by slow CORBA periodic tasks.
OA-18976
Issue Summary: API calls to place an order failed with the error: duplicate key value violates unique constraint "on_screen_notification_params_unq0".
Fix Description: Improper hashing and equality check of managed entities for on-screen notifications that led to a database-level constraint violation has been fixed.
OA-18934
Issue Summary: The Microsoft 365 menu item was not displayed in CCPv1 and UX1.
Fix Description: Unnecessary client dependency that led to JVM classloader errors related to incompatible code versions during remote EJB calls has been fixed to resolve this issue.
OA-18694
Issue Summary: An RQL query executed incorrectly in case of a duplicate property.
Fix Description:
There was an error in the APS RQL processor related to when an APS property in schemas of different applications was declared with different types (string and integer). The issue is now fixed and an integration test for this case is created.
OA-18541
Issue Summary: The other reseller's skins were visible in the settings menu.
Fix Description: OwnerId has been added when registering a skin package to resolve this issue.
OA-22103
Issue Summary: For some APS 1.x applications, resource counter values were not displayed on the application instance screen in case of large numbers.
Fix Description: The application instance screen is now displayed without errors.
General
OA-13559
Issue Summary: Disabled TLSv1.1 protocol was enabled during upgrade to 20.4.
Fix Description: This issue has been fixed by removing {{-TLSv1 -TLSv1.1 }} from lists of SSH protocols in modules/updater/bssupdater/bsstools/settings.py.
OA-20858
Issue Summary: The Helm version is not detected on clean installation.
Fix Description: The exception is now fixed. Clean installation with Helm 3 works correctly.
OA-20432
Issue Summary: Temporary files in the a8n-operator Pod were not removed, which caused disk overload.
Fix Description: Temporary files are now cleaned correctly in the a8n-operator Pod.
OA-14582
Issue Summary: The Dojo Toolkit version was outdated.
Fix Description: Dojo Toolkit has been updated to the latest version.
OA-6108
Issue Summary: The version of jQuery was outdated.
Fix Description: The jQuery dependency has been updated to the latest version.
Account and Plan Configuration
OA-15199
Issue Summary: Renaming a subscription in UX1 made the Next Billing Date setting incorrect.
Fix Description: The subscription Next Billing Date setting is not changed now after the subscription name is changed.
OA-23063
Issue Summary: The IDP password policy was not used in the password generator in UX1.
Fix Description: The password policy has been passed to the password-generating widget in UX1.
OA-21103
Issue Summary: An account could be created using APS API without a region or with a wrong region.
Fix Description: Now, when creating an account using APS API, a valid region for a country must be added.
E-Commerce
OA-19028
Issue Summary: The preauthorization charge refund failed even though the initial preauthorization charge was successful.
Fix Description: When a user clicks the "X" button after entering the card details (the "Add" button is clicked), then the "Declined by Customer" action is not sent now.
OA-21628
Issue Summary: An index for the Reseller Transaction table query was required.
Fix Description: The additional index "ResellerTrans__EndCustDocID" has been added to the "ResellerTrans" table in the database to improve query performance.
OA-21372
Issue Summary: Unnecessary payment methods were listed in the EARM payment confirmation pop-up window.
Fix Description: The list of forbidden payment methods has been added to EARM.
OA-19883
Issue Summary: A suboptimal SQL query affected DB performance.
Fix Description: Top SQL queries consuming most of the resources found by DBA experts are now optimized.
Billing
OA-22042
Issue Summary: Additional Billing Orders were generated for an account.
Fix Description: The possibility of charge duplication under a significant load is now removed.
OA-22029
Issue Summary: The order detail description was generated with the system locale instead of the customer locale.
Fix Description: The detail description is now generated in the customer locale.
OA-20643
Issue Summary: The "Refund for Plan" order detail was not localized.
Fix Description: The order detail localization is now fixed.
OA-19578
Issue Summary: The VRD Price Management screen could not be accessed.
Fix Description: There was an error caused by fixing and refactoring related to the OA-18694 issue. The issue and integration tests are now fixed for this case.
OA-19476
Issue Summary: A VRD Billing Order was not generated while an account is in Credit Hold.
Fix Description: Now, the restriction for placing orders while an account is in Credit Hold is lifted.
OA-19231
Issue Summary: It took too much time to open the order screen.
Fix Description: SQL queries have been improved to resolve this issue.
OA-16678
Issue Summary: A CH order with only one item could be canceled by DBP without reseller transactions being removed.
Fix Description: Reseller transactions for canceled orders are now removed.
OA-15350
Issue Summary: Users of Microsoft Outlook could see both reseller and customer details in invoices grouped by subscription.
Fix Description: Users of Microsoft Outlook now see reseller or customer details in invoices grouped by subscription correctly, according to the account type. This issue has been fixed by changing the message template for invoices. CSS styles have been modified to satisfy the rules of the Microsoft Outlook client.
OA-22811
Issue Summary: An outdated payment screen was displayed when attempting to pay an invoice in EARM.
Fix Description: The outdated payment screen is now replaced with a new one that calls the EARM back end.
OA-22230
Issue Summary: An order with costs transactions got stuck in the Check Reseller Balance state if the provisioning was completed the next day or later.
Fix Description: Orders for subscriptions based on a service plan integrated with Rating Engine in the Costs Only mode could get stuck after the provisioning was finished the next day or later when attempting to delete the cost transaction. Now, Billing does not try to delete the cost transaction; it is recalculated by Rating Engine.
OA-22082
Issue Summary: The @@InvoicedCustomerServiceEndDate@ placeholder was incorrectly calculated.
Fix Description: The new placeholder "Last Day of invoiced customer service" has been added and is used in the Reseller Invoice Template now.
OA-22049
Issue Summary: A delivery line with its start date in the future could be created if next billing date was invalid.
Fix Description: Sometimes, a BBP subscription could be paid by some date that is after the next billing date, and the first upgrade or downgrade order cut all resource delivery lines after the next billing date and kept them unchanged. Any following change order led to a resource amount error. Now, such a cut deliver line is marked as Hold, and a customer gets refunded by the nearest order.
OA-22003
Issue Summary: GetOrderDataPackage_API did not support Billing Orders based on VRD charges.
Fix Description: GetOrderDataPackage_API did not return cost transactions for Billing Orders being generated from VRD charges. This issue has been fixed.
OA-21329
Issue Summary: A reseller was not billed if TopUp Options settings were improperly configured.
Fix Description: The issue has been fixed.
OA-19918
Issue Summary: An incorrect tax rate was displayed in UX1 when placing a Renewal Order.
Fix Description: To resolve this issue, the tax calculation is now uses the subscription expiration date instead of the current system date.
Control Panel
OA-20988
Issue Summary: The code in the UI navigation that creates dynamic items was not effective.
Fix Description: The UI navigation performance has been optimized.
OA-20281
Issue Summary: Navigation issues when opening UX1 Cart.
Fix Description: The required placeholder has been added to the list of exceptional placeholders for system applications in the navigation framework.
Platform
OA-21960
Issue Summary: A reseller order with many details was not billed.
Fix Description: Tax calculation for orders with a significant amount of details (> 3,000) is now possible.
Miscellaneous
OA-21378
Issue Summary: Unable to display the "Not invoiced Purchases" section in UX1 for Resellers.
Fix Description: The issue has been fixed by changing the Java class "ResellerTrans.java" field of "discountPercent" type from the primitive "Double" type, which cannot be set to null, to the boxed "Double" type, which is nullable.
OA-20185
Issue Summary: The "Application priority" and "Application rule" discount-related fields appeared if Rating Engine was not enabled.
Fix Description: The discount options "Application priority" and "Application Rule" are now available in the classic "Marketing" panel with the "FEA_UseClassicMarketingFallbackMode" feature enabled in the "Features" table in the BSS database.
OA-19529
Issue Summary: A promotion price was not displayed in the public UX1 Marketplace.
Fix Description: Prices in the public UX1 Marketplace are now displayed with applicable promotions.
OA-19381
Issue Summary: A subscription could not be renewed when a Promotion by One-Time Promo Code was no longer valid.
Fix Description: A customer now can place a renewal order if the previously used Promotion by One-Time Promo Code is not valid.
OA-22882
Issue Summary: Order processing took too long due to many unprocessed events in the Billing task manager.
Fix Description: The memory management issue that slowed down the daily billing process of processing large orders is now fixed.
OA-20609
Issue Summary: The scheduler process sometimes consumed too much memory.
Fix Description: The scheduler "Out of memory" error, which happened after several attempts to import ConfSync data, has been fixed.
Documentation
DOC-2183
Issue Summary: There was a wrong link to documentation in PCP version 20.5.
Fix Description: A redirect has been configured for the URL set for the Documentation button in the UI.
DOC-2168
Issue Summary: The db_precheck script requirements contained incorrect information.
Fix Description: The "Performing the CloudBlue Commerce Database Pre-check" section of the Upgrade Workflow guide has been updated.
DOC-2149
Issue Summary: Windows VM with the SYSPREP configuration description needed to be updated.
Fix Description: The "Creating Windows VM OS Template" section of the Cloud Infrastructure Automation Deployment Guide has been updated.
DOC-2089
Issue Summary: There was no information that Native Integration does not support prorated agreements.
Fix Description: The "Known limitations" section of the Native Integration guide has been updated.
DOC-2087
Issue Summary: Information on how to clean up bloated ChangeNotifications queue was missing.
Fix Description: The following KB article has been created: https://cloudblue.freshdesk.com/support/solutions/articles/44002209791.
DOC-2009
Issue Summary: There was no information about the log-in screen locale in the Identity Service guide.
Fix Description: The respective note has been added to the "About the Identity Service" section of the Identity Service guide.
DOC-2005
Issue Summary: There was incorrect information about Operating Units in PCM documentation.
Fix Description: The "Configuring the System Setting' section of the "Product Configuration Manager" chapter in the Billing Provider guide has been updated.
DOC-1949
Issue Summary: Documentation incorrectly stated that UX1 MP 5.2 is not compatible with CloudBlue Commerce 20.4.
Fix Description: Documentation was updated.
DOC-1941
Issue Summary: Information about vendor contract ID configuration needed to be updated.
Fix Description: The Configuring Vendor Contract IDs procedure is now updated.
DOC-1931
Issue Summary: The GDPR upgrade command description needed to be enhanced.
Fix Description: The "Updating the GDPR Application" section of the GDPR Compliance guide has been updated.
DOC-1841
Issue Summary: Additional information about the Next Billing Date setting was required.
Fix Description: The "The Daily Billing Process" section of the Billing Provider guide has been updated with the respective note.
DOC-1823
Issue Summary: The RDE documentation contained incorrect information about the “Provisioned orders” dataset.
Fix Description: The "Fields in the “Provisioned orders” Dataset" section in the Reporting and Data Export guide has been updated.
DOC-1801
Issue Summary: Additional information about changing Statement Date was required.
Fix Description: The "Assigning Statement Cycle to Customer and Changing Statement Date" section in the Billing Provider guide has been updated.
DOC-1795
Issue Summary: There was incorrect information about the PostgreSQL version in Native Integration service database pre-deployment requirements.
Fix Description: The "Preparing the Native Integration Service Database" section of the Native Integration guide has been updated.
DOC-1602
Issue Summary: The "Collect resources usage after subscription cancellation (days)" resource was not described in Azure NCE Upgrade documentation.
Fix Description: Documentation was updated.
DOC-1303
Issue Summary: UX1 Marketplace release notes did not mention UI changes.
Fix Description: Documentation was updated.
DOC-1145
Issue Summary: Information that a user with the lowest ID number is taken for impersonation was not described.
Fix Description: Documentation was updated.
DOC-1605
Issue Summary: Keystore files were not copied after the BA node migration to Azure.
Fix Description: The procedure to resolve this issue has been described in this KB article.