Release notes for Red Hat Process Automation Manager 7.5

Red Hat Process Automation Manager 7.5

Red Hat Customer Content Services

Abstract

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

Preface

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

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.5 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.5.

2.1. Installation

2.1.1. Image naming and tagging conventions

The Red Hat Process Automation Manager image naming and tagging conventions have changed. Starting with Red Hat Process Automation Manager 7.5.0, the major and minor version is part of the tag itself, along with the micro version. Additionally, the suffix -openshift is replaced with -rhel[version] to signify the underlying operating system version. For example:

  • registry.redhat.io/rhpam-7/rhpam-businesscentral-rhel8:7.5.0 is the Red Hat Process Automation Manager Business Central 7.5.0 image.
  • registry.redhat.io/rhpam-7/rhpam-businesscentral-rhel8:7.5.1 is the Red Hat Process Automation Manager Business Central 7.5.1 image.

2.1.2. Reference implementations

Three reference implementations are available that you can use as starter applications. They are provided in the Red Hat Process Automation Manager 7.5.1 Reference Implementations download, available on the Red Hat Process Automation Manager Software Downloads page in the Red Hat Customer Portal.

Employee Rostering reference implementation

The employee rostering reference implementation enables you to create an application that assigns employees to shifts on various positions in an organization. For example, you can use the application to distribute shifts in a hospital between nurses, guard duty shifts across a number of locations, or shifts on an assembly line between workers.

High available event-driven decisioning reference implementation

A reference implementation for high available event-driven decisioning on Red Hat OpenShift Container Platform is available. You can customize this reference implementation to deploy Drools engine code that requires stateful processing, including rules developed with complex event processing, in an OpenShift environment. Doing this enables the decision engine to process complex event series with high availability.

Vehicle route planning reference implementation

The vehicle route planning reference implementation enables you to create an application that solves a vehicle route planning problem with real-world maps, roads, and vehicles delivering goods to locations, each with a specific capacity. For more information, see the read me file in the vehicle routing ZIP file, included in the reference implementation download.

2.2. Business Central

2.2.1. Decision Model and Notation (DMN) designer improvements

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

  • New Documentation tab that you can use to generate a report of your DMN model. You can print or download the report as an HTML file for offline use.
  • PMML support in DMN included models. You can now use the Included Models tab in the DMN designer to include Predictive Model Markup Language (PMML) models from your project in a specified DMN file. When you include a PMML model within a DMN file, you can invoke that PMML model as a boxed function expression for a DMN decision node or business knowledge model node.

  • Support for JPMML execution of PMML models included in DMN models. For PMML models that you include in DMN models, you can use either the kie-pmml compiler or the full PMML specification implementation with the Java Evaluator API for PMML (JPMML) for PMML execution.

    Important

    Red Hat supports integration with the Java Evaluator API for PMML (JPMML) for PMML execution in Red Hat Process Automation Manager. However, Red Hat does not support the JPMML libraries directly. If you include JPMML libraries in your Red Hat Process Automation Manager distribution, see the Openscoring.io licensing terms for JPMML.

For more information about DMN support in Red Hat Process Automation Manager 7.5, see the following resources:

2.2.2. Ability to convert a guided decision table to a spreadsheet decision table

You can convert a guided decision table in Business Central to an XLS spreadsheet decision table file for offline reference and file sharing. The guided decision table must be an extended entry guided decision table in order to be converted. The conversion tool does not support limited entry guided decision tables. To convert a guided decision table, navigate to the guided decision table asset that you want to convert and in the upper-right toolbar of the guided decision tables designer, click Convert to XLS.

Warning

Guided decision tables and spreadsheet decision tables are different decision table formats that support different features. Any supported features that differ between the two decision table formats are modified or lost when you convert one decision table format to the other.

2.2.3. Bulk reassignment supported for tasks in Business Central

In the Task Inbox and Tasks pages in Business Central, you can now perform bulk reassignment over multiple tasks in a single operation. To reassign tasks in bulk, select two or more tasks, click the Bulk Actions menu in the upper-right corner of the window, and select Bulk Reassign.

