DmnExecutionContext.ExecuteDecision() seems to be using the label instead of the name to identify output from a dependent Decision about common.dmn.engine HOT 2 CLOSED

Hello @ongbengtiong,
your last statement "Seems like you are using the label as the identifier of the output element instead of using name." is correct. It's also mentioned in the Outputs in XML chapter of documentation.

The reason why I decided to do it this way is that label is something that is what you seen in the Camunda decision table designer (and in the simulator as well) by default. Also when you create an output, the output name is empty by default and I think the most of users just set the label.

So the behavior you described is "as designed". Frankly I'm not sure whether to change (update) the design to take the name into the consideration as well, because this will probably be breaking change and a lot of existing DMN files might stop working properly, so there will have to be some king of flag/policy allowing the user to override the current behavior when needed.

Thanks
Radek

from common.dmn.engine.

closing the ticket, works as designed

from common.dmn.engine.