5.2.0 Release Notes

The use of single escape characters for strings has been deprecated. In previous versions of BRMS it was possible to use single escape characters in strings, this behavior was maintained in previous 5.x versions for backwards compatibility, however it is necessary to use double escape characters in BRMS 5.2 as this is no longer supported.

When viewing the BRMS web console in Japanese, if a date is changed the change can be lost. To workaround this issue set the following properties in preference.properties: drools.defaultlanguage=ja drools.defaultcountry=JP.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

Under certain circumstances the BRMS user interface can display HTML tags in error messages.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

Building expressions for 'from' does not work when using generic types with collections. The workaround is to define a system property drools.dialect.mvel.strict=false".

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

When a new declarative model has been created there are limitations on which facts can be added as fields to other facts. The limitation is based on the order of creation of the facts.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

In the BRMS web interface, if a rule uses a global variable that hasn't been imported into the package an error message should be displayed, however, a bug in the code prevents the error message from displaying.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

Importing a Microsoft Excel spreadsheet into in a Knowledge Base will cause the StringIndexOutOfBoundsException exception to be thrown if the spreadsheet was created in Excel 95 or earlier. This is because of an issue in the JXL library which is used to handle these files. This can be worked around by opening and saving the spreadsheet in Microsoft Excel 97 or greater or with OpenOffice.org Calc.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

When using JAAS authentication and no credentials are supplied, ModeShape's Repository.login(...) methods result in a session that does not contain the proper user ID.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

If a global asset is removed from a test scenario and the user tries to access the asset in the expect section a Javascript error occurs.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

When trying to view the source of a declarative model the view source button is missing.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

Translation errors in the Constants_ja_JP.properties file were located.

This behavior persists in JBoss Enterprise BRMS 5.2.0. and will be resolved in a future release.

When a jackrabbit repository with an asset shared between a package and the global area was imported an exception was thrown preventing the operation from completing.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

A bug prevented users with analyst permissions from viewing source, validate, verify, or change states on assets.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Changing the data-type of a column in the guided decision table did not always recreate the column correctly. This left the table in an inoperable state.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

The slf4j-log4j12.jar, which is required for persistence when using IBM's JDK, was not present, this was resulting in the ClassNotFoundException being thrown.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

A bug prevented the proper calculation of expiration offsets, resulting in the Drools MBeans being presented to the JMX console with no expiration. Type declarations (and expiration policies) from different packages have been merged to correct the expiration offset bug, and the correct expiration offset is now calculated.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Classes with two fields that used advanced enumeration failed in test scenarios. An overloaded method was created to handle advanced enumerations and prevent test scenarios from failing.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

SLF4j jar files were incorrectly packaged in jboss-brms.war and caused initialization errors. These jars have been removed and the problem no longer persists.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When writing rules in the BRMS user interface it was not possible to define sub facts with statements that use multiple field constraints.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When creating web decision tables it was possible to add a duplicate attribute or metadata column, however, once the duplicate column had been added it was not possible to remove it. It is no longer possible to add duplicate attribute or metadata columns when creating web decision tables.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Decision table configuration was not being parsed to the overloaded KnowledgeBuilderImpl.add method resulting in a NullPointerException. This bug has been resolved and the NullPointerException is no longer thrown.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

IBM WebSphere Application Server returned a '404 page not found' error message when users attempted to access http://localhost:8080/jboss-brms/. The Drools component has been upgraded to 5.2 and the bug no longer presents.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

A NullPointerException was occurring in AbstractCompositeRestriction when using unbound variables as a side effect of missing import statements.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Users with analyst permissions could not open assets even when they had been assigned category permission that granted access to the category the asset belonged to. This was fixed by allowing analysts to have package wide access via SuggestionCompletionEngine explicitly, ensuring they can open the assets.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

A bug presented where it was not possible to delete a row from template data when multiple rows had been added. The Drools component has been upgraded to 5.2 and the error no longer presents.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