In the Tasks reassignment window, enter the user identifier of the user to reassign the tasks to, and click Delegate. For each task selected, a notification is displayed showing the reassignment result.

2.2.4. Bulk actions supported for tasks in Business Central

In the Task Inbox and Tasks pages in Business Central, you can now perform bulk actions over multiple tasks in a single operation. To update tasks in bulk, select two or more tasks, click the Bulk Actions menu in the upper-right corner of the window, and select one of the following bulk actions:

  • Bulk Claim
  • Bulk Release
  • Bulk Resume
  • Bulk Suspend

If a specified bulk action is not permitted based on the task status, a notification is displayed and the operation is not executed on that task.

2.2.5. Process designer

The following list provides a summary of process designer updates:

  • Support for feature parity when you migrate legacy business processes to the new process designer
  • Support for designer parser round-trip for unsupported elements, such as importing models exported by ARIS BPM diagrams, even if they contain elements that are not supported by Red Hat Process Automation Manager
  • A new text annotation BPMN2 element that enables you to retain existing text annotations when you port external processes to the new process designer
  • Support for ISO8601 expressions for user task notifications

2.2.6. Import and export Dashbuilder data in Business Central

You can now import and export Dashbuilder data as ZIP files. To import and export Dashbuilder data, select the Admin icon in the upper-right corner of the Business Central window and select Dashbuilder Data Transfer.

2.2.7. Test scenarios

The test scenarios designer in Business Central is now available with the new features supported in Red Hat Process Automation Manager 7.5.

  • View coverage reports for rule-based models. The test scenarios designer displays the test coverage statistics in the Coverage Report panel on the right side of the test scenarios designer.
  • Download coverage reports for rule-based and DMN-based models. You can now download the test scenario coverage reports in CSV format.
  • You can run test scenarios with stateless KIE sessions. To configure a stateless KIE session, expand the Settings panel of the test scenario and select or clear the Stateless Session check box to indicate whether or not the KIE session is stateless or not.
Note

The test scenario scesim file format is not public. You can only edit the scesim file using the test scenario editor.

2.3. Process Server

2.3.1. Ability to configure the queue size for the planning engine in a Process Server

You can now configure the queue size for the planning engine in a Process Server. The queue size determines how many solver requests can be enqueued to wait for processing while the engine is working on other requests. If the queue is full, new requests are rejected. The default queue size is equal to the number of active CPU cores. To change the queue size, set the org.optaplanner.server.ext.thread.pool.queue.size system property for the Process Server.

2.4. Red Hat OpenShift Container Platform

2.4.1. Automatic minor and patch version updates in operator deployments on Red Hat OpenShift Container Platform

When you deploy Red Hat Process Automation Manager on Red Hat OpenShift Container Platform using the Business Automation Operator, you can now enable automatic minor and patch version updates.

If you enable automatic patch updates, when a new version becomes available all components of your deployment are updated automatically. Normally, there is no interruption in service.

2.4.2. Support for configuring aliases in Red Hat OpenShift Container Platform

You can now configure container aliases for services running on immutable Process Servers on Red Hat OpenShift Container Platform. If you use Smart Router, it automatically routes requests to Process Servers based on the alias name specified in the requests.

Chapter 3. Deprecated and removed components

The components listed in this section have been deprecated or removed.

3.1. Incremental Maven repository

The incremental Maven repository has been removed from the Red Hat Process Automation Manager 7.5 distribution in favor of the full Red Hat Process Automation Manager 7.5 Maven Repository available from the Software Downloads page in the Red Hat Customer Portal (login required).

3.2. Legacy Test Scenarios tool

The legacy Test Scenarios tool was deprecated with 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.

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

