Changes that affect system behavior




FunctionalityAfterBeforeResult of changes
Client application.
When 1C:Enterprise opens an infobase that is not registered in its infobase list, it creates a directory for storing the service data of the infobase. It creates an individual directory with a unique name for each infobase connection string and each infobase user. The maximum number of directories is 20.When 1C:Enterprise opened an infobase that was not registered in its infobase list, it used a directory with a predefined name for storing the service data of all such infobases: 00000000-0000-0000-0000-00000000000.The service data of infobases that are not registered in the infobase list is stored in dedicated directories. This facilitates disk space management and prevents the growth of a single directory.
Development tools.
When a custom command of a metadata object is renamed, the platform checks whether the new name exactly matches the name of any standard command of that metadata object. The platform also performs this check during the configuration logical integrity check.This feature was not provided.

Names of custom commands of a metadata object could exactly match the names of its standard commands.

Eliminated unexpected system behavior.
Charts.
The chart scale view settings are expanded, they now include scale view, color, and position, scale label angle, grid line visibility and color, and more.

For ChartScale object, the following properties are implemented: GridLinesShowMode, GridLine, GridLineColor, LabelFont, LabelColor, LabelOrientation, MaxLabelRows, LabelAngle, LabelFormat, ScaleLocation, ScaleLine, ScaleLineColor, ScaleStep, ScaleMarkLocation, and ScaleLabelLocation.

The following properties of ChartPlotArea object are deprecated, they are supported solely for compatibility purposes:

  • ShowSeriesScaleLabels. Use SeriesScale.ScaleLabelLocation instead.
  • ShowPointsScaleLabels. Use PointsScale.ScaleLabelLocation instead.
  • ShowValuesScaleLabels. Use ValuesScale.ScaleLabelLocation instead.
  • ShowScaleValueLines. Use ValuesScale.GridLinesShowMode instead.
  • ValueScaleFormat. Use ValuesScale.LabelFormat instead.
  • LabelsOrientation. Use PointsScale.LabelOrientation instead.

In version 8.3.10 compatibility mode, the following properties are hidden from the property palette and do not affect the chart view:

  • LabelAngle
  • ScaleLocation
  • MaxLabelRows
  • ScaleMarkLocation
  • ScaleLabelLocation
These features were not provided.

The chart scale view settings were simpler.

Expanded chart view options.
Full-text search.
The following full-text search features are implemented:
  • In privileged mode, the platform does not check the access rights for objects processed by full-text search.
  • The option to specify whether full-text search gets object presentations is implemented. The FullTextSearchList.GetPresentation property is implemented. The platform always checks the access rights for the object fields that form the presentation, regardless of the value of this property.
  • The platform always checks the access rights for the object fields that form the object description, regardless of the value of FullTextSearchList.GetDescription property.

To apply these changes, disable the compatibility mode and rebuild the full-text search index. Previous 1C:Enterprise versions cannot work with indexes built in version 8.3.11 with compatibility mode disabled. This change is not implemented in 8.3.10 compatibility mode.

Full-text search worked as follows:
  • In privileged mode, the platform checked the access rights for objects processed by full-text search.
  • The platform did not check the access rights for object fields that formed the presentation if FullTextSearchList.GetDescription property was set to False.
Optimized full-text search.
Data composition system.
Spreadsheet documents.
In the data compostion system, nested charts and tables of the resulting spreadsheet document are located in spreadsheet document groupings. The data composition system template composer creates blank templates with VerticalLevel property set. These templates follow the templates of charts and tables located in groupings.

This change is not implemented in 8.3.10 compatibility mode.

In the data compostion system, the resulting spreadsheet document did not contain groupings for charts and nested tables that did not have row groupings. The template composer did not create blank templates with VerticalLevel property set that followed the chart templates. For tables located in groupings, the composer created blank templates with VerticalLevel set to 0.Eliminated unexpected system behavior.
XML and XDTO support.
The option to download XSD documents that import schemas that require HTTP requests to external servers (with redirects) is implemented.

This change is not implemented in 8.3.10 compatibility mode.

The option to download XSD documents that imported schemas that required HTTP requests to external servers (with redirects) was not available.Eliminated unexpected system behavior.
Development tools.
Client application.
In the search and replace dialog box of the text editor, the following behavior of the Replace button is implemented:
  • If the selected text fragment matches the search string, replace it and search for the next occurrence.
  • Otherwise search for the next occurrence. Clicking Replace again replaces it.
