Camunda-modeler: `NO LIST AGGREGATION` is misleading term for DMN Hit Policy Collect without operator

[sebwarnke]

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.

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]

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]

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

[nikku]

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]

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