Starting with the 7.5 release of Red Hat Process Automation Manager, support for Red Hat OpenShift Container Platform 3.x, including installation using all templates and using the Automation Broker (Ansible Playbook) is deprecated. Support for Red Hat OpenShift Container Platform 3.x will be removed in a future Red Hat Process Automation Manager release. Consider deploying Red Hat Process Automation Manager using the Operator on Red Hat OpenShift Container Platform 4.x.

Chapter 4. Technology preview

This section lists features that are in Technology Preview in Red Hat Process Automation Manager 7.5. 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.

4.1. High-availability authoring on Red Hat JBoss EAP (on premise and with Red Hat OpenShift Container Platform)

Configuration of Business Central for high availability is currently a Technology Preview feature. Search and messaging technology used to enable the search feature is considered an implementation detail. That technology might be replaced in Red Hat Process Automation Manager in a future release while the capability offered might be preserved.

4.2. 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 so it is simple to define a case model at high-level. Case modeling supports three types of tasks: human tasks, sub-processes, and sub-cases.

Note

The case modeler in Red Hat Process Automation Manager 7.5 is a Technology Preview feature and is disabled by default in Business Central. To enable the case modeler preview in Business Central, in the upper-right corner of the window click Settings → Roles, select a role from the left panel, click Editors → (New) Case Modeler → Read, and then click Save to save the changes.

4.3. Process instance migration as a standalone service

Process instance migration is now available as a standalone service that contains a user interface and a back end, and packaged as a Thorntail uber JAR. The process instance migration service enables you to define the migration between two different process definitions, known as a migration plan. You can apply the migration plan to the running process instances in a specific Process Server.

For more information about the process instance migration standalone service, see the Process Instance Migration Service page in GitHub.

4.4. 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 Predictive Model Markup Language (PMML) models or Statistical Machine Intelligence and Learning Engine (SMILE) to implement the service.

4.5. Constraint Streams API

You can use the Constraint Streams API as an alternative to the Drools Rules Language (DRL) to program incremental score calculations in plain Java 8+. The Constraint Streams API is fast, scalable, and debuggable. You can use any IDE to develop and debug solvers using the Constraint Streams API. It uses deltas that enable the engine to redo only necessary calculations. It also supports justifications, so you can review the reason a solution was reached in order to debug the solver.

4.6. 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.

4.7. Red Hat JBoss Data Grid replaces Elasticsearch

Red Hat JBoss Data Grid replaces Elasticsearch as the distributed highly scaleable full-text search and analytics engine for Red Hat Process Automation Manager.

Red Hat Data Grid is built from the Infinispan open-source software project and contains indexing capabilities that enable you to store, search, and analyze high volumes of data quickly and in near-real time. In a Red Hat Process Automation Manager clustered environment, it enables you to perform complex and efficient searches across cluster nodes.

The ConstraintStreams API is currently a Technology Preview feature. It does not cover the full range of Red Hat Business Optimizer engine capabilities.

Chapter 5. Known issues

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

5.1. Installation

Red Hat Process Automation Manager in a Red Hat JBoss Web Server datasource configuration is missing elements [RHPAM-2428]

Issue: When you use the installer to install Red Hat Process Automation Manager in Red Hat JBoss Web Server and you configure a datasource, there are some missing elements that are needed for the setup to work properly.

Steps to reproduce:

  1. Use the installer to install Red Hat Process Automation Manager on Red Hat JBoss Web Server.
  2. When prompted, click Configure Advanced Properties → Configure Database Settings.
  3. Configure your settings and add a user name and password.
  4. Try running the server.

Expected result: Red Hat Process Automation Manager starts.

Actual result: Red Hat Process Automation Manager does not start.

Workaround: Modify the resource in the context.xml file as described in the "Configuring JDBC Web Server data sources" section of Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss Web Server.

On Red Hat JBoss EAP, the Red Hat Process Automation Manager installer creates an incorrect password vault for the created datasource [RHPAM-2407]

