1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | ObjectIdentifiersExtensions |
| Full Name | Catalog.ObjectIdentifiersExtensions |
| Alias | — (service object, alias not assigned) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Owner Subsystem | Library of Standard Subsystems (BSP), mechanism "Update IB Version" / "Configuration Extensions" |
| Where to Find | e1cib/list/Catalog.ObjectIdentifiersExtensions (in the interface — section "Administration" → service data of the extensions subsystem; available to the administrator for diagnostics) |
Purpose. A service (auxiliary) catalog that stores stable identifiers of metadata objects added to the configuration through extensions. It ensures synchronization and control of the relevance of extension metadata: the BSP mechanism matches extension objects with their records in the catalog by a technical key (regardless of the name), tracks versions of connected extensions (UUID, hash sum), and checks compatibility when connecting/updating an extension. It is filled and updated primarily programmatically; in the user interface, it is used by the administrator for viewing and diagnosing the state of extensions.
This is a technical object of the platform-application level. It does not participate in accounting and tax accounting, does not store economic data, and is not related to the chart of accounts, VAT/individual income tax/social tax rates, electronic invoices (ESF)/SNT, etc.
2. Attributes of Headers and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| CollectionOrder | Number (xs:decimal) |
Not checked | Order number of the object in the metadata collection — maintains the hierarchy and sequence of extension objects |
| Name | String (xs:string) |
Not checked | Programmatic name of the extension metadata object (e.g., Document1, Catalog2) |
| Alias | String (xs:string) |
Not checked | User representation of the object in the current language |
| FullName | String (xs:string) |
Not checked | Fully qualified name of the object (e.g., Document.GoodsReceipt) |
| FullAlias | String (xs:string) |
Not checked | Full user representation indicating the type (e.g., Document: Goods Receipt) |
| NoData | Boolean (xs:boolean) |
Not checked | Indicator of an object without tabular data (processing, reports, etc.) |
| EmptyReferenceValue | Undefined | Not checked | Empty reference to an object of the corresponding type for technical comparison operations |
| MetadataObjectKey | Value Storage (v8:ValueStorage) |
Not checked | Unique technical key of the metadata object — identification regardless of the name (resistant to renaming) |
| NewReference | CatalogReference.ObjectIdentifiersExtensions | Not checked | Reference to a new element when transferring/migrating data (replacement/merging of identifiers) |
| ExtensionName | String (xs:string) |
Not checked | Name of the configuration extension to which the object belongs |
| ExtensionIdentifier | String (xs:string) |
Not checked | UUID of the extension for precise version identification |
| ExtensionHashSum | String (xs:string) |
Not checked | Checksum of the extension — integrity check and detection of changes |
2.2 Table Parts
None.
Standard Attributes. Code, Name, DeletionMark, Predefined, Reference — provided by the platform. The main identifying field is MetadataObjectKey, not Code/Name.
3. Forms
| Form | Purpose |
|---|---|
| ListForm | Main form for viewing the list of object identifiers of extensions; supports hierarchical display and search. Used by the administrator for diagnostics. |
| ElementForm | Key form for the user to view/edit properties of a single identifier: name, full name, belonging to an extension, UUID, and hash sum of the extension. |
Other forms (selection, groups) are generated automatically by the platform as needed.
4. Key Module Procedures
Application BSL code in the attached evidence is not provided. Below are typical handlers for a service catalog of this kind as part of BSP; specific names/signatures are specified for version 3.0.74.2.
Object Module (ObjectModule):
BeforeWriting(Refusal)— control of the correctness ofMetadataObjectKeyand extension attributes before saving; prevention of writing duplicate identifiers.FillingProcessing(FillingData, FillingText, StandardProcessing)— filling attributes from metadata data during programmatic creation.
Manager Module (ManagerModule):
- Functions for searching/matching an identifier by
MetadataObjectKeyandFullName(analogous to the "Object Identifiers" mechanism of BSP for the main configuration). - Procedures for batch updating/actualizing the catalog when connecting or updating an extension (creating missing ones, marking outdated ones, filling
NewReferenceduring merging).
Form Modules:
ListForm— handlers for selection and hierarchical display.ElementForm— handlers for opening/reading to show properties of the extension metadata object.
Requires verification: the exact composition of the export methods of the manager and their signatures is version-specific for release 3.0.74.2.
5. Posting and Movements
The catalog is not a document and is not posted. It does not generate accounting entries and movements in the registers of accumulation/summary/accounting.
- No registrator, no movement bookmarks, no impact on the accounts of the standard chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.).
- Does not participate in VAT calculation (rate 2026 — 16%), individual income tax, social tax (10%), social tax on pension savings (3.5%), health insurance (2%), social health insurance (3%), social tax (5%), does not generate electronic invoices (ESF)/SNT.
The only "effect" of the record is the updating of the service table of object identifiers of extensions (data of the catalog itself).
6. Related Objects and Input Based On
- Input based on is not provided (service catalog).
- Connections:
- Attribute
NewReference— self-reference to the same catalog (migration/merging of identifiers). - Logically connected with the BSP mechanism "Object Identifiers" (analogous catalog for objects of the main configuration) and with the subsystem "Configuration Extensions".
- Identifies objects physically described in extensions (through
ExtensionName,ExtensionIdentifier,ExtensionHashSum).
- Attribute
7. Extension Points
- Own extensions of the catalog are not recommended: the object is service, its structure and filling are controlled by BSP; interference may disrupt the synchronization of identifiers during updates.
- Correct points of influence:
- Subscriptions to events
BeforeWriting/OnWritingof the object — only for diagnostics/logging, without changing business logic. - Programmatic use of manager methods to search for the reference of the extension object by name/key in the custom extension code.
- Regulatory operations for updating identifiers are initiated by the IB version update mechanism — interference should be done through standard BSP points, not through direct editing of catalog data.
- Subscriptions to events
Requires verification: the list of available common BSP modules for overriding depends on the version of the library in release 3.0.74.2.