1C:Enterprise 8.3.10. New functionality and changes.

Version 8.3.10 includes known bug fixes and functionality modifications.

New functionality and changes
New functionality and changes in the 1C:Enterprise mode
Optimization
Changes that affect system behavior
Changes that require modification of configuration and administrative settings
Renamed objects
Mobile platform
Transition from the previous version to the version 8.3.10

New functionality and changes

Functionality	After	Before	Result of changes
Configuration properties.	For configuration property Compatibility mode, new value Version 8.3.9 is now implemented.	Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.8 was implemented.	Configurations developed in version 8.3.9 or earlier now run in version 8.3.10 without requiring any changes to configuration or to data structures. This allows for transition to version 8.3.10 in two stages: first, version update is applied (without any changes to configuration); then, any needed changes are applied and compatibility mode is disabled. This also allows using version 8.3.9 for infobase operations, if necessary, after transition to version 8.3.10. Compatibility mode must be enabled to use version 8.3.9. If you disabled it, enable it again.
Web client, web service, and HTTP service publishing tools.	In the "publish to web server" dialog box, parameters related to OpenID authentication are now on a separate tab. In the "publish to web server" dialog box, also implemented entering a list of URLs that can be used for user redirection after OpenID authentication.	The only method of specifying a list of URLs that can be used for user redirection after OpenID authentication was to edit default.vrd file manually.	When publishing to web servers, you can interactlvely specify all of the parameters defined in default.vrd file.
Client application installation.	Rules for detecting computers with Ukrainian language pack are improved. When a 1C:Enterprise client application is being installed on Windows, the installer language and the default platform language are set to Ukrainian if at least two of the following conditions are met: The home location specified in the operating system settings is Ukraine. Ukrainian keyboard layout is installed. Ukrainian hryvnia (UAH) is selected as the currency unit. Ukrainian locale is selected in the operating system settings. Ukrainian is set as the default operating system language.	When a 1C:Enterprise client application was being installed on Windows, the default platform language was set to Ukrainian only if the primary operating system language was Ukrainian. The only way to run the installer in Urkainian was using the /luk command-line option.	Improved 1C:Enterprise installer usability for Ukrainian speakers.
1C:Enterprise script. Administration tools.	Implemented functionality for collecting information on circular references during 1C:Enterprise script execution. Using this feature may result in reduced application performance. It is recommended that you use this feature for testing purposes only. Implemented global context method CheckScriptCircularRefs(). For technological log settings file (logcfg.xml), implemented item <SCRIPTCIRCREFS>. Implemented technological log event <SCRIPTCIRCREFS>. Implemented command-line option for the thin client and thick client startup: /EnableCheckScriptCircularRefs. Implemented command-line parameter for 1C:Enterprise server startup: -EnableCheckScriptCircularRefs. In the dialog box used to specify client application startup parameters from Designer, implemented parameter Detect 1C:Enterprise script circular references. Implemented parameter EnableCheckScriptCircularRefs in file conf.cfg. If 1C:Enterprise is started with option/parameter EnableCheckScriptCircularRefs, discovery of any circular reference will result in unrecoverable error containing information on the discovered circular reference.	This feature was not provided.	Diagnostics of circular reference usage in 1C:Enterprise script is now more intuitive.
Configuration extensions.	In module editor, implemented functionality for adding a specific method to extension (when working with a configuration being extended). In module editor, implemented navigation from annotation of extending method to method being extended (when working with an extension). Implemented keyboard shortcut Alt+Shift+F2 for command Add to extension. Keyboard shortcut Alt+F2 for this command is now disabled.	User-friendly functionality for adding methods to extensions was not available. Navigation from annotation of extending method to method being extended was not available. Keyboard shortcut Alt+F2 was used for command Add to extension.	Creating 1C:Enterprise script-based module extensions is now more ergonomic.
Dynamic lists.	Implemented additional processing for data received by a dynamic list before the data is displayed. Implemented event OnDataGetAtServer. In version 8.3.7 compatibility mode, behavior remained unchanged.	This feature was not provided.	It is now easier to use dynamic lists to output linked data that was previously extremely difficult or impossible to obtain through dynamic list query.
Managed forms.	Implemented arbitrary scaling of managed forms in Taxi interface. If compact display mode is set at application level, interactive scaling is disabled. Form size settings are saved per DPI value and per form scale value. Implemented managed form property Scale, command Change scale in client application menu View, and system command bar button used to open the scale change dialog box. This change is not implemented in 8.3.6 compatibility mode. Implemented support for picture variant sets in client applications for PC (thick client, thin client, and web client). Added variants of system pictures used for client applications. Implemented new resolutions for picture variants: bldpi (85% scale), aldpi (125% scale), amdpi (175% scale), and udpi (400% scale). In picture variant set manifest, implemented choice of target interface for each variant. To define size of picture variants more precisely, implemented parameters for height and width of each variant in picture variant set manifest. For system enumeration PictureSize, implemented values RealSizeIgnoreScale and AutoSizeIgnoreScale.	This feature was not provided. Compact viewing mode was available at form level and at application level (through 1C:Enterprise script). Picture variant sets were supported in mobile application only.	Interface customization is now more user-friendly.
1C:Enterprise script.	Implemented generation of text strings whose content depends on a number specified in a string. Examples: 1st week of the month, 2nd week of the month. Implemented the StringWithNumber() function. The following langauges are supported: Azerbaijanian, Belarusian, Chinese, Bulgarian, English, Estonian, Finnish, French, Georgian, German, Hungarian, Kazakh, Kyrgyz, Latvian, Lithuanian, Polish, Romanian, Russian, Turkish, Turkmenian, Ukrainian, and Vietnamese,	This feature was not provided.	Generation of text strings whose content depends on a number specified in a string is now streamlined.
Spreadsheet documents.	Implemented getting data area size value during import from third-party spreadsheet formats: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument). For object SpreadsheetDocument, implemented methods GetDataAreaHorizontalSize() and GetDataAreaVerticalSize().	This feature was not provided.	It is now easier to import documents in third-party spreadsheet formats without clearly defined boundaries of imported data area.
Development tools. OData interface.	Implemented server debug item Standard OData interface intended for debugging 1C:Enterprise script running during queries to standard OData interface. Changed debug item sorting rules that apply to debug item lists (for HTTP debug protocol). Changed auto attachment dialog box (for TCP debug protocol).	Debugging of 1C:Enterprise script running at the server side during infobase calls through standard OData interface was not supported. Debug item sorting rules that apply to debug item lists (for HTTP debug protocol) were different. Auto attachment dialog box for TCP debug protocol displayed debug items in a different order.	It is now easier to debug 1C:Enterprise scripts using standard OData interface.
Managed forms.	The option to manage height for managed form tables that display data other than dynamic lists is implemented. This includes the option to have table height resized automatically based on the amount of data displayed. The HeightControlVariant managed form table property is implemented. This change is not implemented in 8.3.9 compatibility mode.	This option was not provided on the desktop platform. It was only available on the mobile platform. The HeightControlVariant managed form table property was ignored on the desktop platform.	The option to add a form table that does not display dynamic list data and still is automatically resized based on the number of rows is implemented. This reduces the number of scroll bars and saves form space.
Software licensing. Technological log.	For technological log, implemented registration of events associated with: Granting and releasing licenses (both software and HASP) Granting licenses to base versions Regular checks for discrepancies between the actual hardware and the list of hardware components stated in a license Implemented technological log event <LIC>. The <HASP> technological log event allows to analyze technological aspects of HASP management only (HASP interface calls); it does not allow to monitor granted or released licenses with HASP keys.	This feature was not provided. Only the option to check HASP key operations using the <HASP> event was provided.	Easier investigation of license-related issues.
Data composition system.	Values of type DataComposionSchemaNestedDataSet can now be added to collection DataComposionSchemaDataSetFields. Implemented values of type DataComposionSchemaDataSetFields to be used in methods Add() and Insert() of object DataComposionSchemaDataSetFields.	Values of type DataComposionSchemaNestedDataSet could not be added to collection DataComposionSchemaDataSetFields.	Now it is possible to create a data composition schema with nested data sets using 1C:Enterprise script.
Managed forms.	Implemented control of planner interval background color in accordance with values of measurements associated with this interval. Implemented property PlannerBackgroundInterval.DimesionValues.	Planner interval background color management based on the values of dimensions associated with this interval was not available. Planner interval background color could only be changed for date intervals.	Visual customization of planner is enriched.
Development tools.	Implemented option for running Designer in agent mode. This is a variation of batch mode where Designer operates as an SSH or SFTP server and accepts commands sent through these protocols. While in agent mode, Designer can only work with a single infobase at a time. If access to multiple infobases is required, it is recommended that you run several instances of Designer in agent mode. Implemented command-line options for batch mode: /AgentMode, /AgentPort, /AgentListenAddress, /AgentSSHHostKey, /AgentSSHHostKeyAuto, and /AgentBaseDir. Changed behavior of command-line options /Visible and /LoadConfigFromFiles when used in agent mode. If you need a client application to connect to SSH or SFTP servers, you can now use any application with SSH/SFTP functionality that supports text command exchange with SSH and SFTP servers (examples: putty, winscp, MobaXTerm). This functionality is currently available in beta status.	This feature was not provided.	Designer connectivity automation capabilities are now expanded. Response time of Designer is improved because a separate instance of Designer is no longer started on each call.
Formatted documents.	Implemented saving formatted documents in PDF format (both in interactive mode and by using method FormattedDocument.Write()) . Implemented value FormattedDocumentFileType.PDF.	This feature was not provided. Formatted documents could be only saved in HTML format or as plain text without formatting.	Formatted document management capabilities are now expanded.
Spreadsheet documents.	Implemented 1C:Enterprise script-based management of how row, column, and cell names are displayed in spreadsheet documents. For object SpreadsheetDocument, implemented properties ShowRowAndColumnNames and ShowCellNames. In spreadsheet document editor menu (in 1C:Enterprise mode), implemented commands for defining view of named areas and for assigning area names.	1C:Enterprise script-based management of how row, column, and cell names are displayed in spreadsheet documents was unavailable.	It is now easier to organize editing of spreadsheet documents containing named areas.
Technological log.	Implemented logging of events that occur upon initial connection of 1C:Enterprise server to Microsoft SQL Server database. The events are saved in the technological log. The logging is based on event <DBMSSQLCONN>.	This feature was not provided.	It is now easier to investigate incidents associated with loss of connection between 1C:Enterprise server and Microsoft SQL Server database.
Configuration extensions.	The help available in a configuration being extended includes reference information on extension objects. The reference information on the extension is included in the help search results.	This feature was not provided. Reference information implemented in a configuration extension was missing from the help tree and could not be accessed through searching.	Eliminated unexpected system behavior. Reference information from an extension is included in the help available in the configuration being extended, making it easier to use the resulting configuration.
Spreadsheet documents.	When importing spreadsheet documents from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files, areas of the resulting document that match sheets of the original document are marked up as named row ranges. Names of sheets of the original document are converted into range names so as to satisfy rules of 1C:Enterprise script ID generation. When importing spreadsheet documents from Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) files, sheets with no names provided are imported normally and areas defining these sheets are given automatically generated names. This change is not implemented in 8.3.9 compatibility mode.	When importing spreadsheet documents from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files, areas of the resulting document that matched sheets of the original document were not marked up. When importing spreadsheet documents from Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) files, sheets with no names provided were not imported.	It is now easier to process spreadsheet documents created by importing multipage XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files. It is now easier to recognize pages of the imported documents.
Configuration extensions.	For configuration extensions, implemented configuration extension purposes: Patch, Customization, and AddOn. Extensions are applied in the following order: All extensions with purpose Patch All extensions with purpose Customization All extensions with purpose AddOn Multiple extensions with the same purpose are applied in no specific order. Purpose of extensions that are already loaded to the infobase is automatically set to Customization. Implemented property ConfigurationExtension.Purpose.	This feature was not provided. All extensions were applied with the same priority.	It is now possible to sort extensions by function. It is now easier to understand the purpose of any extension.
Configuration extensions. Spreadsheet documents.	Implemented extensions for spreadsheet documents. Implemented merging of spreadsheet documents during configuration update that uses a file in .cf or .cfu format.	The spreadsheet document extension feature was not provided. The feature allowing spreadsheet document merging during configuration update was not provided.	Configuration extension offers more features now. Additional spreadsheet document management features are now provided for supported configurations.
Pictures.	Implemented getting a specific picture from a picture variant collection based on DPI, display scale factor, and template picture flag. For methods Convert(), Write(), GetBinaryData(), and FileNameFilter() of Picture object , implemented parameters AllVariants and PickVariant.	Platform behavior upon attempt to get a specific picture from a picture variant collection was not defined. This activity could result in system failure.	Eliminated unexpected system behavior. Getting a specific picture (best matching the current display mode) from a picture variant collection is now supported.
Charts.	Now fractional values can be used to define boundaries of gauge chart bands. This change is not implemented in 8.3.9 compatibility mode.	Fractional values could not be used to define boundaries of gauge chart bands.	An additional chart appearance control feature is now implemented.
Charts. Data composition system.	Implemented the following chart display options (also available in data composition system): Displaying trendlines Customizing appearance of series in charts Customizing appearance of series in chart legends Implemented system enumerations ChartTrendLineApproximationType, ChartTrendLineFactor, StockChartUsedPointValue, ShowInChart, and ShowInChartLegend. For system enumeration ChartLabelLocation, implemented values: Auto, TopLeft, BottomLeft, TopRight, BottomRight, TopAndLeftSpecified, and EmptySpace. For system enumeration ChartMarkerType, implemented values Alternation and Auto. Implemented objects ChartLabelArea and ChartTrendLine. For object ChartSeries, implemented properties Trendlines, ShowGraphicalDataRepresentationInChart, and ShowGraphicalDataRepresentationInChartLegend. For property ChartSeries.Marker, the default value is set to Auto. This change is not implemented in 8.3.9 compatibility mode. For objects DataCompositionAreaTemplateChartGroupingAppearance and DataCompositionAppearance, implemented parameters ChartTrendline, ShowGraphicalDataRepresentationInChart, and ShowGraphicalDataRepresentationInChartLegend.	These features were not provided. Value of property ChartSeries.Marker was set to Square, Circle, or Diamond, based on series number.	Additional chart features, related to appearance control and analytics, are now implemented.
Charts. Data composition system.	Implemented new chart types: scatter chart and bubble chart. For Chart object, implemented properties BubbleSizeCommonSeries, BubbleSizeValueSource, DefaultBubbleSize, MinBubbleSize, MaxBubbleSize, ChartBubbleSizing, and BubbleChartNegativeValuesShowMode. Implemented the following chart management features: Selecting data source for point axis. For Chart object , implemented properties PointsAxisValuesSource and PointsAxisSeries. Managing chart axis display options. For Chart object, implemented properties ValuesAxis and PointsAxis. Specifying fractional values for minimum and maximum chart values. Specifyimng the method used to determine minimum and maximum chart values. This change is not implemented in 8.3.9 compatibility mode. Managing line connections between chart dots (where possible). Implemented property Chart.PointsConnection. Use automated calculation of chart transparency. For system enumeration ChartSemitransparencyMode, implemented value AutoCalculate. Expanded set of values that can be used in chart labels. For ChartLabelType system enumeration, implemented values ValueSize, SeriesSize, SeriesValueSize, SeriesPointSize, SeriesPointValueSize, PointSize, and PointValueSize. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.ValuesAxis, ChartType.PointsAxis, ChartType.PointsAxisValuesSource, ChartType.PointsAxisSeries, ChartType.BubbleSizeValueSource, ChartType.BubbleSizeCommonSeries, ChartType.DefaultBubbleSize, ChartType.MinBubbleSize, ChartType.MaxBubbleSize, ChartType.BubbleSizing, ChartType.BubbleChartNegativeValuesShowMode, and ChartType.PointsConnection. For data composition system object DataCompositionAreaTemplateChartGroupAppearance, implemented properties PutOnPointsAxis and UseAsCommonBubbleSizeSeries. Properties AutoMaxValue and AutoMinValue are now deprecated and supported for compatibility purposes only.	These features were not provided. Scatter charts and bubble charts were not implemented. Fractional values could not be used for properties MinValue and MaxValue of Chart object. Properties AutoMinValue and AutoMaxValue were used for calculating minimum and maximum chart values.	Additional chart features are now implemented.
Charts. Data composition system.	Implemented custom labels for chart scales. For ChartPlotArea object, implemented properties PointsScale, ValuesScale, and SeriesScale. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.PointsScale, ChartType.ValuesScale, and ChartType.SeriesScale.	These features were not provided.	Additional chart appearance control features are now implemented.
Charts. Data composition system.	Implemented custom point display order for bar charts. For Charts object, implemented property BarChartPointsOrder. This change is not implemented in 8.3.9 compatibility mode. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameter ChartType.BarChartPointsOrder.	These features were not provided. Points in bar charts were always displayed in bottom-to-top order (the first point at the bottom of the chart).	Additional chart appearance control features are now implemented.
Data composition system. Charts.	Implemented customization of scale lines, scale color, series markers, series indicators, and series line types when displaying charts. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.ScaleLines and ChartType.ScaleColor. For data composition system objects DataCompositionAreaTemplateChartGroupAppearance and DataCompositionAppearance, implemented properties LineInChart, MarkerInChart, and IndicatorInChart.	These features were not provided.	Additional features of chart appearance control through data composition system are now implemented.
Collaboration system.	Implemented the "collaboration system" feature. It is a text message and call system for 1C:Enterprise application users. It features audio calls with optional video feed.. Text conversations can be related to specific infobase objects (context conversations) or not related to any objects (noncontext conversations). Access to conversations is allowed or denied based on the object access rights. Implemented Collaboration system management standard function. Implemented notifications about new messages. Implemented conversation management using 1C:Enterprise script tools. Implemented CollaborationSystem global context property. For ManagedForm object, implemented ConversationsRepresentation property. This property is not available in 8.3.9 compatibility mode. Implemented CollaborationSystemInfoBaseRegistration access right. The web client supports the collaboration system if it runs in one of the following browsers: Google Chrome, Mozilla Firefox, Safari, Microsoft Edge, or Microsoft Internet Eхplorer version 10.0 or later. All of the messages are stored on the collaboration system server. To start using the collaboration system, you have to register your infobase on the collaboration system server. Initially the server is available as the 1cDialog.com service hosted by 1C Company. Note that in order to use the collaboration system you have to open Internet access to wss://1cdialog.com. A distribution kit for a local collaboration system server will be available in a future release. Therefore, you will have a choice between using 1cDialog.com service and running a local server. Using calls is limited during the beta testing period. Call usage instructions will be available separately. This feature currently has beta status. The service access terms will be available separately.	This feature was not provided.	The new feature provides 1C:Enterprise application users with communication options that are tightly integrated into the application interface and business logic.
Dumping configurations to files/Restoring configurations from files.	Implemented partial dump of the configuration being edited to XML files. During partial dump, only objects that were modified since the previous dump are dumped. The file ConfigDumpInfo.xml containing information about all dumped configuration objects is created. This file also contains internal versions of all dumped objects. An object is not dumped during a partial dump if its version numbers in Designer and in file ConfigDumpInfo.xml are identical. Moreover, a file containing information about the differences between the current and the previous dump can be generated. When restoring data from XML files, users can specify that the file containing information about dumped configuration objects must be updated. In this case, information matching the configuration state after it is restored is saved to this file. For Designer batch mode command-line option /DumpConfigToFiles, implemented parameters update, force, getChanges, configDumpInfoForChanges, and listFile. For Designer batch mode command-line option /LoadConfigFromFiles, implemented parameter updateConfigDumpInfo.	Partial dump of configurations to XML files was not supported. Only full configuration dump was implemented.	Dumping configurations to XML files is now faster. especially dumping very large configurations with minor changes.
Dynamic lists.	Implemented management of availability of dynamic list fields (including subordinate fields) for use in groupings, filters, and order settings. Implemented methods SetUseRestrictionsInGroup(), SetUseRestrictionsInOrder(), SetUseRestrictionsInFilter(), GetUseRestrictionsInGroup(), GetUseRestrictionsInOrder(), and GetUseRestrictionsInFilter().	These features were not provided.	Now developers can explicitly prohibit groupings, ordering, and filtering for fields not intended for these operations.
Window-based interface. Dumping configurations to files/Restoring configurations from files.	Implemented visibility management for managed form title. Implemented property ManagedForm.ShowTitle. Implemented visibility management for form closing button. Implemented property ManagedForm.ShowCloseButton. Implemented selection of main application window display mode. Normal. Default display mode for main application window. Workstation. Many items on the system commands area are hidden; all panes in the main application window are hidden; navigation buttons on the home page (including the home page label) are hidden; some of the keyboard shortcuts are disabled. Full-screen workstation. Same as Workstation mode but the application window is displayed in full-screen mode. Kiosk. Same as Full-screen workstation mode but the About button and the hyperlink with user name located in the system commands area are hidden. Implemented global context property ClientApplication that provides access to client application settings (such as getting and changing the client application window title). For metadata object that describes the configuration, implemented property MainClientApplicationWindowMode. Changed version number of format used for dumping configurations to files. The following global context methods are now deprecated. It is recommended that you do not use any of these: SetShortApplicationCaption(), GetShortApplicationCaption(), SetClientApplicationCaption(), GetClientApplicationCaption(), ClientApplicationBaseFontCurrentVariant(), and ClientApplicationInterfaceCurrentVariant(). The above features are available in Taxi interface.	These features were not provided.	Expanded capabilities of client application appearance management. Now a specific interface can be enabled (cashier's interface, self-service kiosk, and more).
Configuration extensions. Common attributes / Data separation.	Implemented a flag specifying whether a common attribute used as a separator can separate configuration extensions. For CommonAttribute configuration object, implemented property ConfigurationExtensionsSeparation. It is recommended that you disable extension separation for separators in Independent and shared mode.	Any configuration separators could be used to separate configuration extensions. Disabling extension separation was not possible if data separation was enabled at infobase level.	Now developers have control over separation of configuration extensions to be used in the infobase. For example, a configuration developer can specify that none of the separators available in the application can be used to separate configuration extensions.

Table of contents

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Web client. Spreadsheet documents.	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.
Managed forms.	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.
Managed forms.	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.
Interface.	The opened items panel was redesigned in Taxi interface: The width of each panel item now depends on the window title. If the panel is horizontal, one line is used to display the title; if the panel is vertical, an unlimited number of lines can be used. If the panel is horizontal, the control item used to access the full list of open windows is located in the right section of the panel. If the panel is vertical, a scroll bar might be displayed. In this case, the panel and the work area of the main window can be scrolled separately. Implemented closing windows by clicking the wheel button on a corresponding item on the opened items panel. Implemented multiple window closing methods in the context menu of a panel item. Implemented dragging windows within the panel to change their order. If the opened items panel is displayed, the home page button is hidden from the work area of the main window.	Appearance and functionality of the opened items panel (in Taxi interface) were different: The width of each panel item was fixed regardless of the item content. If the panel was horizontal, one or two lines were used to display the item title. Windows could not be closed by clicking the wheel button on a corresponding item on the opened items panel. The window order on the opened items panel could not be changed interactively. The home page button was always displayed in the work area of the main window.	It is now easier to use the opened items panel in Taxi interface.
Spreadsheet documents. Web client.	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: Line type Double was replaced by Solid. Line types ThinDashed, ThickDashed, and LargeDashed were replaced by type Dotted.	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.
Managed forms.	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.
Dynamic lists.	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.
Managed forms.	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.
Client application. Data display.	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.

Table of contents

Optimization

Table of contents

Changes that affect system behavior

Functionality	After	Before	Result of changes
Background and scheduled jobs. Server clusters.	Changed approach to storing background and scheduled job execution history. In client/server mode, the stored history data was broken down by infobase. The following history data is stored for each infobase: Up to 1 000 1C:Enterprise script-based background jobs Up to 1 0000 scheduled jobs Up to 1 000 system background jobs (i.e. background jobs created by system) For each job (background, scheduled, or system background), information about at least 3 latest job executions is saved, if possible. The three executions limit can be reduced if over 1 000 records are created for any given job type.	In file mode, the stored job history data was broken down by infobase. In client/server mode, the stored job history data was broken down by server cluster. In both cases, data was stored on the total of 1 000 jobs, regardless of job type (background, scheduled, or system background).	Improved diagnostics of background and scheduled job execution when a large amount of jobs is present in the system. Reduced risk of information about rarely used 1C:Enterprise script-based background jobs being superseded by information about a large amount of scheduled jobs or system background jobs.
Data display. Charts.	For objects Chart, GanttChart, PivotChart, and Dendrogram, the default value of Font property of subordinate objects describing specific chart areas is set to Auto, meaning Normal text font. When the web client is running on Windows, the procedures of displaying charts in the web client, exporting spreadsheet documents containing charts to HTML5 format, and exporting charts to SVG format include checks for OS-based substitutions of chart fonts. If the OS substitutes chart fonts, the resulting files include the names of the fonts that are actually used. When exporting spreadsheet documents to HTML format and displaying spreadsheet documents in the web client, system fonts are not substituted by Arial; instead, the names of the fonts that are actually used are determined.	For objects Chart, GanttChart, PivotChart, and Dendrogram, the default value of Font property of subordinate objects describing specific chart areas was set to Text font. When the web client was running on Windows, the procedures of displaying charts in the web client, exporting spreadsheet documents containing charts to HTML5 format, and exporting charts to SVG format included exporting fonts "as is", without attempting to determine which fonts were actually used. When exporting spreadsheet documents to HTML format and displaying spreadsheet documents in the web client, system fonts were substituted by Arial.	Unified fonts used to display charts across client applications, including the web client running in a variety of web browsers. Unified fonts used to display spreadsheet documents across client applications. When exporting spreadsheet documents containing charts, original fonts used to display the charts are retained.
Binary data.	Binary data management capabilities are now expanded. Implemented bilateral conversion between binary data and the following data types: binary data array, string, binary data buffer, Base64 string, hexadecimal string, and binary data as string. Implemented binary data usage in methods and constructors that previously supported files only. Implemented bitwise operations (AND, OR, NOT, XOR, NAND, and inversion) for binary data stored in a binary data buffer. Implemented binary data exchange with add-ins for add-in developers (also available in the web client). Implemented getting bulk permissions when working with binary data in the web client. Implemented direct copying of binary data from DataReader object to DataWriter object. Implemented global context methods ConcatBinaryData(), SplitBinaryData(), GetBinaryDataFromString(), GetBinaryDataBufferFromString(), GetStringFromBinaryData(), GetStringFromBinaryDataBuffer(), GetBinaryDataFromBase64String(), GetBinaryDataBufferFromBase64String(), GetBase64StringFromBinaryData(), GetBase64BinaryDataFromBinaryData(), GetBinaryDataFromBase64BinaryData(), GetBase64BinaryDataBufferFromBinaryDataBuffer(), GetBinaryDataBufferFromBase64BinaryDataBuffer(), GetBinaryDataFromHexString(), GetBinaryDataBufferFromHexString(), GetHexStringFromBinaryData(), GetHexStringFromBinaryDataBuffer(), GetHexBinaryDataFromBinaryData(), GetBinaryDataFromHexBinaryData(), GetHexBinaryDataBufferFromBinaryDataBuffer(), GetBinaryDataBufferFromHexBinaryDataBuffer(), GetBinaryDataFromBinaryDataBuffer(), GetBinaryDataBufferFromBinaryData(), NumberFromHexString(), and NumberFromBinaryString(). Implemented the option to use binary data streams: In TextReader, TextWriter, ZipFileReader, and ZipFileWriter object constructors In Open() method of TextReader, TextWriter, ZipFileWriter, and ZipFileReader objects In Write() method of TextDocument, SpreadsheetDocument, FormattedDocument, GeographicalSchema, and Picture objects In Put() method of FTPConnection object In Read() method of TextDocument, SpreadsheetDocument, and GeographicalSchema objects In the following methods of CryptoManager object: Encrypt(), Decrypt(), Sign(), and VerifySignature() In method CryptoCertificate.Unload() In method DataHashing.Append() In method FTPConnection.Get() Implemented OpenStream() method for objects HTMLReader, HTMLWriter, JSONReader, JSONWriter, FastInfosetReader, FastInfosetWriter, XMLReader, and XMLWriter. Implemented GetBodyAsStream() method for objects HTTPRequest, HTTPResponse, HTTPServiceRequest, and HTTPServiceResponse. Implemented method ConversionToCanonicalXML.CanonicalizeToStream(). For XSLTransform object, implemented methods LoadXSLStyleSheet() and Transform(). Implemented method ZipFileWriter.GetBinaryData(). For BinaryDataBuffer object, implemented methods WriteBitwiseAnd(), WriteBitwiseOr(), WriteBitwiseXor(), WriteBitwiseAntNot(), and Invert(). For DataReader object, implemented methods CopyTo() and BeginCopyTo(). For methods CopyTo() and BeginCopyTo() of Stream object, changed the purpose of the second method parameter and the return value: the number of bytes to be copied is passed as the second parameter, and the return value is the actual number of copied bytes. The buffer size is defined automatically. The method descriptions are now uniform with the similar methods of DataReader object. This change is not implemented in 8.3.9 compatibility mode.	For methods CopyTo() and BeginCopyingTo() of Stream object, the size of buffer used for copying was passed as the second parameter, and return values were not available.	It is now easier to use binary data for a range of applied tasks.
Event log.	In the event log (opened from a file or otherwise), each data presentation string recorded to the log when an event was registered is only displayed to users that have the right to view this data or Administration right. If a user does not have Administration right and the data presentation is probably unavailable to them, the saved data presentation is hidden from this user. If the Data field of an event log record contains a reference and a user probably has no rights to view the related data object, the Data presentation field is blank.	Access rights of the current user were not checked when displaying presentation of event log data.	Users with restricted rights no longer can access data objects that are unavailable to them by accessing presentations of unavailable objects that were saved earlier.
Development tools.	In the call stack window of the debugger, implemented correct display of method parameters containing extremely long text strings or multiline strings. In this case, the presentation is based on the initial 20 characters of the parameter string appended with ellipsis (...), continued with other parameters and the closing bracket of the method.	In the call stack window of the debugger, method parameters containing extremely long text strings or multiline strings were displayed incorrectly: text presentations of the following parameters (if any) and the closing bracket of the method were missing.	The accuracy of data in the call stack window is improved.
Spreadsheet documents.	When exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats, only right-aligned cell text is converted into numeric format. The content of cells without right alignment is saved as text. This change is not implemented in 8.3.9 compatibility mode.	When exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats, cell text was converted into numeric format regardless of text alignment.	Exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats is improved.
Print tools.	Implemented settings for default page size during printing (including printing to PDF file). This feature is available both for the web client and for documents generated by scheduled jobs. Implemented the PrintSettings object. In the web client parameters dialog box, implemented Default page size settings item. This change is not implemented in 8.3.9 compatibility mode.	A4 format was used as the default paper size. In the web client parameters dialog box, Default page size settings item was not available.	When printing a document (or saving it to a PDF file) in the web client, the paper size set for the current client application is used for pagination purposes. Thus, the resulting document better satisfies user expectations. This functionality is now also available for the documents generated by scheduled jobs.
Data composition system.	When loading data composition schema and data composition settings in interactive mode, style colors and fonts not available in the current configuration are automatically removed from the schema and settings.	When loading data composition schema and data composition settings in interactive mode, style colors and fonts not available in the current configuration caused XDTO data conversion errors.	Now data composition schema and data composition settings containing style colors and fonts not available in the current configuration can be used.
Dynamic lists.	Content of System fields folder cannot be used as selection fields in dynamic lists. If a dynamic list has no main table specified or the specified main table is missing a dynamic list key field, grouping fields cannot be set up for this dynamic list. This change is not implemented in 8.3.9 compatibility mode.	Content of System fields folder could be used as selection fields in dynamic lists. If a dynamic list had no main table specified or the specified main table was missing a dynamic list key field, grouping fields could be set up for this dynamic list, resulting in data retrieval error.	Eliminated unexpected system behavior. Dynamic lists are more reliable now.
Dynamic lists.	The following properties of DynamicList object are unavailable in the thick client: DynamicDataRead, MainTable, CustomQuery, and QueryText. Assigning values to managed form attributes of DynamicList type is not allowed. Passing attributes of DynamicList type as method parameters or return values in client/server interactions is not allowed. This change is not implemented in 8.3.9 compatibility mode.	The following properties of DynamicList object were available in the thick client: DynamicDataRead, MainTable, CustomQuery, and QueryText. However, changing their values did not affect the dynamic lists in any way. Assigning values to managed form attributes of DynamicList type was allowed. However, further behavior was not defined. Passing attributes of DynamicList type as method parameters or return values in client/server interactions was allowed. However, further behavior was not defined.	Dynamic lists are more reliable now. The listed cases of dynamic list misuse are no longer supported.
Charts.	Series data (marker) in a chart legend depends on the appearance of the series in the chart (line color, line style, and marker). This change is not implemented in 8.3.9 compatibility mode.	Series data in chart legend was always represented by a square marker of color matching color of the series in the chart.	Chart readability is now improved (best results for charts printed in black and white).
Data composition system.	Templates of resources created at intersection with matching predefined templates of grouping titles are initially blank. This change is not implemented in 8.3.9 compatibility mode.	Resources were displayed in templates of resources created at intersection with matching predefined templates of grouping titles.	Eliminated unexpected system behavior.
Cryptography support.	If a serial number of a certificate starts with a set high bit, a leading zero byte is appended to the serial number. This change is not implemented in 8.3.8 compatibility mode.	A leading zero byte was not appended to serial numbers of certificates.	Defects in encryption management logic are corrected.
Dynamic lists.	Implemented disabling auto filling of available fields in dynamic lists. This option is only available for dynamic lists generated using custom queries. The system behavior is identical to the similar data composition schema option. Implemented dynamic list property AutoFillAvailableFields. This change is not implemented in 8.3.7 compatibility mode.	Auto filling of all available fields was enabled for all dynamic list queries.	Availability of the list fields can now be changed by the extension of the query language for data composition schema.
Charts. Data composition system.	Implemented management of series display order in chart legends (also available in the data composition system). Implemented property Chart.SeriesOrderInLegend. For ChartType appearance item of DataCompositionAreaTemplateChartAppearance, DataCompositionChartOutputParameterValues, DataCompositionOutputParameterValues, and DataCompositionGroupOutputParameterValues objects, implemented parameter SeriesOrderInLegend. This change is not implemented in 8.3.9 compatibility mode.	Series display order in chart legends could not be changed.	Additional chart display features are now implemented.
Development tools.	The user is asked if they want to save their work whenever they attempt to close the query expression editor dialog box (in the query wizard) by pressing Esc or clicking the Close button (X) after making changes to the expression in the editor.	The user was not asked if they want to save their work whenever they attempted to close the query expression editor dialog box (in the query wizard) by pressing Esc or clicking the Close button (X) after making changes to the expression in the editor. This behavior resulted in loss of user work.	Eliminated unexpected system behavior. Reduced risk of loss of user work when editing query expressions.
Development tools.	Improved diagnostics and system behavior when an invalid or missing manifest is discovered in a picture archive: Archive validation is performed during the import in interactive mode Pictures with invalid or missing manifests are not displayed in Designer Accessing the archive from 1C:Enterprise script generates an error more closely related to the actual problem	The system behavior was different when an invalid or missing manifest was discovered in the picture archive: Archive validation was not performed during the import in interactive mode Attempts to display the picture in Designer or to call it from 1C:Enterprise script could result in abnormal termination or a vaguely described error	Improved diagnostics and system reliability when accessing picture archives with invalid or missing manifests.
Dumping configurations to files/Restoring configurations from files.	During full restoration of a configuration from files, the following rules apply: Configurations that are not covered by support and not connected to configuration repositories can be restored without any restrictions (as before). Configurations that are connected to configuration repositories cannot be restored (the corresponding menu item is disabled). Configurations that are covered by support can be restored provided that: Editing is allowed. All configuration objects can be edited. During partial restoration of a configuration from files, the following rules apply: Configurations can only be restored if all objects to be restored are locked in the configuration repository. Configurations can be restored if all objects to be restored can be edited (for configurations that are covered by support).	Dumping and restoring configurations from files were executed regardless of whether a configuration is covered by support or connected to a configuration repository.	Eliminated issues that occurred when attempting to restore a configuration that is covered by support or connected to the configuration repository from files.
Dynamic lists.	Improved algorithm for searching through search boxes of dynamic lists: Implemented searching for full dates (including both date and time) Implemented searching for numbers with integer and fractional parts by entering integer part only Better readability of search results This change is not implemented in 8.3.9 compatibility mode.	Searching through search boxes of dynamic lists was implemented as follows: Searching for full dates (including both date and time) resulted in a separate search for date and a separate search for the string containing time data Searching for values similar to numbers with integer and fractional parts resulted in a separate search for the integer part and a separate search for the fractional part, with AND conjunction Search results could be displayed inaccurately	Improved searching using search boxes of dynamic lists.
Dynamic lists.	Fields that cannot be used in filters are not available in the advanced search dialog box of dynamic lists (i.e. not displayed in the Search in field list). If the current column of the table associated with the dynamic list displays a field that cannot be used in filters, the command that starts the search by current value is not available.	Fields that could be used in filters were available in the advanced search dialog box of dynamic lists (i.e. displayed in the Search in field list). Availability of the command that starts the search by current value was not affected by whether the field displayed in the current column of dynamic list can be used in filters.	Eliminated unexpected system behavior.
Administration tools.	During the verification and repair of a file infobase, infobase table records are deleted if their keys become non-unique after the records are modified. At that, a diagnostic message is displayed in the message window.	During the verification and repair of a file infobase, keys of infobase table records were not checked for uniqueness after the records were modified. This could result in records with non-unique keys occurring in the infobase. To remedy this, it was necessary to run the infobase verification and repair procedure once more.	Unified behavior of infobase verification and repair procedure between file and client/server infobase modes.
1C:Enterprise script.	Enumerations are present in type selection dialog boxes and type description dialog boxes for all client applications running in managed application mode. This change is not implemented in 8.3.9 compatibility mode.	Enumerations were not present in type selection dialog boxes and type description dialog boxes for thick client and thin client applications running in managed application mode. However, enumerations were present in these dialog boxes for the web client.	Eliminated unexpected system behavior.
Spreadsheet documents.	When exporting spreadsheet documents to Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) format, the name of XML component of shared strings starts with a lowercase letter: sharedStrings.xml. This change is not implemented in 8.3.9 compatibility mode.	When exporting spreadsheet documents to Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) format, the name of XML component of shared strings started with an uppercase letter: SharedStrings.xml.	The platform behavior now conforms to OpenXML standard. Improved compatibility with case-sensitive systems parsing OpenXML files.
Managed forms. Dynamic lists.	Implemented the Main attribute flag for managed form attribute of DataCompositionSettingsComposer type. In this case, Managed form extension for settings composer serves as form extension. The User-defined settings group form property and OnUpdateUserSettingSetAtServer event handler are now available for the form.	Managed form property Main attribute was only set for automatically generated forms of dynamic list settings. Developers were not allowed to create these forms.	Developers can now create all-purpose data composition settings editing forms.
Development tools.	When comparing and merging modules (without using third-party tools), placement of methods in areas defined by preprocessor instructions (#Region, #If) is taken into account. Areas defined by preprocessor instructions are isolated as separate entities (together with procedures and functions). For these areas, implemented specifying the merging parameters.	This feature was not provided. The preprocessor instructions were processed as comments linked to the procedures they preceded. Module merging could result in corrupted structure of blocks defined by preprocessor instructions.	Module merging performed by native Designer tools is now more reliable and user-friendly.
Managed forms.	The navigation panel of the item form of an hierarchical catalog or chart of characteristic types contains: Commands used to access subordinate catalogs with item hierarchy or item and folder hierarchy (no changes since the earlier versions) Commands used to access information registers whose leading dimension type matches the type of catalog or chart of characteristic types, and whose property Select folders and items for this dimension is set to Items or Folders and items The navigation panel of the group form of an hierarchical catalog or chart of characteristic types contains: Commands used to access subordinate catalogs with folder hierarchy or item and folder hierarchy Commands used to access information registers whose leading dimension type matches the type of catalog or chart of characteristic types, and whose property Select folders and items for this dimension is set to Items or Folders and items This change is not implemented in 8.3.9 compatibility mode.	All commands used to access subordinate catalogs were located in the navigation panel of the item form of an hierarchical catalog or chart of characteristic types. The navigation panels of group forms of these configuration objects did not contain any of the commands used to access subordinate catalogs. All commands used to access information registers were located in the navigation panel of the item form of an hierarchical catalog or chart of characteristic types. The navigation panels of group forms of these configuration objects did not contain any of the commands used to access information registers.	Eliminated unexpected system behavior.
Development tools. Dumping configurations to files/Restoring configurations from files.	In the "dump configuration to files" feature, changed the dump format of information about dynamic lists located in managed forms. It is recommended that you dump all forms containing dynamic lists once more.	In the "dump configuration to files" feature, the dump format of information about dynamic lists located in managed forms was different.	In the "dump configuration to files" feature, the format of resulting XML files is improved.
Database configuration update.	Messages about creation and deletion of options tables for charts of characteristic types, charts of accounts, charts of calculation types, and catalogs are not displayed when updating database configuration.	Messages about creation and deletion of options tables for charts of characteristic types, charts of accounts, charts of calculation types, and catalogs were displayed when updating database configuration.	Messages that contain no useful information for the user are no longer displayed when updating database configuration.
Charts.	Expanded set of palettes that can be used to customize chart colors. The palettes can contain either fixed color sets or color sets that vary depending on the quantity of series. Implemented creation of custom color sets for charts. For ChartColorPalette system enumeration, implemented values Auto, Custom, Gradient, Blue, Orange, Green, Yellow, Gray, Warm, Cold, Bright, Soft, and Pastel. For Chart object, implemented the following: Properties GradientPaletteStartColor, GradientPaletteEndColor, and GradientPaletteMaxColors Methods GetPalette() and SetPalette() For ChartType appearance item of data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ColorPalette, GradientPaletteStartColor, GradientPaletteEndColor, and GradientPaletteMaxColors	Only two palettes (with 8 and 32 colors respectively) were available for picking chart colors. Creation of custom chart color palettes was not supported.	Additional chart appearance features are now implemented.
Data composition system.	When data composition output processor outputs merged cells to a spreadsheet document, width of the columns containing merged cells is adjusted in order to minimize height of the content of these cells. This change is not implemented in 8.3.9 compatibility mode.	When data composition processor outputted merged cells to a spreadsheet document, width of the columns containing merged cells was not adjusted in some cases. This could result in inappropriately narrow columns.	Calculation of width of spreadsheet document columns containing merged cells performed by data composition output processor is improved in some cases.
Accounting registers.	The PointInTimeWithPeriodAdjustment type is available in the thin and web clients.	The PointInTimeWithPeriodAdjustment type was available only in the thick client and only on the server.	Eliminated unexpected system behavior.
Spreadsheet documents.	For spreadsheet documents, the option to paste data that has XLS (Microsoft Excel 97-2003) or ODS (OpenDocument Spreadsheet) format is added to the Paste special operation.	For spreadsheet documents, the option to paste data that has XLS (Microsoft Excel 97-2003) or ODS (OpenDocument Spreadsheet) format was not available.	The Paste special operation now supports selection from all spreadsheet formats that support pasting.

Table of contents

Changes that require modification of configuration and administrative settings

Functionality	After	Before	Result of changes
Managed forms.	When collapsing a node of a value tree with subordinate items that is displayed in a managed form, event BeforeCollapse is generated for each node being collapsed throughout the hierarchy. This change is not implemented in 8.3.9 compatibility mode.	When collapsing a node of a value tree with subordinate items that is displayed in a managed form, event BeforeCollapse was only generated for top-level tree items.	Eliminated unexpected system behavior. Value tree items to be collapsed are now defined more precisely in interactive mode.
Access rights.	Calling the AccessRight() method generates an exception if the access right being checked cannot be applied to a metadata object. This change is not implemented in 8.3.9 compatibility mode.	Calling the AccessRight() method always returned True if the access right being checked could not be applied to a metadata object.	Eliminated unexpected system behavior.
Data composition system.	Data composition schema parameters whose types contain only types disabled by functional options are added to the list of available data composition schema parameters with disabled visibility. Therefore, these parameters cannot be edited by users but can still be accessed from 1C:Enterprise script. Moreover, these parameters are not added to the list of available parameter fields. When a report option is loaded, the usage flag is cleared for the data parameters disabled by functional options. The DataCompositionSettingsComposer.Refresh() method disables the Use property of data parameters disabled by functional options. This change is not implemented in 8.3.9 compatibility mode.	Functional options did not affect the visibility of data composition parameters. When a report option was loaded, the usage flag was not cleared for the data parameters disabled by functional options. The DataCompositionSettingsComposer.Refresh() method did not modify the Use property of data parameters disabled by functional options.	Management of report parameters of types disabled by functional options is now more user-friendly.
HTML support.	For HTMLDocumentShell object, implemented property TemplateLanguageCode. If this property is set, the following methods of this object return a result for the specified language: GetCOMObject(), GetHTMLDocument(), and GetText().	Selection of language to be used in return values of HTMLDocumentShell object methods was not available for HTML templates.	Now HTML templates can be used for languages that do not match the language of the current session.
System requirements.	Changed presentation of Microsoft Windows version, starting from Windows Vista, in SystemInfo.OSVersion property. The property text contains the user presentation of the operating system name, as well as technical information (version, build number, and so on). This change is not implemented in 8.3.9 compatibility mode.	Presentation of Microsoft Windows version, starting from Windows Vista, in SystemInfo.OSVersion property did not contain the user presentation of operating system name.	Information about Microsoft Windows version stored in SystemInfo.OSVersion property (for systems running on Microsoft Windows) now offers better readability.
Web services and HTTP services. Internet-enabled functionality.	When method HTTPConnection.CallHTTPMethod() is called, its parameter HTTPMethod must comply with RFC 7230 Read more.. If this requirement is not met, an exception is raised. This change is not implemented in 8.3.9 compatibility mode.	When method HTTPConnection.CallHTTPMethod() was called, its parameter HTTPMethod could take up any value.	The behavior of 1C:Enterprise better complies with RFC standards now.
DBMS operations.	When a 1C:Enterprise application runs in client/server mode using a Microsoft SQL Server database, a query containing expression CAST(... AS STRING(...)) adds trailing space characters to the operation result until it reaches the required length. This change is not implemented in 8.3.9 compatibility mode.	When a 1C:Enterprise application ran in client/server mode using a Microsoft SQL Server database, a query containing expression CAST(... AS STRING(...)) did not add trailing space characters to the operation result until it reached the required length.	1C:Enterprise behavior is now uniform across all supported databases.
XML and XDTO support.	Serialization of a ValueList object using the XDTOFactory.WriteXML() method creates an XML document based on the schema used for serialization of this object with XDTOSerializer.WriteXML() method. Due to this change: Value lists serialized in version 8.3.10 cannot be read in version 8.3.6 or earlier but can be read in version 8.3.7 or later by using XDTOFactory Value lists serialized in version 8.3.10 can be read in version 8.3.6 or earlier by using XDTOSerializer Value lists serialized in versions 8.3.7 to 8.3.9 can be read in any version.	Serialization of a ValueList object using the XDTOFactory.WriteXML() method created an XML document that did not match the schema used for serialization of this object with XDTOSerializer.WriteXML() method.	Eliminated unexpected system behavior.
Managed forms.	If a hyperlink is displayed in a managed form table cell and Read only mode is set for this table cell, double-clicking this cell results in raising the Selection table event once. This change is not implemented in 8.3.9 compatibility mode.	If a hyperlink was displayed in a managed form table cell and Read only mode was set for this table cell, double-clicking this cell resulted in raising two Selection table events.	Eliminated unexpected system behavior.
Development tools.	For event subscriptions, implemented the match check for events and source types. The check is performed prior to saving the configuration. If the event does not match the source type, an error is generated and the configuration is not saved. This change is not implemented in 8.3.9 compatibility mode	For event subscriptions, the match check for events and source types was not performed.	Eliminated unexpected system behavior.
Queries.	An error is generated during query analysis if the expression following the temporary table name does not contain the field name. This change is not implemented in 8.3.9 compatibility mode.	During query analysis, if the expression following the temporary table name did not contain the field name, the name of the first field of the temporary table was used instead.	Eliminated unexpected system behavior.
Spreadsheet documents.	When displaying spreadsheet documents in Taxi interface, the Auto text color is selected as follows: For displaying on monitors: style-based color for text editing For printing: black This change is not implemented in 8.3.9 compatibility mode.	When displaying spreadsheet documents in Taxi interface, black was always used as the Auto text color.	Eliminated unexpected system behavior.
Managed forms.	For attributes of String or Number type displayed in a managed form input field with list selection mode enabled: Restrictions to the length of string that can be entered are removed The input field displaying this data is automatically stretched horizontally This change is not implemented in 8.3.9 compatibility mode.	When editing values of Number type in a managed form input field with list selection mode enabled, number qualifiers configured for the attribute were affecting format of the text being edited.	Improved usability of text input fields.
Spreadsheet documents.	When processing a template in a spreadsheet document cell, content located between the final section [] and an escaped character [ is not removed from the result. This change is not implemented in 8.3.9 compatibility mode.	When processing a template in a spreadsheet document cell, content located between the final section [] and an escaped character [ was removed from the result.	Eliminated unexpected system behavior.
Internet-enabled functionality.	When 1C:Enterprise is running on Microsoft Windows, web server certificate checks are performed for all chains of trusted certificates registered in the Windows trusted certificate store.	When 1C:Enterprise was running on Microsoft Windows, web server certificate checks could fail if a trusted parent certificate of the certificate being checked was not registered in the trusted certificate store.	Eliminated situations that could occur on Microsoft Windows when 1C:Enterprise failed to check a web server certificate via HTTPS/FTPS if the server certificate publisher was not included in the list of trusted root certificates.
Full-text search.	If a full-text search query generates multiple intermediate results and the search result contains under 1 mln records, the user gets the search result. This change is not implemented in 8.3.9 compatibility mode. To enable this feature, set the configuration compatibility mode to None and update the full-text search index. The later a data item was modified, the higher in the full-text search results it is displayed (within a single configuration object, such as a document type).	If a full-text search query generated multiple intermediate results, the error stating that there are too many search results was displayed to the user.	Full-text search now returns results when searching for several words that commonly occur separately but rarely occur together.
Client application installation.	Searching the distribution kit directories for new 1C:Enterprise versions when opening the infobase list window is now faster. The search is performed for the names of distribution kit directories. Distribution kit type and bitness are determined based on the name of .msi file: 1CEnterprise 8.msi — 32-bit version, full distribution kit 1CEnterprise 8 Thin client.msi — 32-bit version, thin client 1CEnterprise 8 (x86-64).msi — 64-bit version, full distribution kit 1CEnterprise 8 Thin client (x86-64).msi — 64-bit version, thin client	Searching the distribution kit directories for new 1C:Enterprise versions was insufficiently fast because it relied on data stored in properties of .msi files.	The infobase list dialog box now opens faster if the Install new application versions automatically check box is selected in the dialog box settings.
Managed forms.	When attempting to create a managed form group with an invalid value of Type property using 1C:Enterprise script, an exception is raised. This change is not implemented in 8.3.9 compatibility mode.	When attempting to create a managed form group with an invalid value of Type property using 1C:Enterprise script, the system behavior was not defined and could result in abnormal termination.	Eliminated unexpected system behavior.
Data composition system.	Implemented setting expressions simultaneously both for detailed records and totals records of user-defined fields of the data composition system. Implemented the same for user-defined field presentations in detailed records and totals records of the data composition system. For DataCompositionUserFieldExpression object, implemented methods SetExpressions() and SetExpressionsPresentation(). Methods SetDetailRecordExpression(), SetTotalRecordExpression(), SetDetailRecordExpressionPresentation(), and SetTotalRecordExpressionPresentation() are now deprecated and supported for compatibility purposes only. It is recommended that you do not use any of these.	Expressions of user-defined fields of the data composition system for detailed records and totals records were set by different methods. Presentations of user-defined fields of the data composition system for detailed records and totals records were also set by different methods.	Eliminated unexpected system behavior. User-defined fields of the data composition system that contain deleted or renamed query fields in both expressions are now editable.
Data composition system.	When automatically filling available fields of query data set for virtual tables of information registers, dimension fields become available for filtering based on virtual table parameters. This change is not implemented in 8.3.9 compatibility mode.	When automatically filling available fields of query data set for virtual tables of information registers, dimension fields did not become available for filtering based on virtual table parameters.	Getting data from information registers through the data composition system is now more efficient when virtual tables of information registers are used.
Queries.	When adding filter expressions to a query by using QuerySchemaExpression object constructor, the filter expressions are added without conversion. This change is not implemented in 8.3.9 compatibility mode.	When adding filter expressions to a query by using QuerySchemaExpression object constructor, the filter expressions were corrupted due to conversion.	Eliminated unexpected system behavior.
Configuration repositories.	New configuration repositories are created in version 8.3.8 format, with page size 8192 bytes. You can use the cnvdbfl utility to change configuration repository format from version 8.2.14 to version 8.3.8 and vice versa.	The configuration repository database was created in version 8.2.14 format.	You can set the configuration repository format to version 8.3.8. Repositories that have this format can store larger reporitory history.
Accounting registers.	If an accounting register resource value is associated with the accounting flag for a chart of accounts, values of this resource in Balance, Turnovers, BalanceAndTurnovers, and DrCrTurnovers virtual tables depend on the status of this accounting flag for each account. If the accounting flag is set, the resource value has Number type. If the accounting flag is cleared, the resource has value is NULL. This change is not implemented in 8.3.9 compatibility mode.	Virtual tables of accounting registers (Balance, Turnovers, BalanceAndTurnovers, and DrCrTurnovers) could return non-NULL values of accounting register resources associated with accounting flags for accounts where these accounting flags were disabled.	Eliminated unexpected system behavior.
Web client. Client application. Interface. Managed forms. Applied objects.	Ended support of modal windows in the web client, regardless of web browser used. Any modal method call performed by an application now raises an exception. For the thin client and web client, ended support of document posting performed in the mode interactively specified by the user. Accessing a document with such posting mode now raises an exception. The system enumeration value PostingModeUse.Ask is no longer supported by the thin client and web client. The window opening option (Window parameter) is now ignored when used in methods OpenForm() and GetForm(), and when used as a structure property value CommandExecuteParameters.Window (with type defined by system enumeration WindowOpenVariant). In the thin client, the Window parameter is ignored when the compatibility mode is disabled. The system enumeration WindowOpenVariant is excluded from the Syntax Assistant. In the thin client and web client, forms can no longer be opened in separate windows when Forms in tabs interface mode is enabled. In the web client, ended support of interface mode Forms in separate windows. In the thin client, interface mode Forms in separate windows cannot be enabled through the client application parameters dialog box. In the web client, ended support of the web client command-line parameter isdi. The check whether popup windows are blocked is not performed when starting the web client.	Windows that locked other windows were supported in the web client. Document posting mode could be specified by the user interactively, as a part of the posting procedure. In the thin client and web client, forms could be opened in separate windows when interface mode Forms in tabs was enabled. In the web client, interface mode Forms in separate windows was supported.	Ended support of interface mode not supported by the current web browsers.
Interface. Data display.	Redesigned user notifications available in Taxi interface. The new notification functionality includes: Displaying multiple notifications simultaneously Displaying notifications while the main application window is minimized Refreshing the notification window until the user closes it Reacting to the user touching the notification window Implemented notification management through the notification center. Dragging the notification window is not supported. For global context method ShowUserNotification(), implemented parameters UserNotificationStatus and UniqueKey. The parameter of URL method is renamed to ActionOnClick. For the specifics of notification behavior depending on the operating system and the client application, refer to the documentation.	These features were not provided. Capabilities of global context method ShowUserNotification() were limited.	Notification management in Taxi interface is now more user-friendly.
Charts. Spreadsheet documents.	Implemented the availability to open details for Gannt charts displayed in spreadsheet documents. The procedure is identical to opening details for Gannt charts displayed in managed forms. For spreadsheet document event handlers DetailProcessing and AdditionalDetailProcessing, implemented parameter AdditionalParameters. This parameter stores the date that is used as an input parameter for retrieving the details. This change is not implemented in 8.3.9 compatibility mode. The context menu of Gantt charts in spreadsheet documents now opens on releasing the right mouse button. This change is not implemented in 8.3.9 compatibility mode.	Any attempt to access details for a Gantt chart in a spreadsheet document resulted in opening a window containing a noninteractive list of details. Spreadsheet document event handlers DetailProcessing and AdditionalDetailProcessing had only two parameters (and did not have the AdditionalParameters parameter). The context menu of Gantt charts embedded in spreadsheet documents opened on clicking the right mouse button.	Eliminated unexpected system behavior. The behavior of Gantt chart details in spreadsheet document is now standardized.
Charts. Web client.	If chart properties Adjust series and Adjust points are set to False, series colors or point colors now use the custom color palette in the thin client. This change is not implemented in the web client . This change is not implemented in 8.3.9 compatibility mode.	If chart properties Adjust series and Adjust points were set to False, series colors or point colors used the default color palette in the thin client, and the custom color palette in the web client.	Eliminated inconsistencies in chart appearance between the web client and thin client.
Charts.	During chart deserialization, if Adjust series or Adjust points property is set to False, series colors or point colors use the custom color palette (they are set once the palette is loaded). This change is not implemented in 8.3.9 compatibility mode.	During chart deserialization, if Adjust series or Adjust points property is set to False, series colors or point colors used the default color palette.	Eliminated unexpected system behavior.
Charts.	During interactive chart editing, if Adjust series or Adjust points property is set to False, the following operations are performed: Parameters controlling the appearance of series or points are set to default values The chart is redrawn. This change is not implemented in 8.3.9 compatibility mode.	During interactive chart editing, parameters controlling appearance of series or points were not set to default values if Adjust series or Adjust points property was set to False.	Eliminated unexpected system behavior.
Charts.	If Adjust series or Adjust points chart property is set to False, any attempt to change series properties or point properties for this chart by using 1C:Enterprise script raises an exception. This change is not implemented in 8.3.9 compatibility mode.	Attempts to change a series or point property for a chart by using 1C:Enterprise script did not raise an exception if Adjust series or Adjust points chart property was set to False. The property was set for series or point instead.	Invalid chart use is not allowed now
Common objects.	In a value table generated using the Unload() method of a tabular section of any object, names of predefined columns are generated in 1C:Enterprise script language variant specified in the Script variant configuration property. This change is not implemented in 8.3.9 compatibility mode.	In a value table generated using the Unload() method of a tabular section of any object, predefined column names could be accessed in the following 1C:Enterprise script language variants: If the resulting value table was not transferred between the client and the server, both English and Russian. If the resulting value table was transferred between the client and the server, English only.	Eliminated unexpected system behavior.

Table of contents

Renamed objects

Object	The old name	The new name
Method StrStartWith(). The previous name is now deprecated and supported for compatibility purposes only.	StrStartWith().	StrStartsWith().
XSL stylesheet loading methods of XSLTransform object. The previous names are now deprecated and supported for compatibility purposes only.	LoadFromString() LoadFromNode() LoadFromFile()	LoadXSLStylesheetFromString() LoadXSLStylesheetFromNode() LoadXSLStylesheetFromFile()
Names of debug items used in file infobases.	For Web services: Server (file-based variant) For HTTP services: Server (file-based variant)	For Web services: Web service For HTTP services: HTTP service
Titles in the sections panel settings dialog box.	Available sections Selected commands	Available sections: (added trailing character «:») Selected sections
Copyright holder information.	(с) '1C' 1996-2016.	(c) 1C LLC 1996-2016.
Changed presentation of spreadsheet document menu commands used for named area display management.	Show Named Rows/Columns Show Named Cells	Show row and column names Show cell names
Presentations of configuration storage compatibility mode values.	Version 8.3.2 Version 8.3.3	Version 8.3.2 or eralier Versions 8.3.3 - 8.3.5

Table of contents

Mobile platform

Functionality	After	Before	Result of changes
Mobile device-specific features.	Implemented the following location features: Selecting a location provider either from the global list of providers, or from the list of providers available now Checking if location service is enabled Geofence management Implemented the Geofence object. Implemented LocationRelativeToGeofence system enumeration. Implemented LocationProviderInformation.Available property. Implemented AvailableOnly parameter for the following methods of LocationTools object: GetProviders(), GetProvider(), GetMostAccurateProvider(), and GetMostPowerSavingProvider(). For LocationTools object , implemented methods: LocationDataUseEnabled(), AttachProvidersAvailabilityChangeHandler(), DetachProvidersAvailabilityChangeHandler(), EnableGeofencesMonitoring(), GetMonitoredGeofences(), GetMonitoredGeofence(), DisableGeofencesMonitoring(), DisableAllGeofencesMonitoring(), and AttachMonitoredGeofencesBorderCrossingDetectionHandler().	These features were not provided.	Location management capabilities are now expanded. For example, predefined actions can be performed when a mobile device reaches a specific location.
Binary data.	Implemented binary data management capabilities for the mobile platform.	This feature was not provided. Binary data management capabilities were only available for the PC platform.	Binary data management capabilities are now implemented for the mobile platform.
Internet-enabled functionality.	Implemented check whether a mobile device is in roaming mode. The Internet connection change handler is called when the roaming mode status is changed. Implemented method InternetConnectionInformation.GetRoamingUsage().	Check whether a mobile device is in roaming mode was not implemented.	A variety of actions can be performed when roaming mode is enabled on a mobile device. For example, access to mobile Internet can be restricted or prohibited due to high Internet charges in roaming.
Internet-enabled functionality.	For mobile platforms running on Windows, implemented secured connection management capabilities.	Secured connection management capabilities were not available for mobile platforms running on Windows.	Mobile platforms running on Windows can now access resources that require secured connection.
Cryptography support.	Implemented encryption operations for the mobile platform. The mobile platform behavior is identical to that of the thin client. Details of the encryption operations are described in the documentation. Implemented CryptoManager.ShowCertificateList() method. Implemented CryptoKeysContainer object. Changed behavior of the following methods of CryptoCertificateStore object on the mobile platform: Add(), Delete(), BeginAdding(), and BeginDeleting().	Encryption operations were not implemented for the mobile platform.	On the mobile platform, you can implement a check whether a document stored locally was modified. Sensitive data and documents can now be securely sent through open channels thanks to encryption capabilities.
Mobile device-specific features.	For the mobile platform, implemented a check whether contacts and calendars can be added or edited. For ContactManager object, implemented methods ContactEditingSupported() and ContactsAppendingSupported(). For CalendarsManager object, implemented methods CalendarEditingSupported() and CalendarsAddingSupported(). The CalendarManager.CalendarEditingSupported property is now deprecated and supported for compatibility purposes only. For 1C:Enterprise applications running on Windows, the CalendarManager.EventEditingSupported() method always returns False.	The check whether contacts can be added or edited was not implemented. The check whether calendars can be added or edited was implemented in a different way.	Unified contacts and calendar management as related to adding and editing objects.
Mobile device-specific features.	Implemented new configuration permission: Ads. This permission is only used by the mobile application builder when selecting a mobile platform version for iOS to be used in the builds. If the Ads permission is used in the configuration export file, The app uses ads check box is unavailable in the mobile configuration form of the mobile application builder.	The permission specifying that ads are allowed for a mobile application was not implemented in the configuration. Instead, The app uses ads check box in the mobile application builder was used for this purpose.	Now the mobile application builder can be forced to use an advertisement-enabled mobile platform version for iOS in the builds.
File operations.	For the mobile platform, implemented getting thumbnails for pictures and video files stored in the corresponding libraries of the mobile device. This feature requires the file path to start with content: schema. For File object , implemented methods GetMobileDeviceLibraryFileThumbnailPicture() and BeginGetMobileDeviceLibraryFileThumbnailPicture().	This feature was not provided. It was possible to fully load a picture or video file into memory when a thumbnail could be used instead	Optimized mobile device memory use when loading pictures or video files from the corresponding libraries of the mobile device. Reduced risk of insufficient memory error for mobile applications that load a large number of pictures or video files from the corresponding libraries of the mobile device.
Managed locks.	Implemented data lock management for mobile platforms. Implemented global context methods LockDataForEdit(), UnlockDataForEdit(), SetLockWaitTime(), and GetLockWaitTime(). Implemented methods IsLocked(), Lock(), and Unlock() for objects CatalogObject, DocumentObject, and ExchangePlanObject. Implemented method AccumulationRegisterRecordSet.LockForUpdate(). Implemented method ManagedForm.LockFormDataForEdit(). Implemented DataLock and DataLockItem objects. For Document, Catalog, and ExchangePlan configuration objects, implemented the DataLockFields property. For Configuration, Document, Catalog, ExchangePlan, Constant, Sequence, AccumulationRegister, and InformationRegister configuration objects, implemented DataLockControlMode property.	Managed lock support was not provided on the mobile platform.	Object lock management during background job execution on the mobile platform is now available.
File operations.	Implemented getting a file mask that describes all files, as well as getting a file path separator character, regardless of the mobile operating system where 1C:Enterprise is running. Implemented methods GetAllFilesMask(), GetClientAllFilesMask(), GetServerAllFilesMask(), GetPathSeparator(), GetClientPathSeparator(), and GetServerPathSeparator(). Implemented method BeginGetMobileDeviceLibraryDir().	Getting a file mask that describes all files and getting a file path separator character regardless of the mobile operating system used was not supported.	File operations in mobile applications are nearly operating system-agnostic now.
System requirements.	Implemented Android 7.0 support. Implemented multiwindow mode for Android 7.0. For Android versions 6.0 or earlier: Introduced a new API for operations with the mobile device camera Implemented dynamic resolutions	Multiwindow mode was not supported for Android 7.0. Dynamic resolutions were not supported for Android versions 6.0 or earlier. Dynamic resolution management was not supported for Android versions 6.0 or earlier.	Improved support of Android versions 6.0 and earlier.
Mobile device-specific features.	Implemented barcode scanning capability for mobile devices running Windows 10. Barcode scanning is not supported for mobile devices running Windows 8.1 or earlier. For devices running Windows 10, implemented availability of MultimediaTools.ShowBarcodeScanning() method, while MultimediaTools.BarcodeScanningSupported() method returns a value specifying whether barcode scanning functionality is available. For successful barcode scanning, continuous auto focus mode must be supported for the primary device camera.	Barcode scanning was not supported for mobile devices running Windows.	Expanded mobile platform capabilities for devices running Windows 10.
Managed forms.	For the mobile platform, implemented form field extension for the calendar field. The form field extension for the calendar field does not support dragging.	This feature was not provided.	Expanded Data type data management capabilities for mobile platform forms.

Table of contents

Transition from the previous version to the version 8.3.10

Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.10.
Some features that are added in version 8.3.10 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
If a full-text search query generates multiple intermediate results and the search result contains under 1 mln records, the user gets the search result.
To enable this feature, set the configuration compatibility mode to None and update the full-text search index.
It is recommended that you convert large configuration repositories (repositories that store 30 000 - 40 000 versions, such as 1C:ERP Enterprise Resource Planning 2) to version 8.3.8 format using the cnvdbfl utility.

Functionality	After	Before	Result of changes
Server clusters.	Improved server cluster scalability for the following cases: Servers run on processors with a large number of cores. A large number of users is served. Internal data exchange between the client and the server is compressed. Reduced amount of RAM used by 1C:Enterprise server to run applications that utilize batch queries.	Poor server cluster scalability was observed in the following cases: Servers run on processors with a large number of cores. A large number of users is served. Internal data exchange between the client and the server is compressed. 1C:Enterprise server used a significant amount of RAM to run applications that utilized batch queries.	Improved 1C:Enterprise server cluster scalability.
Встроенный язык.	Faster 1C:Enterprise script execution by 1C:Enterprise server.	The performance of 1C:Enterprise script execution by 1C:Enterprise server was insufficient.	Optimized 1C:Enterprise script execution by 1C:Enterprise server.
Data composition system.	Faster initialization of data composition settings composer by source of available data composition settings when using schemas with a large number of calculated fields.	The performance of initialization of data composition settings composer by source of available data composition settings when using schemas with a large number of calculated fields was insufficient.	Improved performance of data composition system initialization in several scenarios.
Server clusters.	Reduced amount of RAM used by 1C:Enterprise server to run applications that utilize batch queries.	Significant amount of RAM was used by 1C:Enterprise server to run applications that utilize batch queries.	Optimized amount of RAM used by 1C:Enterprise server to run batch queries.
Configuration repositories.	Optimized updating of local cache of configuration storage when putting objects into storage and getting objects from storage.	The performance of putting objects into configuration storage and getting objects from storage was insufficient.	Putting objects into configuration storage and getting objects from storage is now faster.
Development tools.	Implemented retention of module search index between Designer sessions. Reduced time required for initial generation of module search index. Significantly reduced time required for module search index generation during all subsequent Designer sessions. Running Designer with command-line option /ClearCache clears the module search index.	Module search index was not retained between Designer sessions. Index generation required significant time.	It is now easier to work with large configurations.
1C:Enterprise script.	When searching for strings in a value table using the FindRows() method, the index is only analyzed for column content matches between the search parameters and the index. The relative order of columns in the search parameters or in the index is ignored during the search.	When searching for strings in a value table using the FindRows() method, the index was only used if the relative order of columns in the search parameters matched the index column order.	Using the index to search value tables by multiple columns is now faster.
Full-text search.	Optimized full-text search index generation and update.	The performance of initial generation and updates of full-text search index was insufficient.	Updating the full-text search index is now faster.
DBMS operations. Queries.	Improved processing speed of queries containing keyword DISTINCT that get a large number of records (in file infobases).	Processing speed of queries containing keyword DISTINCT that get a large number of records (in file infobases) was insufficient.	Getting large lists of unique records from file infobases is now faster.
DBMS operations. Queries.	Faster deletion of large record sets from file infobases. Faster recalculation of totals for tables with a large number of records in file infobases.	The following operations in file infobases were insufficiently fast: Deleting large record sets Recalculating totals for tables with a large number of records	File infobases now work faster in some scenarios.
Dynamic lists.	Improved performance when getting data displayed as dynamic list with conditional formatting.	The performance of getting data displayed as dynamic list with conditional formatting was insufficientl.	The performance of dynamic lists with conditional formatting is now improved.
Dynamic lists.	Faster opening of forms containing dynamic lists with complex queries.	The performance of opening forms containing dynamic lists with complex queries was insufficient.	Forms containing dynamic lists with complex queries now open faster.
Dynamic lists.	For dynamic lists, implemented the option to enable or disable getting presentations for values of reference types that are not displayed in the form or are associated with invisible form items. Presentations of key field values for dynamic lists in selection mode are obtained regardless. Implemented dynamic list property GetInvisibleFieldPresentations. This change is not implemented in 8.3.7 compatibility mode.	In dynamic lists, presentations were obtained for all reference type values to be sent to client side.	Dynamic lists can now be displayed faster in some cases.
Data composition system.	Optimized RAM usage when composing data composition templates with large queries in data composition schema.	RAM usage when composing data composition templates with large queries in data composition schema was sub-optimal.	Composing data composition templates with large queries in data composition schema now requires less RAM.
Infobase operations.	Slightly improved thin client startup time in file infobases when working with large configurations.	Startup time of the thin client in file infobases when working with large configurations was insufficient.	Startup time of the thin client in file infobases when working with large configurations is now improved.
Configuration repositories.	Optimized object lock and release operations in configuration repositories. Changed internal format of locked object data storage for infobases connected to repositories. The data storage format is changed after the data storage optimization operation is completed using the Local repository data usage settings dialog box. This optimization is only available if the configuration was bound to a configuration repository in an earlier platform version. To use the optimized infobase in an earlier platform version, rebind the infobase to the configuration repository in an earlier platform version.	The performance of object lock and release operations in configuration repositories was insufficient.	Working with configuration repositories that store large configurations is now faster.
Client application.	Improved startup time of client applications after dynamic update.	Client applications required longer time to start after dynamic update.	Improved startup time of client applications after dynamic update.

1C:Enterprise Developer's Community