1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | OrganizationBusinessTripsAttachedFiles |
| Full Name | Catalog.OrganizationBusinessTripsAttachedFiles |
| Synonym | — (not available; technical object) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Hierarchy | None (linear list) |
| Owner | Document OrganizationBusinessTrips (via attribute FileOwner) |
| Subsystem | “File Management” (BSP) |
Purpose. The catalog stores files attached to the documents of “Organization Business Trips”: orders for business trips, advance reports, electronic tickets, hotel bills, boarding passes, and other scans confirming the fact of the business trip and incurred expenses. The files are managed by the HR department, accounting, and managers. The catalog is technical — users do not open it directly; all work is done from the owner document card through the standard mechanism of attached files of the 1C platform.
Where to find (service):
e1cib/list/Catalog.OrganizationBusinessTripsAttachedFiles
In normal mode, it opens not a list, but the “Attached Files” panel on the document form “Organization Business Trips”.
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Author | CatalogReference.Users | Mandatory (ShowError) | The user who uploaded the file. Automatically filled upon creation. |
| FileOwner | DocumentReference.OrganizationBusinessTrips | Not checked | Reference to the business trip document to which the file is attached. Defines ownership. |
| UniversalModificationDate | DateTime | Not checked | Date/time of the last modification of the file in UTC. Used for synchronization and tracking changes. |
| CreationDate | DateTime | Mandatory (ShowError) | Date/time of the initial upload. Automatically filled. |
| Encrypted | Boolean | Not checked | Indicator that the file content is encrypted. |
| ModifiedBy | CatalogReference.Users | Not checked | The user who last modified the file or card. Automatically updated. |
| ImageIndex | Number | Not checked | Index of the file icon in the interface (by extension). |
| Description | String | Not checked | User's text comment on the file content. |
| SignedEP | Boolean | Not checked | Indicator of the presence of an electronic signature (for legally significant documents). |
| FilePath | String | Not checked | Path to the file on the storage volume. Empty when stored in the database. |
| Size | Number | Not checked | Size of the file in bytes. |
| Extension | String | Not checked | Extension without a dot (pdf, xlsx, jpg). Defines the type and application for opening. |
| EditingBy | CatalogReference.Users | Not checked | The user who has taken the file for editing (loan). Empty if the file is free. |
| TextExtractionStatus | EnumerationReference.TextExtractionStatuses | Not checked | Status of text extraction for full-text search: Not extracted / Extracted / Error. |
| TextStorage | ValueStorage | Not checked | Extracted text of the file in compressed form (for search). |
Service owner field. The attribute Owner (standard for the catalog with an owner) in attached files is not used as primary — the ownership to the document is defined by the application attribute FileOwner. This is a typical BSP scheme: the catalog of attached files is not “tightly” subordinate to the owner but stores a reference to the document as an explicit attribute, allowing one document to have an arbitrary number of files.
2.2 Table Parts
Table parts are absent. The binary content of the file in the catalog is not stored in the attribute — it is placed either in the file storage volumes (then FilePath is filled), or in a separate information register of binary data (see section 5). This is the standard architecture of the “File Management” subsystem.
3. Forms
The catalog usually does not contain its own forms and uses the common forms of the “File Management” subsystem. Possible/used forms:
| Form | Purpose |
|---|---|
| ElementForm (if available) | File card: description, author, dates, size, signature/encryption indicators, buttons “Open”, “Edit”, “Finish Editing”, “Save As…”. |
| ListForm (if available) | Service list of all files in the catalog; not used in application work. |
Common form AttachedFiles (BSP) |
Panel with a list of files, embedded in the document form “Organization Business Trips”. Main user interaction point. |
Common form AttachedFileCard (BSP) |
Unified file card for all catalogs of attached files in the configuration. |
Application forms specifically for this catalog are usually absent; display and editing are delegated to the common BSP forms, which makes the object “technical”.
4. Key Procedures of Modules
Application code in the module of the catalog itself is usually absent or minimal; all logic is transferred to the common BSP modules. Typical handlers and procedures for an object of this type:
- ObjectModule → BeforeWriting — recording the user in
ModifiedBy, updatingUniversalModificationDate, controlling file occupancy (EditingBy). - ManagerModule — service functions for obtaining representation, image index by extension.
- Common module FileManagement / FileManagementService — adding a file (
AddFile), taking/releasing for editing (TakeFile,FinishEditing), saving a new version, extracting text for full-text search (ExtractText), checking rights. - Common module FileManagementClient — opening a file in an external application, saving to disk, interactive work with the attached files panel.
- Handler FillingProcessing — setting
Author,CreationDate,FileOwnerwhen created from the owner document.
Exact paths
path:stringare not provided: the attached evidence contains only the structure of attributes; BSL fragments of the module are not provided. The listed procedures are the standard implementation of the “File Management” subsystem for catalogs of attached files.
5. Movements and Registers
The catalog is not conducted — the concept of conducting and accounting entries for catalogs is not applicable. The object does not generate its own movements in accumulation or accounting registers.
Data related to the file is stored in auxiliary registers of the “File Management” subsystem:
| Information Register | What it stores |
|---|---|
BinaryFileData (or storage in volumes via FilePath) |
The binary content of the file itself. |
FileVersions / related catalog of versions |
History of versions (if versioning is enabled). |
| Register of text extraction statuses | Reflection of the full-text index (duplicated by the attribute TextExtractionStatus). |
Accounting context (at the owner document, not at the catalog). Entries are generated by the document OrganizationBusinessTrips, not the file. According to the typical chart of accounts of the RK, business trip and related expenses are reflected, for example: 1250 (short-term employee debt on advances/reports) and expense accounts; when purchasing services with VAT, 3130 (VAT payable, rate 16% in 2026), 3310 (KZ to suppliers), 1030 (money in current accounts), income/cost of operations — 6010/7010. Accruals for the traveling employee are subject to RK 2026 regulations: PIT 10% (15% over 8,500 MRP annual income), basic deduction for PIT 30 MRP per month (not more than 360 MRP per year) at MRP = 4,325 ₸ and MZP = 85,000 ₸; OPE 10% (base ceiling 50 MZP), OPEP 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%. Electronic documents for services acquired during the business trip are issued through ESF (IS ESF) and STS. These amounts have no relation to the catalog of attached files and are provided as the context of the owner document.
6. Related Objects and Input Based On
- Document
OrganizationBusinessTrips— owner of the files (FileOwner). The only source and access point. - Catalog
Users— attributesAuthor,ModifiedBy,EditingBy. - Enumeration
TextExtractionStatuses— attributeTextExtractionStatus. - Common objects of the “File Management” subsystem BSP — common forms, registers of binary data and versions, storage volumes.
Input based on for this catalog is not provided: elements are created only through the mechanism of attaching a file to the owner document (button “Add” / drag-and-drop / from scanner in the files panel). Manual creation of an element in the catalog list is not applied in application work.
7. Extension Points
- Event subscriptions
BeforeWriting/OnWritingof the object — additional validation (for example, prohibition of deleting signed EP files, control of extensions/size). - Extension of common BSP modules (
FileManagementService,FileManagement) — overriding storage rules, text extraction, restrictions on file types. - Overridable BSP modules (
FileManagementOverridable) — standard customization point of the logic of attached files without modifying standard modules. - RLS / access rights — limiting visibility of files by owner document and organization through access group profiles.
- Additional attributes/information — through the “Properties” subsystem if necessary for file classification.
- Storage volumes of files — moving binary data to the file system to unload the database (filling
FilePath).
Version-specific (requires verification on specific version 3.0.74.2): whether the storage mode is enabled in volumes or in the database, whether versioning and full-text search are activated — these are configuration parameters, not object properties.