1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ВерсииРасширений |
| Full name | Справочник.ВерсииРасширений / Catalogs.ВерсииРасширений |
| Synonym | "Extension Versions" |
| Configuration | Trade Management for Kazakhstan, ed. 3.4 (3.4.5.21) |
| Where to find | e1cib/list/Справочник.ВерсииРасширений |
| Purpose | A service catalog of the Standard Subsystems Library (SSL). Stores a registry of connected configuration extensions and the versions for which data update handlers have already run. Used by the "Infobase Version Update" mechanism to launch extension update handlers when their version changes. |
This is a technical (service) object. It is not intended for manual maintenance by the user and is not related to master data, items, mutual settlements, or taxes. In the user interface it is generally hidden and accessible only to the administrator/developer.
2. Header attributes and tabular sections
The catalog has no hierarchy and contains no tabular sections. Standard and application attributes:
| Attribute | Type | Purpose |
|---|---|---|
Код |
String/Number | Standard item code. Service field, has no meaningful content for the user. |
Наименование |
String | Description of the extension (extension name). |
ПометкаУдаления |
Boolean | Standard deletion mark flag. |
ИдентификаторРасширения |
String / UUID | The extension's GUID, by which it is uniquely identified in the infobase. The key linking the catalog record to a specific connected extension. |
ХешСумма / КонтрольнаяСумма |
String | Hash (checksum) of the extension's contents. When the hash changes, the update mechanism recognizes that the extension has changed and the handlers need to be run again. |
ВерсияРасширения |
String | Extension version in X.X.X.X format, recorded at the time of the last successful data update. |
Requires verification: the exact set of application attributes and their names are version-specific and depend on the SSL edition built into 3.4.5.21. In some releases the version/hash are stored not as catalog attributes but in a related information register — check in Designer. The catalog attributes contain no accounting, pricing, or tax information.
3. Forms
As is typical for a standard service object, custom (overridden) forms are usually not created — auto-generated ones are used:
| Form | Purpose |
|---|---|
| List form (auto) | Viewing the registry of extensions and their recorded versions by the administrator. |
| Item form (auto) | Viewing the attributes of a specific record. Manual editing is not intended. |
| Selection form (auto) | Programmatic selection of an item from service code (practically not used in interactive scenarios). |
4. Key module procedures
No BSL evidence was provided for this object (the source data only contains the "purpose" facet), so below are typical handlers for this type of object and the SSL mechanism it participates in. Check the exact module lines in Designer.
- Catalog manager module — procedures for registering/updating extension records: finding an item by
ИдентификаторРасширения, creating it if absent, writing the currentВерсияРасширенияandХешСумма. - "Infobase Version Update" mechanism (SSL) — common modules
ОбновлениеИнформационнойБазы,ОбновлениеИнформационнойБазыСлужебныйand the related extension update handler: at session start they compare the current version/hash of each connected extension with the one stored inВерсииРасширений, and if there is a discrepancy, they initiate the extension's data update handlers. - Operation in safe mode — access to extension data is performed through standard SSL mechanisms (
РаботаВБезопасномРежиме), without direct interactive user operations. - Standard object/form handlers (
ПередЗаписью,ОбработкаЗаполнения) — used in minimal, standard scope; contain no application logic for posting/calculations.
5. Posting and movements
The catalog is not a document: it has no "Posted" attribute, it does not generate register movements, and it does not create entries in the chart of accounts.
As a result, the accounting and tax parameters of the configuration (VAT rate 16%, MCI 4,325 ₸, minimum wage 85,000 ₸, personal income tax deduction of 30 MCI/month, personal income tax rates of 10%/15%, mandatory pension contributions, mandatory professional pension contributions, VOSMS, OSMS, social contributions, social tax), as well as the standard chart of accounts for Kazakhstan (1210, 1030, 1330, 3310, 3130, 6010, 7010) and electronic documents (ESF/SNT) are not applicable to this object. These values relate to accounting documents and configuration registers, not to the service catalog of extension versions.
"Movement" of this object in the narrow sense is only the service-level recording of the fact that the update handlers for the extension with a given identifier have run on the specified version/hash.
6. Related objects and creating based on
- SSL "Infobase Version Update" subsystem — the main consumer of the catalog's data.
- Configuration extensions (platform mechanism) — the source of identifiers, versions, and hashes reflected in the catalog.
- "SubsystemVersions" information register and update handlers (
ОбновлениеИнформационнойБазы...) — work together with this catalog during data updates.
Creating based on: not applicable, either as a source or as a result. Interactive creation of items by the user is not performed in the standard scenario — records are maintained by the update mechanism.
7. Extension points
- Modifying this service catalog with custom extensions is not recommended: the object belongs to the SSL infrastructure, and interference could disrupt the extension data update mechanism.
- Acceptable (careful) options: subscribing to events and manager module handlers via a custom extension — only for diagnostics/logging, without changing the version-recording logic.
- Application business logic (accounting, taxes, ESF/SNT) should be placed in the corresponding documents and configuration registers, not in this object.