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

Using process instance modification, a process instance may end between instructions

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 7.3.0, 7.3.0-alpha4
    • None
    • engine

    Description

      Assume the following process:

      The following works:

      1. Instantiate the process
      2. Perform the following modification:
        1. cancel the task instance
        2. start before task

      The following does not work

      1. Instantiate the process
      2. Perform the following modification:
        1. cancel the task instance
        2. start after task
        3. start before task

      The reason is that starting after the task already ends the process instance and removes it from the database. The third instruction results in database integrity violations.

      This problem might become more evident when using CAM-3454 with a completely synchronous process model.

      Solution Options:

      1. either consider this part of the feature; then, there should be a proper exception telling the user that the process instance has intermediately finished
      2. the process instance should not be removed when the process ends with more pending modification instructions

      Test case that asserts solution 2 (this does not mean solution 2 is favored): https://github.com/camunda/camunda-bpm-platform/commit/a8decdefce0557a80eb3260b2fe3009a556b5dd3

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          1. diagram.svg
            8 kB
            Thorben Lindhauer

          Issue Links

            Activity

              People

                sebastian.menski Sebastian Menski
                thorben.lindhauer Thorben Lindhauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce