Release notes for Red Hat Process Automation Manager 7.9

Red Hat Process Automation Manager 7.9

Abstract

This document contains release notes for Red Hat Process Automation Manager 7.9.

Preface

These release notes list new features, features in technology preview, known issues, and issues fixed in Red Hat Process Automation Manager 7.9.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. Product overview

Red Hat Process Automation Manager is an open-source business automation platform that combines business process management (BPM), case management, business rules management, and resource planning. It enables business and IT users to create, manage, validate, and deploy business processes, cases, and business rules.

Red Hat Process Automation Manager uses a centralized repository where all resources are stored. This ensures consistency, transparency, and the ability to audit across the business. Business users can modify business logic and business processes without requiring assistance from IT personnel.

Red Hat Process Automation Manager 7.9 provides increased stability, several fixed issues, and new features.

Red Hat Process Automation Manager is fully supported on Red Hat OpenShift Container Platform and can be installed on various platforms.

Note

Red Hat Process Automation Manager requires Java 8 or later.

For information about the support policy for Red Hat Process Automation Manager, see the Release maintenance plan for Red Hat Decision Manager 7.x and Red Hat Process Automation Manager 7.x.

Chapter 2. New features

This section highlights new features in Red Hat Process Automation Manager 7.9.

2.1. Business Central

2.1.1. Support for multiple diagrams in DMN models

For complex DMN models, you can now use the DMN designer in Business Central to design multiple DMN decision requirements diagrams (DRDs) that represent parts of the overall decision requirements graph (DRG) for a DMN decision model. This improvement enables you to better organize DMN decision models with many decision requirements by dividing the model into smaller nested DRDs.

For more information about creating DMN models with multiple diagrams, see Designing a decision service using DMN models.

2.1.2. Dashbuilder runtime

Dashbuilder runtime is a new add-on standalone web application, distributed as a WAR to run the dashboards on Red Hat JBoss EAP. If you have access to dashbuilder runtime, you can explore the dashboards created in Business Central. The following list provides a summary of dashbuilder runtime updates:

  • After creating dashboards using datasets and pages, you can export these dashboards from Business Central using custom export.
  • You can import, access, and run the dashboards that are exported from Business Central in dashbuilder runtime.
  • Dashbuilder runtime accesses the KIE Server REST API to run the queries from imported KIE Server datasets.
  • Dashbuilder runtime provides embedded capabilities that allow you to set a specific dashboard from an instance of dashbuilder runtime on your web applications.
  • In Dashbuilder runtime, you can import multiple dashboards in a single dashbuilder runtime instance.
  • You can create and add external components that can be a part of the dashboard page.

2.2. Entando AppBuilder

Entando AppBuilder is now officially removed from the Red Hat Process Automation Manager 7.9. Red Hat Process Automation Manager no longer includes entitlements for Entando AppBuilder. The feature references and documentation is not be available from the 7.9 release.

2.3. Process Designer

2.3.1. Process designer updates

The following list provides a summary of process designer updates:

  • Ability to add data objects in a process diagram
  • Ability to add Kafka work item in a process diagram to send events to a Kafka topic
  • Ability to double-click any diagram node to edit its name using the new inline text editor
  • Ability to view highlighted syntax when writing a script in Java, JavaScript, and MVEL
  • Ability to use multiple connections for a task or an event using jbpm.enable.multi.con system property

For more information, see Designing business processes in Business Central.

2.3.3. Ability to configure emails in the task notification

You can now directly add email addresses to send task notification emails. For more information, see Designing business processes in Business Central.

2.4. Decision engine

2.4.1. Descope traits in decision engine

The traits functionality and its specific implementation code is moved to an individual module named drools-traits. To use traits, you can import the drools-traits module to Maven. The existing implementation is not supported in the executable rule model.

2.4.2. New drools-metric module for decision engine performance analysis

A new module named drools-metric is added, which can assist in the performance analysis of the decision engine.

For more information, see Designing a decision service using DRL rules.

2.5. Process engine

2.5.1. Support for process fluent API

You can now create a business process using the process fluent API. Following is a basic example of creating a business process using fluent API: 

ProcessBuilderFactory factory = ProcessBuilderFactories.get();
Process process = factory
    // start process definition
    .processBuilder(processId)
    // package and name
    .packageName(packageName)
    .name(processName)
    .setMetadata("pepe", true)
    // start node
    .startNode(1).name("Start").done()
    // script node in Java language that prints "action"
    .actionNode(2).name("Action")
    .action(Dialect.JAVA,
            "System.out.println(\"Action\");").done()
    // end node
    .endNode(3).name("End").done()
    // connections
    .connection(1, 2)
    .connection(2, 3)
    .build();

For more information about process fluent API, see Interacting with Red Hat Process Automation Manager using KIE APIs.

2.5.2. Enhanced search capabilities

Red Hat Process Automation Manager 7.9 provides enhanced search capabilities, including flexible search criteria for tasks, process instances, and cases. For more information, see Designing and building cases for case management.

