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

I can determine the current state of a historic process instance

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.6.0, 7.6.0-alpha3
    • Component/s: engine
    • Labels:

      Description

      There exists a field (e.g. processInstanceState) to determine the current state of a historic process instance. The following distinction should be made:

      • active
      • suspended
      • completed
      • externally terminated (for example in case of RuntimeService#deleteProcessInstance())
      • internally terminated (e.g. terminate end event, etc.)

      The semantic of the states should be clearly specified.

        Issue Links

          Activity

          Hide
          askar.akhmerov Askar Akhmerov added a comment - - edited

          Basic AT:

          • TC1
            • process definition
              • start
              • parallel gateway
              • termination event
              • end event
            • assert
              • one historic process entity in the database
              • state - TERMINATED_INTERNALLY
          • TC2
            • process definition
              • start
              • user task
              • suspend
              • activate
              • end
            • assert
              • after each step proper state is assigned to the record
                • ACTIVE
                • SUSPENDED
                • ACTIVE
                • COMPLETED
          • TC3
            • process definition
              • start
              • ut
              • cancel
            • assert
              • state - TERMINATED_EXTERNALLY
          • TC4
            • process definition
              • start
              • script task (throw new exception)
              • end
            • assert
              • state - COMPLETED
          • TC5
            • process definition
            • P1:
              • start
              • call activity with boundary error event
                • on error end
              • end
            • P2:
              • start
              • error end event
            • assert
              • two records in HPI
              • one in state COMPLETED
              • second one in state TERMINATED_INTERNALLY

          exact identification of activity type that triggered TERMINATED_INTERNALLY state is out of scope for this ticket.

          Show
          askar.akhmerov Askar Akhmerov added a comment - - edited Basic AT: TC1 process definition start parallel gateway termination event end event assert one historic process entity in the database state - TERMINATED_INTERNALLY TC2 process definition start user task suspend activate end assert after each step proper state is assigned to the record ACTIVE SUSPENDED ACTIVE COMPLETED TC3 process definition start ut cancel assert state - TERMINATED_EXTERNALLY TC4 process definition start script task (throw new exception) end assert state - COMPLETED TC5 process definition P1: start call activity with boundary error event on error end end P2: start error end event assert two records in HPI one in state COMPLETED second one in state TERMINATED_INTERNALLY exact identification of activity type that triggered TERMINATED_INTERNALLY state is out of scope for this ticket.
          Show
          sebastian.menski Sebastian Menski added a comment - Askar Akhmerov the Test MultiTenancyHistoricProcessInstanceStateTest is failing on history level none. Cloud you please fix this https://hq2.camunda.com/jenkins/ci/job/7.6-engine-UNIT-historylevels/lastCompletedBuild/container=h2,historylevel=none,jdk=jdk-6-latest/testReport/org.camunda.bpm.engine.test.api.multitenancy.query.history/MultiTenancyHistoricProcessInstanceStateTest/testSuspensionWithTenancy/

            People

            • Assignee:
              Unassigned
              Reporter:
              roman.smirnov Smirnov Roman
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development