1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | MainAssetsAttachedFiles |
| Full Name | Catalog.MainAssetsAttachedFiles |
| Synonym | “Attached Files (Main Assets)” |
| Configuration | Accounting for Kazakhstan, ed. 3.0.74.2 |
| Source Subsystem | “File Management” (BSM) |
| File Owner | Catalog.MainAssets |
Purpose. The catalog is designed to store attached files (documents, images, scans) to the elements of the catalog Main Assets. It is used by accountants, warehouse workers, and other employees to attach technical passports, photographs, inventory cards, invoices, and other documentation to specific fixed assets. It provides centralized file storage with versioning, electronic signatures, and encryption. This is a standard object of the attached files mechanism of BSM, generated for the owner “Main Assets”; its name is constructed according to the template <OwnerName>AttachedFiles.
Where to find:
e1cib/list/Catalog.MainAssetsAttachedFilesIn practice, the list is rarely opened separately — work is done from the element/list form of the catalog Main Assets through the “Files” command or the attachments panel.
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Author | Catalog.Users | Mandatory (ShowError) | User who uploaded the file. Audit and access control. |
| FileOwner | Catalog.MainAssets | Not checked | Reference to the fixed asset object to which the file is attached. The main attribute of the “file — object” link. |
| UniversalModificationDate | Date and time | Not checked | Universal date of the last modification of the file (UTC). Synchronization and control of version relevance. |
| CreationDate | Date and time | Mandatory (ShowError) | Date and time of the first upload. Set automatically, not changed. |
| Encrypted | Boolean | Not checked | Indicator of encryption by cryptographic means. Access to the file is possible only with a certificate. |
| ModifiedBy | Catalog.Users | Not checked | User who last modified the file or attributes. Updated automatically. |
| ImageIndex | Number | Not checked | Index of the file icon (by extension) for display in lists. |
| Description | String | Not checked | Arbitrary user comment on the file. |
| SignedEP | Boolean | Not checked | Flag of the presence of an electronic signature. Set automatically when adding EP. |
| FilePath | String | Not checked | Path to the file on the volume (for storage “In volumes on disk”). Formed automatically. |
| Size | Number | Not checked | Size of the file in bytes. Control of quotas and analysis of occupied space. |
| Extension | String | Not checked | Extension without a dot (pdf, jpg, docx). Determines the type and available operations. |
| EditingUser | Catalog.Users | Not checked | User who has taken the file for editing. Mechanism for blocking simultaneous modifications. |
Additionally, for this type of object, standard service attributes are CurrentVersion (link to the current version of the file), FileStorageVolume, and FileStorage (binary data when stored in the IB) — the composition depends on the configuration of the file storage method.
2.2 Table Parts
The object does not have its own table parts. File versions are stored in the subordinate information register / version catalog of the “File Management” subsystem, not in the table part.
3. Forms
| Form | Purpose |
|---|---|
| ElementForm | Card of the attached file: description, author, dates, size, EP/encryption indicators; commands for viewing, editing, saving to disk. |
| ListForm | List of files, usually in the context of the owner-fixed asset; filtering by owner, author, extension. |
| SelectionForm | Selecting an existing file in other forms and processes. |
In the standard configuration, the card and lists are usually implemented with common forms of the file management subsystem (CommonForm.AttachedFileForm, panel “Attached Files”), rather than individual forms of this catalog.
4. Key Module Procedures
No separate application evidence for BSL modules of the object is attached. For this type of object, the logic is transferred to the common modules of the “File Management” subsystem (BSM). Standard handlers:
- ObjectModule →
BeforeWriting— updating attributesModifiedBy,UniversalModificationDate, recalculatingImageIndexby extension, controlling file occupancy for editing. - ObjectModule →
BeforeDeleting— clearing binary data/file in the volume, deleting versions and signatures. - Common module
FileManagement/FileManagementService— adding a file, creating a version, occupying/releasing for editing, saving to disk, working with volumes. - Common module
FileManagementClient— opening, viewing, editing in an external application. - Mechanisms ElectronicSignatures (
SignedEP) and Encryption (Encrypted) — from the corresponding subsystems of BSM.
Requires verification (versioned): the exact list of procedure names and their signatures in common modules depends on the version of BSM embedded in 3.0.74.2.
5. Posting and Movements
The object is a catalog and is not posted — it does not generate documents and accounting entries, does not create movements in accumulation/accounting registers. Rates and accounts of the RK (VAT 16%, accounts 1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.) are not applicable to this object: it only stores files attached to the elements of the catalog “Main Assets” and does not participate in tax/accounting.
Indirectly related are the service registers of the file management subsystem (information register with file versions, registers for storing signatures and encryption data), updated when recording an element.
6. Related Objects and Input Based On
- Catalog.MainAssets — file owner; all work is done from its forms (attribute
FileOwner). - Catalog.Users — attributes
Author,ModifiedBy,EditingUser. - BSM Subsystems — “File Management”, “Electronic Signatures”, “Encryption”, “File Storage” (volumes on disk).
- Input based on is not provided for the service file catalog: elements are created by adding/uploading files commands, not by the “Input Based On” mechanism.
7. Extension Points
- Configuration Extension: adding custom attributes to the file card (for example, “Type of Fixed Asset Document”, “Inventory No.”), additional commands in the attached files form.
- Event Subscriptions
BeforeWriting/BeforeDeletingof the catalog — for custom auditing or integration with an external archive. - Additional Attributes and Information (subsystem “Properties”) — if necessary, to categorize attachments.
- Storage Volume Configuration — moving files from IB to volumes on disk (attributes
FilePath,FileStorageVolume). - Access Restriction (RLS) — by owner-fixed asset and author, integration with access group profiles.
Do not directly modify the composition of service attributes in the standard configuration — use extensions to maintain the updateability of the “File Management” subsystem.