The fact type navigator was incorrectly displaying multiple icons in Internet Explorer 8. This has been resolved so that only the appropriate icons are displayed.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Using dependent enumerations in the same DSL sentence was triggering the java.lang.IndexOutOfBoundException exception. An overloaded method was created to handle dependent enumerations in the same DSL sentence, and this exception no longer occurs.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

The dialog box displayed in Fire Fox 5 to users attempting to add conditions to a rule was too small and presented usability issues. The dimensions of the dialog box has been adjusted to provide more space for entering new conditions.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When adding a DSL sentence in the guided editor enumerations are selected from a dropdown box, however, when the editor refreshed after certain actions the selected enumerations changed to different values.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

A KnowledgeAgent set up to monitor a .drl file would correctly monitor the file for changes unless a change to the file introduced an error, at which point the knowledgeAgent would no longer monitor the resource for changes.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When adding test scenarios to a 'Given' fact with a field value of type string, the literal values added were not always displayed correctly in the guided editor.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

After inserting multiple facts into the given section of a test scenario the input fields were missing. The Drools component has been upgraded to 5.2 and the error no longer presents.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When using the advanced view of the BRMS web user interface if the user declared a fact and attempted to switch back to the basic view, the following error message was displayed, "There are errors in this view. Can not switch to guided mode until the errors are resolved". The error message has been updated to provide more information and now reads, "Defining declared types in this view is not allowed. Please remove all declared types from the view."

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When using Java Enums in a fact model the Guided Editor showed a combo box with the correct values however, the values were parsed as strings and didn't work as expected. This has been resolves and the values are being parsed as expected.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

It was not possible to bind variables in facts or in fields inside statements like "Any of the following are true" with the guided editor. Upgrading the drools component to 5.2 has resolved this issue.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

A NullPointerException is thrown and prevents the PetStorExample from running when the openJDK runtime environment is being used.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Multiple versions of the same class were present in the Maven Bulk Importer JAR. The additional instances of the classes have been removed.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

The signed standalone version of BRMS was failing to start due to a security exception in brms.war, the RoleBasePermissionResolver.class was moved to the org.drools.guvnor.client.security.permission package which resolved the issue.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Adding or changing values for an enumeration in the guided editor would cause all the other fields in the editor to reload. To reduce unnecessary reloading and make the presentation of the editor clearer, the rule being edited is now presented as plain text and the editing controls are only shown when the text is clicked on.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When importing a repository from an XML file with Modeshape, the ConstraintViolationException exception was thrown. Upgrading the version of ModeShape resolved this issue.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When using the conditional 'or' element in the left handside of rules with a return value restriction the NullPointerException exception was thrown.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When searching for assets by the 'date created' or 'last modified' attributes, the search results were based on 12:00 PM (midday) instead of 12:00 AM (midnight), this offset the results by 12 hours excluding some results that should have been included, and including some results that should not have been included. The search results now take 12:00 AM as the boundary between days, and the appropriate search results are returned.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Rule attributes declared at the package level with Guvnor were being ignored by the knowledgeAgent.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

After creating a rule with the Guided Editor with the 'Or' conditional operator and adding a fact type it was not possible to delete the fact type.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When running test scenarios in BRMS it was not possible to turn off RuleFlow. An "Activate rule flow group" option has been added making it possible to specify which ruleflow-groups should be activated when running test scenarios.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

The WebDAV servlet was preventing the correct export and import of global assets between environments.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When input streams were opened by the isPackage() method in the org.drools.commons.jci.compilers.EclipseJavaCompiler class some input streams were not being closed.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When multiple categories existed for assets, and the user tried to view assets by category if the list extended beyond the available space, it was not possible to scroll down to view the complete list. A scroll bar has been added and users can now view the complete list.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

Translation errors in the Constants_ja_JP.properties file were discovered.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.

When viewing events logs in the BRMS user interface the message text did not wrap, this caused a horizontal scroll bar to appear which was awkward to work with. The event log page has been redesigned so that the text wraps and the messages are easier to read.

This issue was resolved in JBoss Enterprise BRMS 5.2.0.