Directory "ContractsCounterpartiesAttachedFiles" — Technical Description

1. Identification

Purpose. A service (technical) catalog of the “File Management” subsystem of the standard subsystem library (BSP). Stores files attached to the elements of the “Counterparty Contracts” catalog: scanned copies of contracts, additional agreements, acts, specifications, and other accompanying documentation in electronic form. Each catalog element is one attached file along with its metadata (author, dates, size, extension, signature and encryption indicators). The user interacts with the catalog indirectly — through the “Attached Files” command in the counterparty contract card; it is not displayed directly in the sections of the command interface.

Attached files of this type are created automatically for each owner catalog that has file management enabled. Similar objects exist for counterparties, nomenclature, and other configuration objects.

Where to find (navigation link): e1cib/list/Catalog.CounterpartyContractsAttachedFiles — opens a service list of all files; in standard operation, the “Attached Files” command is used from the contract form.

2. Attributes and Table Parts

2.1 Header Attributes (from evidence)

2.2 Typical Attributes for Attached Files in BSP

In addition to those listed in evidence, the attached files catalogs in BSP typically contain several other attributes that ensure versioning and content storage:

The exact set of service attributes for versioning depends on the version of BSP built into 3.0.74.2 — requires verification in the specific delivery.

2.3 Table Parts

The catalog has no table parts. A file is an atomic entity: one catalog element corresponds to one attached file. Data on versions and electronic signatures are placed in separate objects (version register, register of digital signature information), not in table parts.

3. Forms

The service catalog of attached files generally does not have its own forms — work is conducted through the common forms of the “File Management” subsystem of BSP:

If in a specific delivery the forms are still redefined at the catalog level — their purpose coincides with the above; requires verification of the metadata composition 3.0.74.2.

4. Key Module Procedures

No separate BSL code is attached in evidence. For the service catalog of attached files, the main logic is implemented not in the object module, but in the common modules of the BSP file subsystem (FileManagement, ServiceFileManagement, ServiceFileManagementClient, ServiceFileManagementServerCall). Typical handlers and logic points for this type of object:

• ManagerModule.BeforeOpeningForm — substitution of its own forms with common BSP forms.
• ObjectModule.BeforeWriting — filling in service fields: UniversalModificationDate, ModifiedBy, indicators SignedByEP/Encrypted, recalculation of Size.
• ObjectModule.BeforeDeleting — clearing content in the disk volume (deleting the physical file) when deleting an element stored outside the IB.
• Common module ServiceFileManagement — methods AddFile, UpdateFileVersion, TakeFile/ReleaseFile, working with versions, EP, and encryption; these create and modify elements of this catalog.
• Editing Lock Handlers — setting/removing the EditingUser attribute to prevent simultaneous modification of the file by multiple users.

Specific paths path:string are not provided — evidence with the source code of the modules was not supplied; standard handlers characteristic of BSP attached files are listed.

5. Posting and Movements

The catalog is not a document and is not posted — it does not generate registers and accounting entries. This is fundamental for this type of object: attached files store electronic documents, not facts of economic life.

The generated data is of an accounting-technical nature and is created by the file subsystem, not by the posting mechanism:

• recording content in value storage (when stored in IB) or physical file in volume on disk;
• recording versions in the service register/catalog of attached file versions;
• recording information about electronic signatures in the register of digital signature information of BSP.

The accounting meaning (entries according to the typical chart of accounts of the RK) arises not in the file, but in the related owner document. For reference — these entries form sales/purchase documents according to the contract to which the file is attached, for example:

Electronic documents for such a contract (ESF in the ESF IS, SNT) are issued by the relevant configuration objects; the attached file itself only stores their electronic copies/scanned images. All tax amounts in the owner documents are calculated according to the RK norms of 2026 (VAT 16 %, PIT 10 %/15 %, OPP 10 %, OPPR 3.5 %, VOSMS 2 %, OSMS 3 %, CO 5 %, social tax 6 %; MRP 4,325 ₸, MZP 85,000 ₸), but they have no relation to the catalog of files itself.

6. Related Objects and Input on the Basis

Owner (mandatory link):

• Catalog.CounterpartyContracts — defined through the attribute FileOwner; determines which contract the file relates to.

Adjacent objects of the BSP file subsystem:

• Catalog.UsersFileSets / register of versions of attached files — storage of version history;
• RegisterInformation.FileElectronicSignatures (information about EP) — signature data for the attribute SignedByEP;
• Catalog.FileStorageVolumes — volumes for storage “on disk”;
• Enumeration.FileStorageTypes — method of storage;
• Catalog.Users — attributes Author, ModifiedBy, EditingUser.

Input on the basis. The “Input on the basis” mechanism for this catalog is not applied — elements are created exclusively through the “Attached Files” command (adding/uploading/scanning) in the counterparty contract form and programmatically by means of BSP.

7. Extension Points

• File upload/save — redefined through common modules FileManagement* (configuration extension), but with caution: this is BSP code, updated together with the platform library.
• Additional attributes and information — service file catalogs are generally excluded from the composition of objects with additional attributes; if necessary, arbitrary notes are stored in the Description attribute.
• BSP event handlers — subscriptions to events of recording attached files for logging/integration with external EDO, ESF IS, SNT.
• Configuration extension — adding custom attributes/commands to the list form of attached files without removing the configuration from support.
• Access restriction (RLS) — access to files inherits rights to the owner object (counterparty contract); settings... ```