Loading...

XML

Word

Printable

Steps to Reproduce:
1. define a data type with number property constrained to a range
2. use the data type as input to decision table
3. add a single row matching the whole range
4. validate the decision and see Gaps reported
Release Note Text:

Hide
This issue is reproducible for each decision table generated before https://github.com/kiegroup/kie-tools/pull/1383.

More detailed. It is not enough to have data type constraint specified in data type details, user need to set the same constraint also in decision table column header details.

Before https://github.com/kiegroup/kie-tools/pull/1383 user needed to sync data type constraint definition and column header definition manually.

Show
This issue is reproducible for each decision table generated before https://github.com/kiegroup/kie-tools/pull/1383 . More detailed. It is not enough to have data type constraint specified in data type details, user need to set the same constraint also in decision table column header details. Before https://github.com/kiegroup/kie-tools/pull/1383 user needed to sync data type constraint definition and column header definition manually.
Docs QE Status:
NEW
QE Status:
NEW
[QE] How to address?:
---
[QE] Why QE missed?:
---

Validation is reporting Gaps in constrained data type even though the matched range equals the constrained type range.

Happens for both imported and structure data types.