...

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.

Contains a list of mappings of the minimum age of audit trail entry types and the corresponding cleanup timing.

In the example configuration below, the defaultCleanupAfterDays Parameter implies that all audit trail entries can be deleted after 10 days, if not further specified in actions. However, two mappings are listed in actions overwriting the defaultCleanupAfterDays value for two audit trail entry types. The entries of Core API type 100 (OBJECT_CREATED) have do stay forever and will be never deleted. The entries of Core API type 400 can be deleted already after 1 days.

{
	"audit": {
		"defaultCleanupAfterDays": 10,
		"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:

When executed, the command reads the configuration

• Antje: Cleanup Section moved to Commander tooling page

For a cleanup the audit trail, the commander service can be used as a tool to remove audit trail entries.

>>> audit-cleanup Command

Modification History

...

The audit trail is the history protocol of an object, serving to document its total entire lifecycle. There are many different actions that trigger the creation of a new entry in the respective object's audit trail. In this article, an overview of the different history codes is provided , that can occur in the audit trail.

History Codes

The GET "/dms/objects/{id}/history” REST endpoint returns a list of changes made to the object with the id ID {objectId}. The meanings of the individual history codes are listed in the table below.

...