Release notes for Red Hat Decision Manager 7.11

Red Hat Decision Manager now provides support for the following Red Hat build of Kogito microservices that you can use to build cloud-native applications that adapt to your business domain and tooling:

For more information about getting started with Red Hat build of Kogito in Red Hat Decision Manager, see Getting started with Red Hat build of Kogito in Red Hat Decision Manager.

Red Hat Decision Manager now supports Red Hat build of Kogito JVM Quarkus runtime images.

For more information, see Getting started with Red Hat build of Kogito in Red Hat Decision Manager.

Red Hat Decision Manager now includes Red Hat build of Kogito builder images for Red Hat build of Quarkus and Spring Boot.

For more information, see Getting started with Red Hat build of Kogito in Red Hat Decision Manager.

You can configure Smart Router (KIE Server Router) for Transport Layer Security (TLS) support to allow HTTPS traffic. In addition, you can disable insecure HTTP connections to Smart Router. For more information, see the "Configuring Smart Router for TLS Support" section in Installing and configuring Red Hat Decision Manager in a Red Hat JBoss EAP clustered environment

It is now possible that the the BatchExecutionHelperProviderImpl.newXStreamMarshaller() method creates a secure XStream instance. The XStream instance accepts only pre-defined KIE classes in payloads by default. If you use the XStream instance created by the method, you must add allowed classes. For example, add domain model classes in your application code or you receive the ForbiddenClassException exception.

final BatchExecutionHelperProviderImpl batchExecutionHelperProvider = new BatchExecutionHelperProviderImpl();
XStream xstream = batchExecutionHelperProvider.newXStreamMarshaller();
String[] allowList = new String[]{
    "org.example.model.Person",
    "org.example.model.Company"
};
xstream.addPermission( new WildcardTypePermission( allowList ) );

Support for Red Hat Decision Manager on IBM WebSphere Application Server, Oracle WebLogic Server, Red Hat JBoss Web Server, and Apache Tomcat is now in the maintenance phase. Red Hat will continue to support Red Hat Decision Manager on these platforms with the following limitations:

In the future, Red Hat might direct customers to migrate to new platforms and product components that are compatible with Red Hat’s hybrid cloud strategy.

Both OptaPlanner 7 and OptaPlanner 8 are included with Red Hat Decision Manager 7.11, but OptaPlanner 7 is deprecated and might be removed in a future release. For information about migrating your OptaPlanner 7 projects to OptaPlanner 8, see Upgrading your Red Hat build of OptaPlanner projects to OptaPlanner 8.

The following OptaPlanner tooling in Business Central is part of OptaPlanner 7. It is deprecated and might be removed in a future release.

Support for JDK 8 is deprecated from Red Hat Decision Manager and might be removed in a future release.

For a complete list of supported JDK configurations, see Red Hat Decision Manager 7 Supported Configurations.

The legacy kie-pmml dependency was deprecated with Red Hat Decision Manager 7.10.0 and will be replaced in a future Red Hat Decision Manager release. For more information, see Designing a decision service using PMML models.

Support for integration with the OSGi framework is deprecated in Red Hat Decision Manager. It does not receive any new enhancements or features and will be removed in a future release. The decision and process engine integration with the OSGi framework is currently incompatible in Fuse version 7.8. If you intend to use the OSGi framework, continue to use Red Hat Decision Manager version 7.9 with Fuse version 7.7 until Fuse version 7.9 is available and certified.

The Red Hat Decision Manager RuleUnit API is now deprecated due to incompatibility with the Kogito RuleUnit API.

The legacy Test Scenarios tool was deprecated in Red Hat Decision Manager version 7.3.0. It will be removed in a future Red Hat Decision Manager release. Use the new Test Scenarios designer instead.

From Red Hat Decision Manager version 7.5, images and templates for Red Hat OpenShift Container Platform 3.x are deprecated. The deprecated images and templates are not supported with new features but remain available until the end of Red Hat OpenShift Container Platform version 3.x support. For more information about the full support lifecycle phase for Red Hat OpenShift Container Platform version 3.x, see Red Hat OpenShift Container Platform Life Cycle Policy (non-current versions).

Consider deploying Red Hat Decision Manager using the operator on Red Hat OpenShift Container Platform 4.x.

You can deploy a high-availability Red Hat Decision Manager authoring environment on Red Hat OpenShift Container Platform 4.x using the operator.

An installer wizard is provided in the OpenShift operator for Red Hat Decision Manager. You can use the wizard to deploy a Red Hat Decision Manager environment on Red Hat OpenShift Container Platform with the operator.

You can perform the following tasks to customize the Business Central authoring perspective:

Workaround: None.

Workaround: None.

Workaround: None.

Steps to reproduce:

Workaround: None.

Steps to reproduce:

Expected result: Validation of the XLS table succeeds.

Actual result: Validation of the XLS table fails.

Workaround: None.

Steps to reproduce:

Expected result: The guided decision table sorting functionality works correctly in the decision table graph.

Actual result: The guided decision table sorting functionality does not work correctly.

Workaround: None.

Workaround: None.

Workaround: None.

Steps to reproduce:

Workaround: Keep a single folder inside your workspace. If you want to work on multiple projects, open the projects in separate VSCode instances.

Steps to reproduce:

Workaround: The transitive decisions must be part of the encapsulatedDecisions section of the modeled decision service.

Steps to reproduce:

Workaround: Keep a single occurrence of the decision component for each DRD.

Steps to reproduce:

Expected result: The DMN editor provides helpful suggestions when you are writing literal expressions.

Actual result: The DMN editor does not parse any helpful suggestions when you are writing literal expressions.

Workaround: None.

Steps to reproduce:

Expected result: The DMN editor suggests correct functions for an addition expression.

Actual result: The DMN editor suggests functions that return list instead of a number.

Workaround: None.

Steps to reproduce:

Expected result: The DMN editor recognizes variables when you parse the number type to a literal expressions.

Actual result: The DMN editor fails to recognize variables.

Workaround: None.

Steps to reproduce:

Expected result: The DMN editor recognizes the duration expression.

Actual result: The DMN editor fails to recognize the duration expression and suggests string functions.

Workaround: None.

Steps to reproduce:

Expected result: The DMN editor recognizes the date expressions.

Actual result: The DMN editor fails to recognize the date expression and suggests string functions instead of date functions.

Workaround: None.

Steps to reproduce:

Expected result: The DMN editor offers related suggestions when you parse a negated boolean expression.

Actual result: The DMN editor fails to provide related suggestions when you parse a negated boolean expression.

Workaround: None.

Steps to reproduce:

Expected result: When you upload an asset for KogitoBuild, the Red Hat build of Kogito S2I image generates the project using kogito-quarkus-dm-archetype:1.5.0.redhat-00001.

Actual result: When you upload an asset for KogitoBuild, the Red Hat build of Kogito S2I image generates the project using kogito-quarkus-archetype:1.5.1-SNAPSHOT.

Workaround: None.