You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When defining a @Jobworker, we find the following:
If all parameters are declared @variable --> values are passed correctly (e.g., foobar( @variable a, @variable b ))
If all parameters are declared @VariablesAsType --> values are passed correctly (e.g., foobar( @VariablesAsType a, @VariablesAsType b ) )
If some parameters are @variable and others @VariablesAsType --> @VariablesAsType values are missing (e.g., foobar( @variable a, @VariablesAsType b ) )
Looking closer, we see that as soon as a @variable parameter is used, all non-@variable (i.e., @VariablesAsType) parameters are missing from ActivatedJob: getVariablesAsMap() and getVariables() bear witness to this. Stepping through the code shows that this seems to happen fairly deep in the system; possibly even prior to spring-zeebe (not sure).
This is not a problem in the engine: all parameters are shown correctly in Operate.
Invoking getVariablesAsMap().get() and getVariablesAsType() does not trigger this behavior, so it must be something else.
The versions tested are:
Zeebe 8.1.8
Spring-Zeebe 8.2.0
The text was updated successfully, but these errors were encountered:
When defining a @Jobworker, we find the following:
Looking closer, we see that as soon as a @variable parameter is used, all non-@variable (i.e., @VariablesAsType) parameters are missing from ActivatedJob: getVariablesAsMap() and getVariables() bear witness to this. Stepping through the code shows that this seems to happen fairly deep in the system; possibly even prior to spring-zeebe (not sure).
This is not a problem in the engine: all parameters are shown correctly in Operate.
Invoking getVariablesAsMap().get() and getVariablesAsType() does not trigger this behavior, so it must be something else.
The versions tested are:
Zeebe 8.1.8
Spring-Zeebe 8.2.0
The text was updated successfully, but these errors were encountered: