Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-6035

Executing a compensation handler can access camunda:input variables that are not part of the variable snapshot when the scope finished

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Open
    • Priority: L3 - Default
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: engine
    • Labels:

      Description

      Problem:
      Creating an event scope execution executes the input mappings of the scope.

      Situations:

      • During regular process execution, the event scope execution is created, then the input mappings are executed, then the variable snapshot is copied to the new event scope execution. In case the variable snapshot does not overwrite all input variables, there will be unexpected snapshot variables when compensation is thrown
      • During migration, when an event scope is added its input mapping is executed. This leads to variables being present in the variable snapshot that were not present when the task was executed

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            thorben.lindhauer Thorben Lindhauer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: