JBoss Enterprise BRMS Platform 5 5.3.

1 Release Notes

JBoss Enterprise BRMS Platform 5

5.3.1 Release Notes
Important information related to the JBoss Enterprise BRMS Platform 5.3.1 product release

Legal Notice

Legal Notice
Copyright 2012 Red Hat, Inc. T he text of and illustrations in this document are licensed by Red Hat under a Creative Commons AttributionShare 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, JBoss, MetaMatrix, 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 T orvalds 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. All other trademarks are the property of their respective owners.

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

Abstract
T hese release notes contain important information related to the JBoss Enterprise BRMS Platform product. Known problems, additional resources, and other current issues are addressed here.

Table of Contents

Table of Contents
1. Overview 2. Frequently Asked Questions 3. New Features 4. Experimental and Deprecated Features 4.1. Experimental Features 4.2. Deprecated Features 4.3. T echnical Preview 5. Security 6. Known Issues 7. Resolved Issues A. Revision History

1. Overview
JBoss Enterprise BRMS Platform is a business rules management system for the management, storage, creation, modification, and deployment of business rules and business processes. Web-based user interfaces and plug-ins for JBoss Developer Studio provide users with different roles the environment suited to their needs. JBoss Enterprise BRMS provides specialized environments for business analysts, rules experts, developers, and rule administrators. T he JBoss Enterprise BRMS Platform 5.3.1 release introduces support for Java Development Kit version 7. In addition to being able to deploy JBoss Enterprise BRMS Platform 5.3.1 to JBoss Enterprise Application Platform 5, JBoss Enterprise SOA 5, JBoss Enterprise Web Server 1, support has been added for JBoss Enterprise Application Platform 6 and JBoss Web Server 2. T his release also includes numerous bug fixes and improvements to previous releases. T he JBoss Enterprise BRMS Platform 5.3.1 release is initially for the deployable packages. T he deployable packages allow users to deploy JBoss Enterprise BRMS Platform 5.3.1 to an existing application server, please refer to the BRMS Getting Started Guide for further details. T he standalone package, which comes with JBoss Enterprise BRMS Platform 5.3.1 and will be based on JBoss Enterprise Application Platform 5.2, will be available at a later date when JBoss Enterprise Application Platform 5.2 becomes available. Supported configurations or JBoss Enterprise BRMS Platform 5.3.1 are listed on access.redhat.com. T he components that have been integrated into JBoss Enterprise BRMS Platform 5.3.1 are list on access.redhat.com.

2. Frequently Asked Questions

Q: A: Can I use a different repository than the default? JBoss Enterprise BRMS Platform 5.3.1 has a pluggable repository mechanism allowing any JCR compliant repository to be used. Apache Jackrabbit is still the default repository. ModeShape has been included as a technical preview in BRMS 5.3.0, installation and configuration instructions have been included in the BRMS Administrator Guide at

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

http://docs.redhat.com/docs/enUS/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_Administrator_Guide. Q: A: Where is the documentation? T he JBoss Enterprise BRMS Platform documentation is available for online reading and download at https://access.redhat.com/knowledge/docs/JBoss_Enterprise_BRMS_Platform/. T he JBoss Enterprise BRMS Platform API documentation is also available for download from the Red Hat Customer Portal at https://access.redhat.com. It contains the full API reference in standard JavaDoc HT ML format. Q: A: What application and database servers is this product supported on? Refer to https://access.redhat.com/knowledge/articles/119933 for a complete list of the application and database servers that the JBoss Enterprise BRMS Platform is supported on. T he default configuration uses an embedded Derby database. T his configuration is included only for evaluation, testing and demonstration purposes. It is not supported configuration for a production environment. Q: A: Where can I find out more details about my support contract? Details of support policies are located at the following URLs: Support Processes http://www.redhat.com/support/process/ Production Support Scope of Coverage http://www.redhat.com/support/policy/soc/production Production Support Service Level Agreement http://www.redhat.com/support/policy/sla/production/ Developer Support Scope of Coverage http://www.redhat.com/support/policy/soc/developer/ Developer Support Service Level Agreement http://www.redhat.com/support/policy/sla/developer/ Product Update and Support Policy by Product http://www.redhat.com/security/updates/jboss_notes/ JBoss End User License Agreement http://www.redhat.com/licenses/jboss_eula.html

Table of Contents

Q: A:

Where are the installation instructions? Complete installation instructions can be found in the BRMS Getting Started Guide at https://access.redhat.com/knowledge/docs/enUS/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_Getting_Started_Guide/index.html. What issues might I encounter when migrating to this release? Read Section 6, Known Issues to learn about the differences between this release of JBoss Enterprise BRMS Platform and previous releases that may cause difficulties when moving your applications to this version. As a matter of best practice, Red Hat recommends that you test all of your existing applications on this new version of the JBoss Enterprise BRMS Platform before deploying it in your production environment.

Q: A:

3. New Features
Java Development Kit 7 JBoss Enterprise BRMS Platform 5.3.1 introduces support for Java Development Kit 7; however, when deploying JBoss Enterprise BRMS Platform 5.3.1, JBoss Enterprise Application Platform 5 does not include support for the IBM JDK7. Deploy to JBoss Enterprise Application Platform 6 JBoss Enterprise BRMS Platform 5.3.1 introduces support for JBoss Enterprise Application Platform 6. Deploy to JBoss Web Server 2 JBoss Enterprise BRMS Platform 5.3.1 introduces support for JBoss Web Server 2.