Issue: If you use the installer to install Red Hat Process Automation Manager on Red Hat JBoss EAP and you configure database settings, the datasource element in the standalone files is wrong and connection to the database fails.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  1. Use the installer to install Process Server only onto Red Hat JBoss EAP.
  2. When prompted, click Configure Advanced Properties → Configure Database Settings.
  3. Open the standalone.xml or standalone-full.xml file to verify user credentials.

Expected result: The datasource element in the standalone files should look similar to the following, where <NEWDATASOURCE> is the name of your database: 

<password>${VAULT::datasource.<NEWDATASOURCE>::password::1}</password>

Actual Result: The datasource element in the standalone files looks similar to the following: 

<password>:datasource.<NEWDATASOURCE>::password::1</password>

Workaround: Replace the <password> entry with the correct password vault entry for the database. In this example, <NEWDATASOURCE> is the name of your database: 

${VAULT::datasource.<NEWDATASOURCE>::password::1}

5.2. Business Central

You cannot start a task if the Elytron adapter is installed [RHPAM-2450]

Issue: If Business Central on Red Hat JBoss EAP is integrated with RH-SSO using the Elytron adapter, errors are displayed after a task is started.

Steps to reproduce:

  1. Install Red Hat Process Automation Manager on Red Hat JBoss EAP.
  2. Configure Business Central with RH-SSO using the Elytron adapter.
  3. Import a process sample.
  4. Start the process.
  5. Start a task.

Expected result: The task starts correctly.

Actual result: The task does not start and an error is displayed.

Workaround: Use the legacy adapter instead of the Elytron adapter. Enter the following command to install the legacy adapter: 

./bin/jboss-cli.sh -c --file=bin/adapter-install.cli

An error might occur if you import a sample project twice [RHPAM-2434]

Issue: An Unable to complete your request error might appear if you import a sample project that has already been imported.

Steps to reproduce:

  • Import a sample project twice. Note that this error does not always occur.

Workaround: If the sample project that failed to import is present in your space, remove it then import it again.

In the guided rule editor, you cannot use the is contained in comma separated list constraint in combination with complex values [RHPAM-2457]

Issue: In the guided rule editor, you cannot use the is contained in comma separated list constraint in combination with complex values. Complex values are values that contain a comma or are wrapped by brackets.

Workaround: None.

The Bulk Reassign check boxes on the Task List page reset before finishing the selected operation [RHPAM-2387]

Issue: If you select multiple tasks on the Task List page and then select a bulk reassignment operation, when the dialog box appears over the Task List page, the previously selected tasks are no longer selected.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  • On the Task List page, select multiple tasks and choose a bulk reassignment operation.

Expected result: A dialog box appears on top of the Task List page. The list of tasks is visible on the Task List page and the previously selected tasks are still selected.

Actual result: A dialog box appears on top of the Task List page. The list of tasks is visible on the Task List page and the previously selected tasks are not selected.

Workaround: None.

The Bulk Reassign operation fails if you include tasks that are in a state that does not allow reassignment [RHPAM-2386]

Issue: If you select multiple tasks with various states, for example Ready and Reserved, including tasks that are in a state that does not allow reassignment, for example Suspended and Completed, then the bulk reassign operation fails.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  1. Select tasks with various states and include one task that is in the Suspended state.
  2. Run the bulk reassignment. An error message appears telling you that some of the the tasks could not be reassigned because they were not in the correct state.
  3. Click OK.

Expected result: The dialog box closes and the operation is attempted on all of the tasks. Results for particular tasks are presented separately as notifications.

Actual result: The dialog box does not close. When you close it manually by clicking the x in the top right corner, and you check the states of the previously selected tasks, only the tasks processed before first failure are reassigned.

Workaround: Before running the bulk action, filter the tasks and omit any task that will interrupt the reassignment.

In the DMN designer, the DMN file validation operation does not report invalid operators [RHDM-1119]

Issue: In the DMN designer, if the DMN model contains an invalid operator (an operator that does not exist), for example >>>>, the validation operation does not report the invalid operator.

Workaround: None.

5.3. High availability

In a high-availability authoring environment, when one user imports a project, another user is unable to see it [RHPAM-2470]

