Matteo Mortari created DROOLS-5054: -------------------------------------- Summary: DMN Editor does not cascade allowedValues for Decision Table input Key: DROOLS-5054 URL: https://issues.redhat.com/browse/DROOLS-5054 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Matteo Mortari Assignee: Michael Anstis Attachments: Traffic Violation (1).dmn Following the Traffic Violation tutorial, e.g.: https://access.redhat.com/documentation/en-us/red_hat_decision_manager/7.... Despite {{Violation.Type}} is defined as a constraint enumeration: {code:xml} <dmn:itemComponent id="_D16710C9-F626-4351-ABCE-C7F0A1A82F70" name="Type" isCollection="false"> <dmn:typeRef>string</dmn:typeRef> <dmn:allowedValues kie:constraintType="enumeration" id="_C4AFEF49-331A-4A9F-B9AF-478DB7525008"> <dmn:text>"speed", "parking", "driving under the influence"</dmn:text> </dmn:allowedValues> </dmn:itemComponent> {code} the constraints are not cascaded down to the Decision Table input: {code:xml} <dmn:input id="_CD3B3323-7C98-44CB-802E-F3A52A4364CC"> <dmn:inputExpression id="_621CEBEF-0710-4474-AFC3-D305517A348F" typeRef="string"> <dmn:text>Violation.Type</dmn:text> </dmn:inputExpression> </dmn:input> {code} and this does not allow for the Decision Table static analysis to be perfomed (the static analysis reckognize these values seems to be enumerated, but the decision table column does not list them) -- This message was sent by Atlassian Jira (v7.13.8#713008)