New audit logging (#661686)
The audit logging of the administrative actions which are performed in the Web Admin Suite has been improved. Now, for every configuration change, both the previous and the new values are logged in a human-readable format. Therefore, the audit.log file allows to easily track all configuration changes because it is visible at a glance what someone changed.
Example log entry for a change of the phone number of a user on the Users page:
2026-03-19 09:29:46,519 INFO [admin--9017524b-ab46-41b5-9752-4bab4681b52f] updateEngineer [16474][bauer] Changes: [Phone]: [966698] -> [123456]
For changes to script and template content, the audit.log will contain a diff so that the administrator can see which lines have been added, modified or removed. This diff contains the changes plus 3 lines of context before and after the changed lines. Example:
2026-03-31 11:54:30,769 INFO [admin--2edc8c2e-142b-4240-9c8c-2e142b82409e] ScriptSource.update [5536] [Content change summary]: [blocks=1, +1/-1, blocks ranges=[8-8->8-8], changedLines=[old:[8] -> new:[8]]][Diff]: [--- old/AddAttachment
+++ new/AddAttachment
@@ -5,7 +5,7 @@
def ticket = ticketService.getByCriteria(ticketCriteria).get(0);
byte[] bytes = "This is test attachment content".getBytes();
AttachmentEntry entry = new AttachmentEntry();
- entry.setDescription("attachment added by a task");
+ entry.setDescription("attachment added for testing");
entry.setEncoding("utf-8");
entry.setMimeType("text/plain");
entry.setFile(new ContentFile("fileName", new ByteArrayInputStream(bytes), bytes.length));]
For workflows, only the basic actions, such as creating or editing a workflow or modifying localized names are logged. The changes performed inside the workflow itself are not part of audit logging due to their complexity. As workflows are versioned, the changes can be tracked by comparing the respective workflows directly.
Log entries related to ETL Runner are written to the regular audit.log if ETL Runner is deployed in the application server. If ETL Runner is executed in standalone mode, the logs are written to the etl-runner.log in the directory of the JAR file.
You need to update the XML configuration files for this change to become effective.