Tuesday, April 15, 2014
First, import the camunda-bom in the dependencyManagement section of your maven pom:
Now you can reference multiple camunda dependencies without adding their <version> information:
What's more: we also give you the versions for the the required dependencies of camunda engine. This way you will always get the version of mybatis, joda-time, java-uuid-generator that the current version of camunda-bpm was built and tested with:
Note that most of our maven artifacts are pushed to maven central.
Saturday, April 5, 2014
The source code of the tutorial can be found on github. Since the guide is a step-by-step tutorial, you can checkout the source code for each step as a tag in git.
I hope you like the tutorial, please give us feedback in the forums and via @camundaBPM.
Read the guide on how to get started with camunda BPM and Java EE.
Friday, April 4, 2014
The camunda BPM team is pleased to announce the release of camunda Modeler 2.5.0. This release is dedicated to align the latest improvements of camunda BPM 7.1 with the modelers properties panel. Furthermore we implemented a new properties tab for extension elements and of course we fixed bugs.
Monday, March 31, 2014
- Improved process engine with Job Definitions, better BPMN coverage and improved performance,
- All-new BPMN Model API for convenient BPMN model access,
- New features in the cockpit monitoring web application,
- Improved Tasklist and Task Forms, including support for HTML5 and Generated Task Forms.
- Support for Oracle WebLogic Server 12c and JBoss Application Server 7.2 and JBoss EAP 6.1 / 6.2
Tuesday, March 18, 2014
On March 14 we merged the online community BPM-Netzwerk.de with more than 10,000 members into the new camunda BPM network.
I personally created the first version of this community in 2004, and together with Robert Emsbach grew the community in the German speaking area. I learned a lot about community building during that time, especially in the BPM world.
Now camunda takes over and will bring our network to the next level: Firstly, we want to grow our community outside the German speaking area as well, and secondly we want to explore new possibilities for discussing BPM online, that should go beyond the typical instruments we already know from general virtual communities. That's why we created the BPMN forum for discussing BPMN diarams online.
This video provides a short introduction: http://vimeo.com/89381906
It would be great if people should like this new way of discussing BPM(N) online (right now the first reactions look pretty promising), and I would like to express my gratitude to Robert for the great time we had with BPM-Netzwerk.de. He is a BPM enthusiast just like me, but way more important, he is a very good friend.
Monday, March 17, 2014
BPMN 2.0 defines events and tasks catching messages. The following is a fragment of a process waiting for an order to be cancelled:
|Intermediate Message Catch Event|
<bpmn2:message id="Message_1" name="orderCancelled"/>
<bpmn2:process id="Process_1" isExecutable="false">
<bpmn2:intermediateCatchEvent id="IntermediateCatchEvent_2" name="Order
New Fluent API
.setVariable("CANCEL_TIMESTAMP", new Date())
The fluent DSL makes it easy to define a complex correlation set based on different restrictions. The above example correlates the message on the business key. On top of that, correlation based on process variables and process instance id is supported:
The API also makes it easy to provide the message payload as a single or multiple variables through setVariable(varName, value).
More Efficient than Query + TriggerWe recommend using the fluent DSL or the RuntimeService.correlateMessage(...) methods introduced in 7.0 over the Query + Trigger pattern. Using the Query + Trigger pattern you first query for an execution having a message event subscription and then trigger that execution:
Not as efficient:
Execution e = runtimeService.createExecutionQuery()
Map<String, Object> variables = new HashMap<String, Object>();
variables.put("CANCEL_TIMESTAMP", new Date());
runtimeService.messageEventReceived("orderCancelled", e.getId(), variables);
The Query + Trigger pattern has two disadvantages:
- More lines of code :)
- Two process engine commands instead of a single one. This makes it less efficient in terms of performance.
Thursday, March 13, 2014
The plugin was accepted by the Grails community and was published in their plugin repository:
The code is pushed to github: https://github.com/plexiti/camunda-grails-plugincamunda Grails Plugin 0.1.0 released: http://t.co/cy539EHEUV— Grails Plugins (@grailsplugins) March 13, 2014