Details
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
AT
- Removal time is calculated based on process engine configuration settings for removal time strategy (start, end, none) and TTL of local process definition:
Batch batch = historyService.setRemovalTimeToHistoricProcessInstancesAsync() .byQuery(query) .executeAsync();
- if removal time strategy is set to ...
- start: removal time = startTime + TTL
- end: removal time = endTime + TTL
- if process instance has not been ended and removal time strategy is set to end, instance is not updated
- none: no update is performed
- if removal time strategy is set to ...
- Removal time can be set to an absolute value or to null:
Batch batch = historyService.setRemovalTimeToHistoricProcessInstancesAsync() .byQuery(query) .removalTime(new Date()) .executeAsync();
- process engine configuration settings in terms of removal time strategy (start, end, none) are disrespected
- Throw BadUserRequestException if no historic process instances can be found
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is depended on by
-
CAM-10172 Introduce extra mysql queries for setting removal time async without respecting hierarchies
- Closed
-
CAM-10173 Introduce specific create auth permission for all removal time batches
- Closed
-
CAM-10174 Introduce operation logs for all removal time batches
- Closed
-
CAM-10175 I can read documentation about removal time batches
- Closed
-
CAM-10176 Using REST API, I can set a removal time via batches asyncronously
- Closed
- is related to
-
CAM-10152 Using Java API, I can recalculate the removal time based on TTL for processes asynchronously
- Closed