---
title: "Directory \"Organization Units Attached Files\" — Technical Description"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/spravochnik-podrazdeleniyaorganizaciyprisoedinennyefayly--en
source: BuhGPT
---

# Directory "Organization Units Attached Files" — Technical Description

> **TL;DR:** ```html 1. Identification Parameter Value Object Type Catalog Name OrganizationDepartmentsAttachedFiles Full Name Catalog.OrganizationDepartmentsAttachedFiles Synonym — (service object, not displayed as a separate list in the command interface) Configuration Accounting for Kaz

---

```html
1. Identification

Parameter
Value

Object Type
Catalog

Name
OrganizationDepartmentsAttachedFiles

Full Name
Catalog.OrganizationDepartmentsAttachedFiles

Synonym
— (service object, not displayed as a separate list in the command interface)

Configuration
Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2)

Subsystem
Working with attached files (BSP — "Attached Files")

Owner
Catalog.OrganizationDepartments

Where to find
e1cib/list/Catalog.OrganizationDepartmentsAttachedFiles

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)

Name
Type
Mandatory
Purpose

Author
Catalog.Users
Mandatory (ShowError)
The user who uploaded the file. Audit and access control. Automatically filled in upon creation.

FileOwner
Catalog.OrganizationDepartments
Optional
The department to which the file is attached. Determines access rights through RLS.

UniversalModificationDate
DateTime
Optional
Universal (UTC) time of the last modification of the file. For synchronization and tracking changes.

CreationDate
DateTime
Mandatory (ShowError)
The moment the file is uploaded to the system. Automatically filled in.

Encrypted
Boolean
Optional
Indicator that the file is encrypted (works in conjunction with encryption certificates).

ModifiedBy
Catalog.Users
Optional
The user who last modified the file or its metadata.

ImageIndex
Number
Optional
The index of the file icon in the interface (depends on the file type).

Description
String
Optional
Text description of the file entered by the user.

SignedEP
Boolean
Optional
Indicator of the presence of an electronic signature on the file.

FilePath
String
Optional
Path to the file on the disk (for storage "On disk in specified volumes").

Size
Number
Optional
Size of the file in bytes.

Extension
String
Optional
File extension (pdf, docx, etc.). Determines available actions.

EditingBy
Catalog.Users
Optional
The user who has locked the file for editing (the "locking" mechanism).

TextExtractionStatus
Enumeration.TextExtractionStatuses
Optional
Status of text extraction for full-text search (not extracted / extracted / error).

TextStorage
ValueStorage
Optional
Extracted text from the file for full-text search.

FileStorageType
Enumeration.FileStorageTypes
Mandatory (ShowError)
Storage method: in the database or on disk. Affects the use of FileStorage/FilePath.

Volume
Catalog.FileStorageVolumes
Optional
Volume (folder on disk) for storage when the type is "On disk".

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

Name
Type
Purpose

FileStorage
ValueStorage
Binary content of the file when stored "In the database".

VersionNumber / CurrentVersion
Number / CatalogReference.<...>VersionsOfAttachedFiles
Indicator and reference to the current version (if the versioning mechanism is enabled for the object).

UploadedFile, ElectronicSignature
service
Technical fields for exchange/signature.

Standard: Code, Name, DeletionMark, Predefined, Reference
—
Standard attributes of the catalog. Name = file name without extension.

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:

Form
Type
Purpose

Element Form (auto/general)
Element
View and edit metadata of a single file: description, author, dates, size, signature/encryption indicators. Usually opened only for service purposes.

List Form (auto)
List
Technical list of all files in the catalog. Not used directly in the user interface.

CommonForm.AttachedFiles
General
Main working interface: list of files attached to the department with commands "Add", "Open", "Edit", "Save", "Sign EP", "Encrypt", "Versions".

CommonForm.AttachedFile
General
Card of a single attached file for viewing properties and working with versions/signatures.

CommonForm.FileTypeSelectionFormForCreatingElectronicSignature and others
General
Service forms for signing/encryption and volume selection.

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

Relation
Object
Nature of Relation

Owner
Catalog.OrganizationDepartments
Each file refers to the department through FileOwner; determines RLS access.

Author / ModifiedBy / EditingBy
Catalog.Users
Audit and editing lock.

Storage on Disk
Catalog.FileStorageVolumes
Through the attribute Volume and path FilePath.

Storage Type
Enumeration.FileStorageTypes
"In the information base" / "In volumes on disk".

Text Extraction
Enumeration.TextExtractionStatuses
Management of full-text search.

Versions
subordinate catalog of versions of attached files
History of content (if the versioning mechanism is enabled).

Electronic Signature / Encryption
subsystem of electronic signatures, Catalog.CertificateKeyStorageEP
Indicators SignedEP, Encrypted
```

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_