Today we relased a new version of the camunda Modeler. It provides better property editing support for BPMN 2.0 and camunda BPM properties, improvements in pool and lane handling and fixes a number of important bugs.
Finally, we switched from activiti to camunda as the default namespace prefix for engine attributes.
Property Editing SupportKristin and Roman extended the property panel to achieve partity with new engine extensions and features introduced in camunda BPM 7.0:
- On throwing message events and send tasks service task engine extensions may be edited
- On call activities passing the business key as well as all variables may be edited
- On call activities the called element binding and version may be specified
- On start events the form key may be edited independent of the event definition
In addition, documentation may now be maintained for all BPMN 2.0 elements.
To enhance the modeling experience I worked on an improved pool and lane handling
- Pools and lanes may not be shrinked below their children bounds
- Bendpoints are properly update upon pool or lane resize
- Sufficient space is added on the diagram when adding a new pool
BPMN 2.0 Compatibility
Daniel, Roman and I improved the interoperability of the modeler by fixing a number of diagram import and export related bugs:
- No more xsi:type=“xsd:anyType" is added to extension elements on export
- Documentation is exported correctly without reordering
- Data object references are supported on import and are correctly created by the modeler
- Diagrams containing invalid DI references to data objects are automatically fixed during import
Check out the release notes for a complete list of changes.
Behind the Scenes
Christian and Roman integrated the modeler tests into our continuous integration. As a result the ~500 modeler tests run now continuously and no test covered feature will accidently be broken again.
What is lying ahead of us? For the next modeler release we look into Eclipse Kepler support and more modeling improvements.