1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | ExtensionVersions |
| Full Path | Catalogs.ExtensionVersions |
| Alias | — (no separate alias assigned; used in the interface as "Extension Versions") |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Subsystem | Standard subsystems (BSP) → "Update IB Version" mechanism / working with extensions |
| Purpose | Service catalog for managing the versions of configuration extensions. Automatically tracks the composition of installed extensions at session start, records their state (name, version, checksum), and creates version records. Ensures consistency when working with split data and controls dynamic changes in the composition of extensions. |
Usage Characteristic: the object is service-oriented, managed by the system (BSP), not by the end user. It does not participate in accounting/tax records, does not store financial data, and does not generate entries. Access to elements occurs at session start, during installation/deletion of extensions, and through a scheduled task to clear outdated parameters.
Where to find in 1C: section "Administration" / service mechanisms → "Extension Versions".
Navigation link: e1cib/list/Catalog.ExtensionVersions
2. Header Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| MetadataDescription | xs:string (String) | DontCheck | Stores the serialized description of the composition of installed extensions (names, versions, checksums). Used for identifying the unique combination of extensions and comparing the current state of the system with previously recorded data. |
| LastUsedDate | xs:dateTime (Date) | DontCheck | Records the moment of the last access to this version of extensions. Used during the automatic cleanup of outdated versions: the operational parameters of versions that have not been used for a long time are deleted by a scheduled task. |
Standard Attributes:
| Attribute | Purpose |
|---|---|
| Code | String identifier of the version, displayed in the item form. |
| Name | Not actively used — versions are identified by the attribute MetadataDescription. |
| DeletionMark / Predefined / Reference | Standard system attributes of the catalog. |
2.2 Table Parts
The catalog does not contain table parts. The entire composition of extensions is stored in the attribute MetadataDescription as structured (serialized) text.
3. Forms
| Form | Purpose |
|---|---|
| ItemForm | Form of the catalog item. Contains fields for viewing and editing Code, MetadataDescription, and LastUsedDate. By default, fields are read-only (data is managed by the system); includes the command "EnableEditing" for administrative changes. |
| ListForm | Form of the list of extension versions. Displays all registered versions in tabular form. Contains the command "EnableEditing" for administrative access. Main user form, but rarely opened — usually by administrators for diagnostics. |
4. Key Module Procedures
The attached evidence does not contain the original BSL code with the binding
path:string, therefore below are typical handlers for the service catalog of this type (BSP mechanism "Working with Configuration Extensions"). Specific procedure names in version 3.0.74.2 require verification with the modules — version-specific.
Module of Forms (ItemForm / ListForm):
OnCreateOnServer— when opening the form, sets the "read-only" property for the fieldsMetadataDescriptionandLastUsedDate, hides service details.EnableEditing(Command)— removes the "read-only" lock from the fields for administrative editing; accompanied by a warning about the service nature of the data.
Typical Server Mechanisms (manager module / common BSP modules):
- Registration of the current version of extensions at session start: the system generates a description of the composition of extensions, searches for the corresponding element by
MetadataDescription, if absent — creates a new one, if present — updatesLastUsedDate. - Scheduled cleanup: deletion of elements whose
LastUsedDatehas exceeded the established storage period (operational parameters of unused versions are deleted).
5. Posting and Movements
The catalog is not a document and is not posted. It does not generate movements in accounting registers, accumulations, or information and does not create accounting entries.
For comparison — accounting accounts of the typical chart of accounts of the RK, which in this object are not involved and are provided solely as a reference for the applied contour (the catalog itself does not refer to them):
| Account | Purpose |
|---|---|
| 1210 | Short-term accounts receivable from customers |
| 1030 | Cash in current bank accounts |
| 1330 | Goods |
| 3310 | Short-term accounts payable to suppliers |
| 3130 | VAT payable |
| 6010 | Income from sales of goods and services |
| 7010 | Cost of goods and services sold |
Accounting and tax parameters of the RK configuration for 2026 (VAT rate 16%, MRP 4,325 ₸, MZP 85,000 ₸, PIT 10%/15%, OPE 10%, OPR 3.5%, WOSMS 2%, OSMS 3%, CO 5%, social tax 6%) are implemented in applied documents and registers; they have no relation to the service catalog ExtensionVersions.
6. Related Objects and Input on Basis
- Input on Basis — not provided and not applied (service object).
- Related Mechanisms: BSP subsystem "Working with Configuration Extensions", data splitting mechanism, scheduled tasks for cleaning outdated versions.
- References from Other Objects: catalog elements are used by internal mechanisms of the platform/BSP to match the state of extensions; applied documents of the configuration do not refer to it.
7. Extension Points
- Form Handlers (
OnCreateOnServer, commandEnableEditing) — can be overridden in the extension to change the logic of access to editing. - Additional Attributes/Information — can be added through the mechanism "Additional Attributes and Information", however, for a service object, this is not recommended.
- Scheduled Cleanup — the storage period of unused versions can be configured by BSP logic; behavior change is possible through subscription/override of the corresponding scheduled task.
Important: this is a service catalog of the platform-library mechanism. Manual editing, adding, and deleting elements outside of administrative diagnostics is not recommended — data is managed by the system automatically.