Chapter 3. Known issues

Task operations using JMS currently do not correctly look up the groups the user is part of. As a result, a user might not be allowed to perform operations on tasks if those operations require the user to be part of a specific group (like for example claiming a group task). As a workaround, the remote REST API should be used instead.

A task which defines reassignment to another user and is stored in jBPM5 cannot be loaded in jBPM6. The attempt to load it will fail with error: org.postgresql.util.PSQLException: Bad value for type long : deadline.

The only known workaround at this point in time is to provide additional configuration files inside the META-INF directory, next to persistence.xml with the following content:

<?xml version="1.0"?><!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <typedef name="materialized_clob" class="org.hibernate.type.TextType" /> </hibernate-mapping>

This instructs Hibernate to use TextType for materialized clubs.

When using the IE10 browser, the tree of simulation results does not handle a click event. Only general simulation results are seen and the detailed ones are not available. There is no known workaround at this point in time.

Nested nodes (inside a embedded subprocess or swimlane) use coordinates relative to the top left corner of its parent (instead of the top left corner of the canvas). As a result, if you import this process in Eclipse BPMN2 Modeler, it will fail to correctly locate these nodes.

A known issue with caching causes a newly created Process to have the name of a previously created Process rather than the one that is assigned to it. This issue only occurs in IE10 and can be worked around by clearing the browser cache before creating a new process.