Release notes for Red Hat Process Automation Manager 7.7
Red Hat Customer Content Services
brms-docs@redhat.com
Abstract
Preface
These release notes list new features, features in technology preview, known issues, and issues fixed in Red Hat Process Automation Manager 7.7.
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.7 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.
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.7.
2.1. Reference implementations
The high available event-driven decisioning reference implementations are improved.
No root access in the container required for HA CEP services
When implementing high available event-driven decisioning in Red Hat Process Automation Manager, the HA CEP (high-availability complex event processing) services do not require root access within the container.
On-the-fly KJAR updating of HA CEP services
When implementing high available event-driven decisioning in Red Hat Process Automation Manager, you can update KJAR HA CEP services without removing and redeploying the HA CEP solution. The content of working memory is preserved.
2.2. Business Central
2.2.1. Maven archetype support in Business Central
Maven archetype support is now available in Business Central. To access this functionality, select the Admin icon in the top-right corner of the screen and select the Archetypes option on the Business Central Settings page. The following list provides a summary of Maven archetypes enhancements:
- You can list, add, validate, set a default, and delete the archetypes.
- You can use them as a template when creating a new project in Business Central.
- To manage all available archetypes in spaces, go to Design → <your_space> → Settings in Business Central.
For more information about archetypes management, see Configuring Business Central settings and properties.
2.2.2. Test Scenarios
The test scenarios designer in Business Central is now available with the new features supported in Red Hat Process Automation Manager 7.7.
- In DMN-based as well as rule-based test scenarios, it is now possible to define the value of a collection like a list or a map by using an expression in both GIVEN and EXPECT columns. To add an expression, you can now choose Define list from the collection editor.
-
You can now use the KIE Server REST API to execute the test scenarios externally. It executes the test scenarios against the deployed project. This functionality is disabled by default, use
org.kie.scenariosimulation.server.ext.disabled
system property to enable it.
For more information about test scenarios designer in Business Central, see Testing a decision service using test scenarios.
2.2.3. Ability to create a project from empty repositories
You can now create a new project in Business Central by importing an empty GitHub or GitLab external repository.
2.2.4. Squash commit on change requests
You can now squash multiple commits into a single commit and add the commit to a target branch for a change request. For more information about change requests in Business Central, see Managing projects in Business Central.
2.2.5. Navigation from subprocess instance to parent process instance using the process instance page in Business Central
The process instance page in Business Central is now available with new navigation features for the parent and subprocess instance.
- In the Instance Details tab, you can now click the Parent Process Instance ID field to navigate to the parent Instance Details tab.
- In the Diagram tab, you can now see a new menu containing links of the parent process and subprocess to navigate between the subprocess and parent process Diagram tab.
For more information about process instance management, see Managing and monitoring business processes in Business Central.
2.2.6. Code completion for FEEL expressions in Decision Model and Notation (DMN) designer
When typing a FEEL expression in the boxed literal expression editor, you can now see FEEL functions appear as suggestions that you can apply to complete the expression if required.
2.2.7. Decision Model and Notation (DMN) designer improvements
The Decision Model and Notation (DMN) designer in Business Central includes the following notable enhancements:
- New visual indication for the data type nesting levels in a project allowing users to quickly reference nesting details without leaving the editor.
- Zero values are hidden in the Data Type constraints wizard to eliminate wasted screen space.
- Improved visual and functional support for the search component placeholder.
- Support for drag and drop to reorder data types.
2.2.8. New CaseLogCleanupCommand
command
Starting with Red Hat Process Automation Manager 7.7, support for the CaseLogCleanupCommand
command to clean up cases based on different parameters.
2.2.9. Support for branch management and performing Maven actions on branches using the REST API
Users can now manage branches and perform Maven action on branches using the REST API:
Return all branches in a specific project and space:
[GET] /spaces/{spaceName}/projects/{projectName}/branches::
Add a specific branch to a specific project and space:
[POST] /spaces/{spaceName}/projects/{projectName}/branches::
Delete a specific branch from a specific project and space:
[DELETE] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}::
Compile a specific branch in a specific project and space. If branchName
is not specified, then the request defaults to using the master branch.
[POST] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}/maven/compile::
Install a specific branch in a specific project and space. If branchName
is not specified, then the request defaults to using the master branch.
[POST] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}/maven/install::
Test a specific branch in a specific project and space. If branchName
is not specified, then the request defaults to using the master branch.
[POST] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}/maven/test::
Deploy a specific branch in a specific project and space. If branchName
is not specified, then the request defaults to using the master branch.
[POST] /spaces/{spaceName}/projects/{projectName}/branches/{branchName}/maven/deploy::
For more information about REST API for Business Central spaces and projects, see Interacting with Red Hat Process Automation Manager using KIE APIs.
2.2.10. Support for DMN 1.3
Red Hat Process Automation Manager 7.7 is now DMN 1.3 ready.
2.2.11. Supported languages
Starting with the 7.7 release, the Red Hat Process Automation Manager user interface is now localized in Spanish and French in addition to English and Japanese.
2.3. Decision engine
2.3.1. Default support for executable rule models in the kie-maven-plugin
plugin
Rule assets in Red Hat Process Automation Manager are built from executable rule models by default with the standard kie-maven-plugin
plugin. Executable rule models are embedded models that provide a Java-based representation of a rule set for execution at build time. The executable model is a more efficient alternative to the standard asset packaging in previous versions of Red Hat Process Automation Manager and enables KIE containers and KIE bases to be created more quickly, especially when you have large lists of DRL (Drools Rule Language) files and other Red Hat Process Automation Manager assets.
If you are upgrading to Red Hat Process Automation Manager 7.7 from a previous version of the product and you have not already enabled executable rule models, you must add the required dependency to your existing Red Hat Process Automation Manager projects so that your rule assets are built from executable models in Red Hat Process Automation Manager 7.7.
For instructions on enabling executable rule models when upgrading to Red Hat Process Automation Manager 7.7, see Patching and upgrading Red Hat Process Automation Manager 7.7.
For more information about executable rule models, see Packaging and deploying a Red Hat Process Automation Manager project.
2.4. Integration
2.4.1. Spring Boot applications
Spring Boot applications now provide Spring bean support for the notificationlistener
class.
2.5. Red Hat Business Optimizer
2.5.1. Added Spring Boot starter
Red Hat Business Optimizer now includes a Spring Boot starter. You can use the Spring Boot starter to avoid common issues with class loading and use application.properties
to overwrite the solver configuration. The solverConfig.xml
file is no longer required because the starter automatically detects @PlanningSolution
and @PlanningEntity
annotations. The constraint streams API is improved. You can now modify your streams using the groupBy()
building block.
For more information, see Creating Red Hat Process Automation Manager business applications with Spring Boot.
2.5.2. SolverManager
You can use SolverManager as wrapper for one or more Solver instances to simplify planning REST API and other enterprise services. The solve(…)
methods differ from the normal Solver.solve(…)
method:
-
SolverManager.solve(…)
schedules a problem for asynchronous solving without blocking the calling thread. This avoids timeout issues of HTTP and other technologies. It returns immediately. -
SolverManager.solve(…)
solves multiple planning problems of the same domain, in parallel.
SolverManager supports batch solving and solving that displays the progress to the end-user:
public class TimeTableService { private SolverManager<TimeTable, Long> solverManager; // Returns immediately, ok to expose as a REST service public void solve(Long timeTableId) { solverManager.solveAndListen(timeTableId, // Called once, when solving starts this::findById, // Called multiple times, for every best solution change this::save); } public TimeTable findById(Long timeTableId) {...} public void save(TimeTable timeTable) {...} public void stopSolving(Long timeTableId) { solverManager.terminateEarly(timeTableId); } }
2.6. Red Hat OpenShift Container Platform
2.6.1. Support for Git hooks in operator deployment on Red Hat OpenShift Container Platform
When deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform using the operator, you can configure Git hooks to enable interaction between the built in Git repository of Business Central and other repositories.
For more information, see Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using Operators.
2.6.2. Support for role mapping in operator deployment on Red Hat OpenShift Container Platform
When deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform using the operator and using RH-SSO or LDAP authentication, you can configure role mapping to link roles defined in Red Hat Process Automation Manager to different roles defined in RH-SSO or LDAP.
For more information about role mapping in operator deployment on Red Hat OpenShift Container Platform, see Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using Operators.
2.6.3. Support for external database drivers in operator deployment on Red Hat OpenShift Container Platform
When deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform using the operator and configuring a KIE Server to use an external database server, you can configure the use of an Oracle, Sybase, DB2, or MS SQL server.
For more information, see Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using Operators.
2.6.4. Support for JVM configuration in operator deployment on Red Hat OpenShift Container Platform
When deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform using the operator, you can set custom JVM configuration for Business Central and KIE Server pods.
For more information about JVM configuration in operator deployment on Red Hat OpenShift Container Platform, see Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using Operators.
2.6.5. Deploying an authoring environment on Red Hat OpenShift Container Platform without ReadWriteMany support
When deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform, you can deploy an authoring environment if your Red Hat OpenShift Container Platform infrastructure does not provision persistent modules that support the ReadWriteMany mode.
For more information, see Deploying a Red Hat Process Automation Manager authoring environment on Red Hat OpenShift Container Platform.
2.6.6. A single built-in user account for communication between Business Central and KIE Server
Red Hat Process Automation Manager now uses a single built-in administrative user account for communication between Business Central and KIE Server. You no longer need to configure multiple built-in user accounts.
For more information, see Deploying a Red Hat Process Automation Manager authoring environment on Red Hat OpenShift Container Platform.
2.6.7. Support for concurrent service deployment on a KIE Server in a Red Hat Process Automation Manager authoring environment on Red Hat OpenShift Container Platform
If you deploy a Red Hat Process Automation Manager authoring environment on Red Hat OpenShift Container Platform 3.x using templates, you can deploy several services on the same KIE Server concurrently, without needing to wait for a deployment to complete before you can start the next deployment. This functionality is provided by the ControllerBasedStartupStrategy setting that applies to communication between Business Central and KIE Server. You can also enable this strategy when deploying on Red Hat OpenShift Container Platform 4.x using the operator.
For more information, see Deploying a Red Hat Process Automation Manager authoring environment on Red Hat OpenShift Container Platform.
2.6.8. Support for deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform 4.3
Deploying Red Hat Process Automation Manager using the operator on Red Hat OpenShift Container Platform 4.3 is now supported.
For more information about deploying Red Hat Process Automation Manager on Red Hat OpenShift Container Platform 4.3, see Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using Operators.
2.6.9. Red Hat JBoss EAP version updated to 7.2.6
In Red Hat Process Automation Manager images for Red Hat OpenShift Container Platform, the Red Hat JBoss EAP version is updated to 7.2.6.
Chapter 3. Deprecated and removed components
3.1. Deprecated components
The components listed in this section have been deprecated.
3.1.1. 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.1.2. 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 using all templates to install Red Hat Process Automation Manager, 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.
3.1.3. Legacy process designer
The legacy process designer in Business Central is deprecated in Red Hat Process Automation Manager 7.6.0. The legacy process designer will not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer. Create all new processes in the new process designer. For information about migrating projects to the new designer, see Managing projects in Business Central.
3.2. Removed components
The component listed in this section are removed.
3.2.1. Legacy Business process asset
The legacy Business process asset is removed in Red Hat Process Automation Manager 7.7. Use the new Business process asset instead.
3.2.2. Removed supported languages
In the Red Hat Process Automation Manager user interface, support for the Chinese, German, and Portuguese languages is now removed.
Chapter 4. Technology preview
This section lists features that are in Technology Preview in Red Hat Process Automation Manager 7.7. 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
.
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. Red Hat OpenShift Container Platform 4.x deployment on restricted networks
You can use Operator Lifecycle Management to deploy Red Hat Process Automation Manager on Red Hat OpenShift Container Platform 4.x on restricted networks that do not have a connection to the public Internet.
For more information about deployment in a restricted network, see Deploying a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using Operators.
4.2. 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.
4.3. 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.
The case modeler in Red Hat Process Automation Manager 7.7 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.4. 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 KIE Server.
For more information about the process instance migration standalone service, see the Process Instance Migration Service page in GitHub.
4.5. 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.6. 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. 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. Note that the Constraint Streams API fully supports the NQueens, Task assigning, and Flight Crew Scheduling use cases.
4.7. 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 5. Known issues in Red Hat Process Automation Manager 7.7.0
This section lists known issues with Red Hat Process Automation Manager 7.7.
5.1. Business Central
In a high-availability deployment of Business Central, deploying a service to a KIE Server using Business Central intermittently fails [RHPAM-2830]
Issue: In a high-availability deployment of Business Central, Sometimes the service is not deployed to a KIE Server when you use the Business Central user interface in a high-availability deployment.
Workaround: There is no workaround in an on-premise deployment using the Red Hat JBoss EAP. Do not use an on-premises high-availability deployment of Business Central to deploy services to KIE Servers.
In a deployment on Red Hat OpenShift Container Platform, the issue is resolved starting in Red Hat Process Automation Manager version 7.7.1. When you deploy a high-availability authoring environment on Red Hat OpenShift Container Platform in Red Hat Process Automation Manager version 7.7.0, you must enable the OpenShiftStartupStrategy
setting. For instructions about enabling this setting, see Enabling the OpenShiftStartupStrategy setting to connect additional KIE Servers to Business Central in the Deploying a Red Hat Process Automation Manager authoring environment on Red Hat OpenShift Container Platform document. You must complete this procedure even if you do not connect any additional KIE Servers to Business Central.
When you log out and log back in to Business Central, the language switches to English instead of the selected language [RHPAM-2779]
Issue: In Business Central, when you select a language from the Languages drop-down menu and log out and log back in to Business Central, the language switches to English instead of the selected language.
Steps to reproduce:
- In Business Central, select the Admin icon in the top-right corner of the screen and select Languages.
- Select French from the Languages drop-down menu.
- Click Ok.
- Log out of Business Central.
- Log in to Business Central.
- In Business Central, select the Admin icon in the top-right corner of the screen and select Languages.
Expected result: A dialog box with a list of languages appears.
Actual result: Business Central is reloaded and the language switches to English instead of French.
Workaround: Select the Admin icon in the top-right corner of the screen, select Languages and select the desired language.
An error occurs during a WAR file deployment with invalid jandex index files in Business Central [RHPAM-2742]
Issue: When you deploy Business Central or KIE Server WAR
files to Red Hat JBoss EAP or Thorntail, an invalid jandex index file error occurs with the following message:
WFLYSRV0002: Could not read provided index: /content/kie-server.war/WEB-INF/lib/kubernetes-client-4.6.0.jar/META-INF/jandex.idx
The alerts panel mixes the messages from multiple projects instead of showing messages related just to the opened project [RHDM-1243]
Issue: In the Alerts panel, you can see alert messages from multiple projects instead of only messages related to the opened project.
Steps to reproduce:
- Start Business Central.
- Open MySpace.
-
Add a project named
a-project
. -
Add a DMN asset named
a-model
. -
Add a decision node named
A-Decision
but do not specify its expression. -
Click Save to save the
a-model
. - Return to MySpace.
-
Add a project named
b-project
. -
Add a DMN asset named
b-model
. -
Add a decision node named
B-Decision
but do not specify its expression. -
Click Save to save the
b-model
.
Expected result: The Alerts panel does not mix messages from multiple projects.
Actual result: The Alerts mixes messages from multiple projects.
Workaround: None.
Dashbuilder data transfer feature does not work on Windows [RHPAM-2751]
Issue: The Dashbuilder data transfer feature does not work on Windows. You can not export and import the Dashbuilder related data out of or into Business Central.
Steps to reproduce:
- Start Business Central on Windows.
- Select the Admin icon in the top-right corner of the screen and select Dashbuilder Data Transfer.
- Try to export or import some data.
Expected result: You can export or import dashboard data on Windows.
Actual result: You cannot export or import dashboard data on Windows.
Workaround: None.
5.2. Process Designer
If you try to migrate a process with a custom data type containing <
>
characters, you receive a warning message [RHPAM-2772]
Issue: It is not possible to migrate a process with a custom data type containing <
>
characters. You receive an empty error message in the Migrate Diagram window.
Steps to reproduce:
- Create a process in the legacy process designer.
-
Define a process variable with the name and custom data type containing
<
>
characters. - Migrate the process to the new process designer.
Expected result: You can migrate the process to the new process designer. If the process is broken, an error message appears telling you that you cannot migrate the process.
Actual result: Warnings are shown that you cannot migrate the process.
Workaround: Remove <
and >
characters from custom type of all process variable definitions before you start the migration.
If you use the '^' character in the subject of a user task notification an error occurs [RHPAM-2763]
Issue: In the the process designer, if you use the ^
character in Notifications subject in user task it break a process.
Steps to reproduce:
- Create an user task.
- Click Notifications to specify notifications associated with the user task.
-
Enter the subject
^
in the Notifications. - Click Save.
- Save and reopen the process.
Expected result: The process designer opens and the process is not broken.
Actual result: The process is broken. A system error message appears.
Workaround: Do not use ^
character in the Notifications subject.
Called element in reusable sub process is not populated [RHPAM-2760]
Issue: In the process designer, the reusable sub process is not populated in the Called element drop-down list.
Steps to reproduce:
- Create process A.
- Create process B.
- Create reusable sub process in process B.
- Click Called element property.
Expected result: Called element property is populated.
Actual result: Called element property is not populated.
Workaround: Deactivate the Reusable sub-process and activate it again.
An error occurs when editing the process during restoring the other process [RHPAM-2757]
Issue: In the process designer, While editing the process when you try to restore other process an error message is shown.
Steps to reproduce:
- Create process A and do not close this process.
- Create process B.
- Make a change in process B and click Save.
- Click Latest version and select Version 1. Do not click Restore.
- Open the process A.
- Make a change in process A and click Save.
Expected result: No error messages are shown.
Actual result: An error message is shown.
Workaround: Finish restoring the previous version by clicking Restore before you start editing other processes.
You cannot remove the case file and global variables [RHPAM-2643]
Issue: When editing a case definition in process designer, you can add case file variables in the Case Management section, but you cannot delete them. It is also not possible to delete the global variables.
Steps to reproduce:
- Create a case project.
- Create a case definition.
- In the Properties panel add a case file variable in the Case Management section.
- Add a global variable in the Properties panel.
- Try to delete the case file variable and global variable.
Expected result: A trash can icon appears next to each variable. After you click the icon, the variable is removed.
Actual result: It is not possible to delete variables and the trash can icon is missing.
Workaround:
- Download the process or a case.
-
Locate the case file variable and global variable in the downloaded
.bpmn
file and delete them. - Delete the process or a case from Business Central.
-
Import the previously downloaded and edited
.bpmn
file back into Business Central.
Ruleflow group is not populated [RHPAM-2740]
Issue: In the process designer, the Ruleflow group menu is not populated with the rule flow groups defined in the project.
Steps to reproduce:
- Create a new DRL file containing a rule flow group.
- Create a new process.
- Activate the Business Rule task.
- Click the Rule Flow Group property of the Business Rule task.
Expected result: All the rule flow groups from the project are listed in the Rule Flow Group drop-down menu.
Actual result: The Rule flow Group drop-down menu is empty.
Workaround:
- Click on the canvas.
- Click the Rule flow Group drop-down menu again.
5.3. DMN Designer
In the DMN Designer, you cannot convert a Java class with that contains an invalid DMN identifier [RHDM-1231]
Issue: When you try to convert a Java class to a DMN data type and the Java class contains a field name, you will receive an error.
Workaround: None.
Chapter 6. Fixed issues in Red Hat Process Automation Manager 7.7.0
Red Hat Process Automation Manager 7.7.0 provides increased stability and fixed issues listed in this section.
Red Hat Decision Manager fixed issues apply to Red Hat Process Automation Manager as well. For a list of Red Hat Decision Manager 7.7.0 fixed issues, see the Release Notes for Red Hat Decision Manager 7.7
6.1. Business Central
- When you add a deployment unit and manually enter GAV values, the runtime strategy is not set to the configured default value [RHPAM-2623]
- When you save a filter and then activate it, an error message displays [RHPAM-2545]
- In the guided rule editor, you cannot use a combination of complex values [RHPAM-2457]
- The state of a KIE Server is not updated in the server template after the server disconnects and reconnects to Business Central [RHPAM-2544]
-
The guided rule editor removes
matches
operator from the rule file [RHPAM-2631]
6.2. Process Designer
- If the process designer Properties panel is open and you click the Maximize button, the panel closes and restores the panel [RHPAM-2613]
- Validation for a signal name fails if the name includes spaces, colons (:), or other special characters [RHPAM-2557]
- When you create a gateway, no options are available from the Default Route drop-down list in the Properties panel [RHPAM-2536]
6.3. Process instance migration
- The process instance migration service does not work with an Oracle database [RHPAM-2558]
6.4. Process engine
- Business Central fails to display process details when you use Smart Router to configure multiple KIE Servers [RHPAM-2568]
- When you try to reopen a closed case, it does not resume from the point at which it was closed rather it creates a new process instance [RHPAM-2556]
6.5. Red Hat OpenShift Container Platform
- Optaweb Vehicle Routing tests fail due to different versions of dependencies [RHDM-1129]
6.6. Offline Maven repository
-
The
offliner
tool reports errors when it downloads artifacts for an offline Maven repository [RHPAM-2234]
6.7. DMN designer
- When you change a decision table header in the Properties panel, the change is not saved [RHDM-1181]
-
When you import a data object from a Java class, fields that have the Java
Date
type are not converted to the DMNdate
type [RHDM-1145] -
When you import a data object from a Java class, a field of the Java
List
type is not converted to the DMNcollection
type [RHDM-1144]
Chapter 7. Known issues in Red Hat Process Automation Manager 7.7.1
This section lists known issues with Red Hat Process Automation Manager 7.7.1.
7.1. Red Hat OpenShift Container Platform
You can not deploy immutable KIE Server environments on Red Hat OpenShift Container Platform using Operators [RHPAM-2942]
Issue: Immutable KIE Server environments are unable to deploy on Red Hat OpenShift Container Platform using Operators.
Steps to reproduce:
- Create a KIE application in the Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform using Operators.
- To deploy immutable KIE Server environments, use the following YAML file:
apiVersion: app.kiegroup.org/v2 kind: KieApp metadata: name: rhpam-production-immutable annotations: consoleName: rhpam-production-immutable consoleTitle: PAM Production Immutable consoleDesc: Deploys a PAM Production Immutable environment spec: environment: rhpam-production-immutable useImageTags: true objects: servers: - build: kieServerContainerDeployment: rhpam-kieserver-library=org.openshift.quickstarts:rhpam-kieserver-library:1.6.0-SNAPSHOT gitSource: uri: https://github.com/jboss-container-images/rhpam-7-openshift-image.git reference: master contextDir: quickstarts/library-process
Expected result: Immutable KIE Server deployment errors must not be present in the generated YAML file.
Actual result: The generated YAML file fails with the immutable KIE Server deployment errors.
Workaround: For successful KIE Server deployment on Red Hat OpenShift Container Platform using Operators, use useImageTags
flag.
You can not create custom image for database [RHPAM-2948]
Issue: It is not possible to build a custom extension image for database.
Steps to reproduce:
Download the following
templates.zip
file.curl --insecure --output templates.zip http://rcm-guest.app.eng.bos.redhat.com/rcm-guest/staging/rhpam/RHPAM-7.7.1.CR1/rhpam-7.7.1-openshift-templates.zip
Unzip the
templates.zip
file content.unzip -q templates.zip
For an example, make the image build for MySQL database.
cd templates/contrib/jdbc make build mysql
Expected result: You can create and build a custom extension image for database.
Actual result: You can not build a custom extension image for database.
Workaround: Specify the following repository in the base-db-overrides.yaml
file and restart the image build.
name: "quay.io/kiegroup/jboss-kie-${DATABASE_TYPE}-extension-openshift-image"
Chapter 8. Fixed issues in Red Hat Process Automation Manager 7.7.1
Red Hat Process Automation Manager 7.7.1 provides increased stability and fixed issues listed in this section.
Red Hat Decision Manager fixed issues apply to Red Hat Process Automation Manager as well. For a list of Red Hat Decision Manager 7.7.1 fixed issues, see the Release Notes for Red Hat Decision Manager 7.7
8.1. Business Central
-
In Business Central,
NotificationListener
is starting without ISO expression [RHDM-1278] - Stored credentials are not encrypted when you import a git repository [RHPAM-2838]
- Business Central latency is correlated with the number of group memberships [RHPAM-2708]
8.2. Process engine
- When a process triggers an intermediate timer, the event subprocess with the timer is also fired [RHPAM-2864]
- An error boundary event is unable to handle an exception thrown by reusable sub-process node [RHPAM-2782]
-
When a test starts with a high number of processes and timers, then the server throws an
OutOfMemoryError
error before all the process instances are created [RHPAM-2912]
8.3. Installer
- When you run the Red Hat Process Automation Manager installer the installation path step references Red Hat JBoss Web Server 5.1 instead of Red Hat JBoss Web Server 5.2 [RHPAM-2745]
8.4. Integration
-
Springboot support for
@Autowired
beans in theNotificationListener
is missing [RHPAM-2705]
8.5. Red Hat OpenShift Container Platform
-
In Business Central, you can not login with the newly created
adminPassword
[RHPAM-2777] -
Business Central does not accept the newly created
adminUser
andadminPassword
. It allows you to login with old credentials [RHPAM-2762]
Appendix A. Versioning information
Documentation last updated on Monday, May 25, 2020.