I am happy to announce the official launch of the camunda BPM incubation space with the first large community contribution by plexiti. View it on github: https://github.com/camunda/camunda-bpm-incubation https://github.com/camunda/camunda-bpm-fluent-testing The goal of the camunda BPM incubation space is to promote the development of interesting new projects and ideas around BPM, BPMN and process engines. Due to the productization and stabilization focus in the camunda BPM core platform, we decided to separate out these experimental projects from the core platform.
I am happy to announce the release of camunda bpm platform 7.0.0-alpha2. This is the first camunda BPM release that contains a distribution for Glassfish Application Server. You can now download a complete open source BPM platform with fully compliant Java EE 6 integration! Download it now! Highlights: Glassfish 3.x Distribution with Java EE 6 process engine integration New Job Executor Service with JCA 1.6 Integration Job Executor manageability through JMX New space for documentation: http://docs.
After launching our open source platform camunda BPM on 18th March, we gave it a proper welcoming to the BPM community last week. 55 people showed up to the launch party held at camunda HQ, which coincided with our 5th birthday. It was a great night, during which the hard-working team around camunda BPM had the chance to demonstrate some of the platform's great features and advantages followed by good discussions with the guests afterwards.
Process management is not a bureaucratic evil but can be a key instrument for scalable business models. But to do so we need to get rid of our old ways of thinking. Need an example? The whole Zero Code BPM – Illusion, is one of many errors that have dominated process management in the past. On 18th March we released our BPM platform under an open source license as Business Process Management is impossible without IT (not everyone likes this, but it’s just the way it is).
Scott Francis has written an excellent post about the core message of our presentation at bpmNEXT. He called it the "Zero Code Hypothesis". Though Scott's summary is completely right in its essentials, I would like to put some details straight: We don't think that "Zero Code BPM" does not work at all - Zero Coding and our approach are both reasonable, depending on what you have and what you need.
Yesterday we released version 2.0.12 of our modeler with a number of bug fixes as well as layout and usability improvements. One highlight is splitting layouted sequence flows to insert new flow elements between two connected nodes. Other things worth noting include Improved integration of the model wizard Proper support for event subprocess / non-interrupting start event Diagram image generation handles spaces in diagram file names correctly Event Subprocess Wizard integration We also fixed some crucial bugs, reworked the layouting of participants and the resize behavior of pools, lanes and subprocesses.
bpmNEXT has definetely been a Home Run, as Bruce Silver puts it. Bruce has impressively succeeded in creating a real think tank event for BPM thought leaders sharing their ideas, visions and quite a lot of crazy new stuff around BPM. For those of you who do not know him: Bruce Silver is the BPMN Guru in the US, and I really admire him for both his competence and all that he has done for the standard.
Along with the launch of our open-source BPM platform we made the camunda modeler available to the public, both as a software and as source code. With the camunda modeler, you get at free modeling tool that integrates in your Eclipse IDE and focuses on seamless modeling of process and collaboration diagrams. But see yourself: We invite you to try out the modeler, give us feedback and contribute to it. Present, past and Future The camunda modeler is based on the Eclipse BPMN 2.
The camunda bpm stacks currently includes three web apps: cycle, cockpit, tasklist. All of them are rewrites from a JSF 2.0 ancestor version and with this post I want to explain the decision to built them on a HTML5 plus REST architecture and not with <insert java web framework here>. Its clear that the web itself is based on the client-server principle. Many Web frameworks like JSF, Vaadin etc. implement it like this:
camunda BPM comes with a fresh REST API based on JAX-RS. Its goal is to expose the process engine services as broadly as possible. That means we aim to enable you to interact with process engine services via REST with similar expressiveness as in plain Java. With 7.0.0-alpha1, we provide methods such as task querying that already realize our desired degree of detail (similar for process definitions and instances). For future releases, we plan to broaden the scope to reach the afore-mentioned goal.