DMN evaluation result is different on 7.19 and 7.20

[d-molotchko-cap]

Environment (Required on creation)

7.20.0

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

There is existing DRD that provides different result on 7.19.0 and 7.20.0 versions. Due to business restrictions I've created a synthetic example that demonstrates this. Have a look on https://github.com/CapBPM/dmn-evaluation-context-issue

Steps to reproduce (Required on creation)

Use mvn -Pc719 test for running example on 7.19.0 platform
and mvn -Pc720 test for running example on 7.20.0 platform

Observed Behavior (Required on creation)

You will get assertion on second run

Expected behavior (Required on creation)

Test should pass on both platforms

Root Cause (Required on prioritization)

It seems there was a change that changed context ordering while DRD execution somehow

Links

PoC: https://github.com/CapBPM/dmn-evaluation-context-issue

[tasso94]

Hi @d-molotchko-cap,

This behavior change was introduced with FEEL Engine 1.16.1.

Since this is not a bug in Camunda 7, please open a ticket in the issue tracker of the FEEL Engine:
https://github.com/camunda/feel-scala/issues/new/choose

As a workaround, you could downgrade the FEEL Engine to version 1.16.0 by adding the following maven coordinates to your spring boot application:

<dependency>
  <groupId>org.camunda.feel</groupId>
  <artifactId>feel-engine</artifactId>
  <version>1.16.0</version>
  <classifier>scala-shaded</classifier>
</dependency>

Best,
Tassilo

[d-molotchko-cap]

Hi @tasso94,

thanks for details!