In the search and replace dialog box of the text editor, clicking the Replace button searched for the next occurrence of the search string. Clicking Replace again replaced it.Eliminated unexpected system behavior.
Spreadsheet documents.
In the dialog box for setting a spreadsheet document area name, the default name is generated in the language that matches the current 1C:Enterprise script variant.

This change is not implemented in 8.3.10 compatibility mode.

In the dialog box for setting a spreadsheet document area name, the default name was generated in the language that matched the client application interface language.Eliminated unexpected system behavior.
Development tools.
During the creation of a configuration update file, the message stating that the configuration update requires 1C:Enterprise version 8.3.9.2033 or later is no longer displayed.During the creation of a configuration update file, the message stating that the configuration update required 1C:Enterprise version 8.3.9.2033 or later was displayed.Removed a message that is no longer relevant.
XML and XDTO support.
When an XSD schema is imported to an XDTO package, for references to global elements and attributes, the default and fixed properties are imported to DefaultValue and Fixed properties, regardless of the element or attribute declaration type.When an XSD schema was imported to an XDTO package, for references to global elements and attributes, the default and fixed properties that were specified locally were not imported.Eliminated unexpected system behavior.
Dynamic lists.
If a dynamic list contains PredefinedDataName and DataVersion fields, the following rules apply to these fields:
  • Only the following comparison types are available: Equal to, Not equal, In list, Not in list, Filled, and Empty.
  • Search through the search field of the dynamic list is not supported.
  • Advanced search is only available by exact match.
If a dynamic list contained PredefinedDataName and DataVersion fields, the following rules applied to these fields:
  • All comparison types were available.
  • Search through the search field of the dynamic list generated an error.
  • Advanced search allowed selection of any search type but generated an error if search at beginning of line or anywhere in the line was selected.
Eliminated unexpected system behavior.
External reports and data processors.
The option to disable the warning of the unsafe operation protection system when you create an external report or data processor object is implemented (use it when you are sure that the file specified in the method parameter contains trusted script).

For the Create() method of ExternalReportsManager and ExternalDataProcessorsManager objects, the UnsafeOperationProtection parameter is implemented.

This feature was not provided.When adding an external report or an external data processor from a file, you can specify that the file contains trusted script and therefore does not require displaying the unsafe operation protection system warning.
1C:Enterprise script.
The option to omit a notification description handler is implemented. Use this option in scenarios where you would create an empty handler (because the result of the execution of an asynchronous method is not important and only the handler for the method errors is important).

Now you can omit any parameter of the NotifyDescription constructor.

A handler for asynchronous method errors could only be created together with an empty handler for the method execution result.Simplified handling of asynchronous method errors.
ZIP archive operations.
When 1C:Enterprise accesses a file name using the properties of ZipFileEntry object (this includes the scenario when a file is being written to the disk), it replaces invalid characters with underscores (_). The list of invalid characters includes all characters that are not allowed in Windows file names. 1C:Enterprise makes the replacement on all operating systems.This change is not implemented in 8.3.10 compatibility mode.

To provide access to the original file names (before the character replacement), the following properties are implemented for ZipFileEntry object: OriginalFullName, OriginalName, OriginalPath, OriginalExtension, and OriginalBaseName.

If a name of a file stored in a ZIP archive contained invalid characters, the name was truncated, leaving only the part before the first invalid character. The list of invalid characters included all characters that were not allowed in Windows file names. This might cause issues when extracting files whose names contained invalid characters.Any file can be successfully extracted from a ZIP archive on any operating system. The names of the extracted files might change,
Data display.
Spreadsheet documents.
The look of a spreadsheet document containing SVG pictures in the thin client exactly matches the look of that document in the following cases:
  • In the web client
  • When exported to HTML5 format
The look of a spreadsheet document containing SVG pictures in the thin client could differ from the look of that document in the following cases:
  • In the web client
  • When exported to HTML5 format
Unified look of spreadsheet documents in various client applications and export formats.
Infobase operations.
Server clusters.
In client/server mode, the reliability of the following operations is improved:
  • Restructure database configuration
  • Create initial image of a distributed infobase
  • Restore infobase from a .dt file