4. Experimental and Deprecated Features

4 .1. Experimental Features T he following features are included in this release of the JBoss Enterprise BRMS Platform 5.3.1 as experimental features and are not supported by Red Hat. Experimental Features T raits T raits is an experimental feature that is included with JBoss Enterprise BRMS Platform 5.3.1. jPDL migration tool T he jPDL migration tool in the process designer is an experimental feature. T he BRMS Business Process Management guide provides the steps to enable this experimental feature. Rule T emplates

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

Rule templates are an experimental feature and are not supported by Red Hat.

4 .2. Deprecated Features T he following issues relate to behavior that has been deprecated in the JBoss Enterprise BRMS Platform. Deprecated Behavior Ruleflow file format T he .rf ruleflow file format has been deprecated and will be removed from future versions of JBoss BRMS. Using # in comments Using the '#' character for single line comments has been deprecated. Users should use '//' for single line comments.

4 .3. T echnical Preview Modeshape is a Java Content Repository (JCR) that is included in JBoss BRMS 5.3.1 as a technical preview, see the BRMS Administration Guide for further details.

5. Security
T he JBoss Enterprise BRMS 5.3.1 deployable release resolves one known security flaw: CVE-2012-2379 Apache CXF does not verify that elements were signed / encrypted by a particular Supporting T oken. A flaw was found in the way Apache CXF verifies that XML elements were signed or encrypted by a particular Supporting T oken. CXF checks to ensure these elements are signed or encrypted by a Supporting T oken, but not whether the correct token is used. A remote attacker could use this flaw to transmit confidential information without the appropriate security, and potentially to circumvent access controls on web services exposed via CXF. T his flaw is resolved in the JBoss Enterprise BRMS 5.3.1 deployable release via a component upgrade. T he JBoss Enterprise BRMS 5.3.1 standalone release will inherit additional security fixes from JBoss Enterprise Application Platform 5.2.0 when it is released.

6. Known Issues
T he following issues are known to exist in JBoss Enterprise BRMS Platform 5.3.1 and will be fixed in a subsequent release. BRE (Expert, Fusion) BZ#724616 - Encrypted passwords in the change-set.xml T he drools client API accesses JBoss Enterprise BRMS with credentials declared as plain-text in a change-set.xml file or property files. A request has been made to develop a mechanism to obfuscate the password.

Table of Contents

BZ#755129 - PackageBuilder fails with StackOverflowError if declared model contains recursive data types PackageBuilder fails with the StackOverflowError if the declared model contains recursive data types. BZ#814669 - camel cannot find type converters when deployed on jboss Camel cannot find type converters for String to InputStream conversions when deployed on JBoss, preventing commands being sent in JAXB, JSON or XStream.

BRM (Guvnor) BZ#724638 - Is not possible set facts sub-fields in T est Scenarios It is currently not possible to define a sub-field for facts in test scenarios. For example, "address.city". BZ#724795 - JCR session doesn't contain the current user when ModeShape is used When using JAAS authentication with ModeShape and no credentials are supplied, ModeShape's Repository.login(...) methods result in a session that does not contain the proper user ID. BZ#758199 - Asset Editors: Saving one tab refreshes the others to the default state When using multiple assets editors in different tabs, saving one asset editor refreshes all the asset editors and any unsaved work in the other asset editors is lost. BZ#806887 - Open assets by URL only works at the second attempt T he URL to open an asset must be entered into the browser twice before it will successfully open. T he first attempt to open the asset results in the main search page of the JBoss Enterprise BRMS user interface being opened, the second attempt results in the asset being correctly opened.

jBPM 5 BZ#757185 - Parser doesn't support 'Unspecified' and 'Mixed' gateway directions. An IllegalArgumentException exception is thrown by the parser when 'Unspecified' or 'Mixed' gateway directions are used in process definition files. T his is because types of gateways are not currently supported. BZ#804989 - Designer doesn't allow sequence flow from boundary compensation event T he jBPM runtime, and by extension the Process Designer, do not support sequence flow from boundary compensation events. BZ#807187 - Adhoc subprocess does not complete after triggering end event node inside Ad-hoc sub-processes with non-terminating end event nodes do not end and the processes

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

