From bc3b59e744aa6f023a9d34c93d41408abb2286a9 Mon Sep 17 00:00:00 2001 From: Ralph Soika Date: Wed, 5 Jun 2024 11:57:14 +0200 Subject: [PATCH] docu --- src/site/markdown/archive/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/markdown/archive/index.md b/src/site/markdown/archive/index.md index 7456c154..6a6e224a 100644 --- a/src/site/markdown/archive/index.md +++ b/src/site/markdown/archive/index.md @@ -6,7 +6,7 @@ Imixs-Office-Workflow provides you with the functionality of an audit-proof arch You ensure audit-proofing yourself through the workflow model. Every workflow model should have at least one final workflow status where no changes (events) can occur. This prevents users from making retrospective changes to data. - + The audit log is generated through the workflow history, which you also define via modeling. Additionally, the workflow system has a technical audit log that cannot be influenced. These data are fixed in the item '$eventlog'.