In client/server mode, the following operations might cause issues:
  • Restructure database configuration
  • Create initial image of a distributed infobase
  • Restore infobase from a .dt file
Improved reliability of some operations in client/server mode.
Spreadsheet documents.
Web client.
When a spreadsheet document is exported to PDF format, the resulting document includes the page size and orientation (PickTrayByPDFSize property of a PDF document).

If you need to print the resulting document on custom-size paper from a web browser, it is recommended that you set the PrintAccuracy property of the spreadsheet document to Accurate. In Microsoft Internet Explorer, you do not need to use this property.

When a spreadsheet document was exported to PDF format, the resulting document did not include the page size and orientation. Printing the resulting document required a manual check of paper size and orientation in the PDF viewer.Eliminated unexpected system behavior.
Common objects.
Configuration properties.
If you access the UsePurpose property of the entire configuration or a managed form from 1C:Enterprise script, it has Undefined value.When the UsePurpose property of the entire configuration or a managed form was accessed from 1C:Enterprise script, it had FixedArray type, with the selected values as array elements.Eliminated unexpected system behavior. The behavior of this property is now similar to the behavior of other properties that do not affect application functionality in 1C:Enterprise mode.
Web client.
In the web client, the performance of opening system dialog boxes, as well as dialog boxes opened using ShowQueryBox() and ShowMessageBox() methods, is improved.In the web client, opening system dialog boxes, as well as dialog boxes opened using ShowQueryBox() and ShowMessageBox() methods, took more time.Improved performance and reliability of the window subsystem of the web client.
Spreadsheet documents.
In spreadsheet documents, there is no spacing between pictures and their borders.

This change is not implemented in 8.3.10 compatibility mode.

In spreadsheet documents, unexprected spacing might appear between pictures and their borders.Eliminated unexpected system behavior.
Full-text search.
Morphological full-text search by attribute name is now supported.

It is recommended that you rebuild the full-text search index in order to use this feature.

This change is not implemented in 8.3.10 compatibility mode.

Morphological full-text search by attribute name was not supported.Full-text search by attribute name is more user-friendly.
Data exchange.
ThisNode() method of ExchangePlan object always returns a reference to the exchange plan item with ThisNode property set to True.

This change is not implemented in 8.3.10 compatibility mode.

ThisNode() method of ExchangePlan object did not always return a reference to the exchange plan item with ThisNode property set to True.Eliminated unexpected system behavior.
Queries.
In the query language, if a CASE operation includes a nested CASE operation or ISNULL() function, which uses both a virtual field and a nonvirtual field, the CASE calculation result is correct.In the query language, if a CASE operation included a nested CASE operation or ISNULL() function, which used both a virtual field and a nonvirtual field, the CASE calculation result was incorrect and this might cause an unexpected shutdown.Eliminated unexpected system behavior.
Charts.
The chart view in the thin client and web client is unified:
  • Area sizes specified in the form attribute always affect the chart view.
  • Chart behavior is unified across client applications.
  • Area sizes used to draw a chart exactly match the area sizes retrieved using 1C:Enterprise script.

This change is not implemented in 8.3.10 compatibility mode.

The chart views in the thin client and web client were different:
  • Area sizes specified in the form attribute did not always affect the chart view.
  • Chart behavior was not unified across client applications.
  • Area sizes used to draw a chart did not exactly match the area sizes retrieved using 1C:Enterprise script.
Eliminated unexpected system behavior. The chart view is more predictable.
Development tools.
During application debug, you can access variable properties (provided that it has properties) even if the variable presentation is not available.During application debug, if a variable presentation was not available, the variable properties were also not available.Eliminated unexpected system behavior.
Dumping configurations to files/Restoring configurations from files.
Intertactive export of configurations to files is always performed in hierarchical format. The flat format is only supported in batch Designer mode.

It is recommended that you always use the hierarchical format.

The interactive export of configurations to files offered a choice between flat and hierarchical formats.The option to export configuration files in flat format is disabled due to possible issues. For example, transferring exported files between different file systems might be difficult.
Development tools.
During debugging over TCP, debugger no longer stops responding while calculating an expression or editing a variable value.During debugging over TCP, debugger might stop responding while calculating an expression or editing a variable value.Application debugging over TCP is more predictable and reliable.
Client application.
In the Start menu, a single shortcut combines 32-bit and 64-bit versions of 1C:Enterprise.

