Today we are happy to announce the new release of the camunda Modeler. This version adds official support for Eclipse Kepler. On top of that it ships with the ability to change the type of tasks, events and gateways as well as a simplified connection of elements.
Eclipse Kepler Support
Kepler support is finally there. Head over to the downloads site and get a fresh version of the modeler, ready for Kepler.
Morphing áka Changing Flow Node Types
Morphing flow nodes to different types is something we are pretty exited about because it makes it a lot easier to change existing process models. Thanks to Roman, this feature is now available via the actions menu as two small gears for tasks, events and gateways.
Changing the flow node type performs a semantic check on the model and makes sure that invalid outgoing flows (according to the BPMN 2.0 specification) are removed. You may undo the operation via CTRL-Z if it has unexpected implications on your model.
Easier Connection of Elements
We simplified the connection of objects via the actions menu. In the new version of the Modeler the tool will automatically choose the correct connection type based on the rules defined in BPMN 2.0. That also means that some invalid connections may no longer be drawn. Bear with us, it is all for the sake of better BPMN 2.0 models.
Property Panel Improvements
Some other notable changes to the properties panel include (thanks to Kristin and Roman):
- targetNamespace editable
- compensation task editable
- message names editable
- async throwing message event editable
- datastores and data objects may be maintained
- loop for activities can be set
- call activity property validation added
BPMN 2.0 Compatibility
To help mitigating common modeling errors we added further checks to the Modeler for flow and flow node addition, as well as reconnection of flows. These reduce the likelihood that invalid BPMN 2.0 is the result of a modeling session.
Check out the all closed issues for a complete list of changes.
Behind the Scenes
Michael has done a great job on improving our Jubula QA. The others in the team are already working on features for the next modeler version. Expect something exciting!