Search this Blog

Search this Blog


Follow our Blog by Email

Thursday, October 1, 2015

Camunda 7.4.0-Alpha2 released

Today we release Camunda BPM 7.4.0-Alpha2. This is the second alpha release previewing the upcoming 7.4.0 Release.

The highlights of this release are:
  • Improved DMN Engine
    • Hit Policies
    • Data Types
  • New Cockpit Features,
    • Auditing of DMN Decisions,
    • BPMN Heat Map,
  • Improved BPMN Engine
    • Support for BPMN Escalation
    • Improved Asynchronous Execution Efficiency
    • SLF4j Logging
    • Faster Deployments
  • Improved CMMN Engine
    • Add Support for Repetition Rule
  • Support for Tomcat 8
  • New Documenation
  • Many Bugfixes

Overall more than 170 issues were closed. See complete Release Notes in Jira.

Thursday, September 24, 2015

Impressions from Camunda Community Day 2015

Or in other words: Our most awesome community day yet!

Last week our annual Camunda Community Day took place. I always enjoy that day very much because it gives me the opportunity to get in touch with community contributors and users. I always learn a lot during these days and I take a lot of engergy away from it.

Same as last year, the Community Day took place here at the Camunda office in exactly the same space in which we normally sit behind our desks and write code.

We had to limit reservations to 100 (including ourselves). Two things struck me with this: when we announced the date in Camunda Network, it was almost instantly sold out, and almost everybody who reserved a seat also showed up. Nastasja tells me that out of 100 reservations only about 10 people did not attend (which is amazing for an event where reservation and attendance is is free) :)

Friday, September 11, 2015

Scaling Camunda BPM in a Cluster: Job Executors and Coordination

Throughout development of Camunda 7.4, one of our focus points is job executor features and improvements. The job executor is the process engine's component to perform deferred actions, such as executing an intermediate timer event or an asynchronous continuation. Thus it is central in the Camunda architecture and central for scaling the BPM platform in a cluster. In this post we provide insight in job executor behavior and how job executor instances be coordinated by employing a backoff strategy that is part of the upcoming Camunad 7.4.0-alpha2 release.

Tuesday, September 1, 2015

BPMN Quest - Camunda as a Game Engine!

This year at the annual Camunda hackdays one team bravely took it upon themselves to balance out the innovative and useful projects with something fun and frivolous. For two days somewhere in Brandenburg we were "Awesome-Team-Awesome" and we turned the Camunda engine into a platform to create a D&D style quest game. We call it BPMN Quest.

If you can't wait for it - here you can play it right away.

Start page for bpmn quest.

Context Help in Camunda using SOLR Search Server

Last week we had our anual hack days - that means 48 hours of producing something aswesome. Together with Falko, Ingo and Thorben we build a context help within the Camunda BPM Workbench protoype. This uses Apache SOLR to index various sources (we did the user forum, the docs on Github, a Community Extension and internal best practices). We discussed details on this index and did a comparison to ElasticSearch.

It was a great study for options and use cases of such a help in our tool chain - but watch the result yourself:

Monday, August 31, 2015

Process Test Coverage Report

As part of the Hack Days this year my colleague Falko migrated an existing tool we (Camunda Consulting) used with success in a lot of projects to The Process Test Coverage Report Generator. It just hooks into an automated test (typically JUnit) and creates an HTML report showing the coverage:

  • For every Test Case
  • For the whole Test Suite
See this example for one test case - obviously the Happy Path of the process model:

The report can easily be watched locally within your IDE or hooked into your Jenkins Build. See GitHub Readme for details. 

By the way - our Best Practice is to go for "Flow Node Coverage" - so your Test Suite should "visit" each BPMN Flow Node (Events, Activities, Gateways, ...) at least once.

Happy Testing!

Wednesday, August 19, 2015

How to repeat a task in CMMN?

We have some good news: We implemented the repetition rule in our CMMN engine. This gives the users the ability to repeat a task under certain conditions.

We invite you to try it out!
For testing purposes use the current 7.4.0-SNAPSHOT of the engine and repeat a CMMN task as often as you wish.

There also exists some documentation with an explanation how the repetition rule works and how you can use it. Just read the section about repetition rule.

Every feedback is welcome.
If you miss something or something does not work as expected please let us know.

PS: We are currently refactoring the documentation. So apologize if there is something in the documentation that does not work as usually. We are working on it.