1C:Enterprise installation on a computer with any operation system of Windows family adds all of the available 1C:Enterprise shortcuts to the Start menu.

Pinning a running 1C:Enterprise application to the taskbar actually pins a shortcut to file 1cestart.exe. If multiple 1C:Enterprise applications are running, they are combined into a single taskbar shortcut.

The jump list is only available if the shortcut to 1cestart.exe is pinned to the taskbar.

The Start menu included two 1C:Enterprise shortcuts: one for the 32-bit version and the other one for the 64-bit version.

1C:Enterprise installation on Windows 8 or later did not add all of the available 1C:Enterprise shortcuts to the Start menu.

Pinning a running 1C:Enterprise application to the taskbar pinned exactly that application. If multiple 1C:Enterprise applications were running, they were combined in this shortcut.

The jump list was available for any 1C:Enterprise-related shortcut.

All of the 1C:Enterprise components are available on the Start menu. The jump list behaviour is more predictable.
Data composition system.
The parsing algorithm of data composition system queries validates comparison operations that include String parameters of unlimited length. The parsing is performed when the data composition system wizard is opened and when a schema-based source of available settings is initialized (opening reports also includes this operation).The parsing algorithm of data composition system queries that included String parameters of unlimited length generated errors stating that using strings of unlimited length in queries was not allowed.Eliminated unexpected system behavior.
Collaboration system.
In the collaboration system, video calls use peer-to-peer connections instead of using a central server. The central server is only required to establish connections between the conversation participants.In the collaboration system, video calls always used the central server and did not use peer-to-peer connections.Reduced load on the central server of the collaboration system. If conversation participants belong to a local network, the video call traffic is limited to local network.
Collaboration system.
If 1C:Enterprise connects to the collaboration server through a proxy server, it gets the proxy server settings from the operating system settings or from inetcfg.xml configuration file. NTLM authentication at proxy servers is not supported.Connection to the collaboration server through a proxy server was not supported.Simplified collaboration system setup in scenarios that include a proxy server.
Information registers.
When an information register record set is written using InformationRegisterRecordSet.Write(), Undefined value is not ignored when setting a managed lock.

This change is not implemented in 8.3.10 compatibility mode.

When an information register record set was written using InformationRegisterRecordSet.Write(), Undefined value was ignored when setting a managed lock. This resulted in locking excessive data.Improved parallel writing of information register record sets when multiple users write dimensions of composite types where dimension values can be blank.
Localization.
Support of Kazakh user interface (kk language code) is restored.Support of Kazakh user interface was not available.1C:Enterprise now provides the option to use Kazakh user interface.
Localization.
The French interface language (language code: fr) is not supported.The French interface language (language code: fr) was supported.The French interface language is not supported.
Server clusters.
On Linux, the working process parameter Memory occupied is calculated based on VmRSS (resident set size) value.

The value of Memory occupied parameter in absolute terms is reduced and it is more accurate.

It is recommended that you revise the working process restart options in the working server properties.

On Linux, the working process parameter Memory occupied was calculated based on VmSize (virtual memory usage) value.

On Linux, the cluster monitoring system uses a parameter that provides more accurate data.
Localization.
Entering Russian Ruble symbol (₽, ISO 4217 643) from the keyboard is supported.This feature was not provided.Eliminated unexpected system behavior.
Applied objects.
When floating point numbers are converted between 1C:Enterprise format and external formats, the accuracy of their presentations is never lost.

In scenarios where previously accuracy losses were possible, the conversion algorithm does not depend on the operating system.

When floating point numbers were converted between 1C:Enterprise format and external formats, accuracy losses were possible.

In scenarios where accuracy losses were possible, the conversion algorithm depended on the operation system.

Reduced number of scenarios where conversion of floating point numbers with significant digits in their fractional parts between 1C:Enterprise format and external formats (such as XSL file format) introduces accuracy losses.
Linux.
Improved reliability of the Linux version of 1C:Enterprise in some scenarios.In some scenarios, reliability of the Linux version of 1C:Enterprise was insufficient.Improved stability of the Linux version of 1C:Enterprise.
Technological log.
Updated the <ADMIN> event content and description in the documentation and in the technological log configuration file editor. (read more)The <ADMIN> event content and description in the documentation and in the technological log configuration file editor were incorrect.The technological log configuration file editor is now up-to-date.

Comments
0
Add comment