-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
Given
- some historic data is not needed any more (or regularly)
When
- time comes (scheduler?)
or - some API is called
Then
- appropriate history data is removed from database
So that
- disk resources are freed
- less data is operated in interactions with historic tables -> performance improves
- user does not see obsolete data in cockpit
This is the controller panel for Smart Panels app
- depends on
-
CAM-7541 On startup engine schedule history cleanup
- Closed
-
CAM-7542 Async history cleanup must be configurable
- Closed
-
CAM-7538 I can call history cleanup for process instances via Java API
- Closed
-
CAM-7539 I can call async history cleanup via REST API and Java API
- Closed
-
CAM-7543 Document history cleanup
- Closed