--- title: "Directory \"ExternalComponents\" — Technical Description (Accounting for Kazakhstan 3.0.74.2)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-vneshniekomponenty-tehnicheskoe-opisanie-buhg-en source: BuhGPT --- # Directory "ExternalComponents" — Technical Description (Accounting for Kazakhstan 3.0.74.2) > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name ExternalComponents Full Name Catalog.ExternalComponents ( Catalogs.ExternalComponents ) Synonym — (no separate synonym assigned; the section name "External Components" is used in the interface) Configuration Accounting --- 1. Identification Parameter Value Object Type Catalog Name ExternalComponents Full Name Catalog.ExternalComponents (Catalogs.ExternalComponents) Synonym — (no separate synonym assigned; the section name "External Components" is used in the interface) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Origin Service catalog of the BSP subsystem "Plug-in Components" (StandardSubsystems.Plug-inComponents) Purpose Centralized storage and version control of external components (ActiveX/COM, .dll/.so, Native API, browser plugins) necessary for the operation of configuration functions dependent on native code: cryptography and digital signatures, exchange with the ESF information system and STS, interaction with peripherals (scanners, cash registers, scales), specialized reporting mechanisms. Provides automatic updates from the 1C:ITS Portal and compatibility control with client platforms and browsers. Where to find in 1C: section "Administration" / "Standard Subsystems" → "Maintenance" → "External Components". Navigation link: e1cib/list/Catalog.ExternalComponents This is a service (technical) catalog. It does not participate in accounting and tax accounting, does not generate entries and movements in accounting registers. Tax rates, chart of accounts, and electronic documents of the RK are not directly related to this object — it only ensures the functionality of the mechanisms that use them (for example, connecting a cryptographic library for signing ESF/STS). 2. Attributes of Header and Table Parts 2.1 Header Attributes Name Type Mandatory Purpose Usage Enumeration.UsageOptionsForExternalComponents Fill (ShowError) Status of activity: used / disabled. Critical for automatic deactivation of old versions. Identifier String Fill (ShowError) Unique program identifier of the component (GUID or string name). Main key for searching and managing versions. Version String Fill (ShowError) Version number (for example, 1.2.3.45). Used for version control and determining relevance. VersionDate DateTime Do not check Release date of the version; determines which version is the latest. FileName String Do not check Original file name of the component upon upload (for example, component.dll). For display and reverse saving to file. ComponentStorage BinaryStorage Do not check Binary storage of the component file (binary data of the library for installation on client machines). UpdateFrom1CITS Boolean Do not check Auto-update flag from the 1C:ITS Portal. When installed, activates the logic for deactivating lower versions. ErrorDescription String Do not check Text of the last loading/installation error. For diagnosing compatibility issues. 2.2 Compatibility Attributes (Platform and Browser Flags) A group of boolean attributes describing which client environments this version of the component is suitable for. Automatically filled when loading from the component manifest. Name Purpose Windows_x86 Windows 32-bit (thin/thick client). Windows_x86_64 Windows 64-bit (thin/thick client). Linux_x86 Linux 32-bit (thin client). Linux_x86_64 Linux 64-bit (thin client). Windows_x86_Firefox / Linux_x86_Firefox / Linux_x86_64_Firefox Web client Firefox (NPAPI plugin) on the respective platforms. Windows_x86_MSIE / Windows_x86_64_MSIE Web client Internet Explorer on Windows. Windows_x86_Chrome / Linux_x86_Chrome Web client Chrome (Native Messaging / WebAssembly) on the respective platforms. The attribute Windows_x86_64_MSIE is present in evidence; some flags (macOS, additional browser bitness) may differ between releases of the 1C:Enterprise platform — requires verification in a specific version if a program analysis of the complete set of flags is performed. 2.3 Table Parts The catalog does not have its own application table parts. All information about platform support is included in the header attributes (see 2.2). Additionally, standard table parts of attributes are available, and if necessary, the mechanism of attached files of the BSP. 3. Forms Form Purpose ElementForm View and edit the component card: identifier, version, version date, supported platforms, update flag from ITS. From here, the component file is loaded into storage and unloaded back to file. ListForm List of registered components filtered by usage status and identifier; used by the administrator for review and maintenance. SelectionForm Service selection of the component during program calls. In the absence of explicitly overridden forms, the platform uses auto-generated ones. The main user work is not done directly with the card, but through the service forms of the BSP subsystem (component setup/update wizard). 4. Key Module Procedures In evidence, software modules (BSL) are not attached, so below are typical handlers and API of this type of object within the BSP subsystem "Plug-in Components". Catalog manager module / object module: - FillProcessing — initial initialization of the Usage status and compatibility flags when creating a new element. - BeforeSaving — when UpdateFrom1CITS is set and the version is current, deactivates lower versions of the same component (changing their Usage to "Disabled"), so that only one active version remains for each Identifier. - FillCheckProcessing — control of mandatory attributes Identifier, Version, Usage. Common modules of the subsystem (Plug-inComponents, Plug-inComponentsService, Plug-inComponentsClient/Server): - Registration of the component in the catalog based on the manifest data (filling Identifier, Version, VersionDate, platform flags, ComponentStorage). - Selection of the appropriate version for the current client environment (client type, OS, bitness, browser) based on compatibility attributes. - Connecting the component on the client (ConnectExternalComponent) with recording the error text in ErrorDescription upon failure. - Updating components from the 1C:ITS Portal based on the UpdateFrom1CITS flag. 5. Posting and Movements The catalog is non-posting and does not generate accounting entries and movements in accounting registers. It does not create records in accumulation/accounting registers (including the standard chart of accounts of the RK — 1210, 1030, 1330, 3310, 3130, 6010, 7010). Indirect participation in accounting processes — through the functionality provided: for example, the connected cryptographic component is used when forming and signing electronic documents ESF (ESF IS) and STS; failures in connecting the component lead to the inability to sign/send these documents. The actual movement in accounting is performed by the corresponding configuration documents, not this catalog. 6. Related Objects and Input Based On - Enumeration.UsageOptionsForExternalComponents — source of values for the Usage attribute. - BSP subsystem "Plug-in Components" — the main consumer of the catalog data (registration, selection, connection, updating). - Mechanisms using native components: cryptography and digital signatures, exchange with the ESF information system and STS, interaction with trade equipment/peripherals. - Scheduled/background task for updating components from the 1C:ITS Portal. Input based on for this object is not provided — records are created programmatically when loading/updating components or manually by the administrator in the list form. 7. Extension Points - Additional attributes and information (BSP) — for service classification of components without changing the configuration. - Program API of the subsystem — registration and connection of custom external components through Plug-inComponents (integration of third-party native libraries, for example, cash registers/fiscal registrars). - Overridable modules of the "Plug-in Components" subsystem — point for configuring the composition and rules for updating components. - Configuration extensions — adding attributes/handlers (BeforeSaving, FillCheckProcessing) without removing from support. - Attached files — if necessary, for storing accompanying documentation/manifests next to the catalog element. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_