stays active. BZ#807640 - Conditional sequence flow is not supported by jBPM engine In the BPMN 2.0 specification, conditional flow can be used without gateways. T he JBoss Enterprise BRMS Process Designer supports this feature; however, knowledge bases will not build when processes include conditional flow in the process definition without using gateways. BZ#808070 - Ad-hoc subprocess: the completion condition is limited only to: getActivityInstanceAttribute("numberOfActiveInstances") == 0 When using ad-hoc sub-processes the completion condition is limited only to: getActivityInstanceAttribute("numberOfActiveInstances") == 0, when the number of active instances differs, the ad-hoc subprocess does not end. BZ#811965 - No support for Global Area Business processes created in the Global Area do not have their name, ID, or package set. When processes created in the Global Area are imported into a package the package is set; however, the name and ID are not. T he workaround is to set the name and ID value manually. BZ#812006 - jBPM5 does not handle timer definitions conforming to ISO-8601 T he BPMN 2.0 specification requires that timeCycle and timeDuration conforms to the ISO-8601 for time interval representations; however, jBPM5 is currently using it's own legacy format for expressing timer duration and cycle. BZ#814700 - JBPM engine does not support converging OR gateway Converging OR gateways are not supported in JBoss BRMS 5.3.1. BZ#852114 - Boundary Events on Reusable Subprocess not possible in jBPM Designer When setting boundary events on reusable subprocesses in the process designer caused a validation occurred stating that there was no incoming connections. In JBoss Enterprise BRMS 5.3.1, it is no longer possible to set boundary events on reusable subprocesses. BZ#852231 - BRMS AsyncWSHumanT askHandler port conflicts with JON port configuration T he AsyncWSHumanT askHandler handler was configured by default to use port 5546. When JBoss Enterprise BRMS and JBoss Operations Network 3.1 were run on the same machine there was a conflict because JBoss Operations Network also uses port 5546. T his has been resolved by changing the default port for the AsyncWSHumanT askHandler handler to 5153. Both systems can now run on the same machine with no port conflicts. BZ#864063 - Initial process BPMN2 import fails in Designer (hangs) T he Process Designer was not loading extension elements correctly when first importing BPMN2 processes, causing the imported process not to fail. T his has been resolve and the extension elements are now loaded up front. T his results in the successful import of BPMN2 processes.

10

Table of Contents

T ooling (JBDS) BZ#867819 - deadline support for user task nodes (JBDS plugin) Previously, there was no support for deadlines and notifications in user task nodes when working with the JBoss Developer Studio plug-in, this prevented users from specifying deadlines or notifications. T his has been resolved and users can now specify deadlines and notifications.

User Interface BZ#724254 - Highlight "Save changes" button when any changes are made to assets in Guvnor - or prompt on close... When editing assets in the JBoss Enterprise BRMS user interface there is no visible feedback mechanism that reminds users to save their changes. T his can cause changes to be lost, and means users must be vigilant about saving changes. BZ#836897 - Section 508: A text equivalent for every non-text element shall be provided Previously, not every element in the JBoss Enterprise BRMS user interface had a text equivalent. T his meant the user interface was not compliant with Section 508, and could prevent users with screen readers from accessing the user interface. T his has been resolved by adding text equivalents for all non-text elements.

3rd Party BZ#851670 - Login into Business central blocked when using mod_jk load balancer When accessing business-central via Mod_jk load balancer, an exception occurs during Resteasy HttpServletDispatcher service() method and the login process is not completed. T he exception is raised in the Resteasy code when the request's content-type header is processed, because this header contains the wrong value. T his issue only presents when using Firefox 7 and above, and can be avoided by open the configuration panel of FireFox (In the address bar type about:config). Accepting the warning. Searching for network.http.accept-encoding, and changing the default value (gzip, deflate) to *;q=0.1,gzip,deflat.

7. Resolved Issues
T he following issues have been resolved in JBoss Enterprise BRMS Platform 5.3.1. BRE (Expert, Fusion) BZ#724294 - Issues with knowledge agent when using temporal constraints Using temporal constraints with the knowledge agent resulted in a java.lang.RuntimeException due to a missing domain on the class path. T his happened when the facts were imported as a jar file, and it has been resolved by making sure the evaluator registry is populated during package deserialization. BZ#724313 - [JBRULES-24 38] loading multiple sheets of single Excel book by one change-set xml

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

11

A changeset that imported multiple sheets from the same Excel file decision table, only included the rules from one sheet and silently ignored the rules in the other sheets. T his has been resolved and the rules from all sheets are now correctly imported. BZ#748711 - DRL parser expects a newline at the end of the file Including a comment on the last line of a DRL file, caused a no viable alternative error to occur and the parser to return a null package. T his has been resolved and the no viable alternative error no longer occurs. BZ#814415 - NullPointerException occurs when newInstance property is set to false for the KnowledgeAgentConfiguration When a rule with a sliding window and pending scheduled event expirations was removed from or replaced on the knowledge base, the engine was not properly cleaning the pending event expirations, and a NullPointerException was raised when the expiration was about to be executed. T he engine is now properly cleaning up pending expirations when the rule is removed or replaced, and no more exceptions are raised. BZ#833609 - JPAKnowledgeService sessions fail on CMT under other App Servers Running JBoss Enterprise BRMS Business Process Management in a CMT environment caused a NullPointerExpection on WebSphere, because it did not allow access to UserT ransaction, this made it impossible to run processes in the CMT environment. T his has been resolved by implementing a dedicated T ransactionManager to allow processes to run in the CMT environment. BZ#845843 - Bug with default properties in KnowledgeStoreServiceImpl T he default values for some properties of the KnowledgeSessionConfiguration overwrote the ones explicitly set by the user. As a result, the StatefulKnowledgeSession was created with the default configuration instead of the properties provided by the user. T o resolve this issue, the default values of the KnowledgeSessionConfiguration properties can no longer override the user provided values. T he StatefulKnowledgeSession is now created using the actual configuration defined by the user. BZ#851300 - A Declared bean's field's initialization expression is ignored if the type is primitive On asset copy, the taskName property was not carried over and the taskName property was missing from copied assets. T his has been resolved by ensuring all properties are correctly copied. BZ#851307 - Deadlock when using pseudo session clock A bug in lock acquisition between the PseudoClock and the Agenda was creating a deadlock, as a result, the engine would deadlock when running fireUntilHalt() in one thread and trying to advance the PseudoClock in a second thread. T his has been resolved by properly handling the locks between the agenda and the clock, and the deadlock is no longer created. BZ#851469 - Updating a fact causes NPE with extends When one rule extended another rule and both rules reference the same fact in their conditions,

