[DMN Designer] Gap analysis when Data Type is constrained by enumeration

Running through the "Getting Started Guide" for 7.45.0.Final.

The Data Type "Violation.Type" has an enumeration defined by "3.2. Creating the traffic violations DMN custom data types". Creating the remainder of the example has subsequent saves of the file. The static analysis of the Decision Table for "Fine" shows "Columns: [Violation.Type] relate to FEEL string values which can be enumerated for the inputs; Gap analysis skipped."

As a User I defined the enumeration in the ItemDefinition and therefore was surprised to receive the warning. The warning can be dismissed by replicating the constraint in the Input Clause column definition.

This is probably a DMN specification requirement and the solution is to either copy existing Data Type constraints to the Input Clause column when it is created (IIRC there may be a JIRA for this already, but I'm logging this JIRA in case I remember wrongly.. better to close one than not have any) or to relax the static validation to also include a Data Type lookup when it exists.

I'll leave the decision to mmortari@redhat.com, etirelli and karreiro_.