-
Type:
Feature Request
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: None
User Story (Required on creation):
Boxed contexts are a more business-friendly way of defining contexts in a DMN model.
Resources:
- 10.2.1.4 Boxed Context of the DMN 1.3 specification
- 10.5.1 Context metamodel for the metamodel
- https://github.com/dmn-tck/tck/blob/master/TestCases/compliance-level-3/0040-singlenestedcontext/0040-singlenestedcontext.dmn for an XML example
- https://github.com/camunda-community-hub/dmn-scala/blob/1.6.1/dmn-engine/src/test/scala/org/camunda/dmn/ContextTest.scala for tests in the DMN Scala engine
Functional Requirements (Required before implementation):
- Boxed contexts are supported for execution, i.e.
- Boxed contexts without a result can be used to provide a context as an input for another decision
- Boxed contexts with a result are evaluated correctly and the result value can be used as input for another decision
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
- to be decided: Which elements do we support as context entry values (only expressions or also decision tables? is there more?)
Hints (Optional):
- Based on https://github.com/camunda-community-hub/dmn-scala/blob/1.6.1/dmn-engine/src/test/scala/org/camunda/dmn/ContextTest.scala, it looks like the Scala DMN engine at least has some support for this. In that sense, it makes sense to evaluate what is left after https://jira.camunda.com/browse/CAM-12910 has been implemented.