2.6. Red Hat Business Optimizer

2.6.1. Using Red Hat Business Optimizer with Spring Boot

You can follow the example in Creating a school timetable using Red Hat Business Optimizer with Spring Boot to create a school timetable.

2.6.2. Employee Rostering rotation pattern redesign

The rotation pattern on the Employee Rostering Rotation window has been redesigned for ease of use. For more information, see Running and modifying the employee rostering starter application for Red Hat Business Optimizer using an IDE.

2.7. Spring Boot

2.7.1. Replicating audit data in a JMS message broker

You can now replicate KIE Server audit data to a Java Message Service (JMS) message broker, for example, activeMQ or Artemis, After replicating the data, you can dump the data in an external database schema so that you can improve the performance of your Spring Boot application by deleting the audit data from your application schema.

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

2.7.2. Support for bytea column type

You can now create a PostgreSQL schema that uses the bytea column type instead of the oid column type by setting the value of the org.kie.persistence.postgresql.useBytea property to true.

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

2.7.3. Self-contained Red Hat Process Automation Manager Spring Boot JAR file

You can create a self-contained Red Hat Process Automation Manager Spring Boot JAR file that contains multiple versions of the same KJAR file.

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

2.8. Red Hat OpenShift Container Platform

2.8.1. Support for Red Hat OpenShift Container Platform version 4.6

Red Hat Process Automation Manager now supports Red Hat OpenShift Container Platform version 4.6. In order to support this version, necessary changes in the operator bundle format are made. Red Hat OpenShift Container Platform version 4.6 provides an extended update support. For more information, see Red Hat OpenShift Extended Update Support (EUS) Overview.

Important

Red Hat Process Automation Manager 7.9 is supported only on Red Hat OpenShift Container Platform version 3.11 and Red Hat OpenShift Container Platform version 4.6 EUS. Due to the internal changes of the operator and API version, Red Hat OpenShift Container Platform version 4.5 is not supported and this makes an exception to the general support policy for the Red Hat Middleware products. For more information, see Support of Red Hat Middleware products and components on Red Hat OpenShift.

2.8.2. Support for LDAP failover

When using LDAP authentication, Red Hat Process Automation Manager on Red Hat OpenShift Container Platform now supports failover to a different LDAP server if a server becomes unavailable.

For more information, see Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using Operators and Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using templates.

2.8.3. Integration with new versions of products

Red Hat Process Automation Manager on Red Hat OpenShift Container Platform now supports integration with the following new product versions:

  • Red Hat AMQ 7.7
  • Red Hat AMQ Broker 7.7
  • Red Hat Single Sign-On 7.4.1
  • Red Hat Data Grid 7.3

2.8.4. Support for a customized Smart Router image

Red Hat Process Automation Manager on Red Hat OpenShift Container Platform now supports customized Smart Router images. You can extend Smart Router to provide routing specific to the needs of your environment.

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

2.8.5. Logging level configuration for Smart Router

You can now configure the logging level for Smart Router when deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform.

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

2.8.6. Support for deploying an unmanaged KIE Server on Red Hat OpenShift Container Platform using the operator

You can now deploy Red Hat Process Automation Manager on Red Hat OpenShift Container Platform using the operator with a KIE Server that is not managed by Business Central monitoring.

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

Chapter 3. Support and compatibility

This section highlights supported version updates in Red Hat Process Automation Manager 7.9.

3.1. Support for Firefox 78 ESR

Red Hat Process Automation Manager now supports Firefox 78 ESR browser.

3.2. Support for Red Hat Data Grid 7.3

Red Hat Process Automation Manager now supports Red Hat Data Grid 7.3.

3.3. Support for AMQ Streams 1.5

Red Hat Process Automation Manager now supports AMQ Streams 1.5.

3.4. Support for Red Hat AMQ 7.7

Red Hat Process Automation Manager now supports Red Hat AMQ 7.7.

3.5. Support for High-availability authoring on Red Hat JBoss EAP on premise

Configuration of Business Central on Red Hat JBoss EAP for high-availability (HA) on premise is fully supported.

For more information about installing and configuring Red Hat Process Automation Manager in a Red Hat JBoss EAP clustered environment, see Installing and configuring Red Hat Process Automation Manager in a Red Hat JBoss EAP clustered environment.

3.6. Support for Red Hat JBoss Web Server

You can install Red Hat Process Automation Manager on Red Hat JBoss Web Server 5.3.0 (Apache Tomcat 9.0.30) and Red Hat JBoss Web Server 5.4.0. when available. For more information about installing Red Hat Process Automation Manager on Red Hat JBoss Web Server 5.3, see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss Web Server.

3.7. Red Hat CodeReady Studio integration

You can now integrate Red Hat CodeReady Studio 12.17 with Red Hat Process Automation Manager. For more information about integrating Red Hat CodeReady Studio 12.17 with Red Hat Process Automation Manager, see Integrating Red Hat CodeReady Studio with Red Hat Process Automation Manager.

