-
Bug
-
Resolution: Done
-
Blocker
-
7.2.0.GA
-
13
-
CR1
-
-
-
-
-
-
CR2
An umbrella for the issues we're encountering with using DMN models authored with our editor. A lot of issues are being reported as comments on PRs or as separate JIRA. In reality, in preparation for our MVP we need to be confident all such issues are captured, fixed and re-tested.
- clones
-
DROOLS-3235 [DMN Designer] Runtime issues [7.2.0.Final]
- Closed
- incorporates
-
RHDM-788 DMN DRGElement typeRef to allow FEEL Any
- Closed
-
RHPAM-1672 [DMN Designer] Remove some properties from the Properties Panel
- Closed
-
RHPAM-1673 [DMN Designer] `inputData` and `variable` must have the same name value
- Closed
-
RHPAM-1674 [DMN Designer] Information Item name is empty by default
- Closed
-
RHPAM-1675 [DMN Editor] InformationItem's "Name" is always the same as the containing node
- Closed
-
RHPAM-1676 [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
- Closed
-
RHPAM-1677 [DMN Designer] QName: Default to be 'Any' not 'string'
- Closed
-
RHPAM-1678 [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue`
- Closed
-
RHPAM-1679 [DMN Designer] The `defaultOutputValue` and the `outputValue` are being persisted when the value is empty in the UI
- Closed
-
RHPAM-1680 [DMN Designer] Context: Default can be any expression type
- Closed
-
RHPAM-1682 [DMN Designer] Add support for optional typeRefs
- Closed