Maven archetype support is now available in Business Central. To access this functionality, select the Admin icon in the top-right corner of the screen and select the Archetypes option on the Business Central Settings page. The following list provides a summary of Maven archetypes enhancements:

For more information about archetypes management, see Configuring Business Central settings and properties.

The test scenarios designer in Business Central is now available with the new features supported in Red Hat Decision Manager 7.7.

For more information about test scenarios designer in Business Central, see Testing a decision service using test scenarios.

You can now create a new project in Business Central by importing an empty GitHub or GitLab external repository.

You can now squash multiple commits into a single commit and add the commit to a target branch for a change request. For more information about change requests in Business Central, see Managing projects in Business Central.

When typing a FEEL expression in the boxed literal expression editor, you can now see FEEL functions appear as suggestions that you can apply to complete the expression if required.

The Decision Model and Notation (DMN) designer in Business Central includes the following notable enhancements:

Users can now manage branches and perform Maven action on branches using the REST API:

Return all branches in a specific project and space:

[GET] /spaces/{spaceName}/projects/{projectName}/branches::

Add a specific branch to a specific project and space:

[POST] /spaces/{spaceName}/projects/{projectName}/branches::

Delete a specific branch from a specific project and space:

[DELETE] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}::

Compile a specific branch in a specific project and space. If branchName is not specified, then the request defaults to using the master branch.

[POST] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}/maven/compile::

Install a specific branch in a specific project and space. If branchName is not specified, then the request defaults to using the master branch.

[POST] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}/maven/install::

Test a specific branch in a specific project and space. If branchName is not specified, then the request defaults to using the master branch.

[POST] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}/maven/test::

Deploy a specific branch in a specific project and space. If branchName is not specified, then the request defaults to using the master branch.

[POST] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}/maven/deploy::

For more information about REST API for Business Central spaces and projects, see Interacting with Red Hat Decision Manager using KIE APIs.

Red Hat Decision Manager 7.7 is now DMN 1.3 ready.

Starting with the 7.7 release, the Red Hat Decision Manager user interface is now localized in Spanish and French in addition to English and Japanese.

Rule assets in Red Hat Decision Manager are built from executable rule models by default with the standard kie-maven-plugin plugin. Executable rule models are embedded models that provide a Java-based representation of a rule set for execution at build time. The executable model is a more efficient alternative to the standard asset packaging in previous versions of Red Hat Decision Manager and enables KIE containers and KIE bases to be created more quickly, especially when you have large lists of DRL (Drools Rule Language) files and other Red Hat Decision Manager assets.

If you are upgrading to Red Hat Decision Manager 7.7 from a previous version of the product and you have not already enabled executable rule models, you must add the required dependency to your existing Red Hat Decision Manager projects so that your rule assets are built from executable models in Red Hat Decision Manager 7.7.

For instructions on enabling executable rule models when upgrading to Red Hat Decision Manager 7.7, see Patching and upgrading Red Hat Decision Manager 7.7.

For more information about executable rule models, see Packaging and deploying a Red Hat Decision Manager project.

Red Hat Business Optimizer now includes a Spring Boot starter. You can use the Spring Boot starter to avoid common issues with class loading and use application.properties to overwrite the solver configuration. The solverConfig.xml file is no longer required because the starter automatically detects @PlanningSolution and @PlanningEntity annotations. The constraint streams API is improved. You can now modify your streams using the groupBy() building block.

For more information, see Creating Red Hat Decision Manager business applications with Spring Boot.

You can use SolverManager as wrapper for one or more Solver instances to simplify planning REST API and other enterprise services. The solve(…​) methods differ from the normal Solver.solve(…​) method:

SolverManager supports batch solving and solving that displays the progress to the end-user:

public class TimeTableService {
    private SolverManager<TimeTable, Long> solverManager;

    // Returns immediately, ok to expose as a REST service
    public void solve(Long timeTableId) {
        solverManager.solveAndListen(timeTableId,
            // Called once, when solving starts
            this::findById,
            // Called multiple times, for every best solution change
            this::save);
    }
    public TimeTable findById(Long timeTableId) {...}
    public void save(TimeTable timeTable) {...}
    public void stopSolving(Long timeTableId) {
        solverManager.terminateEarly(timeTableId);
    }
}

When deploying Red Hat Decision Manager on Red Hat OpenShift Container Platform using the operator, you can configure Git hooks to enable interaction between the built in Git repository of Business Central and other repositories.

For more information, see Deploying a Red Hat Decision Manager environment on Red Hat OpenShift Container Platform using Operators.

When deploying Red Hat Decision Manager on Red Hat OpenShift Container Platform using the operator and using RH-SSO or LDAP authentication, you can configure role mapping to link roles defined in Red Hat Decision Manager to different roles defined in RH-SSO or LDAP.

For more information about role mapping in operator deployment on Red Hat OpenShift Container Platform, see Deploying a Red Hat Decision Manager environment on Red Hat OpenShift Container Platform using Operators.

When deploying Red Hat Decision Manager on Red Hat OpenShift Container Platform using the operator, you can set custom JVM configuration for Business Central and KIE Server pods.

For more information about JVM configuration in operator deployment on Red Hat OpenShift Container Platform, see Deploying a Red Hat Decision Manager environment on Red Hat OpenShift Container Platform using Operators.

When deploying Red Hat Decision Manager on Red Hat OpenShift Container Platform, you can deploy an authoring environment if your Red Hat OpenShift Container Platform infrastructure does not provision persistent modules that support the ReadWriteMany mode.

Red Hat Decision Manager now uses a single built-in administrative user account for communication between Business Central and KIE Server. You no longer need to configure multiple built-in user accounts.

If you deploy a Red Hat Decision Manager authoring environment on Red Hat OpenShift Container Platform 3.x using templates, you can deploy several services on the same KIE Server concurrently, without needing to wait for a deployment to complete before you can start the next deployment. This functionality is provided by the ControllerBasedStartupStrategy setting that applies to communication between Business Central and KIE Server. You can also enable this strategy when deploying on Red Hat OpenShift Container Platform 4.x using the operator.

For more information, see Deploying a Red Hat Decision Manager authoring or managed server environment on Red Hat OpenShift Container Platform.

Deploying Red Hat Decision Manager using the operator on Red Hat OpenShift Container Platform 4.3 is now supported.

For more information about deploying Red Hat Decision Manager on Red Hat OpenShift Container Platform 4.3, see Deploying a Red Hat Decision Manager environment on Red Hat OpenShift Container Platform using Operators.

In Red Hat Decision Manager images for Red Hat OpenShift Container Platform, the Red Hat JBoss EAP version is updated to 7.2.6.

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

Starting with the 7.5 release of Red Hat Decision Manager, support for Red Hat OpenShift Container Platform 3.x, including using all templates to install Red Hat Decision Manager, is deprecated. Support for Red Hat OpenShift Container Platform 3.x will be removed in a future Red Hat Decision Manager release. Consider deploying Red Hat Decision Manager using the operator on Red Hat OpenShift Container Platform 4.x.

The legacy process designer in Business Central is deprecated in Red Hat Decision Manager 7.6.0. The legacy process designer will not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer. Create all new processes in the new process designer. For information about migrating projects to the new designer, see Managing projects in Business Central.

The legacy Business process asset is removed in Red Hat Decision Manager 7.7. Use the new Business process asset instead.

In the Red Hat Decision Manager user interface, support for the Chinese, German, and Portuguese languages is now removed.