Business areas of use

• Primarily serves security purposes
• Detailed logging also makes it possible for the course of different procedures o to be traced back o to understand bottlenecks o to eliminate unnecessary iterations • Logging also enables the client to clarify the responsibilities and roles of the users in the system

Event log

The traditional event log stores events related to system operation, typically user activities, parameterizations. The event log is generated for IT professionals and it is stored in an SQL chart with the same structure as the Windows event log, with a time stamp.

The log stores:

• Log ins and log outs • System settings • Comprehensive search log • Special events • Menu launches • Comprehensive logs for parameterizations

Case log

The case log contains all the events related to a paricular case, data modifications, and history. The log module helps the work of end users, because the complete history of a case can be followed in it and documents can be searched specifically. The document log is stored in an SQL chart, with the user’s identification and time stamp.

Beside the event log, the case log is also a part of the product that enables the logging of document modification, editing, exporting, questionnaire modification, workflow forwarding, document creation, transfer books, parallelization, and data modification.

Service log

This service logs the course of other systems and internal services and it is typically evaluated if an error occurs. The service log supports the logging of Andoc’s internal and external system connections.