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

Variable is not implicitly updated if scope is destroyed in same transaction

    Details

    • Type: Task
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.8.0, 7.8.0-alpha2
    • Component/s: engine
    • Labels:
      None

      Description

      Scenario:

      • process instance with a variable of type object
      • update that object value implicity (i.e. without calling DelegateExecution#setVariable or similar)
      • process instance ends in same transaction

      Result:

      • variable update is not reflected in history

      Expected behavior:

      • it should be visible in history

      Variants:

      • this is not only the case for the process scope, but basically for any scope (i.e. updates local variables of subprocesses are not reflected in history if the subprocess ends in same transaction)

      Root cause:

      • destroying a scope clears all the variables
      • clearing variables drops the cached value
      • check for implicit value updates happens only after that and is based on the cached value

      Forum post:

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development