Issue: When multiple users connect to a high-availability Business Central and one user creates a project, another user cannot see the project.

Steps to reproduce:

  1. Log in to Business Central as two different users (A and B) from two different hosts or browsers.
  2. As user A and as user B, open the same space.
  3. As user A, import a project using an external Git repository URL.

Expected result: As user B, you can see the imported project in the space.

Actual result: As user B, you cannot see the imported project in the space.

Workaround: As user B, reload the space.

In a high-availability authoring environment, role changes in Business Central are not saved [RHPAM-2342]

Issue: If you configure a role change in high-availability Business Central, the change can be lost after a time and the roles reset to defaults.

Workaround: Configure the role change again.

In a high-availability authoring environment, an imported project in Business Central appears multiple times [RHPAM-2372]

Issue: If you import a sample project in high-availability Business Central, the project can appear in the list several times. Some copies might not have all of the assets. The environment can slow down when this issue occurs.

Workaround: Ensure one copy has all of the assets, then remove all other copies. If Business Central performance is slow, restart all of the nodes connected to it.

In a high-availability authoring environment, project creation fails when a Business Central node is down [RHPAM-2475]

Issue: When you create a project, the project creation does not complete. The cause is one Business Central node in a high-availability authoring environment going down.

Workaround: Create the project again.

In a high-availability authoring environment, asset creation is not completed when a Business Central node is down [RHPAM-2476]

Issue: When you create an asset, the asset is not indexed. It is displayed in Business Central but you cannot use it. The cause is one Business Central node in a high-availability authoring environment going down.

Workaround: In the Project Explorer view, open the asset and click Save.

In a high-availability authoring environment, multi-project import slows down Business Central [RHPAM-2477]

Issue: When a user imports multiple projects in a high-availability Business Central with multi-project import enabled, Business Central slows down and consumes significant resources.

Steps to reproduce:

  1. In the Settings menu of Business Central, enable multi-project import.
  2. Enter a space and import all samples at one time.

Expected result: Business Central operates normally and imports the samples.

Actual result: Business Central slows down and consumes a lot of resources. In a Red Hat OpenShift Container Platform environment, the pod eventually fails.

Workaround: Restart all Business Central nodes. To avoid this issue, do not enable multi-project import.

5.4. Process designer

If you try to migrate a process with a sequence flow without the source and target nodes set, you should receive a warning message, but you do not [RHPAM-2453]

Issue: If a process in the legacy process designer contains a sequence flow without the source and target nodes set, and you try to migrate that process to the new process designer, you should receive a warning message, but you do not. It is also not possible to migrate process.

Steps to reproduce:

  1. Create a process in the legacy process designer.
  2. Add a sequence flow to the process, do not set the source and target nodes, and then save the process.
  3. Click the Migrate button.

Expected result: You see a message telling you that the source and target nodes for a sequence flow are not set and you cannot migrate the process.

Actual result: No message appears and you cannot migrate the process.

Workaround: None.

If you migrate a process from the legacy process designer to the new process designer, you receive an incorrect warning that a node will be ignored [RHPAM-2452]

Issue: If you migrate a process from the legacy process designer to the new process designer, you receive a warning that a node will be ignored. However, the node is not ignored and is migrated successfully.

Steps to reproduce:

  1. Create a Start to End process in the legacy process designer.
  2. Migrate the process to the new process designer.

Expected result: No warning about ignoring elements are shown if no elements will be ignored after migration.

Actual result: Warnings are shown that some unknown element will be ignored.

Workaround: Ignore the warnings and confirm that all nodes migrate successfully.

In the new process designer, the warning message for migrating a Group element is missing [RHPAM-2454]

Issue: If you migrate a process that contains a Group element from the legacy process designer to the new process designer, the warning message about ignoring the node is missing.

Steps to reproduce:

  1. Create a process in the legacy process designer.
  2. Add a Group element to the process and then save the process.
  3. Migrate the process from the legacy process designer to the new process designer.

