1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | PhoneCallAttachedFiles |
| Full Name | Document.PhoneCallAttachedFiles |
| Alias | — (not set; displayed in the interface as “Attached Files (Phone Call)”) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Subsystem | Standard BSP subsystems → “File Management” |
| Posting | Prohibited (storage object, not an accounting document) |
| Navigation Link | e1cib/list/Document.PhoneCallAttachedFiles |
Purpose. The object is intended for storing files attached to the “Phone Call” documents: audio recordings of conversations, screenshots, PDF notes, and other attachments along with the call card. This is a standard mechanism of the “File Management” subsystem (BSP): each attached file is stored as a separate data element linked to its owner — a specific “Phone Call” document. The user works with files through the attached files panel in the call form; access to the file is restricted by the rights to the owner document.
For each object to which files can be attached, BSP generates its own storage object.
PhoneCallAttachedFilesis such a storage for the ownerDocument.PhoneCall.
2. Attributes of Headers and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Author | ReferenceDirectory.Link.FileSynchronizationAccounts, ReferenceDirectory.Link.Users | Mandatory (ShowError) | The user or synchronization account that created the file. Used for auditing and change history. |
| FileOwner | DocumentReference.PhoneCall | Optional | The phone call document to which the file is attached. Determines the file's location and access control. |
| BorrowDate | DateTime | Optional | Date/time of file being taken for editing (locking). Empty — file is not locked. |
| ModificationDateUniversal | DateTime | Optional | Date of the last modification in UTC. For synchronization and version control. |
| CreationDate | DateTime | Mandatory (ShowError) | Date/time of file creation in the information base. Automatically filled in upon first save. |
| Encrypted | Boolean | Optional | Indicates whether the file is encrypted. A decryption certificate is required when set. |
| ModifiedBy | ReferenceDirectory.Link.FileSynchronizationAccounts, ReferenceDirectory.Link.Users | Optional | The user who last edited the file. |
| ImageIndex | Number | Optional | Index of the file icon in the interface (by extension). |
| Description | String | Optional | Text description of the content/purpose of the file. |
| SignedEP | Boolean | Optional | Indicates the presence of one or more electronic signatures. |
| FilePath | String | Optional | Path to the file in the file system (for storage in the disk volume). |
| Size | Number | Optional | Size of the file in bytes. Automatically filled in upon upload. |
| Extension | String | Optional | File extension (jpg, pdf, mp3, etc.). Determined from the name. |
Standard attributes of the same type of objects (not included in the truncated fragment evidence, present in the standard storage of attached files):
| Name | Type | Purpose |
|---|---|---|
| Name | String | Name of the file without extension; displayed to the user. |
| Number / Date | standard document attributes | Service identification of the file record. |
| StorageText | String / ValueStorage | Extracted text of the file (for full-text search). |
| TextExtracted | Boolean / Enumeration | Status of text extraction. |
| FileStorageType | Enumeration (InInformationBase / InDiskVolumes) |
Method of storing the file body. |
| Volume | ReferenceDirectory.Link.FileStorageVolumes | Volume of storage when stored on disk. |
| FileStorage | ValueStorage | Binary body of the file when stored in the information base. |
2.2 Table Parts
Table parts are absent. The storage of attached files is a “flat” object: one record = one file. The body of the file is stored in the attribute FileStorage (in the information base) or in the file volume (Volume + FilePath); version history is maintained by a separate object (see section 6).
3. Forms
The object does not typically redefine its own forms — work is done through the universal forms of the “File Management” subsystem of BSP:
| Form | Purpose |
|---|---|
Element Form / File Card (AttachedFile from BSP) |
View and edit file properties: name, description, author, dates, encryption and EP indicators. |
| List Form | List of all files attached to calls; called via navigation link. Usually used by the administrator/developer. |
| Select Form | Select previously attached file (in service scenarios). |
| Attached Files Panel | Not a separate object form, but an element of the document form PhoneCall, showing the list of attachments and commands “Add”, “Open”, “Edit”, “Save Changes”, “Sign EP”. |
4. Key Module Procedures
BSL modules in evidence are not attached, so below are typical handlers characteristic of storage objects for attached files in BSP. In the specific assembly 3.0.74.2, their presence should be checked against the object module.
Object Module:
BeforeWriting(Refusal)— filling in service attributes (ModificationDateUniversal,ModifiedBy), checking the correctness of size/extension, processing the indicatorsEncryptedandSignedEP.OnCopying(CopyingObject)— resetting unique characteristics (file body, EP, locking) when copying a record.ProcessingFilling(FillingData, ...)— settingAuthor,CreationDate,FileOwnerwhen programmatically creating through the file management API.OnSettingNewNumber— standard handler for numbering.
Common BSP modules servicing the object:
FileManagement/FileManagementService— programming interface for adding, reading, updating, locking/releasing files.UpdateInformationBaseService— migration of file data during updates.
Requires verification: the exact list of export procedures and signatures depends on the version of BSP embedded in 3.0.74.2.
5. Posting and Movements
The object is not posted and does not generate movements in the registers.
An attached file is an element of the attachment storage, not an accounting document. It has no table parts with amounts, VAT rates, nomenclature, or calculations, therefore it does not generate accounting entries and records in accumulation/information registers. Accordingly, the parameters of tax accounting RK-2026 (VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, deduction for individual income tax 30 MRP, RP accounts 1210/1030/1330/3310/3130/6010/7010, ESF/SNT) do not apply to it — these attributes and movements form actual accounting documents, not the storage of their attachments.
The only “movements” of the object are service records of the “File Management” subsystem:
- record/update of the file body in
FileStorageor in the file volume; - creation of a version history record (see section 6);
- updating the full-text search index based on the extracted text.
The document owner PhoneCall in BK 3.0 is also a CRM document for registering communication and does not make accounting entries — attached files merely complement its card.
6. Related Objects and Input Based On
| Object | Relation |
|---|---|
| Document.PhoneCall | File owner (attribute FileOwner). The file is created from the call form. |
Storage of Versions of Attached Files (…AttachedFilesVersions / BSP version register) |
Stores previous editions of the file; refers to the current record. |
| ReferenceDirectory.FileStorageVolumes | Volume on disk when stored outside the information base. |
| ReferenceDirectory.FileSynchronizationAccounts | Source of the value Author/ModifiedBy during synchronization. |
| ReferenceDirectory.Users | Author/editor of the file. |
| Electronic Signatures (EP Data) | When SignedEP = True — set of signatures of the file. |
Input Based On. The classic “Input Based On” mechanism is not applied for this object. Record creation is performed programmatically through the FileManagement API when adding an attachment to the call (commands of the attached files panel, drag and drop, scanning, uploading from disk), rather than through user input based on.
7. Extension Points
- Configuration Extension. Adding attributes (for example, categories/tags of attachments) and overriding handlers
BeforeWriting,ProcessingFillingthrough object borrowing. - BSP “File Management” Programming Events. Subscriptions to file creation/modification events for custom business logic (indexing, antivirus check, auditing).
- Access Restriction Rules (RLS). Access to the file is inherited from rights to
FileOwner; if necessary — fine-tuning through profiles and access groups. - Storage Volumes. Moving files “in the information base ⇄ in disk volumes” without changing the code — through subsystem parameters.
- Full-Text Search. Configuring text extraction (
TextExtracted,StorageText) for searching the content of attachments. - Electronic Signature. Connecting certificates and configuring verification of EP of attachments (common for the configuration of the EP subsystem; does not directly relate to Kazakhstan's ESF/SNT).