Odd behaviour with complex input parameters

BPMN & Modeling Discussion & Questions
1

Dear Camunda community,

I have found an odd behaviour of the DMN engine (7.9-alph2) with long / complex variable names.

E.g. I have a DMN table with 4 string parameters sourced from a LinkedHashMap object.
On of the input parameters throws an exception if specified as JUEL expression: DMN-01002 Unable to evaluate expression for language ‘juel’

ARINVOICE_REQUEST.data.ReasonCode.reason_description

However, the same parameter specified as JavaScript expression works just fine. Three other parameters have the same structure ARINVOICE_REQUEST.data… and string data type, but work fine as JUEL expessions.

Any ideas?

Best regards,
Ilya

2

As a quick test can you shorten the variable names and see if it still works

3

Hi @StephenOTT,

Looks like the problem is in Modeller tool. I was playing with different variable name length as suggested and have found that if I specify JUEL explicitly, I do not have issues:

  <input id="InputClause_RC" label="Reason Code">
    <inputExpression id="LiteralExpression_RC" typeRef="string" expressionLanguage="JUEL">
      <text>ARINVOICE_REQUEST.data.ReasonCode.reason_description</text>
    </inputExpression>
  </input>

If I just add a variable name without specifying JUEL I got this XML in DMN and it was failing:

  <input id="InputClause_RC" label="Reason Code">
    <inputExpression id="LiteralExpression_RC" typeRef="string">
      <text>ARINVOICE_REQUEST.data.ReasonCode.reason_description</text>
    </inputExpression>
  </input>

Best regards,
Ilya