Implementing DMN 1.6

Development
1

There is a new DMN Standard, 1.6, currently in beta: About the Decision Model and Notation Specification Version 1.6 beta

Currently we are still in the stabilization phase, but I think it would be sensible to talk about this already, because this is one of the reasons why we forked the engine in the first place - maintain it and keep it up to current standards.

I wanted to start this discussion with several questions and topics to discuss:

  1. When would be the appropriate time to tackle this? I think we should stick to our plan and not introduce new features before releasing our stable 1.0, do you agree? In this limits, I think standard-updates should have a high priority on the roadmap.
  2. How do we handle Tooling? We are currently depending on the Camunda Modeler for all modelling tasks. While it should be possible to introduce new bpmn.io versions into the web apps, which will then bring DMN 1.6 support, I doubt that Camunda will Patch DMN 1.6 support into the Camunda 7 DMN moddle libraries and the modeler. We need to either find a way to adapt this tooling ourselves, or create new tooling
  3. Cooperation with other tool vendors, especially OpenBPM should be initiated early on. We are still planning to roll our own web apps, but if we decided to implement new BPMN / DMN standards, we should do what is possibile for us to make sure that tooling in the ecosystem supports it, too.

Again, I don’t think it is reasonable to start development on this now, as our resources are better spent with the stabilization efforts, but I wanted to bring awareness to the upcoming standard update and the implications for ous

1 Like
2

Agreed, it is important to keep up with these essential standards. And yes, I do think it should be out of scope for 1.0. We should have feature parity with C7 7.24, not more.

For employing DMN 1.6 we need the proper resources to implement and especially to test them. Fortunately we have with @steven someone who could help testing that DMN features are working on a real-life usage.

For me, upgrading to that DMN level is something I could imagine for a version 1.1 or 1.2. Does someone now for when we could expect the final version of the standard? I would like to see a commitment for that on the roadmap. It would be a clear sign that Operaton is not staying where C7 ends, but really moves forward and has a vision for it.

1 Like