Chapter 3. New features

A new KIE Server system property, org.kie.executor.jms.jobHeader, was added to Red Hat Process Automation Manager. If the value of this property is set to true, the jobId JMS header property will contain the request identifier.

For a list of KIE Server system properties, see Managing and monitoring KIE Server.

The following list provides a summary of process designer updates:

For more information, see Designing business processes using BPMN models.

When a DMN model is invoked from a business rule task in a BPMN workflow, the output is automatically mapped with the DMN model and returns an object of the type that is defined in the DMN model.

In the BPMN editor, if two nodes are connected with a sequence flow and another node is dragged and dropped over the same sequence flow, then a new sequence flow is created to perform the correct connection assignments.

The KIE API includes the new jbpmHumanTasksWithAdminExtended custom query. This query provides a list of all human task instances on the KIE Server instance. This list includes the administrator user responsible for the task, as well as extended information about the task, such as the user that modified the task most recently.

For more information about custom queries in the KIE API, see Interacting with Red Hat Process Automation Manager using KIE APIs.

You can now use a configuration file to configure Smart Router instead of providing parameters in the command line.

For more information about configuring Smart Router using a configuration file, see Installing and configuring Red Hat Process Automation Manager in a Red Hat JBoss EAP clustered environment.

You can now use the Web Service custom task to send a request including custom information in Simple Object Access Protocol (SOAP) headers.

For more information about custom tasks, see Custom tasks and work item handlers.

Processes developed in Business Central now include the Send Task event handler by default. When creating processes that interact with Red Hat AMQ Streams, you no longer need to add this event handler manually.

For more information about creating processes that interact with Red Hat AMQ Streams, see Integrating Red Hat Process Automation Manager with Red Hat AMQ Streams.

The following quickstarts are included in the Red Hat Process Automation Manager 7.12.0 Kogito and OptaPlanner 8 Decision Services Quickstarts download (rhpam-7.12.0-kogito-and-optaplanner-quickstarts.zip):

Red Hat build of OptaPlanner exposes metrics through Micrometer, a metrics instrumentation library for Java applications. You can use Micrometer with popular monitoring systems to monitor the OptaPlanner solver. For information about using Micrometer with OptaPlanner, see Developing Solvers with Red Hat Process Automation Manager.

Process Instance Migration Service now uses Quarkus instead of Thorntail.

When you deploy Red Hat Process Automation Manager on Red Hat OpenShift Container Platform using the operator installer, by default the deployment uses the OpenShiftStartupStrategy setting. You can now switch to the Controller startup strategy in the configuration user interface if necessary.

You can now set custom hostnames for external routes by using the routeHostname property.

You can now enable or disable SSL in the operator and expose the SSL route.

You can now specify whether to use a default or user customized CORS configuration.

When deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform, LDAP security configuration now uses the Elytron subsystem. To support the Elytron subsystem, the following configuration settings were removed:

The following configuration settings were added:

When deploying a high-availability Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform, you can now configure the user name and password for the Red Hat Data Grid component.

When deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform, running post-configuration scripts on Red Hat JBoss EAP on the Business Central and KIE Server pods is now supported. You can use these scripts to configure Elytron users.

When deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform, you can now configure role mapping for Red Hat Single Sign-On or LDAP configuration by entering the configuration directly in the settings, without using a role mapping configuration file. The use of a role mapping configuration file is now optional but still supported.