Expected result: You see a warning message about ignoring the node.

Actual result: You do not see the warning message.

Workaround: None.

In the new process designer, some end events have incorrect icons [RHPAM-2413]

Issue: In the new process designer, signal, escalation, compensation, and message end events are not filled, but they should be according to the BPMN 2.0 specification.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Workaround: None.

5.5. Red Hat OpenShift Container Platform

The role properties file configuration is available for internal authentication [RHPAM-2247]

Issue: The role properties file configuration should be available only when RH-SSO or LDAP authentication is used. However, currently it is also available when internal authentication is used.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  1. Open the Business Automation Operator UI.
  2. Assign values to mandatory parameters.
  3. Retain the authentication mode Internal.
  4. Complete the role properties file configuration.
  5. Deploy the result.

Expected result: When internal authentication is used, it is not possible to specify the role properties file.

Actual result: When internal authentication is used, it is possible to specify the role properties file.

Workaround: If you plan to use internal authentication, leave the role properties file property in Business Automation Operator UI empty.

Resource requests have an incorrect name in the customer resource (CR) YAML file [RHPAM-2248]

Issue: Resource requests are specified as request in the Business Automation Operator UI, however in the customer resource definition (CRD) they are specified as requests. Therefore, CPU and memory requests from the UI are not applied.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  1. Open the Business Automation Operator UI.
  2. Assign values to mandatory parameters.
  3. Complete CPU and memory requests for Console.
  4. Check the resulting YAML file.

Expected result: In the generated YAML file, resource requests are specified as requests.

Actual result: In the generated YAML file, resource requests are specified as request.

Workaround: In the generated YAML file, change the resource request specification from request to requests.

Product environment fails to deploy on Amazon Web Services (AWS) with AWS Elastic Block Storage (EBS) because of AWS EBS volume plugin lack of support for ReadWriteMany (RWX) persistent volume access mode [RHPAM-2480]

Issue: Several templates used for installing Red Hat Process Automation Manager on Red Hat OpenShift Container Platform, as well as deployment of several environment types using the Business Automation Operator, fail to deploy on AWS with EBS. The templates and environment types include persistent volume claims that require support for the ReadWriteMany access mode and the AWS EBS volume plugin does not provision persistent volumes with this access mode.

The following templates are affected:

  • rhpam75-managed.yaml
  • rhpam75-prod.yaml
  • rhpam75-prod-immutable-monitor.yaml
  • rhpam75-authoring.yaml
  • rhpam75-authoring-ha.yaml

Workaround: Deploy an NFS server and provision the persistent volumes using NFS. For information about provisioning persistent volumes using NFS, see one of the following guides:

Optaweb Vehicle Routing tests fail due to different versions of dependencies [RHDM-1129]

Issue: Optaweb Vehicle Routing is distributed with the incorrect package-lock.json file. As a result, snapshot tests of the optaweb-vehicle-routing-frontend module fail because of changes in HTML code generated by different versions of dependencies.

Workaround:

  1. Change directory to the optaweb-vehicle-routing-frontend module.

  2. Enter the following command to download the required dependencies: 

    $ npm install

  3. Enter the following command to run the tests: 

    $ npm test
  4. Press the u key to update failing snapshots.

The optaweb-employee-rostering example fails to build with the offline Maven repository ZIP files [RHPAM-2465]

Issue: When you build the optaweb-employee-rostering example with only Business Central and the Red Hat Process Automation Manager offline Maven repository, the build fails with the following message: 

Could not resolve dependencies for project org.optaweb.employeerostering:employee-rostering-server:jar:7.26.0.Final-redhat-00004: The following artifacts could not be resolved: net.jcip:jcip-annotations:jar:1.0.0.redhat-8, org.jboss.logging:jboss-logging:jar:3.3.2.Final-redhat-00001: Could not find artifact net.jcip:jcip-annotations:jar:1.0.0.redhat-8 in bxms-product-repo
Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Workaround: Use the the Red Hat GA repository to fetch the missing artifacts.

