Everything within this section is only visible while editing. Use status for "stub" (red) "progress" (yellow) "review" (blue) and "refactor" (grey). Everything contained within the table is displayed in the (INTERNAL) Reports page. | Status | |
|---|
| Priority | 3.0 |
|---|
| Note | published, only the object history - rest of the concept is outstanding |
|---|
| Assignee |
|
|---|
Resources Remarks- Antje: page created
- Antje: table with history codes created
 Needs to be moved to the Document Lifecycle page as subpage - if the DLM page is ready to get published- Heading 1 "Summary" deleted for now - needs to be added later on if the concept is written in detail
- Antje: Cleanup Section startet in the hidden part
Cleanup of the Audit Trail It is possible to delete old audit trail entries by means of the Commander service and a configuration file ./config/system/cleanupConfiguration.json. The audit field in the JSON file contains the details on the deletion of the audit trail entries using the following parameters: | Parameter | Description |
|---|
| defaultCleanupAfterDays |
| | actions | Contains a list | Parameter | Optional | Description |
|---|
| comment |
|
| | action |
|
| | cleanupAfterDays |
|
|
|
| Code Block |
|---|
| language | yml |
|---|
| title | Example cleanupConfiguration.json |
|---|
| {
"audit": {
"defaultCleanupAfterDays": -1,
"actions": [
{
"comment": "OBJECT_CREATED",
"action": 100,
"cleanupAfterDays": -1
},
{
"comment": "DOCUMENT_ACCESSED",
"action": 400,
"cleanupAfterDays": 1
}
]
}
} |
The corresponding command is audit cleanup with two available parameters: | Parameter | Description | Example |
|---|
| -h | --help | Display the help for the command. | audit cleanup -h | | -t | --tenant | Specify the the target tenant. If not specified, the command is executed for all tenants. | audit cleanup -t exampletenant |
default
(with the example tenant default) |
When executed, the command reads the configuration |