12

Table of Contents

calling an update on that fact after calling fireAllRules caused a NullPointerException. T his has been resolved by checking that a rule is enabled before adding its activation to the agenda. T he NullPointerException no longer occurs in this situation. BZ#852881 - ClassCastException in RuleT erminalNode.retractLeftT uple() When using ruleflow group and lock-on-activate, a class exception could occur. T his issue has been resolved by adding a line of code that checks if the left tuple contains a Boolean due to lock-on-activate blocking activation creation. BZ#860698 - java.lang.VerifyError: JVMVRFY012 stack shape inconsistent When a declaration double dereferences within the Business Rules Engine, and the value of the method returned by the second dereferencing is a primitive type, the bytecode of the eval class using it is not correctly generated. A java.lang.VerifyError occurs when trying to instance a class from the incorrectly generated bytecode. T his has been resolved by fixing the bytecode generator to allow it to work even in these specific primitive dereferencing instances. It is now possible to have an eval class do a double dereferencing, which returns a primitive type without any malformed bytecodes. BZ#862325 - Fact modification improperly cancels activations An optimization engine bug occurred when the first rule to fire in a session modified a fact that had activations pending. Accordingly, rules that depended on the modified fact were no longer firing. T his has been resolved by removing the particular optimization for the engine that is no longer relevant to the new algorithms, and the rules now properly fire. BZ#869967 - Fact metadata declared in a POJO are lost when declaring fact metadata in DRL When a POJO had annotations both in the Java class and in the corresponding DRL declared type, only the annotations in the DRL were taken into account. As a result, annotations on the POJO were lost. T his has been resolved by merging annotations on both the POJO and the declared type. It is now possible to use annotations in both the POJO and the corresponding declared type.

BRM (Guvnor) BZ#724474 - Business Rule elements containing a fact that has been removed cannot be edited (in Guided editor) Previously, when a fact within the Business Rule element was removed, the rule could no longer be edited within the Guided Rule Editor. T he particular section of the Guided Rule Editor that used that fact type would freeze and prevent editing. T his has been resolved by allowing frozen sections to be deleted and recreated. BZ#724530 - Enable uploading custom accumulate functions as part of POJO model .jar file When using custom accumulate functions, the custom class had to be packaged as a Jar file and added to jboss-brms.war/WEB-INF/lib. It is now possible to include the class file for custom accumulate functions in the POJO model jar file and upload via the JBoss Enterprise BRMS user interface.

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

13

BZ#724633 - IE6/IE7 don't display facts to setup a new "working sets" Previously, when logged in to the JBoss Enterprise BRMS user interface with Internet Explorer 6 or 7 and attempting to edit a working set, the available fact types were not visible. T his has been resolved and the facts are now visible. BZ#724636 - [GUVNOR-1173] Hiding types list in technical rule editor by default A request was made to hide the type list in the technical rule editor by default. T his request was made to prevent non-technical users from inadvertently changing the type. T his request has been implemented and the type list is now hidden by default. BZ#724764 - Add URIEncoding attribute in BRMS-standalone EWP server.xml for multibyte characters WebDAV issue JBoss Enterprise BRMS supports any UT F-8 character as part of a rule name, but when using WebDAV access, the multibyte characters in the URL were decoded as ISO-8859-1 by default. T his has been resolved by adding URIEncoding support. BZ#745443 - T est Scenarios: Enumerations not working correctly Previously, the QA section of the JBoss Enterprise BRMS user interface did not support dependent enumerations, which resulted in users having to use a work around. Support for dependent enumerations has now been added for the QA section of the user interface and the workaround is no longer necessary. BZ#785748 - Attempting to copy an archived rule would not be visible in the respective package Attempting to copy an archived rule previously created a copy of the archived rule, however, the copy was also archived and did not show up in the package it was copied to. T his has been resolved by removing the ability to copy archived rules. BZ#816572 - Copy of package: value of T ask Name disappears in process BPMN2 Packages that were created by copying an existing package, did not include the taskName property, which resulted in validation failing. T his has been resolved by ensuring that all properties are correctly copied, and validation is able to proceed without failing. BZ#819475 - Importing "import java.util.T reeMap" to a package causes java.lang.NullPointerException at SuggestionCompletionEngineBuilder An error in the handling of generic type parameters caused a java.lang.NullPointerException to occur when building a SuggestionCompletionEngine due to an unhandled null generic parameter type. T his has been resolved by improving the handling of generic type parameters, and java.util.T reeMap can now be imported. BZ#839657 - BRM / Guvnor Does not allow you to open an incomplete BPMN2 process that was not validate before saving Previously, JBoss Enterprise BRMS verified business processes on save operations. T his prevented users from saving process models that were incomplete. T he issues has been resolved by adding support for saving partial process models. Users are now able to save

14

Table of Contents

