On implicit object value update, historic properties activityInstanceId and executionId are incorrect

XMLWordPrintable

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

      This is a general limitation of the feature to update an object variable implicitly. We detect an implicit update when the current command context is closed. At this point in time, the corresponding variable instance still references an execution but that execution is no longer in the state it was in when the variable was actually updated.

      At least the following properties can be incorrect for the resulting HistoricVariableInstance:

      • activityInstanceId (in case the execution has executed additional activities in between)
      • executionId (in case of tree compaction/expansion in between)

      test case: org.camunda.bpm.engine.test.history.HistoricVariableInstanceTest.FAILING_testImplicitVariableUpdateActivityInstanceId

        This is the controller panel for Smart Panels app

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

                Created:
                Updated: