Hotkeys Directory (Catalogs.ГорячиеКлавиши) — Technical Description

1. Identification

Nature of the object. "Hotkeys" belongs to the service catalogs of the SSL (Standard Subsystems Library) subsystem built into UT for Kazakhstan. It is not part of operational, statutory, or tax accounting: it is not a document, is not posted, does not generate register movements, and does not affect the calculation of taxes, cost, or settlements. All Kazakhstan calculation parameters (VAT 16%, MCI 4,325 KZT, minimum wage 85,000 KZT, individual income tax, mandatory pension contributions, social tax, etc.) are not related to this object — they are implemented in accounting documents and calculation registers, not in an interface settings catalog.

2. Header attributes and tabular sections

The catalog is built according to the standard scheme typical for SSL service catalogs. The set of attributes is minimal; the specific composition in edition 3.4.5.21 requires verification against the configurator (see FAQ), but according to the standard model it is as follows.

2.1. Standard attributes

2.2. Header attributes (applied)

2.3. Tabular sections

For a service catalog of this purpose, tabular sections are typically absent. If a specific build contains a tabular section for a "command → combination" list, it has the structure: Команда (String), Комбинация (String), Активность (Boolean). The presence and exact composition of the tabular section is version-specific — verify against the configurator.

3. Forms

If specialized forms are not defined in the metadata, the platform uses auto-generated list and item forms — this is sufficient for the object's service purpose.

4. Key module procedures

No program code (BSL) was provided in the attached evidence — only the naznachenie facet. Therefore, below are the typical handlers for an SSL service catalog; verify the specific module lines against the configurator of edition 3.4.5.21.

Object module (МодульОбъекта)

• ОбработкаЗаполнения(ДанныеЗаполнения, ТекстЗаполнения, СтандартнаяОбработка) — filling default attributes upon creation.
• ПередЗаписью(Отказ) — validation of key combination correctness and uniqueness before writing.
• ПроверкаЗаполнения(Отказ, ПроверяемыеРеквизиты) — verification of required fields (name, combination).

Manager module (МодульМенеджера)

• ОбработкаПолученияФормы(...) — substitution of the default form if needed.
• Functions for retrieving predefined items, if any are defined.

List/item form module

• ПриСозданииНаСервере(Отказ, СтандартнаяОбработка) — initial form setup, setting element availability.
• ПриОткрытии(Отказ) — additional interface configuration.
• Field event handlers (СочетаниеКлавишПриИзменении, etc.) — validation of the entered combination.

The actual names and locations of procedures (path:line) will appear in the description once BSL evidence is loaded from the configurator.

5. Posting and movements

The "Hotkeys" catalog has no posting and generates no movements. This is a non-accounting service object.

• It does not populate any registers (accumulation, information, accounting, calculation).
• It does not generate entries in the standard chart of accounts for Kazakhstan. For comparison, accounting objects in UT for Kazakhstan use accounts: 1210 (short-term receivables from customers), 1030 (cash in current accounts), 1330 (inventory), 3310 (payables to suppliers), 3130 (VAT payable, 16% rate), 6010 (sales revenue), 7010 (cost of sales) — but these do not apply to this catalog.
• Electronic documents (e-invoices in the ESF IS, waybills) are not generated by the catalog.
• Tax indicators (VAT 16%, individual income tax at 10%/15%, mandatory pension contributions 10%, employer pension contributions 3.5%, mandatory social health insurance contributions (employee) 2%, mandatory social health insurance contributions (employer) 3%, social contributions 5%, social tax 6%, standard deduction of 30 MCI/month and no more than 360 MCI/year at MCI 4,325 KZT) are implemented in accounting documents and calculation registers, not here.

Conclusion: the "movements" section for this object is empty by definition of its type and purpose.

6. Related objects and entry based on

• Entry based on: not provided (a service catalog is neither a basis for documents nor vice versa).
• Relations: the object belongs to the interface/SSL configuration subsystem. It can be used as a source of values when configuring form and desktop commands.
• Subordination: an independent catalog; it typically does not require an owner or hierarchy given its purpose.
• Use in accounting chains (orders, sales, e-invoices/waybills, settlements) — absent.

7. Extension points

For customizations, use the configuration extension mechanism (without removing the object from support):

1. Adding attributes — new fields for a set (e.g., scope of application of the combination) via a catalog extension.
2. Overriding forms — extending the list/item form: adding columns, filters, combination validation commands.
3. Intercepting object module handlers — &Before/&After/&Instead for ПередЗаписью, ОбработкаЗаполнения, ПроверкаЗаполнения.
4. Event subscriptions — on catalog item recording, for logging changes to interface settings.
5. Manager module — extending methods for retrieving/selecting predefined sets.

Since the object is a service object and does not affect accounting, extensions are safe from the standpoint of statutory and tax accounting in Kazakhstan.