incomplete process models. BZ#851093 - No listbox for enum fields declared in parent class (sub-class or delegated class) Enumerations that were defined for fields, either as Java enumerations or Guvnor enumerations, in super-classes or wrapped classes were not being detected, and their values were being displayed in a text box, when it should have appeared in a listbox of enumerated values. T his has been resolved by improving support for enumeration fields in super-classes and wrapped classes, and the values are now correctly displayed in a list box. BZ#851100 - RT E with Nested Classes, BRL and Java Some fully qualified inner class names were being incorrectly parsed and the import statements that were automatically generated for nest classes were incorrect. T his caused the completion of knowledge packages with the incorrect import statements to fail, and users had to manually alter the generated import statements. T his has been resolved by ensuring the fully qualified inner class names are correctly parsed. T he import statements generated for inner classes are now correct, and knowledge packages including import statements for inner classes now compile without the need for manually altering of the import statement. BZ#851103 - Existing POJO model w/ nested classes (A$B$C) causing error during build package Some fully qualified inner class names were being incorrectly parsed and the import statements that were automatically generated for nest classes were incorrect. T his caused the completion of knowledge packages with the incorrect import statements to fail, and users had to manually alter the generated import statements. T his has been resolved by ensuring the fully qualified inner class names are correctly parsed. T he import statements generated for inner classes are now correct, and knowledge packages including import statements for inner classes now compile without the need for manually altering of the import statement. BZ#851310 - Drools cannot resolve functions when argument is a fact type T he business rules engine could not resolve functions when a declared type was used as an argument for a function and resulted in compilation failure. T his has been resolved by loading the Java Class corresponding to the declared type when compiling the function. It is now possible to use a declared type as an argument for a function. BZ#852398 - Guided BRL editor: After refreshing a condition table with external data sources , enum select box disappears Within the Guided Business Rules Language Editor, errors occurred with enumeration select boxes disappearing. T his took place when the enumeration widget was defined with an external data-source. T he Label, that shows the current value, was not updating to show the value of the constraint when the remote call completed. T his in turn did not allow the selection of a value from the list. T his issue has been resolved by ensuring the enumeration widget redraws itself correctly when the asynchronous call to retrieve data completes. BZ#853496 - BPMN Editor Does not Show Service T ask for any further new Work Item Definition(s) if definition as corrupted If the configuration of one service task fails within the BPMN2 Editor, all other tasks appear to fail as well. T his causes service task interactions to become unusable within the designer. T his

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

15

has been fixed by evaluating each service node configuration independently while not affecting the evaluation of other service nodes. Users can still see service node definitions of all service nodes with a valid configuration. BZ#858167 - Guvnor: Business Rule - Modal alert, which requires halt the script, occurs when enumeration is defined in DSL Previous program logic error occurred when enumeration was defined for a DSL key; this issue caused Java Script prevention due to an infinite loop. Corrected program logic now allows enumeration values to be defined for DSL keys. BZ#860845 - Assets can not be restored when archiving "Global Area" It was previously not possible to restore assets from an archived global area. T his issued was caused because it should not have been possible to archive the global area, it should only have been possible to archive individual assets in the global. T his has been resolved by preventing users from archiving the global area. BZ#863508 - [guided editor] Adding 'From' element breaks the editor When adding a new 'from' widget to a rule within the Guided Rule Editor, incorrect program logic caused the 'from' widget to fail. Accordingly, the 'from' widget would disappear. Changes to the program logic have rectified the situation and the 'from' widget now functions as expected.

Examples BZ#852347 - SudokuExample throws IllegalArgumentException T he SudokuExample threw an IllegalArgumentException when the solve button was clicked, and the solution was never submitted. T he cause of the IllegalArgumentException has been fixed and the SudokuExample now works.

Internationalization BZ#841078 - Garbled chinese char in generated PNG image and form from jboss BRMS console of BRMS5.3 Images of business processes that were generated in PNG format, that used Chinese characters in the name, comment, and display name, were not rendering properly in the business central console and the Chinese characters were garbled. T his issue has been resolved and the Chinese characters appear correctly. BZ#859790 - Add JVM option -Dfile.encoding=UT F-8 for brms-standalone JBoss Enterprise BRMS 5 is internationalized with UT F-8 encoding; however, when running on a Java virtual machine if the JVM uses a different encoding system, unexpected errors could occur. T his has been resolved by adding "-Dfile.encoding=UT F-8" to the $JAVA_OPT S in run.conf and run.conf.bat to instruct the JVM to use UT F-8 encoding.

jBPM Console

16

Table of Contents

