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
If you use @Variable only those variables are fetched from the payload and will be given to you. If you in addition inject the Payload Map<String, Object> as a parameter it will still only contain the variables present as individual method parameters.
Wanted Behaviour
Be able to overwrite this behavior with additional attribute of the ProcessEngineWorker annotation and still fetch all variables. (adding overwriteVariableFetching boolean parameter)
Possible Workarounds
Not use @Variable and Map<String, Object> in the same method.
The text was updated successfully, but these errors were encountered:
zambrovski
changed the title
Be able to get all process variable injected, even if the explicit injection of a named variable is used.
Be able to get all process variables injected as a payload map, even if the explicit injection of a named variable is used.
Sep 5, 2024
Scenario
Current Behaviour
If you use
@Variable
only those variables are fetched from the payload and will be given to you. If you in addition inject the PayloadMap<String, Object>
as a parameter it will still only contain the variables present as individual method parameters.Wanted Behaviour
Be able to overwrite this behavior with additional attribute of the
ProcessEngineWorker
annotation and still fetch all variables. (addingoverwriteVariableFetching
boolean parameter)Possible Workarounds
Not use
@Variable
andMap<String, Object>
in the same method.The text was updated successfully, but these errors were encountered: