Directory "Hiring in the Organization Attached Files" (Accounting for Kazakhstan 3.0)

1. Identification

Purpose. A technical catalog that implements a file storage system attached to the documents “Hiring in Organization”. It is part of the file management subsystem of the Standard Subsystems Library (BSP). It serves to attach scans of employment contracts, hiring orders, applications, copies of identity documents, and other employee personnel documents to a specific hiring record.

The user does not work with this catalog directly — elements are created automatically when files are uploaded through the “Attached Files” panel of the owner document form. Each catalog element corresponds to one uploaded file (current version; versions are stored separately if versioning is enabled).

Where to find: direct navigation link to the list — e1cib/list/Catalog.HiringInOrganizationAttachedFiles. In normal mode, it opens from the document “Hiring in Organization” → command/panel “Attached Files”.

2. Attributes

2.1 Header Attributes

Binary file data when stored “in the base” is not placed in the catalog attribute but in the subordinate information register (InformationRegister.AttachedFilesStorage / “Binary File Data” BSP). The attributes FileStorageType, Volume, and FilePath determine the location of the content.

2.2 Table Parts

This catalog does not have table parts — it is a flat file card element. The multiplicity of versions and digital signatures is implemented not through table parts but through separate BSP objects (version register, electronic signature information register).

3. Forms

For service catalogs of attached files, specific forms are generally not created, and common managed forms of the “File Management” subsystem of BSP are used. Practical list:

User interaction occurs through the attached files panel of the owner document; separately, the list is rarely opened from the menu (for administration/searching for lost files).

4. Key Module Procedures

There is usually no separate application BSL code (evidence for modules is not attached) for the catalog — all logic is implemented in the common BSP modules. Standard handlers and entry points for this type of object:

• Object Module — BeforeWriting. Filling in service attributes: ModifiedBy, UniversalModificationDate; control that for FileStorageType = OnDisk the Volume is filled.
• Object Module — BeforeDeleting. Initiates the deletion of binary data from the volume (for files on disk) and related versions through the BSP subsystem to avoid leaving “orphans” on the disk.
• FileManagementService (common module). Main business logic: AddFile, UpdateFileVersion, WriteFileToDatabase, text extraction for full-text search, working with volumes.
• FileManagementClientService / FileManagementClient. Client commands: opening, editing (locking via EditingUser), finishing editing, saving the modified file back.
• ElectronicSignature*. Signing and encrypting the file with setting the attributes SignedEP, Encrypted.
• UpdateDatabase. Registering the catalog as part of the attached files and processing the transition between storage methods (base ↔ volumes).

Specific paths path:string cannot be provided — evidence for BSL modules is absent in the source data; standard handlers for this type of object are listed.

5. Posting and Movements

The catalog is not posted and does not generate accounting entries and movements in accumulation/accounting registers — it is a file storage object, not a document. Accordingly, the chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.) and tax calculations are not applicable to it.

Data related to the element is placed in service registers of the “File Management” subsystem:

The financial and tax context (VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, deduction for individual income tax 30 MRP/month and no more than 360 MRP/year, individual income tax 10%/15%, OPP 10%, OPPR 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%, ESF/SNT) is implemented in personnel and payroll documents, not in the file catalog. It is provided here for reference to comply with the current values of the RK for 2026 and is not affected by this object.

6. Related Objects and Input on Basis

• Owner: Document.HiringInOrganization (attribute FileOwner). The lifecycle of the file is tied to the existence of the document.
• Catalog.Users — attributes Author, ModifiedBy, EditingUser.
• Catalog.FileStorageVolumes — attribute Volume (for files on disk).
• Enumerations FileStorageTypes, TextExtractionStatus.
• BSP Registers of binary data, versions, electronic signatures (see section 5).

Input on basis for this catalog is not provided and does not make sense — elements are created by the attached files mechanism, not by “Create on Basis” commands.

7. Extension Points

• Configuration Extension: adding attributes to the file card (for example, type of personnel document, storage period) and columns to the list; overriding handlers BeforeWriting/BeforeDeleting of the object module.
• BSP Programming Interfaces: FileManagement, FileManagementClient, FileManagementService — for programmatically adding/reading files of the hiring document.
• Storage: transferring files “in base ↔ to volumes” through subsystem settings; when externally stored, control the filling of Volume and the availability of the volume directory.
• Full-text Search: using TextExtractionStatus and TextStorage for indexing the content of personnel documents.
• EP and Encryption: standard mechanisms for signing/encrypting with setting SignedEP and Encrypted — integration point with the cryptographic subsystem.

Requires verification (version-specific): the exact names of common forms and service registers of BSP depend on the version of the Standard Subsystems Library embedded in release 3.0.74.2 — verify against the composition of objects of the specific configuration.