6.4 Release Notes
Release Notes for Red Hat JBoss BRMS
Red Hat Customer Content Services
brms-docs@redhat.com
Emily Murphy
Gemma Sheldon
Michele Haglund
Mikhail Ramendik
Stetson Robinson
Vidya Iyengar
Abstract
Chapter 1. Introduction
6.4 Update 6 introduces a small change into the database schema. You must apply the bpms-6.4-to-7.0.sql
script to your database before you run Red Hat JBoss BPM Suite or Red Hat JBoss BRMS 6.4.6. This script is located in the upgrade-scripts/<database-type>
directory, available from the Red Hat JBOSS BPM Suite 6.4 Update 6 and the Red Hat JBOSS BRMS 6.4 Update 6 zip files which you can download from the Red Hat Customer Portal.
1.1. About Red Hat JBoss BRMS
Red Hat JBoss BRMS is an open source decision management platform that combines Business Rules Management and Complex Event Processing. It automates business decisions and makes that logic available to the entire business.
Red Hat JBoss BRMS 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 without requiring assistance from IT personnel.
The list of supported configurations for Red Hat JBoss BRMS is available at the Red Hat Customer Portal.
1.2. What Is New in Red Hat JBoss BRMS 6.4
Red Hat JBoss BRMS 6.4 is a minor release over the previous version 6.3. Noteworthy new features and improvements in this release are described below.
1.2.1. User Interface Improvements
- The Realtime Decision Server now allows filtering the containers based on status and GAV (Maven Group ID, Artifact ID, and version). For more information, see the Containers and Unmanaged Intelligent Process Server Environment sections of the Red Hat JBoss BPM Suite 6.4 Development Guide.
- The guided rule editor now enables you to use formulas for composite field constraints. When adding constraints to a pattern, the Multiple Field Constraint selection (All of (and) and Any of (or)) supports the use of formulas in addition to expressions. For more information, see the WHEN Conditions in Guided Rule Templates section of the Red Hat JBoss BRMS 6.4 User Guide.
1.2.2. Integration and Miscellaneous
- The Google Chrome browser version 54.0.2840.7 is now supported.
- Support for Russian and Traditional Chinese is no longer available for Red Hat JBoss BRMS 6.4.
- Support for Java Development Kit (JDK) version 6 is no longer available for Red Hat JBoss BRMS 6.4.
- Red Hat JBoss Developer Studio Integration Stack 10.0.0.GA supports Red Hat JBoss BRMS 6.4.
- Red Hat JBoss Fuse 6.3 integration pack now includes and supports Red Hat JBoss BRMS 6.4.
- The Update-04 for JBoss Operations Network (JON) 3.3 plugin is available for use with Red Hat JBoss BRMS 6.4.
- Spring integration has been upgraded from Spring 3.x to 4.3.
- KieScanner support is now available in Blueprint integration. For more information, see the Integration with Aries Blueprint chapter of the Red Hat JBoss BRMS 6.4 Admnistration and Configuration Guide.
- Error messages while uploading spreadsheet as multi-bytes name have been improved. Asset names in error messages are now in a human-readable format and are easy to troubleshoot.
Chapter 2. Known Issues
These are the known issues for Red Hat JBoss BRMS 6.4:
- [GPS] (6.4.z)Ability to specify priority for Asynchronous Tasks [RHBPMS-4778]
-
6.4 Update 6 introduces a small change into the database schema. You must apply the
bpms-6.4-to-7.0.sql
script to your database before you run Red Hat JBoss BPM Suite or Red Hat JBoss BRMS 6.4.6. This script is located in theupgrade-scripts/<database-type>
directory, available from the Red Hat JBOSS BPM Suite 6.4 Update 6 and the Red Hat JBOSS BRMS 6.4 Update 6 zip files which you can download from the Red Hat Customer Portal. - When all next moves are not doable, optaplanner get stuck in step and if termination is not based on time, it cycles forever [RHBRMS-1726]
-
If the Business Resource Planner is in a state where all the entities are immovable, it gets stuck and only time based termination can terminate it. To workaround this issue, call the
Solver.terminateEarly()
method to break the cycle. - Use of "contains" operator does not add values from enumeration with quotes in Guided Rules etc. [RHBRMS-2577]
- When using enumeration for a field in guided rules, guided decision tables, or guided decision templates, the resulting rule does not contain the selected value from the enumeration drop down within quotes ("") resulting in validation errors. There is currently no workaround for this issue.
- Backward-incompatible change in ModifyCommand [RHBRMS-2703]
-
The JAXB marshalled form of
org.drools.core.command.runtime.rule.ModifyCommand
has changed and is backward incompatible. If you are creating an XML for marshalled command manually, you need to modify the attributes annotated by JAXB for marshalling in the XML. For more information, see the Migrating from 6.X to 6.4 section of the Red Hat JBoss BPM Suite 6.4 Migration Guide. - Managed KIE Servers do not work with latest Red Hat JBoss EAP security patch for Jackson [RHBPMS-5192]
When using Red Hat JBoss EAP 6.4.20 with Red Hat JBoss BRMS 6.4.10, enabling the Realtime Decision Server by uncommenting the block of system properties in
standalone.xml
results in Jackson deserialization failures, and the Realtime Decision Server fails to deploy in Business Central. This is caused by a Jackson fix introduced in the Red Hat JBoss EAP 6.4.20 patch. For more information, see the JBoss Enterprise Application Platform 6.4 Update 20 Release Notes.To protect Red Hat JBoss EAP 6.4.20 from Jackson databind deserialization vulnerabilities, you must start the server with the following system properties:
-Djackson.deserialization.whitelist.packages=
Using an empty string allows all classes for serialization. This setting is insecure and not recommended in production.
-Djackson.deserialization.whitelist.packages=org.kie,org.drools,other.custom.package
For a secure configuration, add all of the packages in a comma separated list to the property which needs to be serialized. The
org.kie
andorg.drools
packages are mandatory.
Chapter 3. Fixed Issues
These are the high priority issues fixed in version 6.4 of Red Hat JBoss BRMS, sorted by components.
3.1. User Interface
Table 3.1. Business Central Issues Resolved in Version 6.4
Issue | Description |
---|---|
Compilation of spreadsheet fails with specific condition. | |
Rules validation in business-central is very slow. | |
Allow users to edit project’s GAV information in business central Project Editor when it has a parent. | |
Guided Rule Templates: Generates incorrect DRL when literal constraint follows templated constraints. | |
missing filesystem unlock on Exception in JGitFileSystemProvider.commit(). | |
Errors in Phreak under heavy and multi threaded load. | |
[6.4.0][Guided Decision Table] xls can not be validated. |
3.2. Core
Table 3.2. BRE and Core Issues Resolved in Version 6.4
Issue | Description |
---|---|
LHS NullPointerException at PhreakJoinNode.updateChildLeftTuple. | |
Support for custom HTTP headers in Decision Server java client configuration. | |
Drools Timer initiate with milesecond truncated. | |
Rules compilation failure depending on condition ordering. | |
DialectUtil.normalizeRuleName() doesn’t normalize multibyte rule names. | |
Multibyte bind variable name fails with java dialect. | |
Memory leak in KieScanner. | |
Unwanted firing modifying an event over a window:time. | |
InternalFactHandle.isValid returns false but still evaluated when audit log is enabled. |
Chapter 4. Enhancements and Feature Requests
These are the customer-reported enhancements and feature requests implemented in version 6.4 of Red Hat JBoss BRMS.
Table 4.1. Red Hat JBoss BRMS Enhancements and Feature Requests Implemented in Version 6.4
Issue | Description |
---|---|
KieContainer.newKieSession((String) null) should return the default ksession to be consistent with getKieSessionModel(null). | |
Guided Decision Table Editor: Add support for caching enumeration lookups. | |
MemoryUtil should not fail on Google App Engine with NoClassDefFoundError. | |
(6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment. | |
Support for custom HTTP headers in Decision Server java client configuration. | |
Allow users to edit project’s GAV information in business central Project Editor when it has a parent. | |
XStream marshaller can’t be configured with NameCoder. |
Appendix A. Versioning information
Documentation last updated on: Monday, May 13, 2019.