The Update subsystem

The configuration should include a mechanism that automatically determines both the fact of the first launch of the configuration and performing the initial filling of the infobase with the minimum necessary data, as well as the fact of the first launch of a new release and making the necessary changes to the database.

According to the results of processing the information base, at the first launch of the configuration or at the first start of a new release of the configuration, the user should be presented with a report on the changes made to the information base. Situations where processing is not carried out in the required volume should be controlled by configuration. the user should be warned about a problem situation. To display a detailed protocol on the operations performed and errors encountered, use the eventlog.

The issue does not name files, tests, or entry points. Begin by locating the configuration startup and release-update processing, then determine how initial data filling, database changes, user reports, warnings, and eventlog output are currently handled. Done means the required first-launch and new-release behavior is defined and its incomplete-processing cases are controlled.