There is an additional correlation parameter that takes variables with the following semantics:
Intermediate message event/receive task: Set the variables on the execution that is in the intermediate event (like setVariablesLocal)
Event sub process: Set the variables on the execution that represents the scope instance of the event sub process (unlike setVariablesLocal)
This is the controller panel for Smart Panels app
[CAM-10680] On message correlation, I can set local variables in the triggered execution
Link | New: This issue is depended on by SUPPORT-5916 [ SUPPORT-5916 ] |
Description |
Original:
Intermediate message event/receive task: Set the variables on the execution that is in the intermediate event (like {{setVariablesLocal}})
Event sub process: Set the variables on the execution that represents the scope instance of the event sub process (unlike {{setVariablesLocal}}) |
New:
There is an additional correlation parameter that takes variables with the following semantics:
Intermediate message event/receive task: Set the variables on the execution that is in the intermediate event (like {{setVariablesLocal}}) Event sub process: Set the variables on the execution that represents the scope instance of the event sub process (unlike {{setVariablesLocal}}) |
Link | New: This issue is related to SUPPORT-11047 [ SUPPORT-11047 ] |
Labels | Original: SUPPORT | New: SUPPORT engine |
This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2266. Please use this link for any future references and continue any discussion there.