Directory "FileFolders" (Catalogs.FileFolders) — Technical Description

1. Identification of the object

Purpose. The catalog implements a hierarchical “file system” within the information base: users create folders and subfolders for logical grouping of attached files — scans of primary documents, electronic invoices (ESF)/SNT in attachments, templates, contracts, and arbitrary attachments. Each folder can be linked to a physical working directory on the disk (synchronization), supports access rights management at the folder level, and versioning/editing control of attached files. The object is auxiliary (infrastructure) and does not participate in accounting or tax accounting.

2. Attributes and table parts

2.1 Header Attributes

System (standard) attributes of the catalog:

• Code — string identifier of the folder (automatic or manual numbering).
• Name — name of the folder; validated for the absence of invalid characters for the file system (\ / : * ? " < > |).
• Parent — reference to the higher-level folder in the hierarchy (type CatalogReference.FileFolders).
• DeletionMark, Predefined — standard system attributes.

The element form also contains calculated/auxiliary fields FullPath and WorkingDirectory, displaying the folder's path in the hierarchy and the associated physical synchronization directory (formed programmatically, not storage attributes in the classical sense).

2.2 Table Parts

AdditionalAttributes

Purpose. Storage of additional user attributes of the folder, configurable through the “Properties” subsystem (BSP). Allows for the extension of the attribute set without changing the configuration.

3. Forms

Additionally, the object can use common (auto) forms: GroupForm (if hierarchy groups are highlighted separately) and SelectForm for substituting the folder in the attributes of other objects.

4. Key Module Procedures

In the attached evidence, fragments of BSL with paths path:string are not transmitted. Below are typical handlers for catalogs of this type (file folders BSP). Specific lines of the module should be compared with the release 3.0.74.2.

Object module (Catalog.FileFolders.ObjectModule):

• FillProcessing(FillingData, ...) — when creating a new folder, fills Responsible with the current user (Users.CurrentUser()) and CreationDate with the current session date (CurrentSessionDate()).
• FillCheckProcessing(Refusal, CheckedAttributes) — checks the correctness of Name (absence of invalid file system characters).
• BeforeWriting(Refusal) — control of changes in structure/rights, synchronization with the working directory.
• BeforeDeletion(Refusal) — control of the presence of attached files and subfolders before deletion.

Element form module:

• OnCreationOnServer — initialization of visibility of synchronization and rights fields, formation of FullPath.
• Handlers for the “Configure Synchronization” and “Access Rights” commands — opening the corresponding auxiliary forms of the “File Management” and “Access Management” subsystems.

Manager module / common BSP modules:

• Working with folders is encapsulated in common modules of the file subsystem (FileManagement*): creation, movement, determination of full path, synchronization of the directory, rights management.

5. Posting and Movements

The catalog FileFolders is not a document and does not perform posting. It does not generate movements in the accumulation/information registers of accounting or tax accounting and does not create accounting entries.

Accordingly, for this object the typical chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010), nor the rates and parameters of tax accounting of Kazakhstan for 2026 (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, deduction for individual income tax 30 MRP/month and no more than 360 MRP/year, individual income tax 10%/15%, OPV 10%, OPVR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%) are applicable. These parameters relate to accounting documents of the configuration, not to the auxiliary catalog of folders.

The only “movements” related to the folder are the registration of information in the auxiliary registers of the file management subsystem (structure of nesting, access rights, synchronization settings), which is maintained by standard BSP mechanisms, not by posting a document.

6. Related Objects and Input on the Basis

• Catalog.Files (or AdditionalDataStorage/file volumes) — attached files reference the folder through the owner attribute/FileFolder. The folder acts as a container.
• Catalog.Users — attribute Responsible; also participates in access rights management for the folder.
• PlanOfTypesOfCharacteristics.AdditionalAttributesAndInformation — source of additional attributes for the table part.
• Subsystem “Access Management” (RLS) — rights at the folder level.
• Subsystem “File Management” — synchronization with the working directory on the disk, storage volumes.

Input on the basis. For the auxiliary catalog of folders, input on the basis of accounting documents is not provided. Folders are created manually by the user or programmatically during the initial setup of the file storage.

7. Extension Points

• Additional attributes/information (subsystem “Properties”) — extension of folder attributes without changing the configuration (category, retention period, etc.).
• Configuration Extensions — adding attributes, form commands, overriding handlers FillProcessing/FillCheckProcessing without removing from support.
• Event Subscriptions (BeforeWriting, OnWriting) — additional logic for auditing or integration.
• BSP Programmatic API for file management — for automatic creation of folder structure and synchronization during implementation.
• RLS/access restriction templates — fine-tuning of rights at the folder level according to organizational roles.

Requires verification (version-specific): the exact composition of auxiliary fields of the element form (presence of WorkingDirectory/FullPath) and the set of common modules of the file subsystem may differ between BSP releases within the 3.0.74.x line — verify with the specific delivery of 3.0.74.2.