A bug in the Business Central console presented when the process overview was refreshed, which resulted in a large number of open file descriptors per process. T he number of files could quickly reach the maximum number of allowed open file descriptors per process. T he issue has been resolved by ensuring the open files are disposed of after the communication has closed. BZ#801093 - T imer start event does not emit start events repeatedly (in jBPM Console) Incorrect serialization caused lost timers, which meant start events with a cycle time defined only started the first time, and all subsequent starts were lost. T his has been resolved by fixing serialization so that timers are properly stored. Start events with a cycle time interval defined now work as expected. BZ#820309 - Overdue timers are not triggered on session initialization Previously, overdue timers fired before initialization was finished, which caused unexpected errors and resulted in execution failures. T o resolve this issue, a delay for overdue timers has been introduced. T he delay allows for complete initialization to occur before the overdue timers fire. T he delay is configurable with a system property (jbpm.overdue.timer.delay) that has a default value of 2 seconds. BZ#823855 - Accessing a finished process instance - Delete and Diagram behavior Accessing a completed process instance in the business central console, resulted in inconsistent information being displayed to the user. T his has been resolved by ensuring that when a completed process instances is accessed, the view is refreshed to include up to date information. BZ#848855 - T ransaction rollback failure after concurrent access: no transaction! Business process instances could not be accessed concurrently when Jboss Enterprise BRMS was clustered due to the persistence context not being cleared. T his prevented single process instances from being managed by JBoss Enterprise BRMS in a clustered environment. T o resolve this issue, the persistence context is now cleared on the transaction boundary level, and process instances can be managed in a clustered environment. BZ#851484 - JBPM-364 7 NullPointerException in jbpm-console when retrieving process definitions from guvnor A NullPointerException could occur when retrieving process definitions from the asset repository, which resulted in the process definitions not loading. T his has been resolved by ensuring the knowledge agent is null safe. T he process definitions are now loaded without throwing a NullPointerException. BZ#856946 - http://localhost:8080/business-central-server/ displays incorrect information. When users running JBoss Enterprise BRMS business central, visited http://localhost:8080/business-central-server/ the page displayed incomplete information. T he information has been updated and this is no longer an issue.

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

17

BZ#827418 - Saving a BPMN asset that has no end point creates a dead asset Previously, it was not possible to save process models that did not include an end node. T his prevented users from saving process models that were incomplete. T he issues has been resolved by adding support for saving partial process models. Users are now able to save incomplete process models. BZ#834673 - JBPM-3688: Human T ask dying issues In instances where an incorrect request was issued to the human task server, the incorrect request would result in a runtime exception that caused the human task server to die, which meant no more requests could be processed. T his has been resolved by ensuring the human task server is not affected by runtime exceptions, and the process requests continue in the human task server. BZ#834730 - Handling task deadlines in container causes T X errors Different application servers provide different forms of access to UserT ransaction when running in a non-managed thread. Usually UserT ransaction is accessible via JNDI but can be registered under different namespaces for different application servers. As a result of this, when there was no access to transaction instances a failure occurred. T o resolve this issue known JNDI namespaces were added (EAP5 and EAP6), and others can be defined by setting the system property jbpm.ut.jndi.lookup, ensuring that UserT ransaction can be accessed via JNDI. BZ#842547 - HornetQ based human task service doesn't listens on IPs, it listens only to localhost Previously, the HornetQ task server only listened to the localhost making it impossible to connect to a remote service. T his has been resolved by allowing configurable bind for host and IP for the the HornetQ task server. It is now possible to bind the HornetQ task server to a custom host and IP. BZ#843393 - Designer T ask Data Assignments and Commas When users added comma to the comment field of the user task in the Process Designer, the user task would not be parsed properly because there was no support for commas. T he Process Designer now includes support for commas. BZ#845680 - jBPM process designer fails to save swimlanes correctly A Business Process Management swimlane error would occur when a process model was generated with a swimlane positioned at the default position. T his would cause the swimlane to touch the modeling canvas border. Accordingly, the Process Designer would fail to create correct BPMN2 for swimlanes with borders outside or touching the modeling canvas border. T his has been resolved by altering the default swimlane position to not touch the modeling canvas borders. BZ#846486 - Can't save process diagrams if task names contain "&" An error occurred in which entering "&" within the names of tasks would not allow Process Designer to parse the process BPMN2. T his led to a validation error in which users were unable to save the processes. A fix of allowing "&" as part of the task names has rectified this issue.

18

Table of Contents

BZ#846487 - jBPM Designer corrupts diagrams with ambiguous gateways Ambiguously placed gateway nodes within a process diagram caused errors in which Process Designer was no longer able to reopen the diagram. T his issue caused a technical error in which the user was unable to open or edit the process model. T his has been resolved by showing validation errors with ambiguous gateway nodes and allowing Process Designer to open the invalid process. BZ#847044 - ClassNotFoundException: org.drools.event.BeforeRuleBaseLockedEvent when stopping EAP 6.0 Incorrectly disposing of the knowledge agent when shutting down the server caused an exception to be logged. T here was no impact to the application, however, the exception could cause confusion. T o resolve this issue, a listener definition was added to the business central server war, ensuring the correct disposal of the knowledge agent. T he exception no longer occurs. BZ#847381 - JBPM designer: ConditionT ype property on a sequence flow not saved Previously, it was possible for users to set a condition type on sequence flows in the Process Designer; however, the condition type was not stored on the process when the process was saved. T his has been resolved by removing the ability to set a condition type. BZ#851286 - JBPM-3371 T erminate end event in subprocess must not terminate parent process According to the BPMN2 specifications, a terminate node, when executed on a sub-process, should only terminate the execution in that sub-process; however, an error occurred in which the entire process instance would terminate. T his has been resolved by terminating only the sub-process and allowing the parent process to continue executing. BZ#851298 - JBPM-3626 Do not depend on hard coded variable name "processInstance" Previously, for intermediate conditional events to be able to a specific process instance's variables rules, the name of the variable had to be 'processInstance'. T his prevented users from using any name for variables in conditional event rules. T his issue has been resolved by checking the object type instead of relying on the hardcoded variable name. It is now possible to use any name for variables in conditional event rules. BZ#851489 - JBPM-3679 Problem with subprocesses embedded in multi-instance nodes Process instances were locking after sub-processes completed because the parent process was not updated by the sub-process. T his has been resolved by ensuring the parent process instance is also updated. Process instances are no longer locking and are able to continue. BZ#851495 - JBPM-3659 Variable resolution fails if two (or more) variables are in the same string A runtime exception was occurring when variables were present in a single string but were not separated by a space character. T he variables were not resolving and preventing the system from functioning normally. Support has been added to resolve multiple variables supplied in a single string and the runtime exception no longer occurs.

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