3.8. Red Hat Fuse integration

Red Hat Fuse 7.7 is supported on Red Hat JBoss EAP 7.2, whereas Red Hat Process Automation Manager is supported on Red Hat JBoss EAP 7.3. To ensure a stable deployment environment, install Fuse and Red Hat Process Automation Manager on different instances of Red Hat JBoss EAP according to the supported Red Hat JBoss EAP versions. For more information, see Integrating Red Hat Fuse with Red Hat Process Automation Manager

Chapter 4. Deprecated components

The components listed in this section have been deprecated.

4.1. Legacy Test Scenarios tool

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

4.2. Support for Red Hat OpenShift Container Platform 3.x

From Red Hat Process Automation 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 Process Automation Manager using the operator on Red Hat OpenShift Container Platform 4.x.

4.3. Legacy process designer

The legacy process designer in Business Central was deprecated in Red Hat Process Automation Manager since 7.6.0. The legacy process designer does not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer, and create new processes in the new process designer. For information about migrating projects to the new designer, see Managing projects in Business Central.

Chapter 5. Technology preview

This section lists features that are in Technology Preview in Red Hat Process Automation Manager 7.9. Business Central includes an experimental features administration page that is disabled by default. To enable this page, set the value of the appformer.experimental.features property to true.

Important

These features are for Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information on Red Hat Technology Preview features, see Technology Preview Features Scope.

5.1. Case modeler

Case modeler in Business Central now includes the new process designer. It provides the option to model a case as a sequence of stages that makes it easy to define a case model at high-level. Case modeling supports three types of tasks: human tasks, sub-processes, and sub-cases.

The case modeler in Red Hat Process Automation Manager 7.9 is a Technology Preview feature and is disabled by default in Business Central.

To enable the case modeler preview:

  1. In Business Central, select the Admin icon in the top-right corner of the screen and select Roles.
  2. Select a role from the left panel.
  3. Click Editors → (New) Case Modeler → Read.
  4. Click Save.

5.2. Prediction Service API

You can use the prediction service API to provide a prediction service that assists with human tasks. The prediction service can use AI. For example, you can use the Predictive Model Markup Language (PMML) models or Statistical Machine Intelligence and Learning Engine (SMILE) to implement the service.

5.3. Deploying a high-availability authoring environment on Red Hat OpenShift Container Platform 4.x

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

5.4. OpenShift operator installer wizard

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

Chapter 6. Known issues in Red Hat Process Automation Manager 7.9.0

This section lists known issues with Red Hat Process Automation Manager 7.9.

6.1. Business Central

Package list fails to populate default package for imported projects [RHPAM-3209]

Issue: When a project contains many packages, and you try to create a new asset, the list of packages take some time to populate.

Steps to reproduce:

  1. Import a project which contains many packages.
  2. Go to the project page.

  3. Click Add Asset.

    The Assets window appears.

  4. Add any asset in the project.

  5. In the pop-up window, check the Package drop-down list.

    You receive Nothing selected option for some time.

Expected result: Package list is populating default package for imported projects.

Actual result: Package list is not populating default package for imported projects.

Workaround:

  • Make sure you have identical paths in both src/java and src/resources. In your Git repository, insert .gitkeep files to retain the empty folder structure.
  • In the asset pop-up window, manually select the <default> option in the Package drop-down list..

Collection editor is not opening for DRL based test scenarios [RHDM-1464]

Issue: DRL based test scenario throws an unexpected error when you open a collection editor for a list of some datatypes.

Workaround: None.

You cannot add a deployment unit when you create a container for the first time [RHPAM-3254]

Issue: You cannot add a deployment unit when you create a container for the first time, and you receive an unexpected system error.

Steps to reproduce:

  1. In Business Central, go to Menu → Deploy → Execution Servers.
  2. Under Deployment Units, click Add Deployment Unit.
  3. Enter the GAV values manually.
  4. Select the Start Deployment Unit? check box to start the service.

  5. Click Finish.

    You receive an unexpected system error.

Workaround: None.

Unable to navigate from child process instance to parent process instance [RHPAM-3227]

Issue: You cannot navigate from child process instance to parent process instance but possible to navigate from parent process instance to child process instance.

Steps to reproduce:

  1. In Business Central, create parent process and child process relationship.
  2. Start the process instance and make it active.
  3. Notice that, you cannot navigate from child process instance to parent process instance.

Expected result: When there is an active process instance, there must be a link to navigate from child process instance to parent process instance and vice-versa.

Actual result: You cannot navigate from a child process instance to the parent process instance.

Workaround: None.

The deployment unit fields are missing when you add a new deployment unit [RHPAM-3213]

Issue: When you add a deployment unit, fields that are available under Add Deployment Unit are missing.

Steps to reproduce:

  1. In Business Central, go to Menu → Deploy → Execution Servers.

  2. Under Deployment Units, click Add Deployment Unit.

    Deployment unit fields are missing.

