1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | ApplicationSizeHistory |
| Full Name | Report.ApplicationSizeHistory |
| Synonym | “Application size history” (in the metadata tree, the synonym is not specified separately; the displayed name is generated by the team) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Main Form | ReportForm |
| Settings Form | SettingsForm |
Purpose. The report is intended for analyzing and tracking the dynamics of changes in application size (database volume) over time. It is used by administrators and technical specialists to monitor database growth, identify abnormal size spikes, and plan optimization measures for storage. The result is output as a tabular document; additionally, the report can initiate the calculation of the current application size in a background task.
This is a service (administrative) report of the “Service Technology” mechanism. It does not relate to accounting (financial, tax) objects, does not operate with economic data, and does not depend on national accounting standards of the RK (VAT rates, PIT, chart of accounts, etc. are not applicable).
Where to find in 1C: section “Service Technology” → “Application Size History”.
Navigation link: e1cib/list/Report.ApplicationSizeHistory
2. Attributes and Table Parts
2.1 Header Attributes
According to the metadata, the report does not contain its own attributes. All construction parameters are set through data composition settings and form attributes (7 attributes were identified in the form structure).
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| (attributes are absent) | — | — | — |
2.2 Table Parts
Table parts are absent. The report result is generated as a tabular document and displayed in a form field of type SpreadSheetDocumentField. The data for construction is taken from service sources of the application size accounting mechanism (measurement history), not from the attributes/table parts of the report object itself.
3. Forms
| Form | Purpose |
|---|---|
| ReportForm | Main (working) form of the report. Contains ~42 control elements: a field for the tabular document to display the result, commands for generating the report and initiating the application size calculation, as well as control elements for options and settings (quick settings, analysis period). |
| SettingsForm | Settings form of the report (4 elements). Used for configuring construction parameters — period selection, detailing, composition of output indicators. |
4. Key Module Procedures
The attached evidence contains the structure of forms and their purpose, but does not contain BSL listings with the binding “path:string”. Below are typical handlers for reports of this type (service report with background calculation in the SCD). Specific names in version 3.0.74.2 may differ — this is the only truly version-dependent aspect of the section.
Form module ReportForm:
OnDataTransferSettingsToSettings/OnVariantLoadOnServer— initialization of the variant and SCD settings upon opening.OnOpen— restoration of saved settings, determining the availability of the size calculation command.GenerateReport(command) → server-side handler of composition — executesComposer.Execute()/Compose()and outputs the result in the tabular document field.CalculateApplicationSize(command) — initiates a background task for calculating the current database size viaLongOperations.ExecuteInBackground(...).ConnectableHandlerWaiting/ProcessingCalculationCompletion— tracking the status of the long operation and updating the result upon its completion.
Report object module:
OnResultComposition(DocumentResult, DataDecoding, StandardProcessing)— optionally overrides the standard SCD composition.OnDefiningSelectionSettingsInUserMode/SettingsForServiceTechnology— registration of the report in the list of service reports.
General calculation module (mechanism “Service Technology”):
- Background size calculation procedure — traverses database tables, sums the volume, and records a history point in the service storage of measurements.
5. Posting and Movements
The object is a report, not a document:
- It is not posted, does not generate postings and movements in accounting registers, accumulation, or information.
- It does not refer to the chart of accounts of the RK and does not participate in the formation of VAT/PIT/contributions.
The report reads data from the application size measurement history (service storage of the “Service Technology” mechanism) and, upon the calculation command, initiates the recording of a new measurement in this storage through a background task. There is no impact on the accounting registers of the configuration.
6. Related Objects and Input Based On
- No input based on is provided (reports do not support the input based on mechanism and are not input based on).
- Related objects — subsystem “Service Technology” and its service mechanisms for accounting application size (regulatory/background tasks for size calculation, service storage of history).
- The report is published in the command interface of the “Service Technology” section via the corresponding command.
7. Extension Points
- Configuration extension: adding custom report variants (additional dynamics charts, grouping by dates); overriding
OnResultCompositionin the object module for custom output. - Additional reports (external): implementation of an alternative report on size history with connection via “Additional reports and processing”.
- Background calculation: interception/addition of the size calculation procedure in the general module of the mechanism for collecting extended statistics (e.g., size by individual tables/objects).
- Form: adding attributes and commands to the form through extension (e.g., result export button, auto-refresh on schedule).
- Access rights: it is advisable to restrict the report to the role of administrator/technical specialist; when customizing — add rights check before starting the calculation.