-
Notifications
You must be signed in to change notification settings - Fork 190
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
8 additions
and
22 deletions.
There are no files selected for viewing
30 changes: 8 additions & 22 deletions
30
docs/components/modeler/reference/modeling-guidance/rules/httl-required
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,28 +1,14 @@ | ||
| --- | ||
| id: httl-required | ||
| title: HTTL (History Time To Live) required | ||
| description: XXX. | ||
| title: HTTL required | ||
| description: HTTL (History Time To Live) is required in BPMN, DMN, and CMMN models for History Clean up. | ||
| --- | ||
| Each execution of a model resource (BPMN, DMN, and CMMN) generates historic data during execution that is stored in the database. The Camunda 7 History Cleanup removes this historic data from the database based on the HTTL (History Time To Live) defined. If using the History Cleanup in Camunda 7 the HTTL must be defined in one of the following ways: | ||
| - Define HTTL per model directly in the Camunda Modeller | ||
| - Set a default HTTL for the engine that is applied to all deployed model resources on the engine | ||
| - Switch off the HTTL check for the deployment if History Cleanup is not used | ||
|
|
||
| import MarkerGuideline from "@site/src/mdx/MarkerGuideline"; | ||
|
|
||
| An [escalation event](../../../../bpmn/escalation-events/) must reference an escalation defined in the process. The referenced escalation must have a defined escalation code. To fix this problem, open the **Escalation** group in the properties panel, select or create an escalation, and specify its escalation code. | ||
|
|
||
| Camunda 8.2 and later support catch-all events and do not require an escalation reference. | ||
|
|
||
| ## <MarkerGuideline.Invalid /> No escalation selected | ||
|
|
||
|  | ||
|
|
||
| ## <MarkerGuideline.Invalid /> No escalation code specified | ||
|
|
||
|  | ||
|
|
||
| ## <MarkerGuideline.Valid /> Escalation selected and escalation code specified | ||
|
|
||
|  | ||
|
|
||
| ## Reference | ||
|
|
||
| - [Escalation events](../../../../bpmn/escalation-events/) | ||
| - [Rule source](https://github.com/camunda/bpmnlint-plugin-camunda-compat/blob/main/rules/camunda-cloud/escalation-reference.js) | ||
| - [Camunda 7 - Enforce History Time To Live](https://docs.camunda.org/manual/develop/update/minor/719-to-720/#enforce-history-time-to-live) | ||
| - [Camunda 7 - History Cleanup](https://docs.camunda.org/manual/latest/user-guide/process-engine/history/#history-cleanup-by-example) |