Directory "Types of Contact Information" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog is a system classifier of types of contact data linked to various accounting objects (counterparties, organizations, employees, individuals, banks, warehouses, etc.). It defines which types of contact information (phones, addresses, e-mail, websites, etc.) can be recorded for each type of object. The catalog is used by the platform and the "Contact Information" subsystem automatically when working with the information register ContactInformation and with input forms for contact data on objects.

It is typically filled out during the initial setup/implementation of the configuration and is rarely changed in operation. Users rarely access it directly — work is done through the interfaces of the objects themselves, where predefined types of contact information are already utilized.

Where to find in 1C:

• Section "Administration" → "Types of contact information".
• Navigation link: e1cib/list/Catalog.ContactInformationTypes

2. Attributes and Table Parts

2.1 Header Attributes

Standard attributes. In addition to those listed, the catalog contains standard attributes: Code, Name, Parent (in hierarchy), DeletionMark, Predefined, Reference, and other system fields. Many types of contact information in the standard delivery are predefined elements — their set is defined by the configuration and ensures the operation of standard forms.

Additionally, the "Contact Information" subsystem of BSL stores a set of service settings for each type (for example, flags "View only", "Allow multiple values", "Check correctness of filling", "Store change history", "Always show"). In a specific version, these settings may be implemented as separate attributes of the catalog or as parameters of the type description — this is version-specific and requires verification in the specific build 3.0.74.2.

2.2 Table Parts

Table parts are absent.

3. Forms

The catalog contains three forms:

Key form for the user: ElementForm.

4. Key Module Procedures

No direct evidence in the text of the modules (BSL) for this build is attached. Below are typical handlers characteristic of the catalogs of the "Contact Information" subsystem of BSL; their presence and exact implementation may vary by versions.

Module of the form ElementForm:

• OnCreateOnServer — initial setup of the form: availability/visibility of attributes depending on the value of Type (for example, different validation settings are available for address and phone).
• TypeOnChange — restructuring of the form when changing the type of contact information (recalculation of visibility and availability of elements).
• BeforeWriteOnServer / OnWriteOnServer — control of the correctness of the combination Type + ContactInformationObjectType.

Module of the object (ObjectModule):

• CheckFillingProcessing — checking the mandatory attributes Type and ContactInformationObjectType (ShowError mode).
• BeforeWrite — service logic of the CI subsystem; protection of predefined elements from incorrect changes to key properties.

Module of the form ListForm:

• Command/handler ChangeSelected — group change of attributes of marked elements in the list (standard BSL mechanism "Change selected objects").

Interaction with the application logic of contact information is provided by the common modules of the BSL subsystem — ContactInformationManagement, ClientServerContactInformation, ContactInformationService (the set and names depend on the specific build).

5. Posting and Movements

The catalog is not a document and is not posted — it does not generate movements in registers. No postings (accounting entries) are created for it.

The role of the object is a classifier-source of references. The values of the catalog are used as a dimension/value when filling the information register ContactInformation, where actual data for a specific object (counterparty, organization, individual) is stored: Object, Type (reference to Catalog.ContactInformationTypes), Type, Representation, FieldValues, and if necessary — coordinates/history period.

Thus, the object indirectly participates in the business processes of accounting in the RK (formation of ESF in the ESF IS, STS, printed forms, and contracts), where addresses, phones, and e-mails of counterparties and organizations are taken from the register ContactInformation according to the corresponding types. However, the catalog itself does not write to accounting registers and to the accounts of the standard plan of the RK (for example, 1210, 1030, 1330, 3310, 3130, 6010, 7010). The VAT rate is 16%, MRP indicators (4,325 ₸), MZP (85,000 ₸), deduction for individual income tax (30 MRP/month, but not more than 360 MRP/year), individual income tax rates (10% / 15%), OPE 10%, OPEP 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6% — do not directly relate to this object: it does not perform calculations and accounting movements.

6. Related Objects and Input on Basis

• InformationRegister.ContactInformation — the main consumer of the catalog; stores actual contact data of objects by types of CI.
• Enumerations: ContactInformationTypes (address, phone, e-mail, webpage, fax, other, skype) and ContactInformationObjectTypes (type of owner object).
• Owner objects of CI: Catalog.Counterparties, Catalog.Organizations, Catalog.Individuals, Catalog.Employees, Catalog.Banks, Catalog.Warehouses, and others — on their forms, types of CI are displayed according to ContactInformationObjectType.
• Common modules of the "Contact Information" subsystem of BSL — programmatic reading/writing of values by types.

Input on basis for this catalog is not provided (it is not a document). New elements are created manually or supplied predefined as part of the configuration.

7. Extension Points

• Configuration extension: adding custom types of contact information (for example, "Additional phone of the sales department", "Legal address of the branch") for the necessary types of objects — by creating catalog elements with correct Type and ContactInformationObjectType.
• Forms: refinement of ElementForm/ListForm extension — adding attributes, service settings, additional validation through handlers OnCreateOnServer, TypeOnChange.
• Object handlers: overriding/extending CheckFillingProcessing and BeforeWrite in the extension to control business rules when entering types of CI.
• BSL Programmatic API: using common modules ContactInformationManagement/ClientServerContactInformation for reading and writing values by types without direct access to the register.
• Group change: the "ChangeSelected" mechanism on the list form — for mass correction of attributes of existing types.

⚠️ When refining predefined types of contact information, exercise caution: several standard forms and printing mechanisms of the configuration rely on specific predefined elements, changing their key properties may disrupt the operation of standard functionality.