1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | EmployeesOrganizationsAttachedFiles |
| Full Name | Catalog.EmployeesOrganizationsAttachedFiles |
| Synonym | “Attached Files (Employees)” |
| Configuration | Accounting for Kazakhstan, ed. 3.0.74.2 |
| Subsystem | File Management (BSP, “File Operations”) |
| Owner | Catalog.EmployeesOrganizations (via attribute FileOwner) |
| Where to Find | navigation link e1cib/list/Catalog.EmployeesOrganizationsAttachedFiles |
Purpose. The catalog is intended for storing files attached to employee cards of organizations: scans of documents (identity card, work book, diplomas, certificates), photographs, applications, and other personnel accounting files. It is used by HR specialists and accountants when working with personal data. Access to files is controlled by the same rights as access to employee cards (read/write).
The catalog is service: it does not have its own menu item, files are opened and added through the employee card in the personnel accounting section. The direct navigation link is mainly used for administration and debugging.
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
Author |
CatalogReference.Users | Mandatory (ShowError) | The user who initially uploaded the file. Automatically filled upon creation. |
FileOwner |
CatalogReference.EmployeesOrganizations | Optional | The employee to whose card the file is attached. Defines context and access rights. |
UniversalModificationDate |
Date and Time | Optional | Date of the last modification of the file in UTC. For synchronization and relevance control. |
CreationDate |
Date and Time | Mandatory (ShowError) | Date and time of record creation. Automatically filled. |
Encrypted |
Boolean | Optional | Indicates that the file content is encrypted. |
ModifiedBy |
CatalogReference.Users | Optional | The user who last modified the file or its attributes. |
ImageIndex |
Number | Optional | Index of the icon for display in lists (depends on extension and state). |
Description |
String | Optional | Arbitrary comment on the file. |
SignedByEP |
Boolean | Optional | Indicates the presence of an electronic signature. Important for legally significant documents. |
FilePath |
String | Optional | Path to the file on the storage volume (when stored on disk/in a network folder). |
Size |
Number | Optional | Size of the file in bytes. For storage volume control. |
Extension |
String | Optional | File extension (pdf, docx, jpg, etc.). Determines the way of opening. |
EditingBy |
CatalogReference.Users | Optional | The user who has taken the file for editing (blocks changes by others). |
TextExtractionStatus |
EnumerationReference.TextExtractionStatuses | Optional | Status of background text extraction for full-text search. |
TextStorage |
Value Storage | Optional | Extracted text content of the file for searching. |
The standard attribute Name is used as the file name without the extension.
2.2 Table Parts
The catalog does not have its own table parts. This is typical for objects of the type “AttachedFiles” in BSP: one record = one attached file.
2.3 Storage of Binary Content
The body of the file is not stored in the attributes of the catalog. Depending on the settings of the file storage volume:
- In the information base — through the subordinate information register of the attached files storage (binary data in a resource of type “Value Storage”);
- On volumes — the file is located on the disk/in a network folder, and the path is recorded in the attribute
FilePath.
3. Forms
| Form | Purpose |
|---|---|
ElementForm |
Card of the attached file: name, description, author, dates, size, extension, encryption/signature indicators; commands for opening, saving, editing, signing by EP. |
ListForm |
List of files attached to a specific employee (usually embedded in the EmployeesOrganizations card). |
SelectForm |
Selecting an existing file (rarely used, during exchange/migration). |
The main user scenario is implemented not by the catalog's own forms, but by common forms of the “File Operations” subsystem of BSP (AttachedFiles, FileViewForm, etc.), which are universal for all catalogs of attached files in the configuration.
4. Key Module Procedures
Evidence with BSL text for this object is not attached, so below are the typical handlers of this type of object in BSP. Specific signatures are clarified according to the modules of your version.
Object Module (ObjectModule):
BeforeWriting(Refusal)— updating service attributes (ModifiedBy,UniversalModificationDate), controlling file occupancy for editing.BeforeDeleting(Refusal)— deleting related binary content (from the storage register or from the volume).OnCopying(CopyingObject)— resetting the indicatorsEditingBy,SignedByEP, and service dates.
Mechanism of Attached Files (common modules of BSP):
FileOperations/FileOperationsService— adding, opening, saving, updating files; extracting text for full-text search (fillingTextStorage, managingTextExtractionStatus).AttachedFiles— programming interface for adding a file to the owner (AddFile), obtaining a list of employee files.- Working with EP — signing/verifying the signature, setting the indicator
SignedByEP.
5. Posting and Movements
The catalog is not a document, it does not perform postings and movements in registers and does not generate entries in accounting/tax accounting. For this reason, the chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010), rates and deductions (VAT 16%, PIT 10%/15% with a threshold of 8,500 MRP, OPE 10% with a base ceiling of 50 MZP, OPR 3.5%, VOSMS 2%, OMS 3%, CO 5%, social tax 6%, MRP 4,325 ₸, MZP 85,000 ₸, basic deduction for PIT 30 MRP/month, but not more than 360 MRP/year) do not apply to this object — they relate to calculation and accounting documents of the configuration, not to the file storage.
The only “movements” related to the catalog are the recording/deletion of binary content:
- in the information register of the attached files storage (when stored in the IB), or
- in the file system of the volume (when stored on disk), with the fixation of
FilePath.
6. Related Objects and Input Based on
Catalog.EmployeesOrganizations— owner of the files; attachment, viewing, and deletion of files are performed from its card.Catalog.Users— attributesAuthor,ModifiedBy,EditingBy.Enumeration.TextExtractionStatuses— status of background text extraction.- Information register of the attached files storage and file storage volumes — physical storage of content.
- BSP mechanisms: “File Operations”, “Full-text Search”, “Electronic Signatures”.
Input based on is not applied for the service catalog of attached files. Record creation occurs only through the file attachment mechanism from the employee card.
7. Extension Points
- Configuration Extension — adding attributes (for example, document type, validity period) and modifying
ElementFormwithout removing from support. - Programming Interface
AttachedFiles— mass addition/export of employee files in custom processing. - Subscriptions to events
BeforeWriting/BeforeDeletingof attached files objects — for auditing, additional control of rights, or integration. - Access Control (RLS) — configuring file visibility through rights to the owner (
EmployeesOrganizations). - Full-text Search — using
TextStorageandTextExtractionStatusfor searching through the content of attachments.
Note. The presence of specific attributes and forms depends on the version of BSP within the edition 3.0.74.2 — the composition of service attributes of attached files is version-specific and is clarified according to the configurator.