19

BZ#851503 - JBPM-34 54 Repeating intermediate timer events will only fire if the attached process completes successfully. In cases where an unexpected error in the process flow occurred, the started by timer was not rescheduled properly, instead it was reregistered which caused duplicate executions. T his was resolved by ensuring that timers are only registered once even when unexpected errors occur. BZ#852095 - Business rule task on entry action not triggering On entry scripts in rule tasks were not being triggered. T his has been resolved by ensuring the rule task now correctly triggers any on entry scripts, before activating the rule flow group. BZ#852111 - "Editor for Data Assignments" is currently not pulling in global variables. T he form and script editor in the Process Designer did not show users global variables available via auto-complete. T his has been resolved by adding support to show global variables via auto-complete. BZ#852112 - CancelActivity value is not saved on boundary event T he value stored in the cancelACtivity property was not stored on save operations in the Process Designer, and users setting cancelActivity property to true would cause it to revert back to the default false value. T his has been resolved in the Process Designer and users can now set cancelActivity property correctly and it will persist after save operations. BZ#852117 - Sorting in Shape Repository in jBPM Designer Element names within the Process Designer shape repository previously could not be sorted. T he ability to sort element names by alphabetical order was requested for usability purposes. T his has been resolved by allowing alphabetical sorting within the shape repository. BZ#852122 - Designer process with space in name creates invalid ID When creating a BPMN2 process within Process Designer, users who kept spaces in the process names would have these spaces pulled through into the process ID. T his would result in an invalid ID. T his issue has been resolved by removing spaces from the process asset name when creating the process ID. Accordingly, valid IDs are now created. BZ#852125 - can't save a process if use '<' or '>' in a sequence Flow's name A Process Designer error occurred when attempting to save a sequence with the '<' and '>' characters. While using these characters, users were unable to save the process they were working on. T his has been fixed by using html-escaping name properties. Users can now save these processes. BZ#852873 - Implementing Shared Entity Manager support and RESOURCE_LOCAL transaction A request for support of Shared Entity Manager and RESOURCE_LOCAL transaction for persistence was made for Business Process Management since default BRMS code did not support those features. T his has been resolved by allowing a shared entity manager on top of the already supported shared entity manager factory when using the Spring integration.

20

Table of Contents

BZ#852879 - HT Deadlines are not cancelled on task completion Human T ask deadlines were not cancelled when the task finished by means such as complete, skip, fail, or exit. T he actions related to the deadline would still trigger after task completion. T his has been resolved by cancelling task deadlines once the task is complete. BZ#853014 - Human task named queries are incompatible with hibernate 4 Various Human T ask queries were only compatible with Hibernate version 3 although both Hibernate 3 and 4 are supported. T his caused an issue with limited functionality with the Human T ask services; accordingly, errors such as Group T asks not appearing on the Group T ask panel in Business Central Console occurred. T hese compatibility issues have been resolved by enhancing functionality on both Hibernate 3 and Hibernate 4. BZ#853026 - JPAWorkingMemoryDBLogger can't access UserT ransaction on EAP6/JBoss AS 7.1.x Different application servers provide different forms of access to UserT ransaction when running in a non-managed thread. Usually UserT ransaction is accessible via JNDI but can be registered under different namespaces for different application servers. As a result of this, when there was no access to transaction instances a failure occurred. T o resolve this issue, known JNDI namespaces were added (EAP5 and EAP6) and others can be defined by setting the system property jbpm.ut.jndi.lookup, ensuring that UserT ransaction can be accessed via JNDI. BZ#854965 - Cannot retrieve Boolean variable from Human T ask when using generated task form An error occurred in the Business Central Console whenever parameters were transported as strings via HT T P protocol. T hey would not properly set as standard process variables such as Boolean, integer, float, and object. T his would result in errors such as not being able to retrieve variables from the Human T ask. T his has been resolved by ensuring data type awareness for standard process variables, and it has been integrated with Business Central Console. BZ#858120 - T he language "en-UK" is hardcoded in HumanT ask handlers User tasks were previously created with the hardcoded locale (en-UK), which prevent users from changing the locale. T his issue has been resolved by ensuring the user can configure the locale. In addition to this, it is now possible to configure the business central server to a specific locale. BZ#861898 - Process Instance Diagram in jBPM Console shows wrong multiple markers due to the ordering of JPAProcessInstanceDbLog.findNodeInstances() Due to the way different databases handle timestamps the log events could be returned out of order. T his resulted in incorrect markers on the diagrams in business central. T his issues has been resolved by ensuring that data (events) fetched from the database are ordered by ID, this ensures the correct order is returned and the markers on process diagrams are correct. BZ#862296 - IllegalArgumentException when opening Business Central Business Central was no longer able to be used when a process with a faulty script task was deployed after the fireAllRules method had been initialized. T his occurred because the

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

