Directory "Organization Units Attached Files" — Technical Description

1. Identification

Purpose. A technical catalog for storing files attached to elements of the "Organization Departments" catalog (scanned copies of orders for the creation of a department, regulations, lease agreements, photographs, etc.). This is one of many similar catalogs <Owner>AttachedFiles, automatically generated by the BSP's attached files mechanism for each owner object.

The user interacts with the object indirectly — through the "Attached Files" command (or file panel) in the department card. The first element of the catalog is created automatically when the first file is added to a specific department. The catalog stores both the file content (in the database or on disks) and its metadata: author, dates, size, version, signature/encryption indicators.

Access to files is restricted through RLS by the attribute FileOwner: the user sees and edits the file only if they have rights to the owner department. This is critical for compliance with information security policies.

The accounting currency of the configuration is tenge (₸). This financial performance object does not store; RK parameters (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, etc.) do not affect it and are provided in the sections below only for the context of related accounting objects.

2. Header Attributes and Table Parts

2.1 Header Attributes (from evidence)

There are also standard attributes of the BSP mechanism (not included in the evidence fragment but mandatory for this type of object):

2.2 Table Parts

The object does not contain its own application table parts. Versioning (history of content changes) is implemented not by a table part, but by a separate subordinate catalog of versions, if the versioning mechanism for the owner is enabled.

3. Forms

For service catalogs of attached files, forms are generally not overridden and are inherited from the common BSP mechanisms. Work is conducted through the common forms of the subsystem:

If specific delivery for the object specifies its own ElementForm/ListForm, they duplicate the functionality of the common forms — version-specific, requires verification in the specific configuration 3.0.74.2.

4. Key Procedures of Modules

Application BSL code (evidence with paths module:string) is not attached, so below are typical handlers for this type of object, implemented by the BSP's attached files mechanism.

Object module / manager module:

• BeforeWriting(Refusal) — control of filling mandatory attributes (Author, CreationDate, FileStorageType); if values are empty — set Refusal = True (ShowError behavior). Auto-fill ModifiedBy and UniversalModificationDate.
• BeforeDeleting(Refusal) — when FileStorageType = OnDisk deletes the physical file from the volume, frees up occupied space, cascades version cleanup.
• FillingProcessing(FillingData) — sets Author, CreationDate = CurrentSessionDate(), default values for FileStorageType.

Common programming interface (modules FileOperations, FileOperationsService, FileOperationsServiceServerCall):

• AddFile(...) — creates a new element of the catalog, writes content to FileStorage (in the database) or to the volume (FilePath, Volume), calculates Size, Extension, ImageIndex.
• UpdateFileVersion(...) / CreateVersion(...) — fixes a new version of the content.
• LockFileForEditing(...) / UnlockFile(...) — manages the EditingBy attribute (the "locking" mechanism).
• SignFile(...), EncryptFile(...), DecryptFile(...) — sets the indicators SignedEP, Encrypted and works with certificates.
• ExtractFileText(...) (scheduled task "Extracting text from files") — fills TextStorage and sets TextExtractionStatus for full-text search.

5. Conducting and Movements

The catalog is not a document and is not conducted — it does not generate movements in accumulation/information registers and accounting entries. This is a service storage of files; its records do not participate in accounting, tax, and operational records.

Indirectly, the object is involved only in service registers of the file subsystem, for example:

• InformationRegister.StoredFileSizes (accounting for storage volume in volumes) — if the volume mechanism is enabled;
• full-text search mechanisms (by TextStorage).

For context: accounting entries in the configuration are generated by sales/purchase documents, not this catalog. According to the standard chart of accounts of the RK, this is, for example: Dr 1210 Cr 6010 — revenue from sales; Dr 3130 — VAT payable at the rate of 16%; Dr 7010 Cr 1330 — write-off of the cost of goods; Dr 1030 Cr 1210 — receipt of payment; Dr 3310 — settlements with suppliers. The attached files of departments are not directly related to these entries — the file can only be a scanned copy of the primary document that generated the entry.

6. Related Objects and Input on Basis