Directory "Interaction Bookmarks" (Catalogs.InteractionBookmarks) — Accounting for Kazakhstan 3.0.74.2

1. Identification

Purpose. The catalog stores personal user settings for filters and data views when working with the interactions subsystem. Each element is a named "bookmark" with a saved set of filters, sorts, groups, and conditional formatting, configured through the data composition system (DCS) mechanism. Bookmarks allow the user (primarily the sales manager working with CRM) to quickly switch between frequently used views of the interaction list without reconfiguring the filters.

This is a service catalog: it does not participate in accounting, does not store monetary/quantitative data, and is not related to currency, taxes, or the chart of accounts. Accordingly, issues related to rates (VAT 16%, PIT, social tax 6%, etc.), electronic documents (ESF, SNT), and accounts of the standard chart of accounts of the RK do not pertain to this object — it only configures the appearance of lists in the "Interactions" subsystem.

Where to find in 1C: section "Standard subsystems" → "Interaction Bookmarks". Direct navigation link: e1cib/list/Catalog.InteractionBookmarks. There is usually no explicit menu item for opening — access is provided from the interactions interface through the bookmarks mechanism.

2. Attributes and Table Parts

2.1 Header Attributes

Standard attributes. In addition to the explicit attribute, standard attributes of the catalog are used:

• Code — unique code of the element (visible in the ElementForm through the input field);
• Name — displayed name of the bookmark, by which the user selects it;
• other standard attributes (Reference, DeletionMark, Predefined, etc.) — according to the general model of the catalog.

2.2 Table Parts

Table parts are absent. All information about the bookmark is encapsulated in the attribute SettingsComposer (serialized DCS settings within ValueStorage).

3. Forms

4. Key Module Procedures

No specific application BSL code (evidence with paths and strings) for this catalog is attached — the object is service, its logic relies on standard platform mechanisms and the general DCS module. Below are typical handlers characteristic of a catalog of this type (data composition settings form).

Element form module (ElementForm):

• OnCreateOnServer — form initialization: unfolding saved settings from the attribute SettingsComposer into the form composer (SettingsComposer), configuring available filter fields based on the data source composition of the interactions subsystem.
• OnReadOnServer — restoring the settings composer when opening an existing element (deserialization ValueStorage → SettingsComposer.Settings).
• BeforeWriteOnServer — collapsing the current settings of the composer back into the attribute SettingsComposer (Settings → New ValueStorage(...)) before saving the element.
• Handlers of the composer element (e.g., SettingsComposerSettingsOnChange) — recording the fact of changes in filters/sorts for subsequent writing.

List form module (ListForm):

• OnCreateOnServer — setting up the dynamic list of bookmarks, limiting visibility to the bookmarks of the current user (when using such a storage scheme).

Object / manager module:

• Application code is usually absent; standard catalog writing mechanisms are used.

Requires verification (version-specific): exact names of procedures and the presence of filtering bookmarks by the current user in configuration 3.0.74.2 — they depend on the implementation of the "Interactions" subsystem of the specific version of the BSP.

5. Posting and Movements

The catalog is not posted and does not generate movements in registers. This is a category of the object "Catalog", not a document: it has no posting attribute, no sets of register records, it does not generate accounting entries.

Accordingly, this object does not refer to accounting registers and does not generate records in the standard chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.) — these accounts and related amounts (VAT at a rate of 16%, income, cost) pertain to accounting documents of the configuration, but not to the settings for list representation.

The only result of recording an element is the saving of serialized DCS settings in the attribute SettingsComposer of the catalog table.

6. Related Objects and Input Based On

• Interactions Subsystem — consumer of settings: interaction list forms (calls, meetings, emails, scheduled interactions) apply the selected bookmark as a set of filters/sorts.
• Data Composition System (DCS) — platform mechanism, whose settings are serialized in the attribute SettingsComposer.
• Users — bookmarks are personal; the connection with the user is implemented through storage/filtering in the interface.

Input based on: not provided. The catalog is neither a basis nor a result of input based on other objects.

7. Extension Points

• Extension of filter composition. Through modification of the data source of interaction lists, new fields can be added that will become available when configuring the bookmark in ElementForm.
• Form subscriptions/handlers. In the configuration extension, OnCreateOnServer/BeforeWriteOnServer forms can be intercepted to add custom logic (e.g., default bookmark templates, change audit).
• Additional attributes/information. As with any catalog, the mechanism for additional attributes and information of the BSP can be connected (if the object is included in the corresponding composition).
• Access restriction (RLS). If necessary to limit the visibility of bookmarks between users, the logic can be enhanced through access restrictions at the record level.
• Change of representation. Configuration of the element form (available fields of the composer, conditional formatting) — a typical customization point without interfering with the object module.