TECHNICAL Sign up Sign in EN


Logging is the main tool for parsing what happened. They show who, what, what, when changed, added, or deleted. All information is stored for any changes. ERP-Platform has 2 types of logging:
  • Local
  • Global

Local Logs

This type of logs is configured individually in each module using the appropriate configuration programming. They can be created in the usual way by creating triggers, creating inference procedures, storage tables, interfaces, etc. This method is possible but somewhat costly.
Therefore, in the process of development, the creation of logs was automated as a typical task, and there is a special form of configuration for logs. For automated creation of logs you need:
  1. Create a log table based on the original table (which needs to be logged). The system will automatically create NEW and OLD fields for each field of the source table, as well as build all system links with the source table.
  2. Create a LOG form, link it to the desired table and display it in the right place in the interface
  3. Create a trigger for logging through a special procedure. You only need to specify the source table and the log table. The trigger will be created automatically.

System Logs

There are also system logs. These are deep system logs that everyone writes. Any actions on any table will be reflected in them. The purpose of system logs is to sort out mysterious situations, for example, when employees claim that they did not do anything and it happened by itself.

In the table configurator, you can click on the "Connect system logs" button. From that moment on, absolutely all changes that took place in it will be written in the configurator using this table, regardless of the programs.

Also, in a special module, you can configure the storage mode of these logs in days, enable or disable the system as a whole, as well as look at the details of the changes according to the required table.

Technically, the system logs are arranged as follows:
  • There are 2 log tables. Recording packet table and data table.
    - Package table - written where, who and when changed. Those. who performed the operation and which one. Package data is never deleted.
    - Data table - data on the packet is recorded, what has changed and what has changed within the operation. This data can be quite voluminous, therefore, after the specified number of days, they are deleted.
  • When connecting the table to the system logs, a trigger is automatically created that writes change packages and data to these packages.