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

I can identify externally terminated historical process instances

    Details

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

      Description

      right now there is no way to distinguish between Historical process instances that were ended externally, for instance through the cockpit, and internally, for instance through the termination event, or terminating error boundry.

      Please add a way to distinguish between those.

      Suggested implementation: add boolean parameters to indicate external termination of the historic process instance

        Activity

        Hide
        askar.akhmerov Askar Akhmerov added a comment -

        While implementing I realized, that combining parts of this implementation with state column in the database achieves desired outcome on https://app.camunda.com/jira/browse/CAM-3477. So this ticket will be closed, Implementation will be done on original ticket.

        Show
        askar.akhmerov Askar Akhmerov added a comment - While implementing I realized, that combining parts of this implementation with state column in the database achieves desired outcome on https://app.camunda.com/jira/browse/CAM-3477 . So this ticket will be closed, Implementation will be done on original ticket.

          People

          • Assignee:
            Unassigned
            Reporter:
            askar.akhmerov Askar Akhmerov
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development