Using script variables in task name and history tables

Camunda 7 Topics Discussion & Questions
1

Hi,

we are using script variables in the task name. They are correctly replaced for the given user task instance, but when we look at the historic entry the original not processed value is saved (e.g. name="${myNameValue}").

Is this the correct behaviour, so the historic task entry does not contain the resolved name value?

Regards

Alexander

2

Hi Alexander,

This sounds like a bug. To validate that, could you please add a minimal BPMN model where you use such an expression? Also, which Camunda version do you use?

Cheers,
Thorben

3

Hello,

I have created an example workflow. When it is executed the following content is saved in the history tables for the user task.

ACT_HI_ACTINST(ACT_NAME_) = ${label} => so the expression is saved here
ACT_HI_TASKINST(NAME_) => My label => so the evaluated expression value is saved

The question is, should also the evaluated expression value be saved in the ACT_HI_ACTINST table?

ExpressionInTaskName.bpmn (3.7 KB)

Regards

Alexander

4

Anything new on this if this is really a bug or a correct behaviour? We are using 7.8.0 version of Camunda.

5

Sorry for not getting back earlier. This is expected behavior as the name of the activity in the diagram is ${label}.