DMN Engine should only evaluate until first matching rule with Hit Policy "First"

[ThorbenLindhauer]

This issue was imported from JIRA:

Field	Value
JIRA Link	CAM-12048
Reporter	KVB24Dx What is this name? This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.
Has restricted visibility comments	true

---

AT:

• For a DMN table with Hit Policy "First", as soon as a matching rule is found, the decision evaluation should stop

Reasoning:

• saves EDEs and execution time

Context:

• Please follow this discussion with myself, Stefan, Rob, and Yana: https://camunda.slack.com/archives/C6M6X3EKZ/p1592232459134700

Links:

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @tasso94

---

Hi KVB24Dx,

Thank you for reaching out to use with your feature request.

We will qualify the feature and come back to you soon – next week at the latest.

Stay tuned!

Best, Tassilo

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @tasso94

---

Hi KVB24Dx,

Thanks for reaching out to us with your request.

Right now, independently of the chosen hit policy, all rules are first evaluated, and afterward, the matching rules are filtered based on the selected Hit Policy. The related code can be found here <1>.

Therefore, I cannot confirm that the DMN Engine stops executing the subsequent rules once the first rule evaluates to true when the Hit Policy "First" was selected.

Your proposal sounds like a valid feature request to me. Therefore, I'll forward the feature request for decision making.

Stay tuned!

Best, Tassilo

<1>

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @ThorbenLindhauer

---

KVB24Dx, as this is not an easypick change we cannot schedule the ticket on the side. Please bring it via @nevries to a release planning session if you would like us to prioritize it.