While Dashboard Filter's auto-refresh feature was enabled, errors would occur whenever auto-refresh was started, stopped, or edited. An unexpected error would display even if the user did not interact with the application. This issue has been resolved and no more exception errors are thrown for the auto-refresh feature.

When a project with different versions was deployed multiple times the process definition list only showed one version of the process definition. This caused an issue deploying different versions of a project. This issue has now been fixed.

A process with a FreeMarker form (*.FTL) didn't save its data on clicking the save button. Instead, an error message would be generated in the log files with the message "User '[UserImpl:'***']' was unable to execution operation 'Start' on task id 4 due to a no 'current status' match". This issue has now been fixed.

The two options available for loading property files in the LDAPUserGroupCallbackIml were not functional and buggy.

The files were not loaded when their location was specified by a system property and neither were they loaded when they were dropped under business-central.war/WEB-INF/classes folder. The only workaround was to add the property files directly in the org.jbpm module.

This has now been fixed by allowing any valid URL to specify location of the UserGroupCallback property file. In addition to URL protocols (file, http, etc) you can now use classpath. If no protocol is available (no valid URL) the classpath based location is assumed. From classpath the system will try to load first from local class loader (class that requires the reading) and if not found fall back to thread context class loader.

A NullPointerException was displayed to the user when a query was made via a REST command for a WorkItem that didn't exist. Instead of informing the user that the WorkItem didn't exist anymore, the exception was displayed.

This has now been fixed by displaying a user friendly message on execution of such a query: 'RestOperationException thrown with message 'WorkItem 1 does not exist.'

Uploading a file via Authoring → Artifact Repository in Business Central resulted in a “Uploaded Successfully” message, but no file was actually uploaded. The workaround was to restart BPMS. However, in the latest version of BPMS, this issue has been fixed.

Process changes were not being reflected when a project was re-deployed with the same GAV (Group, Artifact and Version) and the same BPMN version. The only known workaround was to change any of the GAV for that project.

This issue has now been fixed by ensuring that on undeploy of runtime manager the releaseId of the project was removed from the local KIE repo. The repo used to keep a local cache of deployed artifacts and this was causing the older version of the project to be used on runtime.

Sending an object as a parameter to the execute task for a REST service resulted in a SerializationException error. This error only occurred when calling the complete method of TaskService. If CompleteTaskCommand was used and the execute method of KieSession was invoked with this command as a parameter there was no error and the task status was changed to completed. This applied to both REST and JMS. This issue has now been fixed.

REST operations that retrieved Task instances would fail when forced to use the JSON format (ACCEPT header). There was a server side error thrown when the server instance tried to convert the (JAXB) Task instance to JSON. The workaround for this issue was to use XML instead of JSON (by setting it in the ACCEPT header).

This issue has now been fixed in the latest version of the product and the workaround is no longer required.

Requesting a list of current deployments using the REST API while a deploy or undeploy request is pending caused a race condition terminating in a NullPointerException. This issue has now been fixed by modifying the code to prevent the race condition from happening.

Trying to copy a rule in Business Central caused errors if the new rule name contained spaces. A workaround was to give the new rule a name without spaces while copying and then once the copy was done successfully, to rename it with spaces. This issue has now been fixed in the latest release and copy operations complete successfully with spaces in the name.

It was not possible to register Custom Work Item Handlers via Business Central, even though it was possible to add them via Business Central. This has now been fixed by using reflection to register the work item beans.

Task operations using JMS did not correctly look up the groups the user was a part of. As a result, a user would not be allowed to perform operations on tasks if those operations required the user to be part of a specific group (for example, claiming a group task). This has been resolved by extending the UserGroupCallback mechanism in human-tasks for JMS call support.

The system used to throw an IllegalArgumentException when a kjar with missing dependencies was uploaded. This message was not very clear about the actual error and it was often misleading. The system now informs the user with a more helpful error message when a kjar with missing dependencies is uploaded.

While running Business Central through JBoss EWS 2.0, users would still receive task information even after a process instance was aborted. This was caused by a missing TransactionSynchronizationRegistry in tomcat configuration. This has been resolved by adding the TransactionSynchronizationRegistry into the context.xml file.

A REST service task added to a process would cause errors on deployment with a ClassCastException error with an assignemnt set for the URL property. The error was caused due to incorrect typing of DataInputSet properties for the URL like ConnectTimeout and ReadTimeout. This issue has now been fixed.

Using the REST API, it was not possible to execute any queries that had the status of InProgress. The server would return a BAD_REQUEST flag in response to the query with a message saying that the status “Inprogress is not a valid status type for a task”. This issue was caused due to the lack of a method that didn't transform the string input to the correct corresponding value of enum and has now been fixed by the addition of this method.

While registering a work-item handler through a ksession and work-item manager, users would sometimes experience a method fail with a NullPointerException. This error occurred with the drools.session.conf and the CustomWorkItemHandlers in the home directory. The configuration files were poorly loaded which caused the error. This issue has been resolved by ensuring that class path resources will only override values from the home directory when such values exist.

The Process Designer was unable to open processes containing user tasks that had been written externally if they contained missing data types. While trying to open such processes, an exception was thrown and nothing was displayed. The runtime for BPMS could execute these processes, but the Process Designer GUI had trouble displaying them. In addition, a process that contained "." in process variable names also caused issues when they were displayed in the Process Designer.

Both these issues have now been fixed with this release.