Details
-
Bug
-
Resolution: Done
-
Critical
-
7.14.0.Final
-
2018 Week 45-47
-
5
-
Workaround Exists
-
-
NEW
-
NEW
Description
The decision table output column data type is not stored, if the decision table was generated according to some input data.
An example of such table is attached auto.dmn . This table was created in steps below:
- Create new DMN diagram
- Add an Input Data node : applicant
- Add a Decision node: applicant score
- Connect them
- Define new data type: tApplicant.
- lang:string (Constraints: "c", "java")
- open source: boolean
- Set applicant node data type as tApplicant
- Set applicant score node data type as number
- Open expression editor for applicant score node
- Set its top level expression as Decision Table
- Save and download DMN model
- It will be like the attached
<dmn:output id="_E6C7E5E6-45C5-4FC2-A37B-69806046893F" name="output-1" typeRef="string"> <dmn:outputValues id="_B473BAB4-521D-4FD9-88BC-C28CD497F03A"> <dmn:text></dmn:text> </dmn:outputValues> <dmn:defaultOutputEntry id="_85BF133E-380C-4F0E-9E2A-0C5C6493F6B4" typeRef="string"> <dmn:text></dmn:text> </dmn:defaultOutputEntry> </dmn:output>
Attachments
Issue Links
- is cloned by
-
RHPAM-1676 [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
- Closed
- relates to
-
DROOLS-3225 [DMN Designer] Decision table output data type is not stored
- Closed