Workaround: Deployment unit fields appear only if you navigate to Process Configuration and come back.

6.2. Form modeler

DocumentCollection output parameter does not work in generated forms [RHPAM-3252]

Issue: If documents are configured as output variable only, for example, documents are uploaded as a part of the user task, then the input parameter of DocumentColletion type is not present and the default value "" (empty string) is sent to DocumentCollection, and also you receive an exception.

Steps to reproduce:

  1. Deploy the project attached in the RHPAM-3252 issue.
  2. Create a new process instance.

  3. Enter the following endpoint URL: 

    http://<host>:<port>/kie-server/services/rest/server/containers/\{containerId}/forms/tasks/\{taskInstanceId}/content\

You receive an exception.

Workaround: None.

6.3. Process Designer

Data objects in Assignments disappear once you save the process [RHPAM-3212]

Issue: Data objects which are present in Assignments disappear once you save the process.

Steps to reproduce:

  1. Create a data object.
  2. Create a user task.
  3. Click the Properties icon on the upper-right side of the screen to open the Properties panel.
  4. Expand Implementation/Execution and select Assignments to open the Data I/O window.
  5. Next to Data Inputs and Assignments, click Add and select a Source value.
  6. Next to Data Outputs and Assignments, click Add and select a Target value.
  7. Close the Assignments and save the process.
  8. Open the Assignments sub-section.

Expected result: Source and Target fields are empty.

Actual result: Source and Target fields are set to data object.

Workaround: Deselect the task and then select the task again.

A new rule flow group is not reflected in business rule task properties [RHPAM-3195]

Issue: When you create a new rule flow group, the change is not reflected in business rule task’s property.

Steps to reproduce:

  1. Create a business process.

    Do not close the process.

  2. Create a testrule.rdrl file containing testgroup as ruleflow-group.
  3. Select Business Rule in created process.
  4. Expand Implementation/Execution and select Rule Flow Group drop-down list.

Expected result: The Rule Flow Group drop-down list contains ruleflow-group that is specified in DRL file. For example, testgroup.

Actual result: The Rule Flow Group drop-down list is empty.

Workaround: Deselect the business rule task and then select the business rule task again.

Edited rule flow group is not reflected in business rule task properties [RHPAM-3194]

Issue: When you edit a rule flow group, the change is not reflected in business rule task’s property.

Steps to reproduce:

  1. Create a business process.

    Do not close the process.

  2. Create a testrule.rdrl file containing testgroup as ruleflow-group.
  3. Open a testrule.rdrl file and change the testgroup to testgroup-renamed.
  4. Save the changes.
  5. Select Business Rule in created process.
  6. Expand Implementation/Execution and select Rule Flow Group drop-down list.

Expected result: The Rule Flow Group drop-down list contains edited testgroup-renamed value.

Actual result: The Rule Flow Group drop-down list contains testgroup value.

Workaround: Deselect the business rule task and then select the business rule task again.

The cursor position is different in Firefox browser when you use an inline text editor [RHPAM-3171]

Issue: When you use an inline text editor, the cursor position is different in Firefox browser in comparison with Google Chrome browser and Kogito VSCode extension.

Steps to reproduce: Perform the following steps using both Firefox and Google Chrome browser.

  1. Create any node.
  2. Double-click the node to activate inline text editor.

Expected result: The cursor is on the same position in Firefox browser in comparison with Google Chrome browser.

Actual result: The cursor is on the different position in Firefox browser in comparison with Google Chrome browser.

Workaround: None.

Editing text using an inline text editor is displayed over Properties panel or expanded palette [RHPAM-3172]

Issue: When you place any task, sub-process, or text annotation in the Properties panel and start editing its name by using an inline text editor, the text is visible over the Properties panel.

Steps to reproduce:

  1. Create any node.
  2. Ensure that the Properties panel is open and tool palette is expanded.
  3. Move the node under the Properties panel or the expanded area of the tool palette in a way that you can still click on the node.
  4. Double-click the node to activate inline text editor.
  5. Enter any text.

Expected result: The node is not editable or the text is shown next to the Properties panel or the tool palette and it is entirely visible.

Actual result: The text is visible over the Properties panel.

Workaround: None.

You cannot create or open Case Management (Preview) asset [RHPAM-3281]

Issue: When you create or open Case Management (Preview) asset, you receive a runtime exception.

Steps to reproduce:

  1. Create a case project.
  2. Create a new Case Management (Preview) asset.

Expected result: You can successfully create or open a Case Management (Preview) asset.

Actual result: You receive a runtime exception when you create or open a Case Management (Preview) asset.

Workaround: None.

Not all illegal characters are removed from data object name [RHPAM-3250]

Issue: When you create a data object with a name containing illegal characters, you receive a warning message after saving, closing, and saving it again.

Steps to reproduce:

  1. Create a data object with ~!@#$%^&*()_+`10-={}[]:"|;'\<>?,./°ľščťžýáíéúä!ô§ň name.
  2. Save, close, and reopen the process.
  3. Move the node and save the process again.

