1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ВнешниеКомпоненты |
| Full name | Справочник.ВнешниеКомпоненты / Catalogs.ВнешниеКомпоненты |
| Synonym | "External Components" |
| Configuration | Trade Management for Kazakhstan, ed. 3.4.5.21 |
| Subsystem | Standard Subsystems (Standard Subsystems Library, SSL) → "External Components" |
| Where to find in 1C | "Standard Subsystems" section → "External Components". Direct navigation link: e1cib/list/Справочник.ВнешниеКомпоненты |
Purpose. A service catalog included in the SSL. Stores external components (add-in, native / COM) used by the configuration: the component file(s) and its metadata. The components are used by subsystems for working with retail equipment, cryptography/digital signatures, exchange with government information systems (ESF IS, SNT), scanning, etc. A catalog item is a "card" of a component installed in the infobase, from which the platform connects it on the client/server via ПодключитьВнешнююКомпоненту.
This is a technical (service) infrastructure object. It is not an object of operational or regulated accounting, does not store monetary amounts, and is not involved in tax calculation.
2. Header attributes and tabular sections
Header attributes
| Attribute | Type | Purpose |
|---|---|---|
Код |
String | Internal code of the catalog item. |
Наименование |
String | Component representation for the user. |
ИдентификаторОбъекта |
String | Programmatic component identifier (object name within the component archive) used for connection. |
ПолноеНаименование / Назначение |
String | Detailed description of the component's purpose (which task it is used for). |
Версия |
String | Version of the loaded component (filled from the manifest during loading). |
ЭтоРасположениеВнешнейКомпонентыВМакете |
Boolean | Flag: the component is delivered in a configuration template rather than stored as an attached file. |
ИмяМакета |
String | Configuration template name, if the component is taken from a template. |
Удалить* / ПометкаУдаления |
Boolean | Service/standard catalog attributes. |
Storage of binary content
The component file (usually a ZIP archive with a MANIFEST.XML manifest and binary files for various platforms/bitness) is not stored in an attribute, but through the SSL's attached files mechanism. The file owner is a subordinate catalog:
Справочник.ВнешниеКомпонентыПрисоединенныеФайлы— attached files of a specific component (binary data in volumes/database), attributes:ВладелецФайла,ХранилищеФайла/link to volume,Расширение,РазмерФайла,ДатаМодификацииУниверсальная,ВерсияФайла, etc.
The catalog has no separate tabular section with business data; if present in a specific version, a service compatibility tabular section is used (a list of supported platforms/bitness) filled in automatically from the manifest.
3. Forms
| Form | Purpose |
|---|---|
Item form (ФормаЭлемента) |
Component card: name, object identifier, version, "from template" flag, management of the attached file (upload/replace/download). |
List form (ФормаСписка) |
List of registered components; used to run commands for loading a new component and updating. |
Selection form (ФормаВыбора) |
Selecting a component for other objects/data processors. |
| SSL service forms | External component loading/update wizard (manifest, bitness, version check) — called from the subsystem's common modules. |
If specific forms are not defined in a given release, the platform uses auto-generated catalog forms.
4. Key module procedures
No applied BSL evidence for the modules is attached (the source contains only the "purpose" facet). Below are typical handlers and logic points for this type of object in the SSL; verify specific procedure names against release 3.4.5.21.
Object module / catalog manager module:
ОбработкаЗаполнения— initialization of a new item.ПередЗаписью/ПриЗаписи— validation ofИдентификаторОбъекта, version update.ОбработкаПроверкиЗаполнения— check of required attributes (name, identifier) and presence of the attached file.
Subsystem common module (SSL server logic, e.g. ВнешниеКомпоненты/ВнешниеКомпонентыСлужебный):
ПодключитьВнешнююКомпоненту(...)— connect a component by catalog reference or identifier (client/server), taking caching into account.ЗагрузитьВнешнююКомпоненту(...)/ОбновитьВнешнююКомпоненту(...)— load a ZIP archive, parse the manifest, record the version and attached file.ПроверитьПодключениеВнешнейКомпоненты(...)— diagnostics of component availability on the current platform/bitness.- Functions for retrieving the location — return the address from a template (
ЭтоРасположениеВнешнейКомпонентыВМакете = Истина) or from the attached file.
5. Posting and movements
The catalog is not posted and does not generate movements in registers, nor does it generate accounting entries. A "Catalog" type object has no posting mechanism; changes affect only the tables of the catalog itself and the subordinate attached files catalog.
Kazakhstan planned/tax indicators do not apply to this object. For reference, the correct Kazakhstan-2026 parameters used in the configuration's operational and regulated documents (sales, receipts, ESF/SNT, payroll) are given below, but are not used in this service catalog:
- VAT — 16% (standard 2026 rate).
- MCI = 4,325 ₸, minimum wage = 85,000 ₸.
- Individual income tax (IIT): base deduction of 30 MCI/month (no more than 360 MCI per year); rate 10% up to 8,500 MCI of annual income and 15% above.
- Mandatory pension contributions (MPC) 10% (base cap — 50 minimum wages), MPCE 3.5%, OSMS (employee) 2%, OSMS (employer) 3%, social contributions 5%, social tax 6%.
- Standard Kazakhstan chart of accounts for trade operations: 1210 (short-term accounts receivable from customers), 1030 (cash at current accounts), 1330 (goods), 3310 (accounts payable to suppliers), 3130 (VAT payable), 6010 (revenue from sales), 7010 (cost of sales).
- Electronic documents: ESF (ESF IS), SNT. Accounting currency — tenge (₸).
These values represent the platform context where postings actually occur; the "ВнешниеКомпоненты" catalog itself is not involved in them.
6. Related objects and input based on
Справочник.ВнешниеКомпонентыПрисоединенныеФайлы— a subordinate catalog storing binary component files (owner — the "ВнешниеКомпоненты" item).- Common modules of the SSL "External Components" subsystem — connection/loading API.
- Consumer subsystems: working with retail equipment, cryptography and digital signatures, integration with ESF IS and SNT, barcode scanning — access the catalog to connect the needed component by identifier.
- SSL information registers for settings of connected equipment/services referencing the component.
Input based on is not provided for this catalog by the standard configuration: items are created manually or programmatically when a component is loaded.
7. Extension points
- Loading a custom component: adding your own item with a ZIP archive (manifest + binaries for the required platforms/bitness) and connecting via the subsystem's API by
ИдентификаторОбъекта. - Configuration extension: adding card attributes (e.g., links to documentation, responsible person, usage environments) and subscriptions to the
ПередЗаписью/ОбработкаПроверкиЗаполненияevents without removing the object from support. - Wrappers over the connection API: a custom common module on top of
ПодключитьВнешнююКомпонентуfor centralized logging and connection error handling. - Rights and access profiles: configuring roles for modifying the catalog — access to loading/updating components is usually restricted to the administrator.
Requires verification in release 3.4.5.21: the exact procedure names of the "External Components" subsystem's common modules and the composition of service compatibility attributes by platform — these are version-dependent in the SSL.