1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ВидыСделокСКлиентамиПрисоединенныеФайлы |
| Full name | Справочник.ВидыСделокСКлиентамиПрисоединенныеФайлы |
| Synonym | "Attached Files (Client Deal Types)" |
| Configuration | Trade Management for Kazakhstan, 3.4.5.21 |
| SSL Subsystem | "File Operations" (РаботаСФайлами) |
| Owner | Справочник.ВидыСделокСКлиентами |
| Hierarchy | None |
Purpose. This is a service catalog automatically generated by the "File Operations" mechanism of the Standard Subsystems Library (SSL). It stores files attached by the user to items of the owner catalog ВидыСделокСКлиентами (agreement scans, templates, images, deal regulation documents, etc.). The user does not work with this catalog directly as a list — it is opened via the "Attached files" command from the deal type card. Each item of this catalog corresponds to one attached file and is subordinate to a specific owner item.
Important: the object is not an accounting entity (document) — it does not participate in posting and does not generate accounting entries or register movements. Tax rates, the chart of accounts, and electronic documents (ESF, SNT) do not apply to it. All financial calculations are performed by the documents that own the business transactions, not by the file storage.
2. Attributes and tabular sections
SSL attached file catalogs have a standard set of attributes. The object has no tabular sections.
Standard attributes
| Attribute | Type | Purpose |
|---|---|---|
Код |
String/Number | Internal item code |
Наименование |
String (150) | File name without extension (display name) |
Владелец |
CatalogRef.ВидыСделокСКлиентами | Owner item the file is attached to |
ПометкаУдаления |
Boolean | Standard deletion mark |
Object attributes (file mechanism specifics)
| Attribute | Type | Purpose |
|---|---|---|
ХранилищеФайла |
ValueStorage | Binary file data when stored in the infobase (empty when stored in volumes) |
ПутьКФайлу |
String | Relative file path when stored in a disk volume |
ТомХранения |
CatalogRef.ТомаХраненияФайлов | Storage volume (for "stored in disk volumes" option) |
Расширение |
String | File extension (pdf, xlsx, png …) without the dot |
Размер |
Number | File size in bytes |
Автор |
CatalogRef.Пользователи (or author type) | User who added/modified the file |
ДатаСоздания |
Date | File creation moment |
ДатаМодификацииУниверсальная |
Date | Universal (UTC) date of last modification |
ЗапретРедактирования |
Boolean | "Read-only" flag |
ЗанятоДляРедактирования |
Boolean / user reference | Editing lock flag, who holds it |
ПодписанЭП |
Boolean | File has a digital signature |
Зашифрован |
Boolean | File is encrypted |
ТекущаяВерсия |
CatalogRef.*ВерсииПрисоединенныхФайлов | Reference to the current version (if versioning is enabled) |
ТекстХранилище |
ValueStorage | Extracted file text for full-text search |
Описание |
String (unlimited) | User comment on the file |
3. Forms
| Form | Purpose |
|---|---|
| Item form | Attached file card: name, author, dates, size, signature/encryption flags, "Open", "Save", "Edit", "Finish editing" commands |
| List form | List of files attached to the owner (usually the subsystem's common form is called) |
In practice, the file-handling interface is implemented by the common forms of the "File Operations" subsystem (ОбщаяФорма.ПрисоединенныеФайлы, SSL viewing/selection forms), rather than by dedicated forms of each attached-files catalog. Therefore the object itself often lacks its own forms or has them reduced to a minimum — work is done through standard SSL mechanisms.
4. Key module procedures
No application-level evidence for the object's modules has been provided (only the "Purpose" facet was supplied). Below are typical handlers for this type of object.
The object module / manager module of attached file catalogs are usually thin: almost all business logic is moved to SSL common modules. Possible handlers:
ПередЗаписью(Отказ)— validates file attribute correctness, sets the author/dates, calls SSL service mechanisms.ПриКопировании(ОбъектКопирования)— resets lock/signature flags when copying.ПередУдалением(Отказ)— deletes related versions and physical files from the volume.
The main logic resides in the subsystem's common modules:
РаботаСФайлами/РаботаСФайламиКлиент— client scenarios: open, save as, add, edit.РаботаСФайламиВызовСервера— server-side file operations.РаботаСФайламиСлужебный,РаботаСФайламиСлужебныйКлиент— service procedures (locking, versions, text extraction, volume operations).ПрисоединенныеФайлы,ПрисоединенныеФайлыСлужебный— API for adding/retrieving attached files for an arbitrary owner.
Requires verification: the exact composition and signatures of module procedures depend on the SSL version built into 3.4.5.21.
5. Posting and register movements
The catalog is not posted and does not generate movements in any register. It only implements storage of file metadata and content. Accordingly:
- accounting entries (Kazakhstan chart of accounts 1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.) are not generated;
- VAT (Kazakhstan 2026 rate — 16%), individual income tax, mandatory pension contributions, health insurance (OSMS/VOSMS), social contributions, social tax do not apply to the object;
- electronic documents ESF (ESF IS) and SNT are not issued by this catalog.
The only "movements" of data are writing/reading binary content: either into the ХранилищеФайла attribute (storage in the infobase), or into the file system of the ТомаХраненияФайлов volume (storage in disk volumes). The storage option is set in the "File Operations" subsystem settings.
6. Related objects and "input based on"
| Relation | Object |
|---|---|
| Owner | Справочник.ВидыСделокСКлиентами |
| File versions | Справочник.ВидыСделокСКлиентамиВерсииПрисоединенныхФайлов (when versioning is enabled) |
| Storage volumes | Справочник.ТомаХраненияФайлов |
| Users | Справочник.Пользователи (author, held by) |
| Common mechanisms | SSL "File Operations" subsystem, "Digital Signatures and Encryption" |
Input based on is not applicable for attached files. Instances are created solely by file-adding commands from the owner's card (uploading from disk, scanning, creating from a template).
7. Extension points
- Configuration extension: adding custom attributes/forms to the catalog without removing it from support; overriding the behavior of the subsystem's common forms.
- SSL common modules with an override suffix (
РаботаСФайламиПереопределяемый, etc.) — configuring file-handling parameters, type/size restrictions. - Event subscriptions (
ПередЗаписью,ПриЗаписи) of the catalog — for auditing, additional validation, auto-numbering. - RLS / access rights: access control for files is inherited from the rights to the
ВидыСделокСКлиентамиowner; configured via access group profiles. - Full-text search: content indexing via the
ТекстХранилищеattribute.
Where to find
1C navigation link:
e1cib/list/Справочник.ВидыСделокСКлиентамиПрисоединенныеФайлы
The standard interface does not display the list separately — files are opened via the "Attached files" command from the item card of the "Client deal types" catalog.