Document "Personnel Movement of Organizations Attached Files" - Technical Description

1. Identification

Purpose. A service object of the “Attached Files” subsystem of the standard subsystem library (BSP). It stores files attached to the “Personnel Movement of Organizations” documents — scans of orders, PDFs, images, Word/Excel documents, etc. Each element is one attached file along with metadata: author, creation date, size, extension, encryption signs, and electronic signature. The user interacts with the object indirectly — through the “Attached Files” command in the owner document form, rather than through a separate list. It is used by HR specialists and accountants for documentary confirmation of employee transfers between holding organizations and operations during the reorganization of legal entities.

This is a metadata storage object for the file. The file body itself is stored either in the value storage attribute (FileStorage, when stored in the IB), or on a disk volume (when FileStorageType = OnDiskVolumes, then the path is in the attribute FilePath).

Where to find: navigation link e1cib/list/Document.PersonnelMovementOrganizationsAttachedFiles (for service viewing/administration; in normal mode, it opens from the owner document card).

2. Header Attributes and Table Parts

2.1 Header Attributes

Additionally, according to the standard BSP model, the object has the attributes: Name (file name without extension), FileStorageType (in IB / on disk volumes), FileStorage (ValueStorage — file body when stored in IB), TextStorage / Text (extracted text for full-text search), HashValue, VersionRecordUnavailable.

2.2 Table Parts

The object does not have its own application table parts — it is a single-element storage for one file. File versions, electronic signatures, and encryption certificates are stored in subordinate information registers of the file management subsystem (see section 5), not in the document's table parts.

3. Forms

A separate object of this purpose usually does not have independent user forms — the card and list are taken from the “Attached Files” subsystem of the BSP:

4. Key Module Procedures

In the attached evidence, fragments of BSL code are absent, so below are typical handlers for objects of this type (subsystem “Attached Files” BSP). In the specific assembly 3.0.74.2, the composition may differ — it is specified in the configurator.

Object Module:

• BeforeWriting(Refusal) — control of filling Author, CreationDate; fixing UniversalModificationDate, ModifiedBy; recalculation of Size, Extension.
• OnCopying(CopyingObject) — reset of blocking signs (EditingUser), signatures, and versions for the copy.
• FillingProcessing(FillingData) — setting FileOwner, Author = Users.CurrentUser(), CreationDate = CurrentSessionDate().

Manager Module / Server Calls of BSP (FileManagement, AttachedFiles):

• adding a file from the file system with text extraction for full-text search;
• retrieving/saving the file body (FileStorage or disk volume);
• capturing and releasing the file for editing (EditingUser);
• working with versions, applying and verifying electronic signatures, encryption/decryption.

5. Posting and Movements

The object is not a posting document in the accounting sense and does not generate accounting entries and movements in accumulation registers. It is a storage for an attached file: it has no posting attribute, no movements in accounting, mutual settlements, VAT, etc.

What happens when working with the object:

• record/update of the storage element and its metadata;
• recording of subordinate information registers of the file management subsystem: file versions, electronic signatures, encryption certificates, editing signs.

No entries of the typical chart of accounts of the RK are generated by this object. Accounting movements (income 6010, cost 7010, receivables 1210, cash 1030, goods 1330, payables 3310, VAT payable 3130 at the rate of 16%), as well as calculations for PIT, OPE, OPEP, VOSMS, OMS, SO, and social tax are performed by specialized documents of the configuration, not by the file storage. They are mentioned solely as a reference that this service object has no relation to them.

6. Related Objects and Input Based On

Input Based On. Not provided and not applied: the object is created only as an attached file of the owner document through the attachments interface. There is no independent input based on.

7. Extension Points

• Configuration Extensions (without removal from support): subscription to the event BeforeWriting of the object — additional validation of file type/size/extension, restriction of acceptable attachment formats for personnel documents.
• Event Subscriptions of the type DocumentReference.PersonnelMovementOrganizationsAttachedFiles — synchronization with external storage/archive, automatic text extraction, tagging.
• Access Restrictions (RLS): setting rights to view/edit files through Author and FileOwner — delineation of access for HR specialists and accountants.
• BSP Mechanisms: overridable modules of the “File Management” subsystem (storage rules on disk volumes, maximum size, antivirus check, viewing formats).
• Full-text Search: using the extracted text of the file in search scenarios.

“Requires verification” (version-specific for 3.0.74.2): the exact composition of storage attributes (FileStorage vs storage on volumes), the presence of separate ElementForm/ListForm and specific names of subordinate information registers for versions/signatures — specified in the configurator of this assembly.