New functionality and changes in the 1C:Enterprise mode
|Functionality||After||Before||Result of changes|
|Implemented automated marking of blank fields when entering data into spreadsheet documents in the web client.||Automated marking of blank fields was not performed when entering data into spreadsheet documents in the web client.||Eliminated unexpected system behavior.|
||Implemented changes to calculation of page tab size and the appearance of page tabs in vertical mode.
Implemented scaling of pictures in page tabs when changing DPI (both for thin client and thick client). This change is not implemented in 8.3.9 compatibility mode.
Implemented slight size and position changes for several types of managed form items.
Changed appearance of slider (both in Taxi interface and in the web client with Version 8.2 interface). The slider appearance in the web client differs from its appearance in the thick and thin clients.
The size of the colored picture used for input fields that display data of Color type differs between the web client and the thick/thin clients.
Changed appearance of system forms (in Taxi interface for both thick and thin clients) for better conformity with general visual interface style.
Increased hit boxes for icons that collapse and expand tree nodes in tables (in Taxi interface).
Improved appearance of controls for non-standard DPI values. Modified size calculation for slider fields in forms.
|The interface appearance was different. Pictures in page tabs were not resized when changing DPI (both for thin client and thick client).||Improved appearance of client applications.|
||Changed appearance of form navigation panel in Taxi interface. In Russian localization, the name of panel item Main is now slightly changed. All commands are displayed in the form navigation panel. Full names are displayed for all of the panel commands. If a command does not fit the form actions panel, the command is displayed in the More menu.||Appearance of form navigation panel was different. In Russian localization, the name of panel item Main was slightly different. The following rule was in force when displaying commands: if the Important group contained more than two commands, only two commands were displayed on the navigation panel. Commands that did not fit the form navigation panel were available through the More menu. Long names were shortened and marked with ellipses (...) both in the thick and thin clients.||Application UI was improved.|
||The opened items panel was redesigned in Taxi interface:
||Appearance and functionality of the opened items panel (in Taxi interface) were different:
||It is now easier to use the opened items panel in Taxi interface.|
|All border types are now displayed in spreadsheet documents opened in the web client. Appearance of border lines of spreadsheet documents opened in the web client depends on the browser and may differ from appearance of border lines of spreadsheet documents opened in the thick or thin client.||Only border lines of these types were displayed for spreadsheet document cells: Solid, Dotted, and None. All other line types were replaced by the above types as follows:
||Eliminated unexpected system behavior. Border lines of spreadsheet documents opened in the web client now more closely conform to border lines of spreadsheet documents opened in the thick or thin client.|
||If the freeze area of a managed form table exceeds the visible area of the table, column freeze is canceled automatically.
This change is not implemented in 8.3.9 compatibility mode.
|If the freeze area exceeded the size of the whole table, the table could not be scrolled horizontally.||It is now easier to work with tables in small forms.|
|Data composition system.
||In the "Main" data composition appearance template used in Taxi interface, text color is set to Auto for all template areas except the report header.
This change is not implemented in 8.3.9 compatibility mode
|In the "Main" data composition appearance template used in Taxi interface, gray text color was used for some of the template areas (except the report header).||Now optimal text color is chosen whenever a report is displayed or printed, improving readability.|
||Implemented sorting for dynamic lists by clicking any column header in the table displaying dynamic list data, provided that the query text contains aggregate functions and GROUP BY expressions.
This change is not implemented in 8.3.7 compatibility mode.
|Dynamic list sorting by clicking any column header in the table displaying dynamic list data was not supported, regardless of whether the query text contained aggregate functions or GROUP BY expressions.||Behavior of tables displaying dynamic list data is now more intuitive and predictable.|
||In the thin and thick clients, the wheel button scrolls a form item where mouse cursor is currently located (provided that such form item is scrollable). The form item is scrolled regardless of whether it has received input focus. After the form item is fully scrolled, the parent form item starts scrolling (provided that it is scrollable).||In the thin and thick clients, the wheel button only scrolled active form items. In the web client, the wheel button scrolled both active and nonactive form items.||Managed form navigation is now more user-friendly. Unified scrolling behavior between the web client, the thin client, and the thick client.|
|All standard pictures used by client applications are implemented as sets of pictures optimized for a variety of DPI and display scale values. Standard pictures are redesigned.||Standard pictures used by client applications were not optimized for current DPI and display scale values. Therefore, applying non-standard DPI could result in blurry standard pictures.||Optimized appearance of client interface for non-standard DPI and display scale values.|
|Client application installation.
||If any issue occurs during the thin client update over HTTP, you have the option to get the name of the file that cannot be updated. This option is provided in the following scenarios:
||If any issue occurred during the thin client update over HTTP, the option to get the name of the file that cannot be updated was not available. In particular, there was no way to get the file name of a corrupted archive of the name of the file that had invalid digital signature.||Improved issue diagnostics during the thin client update over HTTP.|