--- title: "Directory \"Enforcement Order 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-ispolnitelnyylistprisoedinennyefayly-tehniche-en source: BuhGPT --- # Directory "Enforcement Order Attached Files" — Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name ExecutiveSheetAttachedFiles Full Name Catalog.ExecutiveSheetAttachedFiles ( Catalogs.ExecutiveSheetAttachedFiles ) Synonym — (none; technical object, not directly opened from the interface) Configuration Accounting for --- 1. Identification Parameter Value Object Type Catalog Name ExecutiveSheetAttachedFiles Full Name Catalog.ExecutiveSheetAttachedFiles (Catalogs.ExecutiveSheetAttachedFiles) Synonym — (none; technical object, not directly opened from the interface) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Owner Document “ExecutiveSheet” (via attribute FileOwner) Purpose. The catalog stores files (scans, PDFs, images, documents) attached to the “Executive Sheet” documents. This is a service object of the “File Management” subsystem of the BSP: an instance of the catalog is created automatically when a file is attached to the executive sheet. The user interacts with it indirectly — through the panel/form of attached files of the owner document. The object provides storage of binary data (in the database or on disk volumes), versioning, encryption, electronic signing, and text extraction for full-text search. It is used by the accounting and HR departments when managing executive documents (collections for alimony, court decisions, etc.). Each type of document that supports attached files has its own catalog of the form AttachedFiles. This catalog is a container for files specifically for the “Executive Sheet” document. 2. Attributes 2.1 Header Attributes Name Type Mandatory Purpose Author CatalogReference.Users Mandatory (ShowError) The user who created the file record. Automatically filled. FileOwner DocumentReference.ExecutiveSheet Optional Reference to the “Executive Sheet” document to which the file is attached. Main linking attribute. UniversalModificationDate Date (DateTime) Optional Date/time of the last modification of the file in UTC. Used during synchronization. CreationDate Date (DateTime) Mandatory (ShowError) Date/time of record creation. Filled during the first save. Encrypted Boolean Optional Indicates that the file is encrypted. ModifiedBy CatalogReference.Users Optional The user who last modified the file or its attributes. ImageIndex Number Optional Index of the file type icon for display in lists/forms. Description String Optional Text comment on the file entered by the user. SignedEP Boolean Optional Indicates the presence of an electronic signature on the file. FilePath String Optional Path to the file on the server (when stored on disk volumes). Size Number Optional Size of the file in bytes. Automatically filled during upload. Extension String Optional File extension (“pdf”, “docx”, etc.). Determined from the name. EditingUser CatalogReference.Users Optional The user who has taken the file for editing (the file is “occupied”). TextExtractionStatus EnumerationReference.TextExtractionStatuses Optional Status of text extraction for full-text search (not extracted / extracted / error). TextStorage ValueStorage Optional Extracted text of the file for full-text search. FileStorageType EnumerationReference.FileStorageTypes Mandatory (ShowError) Storage method: in the database or on a disk volume. Key attribute. Volume CatalogReference.FileStorageVolumes Optional Storage volume (if storage on disk is selected). FileStorage ValueStorage Optional Binary data of the file (if stored in the database). Additionally (standard catalog attributes): Name — file name without extension; Code — service code; DeletionMark, Predefined (not used). 2.2 Table Parts This catalog does not have table parts. All file attributes are stored in the header attributes; versions, signatures, and the binary data itself are placed in service information registers of the file management subsystem (see section 5). 3. Forms Separate custom forms for the attached files catalog are generally not created — work is conducted through common forms and mechanisms of the BSP. The following are practically used: Form Purpose Common form AttachedFiles (CommonForm of the subsystem) List of files attached to the current executive sheet: adding, opening, saving, signing, encrypting, working with versions. Common form AttachedFile / file card Viewing and editing attributes of a specific file (description, EP, versions). Selection form / list of catalog elements Service form for administration and analysis of the file storage. If the configuration does not specify custom forms for the object, the platform generates them automatically; functionality is fully provided by the common BSP forms “File Management”. 4. Key Module Procedures The application code in the catalog module is usually minimal; all logic is concentrated in the common modules of the “File Management” subsystem of the BSP. Typical handlers and logic points for this type of object: - ManagerModule / ObjectModule — handler BeforeWriting: control of mandatory attributes filling (Author, CreationDate, FileStorageType), updating UniversalModificationDate and ModifiedBy. - FileManagement (common module) — AddFile, UpdateFileVersion, OccupyFile / CancelFileEditing, ReleaseFile: creating a catalog record, placing binary data in the database or volume, maintaining versions. - FileManagementService / …ClientServer — determining Extension, Size, ImageIndex from the uploaded file; selecting volume via FileStorageVolumes. - ElectronicSignature — signing/verifying EP, setting the flag SignedEP. - Encryption — encrypting/decrypting data, setting the flag Encrypted. - FileTextExtraction (scheduled task) — extracting text into TextStorage, setting TextExtractionStatus. Specific paths path:string in the provided evidence are absent, therefore typical handlers of this type of object are listed. The composition of called procedures is version-specific and is clarified by the modules of the specific assembly 3.0.74.2. 5. Posting and Movements The catalog is not a document and is not posted — it does not generate entries in the chart of accounts and movements in accumulation/accounting registers. Economic operations and amounts (collections, withholdings, VAT, etc.) are reflected by the owner document “Executive Sheet” and related calculation documents, not the file storage. Data of the object participate in service registers of the “File Management” subsystem: Register (type) Role Information Register BinaryFileData / BinaryFileDataStorage Binary data of the file and its versions (when stored in the database). Information Register FileVersions / version history Storage of previous versions and versioning metadata. Information Register for EP and encryption Data of electronic signatures and encryption certificates of the file. Information Register FileTexts Extracted text for full-text search. For reference — numerical specifics of RK-2026, applied in owner documents (not in this catalog): VAT rate 16%; MRP = 4,325 ₸, MZP = 85,000 ₸; PIT 10% (15% over 8,500 MRP annual income); standard deduction for PIT — 30 MRP/month, but not more than 360 MRP/year; OPE 10% (base ceiling 50 MZP), OPEP 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%. Typical accounts of the RK: 1210, 1030, 1330, 3310, 3130, 6010, 7010. Electronic documents — ESF (IS ESF) and SCT. Currency — tenge (₸). These values relate to accounting documents of the configuration; the attached file storage does not use them. 6. Related Objects and Input Based On - Document “ExecutiveSheet” — owner of the files (attribute FileOwner). Catalog records are created from the form of this document. - Catalog “Users” — attributes Author, ModifiedBy, EditingUser. - Catalog “FileStorageVolumes” — attribute Volume when stored on disk. - Enumerations FileStorageTypes, TextExtractionStatuses. - BSP subsystem “File Management” — registers of versions, EP, encryption, texts. Input based on for this object is not provided: records are generated only by the file attachment mechanism, not by the “Create Based On” commands. 7. Extension Points - Event subscriptions BeforeWriting / OnWriting of the catalog — additional control (for example, limiting extensions or maximum file size for executive sheets). - Overridable BSP modules FileManagementOverridable, ElectronicSignatureOverridable — setting rules for storage, signing, encryption. - Configuration extension — adding custom attributes (category/type of executive document) and borrowing forms of attached files. - Rights and RLS — restricting access to executive sheet files at the level of roles and access group profiles. - Scheduled task for text extraction — extending scenarios for full-text search in attachments. Where to Find Navigation link 1C: e1cib/list/Catalog.ExecutiveSheetAttachedFiles Through the interface, the object is opened indirectly — from the document “Executive Sheet” via the command to work with attached files. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_