Hi @Philipp_Ossler
Not really. I setup task listener as you suggest. Now I see both variables(I change name to myValueLocal in order not to be confused by duplicated variables names).
Strange that both variabls are visible in a SecondTask scope. Nevertheless, there is no response for request:
{“taskVariables”: [{“name”: “myValueLocal”,
“value”: “2”,
“operator”: “eq”
}],
“processDefinitionName”: “Test variables”,
“taskDefinitionKey”: “task2”
}
However when I use neq operator all tasks are returned including those with myValueLocal set to 2 - that the difference when compared to version without task listener.
Basically, I need to check whether a multi instance task for specific conditions already exists in order not to create duplicated task. Maybe my approach of using local variables is not correct.