Closed saig0 closed 1 year ago
I would recommend backporting the proposed PR to 7.17
, 7.18
, and 7.19
. The PR is strictly additive and not influencing the existing DMN support and behavior (e.g. the version of DMN models created via Model API). This will allow us to support executing DMN 1.4 and 1.5 models in those versions as well without much effort.
To reviewer I backported the changes as-is to the maintenance branches. No adjustments were necessary, they are plain cherry-picks from the main branch.
User Story (Required on creation)
As a developer, I want to be able to execute models compliant with the new DMN 1.5 standard, i.e. a model using the DMN 1.5 namespaces will be recognized as a DMN file and validated using the DMN 1.5 XML Schemas. It can be executed if it uses only the DMN features that we have implemented so far.
Functional Requirements (Required before implementation)
Technical Requirements (Required before implementation)
Limitations of Scope
This does not require the implementation of all changes that DMN 1.5 introduced over DMN 1.4.
Hints
Links
Breakdown
Dev2QA handover