Expected result: All illegal characters are removed when the process is saved and reopened.

Actual result: You receive a warning message.

Workaround: None.

Scrolling of the Properties panel stops when the cursor is over a script area [RHPAM-3208]

Issue: When the cursor is over a script area, scrolling of the Properties panel stops.

Steps to reproduce:

  1. Create a user task.
  2. Expand Implementation/Execution section.
  3. Scroll down and keep scrolling until it stops.

Expected result: Scrolling stops working when the scrollbar is at the bottom of the page.

Actual result: Scrolling stops working when the cursor is over the On Entry Action field.

Workaround: If the cursor is outside the text area, the main scrollbar is always activated.

Text area used for script task is cropped and shifted [RHPAM-3207]

Issue: Text area used for script task is cropped and shifted when you enter many lines of code. Also, the vertical scrollbar is shifted.

Steps to reproduce:

  1. Create a script task.
  2. Expand Implementation/Execution section.
  3. In Script text area, enter many lines of code.

Expected result: Text area used for script task is not cropped and shifted.

Actual result: Text area used for script task is cropped and shifted.

Workaround: None.

When an inline text editor is active, you cannot activate any property immediately [RHPAM-3198]

Issue: It is not possible to activate any property immediately in the Properties panel when an inline editor is active.

Steps to reproduce:

  1. Create any node.
  2. Ensure that Properties panel is open.
  3. Double-click on the node to activate the inline text editor.
  4. Click on any property from the Properties panel.

Expected result: You can edit the property when an inline text editor is active.

Actual result: You cannot edit the property when an inline text editor is active.

Workaround: When you follow the steps to reproduce, click on the property again.

You cannot use an inline text editor when a node is near the left canvas border [RHPAM-3167]

Issue: You cannot use an inline text editor when a node is near the left canvas border. This issue is applicable to events, gateways, and data object.

Steps to reproduce:

  1. Create any node.
  2. Place it near to the left canvas border.
  3. Double-click on the node.

Expected result: An inline text editor is active and you can edit the node name.

Actual result: An inline text editor is not active and you cannot edit the node name.

Workaround: None.

The edited node is see-through when you use an inline text editor [RHPAM-3166]

Issue: The edited node is see-through when you use an inline text editor.

Steps to reproduce:

  1. Create an embedded subprocess.
  2. Change the name of the subprocess to a long text. For example, over 300 characters.
  3. Create any node inside the subprocess and place it over the text of the subprocess.
  4. Edit the node name using an inline text editor.

Expected result: The text is readable and the edited node is not see-through.

Actual result: The text is not readable because the edited node is see-through.

Workaround: None.

6.4. Process engine

When the SLA on user task is executed, you receive No session found for context error [RHPAM-3233]

Issue: When the service level agreement (SLA) on user task is executed on container with PER_PROCESS_INSTANCE runtime strategy, you receive No session found for context error.

Steps to reproduce:

  1. Clone the droolsjbpm-integration project.
  2. Open SLAComplianceIntegrationTest.java file from the cloned project.
  3. Comment out all the tests except testSLAonUserTaskViolated().

  4. Open the terminal on kie-server-integ-tests-jbpm/ folder and execute the test using following command: 

    mvn clean install -Pwildfly -Dit.test=SLAComplianceIntegrationTest

  5. Check the logs on the terminal.

    Once the test execution starts, you receive a No session found for context error.

6.5. DMN designer

Decision service is missing inputData element in model with multiple DRDs [RHDM-1483]

Issue: When you reuse a decision component by adding it into a decision service node in a model containing multiple decision requirement diagrams (DRDs), the inputData element is missing from the resulting decision service node.

Steps to reproduce:

  1. Define multiple decision requirement diagrams (DRDs).
  2. In a DRD, define some decisions with inputs.

  3. In another DRD, define decision service and reuse the decision components from the previous DRD.

    Do not duplicate the inputs.

  4. Build and deploy the decision service.

  5. Do any of the following tasks:

    • Evaluate the decision to see the error reported in the description.
    • Verify the DMN source and see that inputData element is missing from the decision service .

Workaround: Add an inputData element manually into the resulting decisionService element.

DMN editor does not detect the changes from the Decision Navigator view [RHDM-1482]

Issue: DMN editor does not detect changes in the file when a decision requirement diagram (DRD) is renamed or removed from the Decision Navigator view.

Steps to reproduce:

  1. Rename a DRD from the Decision Navigator view.

  2. Click Save.

    You receive You have no unsaved changes alert window.

  3. Close the DMN editor.

    You receive You have no unsaved changes alert window.

  4. Reopen the DMN editor.

    The name of the DRD is still the same.

Workaround: Make a different change to the file which then enforces save or discard action.

The constraint value is missing in a decision table [RHDM-1460]

Issue: The constraint value is missing while defining a decision table.

