-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
With DMN 1.1 some elements and attributes change. So which element and attribute is displayed in the dmn-io UI has to be adopted. See
Changes:
- InputClauses don't have a name attribute and instead we use the label attribute for the name of a column
- We drop ItemDefinitions. Instead of AllowedValues we now use InputValues and OutputValues of Input/OutputClauses
- The type of a input column is defined by the type of the input expression
- The type of a output column is defined by the OutputClause.typeRef
- We don't use the camunda:output extension for the output mapping anymore instead we
use the name attribute of the OutputClause - A Decision Table has no name anymore, but we can set a name on the decision
New Things:
- The Definitions element now has the attributes exporter and exporterVersion. Maybe we want to use them and put something meaningful in.
Other:
- I think we should set the namespace attribute of the Definitions element to http://camunda.org/schema/1.0/dmn instead of http://camunda.org/dmn as this is our actual namespace
This is the controller panel for Smart Panels app
[CAM-4860] Adopt DMN 1.1 in dmn-io table UI
Labels | New: DMN-11 |
Rank | New: Ranked higher |
Description |
Original:
With DMN 1.1 some elements and attributes change. So which element and attribute is displayed in the dmn-io UI has to be adopted. See !dmn-io-dmn11.png|thumbnail! Changes: - InputClauses don't have a name attribute and instead we use the label attribute for the name of a column - We drop ItemDefinitions. Instead of AllowedValues we now use InputValues and OutputValues of Input/OutputClauses - The type of a input column is defined by the type of the input expression - The type of a output column is defined by the OutputClause.typeRef - We don't use the camunda:output extension for the output mapping anymore instead we use the name attribute of the OutputClause |
New:
With DMN 1.1 some elements and attributes change. So which element and attribute is displayed in the dmn-io UI has to be adopted. See !dmn-io-dmn11.png|thumbnail! Changes: - InputClauses don't have a name attribute and instead we use the label attribute for the name of a column - We drop ItemDefinitions. Instead of AllowedValues we now use InputValues and OutputValues of Input/OutputClauses - The type of a input column is defined by the type of the input expression - The type of a output column is defined by the OutputClause.typeRef - We don't use the camunda:output extension for the output mapping anymore instead we use the name attribute of the OutputClause - A Decision Table has no name anymore, but we can set a name on the decision |
Description |
Original:
With DMN 1.1 some elements and attributes change. So which element and attribute is displayed in the dmn-io UI has to be adopted. See !dmn-io-dmn11.png|thumbnail! Changes: - InputClauses don't have a name attribute and instead we use the label attribute for the name of a column - We drop ItemDefinitions. Instead of AllowedValues we now use InputValues and OutputValues of Input/OutputClauses - The type of a input column is defined by the type of the input expression - The type of a output column is defined by the OutputClause.typeRef - We don't use the camunda:output extension for the output mapping anymore instead we use the name attribute of the OutputClause - A Decision Table has no name anymore, but we can set a name on the decision |
New:
With DMN 1.1 some elements and attributes change. So which element and attribute is displayed in the dmn-io UI has to be adopted. See !dmn-io-dmn11.png|thumbnail! Changes: - InputClauses don't have a name attribute and instead we use the label attribute for the name of a column - We drop ItemDefinitions. Instead of AllowedValues we now use InputValues and OutputValues of Input/OutputClauses - The type of a input column is defined by the type of the input expression - The type of a output column is defined by the OutputClause.typeRef - We don't use the camunda:output extension for the output mapping anymore instead we use the name attribute of the OutputClause - A Decision Table has no name anymore, but we can set a name on the decision New Things: - The Definitions element now has the attributes {{exporter}} and {{exporterVersion}}. Maybe we want to use them and put something meaningful in. |
Description |
Original:
With DMN 1.1 some elements and attributes change. So which element and attribute is displayed in the dmn-io UI has to be adopted. See !dmn-io-dmn11.png|thumbnail! Changes: - InputClauses don't have a name attribute and instead we use the label attribute for the name of a column - We drop ItemDefinitions. Instead of AllowedValues we now use InputValues and OutputValues of Input/OutputClauses - The type of a input column is defined by the type of the input expression - The type of a output column is defined by the OutputClause.typeRef - We don't use the camunda:output extension for the output mapping anymore instead we use the name attribute of the OutputClause - A Decision Table has no name anymore, but we can set a name on the decision New Things: - The Definitions element now has the attributes {{exporter}} and {{exporterVersion}}. Maybe we want to use them and put something meaningful in. |
New:
With DMN 1.1 some elements and attributes change. So which element and attribute is displayed in the dmn-io UI has to be adopted. See !dmn-io-dmn11.png|thumbnail! Changes: - InputClauses don't have a name attribute and instead we use the label attribute for the name of a column - We drop ItemDefinitions. Instead of AllowedValues we now use InputValues and OutputValues of Input/OutputClauses - The type of a input column is defined by the type of the input expression - The type of a output column is defined by the OutputClause.typeRef - We don't use the camunda:output extension for the output mapping anymore instead we use the name attribute of the OutputClause - A Decision Table has no name anymore, but we can set a name on the decision New Things: - The Definitions element now has the attributes {{exporter}} and {{exporterVersion}}. Maybe we want to use them and put something meaningful in. Other: - I think we should set the {{namespace}} attribute of the {{Definitions}} element to {{http://camunda.org/schema/1.0/dmn}} instead of {{http://camunda.org/dmn}} as this is our actual namespace |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Assignee | Original: Sebastian Stamm [ sebastian.stamm ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Remaining Estimate | New: 0 minutes [ 0 ] | |
Original Estimate | New: 0 minutes [ 0 ] |
https://github.com/dmn-io/dmn-js/commit/707af981ceb8bf7ecf0d730de16bbcf85f390134
https://github.com/dmn-io/dmn-js/commit/76aa3199091b23ac86b831b73306437c1d2fbf3c
https://github.com/dmn-io/dmn-js/commit/be8f841a0eb2dfea89267793182294d8a3e80c41