Document "OutgoingElectronicLetterAttachedFiles" - Technical Description (BK 3.0.74.2)

1. Identification

Purpose. The object stores metadata of files attached to outgoing emails. Each file that a user attaches to the document “Outgoing Email” (PDF, DOCX, XLSX, images, archives, as well as ESF/SNT attachments and printed forms) generates one element of this object. This is a standard object for “attached files” in the BSP mechanism: for each owner object that supports attachments, the platform/configuration creates a separate object <Owner>AttachedFiles.

The object is not accounting: it does not store amounts, does not participate in tax calculations, and does not generate accounting entries. Its role is to serve as a file card (name, size, version, author, signature/encryption attributes, text extraction status). The binary content of the file itself is stored separately (see section 5).

Where to find in 1C: the object is service-related and does not have its own menu item. Access to files is provided from the owner document form (“Outgoing Email”) through the “Attached Files” panel or through the general command of the “File Management” subsystem. Navigation link for service viewing of the list: e1cib/list/Document.OutgoingEmailAttachedFiles.

2. Attributes and Table Parts

2.1 Header Attributes

In addition to the listed attributes, objects of this type typically have service fields for versioning (VersionStorage/CurrentVersion, FileStorageType, FileStorageVolume, DeletionMark). The specific composition of service attributes is version-dependent — requires verification in the configurator of the target release.

2.2 Table Parts

The object has no table parts. It is a flat file card: one record = one attached file. The multiplicity of files for one email is ensured by multiple records with the same FileOwner, not by rows in a table part.

3. Forms

The service object is not designed for independent user operation, so it has minimal application forms. Work is conducted through the general forms of the “File Management” subsystem.

4. Key Module Procedures

No separate reference BSL code for this object is attached in evidence. Below are standard handlers for objects of the type “Attached Files” in the BSP mechanism; actual implementations are concentrated in the general modules of the subsystem, not in the module of the object itself.

Object/Manager Module (standard handlers):

• ProcessingFilling — setting Author, CreationDate, UniversalModificationDate upon creation.
• BeforeWriting — updating UniversalModificationDate, ModifiedBy, controlling the attributes EditingUser/LoanDate.
• BeforeDeletion — clearing associated binary content and versions in the file storage.

General BSP modules servicing the object:

• FileManagement / FileManagementClient — application API: add, open, save, take for editing/release, work with versions.
• FileManagementService / FileManagementServiceServer — low-level operations: writing binary data to storage (volume or DB), text extraction, updating card attributes, checking rights by owner.
• FileManagementInternet/Synchronization… — file exchange with external resources and directories via FileSynchronizationAccounts.
• Electronic signature subsystem (ElectronicSignature/…Service) — setting/checking EP and encryption, reflected in the attributes SignedEP and Encrypted.

Exact paths module:string — are version-specific; requires verification in the configurator of release 3.0.74.2.

5. Posting and Movements

Posting is disabled. The object OutgoingEmailAttachedFiles is service-related, the posting mode is not used. It does not generate accounting entries (accounting register “Cost Accounting”) and does not make movements in accounting registers for cost, VAT, settlements, etc.

Accordingly, this object does not relate to the VAT rate of Kazakhstan 2026 (16 %), nor to the accounts of the standard plan of the RK (1210 — short-term receivables from buyers, 1030 — cash in current accounts, 1330 — goods, 3310 — payables to suppliers, 3130 — VAT payable, 6010 — revenue from sales, 7010 — cost of sales), nor to the parameters of individual income tax (IIT)/pension contributions (PC)/social health insurance (SHI) (MPR = 4,325 ₸, MSP = 85,000 ₸, deduction 30 MPR/month and no more than 360 MPR/year, IIT 10 %/15 % with a threshold of 8,500 MPR, PC 10 % with a ceiling of 50 MSP, OPR 3.5 %, VOSMS 2 %, OSMS 3 %, SO 5 %, social tax 6 %). These norms apply in accounting documents of the configuration, not in the card of the attached file. They are provided here as a reference for the country in case the object is confused with an accounting one.

How the file data is actually stored:

• Metadata (name, size, version, author, dates, EP, encryption) — in the object itself.
• Binary content — depending on the BSP storage settings:
  • in the information register of file storage (AttachedFilesStorage/FilesStorage) when stored in the database, or
  • on disk in volumes (FileStorageVolumes), with the path recorded in the attribute FilePath.
• File versions — in the associated version object (…AttachedFilesVersions or the general versioning mechanism of BSP).
• Extracted text — in the attribute TextStorage, status — in TextExtractionStatus (for full-text search).

6. Related Objects and Input Based On

Input Based On. As a source or receiver for input based on, the object is not used — it is not an accounting document. Instances are created programmatically when attaching a file to an email (using the commands “Add”, “Upload”, “Scan”, as well as automatically when generating and attaching printed forms, ESF, SNT).

7. Extension Points

• Configuration Extensions. Adding custom attributes to the file card (e.g., “Attachment Category”, “Sent to Counterparty”) and columns in the general form of attached files; overriding handlers BeforeWriting/BeforeDeletion through extension plugins.
• Programmatically Overridable BSP Modules. FileManagementOverridable — rules for working with files (available extensions, size limits, actions when adding). ReportVariantsOverridable/SignaturesAndPrints… — when integrating printed forms into attachments.
• Event Subscription Handlers (BeforeWriting/OnWriting of the object) — for auditing, auto-filling descriptions, integration with external document archives.
• File Storage