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
This is the controller panel for Smart Panels app
- is duplicated by
-
CAM-9140 Check usage of #isHistoryLevelFullEnabled when custom history level is set
-
- Closed
-