1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ВыкупВозвратнойТарыУПоставщикаПрисоединенныеФайлы |
| Full name | Catalog.ВыкупВозвратнойТарыУПоставщикаПрисоединенныеФайлы |
| Synonym | "Attached Files (Return Container Buyback from Supplier)" |
| Configuration | Trade Management for Kazakhstan, ed. 3.4 (3.4.5.21) |
| Owning subsystem | "File Handling" (SSL) |
| Purpose | Storage of files (scans, attachments, digital signatures) attached to a specific "Return Container Buyback from Supplier" document |
Purpose per evidence: "Attached Files (Return Container Buyback from Supplier)" is a service catalog of the "Trade Management for Kazakhstan 3.4" configuration, implementing the attached files mechanism of the Standard Subsystems Library (SSL).
This is a typical subordinate catalog of the type <Object>AttachedFiles. Each of its items is a single file (a Word/PDF document, scan image, picture, an ESF/SNT XML, etc.) logically linked to a specific owner document. The user does not work with it directly, but through the "Attached Files" panel in the owner document's form.
Where to find it
- Programmatically/for debugging — list navigation link:
e1cib/list/Catalog.ВыкупВозвратнойТарыУПоставщикаПрисоединенныеФайлы - In the interface — from the "Return Container Buyback from Supplier" document form → the "Attached Files" command/panel (the SSL common form
ПрисоединенныеФайлы).
2. Header attributes and tabular sections
2.1. Standard catalog attributes
| Attribute | Type | Purpose |
|---|---|---|
Owner |
DocumentRef.ВыкупВозвратнойТарыУПоставщика |
The document to which the file is attached. The key "file → document" link |
Description |
String | File name without extension (displayed) |
Code |
String/Number | Internal item code |
DeletionMark |
Boolean | Standard deletion mark |
Predefined |
— | Not used (files are created by users) |
2.2. "File Handling" subsystem attributes
| Attribute | Type | Purpose |
|---|---|---|
Extension |
String | File extension (pdf, xlsx, xml, png…) |
Author |
CatalogRef.Users / ExternalUsers |
Who uploaded the file |
CreationDate |
Date | Moment the file was attached |
UniversalModificationDate |
Date | Date of last modification (UTC) |
FileSize (ОбъемФайла) |
Number | Size in bytes |
BeingEditedBy |
CatalogRef.Users |
Who has locked the file for editing (lock) |
TextStorage |
ValueStorage | Extracted text for full-text search |
FileStorage |
ValueStorage | Binary file data when stored in the infobase |
FileStorageVolume |
CatalogRef.FileStorageVolumes |
Volume when files are stored in disk volumes |
PathToFileInVolume |
String | Relative path to the file within the volume |
SignedWithDS (ПодписанЭЦП) |
Boolean | Flag indicating presence of a digital signature |
Encrypted |
Boolean | Flag indicating content encryption |
PictureIndex |
Number | Icon index by file type in the interface |
Binary data is stored either in
FileStorage(in the infobase) or in volumes (FileStorageVolume+PathToFileInVolume) — depending on the "Store files in disk volumes" setting.
2.3. Tabular sections
| Tabular section | Key attributes | Purpose |
|---|---|---|
DigitalSignatures |
Signature (ValueStorage), IssuedTo, IssuedBy, Thumbprint, SigningDate, ValidFrom, ValidTo, Comment |
Digital signatures applied to the file (for scans of contracts, acts, etc.) |
EncryptionCertificates |
Certificate (ValueStorage), IssuedTo, Thumbprint |
Certificates used to encrypt the file |
3. Forms
Attached files catalogs generally do not have their own forms — work is done through SSL common forms. Standard set:
| Form | Role |
|---|---|
Common form ПрисоединенныеФайлы (SSL) |
Main work panel: list of the owner document's files, adding, viewing, editing, digital signatures |
ItemForm (if present) |
Card of an individual file: name, author, dates, size, signatures |
ListForm (if present) |
Service list of all catalog files (administration/debugging) |
| Common form for selecting/viewing digital signatures | Viewing attributes and verifying digital signatures |
If build 3.4.5.21 has no dedicated forms, the platform generates them automatically, and user work is fully handled by the common forms of the "File Handling" subsystem. (The presence of a dedicated ItemForm is version-specific and must be checked in the configurator of the specific build.)
4. Key module procedures
The source BSL code for this object is not attached in the evidence, so listed below are the typical handlers for an SSL attached files catalog.
Manager module / object module:
FillingProcessing— populates service attributes on creation (author, creation date, extension).BeforeWrite— setsUniversalModificationDate, controls theSignedWithDS/Encryptedflags, releases/sets the edit lock (BeingEditedBy).BeforeDelete— removes binary data from the volume (PathToFileInVolume) if the file was stored in volumes, to avoid leaving orphans on disk.OnCopy— clears references to signatures/binary data so the copy does not inherit the original's digital signature.
Calls through SSL common modules (not in the object module):
FilesOperations/FilesOperationsInternal— adding a file, retrieving binary data, placing it in a volume or infobase, extracting text for search.DigitalSignatureAndEncryption— applying and verifying digital signatures, working with theDigitalSignaturesandEncryptionCertificatestabular sections.
The attachment logic is initiated from the owner document's form via the files panel command; the catalog itself is a passive storage.
5. Posting and movements
The catalog is not a document and is not posted — it does not generate register records or ledger entries. Its role is limited to storing files.
Accounting and inventory movements are generated by the owner document — "Return Container Buyback from Supplier". For context, under the standard Kazakhstan chart of accounts, it affects:
| Operation | Debit | Credit |
|---|---|---|
| Capitalization of bought-back return container | 1330 (goods/container) | 3310 (AP to suppliers) |
| VAT allocation at the rate of 16% (Kazakhstan, 2026) | 1420 (VAT recoverable) | 3310 |
| VAT accrual payable (for the relevant operation) | — | 3130 (VAT payable) |
| Payment to supplier from current account | 3310 | 1030 (funds in current accounts) |
Electronic document flow for the operation is conducted through the ESF IS (ESF) and SNT; the XML of these documents can also be attached as a file to the catalog in question. All amount calculations are in tenge (₸).
The 16% VAT rate and chart of accounts are provided as owner context; the attached files catalog itself is not involved in these calculations.
6. Related objects and entry based on
| Object | Relationship type |
|---|---|
Document.ВыкупВозвратнойТарыУПоставщика |
Owner (parent document) |
Catalog.FileStorageVolumes |
Physical storage location when stored in volumes |
Catalog.Users / ExternalUsers |
File author, editing user |
| "File Handling" subsystem (SSL) | Mechanism for adding/viewing/signing |
| ESF IS, SNT | Source of XML files attached to the document |
Entry based on: not applicable for a service catalog of attached files. Items are created only through the file attachment mechanism from the owner document's form (upload from disk, scanning, drag-and-drop, paste from clipboard).
7. Extension points
- Configuration extension: adding custom file attributes (e.g., "Document type: contract/act/ESF"), enhancing the item form, adding checks in
BeforeWrite. - Storage volumes: moving files from the infobase to disk volumes (the "Store files in volumes" setting) — affects
FileStorageVolume/PathToFileInVolume. - Access rights (RLS): restricting file visibility through rights on the owner document.
- Digital signature/encryption: connecting certificates and signing rules through the "Digital Signature and Encryption" subsystem.
- Event subscriptions / SSL handlers: intercepting file addition for automatic classification, antivirus scanning, or synchronization with an external storage.
When making enhancements, do not change the standard SSL attributes (
FileStorage,FileStorageVolume,DigitalSignatures, etc.) — this will break compatibility with the common forms and updatability of the "File Handling" subsystem.