Red Hat Business Optimizer is missing an environment variable for thread pool queue size [RHDM-1096]

Issue: The org.optaplanner.server.ext.thread.pool.queue.size system property has been added to the Process Server Red Hat Business Optimizer extension. This property cannot be directly set on the Process Server image.

Workaround: Use the existing JAVA_OPTS_APPEND environment variable and append the system property.

The Process Server pod fails to start after a user updates the BusyBox image on Red Hat OpenShift Container Platform [RHPAM-2431]

Issue: In a Red Hat OpenShift Container Platform environment, a Process Server pod fails to start or restart with the latest version of the BusyBox image.

Steps to reproduce:

  1. In your Red Hat OpenShift Container Platform environment, use a template or operator to deploy a Process Server that uses a MySQL or PostgreSQL database server.

  2. Enter the following command to manually update the OpenShift registry to the latest BusyBox image: 

    $ docker pull busybox
  3. Scale the Process Server pod down to 0 replicas and then scale up.

Expected result: The Process Server pod starts normally.

Actual result: The Process Server pod fails to start and remains at 0 replicas.

Workaround:

  1. On a local machine that has access to the cluster and has Docker installed, enter the following command to pull the BusyBox image version 1.28.4: 

    $ docker pull docker.io/busybox:1.28.4

  2. Enter the following comand to tag the image with the latest tag: 

    docker tag docker.io/busybox:1.28.4 myopenshiftcluster/openshift/busybox:latest

  3. Push the image into your Red Hat OpenShift Container Platform environment. For instructions, refer to the following documentation:

High available event-driven decisioning (HA CEP server) build fails [RHPAM-2530]

Issue: The image build for the HA CEP server fails with the following message: 

The command '/bin/sh -c microdnf install --nodocs java-1.8.0-openjdk-headless && microdnf clean all' returned a non-zero code: 141

The probem is caused by a recently found issue with microdnf.

Workaround:

In the springboot directory, edit the Dockerfile file. Replace the line that contains the microdnf command with the following line: 

RUN microdnf install java-1.8.0-openjdk-headless && microdnf clean all

Chapter 6. Fixed issues in Red Hat Process Automation Manager 7.5.0

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

Note

Red Hat Decision Manager fixed issues apply to Red Hat Process Automation Manager as well. For a list of Red Hat Decision Manager 7.5.0 fixed issues, see the Release Notes for Red Hat Decision Manager 7.5

6.1. Decision engine

  • Add a proxy to Maven repositories that are read from the settings.xml file if an active proxy is set up [RHPAM-2191]

6.2. Business Central

  • A group cannot be added in Business Central integrated with RH-SSO [RHPAM-2036]
  • Revert Keycloak version from 6.0.1 to 4.8.3.Final [RHPAM-2371]
  • It is not possible to create a space in Business Central [RHPAM-2351]
  • Extracting source code from Business Central fails when RH-SSO is enabled [RHPAM-2170]
  • You cannot clone a git repository immediately after rebooting Red Hat Process Automation Manager [RHPAM-2297]
  • An unexpected error occurs when you add a deployment unit in the New Server configuration [RHPAM-2298]
  • You resolve dependencies if you use kie.maven.offline.force=true when starting the server [RHPAM-2278]
  • You delete a space or project created by the migration tool [RHPAM-2256]
  • On the Task List page, the Active Filters list is not in sync with Filters panel check boxes [RHPAM-1956]

