Using the FEEL extension, it is also possible to write scripts in FEEL (Friendly Enough Expression Language) which is a part of the DMN specification.
Last Thursday, for our annual Community Day, we hosted our first user feedback session for Camunda Cockpit.
If you attended and even better joined the conversation and provided your feedback — thank you! We truly appreciated your input and are committed to base the future evolution of Cockpit on it.
Have you ever tried to create your own custom batch with Camunda BPM? Well, I did, and it was very time consuming and quite complex. There isn’t really a public API for this purpose. You have to work at the entity level and take care that batch configuration is saved to the ACT_GE_BYTEARRAY database table.
That’s why I’ve decided to create the Camunda BPM Custom Batch Extension.
The goal of this extension is to provide a simple way of using the Camunda Batch functionality for your own purposes.
If you have no clue what Camunda Batch is for, it can be used to split a huge workload (e.g., like reassigning all tasks) into small asynchronous jobs. See the official Camunda docs for more details: Camunda Batch
Next to minor changes, the new release adds support for consuming Camunda’s external tasks (introduced in Camunda 7.4.0) in the form of a Camel route endpoint. This is another level of technical decoupling and brings a lot of adventages.
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.
You are using Confluence? We as community members developed two plugins which allows you to use bpmn-js/dmn-js as full-featured modeling tool within your wiki for BPMN/DMN. Both are available on the on the Atlassian marketplace for free.
Since emails are a common form of communication, processes may also interact with them. For example an order process can start when a new order is received via email or an email is sent at the end which contains an invoice. The extension camunda-bpm-mail makes it easy to integrate emails in a process and interact with them.
We are happy to announce that the Camunda BPM Forum is moving to Discourse.
I want to start with a quote of myself (to give you a good impression on my ego ;-)):
When authoring rules in a more agile, business-friendly way, do not forget about testing them in a more agile, business-friendly way.
This post shows various approaches discussed on the roadshow.
Decision Model and Notation (DMN) is the new kid on the block when it comes to defining decisions and business rules. Like BPMN and CMMN, it tries to bridge the gap between human readable definition of business-relevant aspects and technical realization. DMN therefore has a graphical representation as well as an XML-based serialization format and Camunda provides you with a beautiful editor to manage both. So why not go full DMN any minute now? Probably because you work with business rule definitions for much longer than DMN is around and you manage them in Excel. Recreating these with the DMN editor is a tedious task. That is where Camunda’s newest community extension comes into play: The Excel worksheet to DMN converter.
I was delighted when Daniel asked me to valify (as Robert says) the Camunda BPM Team Blog
and make it fit our CI (nope, for once, this ain’t meaning Continuous Integration).
Here’s the little story about that work… erm… fun and some show-off about the new blog features.