Report "Deferred Update Progress" — Technical Description

1. Identification

Purpose. The report is intended for monitoring the process of deferred updates of the information base after transitioning to a new version of the configuration. It displays statistics on the processing of objects by deferred update handlers (UpdateInformationBase), groups data by time intervals (hours), shows overall progress and the remaining objects to be processed, as well as identifies handlers that have completed with errors. The tool is used by administrators and users with full rights to control the update process, identify "stuck" or problematic handlers, and assess the remaining workload.

The report is of a service (technical) nature: it does not relate to operational accounting, does not deal with monetary amounts, taxes, or the chart of accounts, and works exclusively with metadata of the update process of the information base.

Where to find in 1C. Section "Administration" → "Deferred Update Progress". Navigation link: e1cib/list/Report.DeferredUpdateProgress.

2. Attributes of Header and Table Parts

2.1 Header Attributes

Custom attributes are absent. The report has no data storage attributes and operates entirely based on the information registers of the information base update subsystem. User settings (filter by handler, period intervals, detail mode) are set using standard DCS tools in the settings form, not as object attributes.

2.2 Table Parts

Custom table parts are absent. The resulting tables are dynamically formed during composition through DCS based on source data (information registers on the progress of deferred updates).

Key indicators displayed by the composition scheme (correspond to the columns of the auxiliary form HandlerDependency):

3. Forms

The main form is the universal report form of DCS (not included in the JSON export, but exists by default for all reports in DCS). Additionally, the object contains two auxiliary forms:

The form HandlerDependency allows analyzing the "dependency tree": which handlers block the execution of others (a handler does not start until its predecessors are completed), which helps to localize the cause of progress stoppage.

4. Key Procedures of Modules

In the reference evidence, the original BSL code of the report and form modules is not attached. Below are typical handlers for the report in DCS and its forms of this type (description of general logic, not a guarantee of specific lines in version 3.0.74.2).

Report object module:

• OnResultComposition(DocResult, DataDecoding, StandardProcessing) — programmatic intervention in output: highlighting handlers with errors, formatting progress, refilling calculated columns.
• SettingsForTechnicalSupport() / service functions for preparing the source — collecting data on the update progress from the UpdateInformationBase subsystem to the external data source of DCS.

Report form (universal DCS):

• OnServerCreation — setting initial settings, period intervals, filtering by handler.
• OnOpen — restoring user layout settings.

Form HandlerDependency:

• OnServerCreation — building the tree of handlers and their dependencies from the data of the update subsystem.
• Command handler RegisteredData — opening the form RegisteredData for the current handler.

Form RegisteredData:

• OnServerCreation — filling the table of objects (column TableName) registered for processing by the passed handler.

Requires verification: exact names and signatures of exported methods depend on the version of the BSP embedded in 3.0.74.2.

5. Posting and Movements

The report is not a document, is not posted, and does not generate movements in any accumulation registers, accounting registers, or postings according to the chart of accounts of the RK. It is intended only for reading and visualization.

Data source — information registers of the "Update Information Base" subsystem (BSP), which record:

• list of deferred handlers and their statuses (not executed / executing / completed / completed with errors);
• number of objects registered for processing and the remainder;
• timestamps of processing (for grouping by hourly intervals);
• dependencies between handlers.

Since the object is service-oriented, applied accounting rules of Kazakhstan do not apply (VAT rate 16%, accounts 1210/1030/1330/3310/3130/6010/7010, IPR/OPV/SO, etc.) — these entities are not covered by this report.

6. Related Objects and Input Based On

• BSP subsystem "UpdateInformationBase" — data provider; the report reads service information registers of this subsystem.
• Deferred update processing (launch/repeat of handlers) — the report shows the result of its work; from the form HandlerDependency, one can navigate to analyze problematic handlers.
• Administration roles / full rights — determine access to the report.

Input based on is not supported (the mechanism is not applied for reports). Feedback is only navigational: transitioning from the handler tree to the list RegisteredData.

7. Extension Points

• Configuration extension. Borrowing the form HandlerDependency or the report object to add custom columns (for example, calculated estimates of remaining time) through &Insert/&After in the handlers OnResultComposition and OnServerCreation.
• DCS settings. Custom report variants and user settings (filter by handler name, period intervals, groupings) without changing the code.
• Additional reports (external). BSP mechanism "Additional reports and processing" — if alternative analytics on the same update registers are needed.
• Programmatic access to data — through the API of the UpdateInformationBase subsystem (for custom monitoring tools) instead of direct reading of service registers.

Requires verification: availability of specific exported methods of the update subsystem depends on the version of the BSP included in 3.0.74.2.