Directory "NomenclatureAttachedFiles" — Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. A service (technical) catalog for storing files attached to items in the “Item Catalog”: certificates, specifications, product photos, technical documentation, document scans. It is part of the standard mechanism “Attached Files” of the Standard Subsystems Library (BSP). The user does not create items manually through the menu — records are formed automatically when a file is uploaded/attached from the item card (the “Files” panel). Work with the contents of the files is done in the background.

According to the BSP agreement, a separate catalog of the form <Owner>AttachedFiles is created for each owner object that supports attached files; this catalog specifically serves the item catalog.

2. Attributes and Table Parts

2.1 Header Attributes

Additionally, the object has standard catalog attributes: Code, Name (file name), DeletionMark, Predefined, Reference. The Name stores the file name without the extension; the full name is assembled as Name + "." + Extension.

2.2 Table Part

ElectronicSignatures (standard BSP table part, when electronic signature usage is enabled) — stores information about the electronic signatures applied to the file: signer, signature date, certificate, verification status, the signature value itself (in storage). It is filled when signing the file from the form.

The actual binary content of the file is not stored in the attributes: when stored “in the information base,” it is placed in the service file storage (internal data of the object), when stored “on volumes” — in the file system at the path Volume + FilePath.

3. Forms

In practice, the user interacts not directly with these forms, but through the standard managed panel form “Attached Files” (CommonForm.AttachedFiles / the “Files” field in the item card), which is the client of this catalog.

4. Key Module Procedures

The Evidence with the original BSL text for the object is not attached. Below is the standard composition of handlers for the attached files catalog of BSP (implemented in the object module, manager modules, and form modules, as well as in the common modules of the “File Management” subsystem).

Object Module:

• BeforeWriting — setting UniversalModificationDate, recording the user in ModifiedBy, updating Size, Extension, indicators SignedByES/Encrypted.
• BeforeDeletion — deleting the binary content of the file in the volume (if storage is “on disks”), to avoid leaving “orphaned” files on the disk.
• FillingProcessing — setting Author, CreationDate, FileStorageType according to file storage settings upon creation.

Manager Module / Common Modules of the Subsystem (“FileManagement”, “FileManagementService”, “AttachedFiles”):

• Adding a file to the owner (creating an item, placing content in temporary storage/volume, calculating size and extension).
• Loan/return of the file for editing (filling/clearing the EditingUser attribute), blocking parallel modifications.
• Extracting text for full-text search and setting TextExtractionStatus, writing to TextStorage.
• Working with electronic signatures: signing, adding accompanying signatures, verifying signatures, encrypting/decrypting (managing SignedByES, Encrypted, table part ElectronicSignatures).

Element Form Module: handlers for viewing, opening, saving to disk, updating from file, printing signature information, as well as controlling file occupancy (EditingUser).

The exact composition of procedures and their signatures are version-dependent (determined by the BSP version within 3.0.74.2) — requires verification for a specific delivery during modifications.

5. Posting and Movements

The object is a catalog and is not posted — it does not generate registers and accounting entries. It has no posting mode, movements in accumulation/summary registers and in the accounting register are not created.

Changes when working with the file are limited to:

• recording/changing an item of this catalog;
• placing/removing binary content (in the information base or on the disk volume);
• updating service information for full-text search.

The file does not affect accounting indicators (VAT, cost, income). For reference: typical accounts of the RK affected by documents on the item (not by this catalog) — 1330 “Goods”, 1210 “Short-term Receivables from Customers”, 3310 “Payables to Suppliers”, 3130 “VAT Payable”, 6010 “Revenue from Sales”, 7010 “Cost of Sales”; the VAT rate of the RK for 2026 is 16%. An attached file (for example, a certificate or a scan of an electronic invoice (ESF)/SNT) serves only as an appendix to the item card and does not participate in these entries.

6. Related Objects and Input on Basis

Input on Basis is not provided for the service catalog. The creation mechanism is only through attaching a file to the item (uploading from disk, scanning, copying, drag-and-drop) in the “Files” panel. The file can be copied as attached to another object using standard BSP tools.

7. Extension Points

• Configuration Extension. Adding attributes to the element form, additional commands (for example, export by template), handlers BeforeWriting/BeforeDeletion through annotations &Before/&After.
• Common modules of the “File Management” subsystem. Configuring text extraction scenarios, restrictions on extensions and sizes of uploaded files, automatic signing.
• Storage Volumes (FileStorageVolumes). Transferring content “from the information base to volumes” and back to manage database size; configuring placement rules.
• Full-text search. Enabling/disabling text extraction and processing TextExtractionStatus.
• Electronic signature and encryption. Configuring cryptography programs, signing and verification policies (SignedByES, Encrypted, table part ElectronicSignatures).
• Additional attributes/information (BSP). Classifying files (document type, certificate validity period) through the properties mechanism.
• Data synchronization. The attribute UniversalModificationDate — a reference point during exchange; to be considered when configuring exchange plans.

When making modifications, do not change the purpose of service attributes (Author, CreationDate, FileStorageType, EditingUser) — the standard logic of blocking, storage, and auditing of BSP relies on them.