GISMP Attached Files Directory — Technical Description

1. Object Identification

Purpose. The catalog is a service storage for attached files of objects belonging to the exchange subsystem with GISM (State Information System for Marking and Traceability of Goods). It stores exchange protocol files, XML/JSON packages, receipts, service responses, and arbitrary attachments linked to an owner object (a document or item of a GISM exchange catalog). The catalog is created automatically by the SSL "Attached Files" wizard for a specific owner and is not maintained manually by the user as an independent list.

Attached files are not an accounting object: it is not involved in inventory, monetary, or tax calculations and does not generate movements (see section 5). All numeric and tax rules of Kazakhstan-2026 (VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸) do not apply to it — they relate to the accounting documents to which the files are merely attached.

Where to find: e1cib/list/Справочник.ГИСМПрисоединенныеФайлы

2. Attributes and Tabular Sections

The attached files catalog has no tabular sections. Below is the standard set of attributes generated by the SSL for objects of the "AttachedFiles" type.

2.1. Standard Attributes

2.2. Header Attributes (Application-Level)

The specific set depends on whether file versioning, digital signature, and encryption are enabled for this owner in the "File Operations" subsystem settings. (The presence of version attributes is version-dependent, to be clarified for configuration 3.4.5.21.)

3. Forms

The main work with attachments is not carried out through the catalog's own forms, but through the common forms of the "File Operations" subsystem:

• ОбщаяФорма.ПрисоединенныеФайлы (CommonForm.AttachedFiles) — a panel/list form of attached files embedded in the owner's form;
• ОбщаяФорма.ПросмотрФайла (CommonForm.FileView), ОбщаяФорма.РедактированиеРеквизитовФайла (CommonForm.FileAttributesEdit), ОбщаяФорма.ВыборРежимаОткрытияФайла (CommonForm.FileOpeningModeSelection) — service forms for viewing, editing properties, and selecting the opening method.

4. Key Module Procedures

No separate BSL evidence is attached for the object's modules, so below is the typical set of handlers characteristic of SSL attached files catalogs. The main logic is placed in the common modules of the "File Operations" subsystem.

Object/manager module:

• ОбработкаЗаполнения (FillingProcessing) — initializes the author and creation/modification dates when a file is created.
• ПередЗаписью (BeforeWrite) — updates ДатаИзменения (ModificationDate), ВерсияОтпечаток (VersionFingerprint), and controls the edit lock.
• ПередУдалением (BeforeDelete) — deletes the associated file from the volume (ТомХранилищаФайлов / ПутьКФайлуТома) upon physical deletion.

SSL common modules (actual business logic):

• РаботаСФайлами / РаботаСФайламиКлиент (FilesOperations / FilesOperationsClient) — opening, editing, saving, checking out/releasing a file.
• РаботаСФайламиСлужебный, РаботаСФайламиСлужебныйСервер (FilesOperationsInternal, FilesOperationsInternalServer) — adding a file, creating versions, extracting binary data from ХранениеФайла or the volume.
• РаботаСФайламиВызовСервера (FilesOperationsServerCall) — server calls for adding/updating attachments.
• The "Attached Files" mechanism — mapping the owner to its file catalog (ГИСМПрисоединенныеФайлы).

GISM application layer: writing exchange protocol/receipt files is performed by procedures of the GISM integration modules, which call SSL methods, passing the owner (the document or exchange object) and the binary package data. (The exact names of GISM procedures are version-dependent for 3.4.5.21.)

5. Posting and Movements

The catalog is not a document and is not posted. It does not generate:

• accumulation registers (inventory, mutual settlements, sales);
• accounting registers or accounting entries under the Kazakhstan chart of accounts.

The only "data movement" is the writing/deletion of the file's binary content: either into the ХранениеФайла attribute (inside the infobase), or into a volume file on disk (ТомХранилищаФайлов + ПутьКФайлуТома), plus registering a version in the file versions information register when versioning is enabled.

Accounting entries are generated by the owner documents to which these files are attached, not by the catalog itself. For reference, the relevant accounts of the standard Kazakhstan chart of accounts used by such documents (sales, receipt, payment):

Electronic documents related to the circulation of marked goods (ESF in the ESF IS, SNT) also belong to the owner documents, not to this catalog.

6. Related Objects and Input Based On

• File owner — a document or catalog item of the GISM exchange subsystem (objects of integration with the marking system). A file is created exclusively in the context of its owner.
• Справочник.ТомаХранилищаФайлов (Catalog.FileStorageVolumes) — volumes for file storage outside the infobase.
• Справочник.Пользователи (Catalog.Users) — the Автор (Author) and Редактирует (BeingEditedBy) attributes.
• File versions/binary data information register — when versioning is enabled.
• Input based on — not provided: items are generated programmatically by the attached files mechanism, not by the "Create based on" command.

7. Extension Points

• "File Operations" subsystem settings: enabling versioning, volume storage, digital signature, and encryption affects the composition of attributes and behavior.
• Configuration extensions: subscribing to the ПередЗаписью/ПередУдалением (BeforeWrite/BeforeDelete) events of the object module, adding attributes via an extension.
• SSL common modules (РаботаСФайламиПереопределяемый, РаботаСФайламиКлиентСервер — FilesOperationsOverridable, FilesOperationsClientServer) — procedures for overriding file processing.
• GISM application procedures — the point for embedding logic for auto-saving exchange packages/receipts into attached files.
• Storage settings (ТомаХранилищаФайлов — FileStorageVolumes, size/extension restrictions) — configured by the administrator without changing code.