Skip to main content

BPMN2 Modeler - New & Noteworthy

Version 0.2.3 (More) Bug Fixes and New Example(February 15, 2013)

What's new in this version:
  • A new screencast tutorial has been added to the project, which demonstrates how to implement the <customTask> extension point. The source code for this tutorial is available here, in the "examples" directory of the Git repository.
  • All extension attributes and elements must be enabled explicitly if you want them to appear in Property Sheets. This is done using the <modelEnablement> extension point. Previously any attributes or elements defined with the <modelExtension> extension point were automatically enabled.
  • General cleanup of some unused classes in the jBPM5 Target Runtime plugin. The missing Task decorator icons (for, e.g. Business Rule Task, Script Task, etc.) have been restored.
  • The handling of Messages and Message Flows attached to Participant Bands in Choreography Activities has been cleaned up. Previously it was possible to remove the Message Flow, leaving an unattached Message envelope shape. Also, a button pad (context menu) item for removing the Message has been added; this works just like pressing the "Delete" key, but the new button pad is complementary to its "Add Message" button.
  • A Class Cast exception thrown when trying to create a "New jBPM Process" in a project's sub-folder has been fixed.
  • Operation selection and creation for Service Tasks has been fixed.
  • The Schema Selection dialog has been fixed so that it correctly finds and imports Java classes.
  • The "Undo" menu descriptions after creating Tasks have been changed to read simply "Create Task" instead of displaying a verbose description of what the created Task does.
  • A bug in the file importer that caused Pools with Process references to corrupt the file, has been fixed.
  • Resizing a shape now causes the attached connections to be re-routed, the same way as moving the shape.
  • The Manhattan connection router has been improved a bit so that connections do not cross over the shapes to which they are attached.
  • The Interfaces table column label has been fixed to read "Implementation" instead of "E Class".

Back to the top