extension

In the highly heterogeneous and dynamic landscape of pharma research, where hundreds of researchers and scientists must communicate and undertake deeply complex workflow processes – Camunda has proved the ideal tonic. At CamundaCon Daniel Butnaru, Solution Architect at Roche Pharma, will share how his team utilizes Camunda’s Community Edition straight out of the box to streamline the interaction between researcher (human) tasks with backends and robotics platforms.

The hackdays produced a lot of interesting projects and this is part two of those projects. If you want to catch up on all the fun. you can find part one here. We’ve a dichotomy of project types in this post, ranging from those made for fun to those actually helping productivity. The line is slightly blurred on some of them depending on if you consider reading logs fun or not. Personally I find no better way to relax than curling up on a couch and reading through one of my favorite stack traces. Even if we can predictably assume that in the end the NPE did it. Fun & Games! The hackdays have often produced endearing games like 2015’s...

Each year the coding inclined residents of Camunda towers embark on a 3-day adventure into a realm of big ideas and hacky solutions. Its starts months before when a list of potential project ideas is created. Then as the hackdays approach people find ideas that they like and teams form until the day of reckoning arrives and we all gather together to see if we can realize the lofty ambition of creating a working prototype over the course of about 60 hours. We had some unifying themes these this year and I’m going to write each post on the projects that are (sometimes loosely) related to that theme. In this post I’ll discuss projects that help users get started with...

A Theme of their own Plain Components – The behavioral UI Library Zeebe Benchmark Experiments (aka Spreadsheet-Driven Development) Zakka – distributed fault tolerant workflow engine on Akka Use Node-RED Zeebe nodes for Camunda keyfob detection GitHub Plugin(s) for BPMN Diagrams Optimize Drilldown Nexus and Minio object storage / Camundobot!

Camunda in its current version is perfectly suited to run BPM in cloud infrastructures. From Spring Boot integration to the External Task Pattern and other features you have a lot of freedom to design your BPM architecture the way you want. Is anything missing? Hardly. Except one thing: Identity management in the cloud often differs from classical approaches. Neither the integrated Identity Management nor the optional LDAP Identity Provider fit. That’s why we have been looking for a way to better integrate Camunda’s Identity Management into such environments.

I’m happy to announce the new version 1.3.0 of the Camunda BPM Custom Batch extension. This extension provides a simple way to use the camunda batch functionality for your own purposes and split huge workloads into small asynchronous jobs. If you are interested in how the extension is working, and how customers use it, take a look at the presentation slides from CamundaCon 2018. So what happened since version 1.0.0? Here is a summary of exclusive and prioritized batch jobs.

Camunda BPM Migration is a framework for making process instance migration easier. It builds upon the migration functionality introduced in Camunda BPM 7.5. This is a great feature enabling the community to go boldly where few men have gone before 😉 Typically, instance migration is avoided like the pest. It’s a pain. This feature, together with the migration extension, aims to ease that pain. What Does the Migration Extension Offer? Before answering that, let’s have a look what Camunda already provides. As you know, Camunda BPM provides the ability to do a migration based on process definition mapping. Still, the migration plans can only be defined for deployed processes. This makes it hard to impossible to define a migration plan...

I’m happy to announce the first release of the new community extension FEEL-Scala. FEEL is a part of the DMN specification of the OMG and stands for “Friendly Enough Expression Language”. It provides a simple data model and a syntax designed for a wide audience. The new community extension implements a large feature set of FEEL and replaces the default FEEL engine of the Camunda DMN engine.