Access control helps monitor the system. It is possible to keep record of
The according log entries are written into the user LogFile and can therefore be evaluated.
The auditing module (auditing.mod) in turn, is responsible for the access control. It is also used for data processing revision. The access control will be activated by sending the message "START_AUDITING_SILENT" and activated by parameter TRUE. It ends with the same message and with the parameter FALSE. Since the control mechanism should generally be valid for a complete session, it is recommended to execute the access directly in the project file *.CXP.
The auditing module defines which message to monitor. This definition should be made individually in the customer derivation. Once the module is active, it automatically becomes the receiver of all global messages (broadcasts). For the messages to be followed, it is necessary to define the according actions and to generate an equivalent protocol entry in the module.
The LogFile entry structure looks as follows:
<Date> <Time> <Process ID> INFO cx.app - <Log Entry>
The <Log Entry> is a string, which gets generated by the auditing module. Important for this entry is the use of keywords to execute a better evaluation afterwards. The log file entry for accessing sales item 123456 could look as follows:
<Date> <Time> <Process ID> INFO cx.app - MSG_AUDITING::EDIT_SALES_ITEM::123456