The module is a 1C:Enterprise script program.
Modules are located at fixed points of the configuration and are invoked at predefined points of the 1C:Enterprise operation.
Configuring the system, the expert can use modules to describe complex algorithms of object interactions when the Designer does not provide adequate visual tools.
Form ModuleEach form has a module that describes its behaviour.
Object Module(each type of objects may have only one module). The module for catalogs, documents, reports, data processors, charts of characteristics, charts of accounts, charts of calculation types (registers have a record set module) is not snapped to the form and describes procedures related to an infobase object (e.g. printing, posting, input on basis).
In addition to modules ‘tied' to forms and objects, there are special modules.
The managed application module is located in the root partition of the configuration. It contains event-handling procedures that are initialized on system startup and shutdown with the run mode set to the Managed Application and Ordinary Application option in the configuration settings. The managed application module allows the declaration of variables, declaration and description of procedures and functions that will be available in any configuration module (except for the external connection module). They are also available for non-global shared modules with the Client (Managed Application) property selected. In the context of the managed application module you can also access exported procedures and functions of shared modules.
The external connection module is intended to accommodate texts of functions and procedures that may be called during an external connection session (the Export keyword is to be used).
The session module is a module that isexecuted automatically at the 1C:Enterprise startup upon the configuration restoration.
The session module is used to initialize session parameters and to drill session-related activities. The session module is sometimes executed in the privileged mode in the 1C:Enterprise server cluster.
It does not contain exported procedures and functions and can employ procedures from shared modules of the configuration.
The ordinary application module (there can be only one ordinary application module) is located in the root sector of the configuration and is executed automatically at the 1C:Enterprise startup upon the configuration restoration. It contains event-handling procedures that are initialized on the system startup and shutdown with the run mode set to the Ordinary Application option in the configuration settings. The application module contains procedures to be executed on 1C:Enterprise startup as well as global (exported) procedures that can be invoked from any other configuration module (except for shared modules). It is not displayed in the palette of the configuration root object properties if the Managed Application and ordinary Application option is selected in the configuration settings of the run mode.
In addition to procedures and functions, the application module can contain global variables accessible from any modules of the configuration.
Shared modules accommodate texts of functions and procedures that may be invoked from any other module of the configuration (the Export keyword is to be used). The Shared Modules branch of the configuration object tree is used for operations with shared modules.
Exported variables, procedures and functions of the application module are not available in shared modules.
Exported procedures and functions of shared modules can be accessed from other shared modules or from the application module.
Variables cannot be located in shared modules.