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

Some historic events can't be deleted on custom history level

    Details

      Description

      Impact: Some APIs to remove history data do not work correctly with a custom history level, and leave orphaned entries in the database.

      AT: The engine makes no more assumptions about the history level in order to decide if a history entry is present in the database or not.

      If the user implements an custom history level and tries for example to delete historic incidents this will no work, since the history level full is expected.

          if (isHistoryLevelFullEnabled()) {
          ...
          }
      

      This applies for incidents, identity link's and user operation logs.

      See the following methods:

      • HistoricIncidentManager:
        • deleteHistoricIncidentsByProcessDefinitionId
        • deleteHistoricIncidentsByJobDefinitionId
        • deleteHistoricIncidentsByBatchId
      • UserOperationLogManager:
        • deleteOperationLogEntryById
      • HistoricIdentityLinkLogManager:
        • deleteHistoricIdentityLinksLogByProcessDefinitionId
        • deleteHistoricIdentityLinksLogByTaskId

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              nikola.koevski Nikola Koevski
              Reporter:
              christopher.zell Christopher Zell
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development