Steps to reproduce:

  1. Create a DMN file with decision.
  2. Define a decision table.
  3. Set the first column type as a number.
  4. Save the asset.
  5. Close the editor.
  6. Reopen the asset.
  7. Go to the decision table.
  8. Select the input with type as a number.
  9. Open the Properties panel.
  10. Set the constraint in the Constraint value field.
  11. Select the output column.
  12. Select the input column again.
  13. Verify that the constraint value is missing.

Workaround: None.

The undo and redo operations do not work properly when you delete a node in decision requirements graph (DRG) [RHDM-1459]

Issue: In a model containing multiple decision requirement diagrams (DRDs), the undo and redo operations do not work properly when you delete a node in the decision requirements graph (DRG).

Steps to reproduce:

  1. Move the node to a DRD.
  2. Navigate to DRG.
  3. Delete the node from the DRG.
  4. Undo the changes.

Expected result: You can perform the undo and redo operations in DRG.

Actual result: You receive an error. When you confirm, the DRG is broken.

Workaround: None.

The undo and redo operations are lost when you switch between the diagrams [RHDM-1458]

Issue: In a model containing multiple decision requirement diagrams (DRDs), the undo and redo operations are lost when you switch between the diagrams.

Steps to reproduce:

  1. Open a DMN file with two or more decision requirement diagrams (DRDs).
  2. Make some changes. For example, move a node in one diagram.
  3. Switch to another diagram.

  4. Click Undo or press Ctrl+Z.

    The undo and redo operations are lost and nothing changes.

Workaround: None.

In Business Central, the DMN editor is unable to save the changes in the Properties panel [RHDM-1456]

Issue: When you change the name property in the Properties panel, try to save the changes, and reopen the editor, the DMN editor is unable to save the changes.

Steps to reproduce:

  1. Create a DMN file.
  2. Change the name of the DMN file in the Properties panel.

  3. Click Save.

    You receive You have no unsaved changes alert window.

  4. Close the DMN editor.

  5. Reopen the asset and check the the Properties panel.

    The changes are not saved.

Workaround: None.

DMN editor is reporting unsaved changes in the DMN files when there are no changes [RHDM-1453]

Issue: When you open a DMN file in Business Central and try to close the file without any changes, the DMN editor reports unsaved changes in the DMN files.

Steps to reproduce:

  1. In Business Central, go to Menu → Design → Projects.
  2. Click Try samples.
  3. Open Traffic_Violation project.
  4. Open Traffic Violation DMN file.

  5. Close the editor.

    You receive an Unsaved changes error pop-up.

Workaround: None.

6.6. Decision engine

testDoubleNaN fails after jitting on TypeCoercionTest [RHDM-1470]

Issue: You receive an AssertionError error in org.drools.modelcompiler.TypeCoercionTest#testDoubleNaN when a constraint is jitted.

Steps to reproduce:

  1. Run the following command in org.drools.modelcompiler module: 

    mvn clean install -Dtest=org.drools.modelcompiler.TypeCoercionTest#testDoubleNaN* -Ddrools.jittingThreshold=0

Workaround: None.

6.7. High-availability Business Central on premise

You cannot create multiple processes at the same time [RHPAM-3202]

Issue: When you create multiple processes at the same time, you receive an error message and multiple processes are not created.

Steps to reproduce:

  1. Create multiple processes at the same time.

    You receive an Activity not found error.

Workaround: None.

When you create a project, base-kie-project is created instead of the real name of the project [RHPAM-3193]

Issue: When you create a project, a project with the name base-kie-project is created instead of the real name of the created project.

Steps to reproduce:

  1. Create multiple projects with multiple users in the same space.

    The base-kie-project project is created.

Workaround: Delete and recreate the project or rename the project name from Settings tab.

You cannot create multiple projects at the same time [RHPAM-3192]

Issue: When you create multiple projects at the same time, you receive an error message and multiple projects are not created.

Steps to reproduce:

  1. Create multiple projects at the same time.

    You receive an error.

Workaround: None.

Chapter 7. Fixed issues in Red Hat Process Automation Manager 7.9.0

Red Hat Process Automation Manager 7.9.1 provides increased stability and fixed issues listed in this section.

