[
https://issues.jboss.org/browse/DROOLS-4640?page=com.atlassian.jira.plugi...
]
Michael Anstis commented on DROOLS-4640:
----------------------------------------
[~tari_manga] Could you please clarify your expectation?
The {{ItemDefinition}} "Violation.Type" presumably has a constraint defined as
an enumeration for "speed", "parking" and "driving under the
influence".
I assume you expect the {{InputClause.UnaryTests}} to auto-magically also be defined as
the same enumeration?
Furthermore, presumably, if the constraint for "Violation.Type" is changed the
{{InputClause.UnaryTests}} should change too? Does this relationship work both ways? i.e.
should the User be able to modify the {{InputClause.UnaryTests}} and this be reflected in
the "Violation.Type" constraint, or should the {{InputClause.UnaryTests}} be
read-only and always reflect the {{ItemDefinition}} constraint?
Do you know of other scenarios when the same behaviour should apply? e.g.
{{OutputClause.UnaryTests}}. Any others?
DMN Editor constraint on Type does not reflect in Decision Table
----------------------------------------------------------------
Key: DROOLS-4640
URL:
https://issues.jboss.org/browse/DROOLS-4640
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Matteo Mortari
Assignee: Guilherme Gomes
Priority: Major
Attachments: image-2019-10-11-11-02-31-881.png
Editing the classic Traffic Violation item definition to put enumeration on string for
the violation type "speed", "parking", ... once done in the item
definition is not reflected in the decision table, and that prevents also from getting the
real intended DT static analysis message for the table.
!image-2019-10-11-11-02-31-881.png|thumbnail!
in the attached screenshot I entered the data also manually in the DT's property
right tab.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)