-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
Clarify the following sections:
- https://docs.camunda.org/manual/7.15/user-guide/process-engine/batch-operations/#set-a-removal-time
It is not clear what the hierarchy means, hence it is not clear what is the effect of the hierarchical flag.Historic process and decision instances can be part of a hierarchy. To set the same removal time for all instances within a hierarchy, the method .hierarchical() needs to be called.
- https://docs.camunda.org/manual/7.15/user-guide/process-engine/history/#instance-removal-time
It is not clear that setting the removal time for a chilf process is propagated to the parent process. Furthermore, it is not clear how this section relates to the hierarchical flag. The sentence below could also imply, that is not possible to have different removal times in a hierarchy (even when not using the hierarchical flag to set it).For process and decision instances in a hierarchy (e.g. a process instance that is started by another process instance via a BPMN Call Activity), the removal time of all instances is always equal to the removal time of the root instance.
This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2623. Please use this link for any future references and continue any discussion there.