The dox42 Audit log

Prev Next

The dox42 Audit Log registers all processed dox42 reports.

You can access the dox42 Audit log by selecting System administration > Periodic tasks > dox42 Audit log.

Menu displaying system administration options including periodic tasks and dox42 audit log.

Path to dox42 Audit log

Dox42 audit log displaying various report types and their details in a table format.

dox42 Audit Log page

Description of log elements

Column

Description

Log type

See Log types.

Trace ID

One Report/Entity run creates several lines with the same Trace ID which are divided into different Log types.

Trace ID will be different in case of asynchronous archiving is enabled.

Cache enabled

Shows if the caching function was enabled for the Report/Entity run.

Log types

Log types used for reports

  • dox42 output processing – total execution of the dox42 logic

  • dox42 data serialization – serializing report’s data, it is a part of “dox42 output processing”.

  • dox42 print destination request – release to print destination (screen, file, printer, etc.), it is a part of “dox42 output processing”.

  • dox42 server call – interaction with dox42 Server, it is a part of “dox42 print destination request” or “dox42 archive processing”.

  • Printer: document routing – document routing processing (only when printing to a printer with “Document Routing Agent” active), it is a part of “dox42 print destination request”.

  • Printer: TIFF to EMF conversion – total execution of the conversion logic (only when printing to a printer with “Document Routing Agent” active and “Document routing mode” = “TIFF to EMF”), it is a part of “Printer: document routing”.

  • Printer: Unzip EMF files – total execution of the unzipping logic (only when printing to a printer with “Document Routing Agent” active and “Document routing mode” = “EMF), it is a part of “Printer: document routing”.

  • dox42 archive processing – total execution of the dox42 archiving logic, it is a part of “dox42 output processing” in case of synchronous archiving.

Log types used for data entities

  • dox42 output processing – total execution of the dox42 logic.

  • dox42 print destination request – release to print destination (screen, file, printer, etc.), it is a part of “dox42 output processing”.

  • dox42 server call – interaction with dox42 Server, it is a part of “dox42 print destination request”.

  • Printer: document routing – document routing processing (only when printing to a printer with “Document Routing Agent” active), it is a part of “dox42 print destination request”.

  • Printer: TIFF to EMF conversion – total execution of the conversion logic (only when printing to a printer with “Document Routing Agent” active and “Document routing mode” = “TIFF to EMF”), it is a part of “Printer: document routing”.

  • Printer: Unzip EMF files – total execution of the unzipping logic (only when printing to a printer with “Document Routing Agent” active and “Document routing mode” = “EMF), it is a part of “Printer: document routing”.

Dox42 audit log interface displaying log types and trace IDs for operations.

Log type dropdown

Available actions

Element

Description

Log details button

Opens the dox42 Audit log details page with a detailed audit log entry view.

Retry request button

Is available for log type - dox42 print destination request.

Parent log button

If you do the setup of archive setup (File server or SharePoint) in dox42 parameters for the report, extra lines per each archive process will be added in dox42 audit log.You will find the Trace ID of the initial run of the report (output processing).

Child log button

The same works vice versa with checking the Child log of the output processing.

Download data button

Downloads the raw report data in JSON format regardless of whether the report design was successfully generated or not.

dox42 Audit log displaying parent and child logs with trace IDs and statuses.

dox42 Audit log details page

dox42 audit log details showing data cache usage and report information.

dox42 Audit log details

Element

Data cache used

If set to Yes for dox42 data serialization log type: the data was not generated newly while report running but was taken from the cache.

Document cache used

If set to Yes for dox42 server call log type: the document was taken from the cache instead of sending a request to the dox42 Server.