Support DMN Level 3 conformance level

[nikku]

This is an umbrella issue to track DMN Level 3 modeling support.

What should we do?

Allow users to model advanced constructs defined in DMN Level 3 as supported by the new Camunda DMN engine (DMN Scala):

• [ ] https://github.com/bpmn-io/dmn-js/issues/372
• [x] https://github.com/bpmn-io/dmn-js/issues/704
• [ ] ...

Why should we do it?

Without being able to model these constructs DMN Level 3 engine features remain a non-feature for many users.

[CatalinaMoisuc]

@barmac looked into this a while ago, see: https://gist.github.com/barmac/59d934737587e0248a65b5436bcf8e3d.

[nikku]

We received another validation that this is worth looking into, some day.

[nikku]

@barmac Maybe worth summarizing your findings here.

[barmac]

I spiked on boxed expressions broad support, and discovered that it would require major architectural changes in order to be implemented. It is possible but would get us busy for more than a month. However, the architecture of the library could be simplified as we could use only three packages:

• dmn-js (manager, entry point)
• dmn-js-drd (DRD viewer and modeler)
• dmn-js-boxed-expression (name TBD; viewer and modeler for decision and BKM logic)

Thus, we'd get rid of dmn-js-shared, and merge literal expression and decision table in a single, general library.

More info is in private repo: https://github.com/bpmn-io/internal-docs/issues/778#issuecomment-1623513755

[nikku]

@barmac Let's move this back to backlog? I think we want to decide when to pick it up in an orderly manner.

[barmac]

Yes, it's not on the roadmap at the moment.

[dschulten]

More info is in private repo: https://github.com/bpmn-io/internal-docs/issues/778#issuecomment-1623513755

The private repo apparently no longer exists.

[barmac]

You can check out the spike result at https://github.com/bpmn-io/dmn-js-boxed-expression