21

underlying knowledge session was not completely initialized as it was interrupted by the exception. T his has been fixed by ensuring the exception thrown on the session initialization does not break the initialization. T his result logs the session initialization exceptions on fireAllRules and continues with an unbroken session initialization. BZ#864165 - JPAWorkingMemoryDbLogger throws NullPointerException when used Spring + Resource_Local JPAWorkingMemoryDbLogger threw NullPointerException exception when used with Spring and Resource_Local. T his has been resolved by adding support for RESOURCE_LOCAL configuration when using Spring integration. BZ#864876 - Validation ignore task form when use space character in property "T ask name" A validation error occurred when task names contained the space character. Users would receive a false error regarding no task form being defined. T his has been fixed in Process Designer by omitting the false visual validation error and allowing task names to contain special space characters. BZ#864920 - Error message instead of Edit task form Window if use special character "&" in T ask Name Using the special & character in the taskName property value in the Process Designer caused task form errors to occur and users would see error messages instead of the task form editor. T his has been resolved and users can now see the task form editor correctly, even when the taskName property value contains the special & character. BZ#864972 - Editor task form for human task is empty when use space character in T ask Name Using a space character in the taskName property value in the Process Designer caused task form errors to occur and users would see error messages instead of the task form editor. T his has been resolved and users can now see the task form editor correctly, even when the taskName property value contains a space character. BZ#864977 - Send task does not contain property Operation which is required by BPMN2 T he Process Designer visual validation display incorrect error message for send tasks, this confused users about the state of the send task. T his has be resolved by ensuring the incorrect validation errors no longer occur. BZ#865458 - Generated task form validation functions need to be rewritten in order to use unicode characters It was not previously possible to us unicode characters in String fields in generated task forms due to incorrect validation errors occurring. T his has been resolved by adding support for utf-8 in the validation functions. User can enter utf-8 characters in task forms and do not see false validation errors. BZ#867188 - Designer validation fails when Reusable Subprocess refers to a different package

22

Table of Contents

A Process Designer validation error occurred when reusable sub-processes referred to a different package. T his issue would cause users to see a false error message regarding the process could not be found. T his has been fixed by stopping the false validation message from appearing. BZ#869012 - LocalT askService don't remove listeners Event listeners that were registered on Human T ask work item handler at initialization, were not removed on disposal of the handler and stayed active and receiving events. T his caused unexpected exceptions to be thrown when completing tasks after the knowledge session disposal. T his has been resolved by ensuring that event listeners are removed on handler disposal so that only active event listeners are receiving events from the human task server. BZ#871899 - Creation of getT asksByProcessInstanceIdStatus and getT asksByProcessInstanceIdStatusT askName as public API Previously, there were no public API methods available to get tasks based on the process instance ID. T his prevented users from accessing lists of tasks associated with any give process instance. T he API methods getT asksByProcessInstanceIdStatus and getT asksByProcessInstanceIdStatusT askName have been created and can be used to return tasks by process instance ID and task status, or by process instance ID, task name and task status. T his ensures tasks can be returned for a given process instance. BZ#872548 - Duplicated main agenda group on session reset When a rule or a process raises an exception the agenda is reset by marshaling the old one and unmarhaling it into a new one. T he unmarhaling process had a bug causing the duplication of the main agenda group in the resulting agenda. After the raising of an Exception and the subsequent reset of the agenda, the agenda itself was no longer usable. T his has been resolved, and now the agenda works correctly even after an exception is thrown by a rule or a process. BZ#874104 - Human-task queries for JPA2 seem to fail. Some human task queries were not updated to be aligned with both JPA1 (Hibernate3) and JPA2 (Hibernate4), as a result of this tests were failing and some of the functionality was not available with JPA2 (Hibernate4). T his has been resolved by ensuring all queries are aligned to work with both JPA1 and JPA2. Complete functionality is now available on both JPA1 and JPA2.

User Interface BZ#839923 - Dialog content exceeds dialog in firefox When users logged in to the JBoss Enterprise BRMS user interface with the Firefox web browser, the text in an error message dialogue box could overflow the dialogue box. T his has been resolved and text is now contained within the dialogue box. BZ#847052 - After closing one example application all other applications are closed as well. When closing an example application all other applications were closed as well, this was because every GUI example dialogue called System.exit() when it was disposed of. T his resulted in the user having to restart each example application if they wanted to look at another example. T he GUI example dialogues no longer calls System.ext(), but just disposes of their

JBoss Enterprise BRMS Platform 5 5.3.1 Release Notes

23

example. T he GUI example dialogues no longer calls System.ext(), but just disposes of their dialogue, and the user is able to look at other examples without restarting them.

3rd Party BZ#843284 - MVEL getBestCandidate() does not use argument position When there were overloaded methods with the same number and type of arguments but in different positions, mvel was sometimes unable to select the right one to be invoked. When using the mvel dialect the wrong method was invoked in the consequence. T he algorithm used by mvel to select the method to be invoked has been improved for overloaded methods. Now mvel is able to correctly discriminate which overloaded method has to be invoked.

24

Table of Contents

A. Revision History
Revision 5.3.1-16 Wed November 14 2012 L Carlon Release notes for the JBoss Enterprise BRMS Platform 5.3.1 release