Currently there is very limited list of available Unit to select for Number type of Input in a Decision Model. Suggest to have time unit to represent days:hours:minute (dd:hh:mm). Apart from that also require other units for technical measurement including Hz, MHz, dB and dBmV used in telecommunication industry. If viable, the adding of unit type could be made as a configuration for admin, or allo custom type unit where ...more »
Currently there is no unit available in the decision logic table to define time as duration, i.e number of days/hours/minutes/seconds. The current setting in the decision logic table using a specific date/time is not suitable in the case where the measurement is duration.
If you apply the PDF export function to a DMN diagram, you will get a BPMN-like view of the used input variables. If modeled, a tree-like concatenation of decision tables is displayed as well. The important thing, the decision table (s) themselves with the case distinctions, their criteria and result definitions, is not exportable today. There is also no way to copy out the prepared decision table formatted by copy & ...more »
TranslationTranslated View Original
Currently the Multi Instance Decision has an attribute for Input List, which is based on the Inputs of the single Decision model in the Multi Instance Decision. However in most cases, it is the Output List that is required from the multiple instance of the single Decision (Decision A in diagram), and the aggregation of these output to be used for the other Decision (Decision B in diagram) depending on these outputs. In ...more »
When you create a control table where all input values are enumerated, Signavio should allow automatic rule generation. Here, all combinations are formed automatically. The modeler then has to complete only the results fields.