7.1. Business Central

  • You cannot save a file when you try to rename the package from the source code [RHPAM-3119]
  • The wait spinner is not present when you add a deployment unit, manually enter GAV values, and confirm the alert window [RHPAM-3114]
  • Assets are not properly indexed for clustered Business Central environment [RHPAM-3089]
  • When you try to add a new deployment unit, you receive multiple error notifications [RHPAM-3112]
  • Business Central does not remember the last used branch when you log out [RHPAM-2957]
  • In the Assets list, there are columns like Last modified X day ago and Created XX weeks ago but they are the same for all the assets and does not reflect the actual modified or created values [RHPAM-2865]
  • Package list is not populating correctly for imported projects [RHDM-1377]
  • java.lang.Number import remains in the list of imports when deleted [RHDM-247]
  • If a project contains DRL files with the queries, the test scenarios designer displays queries in the coverage report [RHDM-1448]
  • When you restart Business Central, the connection between KIE Server and Business Central does not re-establish [RHPAM-3137]
  • You cannot lock guided decision table asset in Business Central [RHPAM-2992]
  • When you rename the guided rules used in test scenarios, coverage report displays both original and renamed value of guided rules [RHDM-1334]
  • An error message about missing KIE Server configuration on dashbuilder runtime must be improved [RHPAM-3058]
  • When you remove parent process instance details from the process list, you receive an error message [RHPAM-3102]
  • When you skip a task from task event listener, you receive BAMTaskEventListener warning [RHPAM-3100]
  • To avoid large memory retention, make the LRUCache file configurable [RHPAM-2808]
  • When more than one KIE Servers are connected with different IDs, you receive an unexpected system error [RHPAM-3134]

7.2. Process designer

  • Case management properties are missing in a case definition [RHPAM-3131]
  • If you use the ^ character in the subject of a user task notification an error occurs [RHPAM-2763]
  • Called element in a reusable subprocess is not populated [RHPAM-2760]
  • Ruleflow group is not populated [RHPAM-2740]
  • If you migrate a process from the legacy process designer to the new process designer, you receive an incorrect warning about node being ignored [RHPAM-2452]
  • In the process modeler, the Service Tasks name is changed to Custom Tasks [RHPAM-3008]
  • The leap days are not validated in timer events [RHPAM-2987]
  • When try you implement catch-all errors using an event subprocess, and if the value of ErrorRef for the error start event is empty, you receive build errors [RHPAM-3093]

7.3. Process engine

  • When you implement the interface, EventEmitter fails to execute the methods [RHPAM-3126]
  • When you upgrade Red Hat Process Automation Manager from 7.7.0 to 7.8.0, the userTaskService.saveContent does not work [RHPAM-3123]
  • You can execute the process with multiple Sources (throw link event) with the same link name and you can use only one Target (catch link event) for the same link name across the subprocess level [RHPAM-3132]
  • Define jBPM datasource as @Primary to avoid the failure of entityManagerFactory in JBPMAutoConfiguration [RHPAM-3072]
  • A business process with required variable tag should not be accepted using REST API [RHPAM-3048]
  • The main process fails due to subprocess exception handling transaction rollback [RHPAM-2982]
  • When you dynamically add a new node to a process instance, the execution of the process fails with a runtime exception [RHPAM-3188]

7.4. Decision engine

  • In decision tables, you can terminate the pattern with @watch annotation, which is used to customize the properties that the pattern is reactive on [RHDM-1437]
  • The @watch annotation does not behave properly when you exclude all the properties but one property [RHDM-1436]
  • Constraint jitting fails When you take a string value from a map and compare it with string literal [RHDM-1439]
  • If the accumulate contains more than one accumulating function, you receive an unwanted re-firing of a rule after deserialization [RHDM-1434]
  • Building rules in a default-build target of kie-maven-plugin takes a lot of time [RHDM-1433]
  • In MVEL dialect mode, you cannot compile binary operation for BigDecimal type values, and you receive a compilation error in the executable model [RHDM-1421]

7.5. KIE Server

  • MarshallingException occurs during REST request (JSON) unmarshalling in KIE Server [RHDM-1417]

7.6. Installer

  • On Red Hat JBoss EAP, the Red Hat Process Automation Manager installer adds an additional $ sign in the vaulted password of database user [RHPAM-3148]

7.7. Red Hat OpenShift Container Platform

  • In monitoring console page, when you create a new page, you receive an Activity not found error pop-up [RHPAM-3066]
  • When you try to configure an external Red Hat Single Sign-On configuration, you receive SSL required for: EXTERNAL error message [RHPAM-2804]
  • Missing support for xa-pool configuration of is-same-rm-override field [RHPAM-3071]
  • In Red Hat OpenShift Container Platform, when you create a secure connection between Business Central and KIE Server, an incorrect URL is generated [RHPAM-3162]

Chapter 8. Known issues in Red Hat Process Automation Manager 7.9.1

This section lists known issues with Red Hat Process Automation Manager 7.9.1.

8.1. Business Central

Running tests affects incremental build [RHDM-1508]

Issue: In test scenario simulation, when you test DRL rules and facts containing an enum property, you receive a validation error.

Steps to reproduce:

  1. Download the bpms_scesim-tickets.zip file present in the [DROOLS-5458].
  2. Import the project.
  3. Go to the DRL file and run the validation.
  4. Go to test scenario simulation and run the validation.

  5. Go back to DRL file and run the validation again.

    Validation fails and you receive an error.

  6. Go back to test scenario simulation and run the validation again.

    Validation fails due to the rule not being evaluated for given facts.

Workaround: Navigate to your imported project page and click Build.

A system error occurs when you add a deployment unit [RHPAM-3111]

Issue: You cannot add a deployment unit, you receive an unexpected system error.

