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

Variables set on async process start miss when starting a process instance via FormService#submitStartForm()

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.2.0, 7.1.7, 7.2.0-alpha6
    • Component/s: engine
    • Labels:
      None

      Description

      1. start a process instance which contains an async start event via FormService#submitStartForm()

      -> the variables are not persisted

      AT:

      • variables set during the start of a process with an async start event are persisted

      See failing testcase:
      https://github.com/camunda/camunda-bpm-platform/commit/7af4df9d26160952fd04168f6eebfbf328d66ae3#diff-01b7110b4b9b69e80138d60821281a40R217

      Remarks regarding the solution:

      • for non-async start event, variables and history should be set correctly
      • for async start event, variables and history should have the correct entries with the restriction that activityInstanceId misses on HistoricFormPropertyUpdates. This is due to the problem that these updates have to be written before the async continuation at which the activityInstanceId is unknown yet. This drawback should be documented by a failing testcase and a corresponding ticket.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              meyer Daniel Meyer
              Reporter:
              roman.smirnov Roman Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: