Reference "RemoveTaskQueue" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

The prefix Delete in the name is a convention of standard 1C configurations, indicating an object marked for deletion. Functionality has been transferred to the standard mechanisms of the 1C:Enterprise 8.3 platform (regulatory and background tasks, the "Task Queue" mechanism of BSP). In current versions, the object is retained only for data transfer during updates and should not be used in application logic.

The object does not belong to the accounting subsystem: it does not participate in VAT calculations (in the RK from 2026 — rate 16%), PIT, WPP, and other taxes, does not generate entries according to the RK chart of accounts, and is not related to electronic invoices (ESF)/SNT. The tax/accounting facts of the country listed below do not apply to this technical object.

Where to find in 1C:

• Navigation link: e1cib/list/Catalog.DeleteTaskQueue
• In the interface (in older releases): section "Service Technology" → "Task Queue (not used)". In the current release, the item from the command interface is usually hidden.

2. Attributes and Table Parts

2.1 Header Attributes

The standard attributes of the catalog are Code, Name, DeletionMark, Predefined, Reference. Application attributes of the object:

The property "Mandatory" = "Not checked" for all attributes means that the platform does not perform automatic validation of filling during recording — filling is entirely controlled by the server code that queues the tasks.

2.2 Table Parts

None. All information about the task is stored in the header attributes — each row of the queue corresponds to one element of the catalog.

3. Forms

The object does not have defined forms. This confirms its purely technical nature: the catalog is not intended for interactive user work and is serviced programmatically.

If data viewing is necessary, the platform displays the object through automatically generated forms.

4. Key Procedures of Modules

The object modules (object module, manager module) in the attached evidence are not presented, there is no ready BSL code. Below are typical handlers characteristic of the service catalog-task queue in configurations on BSP; in a specific release, they may be empty, as the object is marked for deletion.

Object Module (ProcessingProcedure is absent — not a document):

• BeforeRecording(Refusal) — service control of queue recording (key check, state); in the marked for deletion object, it usually does not carry application logic.
• OnCopy(CopyingObject) — reset of execution identifiers (ExecutingBackgroundTask, AttemptNumber) when copying, to avoid duplicating active tasks.

Manager Module (typical functions for working with the queue):

• Queue task placement — creating an element, filling MethodName, Parameters, Schedule, ScheduledLaunchMoment, Key.
• Selection of ready-to-launch tasks — selection by Usage = True and ScheduledLaunchMoment <= CurrentDate().
• Updating status after execution — recording TaskState, LastLaunchStartDate, LastLaunchCompletionDate, AttemptNumber.

Requires verification (version-specific): whether the object/manager modules are filled with code in release 3.0.74.2 or the object is left "empty" until physical deletion — determined in the Configurator for a specific delivery.

5. Processing and Movements

The catalog is a non-document object. It:

• is not a document, does not have a processing mode;
• does not generate movements in any accumulation, information, or accounting registers;
• does not create accounting entries and does not affect the RK chart of accounts in any way.

Accordingly, standard accounting entries of the configuration are not applicable to it, for example (for comparison — these are operations of sales/purchase documents, not this object):

• sale of goods: Dr 1210 (short-term receivables from customers) — Cr 6010 (income from sales), VAT accrual 16% Cr 3130, cost write-off Dr 7010 — Cr 1330;
• receipt of goods: Dr 1330 — Cr 3310 (payables to suppliers);
• receipt of payment: Dr 1030 (money in current accounts) — Cr 1210.

Data of the object is stored as catalog elements; "movement" here is only the recording/modification of the queue element itself.

6. Related Objects and Input Based On

• Enumeration TaskStates — source of values for the attribute TaskState.
• Platform mechanisms — background/regulatory tasks of 1C:Enterprise 8.3 (BackgroundTasks, RegulatoryTasks), which are referenced by ExecutingBackgroundTask (UUID) and the object RegulatoryTaskSchedule in the attribute Schedule.
• Subsystem "Task Queue"/"Service Technology" BSP — current replacement for this catalog.

Input based on: not provided either as a basis or as a receiver. The object does not participate in input chains based on application documents and is not related to electronic documents (ESF, SNT).

7. Extension Points

Since the object is marked for deletion, any extension of its application logic is not recommended — instead, the standard mechanisms of background tasks and the "Task Queue" subsystem of BSP should be used. Technically available:

• Configuration extension (Extension): adding attributes/event subscriptions to the catalog is possible but impractical due to the prefix Delete.
• Event subscriptions BeforeRecording / OnRecording of the catalog — for diagnostics or logging during the migration period.
• IB update handlers — a typical place where data from DeleteTaskQueue is transferred to current mechanisms and cleaned; here it is safest to refine migration, not working logic.
• Programmatic API of the object manager — the only supported way of access (there are no forms for interactive work).

Recommendation: plan new tasks through the standard regulatory/background tasks of the platform; gradually eliminate references to Catalog.DeleteTaskQueue in the refined code.