--- title: "Directory \"MeetingAttachedFiles\" — Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-vstrechaprisoedinennyefayly-tehnicheskoe-opis-en source: BuhGPT --- # Directory "MeetingAttachedFiles" — Technical Description > **TL;DR:** ```html 1. Identification Parameter Value Object Type Catalog Name MeetingAttachedFiles Full Name Catalog.MeetingAttachedFiles Synonym — (system object, synonym not specified) Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) File Owner Document.Meeting S --- ```html 1. Identification Parameter Value Object Type Catalog Name MeetingAttachedFiles Full Name Catalog.MeetingAttachedFiles Synonym — (system object, synonym not specified) Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) File Owner Document.Meeting Subsystem Library of standard subsystems (BSP) → "File Management" Purpose. The catalog stores files attached to documents of the type "Meeting". This is a system catalog of the file management subsystem: it automatically manages the metadata of attached documents (PDFs, images, office files, etc.), including versioning, editing status ("loan"), encryption, and electronic signatures. The user interacts with it indirectly — through the "Attached Files" command in the meeting card. The catalog implements strict access control at the record level (RLS): the file is visible and editable only to those users who have rights to the owner document. Where to find in 1C: section "Standard Subsystems" → "Attached Files (Meeting)". Navigation link: e1cib/list/Catalog.MeetingAttachedFiles. 2. Attributes and Table Parts 2.1 Header Attributes Name Type Mandatory Purpose Author Catalog.FileSynchronizationAccounts / Catalog.Users Raise error Who originally attached the file. Automatically filled when creating a record. Mandatory for auditing operations. FileOwner Document.Meeting Do not check Reference to the meeting document to which the file is attached. Defines the context of placement and is used for access rights control (RLS). LoanDate Date and time Do not check The moment when the file is taken for editing ("loan"). Empty if the file is not being edited. ModificationDateUniversal Date and time Do not check Date of the last modification of the file in universal time (UTC). Used for synchronization and determining the relevance of the version. CreationDate Date and time Raise error The moment of the initial saving of the file in the database. Mandatory field for chronology and reporting. Encrypted Boolean Do not check Indicates that the content of the file is encrypted. If True, a certificate is required for decryption. ModifiedBy Catalog.FileSynchronizationAccounts / Catalog.Users Do not check User who last edited the file or its metadata. Updated with each save of changes. ImageIndex Number (15,0) Do not check Index of the icon from the platform's image collection displayed next to the file (depends on the extension). Description String (unlimited) Do not check Arbitrary user comment on the file (purpose of the document, brief content, etc.). SignedEP Boolean Do not check Indicates the presence of at least one valid electronic signature. Used for quick filtering of signed documents. FilePath String (unlimited) Do not check For files in external volumes — the full path to the file on the disk/network resource. Empty if the file is stored in the database. Size Number (15,0) Do not check Size of the file in bytes. Displayed to the user, used for quota control and storage volume assessment. Extension String (10) Do not check File extension without a dot (pdf, docx). Determines the processing method, icon, and available operations. In addition to those listed, catalogs of this type in BSP have system attributes for storage and versioning — FileStorage / StorageVersion, CurrentVersion (current version from the subordinate version catalog), DatabaseRecord, StorageVolume, SignedWithEnhancedEP. The exact set depends on the version of BSP. Requires verification in the specific build 3.0.74.2, as the composition of service attributes is version-specific. 2.2 Table Parts The object does not have its own user-defined table parts. Multiple data (file versions, electronic signatures, encryption certificates) are stored in separate subordinate objects of BSP, not in the table parts of the catalog itself: - versions — in the subordinate catalog MeetingAttachedFilesVersions; - electronic signatures and certificates — in sets of records of information registers of the "Electronic Signatures" subsystem. 3. Forms Form Purpose ElementForm Card of the attached file: viewing and editing metadata (description, author, dates), commands for opening, saving, editing ("loan/release"), working with versions, signing with EP and encryption. ListForm List of all files attached to meetings. Typically called in the context of a specific owner (one meeting) and shows only its files due to RLS. SelectForm Selecting a file from the list during program calls or in subsystem dialogs. In the standard delivery, the card and list of files are formed by common forms of the "File Management" subsystem of BSP (for example, CommonForm.AttachedFile, CommonForm.AttachedFiles), so the catalog may not have its own forms, and interaction occurs through common forms. Requires verification — the specific composition of its own forms depends on the build. 4. Key Module Procedures No separate BSL-evidence for the object's modules is attached. Below are typical handlers and logic points for the attached files catalog of BSP; in this configuration, the main business logic is moved to the common modules of the subsystem, not to the module of the catalog itself. Object Module (ObjectModule): - BeforeWriting(Refusal) — control of the correctness of metadata, setting/updating attributes ModifiedBy, ModificationDateUniversal, checking the lock for editing ("loan"). - OnCopy(CopyObject) — reset of service attributes (SignedEP, Encrypted, links to versions) when copying. - BeforeDeleting(Refusal) — coordinated deletion of file data from storage/volume and subordinate versions. Common modules of the "File Management" subsystem (main logic): - FileManagement / FileManagementService — attaching, opening, saving files, the "loan/release" mechanism for editing. - FileManagementServerCall — server operations for reading/writing binary data, creating new versions. - FileStorageService — working with storage volumes and paths (FilePath, StorageVolume). The "Electronic Signatures" and "Encryption" subsystems service the attributes SignedEP, SignedWithEnhancedEP, Encrypted during signing and encrypting content. Since the modular implementation is part of BSP, specific procedure names and lines require verification in the source code of build 3.0.74.2. 5. Posting and Movements The object is a catalog and does not perform postings — it does not generate entries according to the chart of accounts and does not create movements in accumulation/accounting registers. Entries in accounting registers and business operations with amounts are generated not by it, but by the accounting documents of the configuration (sales, receipts, etc.). It follows that for this catalog, standard postings and accounts for the RK are not applicable — it only stores files. For reference, we will indicate where in the configuration "Accounting for Kazakhstan" actual movements occur (these accounts relate to accounting documents, not to the file catalog): Operation (in accounting documents) Debit Credit Sale of goods to the customer 1210 (short-term receivables from customers) 6010 (income from sales) Accrual of VAT on sales (rate 16 %) 1210 3130 (VAT payable) Write-off of cost 7010 (cost of sales) 1330 (goods) Receipt of goods from the supplier 1330 3310 (payables to suppliers) Receipt of payment to the current account 1030 (cash in current accounts) 1210 The catalog MeetingAttachedFiles does not participate in these postings; it only stores files attached to the meeting (scans of contracts, electronic invoices (ESF)/SNT in PDF format, images, etc.). Electronic documents of the RK (ESF via IS ESF, SNT) are uploaded/downloaded by specialized subsystems; the attached file may serve as a carrier of the printed/visual form of such a document, but does not carry any tax amounts itself. All numerical norms of the RK for 2026 (MPR = 4,325 ₸, MZP = 85,000 ₸, basic deduction for individual income tax 30 MPR/month and no more than 360 MPR/year, individual income tax 10% up to 8,500 MPR of annual income and 15% above, OPP 10% with a base cap of 50 MZP, OPPR 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%, VAT rate 16%) are applied in the calculation documents of the configuration, not in this service catalog. 6. Related Objects and Input Based On Owner Object: - Document.Meeting — the parent document to which files are attached (attribute FileOwner). Related objects of the file subsystem: - Catalog.MeetingAttachedFilesVersions — stores the history of file versions. - Catalog.FileSynchronizationAccounts — accounts involved in the attributes Author and ModifiedBy along with Catalog.Users. - Information registers of the "Electronic Signatures" and "Encryption" subsystems — store signatures (SignedEP) and encryption certificates (Encrypted). - Register(s) of storage and file volumes — when storing files in external volumes (FilePath, StorageVolume). Input Based On. The classic "Input Based On" mechanism is not used for this object. Records are created automatically by the file attachment command in the meeting form (drag-and-drop, "Add file", scanning, from email, etc.). Direct interactive creation of a catalog element by the user is not provided. 7. Extension Points - Configuration Extensions. You can add your own attributes (for example, "Document Category", "Storage Period") and override/supplement the handlers of attached files forms without removing the object from support. - BSP Handlers for File Management. Program events of the "File Management" subsystem (overridable modules like FileManagementOverridable) allow you to embed checks when attaching, limit types/sizes of files, set quota rules (attribute Size). - Access Control (RLS). Rights are inherited from the owner document Meeting. Extension of roles and access restriction templates allows you to adjust the visibility of files to the organization's tasks. - Electronic Signature and Encryption. Integration with EP/encryption subsystems — an extension point for corporate signing policies (including for visual copies of ESF/SNT), services the attributes SignedEP, SignedWithEnhancedEP, Encrypted. - File Storage. Configuring storage volumes allows you to move content from the database to external volumes (attributes FilePath, StorageVolume). ``` --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_