Set Default History Time To Live For Decision Tables #2496
Closed
Description
This issue was imported from JIRA:
| Field | Value |
|---|---|
| JIRA Link | CAM-13082 |
| Reporter | NxjorXgWhat is this name?This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter. |
| Has restricted visibility comments | true |
Environment (Required on creation):
Any engine setup
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
Steps to reproduce:
- Configure the process engine with property
historyTimeToLive, e.g. set toP30D - Deploy a DMN table to the process engine
Observed behavior:
- The decision definition's TTL is
null - Any executed standalone decision does not receive a removal time (it's not a problem for decision executions as part of BPMN process instances, because those receive the removal time of the process instance)
Expected behavior:
- The decision definition's TTL is 30 days
- Executed standalone decision instances receive an accurate removal time
Root cause:
org.camunda.bpm.engine.impl.dmn.transformer.DecisionDefinitionHandler.createFromDecision(DmnElementTransformContext, Decision)doesn't use the engine configuration as the default
Hints:
- The behavior should also be fixed for decision requirements definitions
- The docs suggest that the configuration parameter applies to decision tables (https://docs.camunda.org/manual/7.14/reference/deployment-descriptors/tags/process-engine/#history-cleanup-configuration-parameters)
Links: