`NO LIST AGGREGATION` is misleading term for DMN Hit Policy Collect without operator

camunda / camunda-modeler

An integrated modeling solution for BPMN, DMN and Forms based on bpmn.io.

https://camunda.com/products/modeler

MIT License

1.51k stars 483 forks source link

`NO LIST AGGREGATION` is misleading term for DMN Hit Policy Collect without operator #1619

Open sebwarnke opened 4 years ago

sebwarnke commented 4 years ago

Description

The DMN specification describes the Hit Policy as follows;

In Camunda Modeler we use the term NO LIST AGGREGATION to express that the Hit Policy Collect is to be used without an operator. This usually results in a list of outputs. NO LIST AGGREGATION expresses the opposite. Meaning a less skilled modeller would expect to not receive a list in return.

Bildschirmfoto 2019-11-29 um 12 46 35

Environment

Camunda Modeler Version: 3.5.0

Possible Solution

Replace NO LIST AGGREGATION by NONE
and for even closer alignment with the spec change the drop down label Aggregation to Operator.

ingorichtsmeier commented 4 years ago

Maybe "without list aggregation"?

or "without aggregation"?

or "without function"? (This term is used in the specification, but can be read as "without working" which is useless as well)

nikku commented 4 years ago

I personally like the proposed solution: Operator = NONE || ....

nikku commented 4 years ago

We may rework substantial bits of the HIT POLICY select in the future so I cannot promise we make label related changes right now. Changing the option to simply NONE sounds like a good solution in this case. => We re not aggregating anything but returning the list as is.

nikku commented 4 years ago

As mentioned: We will revise this in future versions of our tool.