6.3. Red Hat OpenShift Container Platform

  • The monitoring console on OpenShift throws a MissingObjectException jgit error [RHPAM-1101]
  • Various errors occur when when you starting clustered Business Central [RHPAM-1747]
  • Strategy and access mode corrections [RHPAM-2314]
  • The OutOfMemoryError error on DataGrid causes issues on project import indexing [RHPAM-2354]
  • If you add an SSH key on the Business Central Settings→ SSH Keys page, the key does not persist on OpenShift [RHPAM-2296]
  • Add Red Hat Process Automation Manager version validation for Red Hat Process Automation Manager operator [RHPAM-2289]
  • Changes in users and roles made by Business Central are not persisted [RHPAM-2282]
  • DB2 fails with the externaldb template [RHPAM-2261]
  • Validation failure does not move focus to the affected page [RHPAM-2246]
  • There are duplicate Base build image fields in Process Server configurations [RHPAM-2245]
  • An authentication error occurs when using the jbpm rest endpoint at Business Central [RHPAM-2361]
  • Error editing guided decision tables [RHPAM-2220]

6.4. Process engine

  • PIM is declaring io.thorntail:bom-all [RHPAM-2328]
  • Timers do not recover after database disconnection [RHPAM-2180]

6.5. Process designer

  • The new process designer processes cannot be saved if they are opened in parallel with DMN [RHPAM-2358]

6.6. Process Server

  • Cannot enable swagger documentation when using spring-boot-kieserver [RHPAM-1999]

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

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

Note

Red Hat Decision Manager fixed issues apply to Red Hat Process Automation Manager as well. For a list of Red Hat Decision Manager 7.5.1 fixed issues, see the Release Notes for Red Hat Decision Manager 7.5

7.1. Installer

  • On Red Hat JBoss EAP, the Red Hat Process Automation Manager installer creates an incorrect password vault for the created datasource [RHPAM-2407]

7.2. Business Central

  • Dashbuilder does not close ResultSet or statement instances [RHPAM-2391]
  • The Save button is not available for XLS decision tables [RHPAM-2335]
  • After you edit comma separated lists in the guided rule editor, escape characters are added to the code [RHPAM-2323]
  • The ExtensibleXmlParser error is thrown for valid processes with dynamic user assignments [RHPAM-2388]
  • The legacy test scenario fails if you do not change the default expect values [RHPAM-2320]
  • The legacy test scenario fails if you use the java.time.LocalDate type field in the expect section [RHPAM-2303]
  • If you filter by asset type, no results are displayed [RHPAM-2287]
  • If you shutdown the server, the web UI hangs without an error message [RHPAM-1931]
  • The Bulk Reassign operation fails if you include tasks that are in a state that does not allow reassignment [RHPAM-2386]
  • The Bulk Reassign check boxes on the Task List page reset before finishing the selected operation [RHPAM-2387]

7.3. Maven repository

  • The OptaWeb Employee Rostering example fails to build with the offline Maven repository ZIP [RHPAM-2465]
  • You cannot create custom workitem handlers in Red Hat Process Automation Manager 7.5 [RHPAM-2493]
  • If the URL used to import a Git project has a leading or trailing space, the import fails [RHPAM-2344]
  • An error occurs if you try to generate a workitem handler through the command line by using the Maven jbpm-workitems-archetype archetype [RHPAM-1772]

7.4. Red Hat OpenShift Container Platform

  • The role properties file configuration is available for internal authentication [RHPAM-2247]
  • Resource requests have an incorrect name in the customer resource (CR) YAML file [RHPAM-2248]

7.5. PMML

  • If a guided scorecard name starts with a lowercase letter, it cannot be tested by the legacy test scenario [RHPAM-2307]

7.6. Process engine

  • The ConditionalEvent statement is not triggered if a process ID contains a hyphen [RHPAM-2304]

7.7. New process designer

  • When you add or remove a field from a form, the form scrolls up [RHPAM-1224]
  • The signal name cannot be dynamic [RHPAM-2360]
  • Some end events have incorrect icons [RHPAM-2413]
  • Multiple scroll bars appear on the canvas [RHPAM-2356]
  • An error is logged if you use a reusable subprocess node with no dataOutput mapping [RHPAM-2412]

7.8. Process Server

  • Log files are flooded with the Unable to load key store. Using password from configuration message [RHPAM-2322]

Appendix A. Versioning information

Documentation last updated on Thursday, October 31, 2019.

Legal Notice

Copyright © 2020 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.