Upgrade to Black Cat 16.x Troubleshooting

The following areas might be a source of issues when starting to use the version Black Cat 16.x, so please make yourself familiar with this section.

TechOps

Removed Configurations

Configuration	Change	Action Required
`migrations.db.enforceValidateDisabledOnMigrate`	Configuration has been removed.	Configuration should be removed from all k8s configs.
`migrations.server.enforceValidateDisabledOnMigrate`	Configuration has been removed.	Configuration should be removed from all k8s configs.
`formulaEngine.script.sandboxHttpClient.sharedConnectionPool.trustAllCertificates`	Configuration has been removed.	Configuration should be removed from all k8s configs. If the current configuration contains this property set to `true`, ensure that all your Groovy logic invoking `httpCall()` `asyncHttpCall()` `boundCall()` `boundExternalSystemCall()` includes the properties parameter with the following key–value pair: `"sslTrustAllCertificates": true`. Otherwise, the SSL certificates of the target servers will be validated.

Configuration

Change

Action Required

migrations.db.enforceValidateDisabledOnMigrate

Configuration has been removed.

Configuration should be removed from all k8s configs.

migrations.server.enforceValidateDisabledOnMigrate

Configuration has been removed.

Configuration should be removed from all k8s configs.

formulaEngine.script.sandboxHttpClient.sharedConnectionPool.trustAllCertificates

Configuration has been removed.

Configuration should be removed from all k8s configs.

If the current configuration contains this property set to true, ensure that all your Groovy logic invoking

httpCall()
asyncHttpCall()
boundCall()
boundExternalSystemCall()

includes the properties parameter with the following key–value pair: "sslTrustAllCertificates": true.
Otherwise, the SSL certificates of the target servers will be validated.

Removed Endpoints

Endpoints	Change	Action Required
`system$dbmigrationmanager.*`	Endpoints removed.	Not Applicable.
`system$servermigrationmanager.*`	Endpoints removed.	Not Applicable.
`system$servermigration.dashboardexportrole`	Endpoint removed.	Not Applicable.
`system$servermigration.dashboardrorole`	Endpoint removed.	Not Applicable.

New Events Behavior

New partitions created in version 16.0 will have no Events enabled by default. Events must be enabled manually.
Existing partitions will retain the same Events settings they had in the previous version.
If new Events are created (from the current list of 45 events), they must be manually enabled in any partitions where they are intended to be used.

Analytics

Dashboards

Property Changes

Property	Change	Action Required
`labelTranslation`	The property is now mandatory in the Dashboards.	Property must contain at least one entry, the default translation (using the `""` key). Example: Java `{ "labelTranslations": { "": "Go to Customer Detail View" // by default, if no specific language is provided } }` In version 16.0, the `label` field still exists, but it is no longer stored in the database as a separate value. Instead, it is merged into `labelTranslations` as the default translation. The `label` field will be removed in a future release because it duplicates the default translation, so you should avoid relying on it going forward.
`category`	The property has been removed from the Dashboards.	Not Applicable.

Property

Change

Action Required

labelTranslation

The property is now mandatory in the Dashboards.

Property must contain at least one entry, the default translation (using the "" key).
Example:

Java

{
  "labelTranslations": {
    "": "Go to Customer Detail View" // by default, if no specific language is provided
  }
}

In version 16.0, the label field still exists, but it is no longer stored in the database as a separate value. Instead, it is merged into labelTranslations as the default translation. The label field will be removed in a future release because it duplicates the default translation, so you should avoid relying on it going forward.

category

The property has been removed from the Dashboards.

Not Applicable.

Data Manager

Property	Change	Description
`default`	New property has been introduced.	Field – `isDefault` Class – `DMDataSource` This field applies to Data Sources based on Attributed Objects (Product, Customer, Seller). It is relevant for anyone using DMDataSlice methods, as these methods depend on Data Sources to construct filter conditions. Previously, when multiple Data Sources existed, there was no way to specify which one should be used by such logic. The behavior itself has not changed, existing logic will continue to produce the same results. The outcome will differ only if you explicitly designate a different Data Source as the default.

Property

Change

Description

default

New property has been introduced.

Field – isDefault
Class – DMDataSource

This field applies to Data Sources based on Attributed Objects (Product, Customer, Seller). It is relevant for anyone using DMDataSlice methods, as these methods depend on Data Sources to construct filter conditions. Previously, when multiple Data Sources existed, there was no way to specify which one should be used by such logic.

The behavior itself has not changed, existing logic will continue to produce the same results. The outcome will differ only if you explicitly designate a different Data Source as the default.