Steps to reproduce:

  1. In Business Central, go to Menu → Deploy → Execution Servers.
  2. Under Deployment Units, click Add Deployment Unit.
  3. Enter the GAV values manually.
  4. Select the Start Deployment Unit? check box to start the service.

  5. Click Finish.

    You receive an unexpected system error.

Workaround: None

Chapter 9. Fixed issues in Red Hat Process Automation Manager 7.9.1

Red Hat Process Automation Manager 7.9.1 provides increased stability and fixed issues listed in this section.

9.1. Business Central

  • You cannot add a deployment unit when you create a container for the first time [RHPAM-3254]
  • Performing test is slow in Business Central [RHPAM-3246]
  • Free form DRL disappears from guided rule editor [RHPAM-3204]
  • Reserved roles defined in Red Hat Single Sign-On application appear as roles and groups in the admin page of the Business Central [RHPAM-2984]
  • In the guided rule editor, you cannot use the formula expression containing quotes as an argument for call method action and it does not reopen correctly [RHPAM-2972]
  • When you rename an asset with unsaved changes, you receive an error [RHPAM-2946]
  • In the guided rule editor, when you use and compare LocalDateTime fields, binding variables which represent these LocalDateTime fields are prefixed with the = character and you cannot validate the rule [RHDM-1408]
  • When you import a Git project, create a new branch, and push it to the remote repository, you cannot see the newly created branch in Business Central [RHDM-1407]
  • When you try to re-import a repository which is initially created by importing an empty repository will result in an empty project [RHDM-1378]
  • You cannot create a project using REST API with provided messages.properties files and the post-commits [RHDM-1354]
  • The deployment unit fields are missing when you add a new deployment unit [RHPAM-3213]
  • Unable to navigate from child process instance to parent process instance [RHPAM-3227]
  • When you create a pie chart, in a Page, using a dataset containing a column with an integer value, you receive an error [RHPAM-2867]

9.2. KIE Server

  • The /server/state REST endpoint prints the KIE Server user and controller user in the clear text [RHPAM-3260]
  • Model definition is not present in the KIE Server Swagger API [RHPAM-3219]
  • Process work flow breaks for processes with timers if one of the node is starting or shutting down at the time of workflow execution [RHPAM-3186]
  • When you try to create a web service call, the classes are not generated and you receive an error [RHPAM-3106]
  • Sync issues may occur when KIE Server is connected to Business Central in high availability (HA) on-premise environments [RHPAM-2965]

9.3. Process engine

  • When the SLA on user task is executed, you receive No session found for context error [RHPAM-3233]
  • You can provide an API method to signal process instance with correlationKey [RHPAM-3269]
  • When a task in event sub-process is marked with Is Async and set as true, you cannot abort the nested process instances [RHPAM-3261]
  • When you skip a task in afterTaskAddedEvent method of TaskLifeCycleEventListener, you receive an IllegalArgumentException exception [RHPAM-3247]

9.4. Process designer

  • Human task reassignment fails and you receive an unexpected error during processing [RHPAM-3244]
  • The Case Modeler (Tech Preview) asset type is now removed [RHPAM-3229]

9.5. Decision engine

  • In the executable model compiler, when you use number inside the bracket to execute a rule, you receive a compilation error and it fails with an exception [RHDM-1491]
  • Inaccurate rule execution in the executable model [RHDM-1465]
  • In the executable model compiler, when a variable is used inside the bracket while casting int to short variable, you receive a compilation error [RHDM-1471]
  • When you upgrade to version 7.8.0, KieBase build fails and you receive org.apache.poi.ooxml.POIXMLException exception [RHDM-1468]
  • When a constraint expression has multiple properties, STANDARD_DRL property fails to recognize multiple properties in an expression [RHDM-1462]

9.6. DMN designer

  • The constraint value is missing in a decision table [RHDM-1460]
  • The undo and redo operations do not work properly when you delete a node in decision requirements graph (DRG) [RHDM-1459]
  • In Business Central, the DMN editor is unable to save the changes in the Properties panel [RHDM-1456]
  • DMN editor is reporting unsaved changes in the DMN files when there are no changes [RHDM-1453]

9.7. Red Hat Business Optimizer

9.8. Red Hat OpenShift Container Platform

  • In Red Hat OpenShift Container Platform, you can add EJB timer related settings to avoid duplicate timer execution [RHPAM-3300]
  • Change the resource requirements for Business Central and KIE Server [RHPAM-3245]
  • When you deploy Red Hat Process Automation Manager on Red Hat OpenShift Container Platform, in the directory for Git indexing, org.uberfire.metadata.index.dir Java setting is not pointing to the shared PersistentVolume (PV) [RHPAM-3141]

Appendix A. Versioning information

Documentation last updated on Tuesday, March 8, 2022.

Appendix B. Contact information

Red Hat Process Automation Manager documentation team: brms-docs@redhat.com

Legal Notice

Copyright © 2023 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.