Functionality | After | Before | Result of changes |
---|---|---|---|
Managed forms. |
The Create menu (in a document journal form) does not contain document types disabled by functional options.
The Show in list menu (in a document form) does not contain list forms disabled by functional options. |
The Create menu (in a document journal form) contained document types disabled by functional options.
The Show in list menu (in a document form) contained list forms disabled by functional options. |
Eliminated unexpected system behavior. |
Server clusters. |
In client/server mode, dynamic updates do not require restarting Designer.
When a scheduled job is started or completed in an infobase, this does not affect the performance of other infobases in the cluster. Improved system reliability in the following scenarios:
|
In client/server mode, dynamic updates required restarting Designer.
When a scheduled job was started or completed in an infobase, this affected the performance of other infobases in the cluster. The system reliability was insufficient in several scenarios. |
Increased stability and reliability of server clusters. |
Predefined data. |
During infobase verification and repair operations, the platform checks whether the main table of an object (catalog, chart of characteristic types, chart of calculation types, or chart of accounts) contains no more than 1 record for each predefined item in each area. If a duplicate item is found, a predefined item mark is removed from it and a deletion mark is set instead. | This feature was not provided. | Improved infobase verification and repair operation. |
External data sources. |
Table fields and cube table dimension fields of external data sources can have NULL values only if the NULL allowed check box is selected in the object settings. For external data source cube table fields NULL values are always allowed.
This change is not implemented in 8.3.6 compatibility mode. |
All external data source table fields could have NULL values. | Improved performance of sorting dynamic lists by fields whose ability to store NULL values is specified correctly. |
Data composition system. |
In a data composition schema, if a query with a nested query is used in a data set, selected fields of the nested query are available for filtering, provided that these fields are not used in aggregate functions of the parent query.
This change is not implemented in 8.3.6 compatibility mode. |
In a data composition schema, if a query with a nested query was used in a data set, selected fields of the nested query were not available for filtering (except virtual table parameters). | In a data composition schema, the generation of a resulting query is optimized for scenarios that utilize nested queries with filters by nested query fields. |
Infobase verification and repair. Common attributes / Data separation. |
Infobase verification and repair can detect and repair the following issue: objects linked to some tabular section rows are absent from the infobase. The search and restoration are performed taking into account all independent separators that include the missing objects. | This feature was not provided. | Improved infobase verification and repair procedure. |
Dynamic lists. |
In dynamic lists, search by reference fields with custom presentations is performed by fields that form the presentation. Such fields are obtained with the help of the PresentationFieldsGetProcessing() handler. | In dynamic lists, search by reference type fields with custom presentation was performed only by fields used in default presentation. | Improved search by reference fields with custom presentations in dynamic lists. |
Managed forms. Command interface. |
In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command is executed from the navigation panel, the Uniqueness command handler parameter is assigned a BOOLEAN value (TRUE if the command is executed through the Open new item context menu command, otherwise FALSE).
In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command is executed from a form navigation panel, the uniqueness of the form being opened is not set. This change is not implemented in 8.3.6 compatibility mode and in the Forms in separate windows mode. |
In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was set to the main window identifier. In the web client, in the Taxi interface or in the Forms in tabs mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was assigned a BOOLEAN value.
In the thin and web clients, in the Taxi interface or in the Forms in tabs mode, when a command was executed from a form navigation panel, the Uniqueness command handler parameter was set to the main window identifier. In the Forms in separate windows mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was set to the main window identifier. In the Forms in separate windows mode, when a command was executed from a form navigation panel, the Uniqueness command handler parameter was set to the main window identifier. |
Unified platform behavior in various client applications and usage scenarios. |
Server clusters. |
For the ragent, rmngr, and rphost commands, which start server cluster processes, the pingPeriod and pingTimeout command-line options are implemented.
In default.vrd file, for the pool item, the serverPingPeriod and serverPingTimeout attributes are implemented. In the web server publishing dialog box, the Check period and Check timeout properties are implemented. In the technological log, for the CONN event, the list of logged events related to the detection of connection losses between processes in a single cluster is extended. |
A less-efficient algorithm was used for detection of connection losses in a cluster. | Improved server cluster stability, faster and more efficient detection of connection losses in a cluster. |
Full-text search. Dynamic lists. Server clusters. |
When a form that contains a dynamic list is closed, the server cluster is notified about that in order to cancel the background job that performs search in the list (if it was initiated earlier). | When a form that contained a dynamic list was closed, the server cluster was not notified about that. If a background job that performed search in the list was running at the moment of closing, it was not interrupted once the form was closed. Instead, it continued running till the completion. | Eliminated unexpected system behavior. Reduced server cluster load in some scenarios. |
Development tools. |
In Designer, the П shortcut is removed from the Move up and Move down commands in the Russian interface (it was assigned to both commands previously). Other keyboard shortcuts for these commands are still in effect, as well as the actions associated with these commands. | In Designer, the П keyboard shortcut was assigned to both Move up and Move down commands in the Russian interface. | Eliminated unexpected system behavior. |
Data composition system. |
Presentations of filter items displayed in reports is changed.
If a report includes a filter item from the user settings and the user settings item presentation is specified for this filter item, the presentation is used for displaying the filter in the resulting report. This change does not affect reports that include filter items that do not belong to user settings. It also does not affect filter items that do not have user settings item presentations specified. This change is not implemented in 8.3.6 compatibility mode. |
If a report included a filter item whose presentation was specified, only this presentation was displayed in the report. Otherwise the filter item was displayed in the following format: <Left value> <Comparison type> <Right value>. | Filter list presentations in reports are easier to read. |
Spreadsheet documents. |
The spreadsheet document behavior is modified in scenarios where a rectangular area of cells is inserted or deleted (interactively or using 1C:Enterprise script). If an area being moved overlaps an area of merged cells and the merged area is not fully included into the area being moved, the merging is removed and the cells previously included in the merged area inherit the formatting of the merged area.
This change is not implemented in 8.3.6 compatibility mode. |
When a rectangular area of cells was inserted or deleted, merged cells that partially overlapped the area being moved were not modified. | Eliminated unexpected spreadsheet document behavior. |
DBMS operations. |
In Oracle Database DBMS an index created for a temporary table that includes more than three dimensions of String type, each of them containing at least 60 characters, might be truncated (with the last fields discarded) if the index key length does not fit the block size. | In Oracle Database DBMS an index created for a temporary table that included more than three dimensions of String type resulted in unexpected system shutdown due to DBMS error. | Eliminated unexpected system behavior. Improved system reliability. |
Administration tools. |
The following requirement is described in the documentation: when an application is updated over HTTP or HTTPS, all .mst, .msi, and .cab files in the distribution kit .zip archive must have a digital signature. The signature is verified on the computer where the application is installed. | Thew documentation did not include the file digital signature requirement. | Documentation issue corrected. |
Development tools. |
Setting a correspondence between Debugger and a debug item no longer requires the exact match of infobase connection strings in Debugger and in the debug item.
The option to edit a variable value during debugging is implemented. The option to view all local variables of a method being debugged in a dedicated window is implemented. The state of folders (expanded or collapsed) in the immediate window and in the local varibles window is preserved when switching to the next debug step. If you use the Break command (Shift+F5) to close an application being debugged, the modal exit confirmation dialog box is never displayed. |
Setting a correspondence between Debugger and a debug item required the exact match of infobase connection strings in Debugger and in the debug item.
The option to edit a variable value during debugging was not provided. The option to view all local variables of a method being debugged in a dedicated window was not provided. The state of folders (expanded or collapsed) in the immediate window and in the local varibles window was not preserved when switching to the next debug step. Using the Break command (Shift+F5) to close an application being debugged sometimes opened the modal exit confirmation dialog box. |
Expanded debug functionality. |
Data composition system. |
The overall columns of a data composition system table display the titles of grouped resource fields if grouping templates are specified for the table columns.
This change is not implemented in 8.3.6 compatibility mode. |
The overall columns in the data composition system table header did not display the titles of grouped resource fields if grouping templates were specified for the table columns. | Eliminated unexpected system behavior. |
Common objects. Development tools. |
The Language code property of the Language configuration object cannot contain the following characters: #, *, |, \, :, ", <, >, ?, /. | The Language code property of the Language configuration object could not contain the # character. | Chance of configuration dump procedure being terminated due to incorrect generation of the file name (which is based on the language code) is reduced. |
Command interface. |
In the thin client, in the Forms in separate windows mode, if a navigation command handler includes the GotoURL() global context method with a navigation point reference parameter, after the command execution the current navigation point is set to this command.
|
In the thin client, in the Forms in separate windows mode, if a navigation command handler included the GotoURL() global context method with a navigation point reference parameter, after the command execution the current navigation point was set to the point passed in the parameter. | Eliminated unexpected system behavior. |
Managed forms. |
In the thin client, the Window property of managed form object is read-only.
This change is not implemented in 8.3.6 compatibility mode. |
In the thin client, the Window property of managed form object was available for both reading and writing. In the web client, the Window property of managed form object was read-only. | Unified system behavior in different client applications. |
Information registers. |
For periodic information registers with resources or attributes indexed, the structure of the index of the slice first/last table is changed. If the information register periodicity is set to By recorder position, register dimensions are added to the index. If the periodicity has any other value, the index is not unique.
When the Compatibility mode configuration property is set to None, the platform performs the restructuring of the slice tables. This change is not implemented in 8.3.6 compatibility mode. |
For periodic information registers with periodicity set to By recorder position, register dimensions were not included in the index of slice first/last tables. For periodic information registers with other periodicity values, the index of slice tables was unique. | An nonunique index issue is eliminated. |
Predefined data. |
The configuration check that is always performed before database configuration update includes a check for duplicate predefined item names. No duplicate predefined item names are allowed for any configuration object. If duplicate predefined items are found, this is reported to the message window but does not prevent the configuration update.
This change is not implemented in 8.3.6 compatibility mode. |
The configuration check that was always performed before database configuration update included a check for duplicate predefined item names, however, duplicate names did not prevent the database configuration from updating. | Improved reliability of configuration updates for configurations that include predefined data. |
Technological log. |
Logging of debugger exceptions in the technological log is implemented. The <EXCP> event is used for that logging. | Logging of debugger exceptions was not performed. | Better debugger error diagnostics. |
Administration tools. |
The infobase verification and repair procedure no longer includes a check for spaces at the end of attribute values that have String type and variable length. | The infobase verification and repair procedure included a check for spaces at the end of attribute values that had String type and variable length. | Eliminated unexpected system behavior. |
Regional settings. |
For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ, and 87-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers. | The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ. and 87-FZ. | The time offset changes introduced by the new law are implemented. |
Next page: Changes that require modification of configuration and administrative settings