1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | TaskQueueHandlers |
| Full Name | Catalog.TaskQueueHandlers / Catalogs.TaskQueueHandlers |
| Alias | — (not set) |
| Configuration | Accounting for Kazakhstan, edition 3.0.74.2 |
| Category | System / service catalog (infrastructure of background tasks) |
Purpose. The catalog is designed to manage handlers for background asynchronous tasks that are executed on a schedule in the configuration. This is a system catalog for configuring the execution parameters of regulatory operations in task queue mode. Its main application is the administration of automated background processes: data synchronization, document processing, calculations, and other tasks performed periodically without user involvement.
The catalog is primarily used by system administrators and users with rights to configure regulatory tasks. Interaction with it occurs infrequently — during the initial system setup or when changing the configuration of background processes. In the service model (SaaS, service manager), records can be created and maintained automatically.
Important: the catalog is not an accounting — it does not store amounts, tax rates, accounting accounts, and does not affect accounting/tax calculations. The tax parameters of RK-2026 (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, deduction for individual income tax 30 MRP/month, etc.) are not related to this object.
Where to find in 1C: section "Service Technology" → "Task Queue Handlers".
Navigation link: e1cib/list/Catalog.TaskQueueHandlers
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Usage | Boolean (xs:boolean) | Optional (DontCheck) | Activity flag of the handler. Determines whether the handler should be executed on schedule. True — task is active, False — paused without deleting settings. |
| Schedule | Value Storage (v8:ValueStorage) | Optional (DontCheck) | Stores the schedule object (RegulatoryTaskSchedule) in binary form: start time, repetition intervals, days of the week, months, and other parameters of regulatory execution. |
| TaskCount | Number (xs:decimal) | Optional (DontCheck) | Counter of the total number of tasks created by this handler. Used for statistics and monitoring activity. |
| TaskDuration | Number (xs:decimal) | Optional (DontCheck) | Average/last duration of task execution in seconds. Used for performance analysis and identifying problematic handlers. |
| Auto | Boolean (xs:boolean) | Optional (DontCheck) | Indicator of an automatically created record from the service manager. True — record is protected from manual editing and deletion, managed only through the service manager; False — record is created manually and available for modification. |
Standard attributes of the catalog: Code, Name, DeletionMark, Predefined, Reference.
2.2 Table Parts
Methods — a list of processing methods that this task queue handler must perform.
| Name | Type | Purpose |
|---|---|---|
| Method | String (xs:string) | Name of the program method (procedure/function) called when executing the task. Each method is unique within a single catalog item. |
3. Forms
In the metadata of the object, forms are not defined (the list of forms is empty). Automatically generated forms by the platform are used:
| Form | Purpose |
|---|---|
| Item Form (auto) | View and configure an individual handler: "Usage" flag, schedule, list of methods, service counters. |
| List Form (auto) | View the list of task queue handlers, filtering, marking for deletion. |
| Selection Form (auto) | Selecting a handler in other objects during programmatic access. |
Requires verification in a specific build: in certain releases, queue administration may be performed through specialized processing/service technology ARM, rather than through the catalog's auto forms.
4. Key Procedures of Modules
Evidence with BSL code (path:string) to this object is not attached. Below are typical handlers characteristic of a service catalog of this type; verify specific implementations in the object/module manager of your build.
- ObjectModule.BeforeWriting — control of the
Autoflag: blocking manual changes to records created by the service manager; checking the uniqueness of methods in the table part "Methods". - ObjectModule.BeforeDeletion — prohibition of deleting automatically created (
Auto = True) handlers. - ManagerModule — program methods for registering/retrieving task queue handlers, reading the schedule object from the "Schedule" attribute, forming and queuing tasks.
- Task Queue Handlers (common modules of the "Service Technology"/TaskQueue subsystem) — execution of methods from the table part, updating counters
TaskCountandTaskDurationbased on actual processing.
5. Posting and Movements
The catalog is not posted and does not generate movements in accounting registers, accumulation, or information. It is not a document and does not participate in accounting/tax accounting.
Accordingly:
- transactions according to the standard chart of accounts of the RK (1210 — short-term receivables from customers, 1030 — cash in current accounts, 1330 — goods, 3310 — payables to suppliers, 3130 — VAT payable, 6010 — revenue from sales, 7010 — cost of sales) are not generated by this object;
- calculation of VAT (rate 16%), individual income tax, social tax, and formation of electronic invoices (ESF) are not performed by this object.
The "movement" related to this catalog is purely infrastructural: queuing and executing background tasks in accordance with the "Schedule" attribute and the composition of the table part "Methods".
6. Related Objects and Input on Basis
- Subsystem "Service Technology" / "Task Queue" — the main area of use; the catalog stores settings for handlers of this subsystem.
- Service Manager (SaaS) — external system that creates and maintains records with the
Auto = Trueflag. - Regulatory and background tasks of the platform — the schedule from the "Schedule" attribute sets the frequency of execution.
- Input on Basis — not provided (the object does not participate in input chains).
7. Extension Points
- Configuration Extension: adding handlers
BeforeWriting/BeforeDeletionin the object module for custom validation logic of methods or additional protection of auto-records. - Additional Attributes/Information: through the characteristic types plan of the subsystem of additional attributes (if available in the configuration), without affecting the standard composition of metadata.
- Custom Queue Methods: registration of new values in the table part "Methods" with implementation of corresponding procedures in common modules — during integration improvements of background processing.
- Event Subscriptions: subscription to
BeforeWriting/OnWritingof the catalog for auditing changes to handler settings.
Requires verification: the availability and composition of extension mechanisms depend on whether the database operates locally or in the service model — in SaaS, manual intervention in records with
Auto = Trueis limited.