1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ЗапланированноеВзаимодействиеПрисоединенныеФайлы |
| Full name | Справочник.ЗапланированноеВзаимодействиеПрисоединенныеФайлы |
| Synonym | Absent (technical catalog; in the interface it is represented via the "Attached Files" mechanism) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Subsystem | "File Management" (SSL / "Standard Subsystems") |
| File owner | Document ЗапланированноеВзаимодействие (CRM functionality for communication planning) |
Purpose. The catalog is intended for storing files attached to "Planned Interaction" documents (calls, meetings, letters). Each catalog item is a separate file with its own metadata (author, size, extension, dates, signature/encryption flags) and a reference to physical storage (database or a volume on disk). The catalog is utility-oriented: the user almost never opens it directly — files are added and viewed from the owner document's form via the standard interface for working with attached files. It provides file versioning, access control (RLS) based on rights to the owner, and support for electronic signature and encryption.
Important: this is a file storage catalog of the CRM module. It does not participate in accounting and tax accounting, does not generate postings, and does not operate with amounts, rates, and accounts. RK tax parameters (VAT 16%, IIT, RK chart of accounts, etc.) are not applicable to this object — they relate to the accounting documents of the configuration, not to the technical file storage.
Where to find it in 1C:
Navigation link: e1cib/list/Справочник.ЗапланированноеВзаимодействиеПрисоединенныеФайлы
Via the interface: section "Standard Subsystems" → "Attached Files (Planned Interaction)", or from the "Planned Interaction" document form → panel/command "Attached Files".
2. Header attributes and tabular sections
2.1 Header attributes (from evidence)
| Name | Type | Requiredness | Purpose |
|---|---|---|---|
| Автор | СправочникСсылка.УчетныеЗаписиСинхронизацииФайлов, СправочникСсылка.Пользователи |
Required (ShowError) | The user or account that uploaded the file. Used for auditing, displaying the creator, and access control. |
| ВладелецФайла | ДокументСсылка.ЗапланированноеВзаимодействие |
Optional | Reference to the owner document. Basis of RLS filtering: rights to the file are inherited from rights to the owner. |
| ДатаЗаема | ДатаВремя |
Optional | Date/time the file was checked out for editing (locked for others). An empty value means the file is free. |
| ДатаМодификацииУниверсальная | ДатаВремя |
Optional | Date of last modification in UTC. For synchronization and determining the relevance of a version. |
| ДатаСоздания | ДатаВремя |
Required (ShowError) | Timestamp of record creation. Filled in automatically, used for sorting and reporting. |
| Зашифрован | Булево |
Optional | File encryption flag. True — a certificate is required to open it. |
| Изменил | СправочникСсылка.УчетныеЗаписиСинхронизацииФайлов, СправочникСсылка.Пользователи |
Optional | The user who last saved a new version. |
| ИндексКартинки | Число |
Optional | Icon index for lists (depends on extension: doc, pdf, xls…). |
| Описание | Строка |
Optional | Text description of the file for search and identification without opening it. |
| ПодписанЭП | Булево |
Optional | Flag indicating the presence of at least one valid electronic signature. |
| ПутьКФайлу | Строка |
Optional | Relative path on the storage volume (when ТипХраненияФайла = НаДиске). |
| Размер | Число |
Optional | File size in bytes. Filled in automatically, used for quotas and reports. |
| Расширение | Строка |
Optional | File extension (docx, pdf…). Determines the icon and available operations. |
2.2 Attributes typical of SSL attached files (supplementing the header)
In addition to those listed in evidence, SSL attached-file catalogs standardly contain the following attributes (the presence of a specific one is version-dependent and is checked in the Designer of this version):
| Name | Type | Purpose |
|---|---|---|
| ТипХраненияФайла | ПеречислениеСсылка.ТипыХраненияФайлов (ВИнформационнойБазе / НаДиске) |
Determines where the binary content resides: in a storage attribute or on a volume. |
| ХранилищеФайла | ХранилищеЗначения |
Binary file data (when stored in the infobase). |
| ТекущаяВерсия | СправочникСсылка.*ВерсииПрисоединённыхФайлов |
Reference to the current version (if versioning is enabled). |
| ЗаемщикФайла | СправочникСсылка.Пользователи |
Who checked out the file for editing (paired with ДатаЗаема). |
| ТомХранилищаФайла | СправочникСсылка.ТомаХраненияФайлов |
The volume on which the file is placed (when stored on disk). |
| КонтрольнаяСуммаФайла | Строка |
File hash for integrity verification. |
2.3 Tabular sections
Utility tabular sections are typical of SSL attached files (checked against this version):
| Tabular section | Purpose |
|---|---|
| ЭлектронныеПодписи | Storage of the attributes of applied electronic signatures: certificate, signature date, signatory, signature stamp. Populated when the file is signed. |
| ЗашифрованныеДанные | Storage of the certificates with which the file is encrypted (list of recipients). Relevant when Зашифрован = Истина. |
3. Forms
The technical attached-files catalog, as a rule, works through the common forms of the SSL "File Management" mechanism and contains a minimal set of its own forms:
| Form | Purpose |
|---|---|
| ItemForm | View/edit the file card: description, metadata, commands for opening, saving, signing, encryption, working with versions. Often absent as a separate form — the common attached-file form is used. |
| ListForm | Utility list of all catalog records (for the administrator/developer). User work is carried out through the common "AttachedFiles" form. |
Common SSL forms (ПрисоединённыеФайлы, ФормаПрисоединённогоФайла, ВыбранныеФайлы) |
The main user interface: a list of files attached to the owner document, add/delete, open, versions, signature, encryption. Called from the "Planned Interaction" document form. |
The exact list of the catalog's own forms is determined by the configuration version; in the standard delivery, priority is given to the subsystem's common forms.
4. Key module procedures
No proprietary BSL code is attached in evidence, so below are the typical handlers for an SSL attached-files catalog. Their composition and signatures are checked in the object/manager module of this version.
Object module:
ПередЗаписью(Отказ)— checking that required attributes are filled in (Автор,ДатаСоздания), controlling the correctness of signature/encryption flags, prohibiting modification of a signed file without removing the signature.ПриЗаписи(Отказ)— updating metadata, synchronizing the modification date, registering changes for the versioning/data exchange mechanism.ОбработкаЗаполнения(ДанныеЗаполнения, ТекстЗаполнения, СтандартнаяОбработка)— filling inАвтор,ДатаСоздания,ВладелецФайлаwhen created from the owner document.ПередУдалением(Отказ)— deleting the binary content from the volume (whenТипХраненияФайла = НаДиске), clearing versions.
Manager module:
- RLS restriction handlers and defining the selection fields for access control by owner (
ВладелецФайла). - Procedures for selecting the presentation and the icon index by extension.
Common modules of the "File Management" mechanism (SSL):
РаботаСФайлами/РаботаСФайламиСлужебный/РаботаСФайламиСлужебныйСервер— adding a file, reading/writing binary data, checking out for editing (ДатаЗаема,ЗаемщикФайла), releasing, creating versions, working with volumes.ЭлектроннаяПодпись,Шифрование— applying/verifying electronic signatures, encryption/decryption (populating the tabular sectionsЭлектронныеПодписи,ЗашифрованныеДанные, flagsПодписанЭП,Зашифрован).
5. Posting and register records
The object is a catalog, not a document — the posting mechanism is not applicable to it: the catalog has no posting module, does not generate accounting postings, and does not create records in accumulation/accounting registers.
What happens instead of "register records":
- Content storage. Binary data is placed either in the
ХранилищеФайлаattribute (ТипХраненияФайла = ВИнформационнойБазе) or on aТомаХраненияФайловvolume at theПутьКФайлуpath (НаДиске). - Versioning. When versioning is enabled, records are created in the versions catalog;
ТекущаяВерсияpoints to the current one. - Access control (RLS). Rights to an item are computed from rights to
ВладелецФайла(the "Planned Interaction" document). - SSL information registers. The subsystem's utility registers are indirectly involved (for example, for storing dates/sizes/version accounting) — their composition is determined by the SSL version.
RK tax/accounting accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010), the VAT rate of 16%, IIT, mandatory pension contributions, and other parameters do not relate to this object and are not applied here: this catalog does not create accounting records. The corresponding logic is implemented in the configuration's accounting documents (sale, receipt, ESF/SNT, etc.).
6. Related objects and entry on the basis of
| Relationship | Object | Nature of the relationship |
|---|---|---|
| File owner | Документ.ЗапланированноеВзаимодействие |
The file is attached to the document; RLS is inherited from the owner |
| Author / Modified by / Borrower | Справочник.Пользователи, Справочник.УчетныеЗаписиСинхронизацииФайлов |
Auditing and edit locking |
| Storage on disk | Справочник.ТомаХраненияФайлов |
Physical placement of binary data |
| Versions | Catalog of attached-file versions of this owner | Storage of version history |
| ES / encryption | Subsystems "Electronic Signature", "Encryption" (SSL) | Applying signatures and encrypting content |
Entry on the basis of. The classic "Entry on the basis of" mechanism is not used for this catalog. Items are created programmatically — when a file is added from the owner document's form via the "File Management" mechanism API (РаботаСФайлами.ДобавитьФайл(...) and the like), rather than through manual entry by the user.
7. Extension points
- Configuration extensions. Event subscriptions/overriding
ПередЗаписью,ПриЗаписи,ПередУдалениемof the object module — for additional validation, auditing, auto-filling of attributes. - SSL programming interfaces. Working through
РаботаСФайлами,РаботаСФайламиКлиент/Серверinstead of directly modifying the catalog — resistant to updates. - Overridable subsystem modules.
РаботаСФайламиПереопределяемый(and analogs) — points for configuring behavior: allowed extensions, size limits, default volumes, versioning rules. - RLS. Configuring/extending access restrictions through the file owner (
ВладелецФайла) — when customizing rights to CRM documents. - Data exchange and synchronization. The
ДатаМодификацииУниверсальная,УчетныеЗаписиСинхронизацииФайловattributes — integration points when configuring file synchronization between nodes.
Requires verification in the specific build 3.0.74.2: the exact list of the catalog's own forms, the presence of the
ТипХраненияФайла/ХранилищеФайла/ТекущаяВерсияattributes, and the composition of theЭлектронныеПодписи/ЗашифрованныеДанныеtabular sections (version-dependent in SSL).