1C:Enterprise 8

Functionality	After	Before	Result of changes
Configuration properties.	For configuration property Compatibility mode, new value Version 8.3.10 is now implemented.	Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.9 was implemented.	Configurations developed using 1C:Enterprise platform version 8.3.10 or earlier can run on version 8.3.11 without any changes to configuration or to data structures. This allows for transition to version 8.3.11 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.10 after the transition to version 8.3.11, even if you disabled the compatibility mode (if you did, enable it again).
Configuration comparison and merging.	Merging composite types and the contents of exchange plans, subsystems, and functional options is implemented. Viewing the differences in these objects is available both in interactive mode (in a dialog box) and in a configuration comparison report. Automatic merging of composite types and the contents of exchange plans, subsystems, and functional options is implemented, with the option to specify the configuration that has priority. The format of the file that stores configuration comparison and merging settings is changed.	Merging composite types and the contents of exchange plans, subsystems, and functional options was not available. Available options included taking the entire object from the configuration being loaded or keeping the existing objects without changing them.	Simplified configuration comparison and merging.
Data history.	The history of database object changes is implemented. The Data history property is implemented for the following configuration objects: catalogs, documents, business processes, tasks, and information registers. The option to keep the history of attributes of these objects (including standard attributes and tabular sections), common attributes (except for data separators), and information register resources is implemented. The options to view and edit data change history, add comments to data history records, and revert to a specific data version are implemented. Native objects of configuration extensions do not support data history. The following access rights are implemented: ReadDataHistory, ReadDataHistoryOfMissingData, UpdateDataHistory, UpdateDataHistoryOfMissingData, UpdateSettingsDataHistory, UpdateDataHistoryVersionComment, ViewDataHistory, EditDataHistoryVersionComment, and SwitchToDataHistoryVersion. The global context property DataHistory is implemented. It provides access to the data history from 1C:Enterprise script. The user interface that provides access to data history is implemented.	This feature was not provided. Implementation of a change history based on built-in 1C:Enterprise tools was possible.	The data history is now available as a platform-level feature. This simplifies application development and support.
Development tools.	In the managed form editor, the option to preview a form as it would look on a mobile application is implemented. This option is available in configuration compatibility mode Version 8.3.7 or later.	In the managed form editor, the option to preview a form as it would look on a mobile application was not available. The preview always displayed a form as it would look on a PC.	Improved form development tools for configurations that run on mobile devices.
Binary data.	A set of functions that perform bitwise operations on integer numbers is implemented. They treat numbers as unsigned 32-bit numbers. The following global context methods are implemented: CheckBit(), CheckByBitMask(), SetBit(), BitwiseAnd(), BitwiseOr(), BitwiseNot(), BitwiseAndNot(), BitwiseXor(), BitwiseShiftRight(), and BitwiseShiftLeft(). This change is not implemented in 8.3.10 compatibility mode.	1C:Enterprise only provided methods for logical operations with data stored in binary data buffers.	Simplified usage of bitwise operations with numerical operands.
Database configuration update. Server clusters.	New infobase restructuring algorithm is implemented. It features the following major differences from the previous algorithm: It only processes physical database tables that were changed. It performs as many changes as possible without copying tables or replicating data between the copies. If replication between table versions is necessary, it is always performed using DBMS tools. This feature has beta status. The new restructuring algorithm is only used in client/server mode with Microsoft SQL Server or PostgreSQL DBMS. The new restructuring algorithm requires Java 1.8 to be installed on the computer that runs 1C:Enterprise server. For the conf.cfg file, new parameters JavaHome, JavaOpts, and UpdateDBCfg are implemented.	This feature was not provided.	The new algorithm significantly improves the performance of infobase restructuring. This reduces the maintenance downtime during application updates on production servers.
Data display. Dynamic lists.	For the format string parameter of Format() function, the option to include a number format template is implemented. The new NF format string parameter is implemented for this purpose. The template specifies the position of a number in a string. The search in dynamic lists is based on the format specified for list columns. The search results are highlighted even in cells that contain string constants before and/or after the number. This change is not implemented in 8.3.10 compatibility mode.	These features were not provided.	You can display formatted values with measurement units in charts and in other interface items that support format strings.
Development tools.	In batch Designer mode, the configuration check includes the option to check configuration modules for synchronous method calls. For /CheckConfig command-line option, the -CheckUseSynchronousCalls parameter is implemented. If you specify this parameter, you also have to specify the -ExtendedModulesCheck parameter for this command-line option.	The option to check configuration modules for synchronous method calls during a configuration check initiated from batch Designer mode was not available. This option was only available if Designer was running in interactive mode.	Eliminated unexpected system behavior.
Web services and HTTP services. Configuration extensions.	For native configuration extension objects of web service and HTTP service types, support of configurable session reuse is implemented.	For native configuration extension objects of web service and HTTP service types, configurable session reuse was not available.	Unified platform behavior for accessing similar mechanisms from a configuration and from an extension.
Collaboration system.	Sending messages from a 1C:Enterprise server to a client application is implemented. A configured collaboration system operates as transport for message exchange purposes. Client applications can get messages both synchronously and asynchronously, depending on the server call type: a regular call or a background job. For collaboration system manager, the following methods are implemented: CreateUser(), DeleteMessage(), BeginAttachNewMessagesHandler(), BeginDetachNewMessagesHandler(), and a new variant of GetConversation() method. For CollaborationSystemConversation object, Key and Visible properties are implemented. For CollaborationSystemConversationsFilter object, Key and Displayed properties are implemented. The CollaborationSystemMessage object and some of its properties (Author, Date, ID, Recipients, and Text) are now available on the client. For CollaborationSystemMessage object, Data and Conversation properties are implemented. Objects CollaborationSystemConversationID and CollaborationSystemMessageID are are now available on the client. Objects CollaborationSystemUserID and CollaborationSystemUserIDCollection, their properties, and their methods are now available on the client.	This feature was not provided. The CollaborationSystemMessage object and some of its properties (Author, Date, ID, Recipients, and Text) were only available on 1C:Enterprise server. Objects CollaborationSystemConversationID and CollaborationSystemMessageID were only available on 1C:Enterprise server. Objects CollaborationSystemUserID and CollaborationSystemUserIDCollection, their properties, and their methods were only available on 1C:Enterprise server.	You can implement client notifications for events that occur on 1C:Enterprise server.
Collaboration system.	The option to attach a handler that is executed after sending a collaboration system message is implemented. A message can now include hyperlinks; clicking a hyperlink executes the handler or a standard action assigned to the hyperlink . For CollaborationSystemManager object, the following methods are implemented: AttachAfterMessageSendHandler(), DetachAfterMessageSendHandler(), AttachMessageActionHandler(), and DetachMessageActionHandler(). The CollaborationSystemMessage.Actions property is implemented. CollaborationSystemConversation and CollaborationSystemConversationContext objects are now available in client applications.	These features were not provided. CollaborationSystemConversation and CollaborationSystemConversationContext objects were only available on 1C:Enterprise server.	Expanded collaboration system capabilities. You can implement automatic replies to incoming messages.
Queries.	For QuerySchemaQueryBatch, QuerySchemaOperators, QuerySchemaColumns, QuerySchemaIndexExpression, QuerySchemaOrderExpression, and QuerySchemaTotalCalculationFields objects, the MoveTo() method is implemented. It moves a collection element to the specified position.	This feature was not provided.	Expanded development tools for some collections related to query schemas.
Configuration extensions. Applied objects.	In configuration extensions, support of native catalogs, documents, exchange plans, and information registers is implemented. For adopted catalogs and documents, the option to add attributes and tabular setions in extensions is implemented. A native exchange plan can only include native extension objects. A native exchange plan cannot be used in a distributed infobase. The option to add native extension objects to adopted exchange plans is implemented. The full list of limitations is provided in the documentation. Deleting an extension deletes all data that was added to native extension objects from the infobase.	These features were not provided.	Expanded configuration extension capabilities. An extension attached to an infobase can store its data in the infobase.
Information registers.	For InformationRegisterRecordKey object, the option to get the related metadata object is implemented. The method InformationRegisterRecordKey.Metadata() is implemented. This change is not implemented in 8.3.10 compatibility mode.	Getting the related metadata object directly from the InformationRegisterRecordKey object was not available.	Getting metadata related to information register record keys is now similar to getting metadata from other configuration objects.
Charts.	For stock charts, support of the following properties of ValuesAxis object is implemented: MinValueDetectionMethod, MinValue, MaxValueDetectionMethod, and MaxValue. This change is not implemented in 8.3.10 compatibility mode.	For stock charts, values of the following properties of ValuesAxis object did not affect the chart view: MinValueDetectionMethod, MinValue, MaxValueDetectionMethod, and MaxValue.	Improved stock chart display options.
Standard functions. Event log.	In the event log, for Users.Add and Users.Modify events, OpenIDAuthentication and UnsafeOperationProtection properties are implemented (in the Data field of the log record). For Users.Add and Users.Modify events, the log viewer now displays OpenID authentication and Unsafe operation protection properties. This change is not implemented in 8.3.10 compatibility mode.	For events that described adding or modifying a user, the OpenID authentication flag and unsafe operation protection flag were recorded to the event log but were not available for viewing.	Eliminated unexpected system behavior. You can access data that was previously unavailable.
Software licensing.	In the license acquisition wizard, selecting a country from a list is implemented.	In the license acquisition wizard, one could enter any word as a country name.	Eliminated issues that occurred due to entering incorrect country name during software license acquisition.
DBMS operations. System requirements.	Support of Oracle Database version 11.2.0.4 (Linux) is implemented. It is only supported with patch 20954292. Oracle Database version 11.2.0.4 (Windows) is only supported with patches 24591646 and 24591637.	Oracle Database version 11.2.0.4 (Linux) was not supported. Oracle Database version 11.2.0.4 (Windows) was supported without the requirement to install any patches.	Extended list of supported Oracle Database versions.
Technological log.	<WINCERT> technological log event is implemented. It is intended for investigating errors related to certificate validation using Windows API methods. This event can only be generated on Windows.	This feature was not provided.	Simplified investigation of errors related to certificate validation on Windows.
Collaboration system.	Local collaboration system server is now available. The server is provided as a standalone distribution package, it requires separate installation. This feature is currently in beta status.	This feature was not provided. The collaboration system only worked over 1cDialog.com service.	You can install and use a local collaboration system server.
Software licensing. System requirements.	If one of the key computer parameters was changed, a license activated on 1C:Enterpirse 8.2.15 or later is considered valid when verified with ring license command with validate option. Using --validate parameter with activate or prepare-request option returns an error if a run-time error occurs when attempting to retrieve any of the key parameters. The behavior of these options when they are used without this parameter is not changed. The license command requires ring utility version 0.8.	If one of the key computer parameters was changed, a license activated on 1C:Enterpirse 8.2.15 or later was considered invalid when verified with ring license command with validate option. If a run-time error occured when attempting to retrieve any of the key parameters, the license was activated successfully and the corresponding license fields were filled with blank values, making the license impossible to use. The license command required ring utility version 0.6.	Eliminated unexpected system behavior.

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Managed forms.	Improved usability of line selection in managed form tables. You can use Ctrl and Shift keys, as well as mouse buttons, to select table lines. This change is not implemented in 8.3.10 compatibility mode.	The only way to select multiple lines in a managed form table was clicking each line while holding down Ctrl.	Improved usability of line selection in managed form tables.
Web client.	A single application can be accessed from multiple web browser tabs.	An attempt to run a second application instance in a second web browser tab generated an error.	The platform supports running multiple web client sessions in a single web browser.
Client application installation.	Implemented a unified name "access application" for all client application types in messages displayed during client application update over HTTP.	In messages displayed during client application update over HTTP, two terms were alternately used for client application: "data viewer" and "access program".	Unified terminology in messages related to access application update over HTTP.
Managed forms. Data display.	When a managed form table is exported using the Output list command: The view of blank values of Number and Date type in the resulting document exactly matches their view in the form. If the table is exported to a text document, tab characters separate all columns of the resulting document. This change is not implemented in 8.3.10 compatibility mode.	When a managed form table was exported using the Output list command: The view of blank values of Number and Date type in the resulting document might not exactly match their view in the form. If the table was exported to a text document, tab characters were only added after the first column that contained a nonblank value.	Eliminated unexpected system behavior.
Managed forms. Data display.	When a managed form table with multiple lines selected is exported using the Output list command (with the Selected items only check box selected): The lines are exported in their original order. If the table displays a dynamic list in Hierarchical list or Tree mode, all of the selected lines are exported, regardless of their positions in the list hierarchy. The performance of the Output list command (with the Selected items only check box selected) is improved in the following scenario: the table displays a dynamic list, a large number of lines is selected, and the dynamic list query is not efficient. This change is not implemented in 8.3.10 compatibility mode.	When a managed form table with multiple lines selected was exported using the Output list command (with the Selected items only check box selected): The lines were exported in the order they were selected. If the table displayed a dynamic list in Hierarchical list or Tree mode, some of the lines were not exported. The performance of the Output list command (with the Selected items only check box selected) was insufficient in the following scenario: the table displayed a dynamic list, a large number of lines was selected, and the dynamic list query was not efficient.	Improved alrogithm of exporting a managed form table to a spreadsheet or text document.
Collaboration system.	The recipient selection procedure in context conversation messages is modified. If the sender does not want to notify any of the users who can see the message (i.e. users having the right to access the object that provides the context), they must explicitly select No notification. Sending a message to an empty list of recipients is not allowed.	Sending a context message with an empty list of recipients was possible.	Improved notification usability.
Spreadsheet documents.	The commands that perform the following operations are added to the Table section of the main application menu: Align pictures (Alignment section) Resize pictures (Size section) Auto space multiple pictures (Distribute section) Order pictures (Order section)	These commands were not available in managed client applications.	Added support of interactive operations with pictures to managed applications.
Collaboration system.	During video calls in the thin and web clients, 1C:Enterprise performs the diagnostics of Internet connection quality. If the quality is insufficient, 1C:Enterprise displays the diagnostics report over the video feed.	During video calls, if the Internet connection quality was insufficient, 1C:Enterprise did not display any diagnostics data. In some cases the picture might freeze without any explanations.	Diagnostics of Internet connection quality during collaboration system video calls are implemented.
Standard functions.	If an application does not contain any objects that can be involved in totals management, when you attempt open the totals management dialog box in ordinary application mode (Main menu – Operations – Totals management), 1C:Enterprise displays a diagnostics message instead of the dialog box.	If an application did not contain any objects that could be involved in totals management, an attempt open the totals management dialog box in ordinary application mode (Main menu – Operations – Totals management) did not open the dialog box and no diagnostics messages were displayed.	Improved 1C:Enterprise usability.
Managed forms.	The tab order of managed form groups does not depend on the United property value of subordinate groups. It depends on group settings (horizontal or vertical). This change is not implemented in 8.3.10 compatibility mode.	The tab order of managed form groups depended on the United property value of subordinate groups. Groups where United was set to False were ignored, their settings did not affect the tab order.	Eliminated unexpected system behavior.
Client application.	Pressing F1 or using Help menu command always opens identical help pages regardless of client application or interface mode.	Pressing F1 or using Help menu command might open different help pages depending on client application, interface mode, or help opening method.	Eliminated unexpected system behavior.
Collaboration system.	If forced switching to the recipients field of a context collaboration system conversation is performed (after an attempt to send a message without any recipients specified), once a user selects a recipient, the focus is set to the message text field.	If forced switching to the recipients field of a context collaboration system conversation was performed (after an attempt to send a message without any recipients specified), once a user selected a recipient (i.e. selected any option except for No notification), the focus stayed in the recipients field.	Improved interface for sending messages in context collaboration system conversations.

Table of contents

Changes that affect system behavior

Functionality	After	Before	Result of changes
Client application.	When 1C:Enterprise opens an infobase that is not registered in its infobase list, it creates a directory for storing the service data of the infobase. It creates an individual directory with a unique name for each infobase connection string and each infobase user. The maximum number of directories is 20.	When 1C:Enterprise opened an infobase that was not registered in its infobase list, it used a directory with a predefined name for storing the service data of all such infobases: 00000000-0000-0000-0000-00000000000.	The service data of infobases that are not registered in the infobase list is stored in dedicated directories. This facilitates disk space management and prevents the growth of a single directory.
Development tools.	When a custom command of a metadata object is renamed, the platform checks whether the new name exactly matches the name of any standard command of that metadata object. The platform also performs this check during the configuration logical integrity check.	This feature was not provided. Names of custom commands of a metadata object could exactly match the names of its standard commands.	Eliminated unexpected system behavior.
Charts.	The chart scale view settings are expanded, they now include scale view, color, and position, scale label angle, grid line visibility and color, and more. For ChartScale object, the following properties are implemented: GridLinesShowMode, GridLine, GridLineColor, LabelFont, LabelColor, LabelOrientation, MaxLabelRows, LabelAngle, LabelFormat, ScaleLocation, ScaleLine, ScaleLineColor, ScaleStep, ScaleMarkLocation, and ScaleLabelLocation. The following properties of ChartPlotArea object are deprecated, they are supported solely for compatibility purposes: ShowSeriesScaleLabels. Use SeriesScale.ScaleLabelLocation instead. ShowPointsScaleLabels. Use PointsScale.ScaleLabelLocation instead. ShowValuesScaleLabels. Use ValuesScale.ScaleLabelLocation instead. ShowScaleValueLines. Use ValuesScale.GridLinesShowMode instead. ValueScaleFormat. Use ValuesScale.LabelFormat instead. LabelsOrientation. Use PointsScale.LabelOrientation instead. In version 8.3.10 compatibility mode, the following properties are hidden from the property palette and do not affect the chart view: LabelAngle ScaleLocation MaxLabelRows ScaleMarkLocation ScaleLabelLocation	These features were not provided. The chart scale view settings were simpler.	Expanded chart view options.
Full-text search.	The following full-text search features are implemented: In privileged mode, the platform does not check the access rights for objects processed by full-text search. The option to specify whether full-text search gets object presentations is implemented. The FullTextSearchList.GetPresentation property is implemented. The platform always checks the access rights for the object fields that form the presentation, regardless of the value of this property. The platform always checks the access rights for the object fields that form the object description, regardless of the value of FullTextSearchList.GetDescription property. To apply these changes, disable the compatibility mode and rebuild the full-text search index. Previous 1C:Enterprise versions cannot work with indexes built in version 8.3.11 with compatibility mode disabled. This change is not implemented in 8.3.10 compatibility mode.	Full-text search worked as follows: In privileged mode, the platform checked the access rights for objects processed by full-text search. The platform did not check the access rights for object fields that formed the presentation if FullTextSearchList.GetDescription property was set to False.	Optimized full-text search.
Data composition system. Spreadsheet documents.	In the data compostion system, nested charts and tables of the resulting spreadsheet document are located in spreadsheet document groupings. The data composition system template composer creates blank templates with VerticalLevel property set. These templates follow the templates of charts and tables located in groupings. This change is not implemented in 8.3.10 compatibility mode.	In the data compostion system, the resulting spreadsheet document did not contain groupings for charts and nested tables that did not have row groupings. The template composer did not create blank templates with VerticalLevel property set that followed the chart templates. For tables located in groupings, the composer created blank templates with VerticalLevel set to 0.	Eliminated unexpected system behavior.
XML and XDTO support.	The option to download XSD documents that import schemas that require HTTP requests to external servers (with redirects) is implemented. This change is not implemented in 8.3.10 compatibility mode.	The option to download XSD documents that imported schemas that required HTTP requests to external servers (with redirects) was not available.	Eliminated unexpected system behavior.
Development tools. Client application.	In the search and replace dialog box of the text editor, the following behavior of the Replace button is implemented: If the selected text fragment matches the search string, replace it and search for the next occurrence. Otherwise search for the next occurrence. Clicking Replace again replaces it.	In the search and replace dialog box of the text editor, clicking the Replace button searched for the next occurrence of the search string. Clicking Replace again replaced it.	Eliminated unexpected system behavior.
Spreadsheet documents.	In the dialog box for setting a spreadsheet document area name, the default name is generated in the language that matches the current 1C:Enterprise script variant. This change is not implemented in 8.3.10 compatibility mode.	In the dialog box for setting a spreadsheet document area name, the default name was generated in the language that matched the client application interface language.	Eliminated unexpected system behavior.
Development tools.	During the creation of a configuration update file, the message stating that the configuration update requires 1C:Enterprise version 8.3.9.2033 or later is no longer displayed.	During the creation of a configuration update file, the message stating that the configuration update required 1C:Enterprise version 8.3.9.2033 or later was displayed.	Removed a message that is no longer relevant.
XML and XDTO support.	When an XSD schema is imported to an XDTO package, for references to global elements and attributes, the default and fixed properties are imported to DefaultValue and Fixed properties, regardless of the element or attribute declaration type.	When an XSD schema was imported to an XDTO package, for references to global elements and attributes, the default and fixed properties that were specified locally were not imported.	Eliminated unexpected system behavior.
Dynamic lists.	If a dynamic list contains PredefinedDataName and DataVersion fields, the following rules apply to these fields: Only the following comparison types are available: Equal to, Not equal, In list, Not in list, Filled, and Empty. Search through the search field of the dynamic list is not supported. Advanced search is only available by exact match.	If a dynamic list contained PredefinedDataName and DataVersion fields, the following rules applied to these fields: All comparison types were available. Search through the search field of the dynamic list generated an error. Advanced search allowed selection of any search type but generated an error if search at beginning of line or anywhere in the line was selected.	Eliminated unexpected system behavior.
External reports and data processors.	The option to disable the warning of the unsafe operation protection system when you create an external report or data processor object is implemented (use it when you are sure that the file specified in the method parameter contains trusted script). For the Create() method of ExternalReportsManager and ExternalDataProcessorsManager objects, the UnsafeOperationProtection parameter is implemented.	This feature was not provided.	When adding an external report or an external data processor from a file, you can specify that the file contains trusted script and therefore does not require displaying the unsafe operation protection system warning.
1C:Enterprise script.	The option to omit a notification description handler is implemented. Use this option in scenarios where you would create an empty handler (because the result of the execution of an asynchronous method is not important and only the handler for the method errors is important). Now you can omit any parameter of the NotifyDescription constructor.	A handler for asynchronous method errors could only be created together with an empty handler for the method execution result.	Simplified handling of asynchronous method errors.
ZIP archive operations.	When 1C:Enterprise accesses a file name using the properties of ZipFileEntry object (this includes the scenario when a file is being written to the disk), it replaces invalid characters with underscores (_). The list of invalid characters includes all characters that are not allowed in Windows file names. 1C:Enterprise makes the replacement on all operating systems.This change is not implemented in 8.3.10 compatibility mode. To provide access to the original file names (before the character replacement), the following properties are implemented for ZipFileEntry object: OriginalFullName, OriginalName, OriginalPath, OriginalExtension, and OriginalBaseName.	If a name of a file stored in a ZIP archive contained invalid characters, the name was truncated, leaving only the part before the first invalid character. The list of invalid characters included all characters that were not allowed in Windows file names. This might cause issues when extracting files whose names contained invalid characters.	Any file can be successfully extracted from a ZIP archive on any operating system. The names of the extracted files might change,
Data display. Spreadsheet documents.	The look of a spreadsheet document containing SVG pictures in the thin client exactly matches the look of that document in the following cases: In the web client When exported to HTML5 format	The look of a spreadsheet document containing SVG pictures in the thin client could differ from the look of that document in the following cases: In the web client When exported to HTML5 format	Unified look of spreadsheet documents in various client applications and export formats.
Infobase operations. Server clusters.	In client/server mode, the reliability of the following operations is improved: Restructure database configuration Create initial image of a distributed infobase Restore infobase from a .dt file	In client/server mode, the following operations might cause issues: Restructure database configuration Create initial image of a distributed infobase Restore infobase from a .dt file	Improved reliability of some operations in client/server mode.
Spreadsheet documents. Web client.	When a spreadsheet document is exported to PDF format, the resulting document includes the page size and orientation (PickTrayByPDFSize property of a PDF document). If you need to print the resulting document on custom-size paper from a web browser, it is recommended that you set the PrintAccuracy property of the spreadsheet document to Accurate. In Microsoft Internet Explorer, you do not need to use this property.	When a spreadsheet document was exported to PDF format, the resulting document did not include the page size and orientation. Printing the resulting document required a manual check of paper size and orientation in the PDF viewer.	Eliminated unexpected system behavior.
Common objects. Configuration properties.	If you access the UsePurpose property of the entire configuration or a managed form from 1C:Enterprise script, it has Undefined value.	When the UsePurpose property of the entire configuration or a managed form was accessed from 1C:Enterprise script, it had FixedArray type, with the selected values as array elements.	Eliminated unexpected system behavior. The behavior of this property is now similar to the behavior of other properties that do not affect application functionality in 1C:Enterprise mode.
Web client.	In the web client, the performance of opening system dialog boxes, as well as dialog boxes opened using ShowQueryBox() and ShowMessageBox() methods, is improved.	In the web client, opening system dialog boxes, as well as dialog boxes opened using ShowQueryBox() and ShowMessageBox() methods, took more time.	Improved performance and reliability of the window subsystem of the web client.
Spreadsheet documents.	In spreadsheet documents, there is no spacing between pictures and their borders. This change is not implemented in 8.3.10 compatibility mode.	In spreadsheet documents, unexprected spacing might appear between pictures and their borders.	Eliminated unexpected system behavior.
Full-text search.	Morphological full-text search by attribute name is now supported. It is recommended that you rebuild the full-text search index in order to use this feature. This change is not implemented in 8.3.10 compatibility mode.	Morphological full-text search by attribute name was not supported.	Full-text search by attribute name is more user-friendly.
Data exchange.	ThisNode() method of ExchangePlan object always returns a reference to the exchange plan item with ThisNode property set to True. This change is not implemented in 8.3.10 compatibility mode.	ThisNode() method of ExchangePlan object did not always return a reference to the exchange plan item with ThisNode property set to True.	Eliminated unexpected system behavior.
Queries.	In the query language, if a CASE operation includes a nested CASE operation or ISNULL() function, which uses both a virtual field and a nonvirtual field, the CASE calculation result is correct.	In the query language, if a CASE operation included a nested CASE operation or ISNULL() function, which used both a virtual field and a nonvirtual field, the CASE calculation result was incorrect and this might cause an unexpected shutdown.	Eliminated unexpected system behavior.
Charts.	The chart view in the thin client and web client is unified: Area sizes specified in the form attribute always affect the chart view. Chart behavior is unified across client applications. Area sizes used to draw a chart exactly match the area sizes retrieved using 1C:Enterprise script. This change is not implemented in 8.3.10 compatibility mode.	The chart views in the thin client and web client were different: Area sizes specified in the form attribute did not always affect the chart view. Chart behavior was not unified across client applications. Area sizes used to draw a chart did not exactly match the area sizes retrieved using 1C:Enterprise script.	Eliminated unexpected system behavior. The chart view is more predictable.
Development tools.	During application debug, you can access variable properties (provided that it has properties) even if the variable presentation is not available.	During application debug, if a variable presentation was not available, the variable properties were also not available.	Eliminated unexpected system behavior.
Dumping configurations to files/Restoring configurations from files.	Intertactive export of configurations to files is always performed in hierarchical format. The flat format is only supported in batch Designer mode. It is recommended that you always use the hierarchical format.	The interactive export of configurations to files offered a choice between flat and hierarchical formats.	The option to export configuration files in flat format is disabled due to possible issues. For example, transferring exported files between different file systems might be difficult.
Development tools.	During debugging over TCP, debugger no longer stops responding while calculating an expression or editing a variable value.	During debugging over TCP, debugger might stop responding while calculating an expression or editing a variable value.	Application debugging over TCP is more predictable and reliable.
Client application.	In the Start menu, a single shortcut combines 32-bit and 64-bit versions of 1C:Enterprise. 1C:Enterprise installation on a computer with any operation system of Windows family adds all of the available 1C:Enterprise shortcuts to the Start menu. Pinning a running 1C:Enterprise application to the taskbar actually pins a shortcut to file 1cestart.exe. If multiple 1C:Enterprise applications are running, they are combined into a single taskbar shortcut. The jump list is only available if the shortcut to 1cestart.exe is pinned to the taskbar.	The Start menu included two 1C:Enterprise shortcuts: one for the 32-bit version and the other one for the 64-bit version. 1C:Enterprise installation on Windows 8 or later did not add all of the available 1C:Enterprise shortcuts to the Start menu. Pinning a running 1C:Enterprise application to the taskbar pinned exactly that application. If multiple 1C:Enterprise applications were running, they were combined in this shortcut. The jump list was available for any 1C:Enterprise-related shortcut.	All of the 1C:Enterprise components are available on the Start menu. The jump list behaviour is more predictable.
Data composition system.	The parsing algorithm of data composition system queries validates comparison operations that include String parameters of unlimited length. The parsing is performed when the data composition system wizard is opened and when a schema-based source of available settings is initialized (opening reports also includes this operation).	The parsing algorithm of data composition system queries that included String parameters of unlimited length generated errors stating that using strings of unlimited length in queries was not allowed.	Eliminated unexpected system behavior.
Collaboration system.	In the collaboration system, video calls use peer-to-peer connections instead of using a central server. The central server is only required to establish connections between the conversation participants.	In the collaboration system, video calls always used the central server and did not use peer-to-peer connections.	Reduced load on the central server of the collaboration system. If conversation participants belong to a local network, the video call traffic is limited to local network.
Collaboration system.	If 1C:Enterprise connects to the collaboration server through a proxy server, it gets the proxy server settings from the operating system settings or from inetcfg.xml configuration file. NTLM authentication at proxy servers is not supported.	Connection to the collaboration server through a proxy server was not supported.	Simplified collaboration system setup in scenarios that include a proxy server.
Information registers.	When an information register record set is written using InformationRegisterRecordSet.Write(), Undefined value is not ignored when setting a managed lock. This change is not implemented in 8.3.10 compatibility mode.	When an information register record set was written using InformationRegisterRecordSet.Write(), Undefined value was ignored when setting a managed lock. This resulted in locking excessive data.	Improved parallel writing of information register record sets when multiple users write dimensions of composite types where dimension values can be blank.
Localization.	Support of Kazakh user interface (kk language code) is restored.	Support of Kazakh user interface was not available.	1C:Enterprise now provides the option to use Kazakh user interface.
Localization.	The French interface language (language code: fr) is not supported.	The French interface language (language code: fr) was supported.	The French interface language is not supported.
Server clusters.	On Linux, the working process parameter Memory occupied is calculated based on VmRSS (resident set size) value. The value of Memory occupied parameter in absolute terms is reduced and it is more accurate. It is recommended that you revise the working process restart options in the working server properties.	On Linux, the working process parameter Memory occupied was calculated based on VmSize (virtual memory usage) value.	On Linux, the cluster monitoring system uses a parameter that provides more accurate data.
Localization.	Entering Russian Ruble symbol (₽, ISO 4217 643) from the keyboard is supported.	This feature was not provided.	Eliminated unexpected system behavior.
Applied objects.	When floating point numbers are converted between 1C:Enterprise format and external formats, the accuracy of their presentations is never lost. In scenarios where previously accuracy losses were possible, the conversion algorithm does not depend on the operating system.	When floating point numbers were converted between 1C:Enterprise format and external formats, accuracy losses were possible. In scenarios where accuracy losses were possible, the conversion algorithm depended on the operation system.	Reduced number of scenarios where conversion of floating point numbers with significant digits in their fractional parts between 1C:Enterprise format and external formats (such as XSL file format) introduces accuracy losses.

Table of contents

Changes that require modification of configuration and administrative settings

Table of contents

Object	The old name	The new name
The name of CREATEINFOBASE command-line option parameter that specifies whether the infobase is added to the infobase list. The previous name is supported for compatibility purposes.	AddInList.	AddToList.
Name of the property of ChartPlotArea object. The previous name is supported for compatibility purposes.	ShowScale	ShowScales
Data composition system output parameter property ChartType.ChartBubbleSizing. In 8.3.10 compatibility mode, the old name is used (in 1C:Enterprise language and when writing the parameter to an XML file).	ChartType.ChartBubbleSizing.	ChartType.BubbleSizing.

Functionality	After	Before	Result of changes
Mobile device-specific features.	The following permissions are implemented for iOS mobile applications: Background location. The mobile application gets location data even when it is inactive. Background audio playback. The mobile application plays audio even when it is inactive. File exchange with PC. Use this permission for mobile applications that exchange files through iTunes.	These features were not provided.	Expanded settings for iOS mobile applications.
Managed forms.	In the mobile platform, the object that visualizes planner data (the planner) is now available. For the object usage specifics, see the documentation.	The planner was only available on the platform for personal computer.	Expanded data presentation options on mobile devices.
Mobile device-specific features.	Support of local and push notifications is added to the mobile platform for Windows. 1C:Enterprise uses Windows Notification Services for this purpose. The notification sending service provided by 1C Company does not support Windows Notification Services. The system enumeration value DeliverableNotificationSubscriberType.WNS is implemented.The DeliverableNotificationSendManager.GetAccessToken() method is implemented. Notification sending errors are returned in the return value of DeliverableNotificationSendManager.Send() method.This change is not implemented in 8.3.10 compatibility mode. The system enumeration DeliverableNotificationSendErrorType is implemented. The DeliverableNotificationSendIssueInformation object is implemented. For DeliverableNotificationSendManager.Send() method, the DeliverableNotificationSendIssuesInformation parameter is implemented. The option to get a local notification when a device is crossing a geofence border is implemented.	Support of local and push notifications was only available for iOS and Android devices. Notification sending errors generated exceptions.	Standard user notifications are now available on mobile Windows devices. Both mobile applications and desktop applications can generate notifications (local and push notifications, respectively).
System requirements.	Support for Android versions earlier than 4.0 is ended. The earliest supported API version is API 14 (Androuid 4.0).	Android versions with API 9 (Android 2.3) or later were supported.	Ended support for legacy Android versions.
Print tools. Spreadsheet documents.	In the mobile platform, support of batch printing is implemented.	This feature was not provided.	Batch printing is now available in the mobile platform.
File operations.	On the mobile platform, the file selection dialog box now supports multiple file masks. The search by mask in the file selection dialog box and the search by mask with FindFiles() method are now case-insensitive. The file selection dialog box and FindFiles() method now support iOS and Android wildcards.	The file selection dialog box did not support multiple file masks. The search by mask in the file selection dialog box and the search by mask with FindFiles() method were case-sensitive. The file selection dialog box and FindFiles() method did not support iOS and Android wildcards.	Expanded file operation tools in the mobile platform. These tools are unified with file operation tools available in the desktop platform.
Formatted documents.	The mobile platform now supports FormattedDocument object (and can display formatted documents in managed forms).	This feature was not provided.	Expanded support of formatted text in mobile applications.
Mobile device-specific features.	On the mobile platform for Windows (except Windows 8.1), support of map operations is implemented. The following methods are now available: ShowOnMap(), GetAddressByLocation(), and GetLocationByAddress(). Global context method MapRepresentationSupported() is implemented.	Map operations were not supported on Windows mobile devices.	Extended mobile platform capabilities on Windows. Determining whether map operations are available is standardized with other operations that might be unavailable on some devices or operating systems.
Mobile applications.	When a configuration that was saved using an earlier 1C:Enterprise version for personal computer is loaded to a mobile application, the mobile device displays a warning and provides the option to cancel the operation.	When a configuration was loaded on a mobile device, 1C:Enterprise did not check whether the configuration was saved using an earlier 1C:Enterprise version for personal computer.	Implemented diagnostics of potential compatibility issues between the mobile platform and the configuration to be loaded (in scenarios where the configuration was saved using an earlier 1C:Enterprise version for personal computer).
Mobile device-specific features.	On Android devices, the following operations with SMS messages are implemented: Get SMS log and check whether getting the log is allowed. For TelephonyTools object, methods SMSLogSupported() and GetSMSLog() are implemented.The SMSLog object is implemented. Filter SMS messages. Create a message based on another message. The wizard that creates an SMS message based on an SMS log entry is implemented. On Android devices, in method SMSLog.FindRecords(), ungrouped filter items are combined using AND operator.	On Android devices, access to SMS message log was not provided. On Android devices, in method SMSLog.FindRecords(), ungrouped filter items were combined using OR operator.	Introduced advanced SMS management tools on Android devices. The behavior of the filter used in a search in the SMS message log is unified with other filters.
Database configuration update.	In built mobile applications, the message stating that unused data will be deleted is no longer displayed after configuration updates. The mobile platform for developers displays a message stating that the update changes metadata structure (only when it actually changes it). The developers are now responsible for preventing data losses caused by configuration updates.	If a configuration update changed metadata structure, a message stating that unused data will be deleted was displayed after the update. The message was displayed both in built mobile applications and in the mobile platform for developers.	Configuration updates are now less distressing to end users. In patricular, end users do not get a message that their data will be lost (which was not always true). At the same time, developers must be more cautious when implementing configuration changes that might cause losses or user data.

Transition from the previous version to the version 8.3.11

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.11.
Some features that are added in version 8.3.11 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.
It is recommended that you rebuild the full-text search index in order to use morphological full-text search by attribute name.
In order to use the collaboration system in 1C:Enterprise 8.3.11 test release, you have to reregister the infobase. After the update to 1C:Enterprise 8.3.11 final release, you have to reregister it. The message history for the period between these two registrations will not be preserved.
It is recommended that you uninstall your HASP Device Driver and then install HASP Device Driver 7.60, which is a part of 1C:Enterprise distribution package.

Table of contents

Version 8.3.10

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
Library updates
Transition from the previous version to the version 8.3.10

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 OnGetDataAtServer. 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.DimensionValues.	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 SelectVariant.	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 DataCompositionAreaTemplateChartGroupAppearance and DataCompositionAppearance, implemented parameters ChartTrendline, ShowGraphicalDataRepresentationInChart, and ShowGraphicalDataRepresentationInChartLegend.	These features were not provided. Value of property ChartSeries.Marker was set to Rect, Circle, or Rhomb, 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.ChartBubbleSizing, 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 that supports interaction between the server, client applications, and users of a single infobase. The collaboration system simplifies automation of enterprise business processes and provides an easy way to establish work-related communication. 1C:Enterprise application uses can exchange text messages and call each other (audio calls with optional video feed). Text conversations can be related to specific infobase objects (context conversations) or not related to any object (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. The email message with the registration code sent from 1cDialog.com when you request registration in the service will include instructions for enabling video calls.	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 SetRestrictionsForUseInGroup(), SetRestrictionsForUseInOrder(), SetRestrictionsForUseInFilter(), GetRestrictionsForUseInGroup(), GetRestrictionsForUseInOrder(), and GetRestrictionsForUseInFilter().	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.
Client application.	For the thin and thick client applications that directly connect to a 1C:Enterprise server, the disconnection monitoring mechanism is implemented. If a server connection issue is detected, the client application automatically attempts to reestablish the connection and repeat the server call. If the connection cannot be established, the application is shut down. The following timeouts are applied: Thin client: ping every 3 seconds, wait for connection for 15 seconds. Thick client: ping every 12 seconds, wait for connection for 60 seconds. The timeout values cannot be changed.	If any server connection issues occurred in the thin or thick client application that was directly connected to a 1C:Enterprise server, the client application might stop responding for a long period (several minutes). That period was defined by TCP stack settings in the operating system.	Improved reliability of client applications that directly connect to a 1C:Enterprise server. Reduced chance of situations when an application stops responding.
DBMS operations. System requirements.	Support of PostgreSQL version 9.6 is implemented.	This PostgreSQL version was not supported.	Extended list of supported PostgreSQL versions.
DBMS operations. System requirements.	Support of Postgres Pro Enterprise version 9.6 is implemented (only in managed lock management mode).	Postgres Pro Enterprise was not supported.	Extended list of supported DBMS versions.

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.
Client application installation.	If any issue occurs during the thin client update over HTTP, you have the option to get the name of the file that cannot be updated. This option is provided in the following scenarios: The archive is corrupted or has invalid structure (the archive file name is provided). One of the distribution kit files has invalid digital signature (the name of this file is provided).	If any issue occurred during the thin client update over HTTP, the option to get the name of the file that cannot be updated was not available. In particular, there was no way to get the file name of a corrupted archive of the name of the file that had invalid digital signature.	Improved issue diagnostics during the thin client update over HTTP.

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(), WriteBitwiseAndNot(), 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.
Spreadsheet documents. Data composition system.	For spreadsheet documents, the option to automatically adapt column width to the display area is implemented (both for viewing and printing). For SpreadsheetDocumentRange and DataCompositionAreaTemplateTableCellAppearance objects, implemented properties HorizontalStretch and WidthWeightFactor. For DataCompositionAppearance object, implemented appearance parameters HorizontalStretch and WidthWeightFactor. When the data composition system displays a chart in a spreadsheet document, it automatically sizes the chart to fit the display area width. This change is not implemented in 8.3.9 compatibility mode.	Spreadsheet document column width could not be adapted to the display area width. When the data composition system displayed a chart in a spreadsheet document, the chart had fixed width.	Improved options for adapting spreadsheed documents to the display area.
Spreadsheet documents.	For form field extension for a spreadsheet document field, the following improvements are implemented: More options for cell selection visibility. You can completely hide the cell selection, or you can make the cell selection visible only when multiple cells are selected (Show selection property). For SelectionShowMode system enumeration, implemented properties DontShow, WhenMultipleCellsSelected, and WhenMultipleCellsSelectedWhenActive. More options for scroll bar visibility: you can have scroll bars displayed only when necessary. The type of VerticalScrollBar и HorizontalScrollBar properties is changed to ScrollBarUse. The option to change the shape of pointer located in a form field extension for a spreadsheet document field. The pointer shape can change depending on the spreadsheet document area where it is located. Implemented property PointerType. The behavior of arrow keys depends on the Show selection property value. If this property is set to Do not show, the arrow keys scroll the spreadsheet document. If this property is set to any of When multiple cells... values, pressing the arrow keys while holding down Shift changes the selection size, and pressing arrow keys without holding down Shift scrolls the spreadsheet document (while keeping the selection).	The following options were available for form field extension for a spreadsheet document field: The selection was either always visible or visible when a cell was activated. The scroll bars were always visible or always hidden. Making scroll bars visible when necessary was not available. The pointer shape in a spreadsheet document always depended on the content of the cell where is was located. The behavior of arrow keys in a spreadsheet document did not depend on any properties of form field extension for a spreadsheet document field.	Extended display options for spreadsheet documents embedded in managed forms.
Managed forms.	In managed form tables, improved algorithm for automatic column width calculation based on the font settings. This change is not implemented in 8.3.9 compatibility mode.	The algorithm for automatic column width calculation based on the font settings sometimes generated poor results.	Improved view of managed form tables.
Dumping configurations to files/Restoring configurations from files.	When restoring help topics from XML files, 1C:Enterprise does not check whether the language of the help topics (Language configuration object) is available in the configuration.	When restoring help topics from XML files, 1C:Enterprise did not restore the help topics whose language (Language configuration object) was not available in the configuration.	Simplified dumping and restoration of configurations, external reports, and external data processors to or from XML files.
Development tools. Configuration extensions.	Configuration extension bookmarks, breakpoints, and performance measurements are stored with extension names.	Configuration extension bookmarks, breakpoints, and performance measurements were stored with internal extension IDs.	Support for future integration of extension debugging with 1C:Enterprise Development Tools.
macOS. Spreadsheet documents.	Implemented export of spreadsheet documents to PDF format on macOS.	An attempt to export a spreadsheet document to PDF format on macOS generated an error.	Eliminated unexpected system behavior.
Operating system.	The time zone detection algorithm on Windows is modified. Now the time zone is determined as follows: Get time zone presentation using Windows API. Search Windows registry for time zone ID by presentation. Use ICU library to determine time zone by ID. If the time zone cannot be determined using this algorithm, try the previous algorithm.	The platform used the following time zone detection algorithm on Windows: Get time zone ID from Windows registry. Use ICU library to determine time zone by ID. If the time zone with this ID is not found in ICU, get time zone using Windows API. Apply time zone parameters (offset, daylight saving time, and so on) and search ICU for a matching time zone.	The session time zone is determined correctly on Windows terminal servers.
DBMS operations.	If 1C:Enterprise is running in managed lock mode (in client/server mode) with PostgreSQL version 9.3 or later, it supports setting lock waiting time. The waiting time is retrieved from the infobase parameters, just like in configurations that use other DBMS types.	If 1C:Enterprise was running in managed lock mode (in client/server mode) with PostgreSQL version 9.3 or later, it did not support setting lock waiting time. In configurations that used PostgreSQL, setting lock waiting time was only supported in automatic lock mode.	In configurations that used PostgreSQL, operations with lock waiting time in managed mode are identical to operations with lock waiting time in configurations that use other DBMS.
Charts. Spreadsheet documents.	When a spreadsheet document that contains a chart is saved to a file, automatically assigned point colors, series colors, and series markers are stored in the format supported by earlier 1C:Enterprise versions. This ensures that the colors and markers are displayed correctly in earlier 1C:Enterprise versions.	When a spreadsheet document that contained a chart was saved to a file, automatically assigned colors and markers were stored in the format that was not supported by earlier 1C:Enterprise versions. This might significantly alter the chart look in earlier 1C:Enterprise versions.	The look of spreadsheet documents with charts in earlier 1C:Enterprise versions is very similar to their look in 1C:Enterprise version 8.3.10 or later.

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.	For global context method ShowUserNotification(), implemented parameters UserNotificationStatus and UniquenessKey. The parameter of URL method is renamed to ActionOnClick. The look of notifications with Information status is slightly changed. In Taxi interface, notifications with Important status are redesigned, including the following changes: 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 clicking the notification window Implemented notification management through the notification center. Dragging the notification window is not supported. 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.	Notifications with Important status are implemented. They are displayed even if the application window is inactive.
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.
Background and scheduled jobs. Common attributes / Data separation.	When a background job is started with a uniqueness key specified, the key uniqueness is verified within the area described by the current set of separators. For each unique set of separators, you can run a single background job with a uniqueness key specified. This change is not implemented in 8.3.9 compatibility mode.	When a background job was started with a uniqueness key specified, the key uniqueness was verified within the entire infobase, regardless of the separator values.	You can run a background job in each unique data area. For example, you can run long calculations in different areas of a separated infobase and avoid conflicts related to duplicate uniqueness keys.
Managed forms.	If the Cancel parameter of OnOpen managed form handler is set to True, once the handler execution is completed, the memory occupied by the form is cleared, all related resources (temporary storage, locks, and so on) are released, and idle handlers are disabled. This change is not implemented in 8.3.9 compatibility mode.	If the Cancel parameter of OnOpen managed form handler was set to True, once the handler execution was completed, in some scenarios the memory occupied by the form was not cleared. Consequently, all related resources (temporary storage, locks, and so on) were not released, and idle handlers were not disabled.	Eliminated unexpected system behavior.
Managed forms.	Implemented the option to apply through alignment (Through alignment property) to managed form groups with United property set to False. This change is not implemented in 8.3.9 compatibility mode.	For managed form groups with United property set to False, the value of the Through alignment property was ignored.	Eliminated unexpected system behavior.
Linux. System requirements.	1C:Enterprise system requirements for Linux computers are modified. The freetype library is now included in 1C:Enterprise distribution kit and excluded from the list of libraries whose availability is verified at 1C:Enterprise startup.	The freetype library was not included in 1C:Enterprise distribution kit. Its availability was verified at 1C:Enterprise startup.	The system requirements for Linux computers are simplified.
Managed forms.	If FixingInTable property of a managed form table column group is set to Left or Right, all of the columns belonging to the group are fixed, as well as all other columns with this property set to Left or Right. This change is not implemented in 8.3.9 compatibility mode.	If FixingInTable property of a managed form table column group was set to Left or Right, only columns to the left or to the right of the group, respectively, were fixed. The columns included in the group were not fixed.	Eliminated unexpected system behavior.
Managed forms.	If a managed group form of "command bar" type has GroupVerticalAlign property set to Auto and it belongs to a group or form with ChildItemsVerticalAlign property set to Auto, the command bar is displayed at the top of the parent group (just below the last item). This change is not implemented in 8.3.9 compatibility mode.	If a managed group form of "command bar" type had GroupVerticalAlign property set to Auto and it belonged to a group or form with ChildItemsVerticalAlign property set to Auto, the command bar was displayed at the bottom of the parent group.	Eliminated unexpected system behavior.
Dynamic lists.	In dynamic list search field, values that can be interpreted as numbers in exponential notation are treated as strings (the platform searches for the specified string). This change is not implemented in 8.3.9 compatibility mode.	In dynamic list search field, values that could be interpreted as numbers in exponential notation were treated as numbers (the platform searched for the number).	Eliminated unexpected system behavior.
Data composition system.	The Use property of data parameters that can be edited by users but are disabled by functional options is disabled in the following scenarios: Loading a report option Calling DataCompositionSettingsComposer.Refresh() This change is not implemented in 8.3.9 compatibility mode.	The Use property of data parameters that were disabled by functional options was disabled in the following scenarios: Loading a report option Calling DataCompositionSettingsComposer.Refresh()	Improved compatibility with data composition system queries created using previous 1C:Enterprise versions.
1C:Enterprise script. Web client.	In the web client, Title() function only converts strings that contain only Latin characters (A-Z, a-z), numbers, and special characters. In other client applications and on the server, Title() function behavior remains unchanged: the conversion rules are defined in the Unicode standard.	In the web client, Title() function always returned the source string.	Corrected the behavior of Title() function.
System requirements. Administration.	1C:Enterprise distribution packages for Windows and macOS include HASP Device Driver 7.60.	1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 6.60.	1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver.

Table of contents

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
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
Property InfoBaseUser.UnsafeActionProtection. The previous name is now deprecated and supported for compatibility purposes only.	UnsafeActionProtection.	UnsafeOperationProtection.
Object UnsafeActionProtectionDescription. The previous name is now deprecated and supported for compatibility purposes only.	UnsafeActionProtectionDescription.	UnsafeOperationProtectionDescription.
Property UnsafeActionProtectionDescription.WarnAboutUnsafeActions. The previous name is now deprecated and supported for compatibility purposes only.	WarnAboutUnsafeActions.	UnsafeOperationWarnings.
The system enumeration that defines the height of a managed form table is renamed. The previous name is now deprecated and supported for compatibility purposes only.	HeightControlVariant.	ItemHeightControlVariant.

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 AttachMonitoredGeofencesBordersCrossingDetectionHandler().	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 ContactsAddingSupported(). 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 GetMobileDeviceLibraryFileThumbnail() and BeginGetMobileDeviceLibraryFileThumbnail().	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 BeginGettingMobileDeviceLibraryDir().	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.
Print tools.	Printing is now supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64).	Printing was not supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64).	Extended mobile application capabilities on Windows.
Mobile applications.	Hardware rendering support is implemented for user interface on Android devices.	This feature was not provided.	Improved performance of user interface generation on Android devices.
Mobile application builder.	In the mobile application builder, automatic deletion of obsolete data is implemented. Obsolete data is defined as mobile application builds and mobile platforms that were last changed (or imported) before a specific date. This date is calculated as follows: current date minus the specified number of days (the gap size). You can specify custom gaps for mobile application builds and mobile platforms. Default values: 90 days for mobile application builds 180 days for mobile platform files If you set the gap size to 0, obsolete objects are never deleted. When you attempt to use an obsolete object, the mobile application builder prompts you to rebuild the mobile application or reimport the mobile platform.	The mobile application builder did not provide tools for automatic deletion of obsolete objects.	You have the option to keep the size of the mobile application builder infobase within reasonable limits, avoiding significant growth of the disk space occupied by this infobase.
Mobile application builder.	The requirements to Android SDK components used to build mobile applications are defined by the requirements of the mobile platform version used to build the applications. The builder uses the latest Android API Level available on the computer, provided that the API Level meets the mobile platform requirements. The requirements to other Android SDK components are defined by Android API Level requirements. If the mobile platform was loaded in a previous builder version, the builder requires Android API Level version 24 or later.	The following Android SDK components were required to build mobile applications for Android: Android API Level version 23 or later Android Tools version 20.0.3 or later Android Platform Tools version 14 or later Android Build Tools version 19.0.0 or later These requirements were applied regardless of the mobile platform versions used to build mobile applications. They were hardcoded in the mobile application builder.	The requirements to mobile application build infrastructure for Android are defined by the mobile platform version, instead of the requirements hardcoded in the mobile application builder.
Mobile application builder.	In mobile application builder, Gradle tool now can be used to build mobile applications. On Android SDK version 26 or later, you can build mobile applications using no other tools besides Gradle. You can specify two Android SDK paths in the builder settings: one for version 25 or ealier and the other one for version 26 or later. Therefore, you can build mobile applications that require any specific Android SDK version. Building with Gradle requires Java 8 on the computer that runs mobile application builder. It does not require Apache Ant.	Mobile application builder did not support building mobile applications with Gradle tool.	Building mobile applications that use new Android SDK versions is now available.
Mobile applications.	Since mobile platform version 8.3.10.71, only building mobile applications with Gradle tool is supported. Use mobile application builder provided as a part of the mobile platform distribution package to build mobile applications. Since mobile platform version 8.3.10.71, Apache Ant is not required for building mobile applications.	Mobile platform versions earlier that 8.3.10.71 did not support Gradle. Building the mobile platform required Apache Ant.	The mobile application building procedure is modified to comply with the changes in the recommended application building procedure for Android.

Library updates

The OpenSSL library is updated to version 1.0.2k and modified to eliminate vulnerabilities.
The libxml2 library is modified to eliminate vulnerabilities.
The libxslt library is modified to eliminate vulnerabilities.
The libtiff library is updated to version 4.0.8.
The libpng library is updated to version 1.6.29.

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.
It is recommended that you uninstall your HASP Device Driver and then install HASP Device Driver 7.60, which is a part of 1C:Enterprise distribution package.

Table of contents

Version 8.3.9

Version 8.3.9 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
Library updates
Transition from the previous version to the version 8.3.9

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.3.8 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, 8.3.6, and 8.3.7.	In version 8.3.9 you can run configurations created in version 8.3.8 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.9 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also gives you the option to use version 8.3.8 for working with the infobase even after the transition to version 8.3.9. You can use this option both before and after removing the compatibility mode (in the latter case you have to turn the compatibility mode back on).
Configuration extensions. 1C:Enterprise script.	In configuration extensions, the option to adopt the following objects is implemented: Common modules Object modules for all object types Manager modules for all object types Session module Managed application module External connection module Command modules The option to adopt ordinary form modules and ordinary application modules is not available.Therefore, you can adopt any module except for modules that are used solely in ordinary applications. The following operations are now available: Call any methods of the extended module from the extending module Add event handlers to adopted modules of abovementioned types Export methods and variables of the extended module form the uniform context of the extended module. Adopted form modules are now handled differently. You have the option to allow or deny extending all modules of abovementioned types (the all module extensions security profile property). You have the option to provide a list of modules where extension is allowed (the Modules available for extension property) or where extension is denied (the Modules not available for extension property). You have the option to create common modules in configuration extensions. For ISecurityProfile object, the following properties are implemented: AllModulesExtension, ModulesAvailableForExtension, and ModulesNotAvailableForExtension (software administration of server clusters based on COM objects). For ISecurityProfile interface, the following methods are implemented: getAllModulesExtension(), setAllModulesExtension(), getModulesAvailableForExtension(), setModulesAvailableForExtension(), getModulesNotAvailableForExtension(), and setModulesNotAvailableForExtension() (Java interface for server administration). In the server cluster command-line utility (rac), for the profile command, the following parameters are implemented: all-modules-extension, modules-available-for-extension, and modules-not-available-for-extension.	The option to adopt modules was not available, except for form modules. The option to create common modules in configuration extensions was not available. Adopted form modules were handled differently. The option to specify which modules can be extended was not available.	The configuration extensions feature now provides the option to extend all 1C:Enterprise script modules, except for those used solely in ordinary applications. New security profile options related to configuration extensions.
Web services and HTTP services. OData interface. Configuration extensions. Server clusters.	The option to manage session lifetime when using Internet services and the standard OData interface is implemented: Automatic reuse of the current session when a new request comes from the same user. Session lifetime management using HTTP request headers. For web services and HTTP services, the ReuseSessions and SessionMaxAge properties are implemented. If a web service or HTTP service is a native configuration extension object, these properties are read-only. The following additions to the default.vrd file are implemented: <standardOData> element, which is subordinate to <point> element. reuseSessions, sessionMaxAge, poolTimeout, and poolSize attributes for <point> and <service> elements. The enableStandardOData attribute of the <point> element is deprecated. If a web service or an HTTP service is a native configuration extension object and it is either not published in the default.vrd file or published without the session reuse option, session reuses are not available for that service. A server cluster service that manages the automatic pool of reused sessions is implemented. The service name is SessionReuseService (Session reuse service).	This feature was not provided. A new session was created for each Internet service call and each standard OData interface query.	Improved performance of Internet services and the standard OData interface.
Formatted documents.	The behavior of the Tab key is changed: If a text is selected or the cursor is located at the beginning of a paragraph, pressing Tab increases the indent. Otherwise pressing Tab adds a tab character. The FormattedDocumentBookmark object is linked to a character within a paragraph, not to a character position. If a text is changed, the bookmark position better matches its original position.	Pressing Tab always increased the indent. The FormattedDocumentBookmark object was linked to a character position within a paragraph.	Formatted document behavior better meets user expectations.
Binary data.	Tools for operations with binary data are implemented. They provide the following options: Specifying byte order Operations with memory buffer that stores binary data File operations where files are treated as binary data Byte-by-byte data access Reading and writing some data types (String and Number). The following objects are implemented: BinaryDataBuffer, Stream, FileStream, MemoryStream, DataReader, DataWriter, ReadDataResult, FileStreamsManager. The BinaryData.Size() method is now available in the web client. For the BinaryData.Write() method, the option to write data to a stream is implemented. The OpenStreamForRead() method is implemented, it opens a stream for reading binary data specified in the BinaryData object.	These options were not provided. The only available options were reading files from disk and writing files to disk without any means to perform any other operations with those files.	Extented capabilities for operations with binary data.
Pictures.	Support of vector images in SVG format is implemented. The PictureFormat.SVG system enumeration value is implemented. The picture editor in Designer does not support editing pictures that have SVG format. The specifics of SVG format support are described in the documentation.	This feature was not provided.	Extended list of supported picture formats. You have the option to use scalable pictures that can be displayed in areas of any size.
Administration tools.	For the /regserver client application command-line option (registration of COM objects), the following optional parameters are implemented: -AllUsers. Perform registration for all computer users. -CurrentUser. Perform registration for the current user. -Auto. Automatically select registration mode based on the user rights, without displaying any questions. The behavior of the /regserver option without parameters is not changed.	When a client application was started with the /regserver command-line option (registration of COM objects), it attempted to perform the registration for all users. If the current user did not have the rights for this, they were prompted to confirm the registration for the current user.	Simpler usage of the /regserver command-line option in 1C:Enterprise batch startup mode.
XML and XDTO support.	Support of Canonical XML 1.1 specification is implemented. The ConversionToCanonicalXML object is implemented. For the XMLCanonicalizationType system enumeration, the following values are implemented: XMLCanonicalization1_1 and XMLCanonicalization1_1WithComments. The XMLCanonicalizingWriter and DOMCanonicalization objects are deprecated. These objects do not support Canonical XML 1.1 specification.	Only Canonical XML 1.0 specification was supported.	Extended capabilities for integration with third-party systems.
DBMS operations. Administration tools.	The option to attempt the restoration of database structure from Designer batch mode command line is implemented. The /IBRestoreIntegrity Designer command-line option is implemented. Running Designer with the /IBRestoreIntegrity parameter is recommended if a previous database configuration update (performed either interactively or in batch mode) have not been completed successfully because of unexpected Designer shutdown or power outage.	This feature was not provided.	Improved infobase fault tolerance in scenarios that include database configuration update.
Predefined data. Event log.	Recording events related to predefined data restructuring to the event log is implemented. This includes the following events: Infobase.Set predefined data update Infobase.Predefined data update Data.Set predefined data initialization Data.Initialize predefined data Data.Add predefined data Data.Modify predefined data Data.Delete predefined data Data.Initialize predefined data, data not found	This feature was not provided.	Simplified diagnostics of predefined data issues.
Spreadsheet documents.	The export of spreadsheet documents to Microsoft Office OpenXML (Microsoft Word 2007- 2010) format includes the export of pictures stored in spreadsheet document cells. This change is not implemented in 8.3.8 compatibility mode.	The export of spreadsheet documents to Microsoft Office OpenXML (Microsoft Word 2007- 2010) format did not include the export of pictures stored in spreadsheet document cells.	Spreadsheet documents exported to Microsoft Word better match the original spreadsheet documents.
Internet-enabled functionality.	The following algorithms can be used together with TLS protocol: GOST R 34.10-2001, GOST R 34.10-94, GOST R 34.11-94, and GOST 28147-89. GOST R 34.10-2012 and GOST R 34.11-2012 algorithms are not supported.	This feature was not provided.	Internet services that use the listed GOST algorithms together with TLS protocol are now supported.
OData interface.	For the standard OData interface, the option to get the following data is implemented: Predefined data item flag and name. Data attribute presentations. The ____Presentation field name suffix is used for getting presentations. Presentation fields are only available for use in the $select operator and only if you specify them explicitly. Specific attributes of tabular sections or record sets (in the $select operator).	These features were not provided.	Extended capabilities of the standard OData interface.
OData interface.	For queries to the standard OData interface, support of the $expand operator is implemented. This gives you the option to include referenced entities in the response body.	This feature was not provided.	The option to get values of referenced entities together with the main query result is implemented, which eliminates the need to use a separate query for each referenced entity.
Dynamic lists.	The following changes are made in the dynamic list query builder: The option to edit batch queries is implemented (the Query batch wizard page). Specifying the number of selected records is not supported but disabling this query option is supported. When the query builder is closed, it checks the query for the TOP keyword and, if the keyword is present, reports that. This change is not implemented in 8.3.8 compatibility mode.	The dynamic list query builder did not provide the option to edit batch queries. The option to specify the number of selected records was available but this number was never used.	The option to edit query batches using the dynamic list query builder is implemented. Better error diagnostics for dynamic list queries.
Configuration extensions.	The option to change access rights (including data access restrictions) in adopted roles is implemented. The option to add roles to configuration extensions is implemented, this requires the use of 1C:Enterprise script. In Designer, the only operation available for such roles is deletion. The option to apply data access restirictions added in a configuration extension to the resulting configuration is implemented through the use of security profiles (the access rights extension property). For the ISecurityProfile object, the RightExtension and RightExtensionDefinitionRoles properties are implemented (for the technology of programmatic cluster administration based on COM objects). For the ISecurityProfile object, the RightExtension and RightExtensionDefinitionRoles properties are implemented (for the Java administration server interface). For the server cluster command-line utility (rac), the right-extension and right-extension-definition-roles parameters of the profile command are implemented.	In configuration extensions, only the option to set access rights for native extension objects in adopted roles was available. The option to change rights in adopted roles was not available.	Significant improvements for access right management in configuration extensions.
Configuration extensions. Development tools.	The following options to check the applicability of a configuration extension without running an applied solution with this extension are implemented: The Check applicability command in the Configuration extensions window 1C:Enterprise script methods Designer batch mode option When a client application is started, extension compatibility issues are no longer displayed in the message window. Instead, they are added to the information for technical support (which is available from the About 1C:Enterprise window). If any compatibility issues are encountered, a warning dialog box is also displayed, with a link to the full list of issues. For the ConfigurationExtensions object, the CheckCanApplyAll() and GetSessionApplicationIssuesInformation() methods are implemented. For the ConfigurationExtension object, the CheckCanApply() method is implemented. For Designer batch mode, the /CheckCanApplyConfigurationExtensions command-line option is implemented. For the Configuration extension management standard function, the Check applicability when adding and loading extensions check box is implemented.	These features were not provided. When an extension was attached, the diagnostics messages were displayed in the message window.	Improved diagnostics for configuration extension attachment issues. The option to automate the diagnostics by running them in the batch mode is implemented.
Event log.	When the event log is exported to an XML file, the state of predefined data update is exported as the value of the Data field. The PredefinedDataUpdate system enumeration is now available in the thin and web clients.	This feature was not provided.	The event log export to an XML file is adjusted to reflect the new events.
Localization.	The French localization of the client applications is available.	This feature was not provided.	1C:Enterprise is available to French-speaking users.
Localization.	The Hungarian localization of the client applications is available.	This feature was not provided.	The Hungarian platform interface is available. 1C:Enterprise is available to Hungarian-speaking users.
Configuration extensions. Development tools.	The ConfigurationExtensionsManager.ExecuteBackgroundJobWithoutExtensions() method is implemented. It runs a background job without extensions (configuration extensions available in the database are not applied in the background job session). For all metadata objects, the ChangedByConfigurationExtensions() method is implemented. It defines whether a configuration object is available in the current session.	This feature was not provided.	Simplified 1C:Enterprise script-based operations with configuration extensions.
DBMS operations. System requirements.	Microsoft SQL Server 2016 DBMS is now supported (including its Linux version).	Microsoft SQL Server 2016 DBMS was not supported.	Microsoft SQL Server 2016 DBMS is now supported.
Client application. System requirements.	A 64-bit client application for Windows is implemented. It includes the thin client (also available as a standalone distribution kit), the thick client, and Designer. The current client application status is beta. When you start a client application, the 32-bit version has priority because most of the add-ins are not yet available for the 64-bit version of 1C:Enteprise platform. Automatic client application updates also install 32-bit versions (provided that the 32-bit versions are available in the distribution kit directories). The 64-bit client installer is similar to the 32-bit client installer. We recommend that you do not install both 64-bit 1C:Enterprise server and applications from the full 64-bit 1C:Enterprise distribution kit on a single computer.	Only 32-bit versions of Windows client applications (including Designer) were available. 1C:Enterprise server was the only 1C:Enterprise component that had a 64-bit version.	Support of 64-bit Windows versions is implemented. Issues caused by insufficient memory for operations with large configurations (such as comparing and merging configurations) are eliminated.
Accounting registers. Database operations.	Before you start infobase verification and repair in the interactive mode, 1C:Enterprise displays a recommendation to create an infobase backup. Infobase restructuring and infobase verification and repair now include a check for the following: the table of accounting register extra dimension values contains records that do not have matching records in the main accounting register table (lost extra dimensions). During the repair, lost extra dimensions are deleted from the table of accounting register extra dimension values if the following conditions are met: The Verify and repair mode is selected. The Check logical infobase integrity option is selected. During the restructuring, the check is performed if any of the following entities change: The totals splitting flag The set of recorders The maximum number of extra dimensions The type of characteristic value in a chart of characteristic types that is used to specify extra dimensions for a chart of accounts. If lost extra dimensions are found during the restructuring, the restructuring is stopped and 1C:Enterprise displays a recommendation to perform infobase verification and repair. The check for lost extra dimensions during the infobase verification and repair is implemented. If extra dimensions are lost, it is recommended that you restore the infobase from a backup. The check is performed if the following conditions are met: The Verify and repair mode is selected. The following options are selected: Check logical infobase integrity, Check referential infobase integrity, Recalculate totals, and Restructure infobase tables.	The diagnostics of extra dimension inconsistencies was insufficient.	Diagnostics and repair of accounting register logical integrity issues that can result in data losses is implemented.
Administration tools.	The rules for generation of application and shortcut names displayed in the Windows Start menu are modified. The new name template is Application name (full version number). In Windows version 8 or later, the 1C:Enterprise 8 folder contains all installed applications (and shortcuts) with their version numbers. In Windows version 7 or earlier, the 1C:Enterprise 8 folder contains folders for each version number. Each of these folders contains all installed applications (and shortcuts) for a specific version, with their names generated according to the abovementioned rule.	The names of installed applications (and shortcuts) did not include the full system version number.	Simplified navigation in the Start menu on Windows version 8 and later. Application names now contain full version numbers.
Accounting registers. Dumping configurations to files/Restoring configurations from files.	The option to create an accounting register record that only affects the opening balance of a single period and does not affect the closing balance of the previous period is implemented. The implementation is based on the new "period adjustment" concept. A period adjustment is a number that represents the number of time intervals within a single second. The maximum number of intervals is 1000. If a record belongs to any period adjustment interval, the record does not affect the closing balance of a period but affects the opening balance of the next period and does not affect the turnovers of both periods. A register record that belongs to a period adjustment interval only affects turnovers if the turnover period includes the entire point in time of that register record. Now the point in time can inlcude not only the date, time, and recorder, but also a period adjustment. For the accounting register configuration object, the Period adjustment length property is implemented. If this property is set to 0, the register does not use period adjustments. The PeriodAdjustment property is implemented for AccountingRegisterRecord and AccountingRegisterSelection objects. This property is also available in the main accounting register table, the extra dimensions table, and the virtual table of register records with extra dimensions. The PeriodAdjustment value is implemented for the Periodicity parameter of the following virtual tables of accounting registers: Turnovers, DrCrTurnovers, and BalanceAndTurnovers. The PointInTimeWithPeriodAdjustment object is implemented. The XML dump format version is changed. If a configuration contains at least one accounting register with period adjustment enabled (the value of the Period adjustment length property is not 0), this makes the infobase incompatible with the earlier 1C:Enterprise versions, including earlier builds of 1C:Enterprise 8.3.9. When you attempt to open such an infobase with 1C:Enterprise version 8.3.9.2015 or earlier, 1C:Enterprise displays the message Configuration structure is incompatible with the current program version and shuts down. To restore the compatibility, you have to delete all of the accounting registers with period adjustment, or set their Period adjustment length to 0.	This feature was not provided. The option to create an accounting register record that only affected the opening balance of a single period and did not affect the closing balance of the previous period was not available.	You can implement certain operations related to opening balance corrections at period boundaries.
DBMS operations. System requirements.	Support of Oracle Database version 11.2.0.4 (Windows) is implemented.	This Oracle Database version was not supported.	Extended list of supported Oracle Database versions.

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Client application.	All of the common report forms use the following help topic priorities: Report help Form help Report form help provided by the platform This change is not implemented in 8.3.8 compatibility mode.	Common report froms used the following help topic priorities: Form help Report help Report form help provided by the platform	Help topics are displayed in more logical order.
Interface. Client application.	For thin client running on Windows operating system, touch screen support is implemented. Support of scrolling with 2-finger gestures in all directions is implemented for all controls that have scroll bars. The effect of 1-finger gestures depends on control type: Horizontal gesture: Scrolling in spreadsheet documents, tables, or forms Selection in text documents, multiline text boxes, formatted documents, planner fields, and HTML document fields Selection or dragging in graphical and geographical schemas Vertical gesture: Selection or dragging in geographical schemаs Scrolling in other form controls that support vertical scrolling The tap detection area is expanded for the following controls: Check boxes in form tables Buttons that expand or collapse tree branches in form tables Buttons that move through hierarchical lists in form tables Hyperlinks in command bars Buttons with hidden borders Cells in form field extensions for period fields For graphical schemas, support of scaling using the scaling gesture is implemented. For tapping form buttons and command bar buttons, a visual effect is implemented.	The touch screen support was limited.	Improved 1C:Enterprise usability for touch monitors.
Spreadsheet documents.	In spreadsheet documents, if a search string can be converted to a number, 1C:Enterprise determines the number of digits in that number. Then it searches exactly for the specified number, without further simplifications or conversions. The search does not ignore strings with leading zeros. This change is not implemented in 8.3.8 compatibility mode.	In spreadsheet documents, for searches by number, 1C:Enterprise did not determine the number of digits in that number. Strings with leading zeros were not converted to numbers.	Better algorithm for searching spreadsheet documents for numeric values.
Web client.	File system extension and cryptography extension are compatible with Mozilla Firefox version 51 and later. The extensions are automatically updated first time they are accessed (after the platform update).	File system extension and cryptography extension were not compatible with Mozilla Firefox version 51 and later.	Eliminated unexpected system behavior.

Table of contents

Functionality	After	Before	Result of changes
Development tools.	The performance of the following Designer operations is improved: Module check Configuration check	The performance of module and configuration checks was insufficient.	Improved usability for developers of large applied solutions.
1C:Enterprise script.	The performance of 1C:Enterprise script execution is slightly improved in the thin and thick client applications.	The performance of 1C:Enterprise script execution in client applications was insufficient.	Improved performance of 1C:Enterprise script execution in the thin and thick client applications.
Common objects.	The performance of updating value table column cells in columns that are not a part of any value table index is improved.	Redundant rebuilding of value table indexes was performed in the event of updating a cell in a column that was not a part of any value table index.	Improved performance for bulk value changes in columns that are not part of any value table index.
Data exchange. Server clusters.	The following operations that are performed during the creation of an initial infobase image in client/server mode are optimized: reading accumulation register and information register record sets, and reading calculation register record sets that do not feature action period. The time required to create an initial image of a client/server infobase is significantly reduced.	The performance of creation of an initial image in a client/server infobase was insufficient.	Improved performance of infobase preparation for new distributed infobase nodes.
Command interface. Development tools.	Improved performance of opening the configuration command interface editor form.	The performance of opening the configuration command interface editor form was insufficient.	Better usability of editing the configuration command inerface.
DBMS operations. Server clusters.	The algorithm of 1C:Enteprise server cluster operations with PostgreSQL DBMS is modified. This reduces PostgreSQL memory usage. If a 1C:Enterprise server cluster connection to PostgreSQL DBMS is idle for 30 minutes, it is released.	The algorithm of 1C:Enteprise server cluster operations with PostgreSQL DBMS caused increased PostgreSQL memory usage. 1C:Enterprise server cluster did not release idle connections to PostgreSQL DBMS.	Reduced PostgreSQL memory usage for operations with 1C:Enterprise server cluster.
Development tools.	Infobase configuration update is optimized. Configuration comparison in scenarios where objects are mapped by their names is optimized.	The performance of infobase configuration update was insufficient.	Improved performance of configuration updates.
DBMS operations.	Temporary table operations are optimized in scenarios that use PostgreSQL DBMS.	The performance of temporary table operations in scenarios that used PostgreSQL DBMS was insufficient.	Improved performance in multiuser mode in scenarios that use PostgreSQL.
Web services and HTTP services.	Sending large files (tens and hundreds of megabytes) over HTTP services is optimized.	The performance of sending large files (tens and hundreds of megabytes) over HTTP services was insufficient.	Improved performance of sending large files over HTTP services.
DBMS operations.	Optimized temporary table operations in scenarios that use Microsoft SQL Server and include high load on 1C:Enterprise and active usage of temporary tables. Pauses during the closing of DBMS connections are eliminated.	The performance of temporary table operations in scenarios that used Microsoft SQL Server and included high load on 1C:Enterprise and active usage of temporary tables was insufficient.	Improved performance in multiuser mode in scenarios that use Microsoft SQL Server.
DBMS operations.	In the file mode, queries are optimized for scenarios where an applied solution has separators but actually contains a single data area. To apply this optimization to an existing infobase, perform infobase verification and repair with the Reindex infobase tables check box selected. Once the restructuring is completed, the optimization is applied to all restructured objects.	In the file mode, in scenarios where an applied solution had separators but actually contained a single data area, the performance of queries was insufficient.	Improved file infobase performance in scenarios where an applied solution has separators but actually contains a single data area.
Development tools. Command interface.	Reduced time of displaying changes in configuration objects that affect the configuration command interface. Such changes cause the immediate update of the active form editor, while other form editors are updated when they are activated.	Changes in configuration objects that affected the configuration command interface caused the update of all open form editors.	Improved Designer performance during the update of properties of configuration objects that affect the command interface.
Formatted documents.	The performance of formatted documents is improved.	The performance of formatted documents was insufficient.	Improved performance of operations with large texts.
Managed locks.	Absorption of managed locks is implemented (when two managed locks are applied at the same time, only one will take effect). A lock that does not have all lock areas specified absorbs a lock that has more lock areas specified, provided that the values in their common areas match. If lock escalation causes a conflict with other locks, the escalation is not performed and an attempt to set the requested lock is made instead. This can lead to a total of more than 100 000 locks in a single area. In scenarios where a single transaction uses a large number of managed locks with slight differences (for example, a single dimension varies), it is recommended that you set a single managed lock where the value of that dimension is not set.	Lock absorption was not performed. If lock escalation caused a conflict with other locks, the transaction that attempted to escalate the lock was canceled.	Reduced number of locks and reduced amount of memory used by the cluster manager. Improved system reliability in scenarios with large numbers of simultaneous locks.
DBMS operations. Calculation registers.	When deleting records belonging to the actual action period, recording of register sets of calculation registers that support actual action period is performed within several queries, which reduces the chance of escalating the lock to the table level. This does not increase the record set execution time.	When deleting records belonging to the actual action period, recording of register sets of calculation registers that supported actual action period was performed within a single query, which could cause lock escalation to the table level.	Reduced chance of table lock, which gives more options for performing parallel operations.
Calculation registers.	The index of the actual action period table of a calculation register is complemented by the start date and end date fields, and the index is now clustered. This reduces the chance of lock escalation to the table level when writing record sets of calculation registers that support action period. For the chart of calculation types table that stores serial numbers of calculation type displacements, a nonunique index by displacement number is implemented. As a result, simultaneous editing of a single chart of calculation types in different data areas of a separated infobase never requires waiting for lock releases. To apply this optimization to existing infobases, perform the infobase verification and repair operation with the Restructure infobase tables option selected.	The index of the actual action period table of a calculation register did not include the start date and end date fields, and the index was not clustered. For the chart of calculation types table that stored serial numbers of calculation type displacements, a nonunique index by displacement number was not available.	Improved calculation register performance in large and separated databases. In large databases and especially separated databases, reduced number of table-level locks for the following tables: actual action period table of a calculation register and table that stores serial numbers of calculation type displacements.
Managed forms. Development tools.	The first opening of managed form editor in Designer is faster.	The first opening of managed form editor in Designer took significant time.	Reduced waiting time in managed form development.
Information registers.	Faster writing of information register record sets that have slice first or slice last options enabled. Faster execution of SliceFirst() and SliceLast() information register manager methods.	The performance of writing information register record sets that had slice first or slice last options enabled and the performance of SliceFirst() and SliceLast() information register manager methods was insufficient.	Improved performance of information registers with slice first or slice last options enabled.
Interface. Managed forms. Functional options.	The performance of RefreshInterface(), SetInterfaceFunctionalOptionParameters(), and SetFormFunctionalOptionParameters() methods is improved. Delays introduced by these methods in applications with multiple simultaneous user connections are eliminated.	The performance of RefreshInterface(), SetInterfaceFunctionalOptionParameters(), and SetFormFunctionalOptionParameters() methods was insufficient. The performance was reduced in applications that called these methods in scenarios with multiple simultaneous user connections.	Streamlined operations in applications that use functional options.
Managed forms. Mobile applications.	In the mobile platform, the performance of operations with large spreadsheet documents is improved.	In the mobile platform, the performance of operations with large spreadsheet documents was insufficient.	Improved performance of operations with large spreadsheet documents on mobile devices.
DBMS operations.	The performance degradation of Microsoft SQL Server 2014 caused by interaction between 1C:Enterprise server and Microsoft SQL Server 2014 is eliminated. 1C:Enterprise server now forces setting TRACE FLAG 4199 for each Microsoft SQL Server 2014 connection. To be able to set the flag, the account that the 1C:Enterprise server uses to connect to the DMBS must have administrator rights. If TRACE FLAG 4199 is set for the entire database, 1C:Enterprise server does not set it for each connection.	In some scenarions interaction between 1C:Enterprise server and Microsoft SQL Server 2014 reduced Microsoft SQL Server 2014 performance. 1C:Enteprise server did not force setting TRACE FLAG 4199 and did not check whether this flag was set for the entire database.	In some scenarions the performance of operations involving Microsoft SQL Server 2014 is improved.
DBMS operations.	For PostgreSQL, reduced the overhead expenses for processing temporary tables.	For PostgreSQL, processing temporary tables took a lot of time.	For PostgreSQL, improved the performance of transactions that actively use temporary tables.

Changes that affect system behavior

Functionality	After	Before	Result of changes
Internet-enabled functionality.	The option to choose FTPES for communication with FTP servers is implemented. For the constructor of the FTPConnection object, the SecureConnectionLevel property is implemented. This property defines the secure connection requirements to the FTP server. If the parameters of the FTPConnection constructor do not have the required types, an exception is thrown. This change is not implemented in 8.3.8 compatibility mode.	All FTP server operations were performed over FTPS. If the parameters of the FTPConnection constructor did not have the required types, an attempt to convert them to the required types was performed.	Extended secure connection management capabilities for FTP server operations.
Managed forms.	Clicking a managed form table cell that displays a picture with a hyperlink (the CellHyperlink property is set to True) calls the Selection event of the form table. This change is not implemented in 8.3.8 compatibility mode.	Clicking a managed form table cell that displayed a picture with a hyperlink (the CellHyperlink property was set to True) did not call the Selection event of the form table.	Eliminated unexpected system behavior. Unified system behavior for different object types that can be displayed in a form table.
Print tools.	The option to use duplex printing settings of the printer is implemented. The system enumeration value DuplexPrintingType.UsePrinterSettings is implemented. The DuplexPrinting property of spreadsheet documents, graphical schemas, representable document batches, and text documents has the following default value: DoNotUse (for 8.3.8 compatibility mode) UsePrinterSettings (when no compatibility mode is set and for 8.2.16 or earlier compatibility mode) Printing spreadsheet documents and representable document batches from the web client to a PDF document and saving a spreadsheet document to a PDF document transfers the DuplexPrinting and PagePlacementAlternation property values to the corresponding PDF document properties. If the PDF viewer software supports these properties, they are applied when the document is printed. If the PDF viewer software does not support these properties, use the print software settings or printer settings for duplex printing.	Duplex printing settings of the printer were ignored during the printing of spreadsheet documents, graphical schemas, representable document batches, and text documents.	Improved document printing options.
Data composition system.	When the data composition schema wizard is opened, data set fields with duplicate names are deleted, leaving only the first one.	When the data composition schema wizard was opened, duplicate data set fields were not deleted.	Eliminated unexpected system behavior.
Technological log.	Debugger exceptions that are thrown during the startup of the debug server (dbgs) are now saved to the technological log. The <EXCP> event is used for that logging.	Debugger exceptions that are thrown during the startup of the debug server (dbgs) were not logged.	Better error diagnostics for the startup of the debug server (dbgs).
Predefined data. Development tools.	If the result of merging configurations would include predefined data items with duplicate names, a numeric suffix is added to the item taken from the source with lesser priority.	The result of merging configurations could include predefined data items with duplicate names.	Eliminated unexpected system behavior.
1C:Enterprise script.	For the StrTemplate() method, the syntax option with a substitution token %(N) is implemented. You can specify a substitution number in parentheses after the percent. With this syntax you can specify a number right after the substitution token in a template string.	Eliminated unexpected system behavior.	You can create template strings where the substitution token is followed by a numeric character.
Development tools.	During the configuration check and refactoring, the search for calls of deprecated synchronous methods does not check the modules that cannot be executed at the client application side. In other modules the search ignores client script parts marked with preprocessor insrtructions and compilation directives.	During the configuration check and refactoring, the search for calls of deprecated synchronous methods ignored the execution context of modules and methods.	Reduced number of false warnings while searching for calls of deprecated synchronous methods during the configuration check and refactoring.
Web client, web service, and HTTP service publishing tools.	If an attempt of publishing to a web server using an account that does not have administrative rights is made: Designer displays a warning dialog box, providing the options to continue the operation or cancel it. The execution of the webinst utility is not interrupted, but it displays a warning.	If an attempt of publishing to a web server using an account that does not have administrative rights was made, no diagnostics was performed.	Better diagnostics for publishing to the web sever.
XML and XDTO support.	When an XDTO package is deleted, 1C:Enterprise checks whether the package is used in web services. If web services that use the package are found, a warning with a web service list is displayed.	When an XDTO package was deleted, 1C:Enterprise did not check whether the package was used in web services,	Eliminated situations where a web service stopped working due to deletion of an XDTO package.
Managed forms.	The option to set the focus to command bars that do not contain form item commands of contain commands from multiple sources using Tab or Shift+Tab is implemented. In the calendar used to enter a date in a text box, selection of the current date by clicking the Today hyperlink is implemented. In the thin and thick clients, in the calendar used to enter a date in a text box, selecting a date that does not belong to the current month adds this date to the text box.	The option to set the focus to command bars that did not contain form item commands of contained commands from multiple sources using Tab or Shift+Tab was not available. In the calendar used to enter a date in a text box, clicking the Today hyperlink set the focus to the current day of the month in the month currently selected in the calendar. In the thin and thick clients, selecting a date that did not belong to the current month activated the selected month in the calendar field. In the web client, this added the selected date to the text box.	Eliminated unexpected user interface behavior in some scenarios. Unified system behavior in different client applications.
Configuration repositories.	When you store an object to a configuration repository, the repository server checks the integrity of object data. In the event of integrity violation an exception is generated and the object is not stored.	The configuration repository server did not check the integrity of stored object data.	Reduced chance of storing corrupted configuration object data to a repository.
Database configuration update.	During a dynamic update, deletion of configuration objects that do not prevent the update and are absent from the new configuration is handled correctly. These objects are only deleted during the exclusive update. This change is not implemented in 8.3.8 compatibility mode.	Deletion of configuration objects that did not prevent the update and were absent from the new configuration was performed immediately, during a dynamic update.	Reduced number of issues that might arise during a dynamic update if some objects were deleted from the new configuration.
Web services and HTTP services. Internet-enabled functionality.	This change is rolled back. The URI string encoding (either with the EncodeString() function or with internal platform algorithms) replaces the percent sign (%) with %25. This change is not implemented in 8.3.8 compatibility mode.	The URI string encoding (either with the EncodeString() function or with internal platform algorithms) did not replace the percent sign (%) with %25. It was left "as is."	RFC 3986 recommendations for URI string encoding are implemented.
Localization.	In the number-to-words conversion algorithm for Azerbaijani language, a typo is corrected. This affects the numbers beginning with "two" and "twenty."	The number-to-words conversion algorithm for Azerbaijani language had a typo. This affected the numbers beginning with "two" and "twenty."	Eliminated unexpected system behavior.
Development tools.	In the debugger, when a collection (for example, a value table) is being viewed in a new window, its columns are no longer sorted in alphabetical order.	In the debugger, when a collection (for example, a value table) was being viewed in a new window, its columns were sorted in alphabetical order. This behavior occurred in 1C:Enterprise versions 8.3.7 and 8.3.8.	Eliminated unexpected system behavior.
Common attributes / Data separation. Configuration extensions.	The data deleted by EraseInfoBaseData() method now includes configuration extensions for the entire infobase or for a specific area, depending on the call parameters.	The EraseInfoBaseData() method did not delete configuration extensions.	The EraseInfoBaseData() method clears more data.
Dynamic lists. Server clusters.	In a dynamic list search box, if you enter a value that can be interpreted as a date with year specified as a 1-digit or 2-digit number, the year is converted to this century year. This prevents the error that occurs when you use Microsoft SQL Server with a zero date offset.	In a dynamic list search box, if you entered a value that could be interpreted as a date with year specified as a 1-digit or 2-digit number, the year was not converted to this century year. In 1C:Enterprise that used Microsoft SQL Server with a zero date offset, this search scenario returned an error.	The dynamic list error that occurred if a date was entered in a search box in 1C:Enterprise that used Microsoft SQL Server with a zero date offset is eliminated.
Spreadsheet documents.	When a spreadsheet document is exported to Microsoft Excel 97 or later format, if it contains cells with multiline text that is aligned centrally and does not fit a cell, the cell is merged. It is horizontal merging that spreads equally to both sides of the cell so that the entire text fits the new merged cell. The columns overlapped by the left and right borders of the merged cell are split into two columns. The resulting document in Microsoft Excel format better matches the original document. This change is not implemented in 8.3.8 compatibility mode.	When a spreadsheet document was exported to Microsoft Excel 97 or later format, if it contained cells with multiline text that were aligned centrally and did not fit the cell, such cells were not merged.	When a spreadsheet document is exported to Microsoft Excel format, the resulting document better matches the original document.
Development tools.	If programmatic access to Microsoft Internet Explorer browser clipboard is disabled by the Allow Programmatic clipboard access security option, an attempt to use the Copy command of the Syntax Assistant context menu results in a notification that the clipboard is not available, which includes a workaround recommendation (use a keyboard shortcut).	If the Allow Programmatic clipboard access security option in Microsoft Internet Explorer was disabled, the Copy command of the Syntax Assistant context menu did not work.	Better diagnostics of unexpected system behavior.
Managed forms.	For groups with titles that display data, the support of Format property in both interface modes (Taxi and Version 8.2) is implemented. This change is not implemented in 8.3.8 compatibility mode.	For groups with titles that display data, the Format property was not supported in some interface modes. This property had some implementation differences between the thin and web clients.	Uniform behavior of the thin and web clients. Eliminated unexpected system behavior.
Development tools.	The option to update configurations that include constant forms using update (.cfu) files is restored. The option to update configurations using update (.cfu) files is implemented for scenarios where only the Use always flag in constant forms was changed.	In some scenarios, if the Use always flag in a constant form was changed in a new configuration, this caused configuration update issues.	Eliminated the issues that appeared during the update of configurations that included constant forms with update (.cfu) files.
Development tools.	If the size of the file that stores new and changed objects, which is created during the generation of a .cfu update file, exceeds 2 GB, the update file is generated in the new format. If you are creating the update file manually, you get a notification about the new format in a dialog box. If you are creating the update file in batch mode, the notificaton is added to the service message file (/out comand-line option). Update files that have new format can only be used in 1C:Enterprise versions 8.3.9.2033 and later. If you attempt to use an update file in an earlier 1C:Enterprise version, you get a message about incorrect data storage format. You can use 1C:Enterprise versions 8.3.9.2033 and later to apply any updates, regardless of their file format.	If the size of the file that stored new and changed objects, which was created during the generation of a .cfu update file, exceeded 2 GB, the update file could not be generated.	1C:Enteprise supports very large update files (.cfu).
Print tools.	The RepresentableDocumentBatch.Print() method splits batches into multiple jobs (in all application types except for the web client). It uses the document batch properties, such as the printer, page orientation, or duplex printing, to generate the jobs (and split document batches).	The RepresentableDocumentBatch.Print() method printed the entire document batch as a single job (in all application types except for the web client). This might cause issues when the documents were to be printed on different printers or with different print settings because jobs always apply the same settings to all its documents.	Eliminated document batch printing issues caused by differences of document print settings (such as the printer, page orientation, or duplex printing).
Operating system.	1C:Enterprise behavior changed in scenarios that involve switching the computer to sleep mode. 1C:Enterprise prevents switching to the sleep mode if: It uses a hardware protection key It runs in file mode and its database file is located on a network resource	1C:Enterprise prevented switching to sleep mode if: It used a hardware protection key It ran in file mode and its database file was located on a network resource It ran in client/server mode.	Power saving schemes applied when 1C:Enterprise runs are changed.
Infobase operations.	Dumping an infobase to a .dt file is not interrupted if any issues related to the internal infobase structure are encountered.	Dumping an infobase to a .dt file was interrupted if any issues related to the internal infobase structure were encountered.	Minor infobase data structure issues, which do not impact 1C:Enterprise functionality, no longer block dumping infobases to files.
JSON support.	Improved reliability of JSON operations.	JSON operations might cause unexpected shutdown.	Eliminated unexpected system behavior.
Server clusters.	When the Secure connection cluster property value is changed, this takes effect after restarting the cluster processes. It is recommended that you restart the cluster after changing the Secure connection property value.	An attempt to change the Secure connection cluster property value generated an error and the value was not changed.	Eliminated unexpected system behavior.

Table of contents

Changes that require modification of configuration and administrative settings

Table of contents

Object	The old name	The new name
The StartPageForms object is renamed. The former name is supported for compatibility purposes.	StartPageForms.	HomePageForms.
The StartPageSettings object is renamed. The former name is supported for compatibility purposes.	StartPageSettings.	HomePageSettings.
The StartPageWorkingArea object is renamed. The former name is supported for compatibility purposes.	StartPageWorkingArea.	HomePageWorkingArea.
The ClientApplicationWindow.StartPage property is renamed. The former name is supported for compatibility purposes.	StartPage.	HomePage.
The TestedClientApplicationWindow.StartPage property is implemented. The former name is supported for compatibility purposes.	StartPage.	HomePage.
Name of the system enumeration that lists item and title alignment options.	ItemsAndTitlesAlign.	ItemsAndTitlesAlignVariant.
The value of the Purpose column of the ExtensionInfo value table returned by GetDBStorageStructureInfo() method. This change is not implemented in 8.3.8 compatibility mode.	Main.	ConfigurationExtensionsInformation.
The value of the Purpose column of the ODataSettings value table returned by GetDBStorageStructureInfo() method. This change is not implemented in 8.3.8 compatibility mode.	Main.	StandardODataInterfaceOptions

Functionality	After	Before	Result of changes
File operations. Multimedia support.	On the mobile platform, the FileDialog object is available. For the dialog limitations on specific mobile operating systems, see the Syntax Assistant. For mobile devices, the option to select files interactively is implemented for the following methods: GetFile(), GetFiles(), PutFile(), and PutFiles(). The File.GetMobileDeviceLibraryFilePresentation() method is implemented. It returns the file presentation for displaying on the mobile device. You can use mobile device library file names (with the content: schema) in constructors of the following objects: File, BinaryData, Picture, and MobileDeviceApplicationRun. You can use them as parameters for the following global context methods: RunApp(), GotoURL(), FileCopy(), MoveFile(), DeleteFiles(), and FindFiles(). On iOS and Android, you can also use them as parameters for the following methods of the MultimediaTools object: PlayAudio() and GetAudioDuration(). The MobileDeviceLibraryDir() global context method is implemented. It returns a path to a mobile device library (a picture, audio, or video library).	The FileDialog object was not available on the mobile platform.	Interactive file operations are implemented for the mobile platform.
Mobile device-specific features.	For Android operating system, the option to process incoming call data using 1C:Enterprise script tools is implemented. For the TelephonyTools object, the CallsHandlingSupported(), AttachCallsHandler(), and DetachCallsHandler() methods are implemented. The TelephonyTools.CallsHandlingSupported() method returns True on Android only.	This feature was not provided on the mobile platform.	The option to process incoming call data in mobile applications using 1C:Enterprise script tools is now available on Android operating system.
Mobile device-specific features.	Extended multimedia options for the mobile platform: The option to play a sound or vibration alert is implemented. The MultimediaTools.PlaySoundAlert() method is implemented. The option to play audio data of various types is implemented. Playing is performed using the default application provided with the operating system. The option to stop playing is implemented. For the MultimediaTools object, the PlayAudio(), StopAudioPlayback(), and GetAudioDuration() methods are implemented. The option to read text using the screen reader provided with the operating system is implemented. The option to stop reading is implemented. For the MultimediaTools object, the PlayText(), StopTextPlayback(), and TextPlaybackSupported() methods are implemented.	These features were not provided on the mobile platform.	Extended multimedia support.
Data composition system.	On the mobile platform, the support of data composition system is implemented, except for the objects that allow user interaction. Therefore, all data composition system operations are performed using 1C:Enterprise script tools. In Designer, the option to create data composition schemas for reports that run in mobile applications is implemented.	This feature was not provided on the mobile platform.	Extended report development capabilities on the mobile platform.
Add-ins.	On the mobile platform, add-in support is implemented. It uses the NativeAPI technology. You can export a mobile configuration from Designer to 1cema.zip format, which includes the add-ins used in the configuration. When you connect a mobile device using Android Debug Bridge (ADB), add-ins are copied to the device. In the mobile application builder, the option to build applications with add-ins is implemented. Add-in development technology documentation and examples are updated (read more).	The mobile platform did not support this feature.	You have the option to expand mobile platform functionality when its standard features do not cover your needs.
Managed forms.	The following features are implemented for the mobile platform: Display a command bar button as a hyperlink. Set horizontal picture alignment on a managed form button. Set gaps between command bar buttons. Set command bar button shapes (except for buttons located in popups). Set the view of managed form buttons. For text boxes, support of CreateButton and ChoiceButtonRepresentation properties is implemented. For text boxes, support of EditTextChange and Creating events is implemented. Support of BorderColor, BackColor, TitleTextColor, and TitleFont properties is implemented for buttons of CommandBarButton and CommandBarHyperlink type and for form group extensions for popups.	This feature was not provided on the mobile platform.	The set of features available on the mobile platform is closer to the set of features available on the desktop platform.
Internet-enabled functionality.	The option to check the availability of data transfer network in mobile applications is implemented. The InternetConnectionInformation global context property is implemented.	This feature was not provided on the mobile platform.	The option to analyze available data transfer methods and choose the optimal strategy for operations with external data is implemented.
JSON support.	The mobile platform now supports JSON operations. Serialization of XDTO documents to JSON objects is not supported.	This feature was not provided on the mobile platform.	Simplified integration with applications (including web applications) that use JSON data format. The option to store data in JSON format (for example, instead of XML format) is implemented.
Internet-enabled functionality.	The behavior of the OpenSSLSecureConnection object is unified with that of the PC platform. If the CertificationAuthorityCertificates parameter of the object constructor is not specified, the certificate is not checked. If the CertificationAuthorityCertificates parameter of the object constructor is specified, the check uses the root certificates installed on the device. The OSCertificationAuthorityCertificates object is now available on the mobile platform. This change is not implemented in 8.3.8 compatibility mode.	The certificate check always used the root certificates installed on the mobile device. The CertificationAuthorityCertificates parameter of the OpenSSLSecureConnection object constructor was ignored.	Unified behavior of the mobile platform and the PC platform. Eliminated unexpected system behavior.
Mobile device-specific features.	The option to check the availability of operations with global contact keys, calendars, and calendar events on different mobile operating systems is implemented. For the ContactManager object, the GlobalContactsKeySupported() method is implemented. For the CalendarsManager object, the GlobalCalendarsKeysSupported() and GlobalEventsKeysSupported() methods are implemented. The GlobalContactKey parameter of the AccountContactData object constructor is no longer supported. The values of properties that describe global contact keys, calendars, and calendar events depend on the result of the function that checks the availability of global key operations. If global key operations are not supported, requests to these values return blank strings. Availability of LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects on the mobile application server is implemented.	The availability of global contact keys, events, and calendar events depended on the platform where a mobile application was running. Developers had no means to check whether operations with global keys from 1C:Enterprise script were supported. The LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects were not available on the mobile application server.	The mobile platform behavior is unified with the general behavior of applications that have features that are not available on some mobile devices or operating systems.
Predefined data.	In the mobile platform, support of the following global context methods is implemented: InitializePredefinedData(), SetInfoBasePredefinedDataUpdate(), and GetInfoBasePredefinedData().	This feature was not provided on the mobile platform.	Unified desktop and mobile platform features related to predefined data.
Managed forms.	New managed form interface features in the mobile platform. Now you can: Create collapsible groups. Manage Pages form item visibility if it is displayed either as the current page or as tabs. In this scenario you can use 1C:Enterprise script to switch between the current page and the tabs. The CurrentPagesState property is implemented. Manage visibility of open and clear buttons in text boxes. The AutoShowClearButton and AutoShowOpenButton properties are implemented for managed form text boxes. Manage multiline text box height. The HeightControlVariant property is implemented for managed form text boxes. Switch form items to edit mode. The ManagedForm.BeginEditingItem() method is implemented. Manage some service options for text boxes, such as: Auto correction. The AutoCorrectionOnTextInput property is implemented. Spell checking. The SpellCheckingOnTextInput property is implemented. Auto capitalization. The AutoCapitalizationOnTextInput property is implemented. Manage the keybord type used to input data. The SpecialTextInputMode property is implemented. Change the label of the return keyboard button. The OnScreenKeyboardReturnKeyText property is implemented. Manage form table height if data displayed in the table is not a dynamic list. The HeightControlVariant property is implemented. Manage the search string position. You can specify whether the search string is displayed in the form header or appears after a user swipes down a table title. Command bar commands are no longer included in the More menu. Table row context menu commands can be moved to the More menu if they do not fit the screen. Fixed spreadsheet document areas are displayed in a new way.	These features were not provided. Command bar commands were duplicated as items of the More menu. 1C:Enterprise attempted to display all table row context menu commands on the screen. Fixed spreadsheet document areas were displayed differently.	The mobile platform interface is closer to the modern interface development standards.
Mobile device-specific features.	The implementation of the Beep() method is now uniform with the implementation of the MultimediaTools.PlaySoundAlert(SoundAlert.Default).	The Beep() method did not perform any actions.	You can use the Beep() method to play the default sound alert of a mobile device.
Administration tools.	For mobile applications, the following features are implemented: Infobase verification and repair. Infobase backup. The option to run an automated backup before the application update, so that you can restore the infobase if any issues occur during the update. This option is enabled by default. The option to schedule automated infobase backups is implemented. The backups are stored to the mobile device storage. These options are available in the application settings dialog box (the Administration button in this dialog box).	This feature was not provided.	Additional options for mobile application administrators.
Mobile device-specific features.	The 1C:Enterprise mobile platform does not support Apple iAd any more as the service is officially shut down. Google AdMob advertisement service is supported for both iOS and Android devices. In Mobile application builder, you can specify that your application uses ads, and the builder picks the appropriate mobile platform for building the application based on the option that you select. You do not have to modify your iOS applications that support both services but the applications that support only Apple iAd require modification.	The 1C:Enterprise mobile platform supported Apple iAd and Google AdMob.	The Apple iAd service, which is now obsolete, is not supported.
Mobile application builder.	Mobile application builder can create application builds for OS emulators.	Mobile application builder could not create application builds for OS emulators.	More options for iOS application developers.

Library updates

The cURL library is modified to eliminate vulnerabilities.
The libtiff library is updated to version 4.0.7.

Table of contents

Transition from the previous version to the version 8.3.9

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.9.
Some features that are added in version 8.3.9 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.
In the file mode, queries are optimized for scenarios where an applied solution has separators but actually contains a single data area.
To apply this optimization to an existing infobase, perform infobase verification and repair with the Reindex infobase tables check box selected.
Once the restructuring is completed, the optimization is applied to all restructured objects.
The index of the actual action period table of a calculation register is complemented by the start date and end date fields, and the index is now clustered. This reduces the chance of lock escalation to the table level when writing record sets of calculation registers that support action period.
For the chart of calculation types table that stores serial numbers of calculation type displacements, a nonunique index by displacement number is implemented. As a result, simultaneous editing of a single chart of calculation types in different data areas of a separated infobase never requires waiting for lock releases.
To apply this optimization to existing infobases, perform the infobase verification and repair operation with the Restructure infobase tables option selected.
After migration to mobile 1C:Enterprise platform version 8.3.9.67 or later, when you first start an application, 1C:Enterprise performs infobase verification and repair with Check logical infobase integrity and Recalculate totals check boxes selected. If this operation takes a long time to complete, it is recommended that you cancel it on the mobile device, retrieve the backup that you created before the update from the mobile device, and use the cluster administration console (1cv8a) to verify and repair the infobase, just like you would do for desktop 1C:Enterprise platform. Then, on the mobile device, restore the repaired infobase from the file.

Table of contents

Version 8.3.8

Version 8.3.8 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
Library updates
Transition from the previous version to the version 8.3.8

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.3.7 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, and 8.3.6.	In version 8.3.8 you can run configurations created in version 8.3.7 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.8 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.7 for working with the infobase even after the transition to version 8.3.7. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Internet-enabled functionality.	Support of Linux trusted certificate directories (/etc/ssl/certs and /etc/pki/tls/certs) is implemented. The OSCertificationAuthorityCertificates object enabling cross-OS certificate operations is implemented. The LinuxCertificationAuthorityCertificates object caching certificate data on Linux operating system is implemented. It is recommended that you use the OSCertificationAuthorityCertificates object. The CertificationAuthorityCertificates parameter of OpenSSLSecureConnection object constructor accepts objects of OSCertificationAuthorityCertificates and LinuxCertificationAuthorityCertificates types. NSS certificates are no longer supported.	On Linux operating system, the platform used NSS certificate store.	On Linux operating system, in the thin client, the option to access infobases published on resources that require clent certificates is implemented.
Web client, web service, and HTTP service publishing tools. System requirements.	Support of Apache 2.4 is implemented for Windows and Linux. For the webinst utility, the -apache24 key is implemented.	This feature was not provided. Apache versions 2.0 and 2.2 were supported.	Extended list of supported web servers.
Automated testing.	The About 1C:Enterprise window and the title of the client application window indicate whether the client application is a test manager or a test client. The TestedApplication.SetFileDialogResult() method is implemented, it provides the result of an operation performed in the file selection dialog box. The resulting collection of the TestedApplication.GetChildObjects() method now inlcudes windows that contain text or spreadsheet documents. The TestedForm.ExecuteChoiceFromList() method is implemented, it selects a value from the list opened using the ManagedForm.ChooseFromList() method. The TestedForm.ExecuteChoiceFromMenu() method is implemented, it selects a value from the menu opened using the ManagedForm.ChooseFromMenu() method. For the TestedFormField object, the support of form field extension for a text document is implemented. For the TestedFormField object, the support of form field extension for a formatted document is implemented. For the TestedFormField object, the following methods are implemented: GetHTML() (returns the formatted document content) and InputHTML() (emulates entering text to the formatted document). The TestedFormField.WriteContentToFile() method is implemented, it writes the document file to the hard disk (same as the Save command). The method is available for spreadsheet document, text document, and formatted document extensions.	These features were not provided.	Extended automated testing capabilities.
Development tools.	The option to save and restore the settings in the configuration comparison and merging window is implemented. A check box that manages automatic automatic saving of the form settings is implemented. The module comparison and merging form is refactored. Now it includes a command bar with the editor commands. The filter settings now include the Show only properties that were changed twice option.	These features were not provided.	Improved usability for applied solution developers who often perform comparison and merging of configurations with custom settings.
Development tools.	The following operations are now available as command-line options for batch Designer startup mode: Compare configurations (/CompareCfg) Merge configurations (/MergeCfg) Lock objects in a configuration repository (/ConfigurationRepositoryLock). Release objects in a configuration repository(/ConfigurationRepositoryUnlock). Store modified objects to a configuration repository (/ConfigurationRepositoryCommit). Label a repository version (/ConfigurationRepositorySetLabel). The following parameters are implemented for /UpdateCfg command-line option of batch Designer startup: -DumpListOfTwiceChangedProperties. Generates the list of properties that were changed twice. -IncludeObjectsByUnresolvedRefs. If the settings include objects that are not in the list of objects to be merged and are not available in the main configuration, but these objects are referred from objects that are in the list, mark them for merging and attempt to continue the merging. -ClearUnresolvedRefs. Clear references to objects that are not in the list of objects to be merged. -Settings. Use the merge settings from the specified file. -force. Automatically resolve merge issues. This affects the platform behavior in the following cases: locked objects are found; properties that were changed twice and do not have the merge mode specified are found; or a warning about deletion of objects refered by objects that do not participate in the merging is issued. For /ConfigurationRepositoryUpdateCfg command-line option of batch Designer startup, the -objects parameter is implemented. This parameter specifies that the operation is performed for a specific set of configuration objects.	These features were not provided. The /ConfigurationRepositoryUpdateCfg command-line option of batch Designer startup was only applicable to the entire configuration.	Simplified automatic update of applied solutions.
Queries.	For the query debug, the following operations are inplemented: viewing the list of temporary tables, the structure of temporary tables, and the contents of temporary tables. The Query.ExecuteBatchWithIntermediateData() method is implemented. The TempTablesManager.Tables property is implemented.	This feature was not provided.	Extended applied solution debug capabilities, especially when debugging complex batch queries.
External data sources.	The ExternalDataSourceManager.TransactionActive() method is implemented. It determines whether an external data source has a transaction in progress.	This feature was not provided.	The option to determine whether an external data source has a transaction is progress is now available.
Web services and HTTP services.	Support of web services that support MTOM standard is implemented (read more).	This feature was not provided. Web services that supported MTOM standard were not supported.	Extended capabilities for 1C:Enterprise integration with third-party systems. Integration with web services that support optimized transfer of binary data is available, which reduces the network traffic and RAM usage.
OData interface.	The following improvements to the standard OData interface are implemented: Filter by composite type Lambda expressions New query options for filtering the received data: $skip. Skips several first records in the query result $inlinecount. Includes the size of the resulting selection to the query result $orderby. Sets the order of records in the query result $count. Returns the number or records in the query More functions can be used in queries: Functions that process string values Functions that process date and time values Function that checks whether a value has the specified type Functions that convert types	The standard OData interface provided more limited functionality	1C:Enterprise object presentations better conform to the OData standard requirements.
Configuration extensions. Development tools.	The ConfigurationExtension() method is implemented for configuration objects. It is used to determine the configuration extension where the object belongs. For ConfigurationExtensionsManager.Get() method, the ConfigExtensionSource parameter is implemented. If specifies which list of extensions is retrieved (database extensions only; extensions available in the current session; or extensions that were disabled or did not pass the check at the attachment stage).	This feature was not provided.	Simplified configuration extension operations in 1C:Enterprise script.
Configuration extensions.	The ConfigurationExtensionCompatibilityMode property of configuration extensions is implemented. This property is used to limit the extension functionality to ensure its compatibility with a specific version of 1C:Enterprise platform, while leaving the option to edit the extension using a later 1C:Enterprise platform version, which provides more features for configuration extensions.The option to create the following objects in configuration extensions is implemented: Common templates Common commands Common pictures Attributes, tabular sections, and attributes of adopted tabular sections for: Reports Data processors Forms, templates, and commands of adopted objects: Exchange plans Filter criteria Settings storage Catalogs Documents Document journals Enumerations Reports Data processors Accounting registers Accumulation registers Calculation registers Information registers Charts of characteristic types Charts of accounts Charts of calculation types Business processes Tasks External data sources: Tables Cubes Dimension tables In configuration extensions, the option to change the properties of adopted configuration objects, which describe both main and auxiliary forms, is implemented. For adopted reports, the option to change the Main data composition schema property is implemented. In configuration extensions, changing the Picture property of subsystems, command groups, commands, and common commands is available. In the module editor, the context help is only displayed for objects included in the current extension.	These features were not provided. In the module editor, the context help was displayed for both the original configuration and the extension.	Extended configuration extension capabilities.
Development tools. Dumping/loading configurations to files.	The option to export external reports and data processors to XML files is implemented. In Designer, the following File menu commands provide this option: Save, Save as, and Save copy. After the export, changing the object type (external report to external data processor or vice versa) is not available. The import is available using the Open command of the File menu. In the external report or data processor editor dialog box, the options to export the report or data processor to files and import it from files are implemented. The export and import commands are available on the Actions menu of the dialog box. The option to compare an external report or data processor with an external report or data processor stored in XML files is implemented. In the external report or data processor editor dialog box, the following Actions menu command provides this option: Compare and merge with external report or data processor. The option to export and import external reports or data processors to or from XML files using the command-line options of Designer batch mode is implemented. The /DumpExternalDataProcessorOrReportsToFiles and /LoadExternalDataProcessorOrReportsFromFiles keys are implemented. Export to both flat and hierarchical file structures is supported. The export is only available in export format version 2.0. The import format is determined automatically during the import.	These features were not provided. External reports and data processors could only be saved in binary format.	Extended capabilities for external report and data processor operations in scenarios that use external version control systems. The option to use external tools for creating and editing external reports and data processors is implemented.
Dynamic lists.	For dynamic lists, support of batch queries is implemented. The dynamic list query builder does not support editing batch queries. This change is not implemented in 8.3.7 repository compatibility mode.	Dynamic lists did not support batch queries.	Extended dynamic list capabilities.
Development tools.	In the Syntax Assistant, more information is added to the description of the HTTP service request handler method. This includes the parameter type and the return value type.	In the Syntax Assistant, some information was missing from the description of the HTTP service request handler method. It did not provide the parameter type and the return value type.	Easier developer access to critical information.
Data display. Managed forms.	For the StyleColors system enumeration, the following values are implemented: ButtonBorderColor (for form buttons and command bar buttons) TableHeaderBackColor (for table header background) TableHeaderTextColor (for table header text) TableFooterBackColor (for table footer background) TableFooterTextColor (for table footer text)	The following values of the StyleColors system enumeration were used to format form items: BorderColor (for form buttons and command bar buttons) ButtonBackColor (for table header background) ButtonTextColor (for table header text) ButtonBackColor (for table footer background) ButtonTextColor (for table footer text)	Extended style item usage options.
Data display. Managed forms.	The sizes of form buttons and command bar buttons are changed. This change is not implemented in 8.3.7 compatibility mode.	Form buttons and command bar buttons had different sizes.	Improved button layout.
Technological log.	For the <CALL> technological log event, the Usr property is implemented. It stores the name of the authenticated infobase user.	The Usr property of the <CALL> technological log event was not available,	The <CALL> technological log event is more informative now.
ZIP archive operations.	For the conf.cfg configuration file, the FileNamesEncodingInZipFile parameter is implemented. It specifies the file name encoding in 1C:Enterprise-generated ZIP archives. It can have one of the following values: UTF8 (UTF8 only) and OSEncodingWithUTF8 (both UTF8 and the operating system encoding). If the parameter value is UTF8, the ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, display file names with non-English characters inside the archives incorrectly. The built-in decompression program from OS X displays such file names correctly. If the parameter value is OSEncodingWithUTF8, the built-in decompression program from OS X displays file names with non-English characters incorrectly but other decompression programs display them correctly.	File names in 1C:Enterprise-generated ZIP archives were always stored in both UTF8 encoding and operating system encoding.	The option to specify encoding for the file names in 1C:Enterprise-generated ZIP archives is implemented.
DBMS operations. System requirements.	IBM DB2 11.1 DBMS is now supported.	IBM DB2 11.1 DBMS was not supported.	IBM DB2 11.1 DBMS is now supported.
Administration tools.	The administration console utility (1cv8a) is available. It includes some of verification and repair features that are available in Designer. You can use the utility to speed up certain operations: Verify and repair exchange plan node tables Verify and repair hash fields in infobase tables The utility is available for the following operating systems: Windows. Installed as a part of the Administration of 1C:Enterprise server component. Linux. Installed unconditionally as a part of the 1c_enterprise83-client-8.3.* package that depends on the 1c_enterprise83-server-8.3.* package of the same version. macOS. Installed unconditionally as a part of 1C:Enterprise.	This feature was not provided. Some of the utility features were available as part of the Verify and repair feature in Designer but they took much more time.	Now you do not have to start Designer to fix some of the infobase issues. This can save valuable time because the utility only processes objects with issues detected and performs a limited set of repair operations.
1C:Enterprise script. Configuration extensions. Administration tools.	Unsafe operation protection is implemented. When a potentially unsafe operation is attempted, 1C:Enterprise displays a warning that contains its description and why it might be unsafe. Potentially unsafe operations include: Loading an external report, an external data processor, or a configuration extension Loading or updating a configuration or an extension Attempting the following operations from an external report, an external data processor, or a configuration extension: Run an operating system command Manage users Load an add-in You have the option to allow or deny a potentially unsafe operation. In some scenarios you have to retry the operation after allowing it. When you load or update a configuration from a .cfu file, 1C:Enterprise adds the warning to existing Designer dialog boxes. The InfoBaseUser.UnsafeActionProtection property is implemented. The ConfigurationExtension.UnsafeActionProtection property is implemented. For the Connect() method of ExternalReports and ExternalDataProcessors objects, the UnsafeActionProtection parameter is implemented. In the configuration extension management dialog boxes (both in Designer and in the standard functions), the Unsafe operation protection check box is implemented. You can define the list of infobases where unsafe operation protection is disabled. For the conf.cfg file, the DisableUnsafeActionProtection parameter is implemented.	Unsafe operation protection was not available. Administrators could prohibit running external reports or data processors using security profiles.	Increased security when running potentially unsafe script.
1C:Enterprise script. Configuration extensions,. External reports and data processors. Administration tools.	In the thin and thick client applications, if unsafe operation protection triggers, once the unsafe operation is completed, the application execution continues as if it was not paused. If the user prohibits the unsafe operation, the platform generates an exception that can be caught using 1C:Enterprise script. The web client and server behavior is not changed.	In the thin and thick client applications, if unsafe operation protection triggered during the execution of the client script, the platform paused the script execution and prompted the user to allow or prohibit the operation. Regardless of the user choice, the script execution was not resumed and the user had to restart the operation.	Simplified application behavior in scenarios where unsafe operation protection triggers in a thin or thick client application.
System requirements.	1C:Enterprise now supports Microsoft Windows Server 2016 (x86-64).	1C:Enterprise did not support Microsoft Windows Server 2016 (x86-64).	The list of supported operating systems is extended.
System requirements.	Astra Linux Special Edition 1.5 is supported.	This release was not supported.	New Linux release is supported.

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Interface.	In the Taxi interface, the appearance of scroll bars is changed.	In the Taxi interface, scroll bars had a different appearance.	Better visibility of scroll bars in managed forms.
Interface.	In the search dialog box that can be opened from a managed form table linked to a FormDataCollection attribute, the order of fields is changed: the Search in field comes before the Find field.	In the search dialog box that could be opened from a managed form table linked to a FormDataCollection attribute, the Find field came before the Search in field.	Unified look and feel of search dialog boxes in managed form fields linked to various data types.
Managed forms.	In the Taxi interface, the following keyboard shortcuts are implemented for the managed form navigation panel: Go to panel: Alt + 4. Go to next/previous panel item: Tab/Shift + Tab or Left Arrow/Right Arrow. Upon reaching the first/last item, the focus does not move to the last/first item. Go to the first panel item: Home. Go to the last panel item: End. Exit panel navigation mode: Esc.	In the Taxi interface, keyboard shortcuts for moving through navigation panel items were not available.	Improved usability of 1C:Enterprise client applications that use the Taxi interface.
Interface.	In the Taxi interface, in dynamic lists, the vertical scrollbar is replaced with a set of buttons (go to beginning, go to end, page up, and page down) located at the right bottom part of the table linked to a dynamic list.	Tables linked to dynamic lists had vertical scroll bars that did not provide comfortable navigation.	Improved navigation in dynamic lists.
Interface. Dynamic lists.	The following commands are added to the context menu of a table linked to a dynamic list whose main table is a document list or a document journal: Post and Clear posting.	For a table linked to a dynamic list whose main table was a document list or a document journal, the Post and Clear posting commands were only available on the More menu.	Simplified posting and clearing posting in dynamic lists.
Interface. Dynamic lists.	The context menu of a managed form table that is linked to the main attribute of a managed list form having the Generate command now includes a Generate submenu.	The generation commands were only available in the command bar of a managed form table linked to the main attribute of a managed list form.	Simplified document generation based on dynamic lists.
Interface.	In the thick and thin clients, in the managed mode, the option to add a search string to the system command area is removed from all interface modes.	The option to add a search string to a system command area was available.	Removed a feature that was no longer in use.
Interface.	The system command area displays the current user name. It is a hyperlink that opens a dialog box with the user info. The dialog box includes the option to log out of the client application. If the user is authenticated using OpenID, this also cancels OpenID authentication (so that a single command both exits the application and cancels OpenID authentication). If the infobase does not have users, the user name is not displayed. The option to specify the URL that is opened after the exit from the web client in the .vrd file is implemented (you can also specify the URL in the publishing settings dialog box in Designer, and then the platform writes it to the .vrd file). The <exitURL> element of the <point> element of default.vrd file is implemented. This change is not implemented in 8.3.7 compatibility mode.	The exit command and the cancel OpenID authentication command were available on the File menu.	Client application behavior is closer to the standard behavior of web applications.
Web client. Managed forms.	In the web client, streamlined the undo operation in text document fields and input fields. In Safari web browser for Apple iPad, the undo operation is applied to an entire word (and not to each of its characters), just like it is implemented in other web browsers.	In the web client, the undo and redo operations were not optimal.	Improved usability of text operations in the web client.
Client application.	On Windows 7 and later and on Linux with Unity desktop shell, support of jump lists is implemented. The last used infobases are automatically added to a jump list, so that a user can open these infobases without opening the 1C:Enterprise start dialog box. On Windows 7 and later, the option to define buttons that are displayed in the application preview taskbar window (using 1C:Enterprise script) is implemented. This is similar to Windows Media Player buttons in its preview window. On Windows 7 and later and on Linux with Unity desktop shell, the option to define a picture or a number to be displayed at the bottom right corner of the application taskbar icon (using 1C:Enterprise script) is implemented. On Windows XP and later and on Linux with Unity desktop shell, the option to enable blinking of a taskbar application icon (using 1C:Enterprise script) is implemented. The OSTaskbarManager object is implemented.	This feature was not provided.	Inproved usability of 1C:Enterprise applications on some operating systems.
Client application. Interface.	1C:Enterprise user interface now has screen reader support, which provides accessibility for blind and visually impaired people. This option is available on Windows XP or later. It uses the NVDA screen reader software (read more). Screen reader support is only available for managed forms, in the thick and thin clients that use the Taxi interface.	This feature was not provided.	Improved 1C:Enterprise usability for blind and visually impaired people due to screen reader support.
Dynamic lists.	In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the Change form command on the More menu) is implemented. Adding subordinate fields is available for fields whose type includes at least one reference type.	In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the Change form command on the More menu) was not available.	Improved data display capabilities in dynamic lists.
Web client. File operations.	In the web client, a CreateDirectory() or BeginCreatingDirectory() method call includes the question to the user: Do you want to create the DirectoryName directory? In the RequestUserPermission() and BeginRequestingUserPermission() method calls, this confirmation is included in the final question to the user (provided that the confirmation is needed).	In the web client, directories were created without user confirmation.	The platform behavior conforms to the general security recommendations for file operations in the web client.

Table of contents

Functionality	After	Before	Result of changes
Server clusters.	Optimized operations with session data. The lags experienced by end users during the periods of high load on the session data storage in client/server mode are eliminated.	Operations with session data required optimization. End users experienced lags during the periods of high load on the session data storage in client/server mode.	Improved 1C:Enterprise usability.
Interface.	The impact on the total number of opened forms to the opening of new forms is reduced.	The impact on the total number of opened forms to the opening of new forms was significant.	Streamlined form opening when many other forms are open.
Queries.	In the query language, <EXPRESSION> OR TRUE expressions are optimized. This change is not implemented in 8.3.7 compatibility mode.	The query language did not feature additional optimization of query texts.	In some scenarios, the optimization increases the performance of dynamic lists and access restriction queries because the DMBS generates a simpler query plan.
Development tools.	The dump configuration to files and restore configuration from files operations are optimized for scenarios where the configuration includes a large number of managed forms.	The performance of dump configuration to files and restore configuration from files operations was insufficient.	In scenarios where the configuration is stored in an external system, improved performance of data exchange between the infobase and that system.
Database operations.	File infobase operations are optimized in the scenario where all of the following conditions are met: A single client application accesses the infobase (Designer counts as a client application, too). The client application and the database are located on different computers. Both computers support SMB 2.1 protocol (operating system Windows 7 or later). A significant number of database write transactions are performed.	In the specified scenario, the file infobase performance was insufficient.	Improved performance of database configuration updates for file infobases in the scenario where Designer and the database are located on different computers.
Data exchange.	The performance of initial infobase image creation is improved. The performance or reading records from independent nonperiodic information registers during the initial image creation is improved.	The performance of initial infobase image creation was insufficient.	Faster creation of subordinate node infobases in distributed infobases.
DBMS operations.	Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized.	The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient.	Improved performance of temporary table operations.
DBMS operations.	In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) have a different execution algorithm when applied to lists containing more than 100 records. This change is not implemented in 8.3.7 compatibility mode.	In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) had a different execution algorithm when applied to lists containing more than 1000 records.	Improved performance for some scenarios that include access to Oracle Database DBMS.
Administration tools. Technological log. Server clusters. DBMS operations.	Getting DBMS lock data is optimized. The time required for getting the data does not depend on the number of infobases in the cluster. The server cluster service that collects DBMS lock data is implemented. It is named AuxiliaryService (Utility cluster service). The option to manage the collection of DBMS lock data is implemented in the technological log (<DBMSLOCKS> element). Enabling the data collection increases the DBMS load.	The time required for getting DBMS lock data depended on the number of infobases in the cluster. The option to manage the collection of DBMS lock data using the technological log was not available.	Extended database diagnostics.
Administration tools. Database operations.	In the file mode, infobase operations are optimized. To support the optimization, the file database data storage format is updated to new version 8.3.8 format. The option to change the page size of the infobase file (1Cv8.1CD) is implemented. The page size can have one of the following values: 4096, 8192, 16384, 32768, or 65536 bytes. If you set the page size for a database having version 8.3.8 format to 8192 bytes or more, the internal database file size cannot exceed 6 GB. 1C:Enterprise version 8.3.8 can open infobases created in the earlier 1C:Enteprise versions (and having version 8.2.14 database format) without changing their compatibility modes. By default, new infobases have version 8.2.14 format. For the conf.cfg file, the DBFormatVersion parameter is implemented. It defines the format of newly created file-mode infobases. For the infobase connection string, the DBFormat and DBPageSize parameters are implemented. They define the format and page size for new infobases. To migrate data between infobase formats, you can use a .dt file (provided that the target infobase has the required format) or convert the infobase file using cnvdbfl utility. The cnvdbfl utility can change the infobase file page size during the conversion.	All infobases had the same format (version 8.2.14). Pages of the infobase file had fixed size: 4096 bytes. The option to change the size was not available. The internal database file size could not exceed 4 GB.	For infobases with large page sizes, the infobase opening time is reduced and the performance of some queries is improved.
Server clusters.	Reduced size of session data on the hard disk. Session data is stored in the server cluster in compressed form.	Session data was stored in the server cluster in uncompressed form.	The space occupied by internal cluster data is reduced. Some of the internal cluster operations are streamlined.
Client application.	Faster thin client startup in the file mode.	The performance of the thin client startup in the file mode was insufficient.	Faster thin client startup in the file mode.
Database operations.	Restructuring of separated hierarchical catalogs is optimized.	The performance of restructuring separated hierarchical catalogs was insufficient.	The performance of restructuring separated hierarchical catalogs is improved.
Database operations.	The RAM usage is reduced for restructuring a database that contains large amounts of binary data in file mode.	Restructuring a database that contained large amounts of binary data in file mode might result in an unexpected shutdown due to insufficient RAM.	Improved system stability for database restructuring in file mode.

Changes that affect system behavior

Functionality	After	Before	Result of changes
Software licensing. Administration tools.	The command-line utility for software license management (which includes license activation, getting license data, getting the list of licenses, and more) is implemented. The utility is delivered in two distribution packages, which are located in the ExtDst subdirectory of the platform version directory (provided that the thick client or 1C:Enterprise server is installed for this platform version). The utility is not installed automatically. In order to use it, you have to install it first. The utility is available for Windows operating system (both architectures) and for Linux operating system (both architectures, as .deb- and .rpm packages). To access the utility, use the ring license command. The utility requires Java version 8. The detailed utility description is available in 1C:Enterprise documentation.	Software license activation was only available in the interactive mode. No other software management options were available.	Simplified software license management on the end-user computer.
Managed forms.	During the automatic generation of managed form items, the names of items that match the CreateByParameter and ShowInList commands are generated according to the following template: <Form><CommandName><ConfigurationObjectName>. This change is not implemented in 8.3.7 compatibility mode.	During the automatic generation of managed form items, the names of items that matched the CreateByParameter and ShowInList commands were generated according to the following template: <Form><CommandName><SequentialNumber>.	Better usability for applied solution developers.
Managed forms.	In a managed form, the width of a drop-down list of an input field is adjusted according to the width of data displayed in that list. Pressing the Home or End key (as a single key or with any modifier keys) is handled directly in the input field.	In a managed form, each drop-down list of an input field had a fixed width set by the platform or by a developer. Pressing the Home or End key (as a single key or with any modifier keys) in an input field had no effect.	Improved usability of input fields in drop-down lists.
Development tools.	The following features are implemented in the compare and merge modules window : Module line numbers Synchronization between the comparison window and the merge result editor window The editor window functionality is closer to that of 1C:Enterprise script editor window Context help is available in the editor window. The context includes the main configuration (before merging) and the current module (after merging) The window title displays the module name The following features are implemented in the window that displays the result of merging with a third-party tool: The editor window functionality is closer to that of 1C:Enterprise script editor window Context help is available in the editor window. The context includes the main configuration (before merging) and the current module (after merging) When a supported configuration is being updated, the compare and merge configurations window has a new filter option: Show only properties with merge conflicts. The filter displays the objects that are not merged with a third-party tool.	This feature was not provided.	Improved usability for developers working on applied solution update functionality.
Development tools.	The Explanation field of the property palette displays Russian property names only when the Russian 1C:Enterprise script variant or the Russian platform interface is selected.	The Explanation field of the property palette always displayed both Russian and English property names.	Improved Designer usability for English-speaking developers.
Web client. Spreadsheet documents.	In the web client, the option to display a background picture and a pattern in a spreadsheet document cell is implemented.	In the web client, displaying background pictures and patterns in spreadsheet document cells was not supported.	Extended spreadsheet document style options in the web client.
Data display. Spreadsheet documents.	In spreadsheet documents exported to PDF format, font substitution for characters that are not available in the current font is implemented. This change is not implemented in 8.3.7 compatibility mode.	In spreadsheet documents exported to PDF format, characters that were not available in the current font were displayed as missing characters (squares).	In spreadsheet documents exported to PDF format, non-English characters are displayed correctly.
Spreadsheet documents.	When a spreadsheet document is exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells is implemented. This option is not available when exporting spreadsheet documents to XLS (Microsoft Excel 95) format. This change is not implemented in 8.3.7 compatibility mode.	When a spreadsheet document was exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells was not supported.	Better conversion of spreadsheet documents to Microsoft Excel and ODS formats.
Configuration extensions.	When an attribute of composite type that does not include references to configuration objects is adopted, the composite type is fully adopted. During the next adoption attempt, the composite type is supplemented with the set of types from the main configuration. When an attribute of composite type that includes references to configuration objects (nonprimitive types) is adopted, it is adopted as AnyRef. During the next adoption attempt, the AnyRef type is only added if the type is no longer composite and does not include CatalogRef, DocumentRef, and similar types. When a configuration extension is attached, the following rules apply: If an extension configuration attribute type includes AnyRef, this requires the matching main configuration attribute type to include any reference. If an extension configuration attribute type includes CatalogRef, DocumentRef, and similar types, this requires the matching main configuration attribute to include any reference type of that kind. If an attribute of composite type cannot include AnyRef type, any composite type adopted for this attribute is adopted with a single Arbitrary type. Such attributes cannot cause configuration extension attachment errors.	When a composite type was adopted, primitive types were always adopted, and a single type from the configuration object reference types was adopted. When a configuration extension was attached, the following rule applied: if an extension attribute type included composite types, this required the matching main configuration attribute to include exactly the same composite types.	Simplified usage of composite types in configuration extensions.
Web services and HTTP services.	During a web service call, if an internal server infrastructure error that is not related to SOAP occurs, the error message contains the correct diagnostics text. The web service call error message is more detailed and can include data from the faultfactor (Node) and Role tags of the web service response.	During a web service call, if an internal server infrastructure error that was not related to SOAP occurred, an incorrect error message was displayed, and the information about the actual error cause was lost. The web service call error message did not include additional details from the web service response.	The web service call error message is more detailed, which simplifies error diagnostics.
Background and scheduled jobs.	When a client application is started with a file infobase, there is a 2-minute delay before starting the execution of scheduled jobs.	When a client application was started with a file infobase, there was a 1-minute delay before starting the execution of scheduled jobs.	Faster startup of client applications in file mode.
Web client, web service, and HTTP service publishing tools.	When a user disables publishing to a web server from Designer, they are prompted to restart the web server.	When a user disabled publishing to a web server from Designer, they were not prompted to restart the web server.	Users are given better understanding of the disable publishing operation, since the publishing is actually disabled when the server is restarted.
Development tools.	In Designer, the option to customize the background of the context method parameter help is implemented. In the context help, links to the Syntax Assistant have the Identifiers color and normal text has the Miscellaneous color.	In the context help, links to the Syntax Assistant had the default Identifiers color and normal text had the default Miscellaneous color.	You can customize the context help of method parameters to make it readable when the module editor color scheme has dark background.
XML and XDTO support. Web services and HTTP services.	In the XDTO model, new properties are implemented. They ensure correct processing of XSD schemas with any combinations of the following attribute values: elementFormQualified (Qualified element form package property), attributeFormQualified (Qualified attribute form package property), and form (property of the Qualified element). The XDTO package editor provides the option to view and edit the new properties. In Version 8.3.7 or earlier compatibility mode, the new properties have their default values.	When processing XSD schemas, the XDTO model ignored actual values of elementFormDefault and attributeFormDefault attributes. It also ignored the form attribute of XSD schema elements and attributes. Instead, it always used the following values: elementFormDefault was always qualified. attributeFormDefault was always unqualified.	Extended list of web services that are compatible with 1C:Enteprise as they are, without any manual corrections to their descriptions.
Administration tools.	The wizards used to add and edit infobases are refactored, the number of wizard pages is reduced. Automatic detection of the infobase connection type is implemented, based on the string stored in the clipboard or the string entered in the Specify infobase name field. This includes the detection of the path to a file infobase or the URL for accessing an infobase running on a web server. Once the infobase type is detected, all of the related wizard fields are filled in.	The wizards used to add and edit infobases were more complex and had more pages.	Simplified adding of infobases to the list.
Managed forms.	If an input field of a managed form displays ValueList data, the value list form that is opened for editing the data gets the following properties from the input field: ChoiceParameters, supplemented with values based on the ChoiceParameterLinks property ChoiceForm (in the web client) ChoiceFoldersAndItems (in the web client) Mask EditFormat QuickChoice TypeLink	If an input field of a managed form displayed ValueList data, the value list form that was opened for editing the data received the following properties from the input field: ChoiceParameters, not supplemented with values based on the ChoiceParameterLinks property ChoiceForm (thin client only) ChoiceFoldersAndItems (thin client only)	Eliminated unexpected system behavior.
Full-text search. Input by string. Dynamic lists.	Input by string and full-text search in dynamic lists find data that is not yet indexed for the full-text search.	Input by string and full-text search in dynamic lists did not find data that was not yet indexed for the full-text search.	Data that is not yet indexed for the full-text search is included in full-text search results and input by string results.
Managed forms.	In the Taxi interface, the appearance of managed form buttons and command bar buttons is changed. For the CommandBarButton and CommandBarHyperlink buttons, support of the following properties is implemented: BackColor, TextColor, Font, BorderColor (except CommandBarHyperlink buttons). For form group extension submenus, support of the following properties is implemented: BorderColor, BackColor, TitleTextColor, and TitleFont. This change is not implemented in version 8.3.7 compatibility mode and in version 8.2 interface compatibility mode. For the standard Copy command of dynamic list table extension: The Auto value of Representation property is equivalent to Picture. The Auto value of OnlyInAllActions property is equivalent to No. For MoveUp and MoveDown managed form table commands, the Auto value of the OnlyInAllActions property is equivalent to No. These commands are included in a compact button group. This change is not implemented in version 8.3.7 compatibility mode. In version 8.3.7 compatibility mode with compact interface the button height in the thin client differs from the button height in the web client.	In the Taxi interface, the appearance of managed form buttons and command bar buttons was different. The CommandBarButton buttons had BackColor, TextColor, Font, and BorderColor properties, which were never used. Form group extension submenus had BorderColor, BackColor, TitleTextColor, and TitleFont properties, which were never used. For the standard Copy command of dynamic list table extension: The Auto value of Representation property was equivalent to Text. The Auto value of OnlyInAllActions property was equivalent to Yes. For MoveUp and MoveDown managed form table commands, the Auto value of the OnlyInAllActions property was equivalent to Yes.	Improved form creation capabilities in the Taxi interface. The default location of some frequently used buttons (Copy in dynamic lists and row movement commands in other tables) changed from the More menu to the command bar.
Managed forms.	The option to display command bar commands as hyperlinks is implemented. Pop-up menus do not support displaying commands as hyperlinks. For the FormButtonType enumeration, the CommandBarHyperlink value is implemented. In 8.3.7 compatibility mode, the FormButtonType.CommandBarHyperlink value is treated as FormButtonType.CommandBarButton. In the Taxi interface, the option to set horizontal picture alignment for managed form buttons is implemented. Pop-up menus do not support this feature. For managed form buttons, the PictureLocation property is implemented. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode. The option to set command bar button spacing is implemeneted. Managed form group extension for a button group is implemented. Pop-up menus do not support this feature. The ButtonGroupRepresentation system enumeration is implemented. In 8.3.7 compatibility mode and version 8.2 interface compatibility mode, the button spacing value is ignored. The option to set button shape (except pop-up menu buttons) is implemented. For managed form buttons and form group extensions for popups, the Shape property is implemented. Pop-up menu commands do not support this property. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode. The option to set managed form button shape is implemented. For managed form buttons and form group extensions for popups, the ShapeRepresentation property is implemented. The ButtonShapeRepresentation system enumeration is implemented. Pop-up menu commands do not support this feature. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode.	Command bar commands could not be displayed as hyperlinks. The option to set horizontal picture alignment for managed form buttons was not available. The option to set command bar button spacing was not available. The option to set button shape was not available. The option to set command bar button appearance was not available.	More managed form appearance options in the Taxi interface.
Managed forms.	Recommendations about the usage of user messages are added to the documentation. The recommendations are aimed to reduce the chance of situations where users cannot read the displayed messages.	The documentation did not contain the recommendations aimed to reduce the chance of situations where users cannot read the displayed messages.	The documentation is improved.
Software licensing.	Updates of Windows 10 operating system never deactivate software licenses.	The software licensing system was not fully compatible with Windows 10. Updates of Windows 10 could deactivate a software license.	Improved compatibility of the software licensing system with Windows 10.
Localization.	The Kazakh interface language (language code: kk) is not supported.	The Kazakh interface language (language code: kk) was supported.	The Kazakh interface language is not supported.
Regional settings.	For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ (Zabaikalye Territory), 27-FZ (Astrakhan Region), 57-FZ (Altai Territory), 58-FZ (Republic of Altai), 59-FZ (Sakhalin Region), 69-FZ (Ulyanovsk Region), 87-FZ (Magadan Region), 109-FZ (Tomsk Region), 271-FZ (Novosibirsk Region), and 395-FZ (Saratov Region). This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.	The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ, 87-FZ, 109-FZ, 271-FZ, and 395-FZ.	The time offset changes introduced by the new law are implemented.
Spreadsheet documents.	Text copied from Microsoft Excel speadsheet cells is fully pasted to 1C:Enterprise spreadsheet cells, regardless of its length.	Text copied from Microsoft Excel spreadsheet cells and pasted to 1C:Enterprise spreadsheet cells was cut, only the first 255 characters were copied.	Eliminated unexpected system behavior.
Spreadsheet documents.	Improved processing of data having date and time format during the import from Microsoft Excel: For standard Microsoft Excel formats, matching 1C:Enterprise format strings are applied. 1C:Enterprise format strings are defined based on the locale codes explicitly specified in Microsoft Excel format strings. The date type uses the first short date format separator found in the infobase. Dates where the month is specified by its first letter are converted to 1C:Enteprise dates having short month presentation. This change is not implemented in 8.3.7 compatibility mode.	Processing of data having date and time format during the import from Microsoft Excel was performed as follows: A fixed list of standard Microsoft Excel formats was applied. Locale codes explicitly specified in Microsoft Excel format strings were ignored. The current infobase settings were used instead. The date type always used the slach (/) separator. Dates where the month was specified by its first letter were converted to dates having full month presentation.	Improved accuracy of date and time import from Microsoft Excel.
Web services and HTTP services.	For configurations that include HTTP services, setting compatibility mode to Version 8.3.4 or earlier is allowed. If your configuration includes HTTP services and you previously opened it with 1C:Enterprise Designer 8.3.4, when you open it with 1C:Enterprise 8.3.8, perform the following steps: Create any configuration object. Save the infobase configuration. Delete that configuration object. Save the infobase configuration.	In 1C:Enterprise 8.3.7 or earlier, if a configuration included HTTP services, setting its compatibility mode to Version 8.3.4 or earlier was not allowed.	You can add HTTP services to configurations that run in compatibility mode Version 8.3.4 or earlier.
Client application. Internet-enabled functionality.	You have the option to select the set of external resources that the platofrm uses (in ExternalResourcesMode parameter of conf.cfg configuration file). If this parameter is not specified, the platform selects its value automatically.	This feature was not provided.	You have the option to select the set of external resources that the platofrm uses.

Table of contents

Changes that require modification of configuration and administrative settings

Functionality	After	Before	Result of changes
Internet-enabled functionality.	The NSSSecureConnection object and NSS certificates are no longer available for use in 1C:Enterprise script.	1C:Enterprise supported NSS certificates in 8.3.6 compatibility mode.	Support of NSS certificates is discontinued.
Internet-enabled functionality.	Support of TLS protocol versions 1.1 and 1.2 is implemented for scenarios where the client certificate is not specified in the connection settings. The SSL protocol version 3.0 is only used when the client application is started with /HttpsForceSSLv3 command-line option. In all other scenarios SSL version 3.0 is not used. 1C:Enterprise ignores the AllowSSLv3 parameter in conf.cfg file. The InternetMail object does not support SSL version 3.0.	1C:Enterprise only supported TLS protocol version 1.0. The AllowSSLv3 parameter was available for use in conf.cfg file. The InternetMail object supported SSL version 3.0.	Increased security of connections established by client applications for Internet operations.
Internet-enabled functionality.	The platform no longer uses cacert.pem file for creating HTTPS/FTPS connections. The platform uses the root certificate store of the operating system for creating HTTPS/FTPS connections. This change is not implemented in 8.3.7 compatibility mode.	The platform used cacert.pem file for creating HTTPS/FTPS connections in scenarios where no certificate stores were specified explicitly.	The outdated technology is no longer supported.
Managed forms.	For managed forms, the option to update data presentations only for the specified set of form items is implemented. For the RefreshDataRepresentation() method, the UpdateItems parameter is implemented. For the EditTextUpdate system enumeration, the Always value is implemented.	The option to specify a set of form items when updating data presentations using the RefreshDataRepresentation() method was not available.	Form data can be updated in idle handlers without losing the text being edited in a text box.
Dumping/loading configurations to files.	The dump of the Source property of the FormItemAddition object to a file is more human-readable. You can restore configuration from files having both property dump formats.	The dump of the Source property of the FormItemAddition object to a file was less human-readable.	Dumping configurations to files produces files that are more human-readable.
XML and XDTO support. Development tools.	Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) is much more detailed. During the creation of WSDefinitions object, exceptions are raised if the used WSDL description has errors. The WSDL description used to create WSDefinitions or WSReference objects must comply with the following rules: Its first tag is <definitions>. It includes the targetNamespace attribute of the <xs:schema> element. If it does not comply with the rules, an exception is raised. This change is not implemented in 8.3.7 compatibility mode.	Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) was not sufficiently detailed. During the creation of WSDefinitions object, if the used WSDL description had errors, invalid elements were ignored. If the first tag of the WSDL description used to create WSDefinitions or WSReference objects was not <definitions>, empty web service description objects were created. If the WSDL description used to create WSDefinitions or WSReference objects did not include the targetNamespace attribute of the <xs:schema> element, the platform set a pseudorandom namespace.	Better diagnostics for WSDL description operations.
Queries.	If a constant stores a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that includes a request to the Value field returns a value of that type. This change is not implemented in 8.3.7 compatibility mode.	If a constant stored a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that included a request to the Value field returned a value of BinaryData type.	Eliminated unexpected system behavior.
Print tools.	The following behavior of the RepresentableDocumentBatch.Print() method is implemented: On Windows: Create a single printer job. Output the entire batch to a file, prompt for the file name before the output. On Linux: If all documents in the batch have identical print settings, use the Windows scenario. If the print settings are different, create a printer job for each document. This change is not implemented in 8.3.7 compatibility mode. The RepresentableDocumentBatch.Title, property is implemented. It is used for generating the batch presentation.	The RepresentableDocumentBatch.Print() method created a job for each document in a batch.	Improved printing of document batches.
Data composition system.	Text and Format conditional appearance items are applied to fields of chart grouping templates of data composition systems regardless of the previous Format value (even if the previous value is taken from the data composition system). Text conditional appearance item has higher priority than Format conditional appearance. This change is not implemented in 8.3.7 compatibility mode.	Text and Format conditional appearance items were applied to fields of chart grouping templates of data composition systems only if the Format conditional appearance was not applied to those fields earlier.	Eliminated unexpected system behavior.
Data composition system.	The MarkNegatives conditional appearance property is only used if this property is set to True and the Use conditional appearance property is also set to True. This change is not implemented in 8.3.7 compatibility mode.	The MarkNegatives conditional appearance property was only used if the Use conditional appearance property was set to True.	Eliminated unexpected system behavior.
Data composition system.	In the query language, the CASE operation result is based on all expression types from all THEN branches of that expression. This change is not implemented in 8.3.7 compatibility mode.	In the query language, the calculation of CASE operation result ignored all THEN branches that included constant expressions with NULL values.	Eliminated unexpected system behavior.
Full-text search.	The option to set a size limit for data indexed for the full-text search is implemented. The default size limit is 1 MB. For the FullTextSearchManager object, the SetMaxIndexedDataSize() and GetMaxIndexedDataSize() methods are implemented. The <FTEXTSKIP> technological log event is implemented. This change is not implemented in 8.3.7 compatibility mode.	The option to set a size limit for data indexed for the full-text search was not available. All infobase data was indexed.	You can limit the full-text search scope by excluding large blocks of data you do not need to search. This increases the performance of full-text search indexing and reduces the index size.
Client application. Internet-enabled functionality. Administration tools.	The algorithm that retrieves the list of infobases and platform updates over HTTPS no longer uses the cacert.pem file, which is included in the platform distribution kit. On Linux, the platform gets certificates from the certification centers specified in the operating system. On Windows, the platrorm uses the operating system root certificate store.	On Windows, the platform used the cacert.pem file and the operating system root certificate store in order to check an HTTPS connection. On Linux, the platform used the cacert.pem file only.	Simplified administration of platform update over HTTPS.
Linux. System requirements.	The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system is refactored. The fontconfig library is used to get the list of fonts. This library is included in the system requirements. The list of directories used for storing fonts is removed from 1C:Enterprise documentation.	The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system used a fixed directory list, which was described in 1C:Enterprise documentation. The fontconfig library was not used for getting the list of fonts.	Extended the list of fonts available to 1C:Enterprise on Linux operating system. Simplified 1C:Enterprise administration.
System requirements.	The type specified for a data composition schema parameter affects the type of query fields that use this parameter. This change is not implemented in 8.3.7 compatibility mode.	The type specified for a data composition schema parameter did not affect the type of query fields that used this parameter.	Data displayed in reports better matches the input parameters.
Dynamic lists.	The dynamic list implementation is refactored in order to increase its quality. The list of virtual dynamic list fields that are not available for use in filter, grouping, and order settings is extended. If the main dynamic list table does not have key fields (according to 1C:Enterprise script object model) and a grouping is set for this table, an error is generated. When a filter, sorting, or grouping by a field that is not included in a query is specified using 1C:Enterprise script, an error informing that the field is not found is displayed. The list of restrictions to queries used to generate dynamic lists is modified. Dynamic list sorting specifics are described in the documentation. The description of algorithms that dynamic lists use for getting data is changed. The standard row picture is generated based on the standard attributes. If a query includes fields whose aliases are identical to standard attribute names and these fields store other data, these fields are not used in standard picture generation. If a dynamic list filter cannot be converted to a query language expression, an error is generated. Dynamic list column data that is not displayed and does not have the Use always property set is not sent to the client. Client access to such columns is not available. If a dynamic list column has the Use always property but the current user does not have the View right for that column, the column data is not sent to the client. Client access to such columns (using the CurrentData property or the RowData() method) is not available. Automatic dynamic list filters for standard Owner, Parent, Date, Period, and IsFolder fields are applied using data composition system tools. Automatic dynamic list filters for key fields can be applied using data composition system tools or using direct addition of main table filter conditions to query texts. When a filter is applied using data composition system tools, it can be applied in nested queries and virtual table parameters. This can significantly change the dynamic list data selection result (compared to the result obtained in 8.3.7 compatibility mode). The detailed description of all the changes listed above is included in the documentation. This change is not implemented in 8.3.7 compatibility mode.	The following virtual fields were not available in dynamic list sorting and grouping settings: DataVersion, PredefinedDataName, tabular sections fields, and fields having the following types: Type, String (unlimited length), and BinaryData (unlimited length). The list of restrictions to the grouping and ordering settings was different and it was not full. If the main dynamic list table did not have key fields (according to 1C:Enterprise script object model) and a grouping was set for this table, the content of data to be displayed was undefined. When a filter by a field that was not included in a query text was set, the filter might be applied without displaying any errors, or ignored. If grouping or sorting by a field that was not included in a query was specified using 1C:Enterprise script, the field was ignored. The list of restrictions to queries used to generate dynamic lists was different. The list of dynamic list sorting specifics was not documented. The description of algorithms that dynamic lists used for getting data was different. If a dynamic list query had fields with aliases matching the names of standard attributes used to generate standard row pictures, they were used in the generation of standard pictures (except the IsFolder attribute). If a dynamic list filter could not be converted to a query language expression, the filter was applied by data composition schema processor after getting the data, and this might reduce the amount of displayed data. If dynamic list settings included grouping or sorting fields that were unavailable (before applying rights and functional options), these fields were ignored. In some scenarios dynamic list column data that was not displayed and did not have the Use always property set was sent to the client. If dynamic list column had the Use always property but the current user did not have the View right for that column, the column data was sent to the client. In this scenario the default values of specific data types were used as column values. Automatic dynamic list filters for key fields and for standard Owner, Parent, Date, Period, and IsFolder fields were applied by direct addition of their conditions to query texts.	Improved quality and reliability of dynamic lists. More details about dynamic list specifics are added to the documentation.
Background and scheduled jobs.	When a nonserializable value is passed to BackgroundJobs.Execute() method as a background job parameter, the background job is not started and an exception is raised. This change is not implemented in 8.3.7 compatibility mode.	When a nonserializable value was passed to the BackgroundJobs.Execute() method as a background job parameter, the background job was started and the Undefined value was stored to that parameter. This did not raise any exceptions.	The start of background jobs complies with the global error diagnostic rules.
Administration tools.	During an unexpected shutdown of the thin client, the dump generation includes taking a screenshot (prntscrn attribute of dump element of logcfg.xml file).	During an unexpected shutdown of the thin client, the dump generation did not include taking a screenshot.	Eliminated unexpected system behavior.
Queries.	The result of division by NULL is treated as a number of unspecified length . This number cannot be used in operations that do not accept numeric operands (such as AND, OR, NOT). This change is not implemented in 8.3.7 compatibility mode.	The result of division by NULL was not treated as a number and therefore could be used in operations that did not accept numeric operands (such as AND, OR, NOT).	Eliminated unexpected system behavior.
Managed forms. Interface.	The approach to processing the closing of applications and managed forms is changed: The new "exit application" mode is implemented. It requires special processing in the BeforeClose and OnClose managed form event handlers. Opening windows and executing server calls is not allowed in BeforeExit and OnExit managed application event handlers, and also in BeforeClose and OnClose managed form event handlers (provided that the form is in the "exit application" mode). The option to generate a text message prompting the user to confirm or cancel the exit is implemented (in the web client all messages are combined in a single dialog box). This approach is described in detail in the documentation. For BeforeClose managed form event handler, the Exit and WarningText parameters are implemented. For OnClose managed form event handler, the Exit parameter is implemented. If BeforeClose or OnClose managed form event handler has the Exit parameter, in version 8.3.7 compatibility mode the parameter is set to Undefined. For BeforeExit managed application module event handler, the WarningText parameter is implemented. This change is not implemented in 8.3.7 compatibility mode.	Depending on the modality usage mode, different approaches to closing managed forms and the main application window were used. In some scenarios (especially in the web client) these approaches led to errors that were hard to detect and fix.	Unified approach to closing forms and the main application window, which provides acceptable user interaction capabilities in all client applications. The implemented platform behavior conforms to the methodology and technical requirements of modern web browsers.
Administration tools. Client application installation.	When an infobase that has a platform version specified in a local or global list of infobases is started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version is performed regardless of the presence of /AppAutoCheckVersion command-line option. If a version that is not available on the local computer is specified and this version cannot be installed, an attempt to run the infobase with the latest 1C:Enterprise version is made During the client application update over HTTP, the check for operating system user right to perform this operation is disabled. If the user does not have sufficient rights for installing the client application, the UAC dialog box prompting to confirm the installation on behalf of a user that has administrative rights is displayed. Error diagnostics during the download and installation of the client application distribution kit over HTTP is improved. In the /AppAutoCheckVersion command-line option, you can explicitly specify whether the search for a specific 1C:Enteprise version is performed.	When an infobase was started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version was only performed if the command line included the /AppAutoCheckVersion option. During the client application update over HTTP, the check for operating system user right to perform this operation was performed.	The usability of selection and update of the client application used to access a specific infobase is improved. Improved reliability of automatic thin client updates over HTTP.
Administration tools.	When the thin client is installed from a custom distribution kit, a single 1cestart shortcut is created in the 1C:Enterprise folder.	When the thin client was installed from a custom distribution kit, the 1C:Enterprise folder included 1cestart shortcut and the Advanced folder with subfolders for each installed 1C:Enterprise version.	Reduced number of 1C:Enterprise startup options available after the installation of the thin client.
Administration tools.	In the client application startup command line, the rules for parsing mandatory parameters are modified. If an option that has a mandatory parameter is specified, the parameter must be also specified (or the option must be omitted). Parameters beginning with slash marks "/" are allowed.	In the client application startup command line, the rules for parsing mandatory parameters were different. Mandatory option parameters could be omitted. Parameters beginning with slash marks "/" (full file name on Linux) could be treated as command-line options.	Eliminated unexpected system behavior.
Administration tools.	1C:Enterprise documentation and Designer help include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode, which were previously missing. For the infobase creation mode (CREATEINFOBASE), new /DumpResult option is implemented. It enables writing the operation result to a file. In the file mode, batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option automatically creates an infobase if the database file is not available in the directory.	1C:Enterprise documentation and Designer help did not include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode. In the file mode, during the batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option, if the dababase file was not found in the specified directory, the user was asked for the confirmation of further actions.	Improved 1C:Enterprise documentation and Designer help. Simplified batch Designer startup in some usage scenarios.
Data composition system.	If a data set field of a data composition schema has an ordering expression specified and the data composition settings include ordering by this field (Descending), the direction speficied in the ordering expression is reversed. This change is not implemented in 8.3.7 compatibility mode.	If a data set field of a data composition schema had an ordering expression specified, ordering for this field was always taken from the ordering expression, while the direction specified in the field settings was ignored.	Eliminated unexpected system behavior.
Managed locks. Accounting registers.	Managed locks that are set for writing accounting register records in the LockForUpdate mode are set by values of nonturnover extra dimensions only. When you set a lock for further operations with balances, it is recommended that you do not specify turnover extra dimension values (you can use the LockForUpdate property or explicitly use a managed lock). When you set a lock for further operations with turnovers, specify all the required extra dimenstion values, including the values of turnover extra dimensions (use the managed lock explicitly). This change is not implemented in version 8.3.7 compatibility mode.	Managed locks that were set for writing accounting register records in the LockForUpdate mode included locks by all extra dimension values.	The behavior of LockForUpdate property of accounting register object is better suited for solving typical tasks. In the LockForUpdate mode, the resulting lock does not inlcude turnover extra dimensions, which fits the frequently used scenarios where the lock is used to check the balances but not the turnovers.
Queries.	In a query, if a single system enumeration is retrieved and it is not combined with other types, the GROUP BY operation groups the values of this field regardless of the enumeration value source. A similar behavior is implemented for UUIDs and references to external data source tables. This change is not implemented in 8.3.7 compatibility mode.	In a query, if a single system enumeration was retrieved and it was not combined with other types, the GROUP BY operation might not group the values of this field (depending on the enumeration value source).	Eliminated unexpected system behavior.
DBMS operations.	For Microsoft SQL Server DMBS, types of table fields that store some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) are changed. New field types are used if no compatibility mode is selected and only after restructuring configuration objects. To perform database table restructuring with modification of field types, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair). This change is not implemented in 8.3.7 compatibility mode.	For Microsoft SQL Server DMBS, table fields that stored some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) had different types.	Better mapping between the stored types and Microsoft SQL Server table field types.
DBMS operations.	For all DBMS, the structure of indexes by fields of composite type is modified. This reduces the total number of indexes. Such indexes are built if no compatibility mode is selected and only after restructuring configuration objects. To perform database table restructuring with index update, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair). This change is not implemented in 8.3.7 compatibility mode.	For all DBMS, the structure of indexes by fields of composite type was different.	Reduced number of indexes for tables storing objects with fields of composite types. This increases the performance of operations with these object types.
Configuration extensions.	When a background job is executed, all the configuration extensions available in the session that startes the job are also attached in the background job session. This change is not implemented in 8.3.7 compatibility mode. For ConfigurationExtensionsManager object, the ExecuteBackgroundJobWithDatabaseExtensions method is implemented. It duplicates the background job execution procedure implemented in earlier 1C:Enterprise versions.	When a background job was executed, all the configuration extensions available in the infobase were attached in the background job session.	Background job execution environment is closer to the parent session environment.
Managed forms.	In the thick and thin clients, when a user starts typing in a cell of a managed form table, the AutoComplete event is fired. This change is not implemented in version 8.3.7 compatibility mode.	In the thick and thin clients, when a user starts typing in a cell of a managed form table, the StartChoice event is fired.	The behavior of the input field in the scenario where a user starts typing in a table cell is uniform with other input scenarios.
Technological log.	The recommendation to have no more than 20 <LOG> elements in the logcfg.xml file is added to the documentation. Adding more than 20 <LOG> elements can impact the platform performance.	The recommendation to have no more than 20 <LOG> elements in the logcfg.xml file was absent from the documentation.	The recommendation to avoid inefficient technological log usage scenarios is added to the documentation.
Automated testing.	A sections panel that is not displayed in the main window because it contains no items is no longer included in the list of subordinate objects returned by the TestedWindowCommandInterface.GetChildObjects() method.	A sections panel that was not displayed in the main window because it contained no items was included in the list of subordinate objects returned by the TestedWindowCommandInterface.GetChildObjects() method.	Eliminated unexpected system behavior.
Automated testing.	The recommendation to use FindObject() and FindObjects() methods to access a required item of a subordinate object list (instead of accessing it by index) is added to the documentation.	The recommendation to use FindObject() and FindObjects() methods to access a required item of a subordinate object list was absent from the documentation.	Improved 1C:Enterprise documentation.
Managed forms.	The OnClose event handler and the notification specified in the OnCloseNotifyDescription form property are not called when a managed form is closed using the Close() method called in the OnOpen event handler. This change is not implemented in 8.3.5 compatibility mode.	When a managed form was closed using the Close() method called in the OnOpen event handler: In the web client, the OnClose event handler and the notification specified in the OnCloseNotifyDescription form property were not called. In the thin client, the OnClose event handler and the notification specified in the OnCloseNotifyDescription form property were called.	Unified client application behavior.
Managed forms.	The documentation describes the following platform behavior: when a value is assigned to a variable that is not declared earlier and has a name identical to a property name available in the current context, this can generate a runtime error or a configuration check error. It is recommended that you declare variables with such names using the Var operator to eliminate possible errors.	The documentation did not contain a clear description of this scenario.	The documentation contains a clear description of a possible scenario and provides recommendations for eliminating possible issues.
Window-based interface.	The order of elements in the collection returned by the GetWindows() method is changed. The documentation and the Syntax Assistant state that the order of elements in that collection does not follow any specific rule and application algorithms must not rely on that order.	The documentation did not state that the order of items in the collection returned by the GetWindows() method does not follow any specific rule.	The documentation provides more detail about the GetWindows() method.
XML and XDTO support.	An attempt to write an invalid qualified element name generates an exception. This change is not implemented in 8.3.6 and 8.3.7 compatibility modes.	An attempt to write an invalid qualified element name did not generate an exception. This might produce an invalid XML file.	Eliminated unexpected system behavior introduced in version 8.3.6.
Dynamic lists.	If the current user does not have the View right for a dynamic list key field, an attempt to get dynamic list data generates an access violation error. Information for technical support includes the list of fields that cannot be accessed due to insufficient rights. This change is not implemented in 8.3.7 compatibility mode.	If the current user did not have the View right for dynamic list key fields, this did not affect the list availability. If a form had conditional formatting based on these key fields, it could not be opened.	Eliminated unexpected system behavior.
Data exchange.	Unexpected system behavior during the writing of ThisNode exchange plan object, which was found in 1C:Enterprise versions 8.3.8.1606 - 8.3.8.1861, is eliminated. If you migrate to a new 1C:Enterprise version: From version 8.3.7 or earlier, no action is reqiured. From version in range 8.3.8.1606 - 8.3.8.1861, it is recommended that after the migration you perform infobase verification and repair with the Check logical infobase integrity check box selected, or use the administration console utility (1cv8a) to verify and repair the infobase. If your infobase contains objects that refer to exchange plan items and they can contain references to ThisNode item, it is recommended that you correct the references using the Replace references to incorrect ThisNode records data processor (read more). The data processor can use the result provided by the administration console (recommended) of the exchange plan record deletion marks as an input. It is recommended that you run the cluster administration console (1cv8a) in verification and repair mode, with report generation enabled. Then use the report as an input for the Replace references to incorrect ThisNode records data processor.	1C:Enterprise versions 8.3.8.1606 - 8.3.8.1861 generated incorrect exchange plan records for ThisNode element. This might result in a variety of errors, such as the following: Duplicating ThisNode records Missing ThisNode records Unexpected shutdown when opening an exchange plan list form And more 1C:Enteprise versions 8.3.7 and earlier did not have this issue.	Eliminated unexpected system behavior.
Dynamic lists.	In the source of available data composition system settings for dynamic lists, the following fields are not available for filtering, sorting, or grouping: Fields subordinate to fields that represent aggregate functions of the query language Fields subordinate to fields from other (external) data sources Subordinate characteristic fields of tabular section fields The search initiated by typing a search string excludes reference fields that represent aggregate functions of the query language. This change is not implemented in 8.3.7 compatibility mode.	In the source of available data composition settings for dynamic lists, the following fields were available for filtering, sorting, or grouping: Fields subordinate to fields that represented aggregate functions of the query language Fields subordinate to fields from other (external) data sources Subordinate characteristic fields of tabular section fields When a filter by any of these fields was applied, a dynamic list might display incorrect data (some data or all data might be missing). An attempt to search in reference fields that represented aggregate functions of the query language initiated by typing a search string might generate errors. If errors we not generated, a dynamic list might display incorrect data (some data or all data might be missing).	The search intiated by typing a search string in dynamic lists is improved. Reduced number of errors that did not have clear descriptions.
Dynamic lists.	In 1C:Enterprise mode, in a dynamic list with a custom query and the main table specified, the availability of main table fields and their subordinate fields for filtering does not depend on the availability of these fields in the dynamic list query. If main table fields are absent from the query text, they are added implicitly. If a dynamic list query text includes a field with alias identical to an alias of a main table field, this field is used in the filter, regardless of whether the fields themselves are identical. Fields having multiple paths (in different 1C:Enterprise script languages) are only available in the current 1C:Enterprise script language. This change is not implemented in 8.3.7 and earlier compatibility modes.	Only fields available in a query text and standard main table fields (such as Ref) were available for filtering. A filter that included unavailable fields with names indentical to main table field names might be applied without any errors generated.	For a dynamic list with a custom query and the main table specified, you can include main table fields that are absent from the query text in choice parameters and choice parameter links.
Accumulation registers. Accounting registers.	Eliminated unexpected system behavior during the calculation of accumulation register and accounting register totals in scenarios where a dimension list includes a dimension of String type and an index by dimensions includes more that 16 database fields. When you migrate to 1C:Enterprise version 8.3.8 or later, it is recommended that you use the data processor available for download at 1c-dn.com (read more). The data processor determines whether additional actions are required. If they are required, after the migration perform infobase verification and repair with Check logical infobase integrity and Recalculate totals check boxes selected, or use the cluster administration console (1cv8a). The latter option is recommended because it is faster.	Accumulation register and accounting register totals might be calculated incorrectly in scenarios where a dimension list included a dimension of String type and an index by dimensions included more that 16 database fields.	Eliminated unexpected system behavior.
Internet-enabled functionality. Web client, web service, and HTTP service publishing tools.	The option to block redirection to potentially harmful sites after completing an OpenID provider operation is implemented. In the default.vrd file, the <returnto> element (subordinate to <provider> element) is implemented. It contains the list of allowed redirection URLs. Note that publishing OpenID providers from Designer does not support <returnto> elements (existing elements of this type are deleted and new ones are not generated). You have to add these elements manually. If you migrate to a new 1C:Enterprise verson, requests to OpenID providers that include the openid.return_to parameter will return HTTP error 400. To eliminate this issue, in the default.vrd file, add the required number of <returnto> elements with available redirection URLs.	The option to affect redirection after completing OpenID provider operations was not provided.	Improved security of OpenID provider operations.
System requirements.	The list of supported operating systems and web browsers is changed: Thin client, thick client, web client, and 1C:Enterprise server (Windows versions): Windows XP Service Pack 3 Windows Vista or later with the latest updates Windows Server 2003 or later with the latest updates On Windows and Linux, Mozilla Firefox versions 38 and later are supported.	The list of supported operating systems and web browsers was different: Thin client, thick client, web client, and 1C:Enterprise server (Windows versions): Windows XP (no Service Pack 3 requirement) Windows Vista or later (no latest updates requirement) Windows Server 2003 (no latest updates requirement) On Windows and Linux, Mozilla Firefox versions 17 and later were supported.	1C:Enterprise requires more secure versions of operating systems of Windows family.
Client application. Client application installation. Add-ins.	Since Windows versions 2008 R2 and later stop trusting SHA-1 certificates in January 2017, the following changes are implemented: .msi and .mst files included in 1C:Enterprise platform distribution kit are signed with SHA-256; all other files are signed with both SHA-1 and SHA-256. The add-in development technology documentation (read more) now includes the following recommendations: sign add-in installer files with both SHA-1 and SHA-256; sign .msi files with SHA-256.	All files included in 1C:Enterprise platform distribution kit were signed with SHA-1. The following recommendations were not available in the add-in development technology documentation (read more): Sign add-in installer files with both SHA-1 and SHA-256. Sign .msi files with SHA-256.	The platform executable files are verified on all supported operating systems of Windows family.

Table of contents

Object	The old name	The new name
Synchronous call usage mode for platform extensions and add-ins property name.	SynchronousExtensionAndAddInCallUseMode.	SynchronousPlatformExtensionAndAddInCallUseMode.
Directory name parameter in BeginCreatingDirectory() method.	Directory.	DirectoryName.
The update start button in the client application update over HTTP dialog box.	Update.	Update and run.

Functionality	After	Before	Result of changes
Development tools. Mobile application builder.	In the mobile platform, support of in-app billing services is added. This includes Apple In-App Purchase (for iOS) and Google Play In-App Billing (for Android). Support of in-app billing for Windows is not provided. The In-app purchases mobile application permission is implemented. The InAppPurchases, InAppPurchase, InAppPurchaseReceipt, and InAppPurchasesValidation objects are implemented. In the desktop platform, the InAppPurchasesValidation object is implemented. It is intended for testing in-app purchase algorithms. In the mobile platform for developers, a service providing an API similar to Google Play In-App Billing is implemented for Android operating system. It is intended for debugging in-app purchase algorithms. The option to test the full purchase cycle is implemented. This includes the purchase creation and the emulation of some related scenarios. The HTTP service (named PurchaseTest) and the testing tools are provided by the mobile application builder. The mobile application builder supports building mobile applications with in-app purchases.	This feature was not provided.	The option to implement purchases and subscriptions in mobile applications is available. You can create applications with paid features.
Development tools. Mobile application builder.	For mobile applications, the option to display ads is implemented. It uses iAd service (for iOS) and AdMob service (for Android). Displaying ads on Windows is not supported. The AdRepresentation object is implemented. Mobile application builder supports applications that display ads.	This feature was not provided.	The option to create mobile applications with advertising monetization model is available.
Spreadsheet documents.	Exporting spreadsheet documents fo PDF format is implemented.	This feature was not provided.	More options for data presentation in mobile applications.
Data display.	On Android version 4.1 or later, numbers are displayed correctly if the NG parameter of the Format function contains two groups.	On Android version 4.1 or later, numbers were displayed incorrectly if the NG parameter of the Format function contained two groups.	Eliminated unexpected system behavior.
File operations.	In the mobile platform, support of asynchronous file operation methods is implemented (this includes global context methods and the File object).	This feature was not supported by the mobile platform.	Improved parallel code implementation for both mobile and desktop platforms.
Full-text search.	On the mobile platform, support of FullTextSearchManager.CheckIndex() method is implemented. In the Syntax Assistant, methods of FullTextSearchManager object are marked as available on the mobile platform.	This feature was not supported by the mobile platform. The Syntax Assistant erroneously stated that methods of the FullTextSearchManager object were not available on the mobile platform.	Extended full-text search support on the mobile platform. The Syntax Assistant description is up-to-date.
Internet-enabled functionality.	On the mobile platform, when specifying request body as a string for an HTTPRequest or HTTPServiceResponse object, you have the option to include BOM characters to the request or exclude them. On the mobile platform, the ByteOrderMarkUsage system enumeration is implemented.	This feature was not supported by the mobile platform.	Simplified mobile application integration with systems that do not expect BOM characters in HTTP requests.
Common objects.	The MobileDeviceApplicationRun object is now available on iOS and Windows platforms. The MobileDeviceApplicationRun.RunningSupported method is implemented to test the availability of this feature. Developers can use this method to determine whether their mobile devices support running external applications.	The MobileDeviceApplicationRun object was not available on iOS and Windows platforms.	The platform behavior related to functionalities that are not available on some mobile devices or operating systems is unified across all platforms.
Managed forms.	In the Syntax Assistant, more information is added to the descriptions of Activate by default and Default button managed form items. The Unfilled selection mode property of managed form input fields is available in mobile platform forms. The Row selection mode property of managed form tables is no longer available in mobile platform forms.	The information in the Syntax Assistant was outdated. The availability of some properties of managed form input fields did not match the capabilities of the mobile platform.	Designer and Syntax Assistant now match the capabilities of the mobile platform.
Mobile application builder.	Data storage structure implemented in the mobile application builder is modified. When the mobile application builder is started for the first time after the update, the data conversion may take significant time.	Data storage structure implemented in the mobile application builder was different.	Data storage structure implemented in the mobile application builder is now more efficient.
Development tools.	When a debug server that does not support HTTP is specified in a mobile application, the error message clearly explains the problem: The mobile platform only supports debugging over HTTP.	When a debug server that did not support HTTP was specified in a mobile application, the error message did not clearly explain the problem.	Better problem diagnostics during mobile applicatiobn development.
Print tools.	In the mobile platform, the design of the page setup form is changed: The ОК button is moved to the window header. The duplicate Scale header is removed.	In the mobile platform, the design of the page setup form was different: The ОК button was located inside a form. The Scale header was duplicated.	Improved design of the page setup form.
Mobile device-specific features.	On iOS devices, receiving location updates when an application is running in background is not supported.	The option to receive location updates when an application is running in background on iOS devices was not documented.	Clarified the specifics of using mobile applications on iOS devices.

Library updates

The cURL library is updated to version 7.43 and modified to eliminate vulnerabilities.
The OpenSSL library is updated to version 1.0.2j and modified to eliminate vulnerabilities.
The libpng library is updated to version 1.6.21.
The libtiff library is updated to eliminate vulnerabilities.
The libxml2 library is updated to version 2.9.4 and modified to eliminate vulnerabilities.
The libxslt library is modified to eliminate vulnerabilities.

Table of contents

Transition from the previous version to the version 8.3.8

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.8.
Some features that are added in version 8.3.8 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.
When the Compatibility mode is set to None, the minimum supported version of Microsoft SQL Server is Microsoft SQL Server 2005 (this includes scenarios that use the Native Client).
In the file mode, infobase operations are optimized. To support the optimization, the file database data storage format is updated to new version 8.3.8 format. The option to change the page size of the infobase file (1Cv8.1CD) is implemented. The page size can have one of the following values: 4096, 8192, 16384, 32768, or 65536 bytes.
To migrate data between infobase formats, you can use a .dt file (provided that the target infobase has the required format) or convert the infobase file using cnvdbfl utility. The cnvdbfl utility can change the infobase file page size during the conversion.
If you migrate to a new 1C:Enterprise version:
- From version 8.3.7 or earlier, no action is reqiured.
- From version in range 8.3.8.1606 - 8.3.8.1861, it is recommended that after the migration you perform infobase verification and repair with the Check logical infobase integrity check box selected, or use the administration console utility (1cv8a) to verify and repair the infobase.
If your infobase contains objects that refer to exchange plan items and they can contain references to ThisNode item, it is recommended that you correct the references using the Replace references to incorrect ThisNode records data processor (read more). The data processor can use the result provided by the administration console (recommended) of the exchange plan record deletion marks as an input.
It is recommended that you run the cluster administration console (1cv8a) in verification and repair mode, with report generation enabled. Then use the report as an input for the Replace references to incorrect ThisNode records data processor.
When you migrate to 1C:Enterprise version 8.3.8 or later, it is recommended that you use the data processor available for download at 1c-dn.com (read more). The data processor determines whether totals recalculation for accumulation registers and accounting registers is required to correct errors in scenarios where a dimension list includes a dimension of String type and an index by dimensions includes more that 16 database fields.
If it is required, after the migration perform infobase verification and repair with Check logical infobase integrity and Recalculate totals check boxes selected, or use the cluster administration console (1cv8a). The latter option is recommended because it is faster.
After the migration from 1C:Enterprise version 8.3.5 to a later version you might get an error when retrieving characteristics. This is because the earlier versions of the platform allow specifying the Description field instead of the Parent field as a filter field for additional characteristic types of metadata objects. To correct the error, enter the correct value to the type filter field.
If your configuration includes HTTP services and you previously opened it with 1C:Enterprise Designer 8.3.4, when you open it with 1C:Enterprise 8.3.8, perform the following steps:
- Create any configuration object.
- Save the infobase configuration.
- Delete that configuration object.
- Save the infobase configuration.
To eliminate the issue with OpenID provider operations, in the default.vrd file for OpenID provider publication, add the required number of <returnto> elements with available redirection URLs.

Table of contents

Version 8.3.7

Version 8.3.7 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
Library updates
Transition from the previous version to the version 8.3.7

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.3.6 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4 and 8.3.5.	In version 8.3.7 you can run configurations created in version 8.3.6 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.7 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.6 for working with the infobase even after the transition to version 8.3.7. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
ZIP archive operations.	The ZipFileWriter and ZipFileReader objects are revised to improve stability during intense simultaneous work of a large number of users and to eliminate the issue with national characters in file names. ZIP archive support is implemented using the zipArchive library. The ZIPCompressionMethod.BZIP2 system enumeration value is implemented.	The ZipFileWriter and ZipFileReader objects had an issue related to intense simultaneous work of a large number of users, and an issue related to national characters in file names. The Info-ZIP library was used for ZIP archive support. The BZIP2 compression method was not supported.	Improved support of ZIP archives (including the support of national characters in file names). You can use the prevalent archive file format on Linux.
Development tools.	Configuration support settings management is available in Designer batch mode. The /ManageCfgSupport command-line option is implemented for Designer batch mode.	This feature was not provided. Configuration support settings management was only available in the interactive mode.	Simplified automated building and testing of applied solutions.
Internet-enabled functionality. Web services and HTTP services.	You can use OS authentication for Internet operations and web services. When a WS-reference is created in Designer, the OS authentication option cannot be disabled. When the list of infobases is retrieved using a web service, OS authentication is used, unless the URL contains authentication data. OS authentication is not supported on Linux. For the InternetProxy object, the option to enable or disable OS authentication for each protocol is implemented. This change is not implemented in 8.3.6 compatibility mode. The UseOSAuthentication parameter is implemented for constructors of the following objects: HTTPConnection, WSDefinitions, and WSProxy. The UseOSAuthentication property is implemented for the following objects: HTTPConnection and WSProxy. For the WSReferenceManager.CreateWSProxy() method, the UseOSAuthentication option is implemented. For the InternetProxy.Set() method, the UseOSAuthentication option is implemented. For the InternetProxy object, the UseOSAuthentication() method is implemented.	OS authentication was not implemented for Internet operations and web services. OS authentication was never used for retrieving a list of infobases using a web service. For the InternetProxy object, basic authentication was used, provided that the user name and password were set.	Extended capabilities for web service operations, Internet operations, and retrieving the list of infobases in corporate environments.
Web services and HTTP services.	You can use a web service whose address is different from the address specified in a WSDL file imported to the applied solution (a WS-reference object). For the WSProxy object constructor, the Location parameter is implemented. For the WSReferenceManager.CreateWSProxy() method, the Location parameter is implemented.	This feature was not provided. A web service could be used only if it was located at the address specified in a WSDL file imported to the applied solution (a WS reference configuration object).	New usage options for Web services in scenarios where a web service has a fixed interface but can be located at different addresses in the Internet. For example, you can use a web service of some broadly used applied solution.
JSON support. XML and XDTO support.	XDTO objects can be serialized to JSON.	This feature was not provided. Only streaming API and object model were supported for JSON.	Simplified usage of JSON format for exchange between various 1C:Enterprise-based systems.
JSON support.	When data is written in JSON format, slash marks (/) can be escaped. For the JSONWriterSettings constructor, the EscapeSlash parameter is implemented. For the JSONWriterSettings object, the EscapeSlash property is implemented. The EscapeSlash property is used by the JSONWriter.WriteValue() method.	The option to enable or disable escape of slash marks in JSON operations was not available.	Better compatibility with external systems that use exchange in JSON format.
Localization.	The NumberInWords() and PeriodPresentation() global context methods support the Azerbaijani language. The language code is az. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant.	The NumberInWords() and PeriodPresentation() global context methods did not support the Azerbaijani language.	Simplified implementation of data presentation for Azerbaijani-speaking users.
Localization.	The NumberInWords() and PeriodPresentation() global context methods support the Turkish language. The language code is tr. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant.	The NumberInWords() and PeriodPresentation() global context methods did not support the Turkish language.	Simplified implementation of data presentation for Turkish-speaking users.
Localization.	The NumberInWords() and PeriodPresentation() global context methods support the Hungarian language. The language code is hu. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant.	The NumberInWords() and PeriodPresentation() global context methods did not support the Hungarian language.	Simplified implementation of data presentation for Hungarian-speaking users.
Spreadsheet documents.	When a spreadsheet document is exported to XLS (Microsoft Excel 97-2003) format, Microsoft Office OpenXML (Microsoft Excel 2007- 2010) format, or ODS (OpenDocument Spreadsheet) format, the following print settings are exported to the resulting file: Margin sizes Header sizes Page orientation Page size Scale Black-and-white option Print area Columns and rows that are repeated on each page Header text This change is not implemented in 8.3.6 compatibility mode.	When a spreadsheet document was exported to XLS (Microsoft Excel 97-2003) format, Microsoft Office OpenXML (Microsoft Excel 2007- 2010) format, or ODS (OpenDocument Spreadsheet) format, its print settings were not exported.	More accurate export of spreadsheet documents to popular spreadsheet document formats.
Configuration extensions.	In configuration extensions, you can create WS references, XDTO packages, web services, and HTTP services. You can publish Internet services belonging to configuration extensions to web servers. In the default.vrd file, the publishExtensionsByDefault attribute is implemented for ws and httpServices elements.	This feature was not provided.	New functionality introduced for configuration extensions.
OData interface.	You can use independent information registers that do not have dimensions in the standard OData interface. The SurrogateKey property is implemented.	This feature was not provided.	The 1C:Enterprise object implementation better complies with the OData standard.
Background and scheduled jobs.	You can quickly determine whether the current session is a background job session. The GetCurrentInfoBaseSession() global context method is implemented. The InfoBaseSession.GetBackgroundJob() method is implemented.	This feature was not provided. The only way to determine the session type was getting all infobase sessions and iterating through them.	Optimized procedure for determining whether the current session is a background job session. This is handy in such scenarios as dividing initialization scripts for client applications and background jobs.
DBMS operations.	Dumping an infobase to a .dt file is interrupted if any issues related to the internal infobase structure are encountered.	Dumping an infobase to a .dt file did not include a verification of the internal infobase structure.	Reduced chance of obtaining a .dt file that cannot be loaded.
Common objects.	The option to read and write data in a scenario where synchronous calls are not allowed is implemented for the following objects: TextDocument, SpreadsheetDocument, FormattedDocument, GraphicalSchema, and RepresentableDocumentBatch (write operation only). The BeginWriting() method is implemented for the following objects: TextDocument, SpreadsheetDocument, FormattedDocument, and GraphicalSchema. The BeginReading() method is implemented for the following objects: TextDocument and GraphicalSchema. The RepresentableDocumentBatch.BeginWritingFileForPrinting method is implemented.	These features were not provided.	The missing functionality is implemented for compatibility with the recent Google Chrome changes.
Cryptography support.	For the Issuer and Subject properties of the CryptoCertificate object the option to get access to all certificate fields that describe issuer and subject is implemented. For the Issuer and Subject properties of the CryptoCertificate object the Street field is implemented. Each of the Issuer and Subject structure fields of the CryptoCertificate object is accessible by: Mnemonic key (for example, CN) UUID key (for example, OID2_5_4_3 for the CN field).	The Issuer and Subject properties of the CryptoCertificate object did not provide access to all certificate fields.	All certificate fields can be accessed, even those that are present due to regulator requirements.
DBMS operations.	When the platform attempts to build an index by more than 3 string fields in Oracle DBMS, it automatically creates V81C_INDEX_BIG tablespace.	When the platform attempted to build an index by more than 3 string fields in Oracle DBMS, if V81C_INDEX_BIG tablespace was missing, an error was generated. Creating the tablespace manually eliminated the error.	The need to create the tablespace manualy is eliminated.
Configuration extensions. Predefined data.	The option to adopt predefined data items is implemented for configuration extensions. This makes the following operations available: check extensions for availability of predefined data items, check whether extension exchange plan content and object registration rules include predefined data items, and use extension predefined items in the query builder.	This feature was not provided.	Expanded configuration extension functionality.
Development tools.	The option to dump configurations to hierarchical file structures, as well as restore them from such file structures, is implemented. Name length for new configuration objects is limited by 80 characters. Existing configuration objects can have names longer than 80 characters until you attempt to edit their names. 1C:Enterprise script modules are dumped to .bsl files. In the dump configuration files dialog box you can select the dump format: flat or hierarchical. The Format parameter is implemented for /DumpConfigToFiles Designer batch mode command-line option. The new parameter describes the dump format. By default configurations are dumped to hierarchical file structures.	Configurations were always dumped to flat file structures. No length restrictions were applied to configuration object names. 1C:Enterprise script modules were dumped to .txt files.	Chance of configuration dump procedure being terminated due to length of the output file path and name exceeding the file system limits is significantly reduced (file names are derived from configuration object names).
Development tools.	A configuration can be partially restored from files. The following operations are available: adding, modifying, deleting, and renaming configuration objects and modifying some properties of configuration objects (such as their modules or help topics). You can simultaneously load a configuration from files and update database configuration. For the /LoadConfigFromFiles Designer batch mode command-line option, the following parameters are implemented: -files (files to load) and -listfile (file containing a list of files to load). In the technological log, the CONFLOADFROMFILES event is implemented.	This feature was not provided. Only restoring the entire configuration from files was available.	Better performance of configuration updates in scenarios where a configuration is stored in an external system.
Development tools.	New debug option is available: debugging over HTTP. Developers can select this option in Designer. The dialog box with automatic debug item attachment settings is refactored. Debug server (dbgs) is implemented, it can be started from the command line, and also as an operating system service. The new debug protocol is not supported on Linux servers in the scenario where 1C:Enterprise starts automatically during operating system startup. The following command-line options are implemented for the server agent (ragent): /debug, /debugServerAddr, /debugServerPort, and /debugServerPwd. For the client application the following command-line option is implemented: /debug. In default.vrd file, for the <debug> element, the protocol attribute is implemented. In comcntrcfg.xml file, for the <config> element, the protocol attribute is implemented. This option is implemented as beta version.	A single debug option was available.	You can debug applied solutions when HTTP is the only available connection protocol. This expands Debugger functionality.
Localization.	The option to localize only a part of 1C:Enterprise platform interface required for a specific applied solution is implemented. Localization tools that support this option are available upon request from 1C Company at MAIL:int@1c.com. This option has the following limitations: Pictures cannot be localized. The option to build a platform distribution kit is not provided.	Only the full localization option was available. Localizations were always delivered as part of the platform distribution kit.	The option to localize the platform interface for specific applied solutions or specific delpoyments is implemented. This option is in demand by users whose native languages are not included in the list of platform localization languages.
Development tools.	Designer help includes the list of executable files of predefined external tools used for comparing and merging modules. It is recommended that you specify these names in the settings for comparing and merging modules with external tools.	Designer help did not include executable file names of predefined external tools used for comparing and merging modules.	Improved Designer help.
Dumping/loading configurations to files.	Versioning is implemented for the format of dumping configurations to files. 1C:Enterprise 8.3.6 has dump format version 1.0, and 1C:Enteprise version 8.3.7 has dump format version 2.0. If the dump files do not include a version number, they are treated as version 1.0-compliant. Files are always dumped in the format that matches the 1C:Enterprise platform version. A configuration can be restored from files only if the version of the files is earlier than or equal to the version supported by the 1C:Enterprise platform.	Versioning was not available for the format of dumping configurations to files.	Some issues related to the incompatibility of dump files generated by different 1C:Enterprise versions are eliminated.
Dumping/loading configurations to files.	The method of dumping the Parameter property of the Button managed form item to files is changed. If the Parameter value references a configuration object, the full name of that configuration object is dumped to files.	The Parameter property of the Button managed form item was dumped as a UUID of the configuration object type if the Parameter property referenced a configuration object.	Eliminated the configuration dump format inconsistency.
Administration tools.	Applied solution license validity check is implemented at 1C:Enterprise platform level. The check is performed for applied solutions running in file mode, and it is also performed on the server for 1C:Enterprise 8.3 Server MINI. The license validity check is not performed for applied solutions that use the base version of 1C:Enterprise. The check involves an Internet connection to the Update Validation Center. The result of the check is displayed in the About 1C:Enterprise dialog box. The Designer interface includes new commands related to this functionality. The following global context methods are implemented: GetConfigurationID, GetLicensingClientName, GetLicensingClientAdditionalParameter, SetLicensingClientParameters, AttachLicensingClientParametersRequestHandler, and DetachLicensingClientParametersRequestHandler. For the conf.cfg configuration file, the LicConfigDebugTimeouts parameter is implemented. The parameter is used to reduce the check interval. The implementations of this functionality are subject to future announcement.	This feature was not provided.	The option to perform a license validity check after updating an applied solution is implemented.
DBMS operations.	Support of Oracle Database version 12.1.0.2 (Linux) is implemented.	This Oracle Database version was not supported.	Extended list of supported Oracle Database versions.
Designer. Client application. Cross-platform architecture. System requirements.	The client application for OS X 10.8 or later is available (64-bit version only). It supports the following features: Thin client, thick client, and Designer File and client/server modes Running 1C:Enterprise server on OS X is not supported. The limitations of the OS X client application are provided in the documentation. Installation and simultaneous work of multiple 1C:Enteprise versions is supported. This option is implemented as beta version.	Infobase access via a web client was available on OS X.	You can develop applied solutions and run client applications on OS X.
System requirements.	Astra Linux Special Edition 1.4 is supported.	This release was not supported.	New Linux release is supported.
Add-ins.	The English description of the add-in development technology is provided as an HTML document. This document is available for download for each platform version as a part of 1C:Enterprise platform 8.3 Add-in technology archive.	The description of the add-in development technology available for download as a part of 1C:Enterprise was only provided in Russian.	Better accessibility of add-in development documentation.
ZIP archive operations.	File names in ZIP archives generated by 1C:Enterprise have both UTF-8 encoding and the current operating system encoding (if is not UTF-8). The ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, read ZIP archives correctly even when the file names inside the archives contain non-English characters. Note that the built-in decompression program for OS X displays file names in such archives incorrectly.	File names in ZIP archives generated by 1C:Enterprise had UTF-8 encoding only. The ZipFileReader object in 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs in Windows XP/2003/2008/7, displayed file names with non-English characters inside ZIP archives incorrectly.	The ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, read ZIP archives correctly even when the file names inside the archives contain non-English characters. Note that the built-in decompression program for OS X displays file names in such archives incorrectly.

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Interface.	In the Taxi interface, when an item is deleted from the Favorites list, a modal confirmation dialog box is no longer displayed. After the deletion, a link for restoring the deleted item is displayed in the Favorites panel.	In the Taxi interface, when an item was deleted from the Favorites list, a modal confirmation dialog box was displayed.	The Favorites pane functionality is fully supported in web browsers that do not support modal dialog boxes.
Interface.	In the Taxi interface, you can pin forms in the main window work area (so that a form is always available). You can also combine two forms in order to have them always displayed together when any of the two forms is opened. In the system menu, context menu of the opened windows panel, and form title context menu, the corresponding commands are implemented.	This feature was not provided.	Improved platform usability. For example, users have the option to compare two instances of a single report featuring different periods.
Data display.	Web service authentication error messages no longer contain HTML text returned by the web server, at no cost to message information value.	Web service authentication error messages contained HTML text returned by the web server.	All information that was not user-friendly is removed from web service authentication error messages
Interface.	Replacement of style elements with actual fonts and colors is improved in some scenarios.	In some scenarios, replacement of style elements with actual fonts and colors was performed incorrectly.	Eliminated unexpected system behavior.
Client application.	The client application help includes the description of the keyboard shortcut Ctrl+Shift+H, which opens the history panel.	Description of this shortcut was not available in the client application help.	Client application help is up-tp-date.
Web client.	In Google Chrome web browser, access to clipboard using context menu commands is implemented (in addition to the previously available keyboard shortcuts). This options requires installing a browser extension. The web client propmts the user to install the extension first time they attempt to access the clipboard using context menu commands. If the extension is not installed, the clipboard can be only accessed using keyboard shortcuts.	In Google Chrome web browser, the clipboard could only be accessed using keyboard shortcuts. Clipboard access using context menu commands was not supported.	Improved web client usability in Google Chrome.
Web client.	New version of the browser extension for Mozilla Firefox is available. The extension only supports asynchronous operations. The synchronous methods are no longer supported.	Another version of browser extension for Mozilla Firefox was available. It supported synchronous operations.	Support of Mozilla Firefox versions 40 and later, which do not support synchronous operations (just like Google Chrome versions 45 and later), is implemented.

Table of contents

Functionality	After	Before	Result of changes
Development tools.	The performance of the following Designer operations is improved: Opening a subsystem editor window Including an object into a subsystem Setting a filter by subsystem in the configuration tree window	The performance of some Designer operations was insufficient.	Streamlined execution of some Designer operations.
Geographical schemas.	The following geographical schema operations are optimized: Loading and rendering geographical schemas Selecting an object in a geographical schema field	The performance of some geographical schema operations was insufficient.	Improved usability of geographical schemas.
Full-text search.	Improved performance of full-text search and of building the full-text search index.	Insufficient performance of full-text search and of building the full-text search index.	Improved performance of full-text search and of building the full-text search index. The improvement is noticeable if the infobase contains indexed objects with a large number of words.
Full-text search. Dynamic lists.	In dynamic lists, the performance of the search initiated from the search string is improved in the following scenario: the full-text search is enabled for the dynamic list main table and filters with Equal to comparison type are applied to the main table fields.	In dynamic lists, the performance of the search initiated from the search string was insufficient.	In dynamic lists, improved performance of the search initiated from the search string.
Queries.	When a query that accesses only tabular section data is executed, the retrieved table is not joined to the parent object table.	When a query that accessed only tabular section data was executed, the retrieved table was automatically joined to the parent object table.	Eliminated unexpected system behavior.
DBMS operations.	Improved performance of reading objects of the following types from DBMS: DocumentObject, CatalogObject, BusinessProcessObject, TaskObject, ChartOfCalculationTypesObject, ChartOfCharacteristicTypesObject, ExchangePlanObject, and ChartOfAccountsObject. Reading any of these objects is followed by implicit transaction creation only if the object has tabular sections and "dirty read" outside of transactions is allowed in the DBMS.	Reading objects of the following types from the DBMS was followed by implicit transaction creation if the object had tabular sections: DocumentObject, CatalogObject, BusinessProcessObject, TaskObject, ChartOfCalculationTypesObject, ChartOfCharacteristicTypesObject, ExchangePlanObject, and ChartOfAccountsObject.	The following values are reduced: Number of data lock waits in the file DBMS. Time required for loading an infobase object from a DBMS in the client/server mode. Number of waits due to internal 1C:Enterprise server locks during bulk reading of infobase objects from a DBMS. DBMS load (due to a significant decrease of the number of transactions).
Managed forms.	Improved performance of managed form conditional appearance. Faster opening of managed forms with a large number of conditional appearance items.	Insufficient performance of managed form conditional appearance.	Improved performance of opening managed forms, especially for file mode infobases and on low-performance computers.
Predefined data.	Improved performance of retrieving predefined data using the PredefinedValue() method.	Insufficient performance of retrieving predefined data using the PredefinedValue() method.	Improved performance of processing predefined data.
Development tools.	The configuration database update time is reduced for configurations that include a large number of roles, provided that the update does not require database restructuring.	The configuration database update required significant time for configurations that included a large number of roles, provided that the update did not require database restructuring.	Reduced database configuration update time.
Managed forms. 1C:Enterprise script.	The performance of opening managed forms is improved in the thin client and web client.	The performance of opening managed forms in the thin client and web client was insufficient.	Improved platform performance.
Platform algorithms.	Internal caching algorithms of 1C:Enterprise are optimized. This improves the performance of many 1C:Enterprise features, including the following: Form opening Queries Functional options Predefined data Reusable return values Data access using "." (dot)	System performance was suboptimal.	Improved platform performance, especially for infobases running in the file mode and on computers with limited RAM (less than 4 GB).
Data access restrictions.	Query execution is optimized for users that do not have full rights in configurations that use access restrictions and have a large number of roles. The query execution time is not significantly affected by the number of roles assigned to a user.	Query execution time was insufficient for users that did not have full rights in configurations that used access restrictions. The query execution time was significantly affected by the number of roles assigned to a user.	Improved performance of configurations with a large number of roles (including form opening performance).
Dynamic lists. Full-text search.	When a dynamic list is searched from a search box by fields that do not belong to the main dynamic list table, full-text search by source objects of the fields is performed first. Fields of objects where nothing is found by the full-text search are excluded from further search.	When a dynamic list was searched from a search box, additional conditions were applied to all fields displayed in the table linked to the dynamic list.	Improved performance of search in dynamic lists in some usage scenarios.
Queries.	In the query language, expressions that include both comparison operators and CASE operators that return only constant values are optimized. The optimization simplifies expressions or their parts.	In the query language, optimization was not available for expressions that included both comparison operators and CASE operators that returned only constant values.	Improved query performance in some scenarios.
Full-text search.	The performance of the input by string feature is improved. The full-text search index data structure is modified. Full-text search index is created in the new format. To convert the index to the new format, clear the index, ensure that the Compatibility mode configuration property is set to Do not use, and then generate the index. The <INPUTBYSTRING> technological log event is implemented, it is used for monitoring events related to input by string. This change is not implemented in 8.3.6 compatibility mode.	The performance of the input by string feature was insufficient. Full-text search index had a different format.	Improved performance of the input by string feature, which, in turn, improves the usability of all platform objects that use this feature.
Automated testing.	In the web client running in the testing client mode, the performance of test scenario commands is improved.	In the web client running in the testing client mode, the performance of test scenario commands was insufficient.	Improved performance of automated testing in the web client.
Data exchange. Common attributes / Data separation.	Improved performance of initial infobase image creation in scenarios where the exchange plan used to create the initial image includes a register that is included in independent separator content (provided that separator is not used in the current session).	The performance of initial infobase image creation in scenarios where the exchange plan used to create the initial image included a register that was included in independent separator content (provided that separator was not used in the current session) was insufficient.	Improved performance of initial image creation in some scenarios.
Common objects.	The algorithms of the following methods are optimized: QuerySchemaAvailableTables.Find(), QuerySchemaSources.Add(), and QuerySchemaTableParameters.Count().	The performance of QuerySchemaAvailableTables.Find(), QuerySchemaSources.Add(), and QuerySchemaTableParameters.Count() methods was insufficient.	Improved performance of query schema operations in 1C:Enterprise script.
Development tools.	Operations in the configuration command interface editor form are optimized for scenarios with a large number of roles. The performance of moving table rows is improved.	The performance of operations in the configuration command interface editor form was insufficient in scenarios with a large number of roles.	Improved usability for application developers that edit the command interface of configurations with a large number of roles.
DBMS operations. Calculation registers.	Both in PostgreSQL and IBM DB2, in scenarios where large calculation register record sets are deleted, deletion of records storing actual action periods is performed faster. This change is not implemented in 8.3.6 compatibility mode.	Both in PostgreSQL and IBM DB2, in scenarios where large calculation register record sets were deleted, deletion of records storing actual action periods was impaired.	Both in PostgreSQL and IBM DB2, optimized deletion of large calculation register record sets.
Spreadsheet documents.	The performance of setting the size and position of spreadsheet document pictures at 1C:Enterprise server side is improved.	The performance of setting the size and position of spreadsheet document pictures at 1C:Enterprise server side was insufficient.	Improved performance of spreadsheet document generation in scenarios where the size and position of spreadsheet document pictures are set from 1C:Enterprise script.
Managed forms. Web client. Server clusters.	The performance of opening managed forms is improved in the following scenario: the web client is running in client/server mode and the server cluster is deployed on a Linux computer.	The performance of opening managed forms was insufficient in the following scenario: the web client was running in client/server mode and the server cluster was deployed on a Linux computer.	Improved web client performance for Linux server clusters.

Changes that affect system behavior

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

Table of contents

Changes that require modification of configuration and administrative settings

Table of contents

Object	The old name	The new name
Spreadsheet document property that describes the language for displaying and editing the document. The former name is supported for compatibility purposes.	TemplateLanguageCode.	LanguageCode.
Presentations of automatically generated graphical schema field command groups. The command groups are displayed in the form customization dialog box in 1C:Enterprise mode.	Size and alignment group (contains the Align left command) Size and alignment group (contains the Align top command) Group group (contains the Auto space: horizontal command) Group group (contains the Bring to front command) Group group (contains the Send to back command)	Horizontal alignment Vertical alignment Distribute Bring forward Send backward

Functionality	After	Before	Result of changes
Development tools.	The option to debug configurations on the mobile platform is implemented. The debugging can only be performed over HTTP (you can select this option in Designer).	This feature was not provided.	Streamlined development of applied solutions for the mobile platform.
Print tools.	The Print mobile application extension, which is used for printing from mobile applications, is implemented. The mobile application builder supports building mobile applications that require this extension.	This feature was not provided.	Reduced list of required permissions for mobile applications that do not require printing.
Spreadsheet documents.	The brightness of frozen spreadsheet document areas is reduced by 2.5%.	The brightness of frozen spreadsheet document areas was reduced by 10%.	Better look and feel of spreadsheet documents with frozen areas.
1C:Enterprise script.	The following string processing functions previously available for the personal computer platform are now implemented for the mobile platform: StrTemplate(), StrCompare(), StrStartWith(), StrEndsWith(), StrFind(), SrtSplit(), and StrConcat(). The SearchDirection system enumeration is implemented.	This feature was not provided.	Unified string processing for the personal computer platform and the mobile platform.
Managed forms.	The Representation property of a managed form button located in a form title command bar affects the button view. When the platform defines the button view, it ignores the properties of the command linked to the button.	The Representation property of a managed form button located in a form title command bar did not affect the button view. When the platform defined the button view, it ignored the properties of the command linked to the button.	You can manage the view of buttons located in form title command bars using the button properties.
Special tools.	For the TelephonyTools.NumberDialingSupported() method the DirectCall parameter is implemented. The parameter streamlines the check for number dialing support.	The TelephonyTools.NumberDialingSupported() method did not support any check options.	Унифицирована возможность проверки работы со специальными возможностями на мобильной платформе.
System requirements.	Support of Windows Phone operating system version 8.1 or later (ARM and x86 architectures) and touch devices that run Windows version 8.1 or later (ARM and x86) is implemented. The mobile platform for Windows Phone supports all mobile platform features available on other operating systems, excluding: Conversion of geographical coordinates to addresses and back, and ShowOnMap() global context method Barcode scanning Phone call log Printing Receiving text messages Notifications Contacts Calendars The mobile platform specifics are described in the documentation. The mobile platform distribution file mobile.zip is complemented with new data. This option is implemented as beta version.	This feature was not provided.	Extended support of operating systems for mobile and touch devices.
Mobile application builder.	Mobile application builder for Windows Phone operating system is implemented. It supports Windows Phone 8.1 or later. New builder parameters are added: The option to build applications for Windows operating system Support of graphic assets required for Windows operating system Publishing of built applications to Windows Store is not supported. When loading mobile platform data from the mobile.zip file to mobile platform builder, you have the option to load only mobile operating systems that are present in the archive. The option to specify different application IDs for different mobile operating systems is supported. The option to export developer certificates from the mobile application builder database is implemented.	Mobile application builder did not support Windows operating system. Attempts to load the mobile platform from the mobile.zip file to mobile application builder were only successful if the file contained platform versions for both Android and iOS. A single mobile application ID was assigned for Android and iOS builds. Exporting developer cerificates from the mobile application builder database was not supported.	Mobile application builder supports Windows operating system, and features other improvements.
Command interface. Managed forms.	On the mobile platform, the Show in list command, which was perviously available only on the personal computer platofrm, is implemented. The ManagedForm.ExecuteNavigation() method and the NavigationProcessing managed form event are implemented.	This feature was not provided.	The interfaces of the mobile and personal computer platforms are unified.
Web services and HTTP services.	On the mobile platform, the option to use a web service whose address does not match the address specified in a WSDL file imported to the applied solution (WS-reference configuration object) is implemented.	This feature was not provided.	Web servfice operations on the mobile and personal computer platforms are unified.
Managed forms.	On the mobile platform, the option to use a selection list to provide a value for a managed form input field that displays date and time is implemented.	On the mobile platform, drop-down lists were not available.	On the mobile platform, the option to use drop-down lists in the input fields that display date and time is now available.
Managed forms.	The option to switch between the input fields using the Enter button of the virtual keyboard (i.e. without closing the keyboard) is implemented. The option to switch between the input fields using Tab/Shift+Tab keys of a physical keyboard connected via Bluetooth is also implemented.	The option to switch between the input fields without closing the virtual keyboard was not available. To switch between the fields, a mobile application user had to close the keyboard, then switch to another field, and then open the keyboard.	Improved mobile application usability is scenarios where multiple input fields are available in a single form.

Library updates

Known vulnerabilities of cURL library are elimitaned.
The OpenSSL library is updated to version 1.0.0t.
The libxml2 library is updated to eliminate vulnerabilities.
The libxslt library is updated to eliminate vulnerabilities.

Table of contents

Transition from the previous version to the version 8.3.7

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.7.
Some features that are added in version 8.3.7 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.
In order to use the new format of full-text search index and improve the performance of the input by string feature, clearing the full-text search index and building a new index is required. The Compatibility mode property must be set to None during these operations.
In the web client, the cryptography extension is required in order to access all certificate fields using the Issuer and Subject properties of the CryptoCertificate object.

Table of contents

Version 8.3.6

Version 8.3.6 includes known bug fixes and functionality modifications.

To obtain a link to an entry of the V8Update file, double-click any of the entry lines. This opens a pop-up window with the link available for copying to the clipboard. This feature is only available if JavaScript is enabled.

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
Library updates
Transition from the previous version to the version 8.3.6

New functionality and changes

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.3.5 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3 and 8.3.4.	In version 8.3.6 you can run configurations created in version 8.3.5 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.6 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.5 for working with the infobase even after the transition to version 8.3.6. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Development tools.	In Designer, in module text, bookmarks can be preserved between different work and module editing sessions. To access the full list of bookmarks, on the Edit menu, click Bookmarks.	This feature was not provided.	Improved Designer usability,
Development tools.	When renaming a configuration object, you have the option to update the object name usage instances in the entire configuration. When deleting a configuration object, you have the option to search for the object name usage instances in the entire configuration. When modifying or deleting a managed form item, attribute, or parameter, the check for usage instances of its name in the form module is performed. When renaming an item, attribute, or parameter, you have the option to update its name usage instances in the form module. The Find references to object operation now includes the search in module texts. You can specify whether you want to use these options in the Designer options window.	These features were not provided.	Reduced chance of making errors when renaming or deleting configuration objects. Improved usability for developers.
Managed forms.	Planner (a visual tool for managing schedule data) is implemented. A new "planner field" type is implemented for managed form fields. The Planner object is implemented. In the TimeScalePosition system enumeration, the following values are implemented: Left and Right (when applied to a Gantt chart, both are treated as Top).	This feature was not provided.	Improved user experience for scheduling (appointments, calendars, and so on).
Configuration repositories.	In Designer batch mode, you can bind an infobase that is not yet bound to the configuration repository (command-line option /ConfigurationRepositoryBindCfg).	This feature was not provided. Infobases could be bound to repositories only interactively.	You can automate more configuration repository operations.
Command interface. Managed forms.	For managed form extensions for objects, catalogs, documents, charts of characteristic types, business processes, tasks, and information register records, the Show in list command is implemented. For managed forms, the ExecuteNavigation() method and NavigationProcessing event handler are implemented.	This feature was not provided.	Improved system usability for automatic object selection in a list being opened.
System enumerations. Client application.	For the SectionsPanelRepresentation system enumeration, the following values are implemented: PictureOnTopAndText and PictureOnLeftAndText. In the client application, in the sections panel editor, the following section view features are available: In Version 8.2 interface compatibility mode: Picture Text PictureAndText In Taxi interface compatibility mode: Picture Text PictureAndText PictureOnTopAndText	For the SectionsPanelRepresentation system enumeration, the following values were available: Picture, Text, PictureAndText.	Extended section view capabilities for the sections panel in the Taxi interface.
Managed forms.	The option to specify a graphical schema field as a source of command bar and managed form button commands is implemented. The only commands available in the web client are print and preview. In the Russian interface some of the graphical schema commands are renamed to the following: Выровнять по левому краю Выровнять по правому краю Выровнять по верхнему краю Выровнять по нижнему краю Переместить вперед Выровнять по центру Выровнять по середине	The option to specify a graphical schema field as a source of command bar and managed form button commands was not provided. In the Russian interface some of the graphical schema commands had different names: Выровнять влево Выровнять вправо Выровнять вверх Выровнять вниз Переместить вверх Выровнять по центру горизонтально Выровнять по центру вертикально	Increased graphical schema usability.
Administration tools.	An object integrity check utility is implemented. It checks the state of file system objects and database objects used by 1C:Enterprise and monitors their changes. The 32-bit and 64-bit versions of the utility are available for Windows and Linux operating systems.	This feature was not provided. File change monitoring was only available using third-party tools. Monitoring of database object changes was not available.	The option to perform system integrity checks to provide protection against unauthorized modifications is implemented.
Internet-enabled functionality.	For the Get() method of the InternetMail object, the MarkAsRead parameter is implemented. This parameter only makes sense when the platfrom uses IMAP for email operations. If the platform uses POP3, an attempt to use this parameter when it is set to False generates an exception. The platform behavior in 8.3.5 compatibility mode is not changed (for the part where the parameter is set to False).	If the platform used IMAP for email operations, the execution of the Get() method of the InternetMail object gave different results depending on the value of the ArrayOfMessageHeadersOrIdentifies parameter. If the parameter was not specified, the flag indicating whether a message was read was not set for messages retrieved from the mail server. If the parameter was specified, the flag was set.	Eliminated inconsistency in the platform behavior during email operations that use IMAP.
Technological log.	For the SCALL and CALL technological log events, new IName and MName fields are implemented. They store additional internal system call data. 1C Company experts might use that data while handling support requests.	This feature was not provided.	The technological log provides additional data that can be helpful for solving complex issues.
Dynamic lists.	The option to get data from a dynamic list (adjusted for column visibility settings and search options applied) is implemented. The following methods are implemented for the managed form table extension for dynamic lists: GetPerformingDataCompositionScheme() GetPerformingDataCompositionSettings()	This feature was not provided.	The option to get dynamic list data that is visible to a user for future processing is available.
Data composition system.	The following subordinate fields are implemented for data composition system fields that have Data among their types: BegOfDay, BegOfWeek, BegOfTenDays, BegOfMonth, BegOfQuarter, BegOfHalfYear, BegOfYear, EndOfDay, EndOfWeek, EndOfTenDays, EndOfMonth, EndOfQuarter, EndOfHalfYear, EndOfYear, Day, WeekDay, WeekDayName, DayOfYear, WeekOfYear, Month, MonthName, Quarter, Year, BegOfMinute, BegOfHour, EndOfMinute, EndOfHour, Minute, and Hour.	This feature was not provided. One could use user-defined expression fields to retrieve this data.	Simplified end-user operations with fields that include date and time.
1C:Enterprise script.	The following string processing functions are implemented: StrTemplate() - replaces variables (such as %1) in a template string by actual values. StrCompare() - performs lexicographic comparison of strings, case-insensitive. StrstartWith() - checks whether a string begins with a substring. StrEndsWith() - checks whether a string ends with a substring. StrFind() - searches for a substring in both directions, anywhere in the line. SrtSplit() - splits a string into substrings based on the specified delimiter. StrConcat() - merges strings included in the array of substrings. The SearchDirection system enumeration is implemented. The Find() function is declared obsolete, it is supported for compatibility purposes. This change is not implemented in 8.3.5 compatibility mode.	This feature was not provided. Developers had the option to implement the functionality introduced in the new functions using 1C:Enterprise script.	Simplified implementation of some standard string processing algorithms.
Web client.	Storing accumulated web client statistics is implemented. This feature is intended for 1C Company experts. To enable it, run the web client with the SYSTEMWEBCLIENTSTAT command-line option.	This feature was not provided.	The set of tools intended for platform performance quality control is expanded with a new tool.
Spreadsheet documents.	Importing data from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument) formats to spreadsheet documents is implemented. This operation can be performed both interactively and from 1C:Enterprise script. The SpreadsheetDocumentValueReadingMode system enumeration is implemented. For the Read() method of the SpreadsheetDocument object, the ValueReadingMode parameter is implemented. Support of pasting areas copied to the clipboard from Microsoft Excel and OpenOffice Calc documents is implemented.	This feature was not provided.	Simplified data import from spreadsheet documents of the following formats: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument).
Data composition system. Dynamic lists.	For the DataCompositionSettingsComposer object. the GetAvailableSettingsSource() method is implemented.	This feature was not provided.	Simplified access to the available settings source of a data composer from another data composer. For example, you can use this feature when you open a new data composition settings editor form that uses the same source as the previous form.
Internet-enabled functionality. Web services and HTTP services.	You can process JSON data using both stream and object approaches. The following objects can be serialized to or deserialized from JSON: primitive types, Array, FixedArray, Structure, FixedStructure, Map, and FixedMap. The JSONReader and JSONWriter objects are implemented. The WriteJSON(), ReadJSON(), WriteJSONDate(), and ReadJSONDate() global context methods are implemented.	This feature was not provided. One could implement processing JSON data using 1C:Enterprise script tools.	Simplified interaction with applications (including web applications) that use JSON data format. You can store various data types in JSON format, which provides an alternative to other formats, such as XML.
Web services and HTTP services.	Web services and HTTP services. For the standard OData interface, getting responses in JSON format is implemented.	This feature was not provided. For the standard OData interface, responses were only available in Atom format.	The OData format is supported in more detail. Using JSON format minimizes the volume of data transferred between the client and the server.
Queries.	You can use logical expressions in descriptions of selection fields and in query result filter expressions (in the WHERE clause).	This feature was not provided. If a logical expression was required for describing a selection field, you had to use a selection clause. Logical expressions in the WHERE clause could be connected only by AND, OR, and NOT logical operators, and they could not be composite.	Simplified writing and understanding of complex queries.
Server clusters. Administration tools.	The automatic server cluster status monitoring feature is implemented. This includes monitoring of several cluster parameters and termination of processes that might cause any issues. The central cluster server agent performs the monitoring. The monitoring results are recorded to the technological log. For the cluster, the Server errors threshold and Terminate corrupted processes properties are implemented. For the IServerAgentConnection object, the SetClusterRecyclingErrorsCountTheshold() and SetClusterRecyclingKillProblemProcesses() methods are implemented. For the rac utility, the --errors-count-threshold and --kill-problem-processes command-line options are implemented. For the technological log, the ATTN event is implemented.	Automatic server cluster status monitoring was not provided.	Increased server cluster reliability by timely detection and termination of processes that might cause issues.
Automated testing.	The automated testing supports the Taxi interface. New automated testing features are added: For the TestedClientApplicationWindow, the StartPage property is implemented. Navigation between windows is implemented. For the TestedClientApplicationWindow object, the GotoStartPage(), GotoNextWindow(), GotoPreviousWindow(), and CloseUserMessagesPanel() methods are implemented. New options for testing managed form fields: Create an item. For the TestedFormField object, the Create() method is implemented. Cancel editing field data. For the TestedFormField object, the CancelEdit() method is implemented. Open a drop-down list, wait for drop-down list generation, and select a list item. For the TestedFormField object, the OpenDropList(), CloseDropList(), ExecuteChoiceFromDropList(), WaitForDropListGeneration(), and DropListIsOpen() methods are implemented.	The automated testing did not support the Taxi interface.	The automated testing can be used with the Taxi interface.
Data composition system. Dynamic lists.	Items of report user settings and dynamic list user settings can be linked to managed form tables. For the DataCompositionUserSettings object, the Filter, Order, Selection, ConditionalAppearance, and Structure columns are implemented. The report user settings form and the dynamic list user settings form are modified: instead of text boxes with the option to open editors (filter, order, and so on), tabs with tables are implemented to provide uniformity with the data composition schema editor in Designer. The Settings command of the report form is displayed in the main form command bar.	Items of user report settings and dynamic list settings could be linked only to managed form text boxes. The report and dynamic list user settings forms had a different layout. The Settings command of the report form was available in the More menu.	Improved standard report and dynamic list user settings form.
Managed forms.	For the Enum metadata object, the ChoiceHistoryOnInput property is implemented. This property defines whether the choice history of a text box linked to an attribute of enumeration type is displayed and saved. For enumerations whose values can be selected in a form, the input history is displayed and saved automatically. This change is not implemented in 8.3.5 compatibility mode.	This feature was not provided. The choice history for a text box linked to an attribute of enumeration type was neither displayed nor saved.	You can specify whether the choice history for a text box linked to an attribute of enumeration type is displayed and saved.
Data composition system.	For the DataCompositionDetailsFieldValues object a constructor is implemented.	The DataCompositionDetailsFieldValues object did not have a constructor.	You can fill detailed data using 1C:Enterprise script.
Web services and HTTP services.	For the HTTPConnection object, you can call any HTTP methods (passing the method name as a string). In order to simplify the usage of PATCH and HEAD HTTP methods, the Patch() and Head() methods are implemented for the HTTPConnection object.	These features were not provided. The HTTPConnection object could only be used to call the GET, PUT, POST, and DELETE methods.	Easier access to the full range of HTTP methods from applied solutions.
Server clusters. Administration tools.	External session management functionality is extended. Methods that are called when a session is hibernated or restored from hibernation are implemented. You can specify a timeout for the external session management web service response. For the external session management web service, the onHibernateSession() and onWakeupSession() methods are implemented. For external session management web service connection string, the optional parameters are implemented: tout sets an external session management web service response timeout, and wsver specifies the external session management web service interface version. The new features are only available if the wsver parameter is set to 2.	These features were not provided.	The web service behavior is uniform with the licensing subsystem behavior.
XML and XDTO support.	FastInfoSet operations are refactored.	FastInfoSet operations had a different implementation.	Improved stability of FastInfoSet operations.
Full-text search.	The full-text search index integrity check is implemented. For the full text search manager, the CheckIndex() method is implemented. The full-text search index update operations are recorded to the tecnological log. In the tecnological log, the FTEXTCheck and FTEXTUpd events are implemented. In the technological log the ftextupd item is implemented.	These features were not provided.	Improved stability of full-text search. An invalid full-text search index can be rebuilt.
Queries.	For the QuerySchemaTempTableDescription object, the TableName property is implemented. You can specify a temporary table name in the query builder. For the QuerySchemaSources object, the Alias parameter of the Add() method is implemented.	These features were not provided.	Improved functionality of the query software model.
Development tools. Common attributes / Data separation. Configuration extensions.	More options for modification of applied solutions (including cloud systems) without disabling their support. You can create configuration extensions and use them to implement applied solution modifications (which do not affect the data structure), so that the applied solution support is not disabled, and all modifications take place in a dedicated object (extension), which is easily connected to and disconnected from the applied solution. You can use extensions to modify forms, create reports and data processors, and create new subsystems. You can apply a configuration extension both in 1C:Enterprise mode and in Designer. You can specify a custom extension set for each separated infobase area.	This feature was not provided. Applied solution developers could create external reports and data processors and modify the applied solution configuration, which resulted in disabling support and did not allow making modifications in different areas of a separated infobase.	The new feature is intended for making small configuration modifications at the deployment stage (including modifications of separated infobases and cloud systems) more easily and with less dependence on vendor configuration modifications.
Data display.	New pictures are added to the picture library: GoForward, GoBack, GoToBegin, GoToEnd, Today, ShowInList.	The listed pictures were not available in the picture library.	More content for the picture library.
Database configuration updates.	The documentation describes Designer batch mode command-line options that manage background and dynamic database configuration updates.	The new Designer batch mode command-line options that manage background and dynamic database configuration updates were not listed in the documentation.	Fixed documentation error.
System requirements. Web client.	Support of Microsoft Windows 10 operating system is implemented. Support of Microsoft Information Services 10.0 web server is implemented. Support of Microsoft Edge web browser is implemented, with the following limitations: Add-ins are not supported File system extension is not available Cryptography extension is not available	Microsoft Windows 10 operating system was not supported. Microsoft Information Services 10.0 web server was not supported. Microsoft Edge web browser was not supported.	Extended list of supported operating systems and web browsers.
DBMS operations.	Support of PostgreSQL version 9.4 is implemented.	This PostgreSQL version was not supported.	Extended list of supported PostgreSQL versions.

Table of contents

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Command interface.	In the Taxi interface, in the functions menu, you can search for commands by their presentations. The search is performed in all sections (not only in the commands of the current section). Commands for specifying navigation and action panel settings are moved to the submenu to the right of the search field. In the Taxi interface, pressing F10 opens the functions menu.	The option to search for a command by a part of its presentation was not provided. Commands for specifying navigation and action panel settings were displayed as links in the right part of the functions menu. In the Taxi interface, pressing F10 opened the main menu.	Improved usability of the function menu.
Managed forms.	If all of the managed form command bar buttons have their OnlyInAllActions parameters set to False and some of these buttons do not fit the command bar width, the More button is added to the command bar, with a submenu that contains all of the command bar commands.	If all of the managed form command bar buttons had their OnlyInAllActions parameters set to False and some of these buttons did not fit the command bar width, there was no way to access the commands that did not fit.	If the command bar has small size, all of its commands are still available.
Client application.	You can fully replace the splash screen that is displayed during the startup of the thin, thick, and web clients. To replace a splash screen in your applied solution, submit a request to 1C Company	This feature was not provided.	In particular cases, you can use a splash screen that is fully customized by the company that uses the applied solution, provided that the splash screen is approved by 1C Company.
Web client.	Web browser pop-up windows are no longer displayed during the printing of spreadsheet documents.	When spreadsheet documents were being printed, web browser pop-up windows were displayed.	Simplified printing of spreadsheet documents for end users. In the Taxi or Forms in tabs interface mode, if the applied solution does not use modal calls, it does not require additional web browser setup.
Managed forms.	In managed forms, if the Create command is available for a text box, it is present in the context menu of the text box.	The Create command was never present in text box context menus.	Improved usability of text boxes.

Table of contents

Optimization

Functionality	After	Before	Result of changes
Full-text search.	The full-text search algorithm is optimized for scenarios where a search string is used multiple times (for example, getting the next batch of search results). The full-text search algorithm is optimized for scenarios where a user does not have access rights for some objects returned by the search.	The full-text search performance was insufficient.	Improved full-text search performance for infobases containing a large number of items, and also in scenarios where a user does not have access rights for some objects returned by the search.
Full-text search.	Optimized memory usage for fuzzy search (the search that uses the # operator). The search for similar words is optimized.	Fuzzy search might cause a memory overflow which, in turn, caused the system shutdown. The search for similar words might take a long time.	Increased stability of the fuzzy search in scenarios where the full text search index has a large size.
Web client.	The web client performance is improved in the following scenarios: Loading web client,. including scenarios with slow connection Opening forms General performance improvements in a variety of scenarios The web client now uses Google Closure Compiler.	The web client performance was insufficient.	Improved web client performance.
1C:Enterprise script.	The loading time of 1C:Enterprise script modules is slightly reduced.	The loading of 1C:Enterprise script modules was not fast enough.	Slightly reduced startup time for applied solutions that include a large number of 1C:Enterprise script modules.
Client application.	The startup time of the client application (before the authentication dialog appears) is slightly reduced.	The client application startup was not fast enough.	Slightly reduced startup time of the client application.
Configuration repositories.	The performance of the following operations is improved: Creating a repository First connection to a repository Storing objects in a repository Updating objects from a repository Updating configuration from a repository The performance of compatibility mode change operations is improved. The 1C:Enterprise version 8.3.3 compatibility mode is implemented for configuration repositories. The configuration repository performance is improved in scenarios where the configuration repository compatibility mode is set to Do no use.	The performance of configuration repository operations was insufficient.	Improved configuration repository performance.
Managed forms.	The strong data compression algorithm for large data volumes (more than 64 KB) transferred between the client and the server (or a web server extension) is optimized. This slightly reduces the time required to open managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode.	The strong data compression algorithm was less efficient.	Slightly reduced time of opening managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode.
Web services and HTTP services.	Faster processing of requests that call the standard OData interface.	Performance of requests that called the standard OData interface was insufficient.	The performance of operations with the standard OData interface is improved.
Managed forms.	Improved performance of opening managed forms in the following scenarios: A form has a large number of items. A form has a large number of attributes. The list of attributes and form items is significantly changed using 1C:Enterprise script. A large number of users are working with managed forms.	The performance of opening managed forms in the listed scenarios was lower.	Improved usability of managed forms.
Managed forms.	Managed form conditional appearance is optimized.	The performance of managed form conditional appearance was lower.	Improved usability of managed forms with conditional appearance.
Development tools.	Performance of base configuration updates (update configuration from file, load configuration from file, and get specific configuration version from configuration repository) is improved.	Performance of base configuration updates was insufficient.	Better usability for developers.
DBMS operations. Administration tools.	For the file mode, the option to restructure the infobase so that all data required to open the infobase is at the beginning of the 1Cv8.1CD file is implemented. This improves the performance of infobase opening. This type of restructuring is performed during the compressing of infobase tables (which is available from a Designer dialog box and as a command-line option), or during infobase verification with the chdfl utility with the Correct errors check box selected. It is recommended that you always perform this optimization after you make any configuration changes (and the associated infobase restructuring) that result in database structure changes.	Internal information required for opening an infobase was evenly distibuted within the 1Cv8.1CD infobase file.	Improved performance of opening file infobases, especially in scenarios where the infobase is located on a network resource.
DBMS operations.	In client/server mode with PostgreSQL DMBS, the query that is executed when deleting records from tables of extra dimensions of accounting registers is optimized.	In client/server mode with PostgreSQL DMBS, the performance of the query that was executed when deleting records from tables of extra dimensions of accounting registers was insufficient.	Improved performance of deleting accounting register records.

Table of contents

Changes that affect system behavior

Functionality	After	Before	Result of changes
Client application.	When a client application is restarted with the /AppAutoCheckMode key, the platform checks the user rights for running the client application. If the user attempts to start the application in the ordinary mode and does not have the right to run the thick client, they are not allowed to access the infobase. In other scenarios the client application that suits the selected start mode best is selected.	When a client application was restarted with the /AppAutoCheckMode key, the platform did not check the user rights for running the client application.	The client application selection algorithm is improved.
Managed forms.	If editing text in a form field extension for a text box is not allowed (the TextEdit property is set to False), the drop-down list of that box does not display the text "Enter the search string".	The drop-down list always displayed the text "Enter the search string".	The recommendation to perform an action that is not allowed is no longer displayed.
Development tools.	During the merging of configurations you can modify the results of module merging. You can use external software (not incorporated in Designer) for comparing and merging module texts. You can specify the external software in the Designer options dialog box. Ready-to-use settings are available for the following external software: For Windows: Araxis Merge, KDiff3, TortoiseMerge, Perforce P4Merge, and DiffMerge For Linux: KDiff3 and Perforce P4Merge You can specify settings for external software that is not on the list.	The results of module merging could not be modified while merging configurations. Only built-in Designer features were available for comparing and merging module texts.	Developers can use any tool that they find convenient for comparing and merging module texts. They can make changes during the merging of configurations (with the help of external software).
Development tools.	Improved setup for the comparison and merging of managed forms. You can specify the comparison and merging rules for a form and for its module directly in the comparison and merging dialog box.	The comparison and merging rules for managed forms were specified in another dialog box. Also, the rules for the form itself and for its module were separated.	Simplified setup for the comparison and merging of managed forms and their modules.
Development tools.	The following features are implemented in the managed form editor: If the Title property of a managed form is not empty, its value is displayed in the window title in the preview area. Clicking a title if the preview area selects the entire form. Right-clicking the title opens the form context menu.	The window title bar in the preview area of the form editor did not have any functionality.	Improved usability of the form preview area in the managed form editor.
Internet-enabled functionality.	Automatic selection of text encoding in email messages containing national characters is implemented. The automatic selection is only performed when the text contains national characters but their encoding is not specified, which does not comply with the standard. This applies to the following email message parts: Message headers Message body Message header parameter values, such as attachment file name.	Email message text was displayed in incorrect encoding when no encoding was specified.	Email messages that do not comply with the standard are processed correctly.
Background and scheduled jobs.	The duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases is reduced. Now the duration of the first access is approximately the same as the duration of subsequent accesses.	The long duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases might cause the user interface to stop responding until loading the backgound job scheduler was complete.	Reduced duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases. Faster start of client applications in the file mode (when the background job manager is accessed during the startup).
Background and scheduled jobs.	In file infobases, if a client application that performs background jobs is closed, the background jobs are terminated after a 30-second timeout. When a job is terminated, a_$Job$_.Terminate event is recorded to the event log.	In file infobases, if the platform could not complete background jobs correctly, it displayed a message prompting the user to choose between waiting and terminating the jobs.	Eliminated unexpected (and not user-friendly) system behavior.
Error handling.	When properties or methods of MetadataObject objects related to external reports or data processors that are no longer available are accessed, the platform generates an exception.	When properties or methods of MetadataObject objects related to external reports or data processors that were no longer available were accessed, the platform was shut down unexpectedly.	Improved system stability.
Development tools. Internet-enabled functionality.	The following information is added to the Syntax Assistant: SSL is supported for POP3 and SMTP. Secure connection does not support checking server and client certificates. Descriptions of the InternetMail object methods that require IMAP connection now reflect that fact. The list of fields filled in the GetHeaders() method of the InternetMail object is provided.	The Syntax Assistant did not contain this information.	Improved Syntax Assistant quality.
Spreadsheet documents.	When a spreadsheet document is exported to Microsoft Excel 2007-2010 format, its comments are converted to Excel table comments. This change is not implemented in 8.3.5 compatibility mode.	When a spreadsheet document was exported to Microsoft Excel 2007-2010 format, its comments were converted to Excel pictures.	Better conversion of spreadsheet document items to Microsoft Excel format.
Background and scheduled jobs.	When a client application is started with a file infobase, there is a 1-minute delay before starting the execution of scheduled jobs.	When a client application was started with a file infobase, there was no delay before starting the execution of scheduled jobs.	Faster startup of client applications in file mode.
Defined types.	During the update of a supported configuration you have the option to merge the following properties with priorities: the Type property of the DefinedType configuration property and the Type property of the ChartOfCharacteristicTypes object.	This feature was not provided.	Improved algorithm for comparing and merging defined types, which simplifies usage of those types in library development tasks.
Managed forms.	Presentations of items found during the input by string with full-text search enabled are identical to presentations of items found with full-text search disabled. The order of items in drop-down lists generated by the input by string feature with full-text search enabled matches the order of items returned by the full-text search algorithm. The algorithm that generates presentations for Task objects in drop-down lists generated by the input by string feature is modified.	Presentations of items found during the input by string with full-text search enabled were different from presentations of items found with full-text search disabled. The order of items in drop-down lists generated by the input by string feature with full-text search enabled was not defined. The algorithm that generated presentations for Task objects in drop-down lists generated by the input by string feature was different.	Improved usability of the input by string feature. Unified generation of presentations for search results.
Configuration repositories.	The configuration repository window now displays names of computers where objects are locked.	The configuration repository window displayed the name of the computer that the current user used for their first connection to the repository.	Eliminated unexpected system behavior.
Internet-enabled functionality.	For the InternetMailMessage object, the PostingDateOffset property is implemented.	This feature was not provided.	You can define the true date of sending an email message.
Dynamic lists.	When a form is opened, the Period property of managed form table extension for dynamic lists and the Representation property of a form table linked to a dynamic list are loaded simultaneously with dynamic list user settings. It is recommended that you get the Period property in the OnLoadUserSettingsAtServer managed form event handler. This change is not implemented in 8.3.5 compatibility mode.	The Period property of managed form table extension was obtained from the user settings before the execution of the OnCreateAtServer managed form event handler. The Representation property of a form table linked to a dynamic list was obtained from the client settings during the form opening.	The Period and Representation properties are stored in a similar way to other dynamic list settings, which simplifies operations with these properties using 1C:Enterprise script.
Spreadsheet documents.	When nonempty spreadsheet document cells with Placement properties are set to Auto are displayed, the cells are not merged up to the next filled cell or up to the horizontal boundary of the spreadsheet document.	When nonempty spreadsheet document cells with Placement properties set to Auto were displayed, the cells were merged up to the next filled cell or up to the horizontal boundary of the spreadsheet document.	The spreadsheet document view in the web client is now closer to the spreadsheet document view in the thin client.
DBMS operations.	In the client/server mode with Oracle Database DBMS, executing a query that contains a subquery in the SELECT section and also an aggregate function adds a GROUP BY section with a constant, provided that such section is not yet present in the query.	In the client/server mode with Oracle Database DBMS, executing a query that contained a subquery in the SELECT section and also an aggregate function resulted in the ORA-937 run-time error.	Improved stability of Oracle Database operations.
Managed forms.	The prevention of unexpected working process or client application shutdown due to managed form operation issues (loss of synchronization between the client and server parts of form data) is implemented. When an issue is detected, only the affected session is closed, and the working process that processes the session is not shut down. By default, the issue details are recorded to the technological log.	A loss of synchronization between the client and server parts of form data could result in a shutdown of the client application or a working process that processed the affected session.	Improved 1C:Enterprise server stability during managed form operations.
DBMS operations.	The chance of deadlocks in queries that include comparisons with UNDEFINED is reduced.	The chance of deadlocks in queries that included comparisons with UNDEFINED was higher.	Increased system stability. Reduced chance of deadlocks that do not have obvious reasons.
Client application. Managed forms. Data display.	For client applications that run on Windows operating systems, Windows scaling is supported. If a custom DPI value is set, interface items are scaled correctly, except pictures that might look a bit blurry.	Client applications that run on Windows operating systems had scaling issues.	Eliminated unexpected system behavior in scenarios where a user sets a custom DPI value for their display.
Configuration repositories.	When a user cancels binding to a configuration repository or when an infobase bound to a repository changes location, the dialog box stating that unbinding from the repository is required is no longer displayed. To unbind a configuration from a repository, you can use the corresponding Designer command.	When a user canceled binding to a configuration repository or when an infobase bound to a repository changed location, the dialog box stating that unbinding from the repository was required was always displayed.	Improved usability of configuration repositories in some scenarios.
Command interface.	The visibility settings for commands in subordinate subsystems are no longer lost when command interface settings of a subsystem that contains subordinate subsystems are copied using the Load() and Save() methods of the StandardSettingsStorageManager object.	When command interface settings of a subsystem that contained subordinate subsystems were copied using the Load() and Save() methods of the StandardSettingsStorageManager object, the visibility settings of commands in subordinate subsystems were lost.	Eliminated unexpected system behavior.
Web client. Spreadsheet documents.	In the web client, the option to select pictures in spreadsheet documents is implemented, and when they are selected, the respective event is called. Improved representation of pictures in spreadsheet documents when viewed in the web client: Cells overlapped by a picture are not merged. Text and pictures in spreadsheet document cells can overlap each other. Eliminated issues that appeared when picture borders were close to cell borders.	Selecting pictures in spreadsheet documents was not supported. Spreadsheet documents had some picture-related issues.	Improved quality of displaying spreadsheet documents with pictures in the web client.
Development tools. Mobile application.	The picture editor dialog box in Designer supports editing template pictures and the new picture variants format that includes a manifest. Template pictures are used in applied solution development for the mobile platform.	Editing template pictures and the new picture variants format that includes a manifest were not supported.	Template picture support is implemented.
DBMS operations.	The DBMS request that the platform generates based on the VALUETYPE function of the query language is simplified.	The DBMS request based on the VALUETYPE function was more complicated.	Eliminated issueds that occured when DBMS could not process a complex request.
Development tools.	During configuration merging and during configuration repository operations, the platform does not perform refactoring operations that are normally performed when configuration objects are renamed or deleted.	During configuration merging and during configuration repository operations, the platform performed refactoring operations that were normally performed when configuration objects were renamed or deleted.	Eliminated unexpected system behavior. Operations whose results were ignored are not performed.
1C:Enterprise script.	If an object is passed to a method written in 1C:Enterprise script and its set of properties is changed during the method execution but the property names are not changed, the object property calls are executed correctly. In particular, when a method being executed adds a property, calls of other properties are executed correctly. If any property names are modified, object property calls might not be executed correctly. This change is not implemented in 8.3.5 compatibility mode.	If an object was passed to a method written in 1C:Enterprise script, the method called object properties by their numbers, which were defined at the moment the method was called. If a property number was changed during the method execution (for example, a new property was added), this was not taken into account and the property call was performed using the old number.	Improved system reliability and reduced chance of errors when a set of properties is changed during method execution.
Managed forms.	In the thin client, formatted strings that are defined during the generation of a drop-down list are displayed accordingly to their formatting if the text box is linked to an attribute of complex type and this attribute has the Undefined value.	In the thick client, formatted strings that were defined during the generation of drop-down lists were displayed without formatting if the text box was linked to an attribute of complex type and this attribute had the Undefined value.	Eliminated unexpected system behavior.
Web client. Managed forms.	In the web client, drop-down lists have the same color scheme as in other client applications.	In the web client, drop-down lists had a color scheme different from the color scheme used in other client applications.	In the web client, drop-down list appearance is uniform with other client applications.
Web client.	In the web client, the appearance of the following interface items is almost identical to their appearance in the thin client: form button command bar button command bar separator	In the web client, the appearance of the following interface items was different from their appearance in the thin client: form button command bar button command bar separator	Uniform client application appearance.
Command interface.	When a user command group is deleted, standard commands that belong to the group are automatically moved to the default standard group specified for those commands. This change is not implemented in 8.3.6 compatibility mode.	When a user command group was deleted, standard commands that belonged to the group were no longer available in the command interface.	Eliminated unexpected system behavior.
Event log.	The UnloadEventLog() method truncates the event time passed to it to an integer number of seconds. When a filter by time is applied to the event log (UnloadEventLog(), CopyEventLog(), or ClearEventLog() method), an event is included in the result even if the millisecond part of the actual event time exceeds the millisecond part of the time specified in the filter.	The UnloadEventLog() method provided the event time with millisecond accuracy. When a filter by time was applied to the event log (UnloadEventLog(), CopyEventLog(), or ClearEventLog() methods), an event was included in the result only if the exact condition was met (including the millisecond part).	Eliminated unexpected system behavior. The behavior of the .lgd log is uniform with that of the .lgf log (regarding the event time presentation and filter functionality).
Print tools. Spreadsheet documents.	The algorithm that calculates spreadsheet document column width for printing is modified. The printed document column width more closely matches the on-screen column width. The chance is noticeable in spreadsheet documents with background pictures. This change is not implemented in 8.3.5 compatibility mode.	For spreadsheet documents, the printed document column width did not exactly match the on-screen column width.	Improved print layout of spreadsheet documents.
Regional settings.	For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, and 69-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.	The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, and 69-FZ.	The time offset changes introduced by the new law are implemented.

Table of contents

Changes that require modification of configuration and administrative settings

Functionality	After	Before	Result of changes
Internet-enabled functionality.	Future 1C:Enterprise versions will not support NSS certificates and related objects, regardless of the compatibility mode. The NSSSecureConnection object will be unavailable for use in 1C:Enterprise script and in thin client HTTPS connection settings.	1C:Enterprise system supports NSS certificates.	Future platform versions will not support NSS certificates.
Automated testing.	For the TestedFormGroup object, the CurrentVisible() function returns False if the object is linked to form group, which is inactive page located in a page group where tabs are not displayed. This change is not implemented in 8.3.5 compatibility mode.	For the TestedFormGroup object, the CurrentVisible() function returned True if the object was linked to a form group, which was an inactive page located in a page group where tabs were not displayed.	The automated testing feature emulates the system functioning and provides form item status data more accurately.
Managed forms.	For managed form attributes of spreadsheet document, graphical schema, and text document types, calling the Show() method raises an exception. This change is not implemented in 8.3.5 compatibility mode.	The system behavior depended on the attribute location on a form and the client application type: The attribute is linked to a managed form item: Thin client: Spreadsheet document: the current form is activated. Graphical scheme: a new form with a copy of the scheme is opened. Text document: a new form with a copy of the document is opened. Web client: For attributes of any type (spreadsheet document, graphical schema, or text document) the current form is activated. The attribute is not linked to a managed form item: Thin client: For attributes of any type (spreadsheet document, graphical schema, or text document), a form with a copy of the document is opened. Web client: Spreadsheet document: a new form with a copy of the document is opened. Graphical scheme: the current form is activated. Text document: the current form is activated.	Unified behavior of various objects in different client applications.
Managed forms.	In the thin and thick clients, buttons (or hyperlinks) located in managed forms become unavailable when commands (or hyperlinks) linked to these buttons become unavailable. This change is not implemented in 8.3.5 compatibility mode.	In the thin and thick clients, buttons (or hyperlinks) located in managed forms stayed available even when commands (or hyperlinks) linked to these buttons were unavailable.	The system behaves as expected. Unified system behavior in different client applications.
Managed forms.	When an item is created in the drop-down list of a text box, you can verify whether the created item matches the choice parameters used for opening the new item form. If the item does not match the choice parameters, a diagnostic message is displayed and the created item is not placed in the text box. The verification is implemented for managed form extensions for objects, catalogs, documents, charts of characteristic types, business processes, and tasks. The following features are implemented: ChoiceParameters standard property of the managed form extension ChoiceParameters property of the managed form extension ChoiceAvailable property of the managed form extension ValueChoice event of the managed form extension The ChoiceParameters and ChoiceAvailable properties of the managed form extension are not available in version 8.3.5 compatibility mode.	A new item that did not match the choice parameters specified for a text box could be created and selected in the text box.	Reduced chance of creating items (from a text box choice list) that do not match the choice parameters specified for the text box.
Managed locks.	The Period field whose value is specified in a periodic information register record set filter is included in the set of managed lock fields for read and write operations on record set data. This change is not implemented in 8.3.5 compatibility mode.	The Period field was not included in the set of managed lock fields for read and write operations on periodic information register record set data.	Improved user experience for periodic information register operations. Reduced chance of deadlocks.
Common attributes / Data separation. Information registers.	When an information register data set is recorded, the default values of independent and shared separators that include the information register are replaced by the separator values set in the current session. If a separator value is not identical to the default value of that separator type or is not equal to the separator value set in the current session, an error is generated. This change is not implemented in 8.3.5 compatibility mode.	When an information register data set was recorded, the default values of independent and shared separators that included the information register were always replaced by the separator values set in the current session	Eliminated unexpected system behavior.
Internet-enabled functionality.	When the InternetMail object is used for interaction with a Microsoft Exchange server, if the filter criterion string value (the Filter parameter of the GetHeaders() and GetUIDL() methods of the InternetMail object) only includes US-ASCII characters, the platform notifies the Exchange server about this in addition to passing the string to the server. Otherwise the platform passes a UTF-8-encoded string. If the filter criterion string value passed to the Exchange server contains not only US-ASCII characters (for example, it includes Cyrillic characters), an error is generated. This change is not implemented in 8.3.5 compatibility mode.	The GetHeaders() and GetUIDL() methods of the InternetMail object always returned an empty array when a string value of the Filter parameter was used in interactions with Microsoft Exchange.	Improved compatibility with Microsoft Exchange during operations with the InternetMail object. You can search in the filter criterion string if all its characters belong to the US-ASCII encoding.
Internet-enabled functionality.	The libetpan library is used to work with IMAP, SMTP, and POP3. This change is not implemented in 8.3.5 compatibility mode.	The UW IMAP toolkit library was used to work with IMAP, SMTP, and POP3.	Improved performance and stability of email management features.
Internet-enabled functionality.	During the creation of an InternetProxy object on Linux operating systems, if the DefaultProxy constructor parameter value is True and the platform cannot find the file inetcfg.xml, the constructor uses the values of the following operating system environment variables: http_proxy, https_proxy, ftp_proxy, ftps_proxy, and all_proxy. The methods of the HTTPConnection and FTPConnection objects do not attempt to determine the proxy server settings. Instead, they use the settings stored in the Proxy property of the respective object. For the Set() method of the InternetProxy object, the User and Password parameters are implemented. For the InternetProxy object, the User and Password methods are implemented. The User and Password properties of the InternetProxy object are declared obsolete, they are suported for compatibility purposes. This change is not implemented in 8.3.5 compatibility mode.	Environment variables were never used for creation of InternetProxy objects on Linux operating systems. If the proxy server parameters were not specified during the creation of HTTPConnection and FTPConnection objects, methods of these objects attempted to retrieve the proxy server settings from environment varaibles.	Eliminated the difference in platform behavior on Windows and Linux operating systems. Eliminated unintuitive platform behavior where methods of HTTPConnection and FTPConnection objects attempted to determine the proxy server settings.
Client application.	Idle handlers are not called while a client application is locked using the LockApplication() global context method or the Temporary lock command. This change is not implemented in 8.3.5 compatibility mode.	Locking a client application using the LockApplication() global context method or the Temporary lock command did not affect the execution of idle handlers.	Increased system security.
xBase support.	If an error occurs during a .dbf file operation performed using the XBase object, an exception is generated. This change is not implemented in 8.3.5 compatibility mode.	If an error occurred during a .dbf file operation performed using the XBase object, dialog boxes were generated.	Eliminated scenarios that looked as if the platform stopped responding (for example, errors generated by .dbf file operations at 1C:Enterprise server side).
Managed forms.	For the TypeLink object constructor, you can specify the first parameter (DataPath) as an empty string.	The TypeLink object constructor did not accept an empty string as the DataPath parameter value.	You can clear the TypeLink property of a managed form field by replacing its value with a new object of that type that does not have the data path specified.
External data sources.	For the ExternalDataSourceTableObject, the GetChangeableFields() and SetChangeableFields() methods are implemented. These methods are intended both for restricting the list of writable external data table fields and for expanding that list with fields have the read-only flag set in the configuration (the ReadOnly property set to True). The GetFieldsToWrite() and SetFieldsToWrite() methods are declared obsolete, they are supported for compatibility purposes.	The GetFieldsToWrite() and SetFieldsToWrite() methods only provided the option to reduce the number of fields that were recorded to external data source tables. The option to record data to fields that are marked as read-only in Designer was not provided.	The platform supports custom algorithms for external data source management. For example, data that is normally not recorded to external data source table fields can now be recorded using a custom algorithm.
Administration tools.	When a list of infobases is updated or when a client application distribution kit is downloaded via the Internet, the root certificates of certification authorities are obtained from the Windows certificate store.	When a list of infobases was updated or when a client application distribution kit was downloaded via the Internet, the root certificates of certification authorities were only obtained from the cacert.pem file.	Improved usability of self-signed certificates in the enterprise environment.
Server clusters.	You can specify the user on whose behalf the cluster manager (rmngr) is started, and it can be different from the user on whose behalf the cluster agent (ragent) is started. You can specify users on whose behalf the cluster manager (rmngr) and working processes (rphost) is started for each cluster on a given computer. You can specify a custom cluster register directory for each cluster manager (rmngr) on a given computer. The following parameters and parameter groups are implemented for the swpuser.ini file: the rmngr_user and rmngr_pass parameters the registry parameter the <PortName:> parameter group, which can contain all of the swpuser.ini file parameters.	Only the user on whose behalf the working process (rphost) was started could be changed.	You can increase server cluster security in scenarios like this: service users use their own applied solutions, external data processors, and add-ins whose access to the server cluster computer infrastructure should be restricted.
Data access restrictions.	Access restriction template parameters that are specified in comments are not replaced by actual values when the template is applied. This change is not implemented in 8.3.5 compatibility mode.	Access restriction template parameters that were specified in comments were not replaced by actual values when the template was applied.	Increased stability of the access restriction system in some scenarios.
Data composition system.	The option to use nested reports during the export of data composition result to a value collection is implemented. Columns with duplicate names are never created during the export. This change is not implemented in 8.3.5 compatibility mode.	The option to use nested reports during the export of data composition result to a value collection was not available. The check for duplicate column names was never performed during the export, so columns with duplicate names might be created.	Extended data composition system functionality.
Data composition system.	When additional data is displayed for hierarchical records, hierarchical record data is used. This change is not implemented in 8.2.16 compatibility mode.	When additional data was displayed for hierarchical records, the detailed record data was used.	Reports display expected data: if a report contains a table with hierarchical groupings in its rows, the data obtained from the hierarchical records is displayed in the columns of additional data for hierarchical grouping rows, not from the detailed records, as it was implemented earlier.
Data composition system.	The value assigned to the Text conditional appearance parameter, which is enabled, is applied to fields of predefined grouping templates and fields of data composition system reports. This change is not implemented in 8.3.5 compatibility mode.	The value assigned to the Text conditional appearance parameter, which was enabled, was not applied to fields of predefined grouping templates or fields of data composition system reports.	Predefined grouping templates can be used together with the Text parameter of data composition conditional appearance.
Data composition system.	The appearance of cells that store parent grouping fields is based on the field expressions obtained for the current grouping. This change is not implemented in 8.3.5 compatibility mode.	The appearance of cells that stored parent grouping fields was based on the field expressions obtained for the parent grouping.	The cell appearance is formed as expected.
Dynamic lists.	If the platform cannot generate the list of available dynamic list settings, an exception is generated and the form is not generated. This change is not implemented in 8.3.5 compatibility mode.	If the platform could not generate the list of available dynamic list settings, no exceptions were generated and the managed form continued functioning as if the dynamic list data source did not have any fields available. All of the form items related to dynamic list data disappeared from the managed form.	Improved error diagnostics during dynamic list operations.
Data composition system.	The data composition template composer uses detailed data set fields for hierarchical grouping records. You can use the EvalExpression() function for getting hierarchical record values within aggregate functions. This change is not implemented in 8.3.5 compatibility mode.	The data composition template composer used hierarchical data set fields for hierarchical records (provided that the fields were available in the set).	You can use all detailed record fields in aggregate functions calculated for hierarchical records.
1C:Enterprise script.	The FindMarkedForDeletion() method only processes data available to the current user. In the Syntax Assistant, the descriptions of the FindByRef() and DeleteObjects() methods are modified to describe their actual behavior. This change is not implemented in 8.3.5 compatibility mode.	The FindMarkedForDeletion() method did not check data access rights. If access was denied, a run-time error was generated. In the Syntax Assistant, the descriptions of the FindByRef() and DeleteObjects() methods did not describe their actual behavior.	The generation of run-time errors during the search for objects marked for deletion is eliminated in scenarios where the user does not have access rights for all objects involved in the search. The description of the system behavior is now correct.
Managed forms.	In the thin client, in the OnOpen managed form event handler, if the Cancel parameter is set to TRUE, the OnClose event handler and the notification set in the OnCloseNotifyDescription managed form property are not called. This change is not implemented in 8.3.5 compatibility mode.	In the OnOpen managed form event handler, if the Cancel parameter was set to TRUE, the OnClose event handler and the notification specified in the OnCloseNotifyDescription managed form property had the following behavior: they were called in the thin client; they were not called in the web client.	Uniform system behavior across multiple client applications.
Automated testing.	New automated testing features: Operations with performance indicators. For the TestedApplication object, the GetAccumulatedPerformanceIndicators() and ClearAccumulatedPerformanceIndicators() methods are implemented. Support of the following managed form items: progress bar fields and track bar fields. The Tumbler radio button field type is now supported. Extended managed form table operations: Deletion mark management. For the TestedFormTable object, the SwitchRowDeleteMark() method is implemented. Setting row selection and getting selected rows. For the TestedFormTable object, the SelectAllRows() and GetSelectedRows() methods are implemented. For the GotoRow(), GotoFirstRow(), GotoLastRow(), GotoPreviousRow(), and GotoNextRow() methods, the Select parameter is implemented. Ordering table data. For the TestedFormTable object, the SetOrder() method is implemented. Expanding and collapsing managed form groups. For the TestedFormGroup object, the Collapse(), Expand(), and GetCurrentPage() methods are implemented. The GetCurrentAreaText() method of the TestedFormField is declared obsolete. It is recommended that you use the GetAreaText() method of the TestedFormField object. In the event of unexpected shutdown of a client application the user actions are automatically recorded to the user action log (provided that the user action log recording is enabled). A dump is also recorded to the dump directory. The data processor that converts the log of user actions to a 1C:Enterprise script scenario is updated URL2.	Operations with performance indicators were not supported, as well as managed form table and managed form group operations. Progress bar fields, track bar fields, and the Tumbler radio button field type were not supported. In the event of an unexpected shutdown of a client application, the user actions were not recorded to the user action log and the accumulated action log was lost.	New automated testing features. Reduced number of manual operations during the testing.
Data display.	In sessions that do not have user interface (background and scheduled jobs, web services, and so on), the BriefErrorDescription() and DetailErrorDescription() method generate results that exactly match the results provided by these methods in managed application client sessions. This change is not implemented in 8.3.5 compatibility mode.	In sessions that did not have user interface (background and scheduled jobs, web services, and so on), the BriefErrorDescription() and DetailErrorDescription() methods generated results that exactly matched the results provided by these methods in ordinary application client sessions.	Eliminated unexpected system behavior.
Common objects.	When a configuration is saved, a check for style elements whose names match the values of the corresponding system value sets is performed: For style elements of Color type: the StyleColors system value set For style elements of Font type: the StyleFonts system value set For style elements of Border type: the StyleBorders system value set If such elements are found, an error is displayed and the configuration is not saved.	When a configuration was saved, a check for style elements whose names matched the values of the corresponding system value sets was not performed.	Eliminated unexpected system behavior. Eliminated situations where two values with the same name were present in a single system value set whose values were connected to style elements.
Internet-enabled functionality.	In the parsing of Internet mail messages, the message validity check is implemented. The check is available both for messages received from the server and during the generation of outgoing messages using the SetSourceData() method of the InternetMailMessage object. For the InternetMailMessage object, the ParseStatus property is implemented. In the technological log, the <MAILPARSEERR> event is implemented. This change is not implemented in 8.3.5 compatibility mode.	Detection of invalid mail messages resulted in an unexpected shutdown.	Improved system reliability during email operations in scenarios where email messages being processed contain errors.
Internet-enabled functionality.	For the SetBodyFromString() method of the HTTPRequest and HTTPServiceResponse objects, the UseBOM parameter is implemented. It manages the availability of BOM in the specified text. In version 8.3.5 compatibility mode, the BOM mark is added by default.	This feature was not provided.	Simplified interaction with systems that do not expect BOM in HTTP queries.
Ordinary forms.	The Name property of ordinary form items is read-only. This change is not implemented in 8.3.5 compatibility mode.	The DBMS request based on the VALUETYPE function was more complicated.	Eliminated issues that occurred when a DBMS could not process a complex request.
OData operations.	The list of functions supported by OData standard interface is revised. The description of mod function is removed from the documentation.	The documentation stated that the mod function was supported by standard Odata interface.	The documentation describes the actual platform behavior.
File operations. Client application.	Both in thin and thick clients, when a file is obtained interactively using the GetFile() method with the "open file" option, the search for associated application is performed (by the file extension). If an associated application is found, a system dialog box for selecting an application to open the file is displayed. If an associated application is not found, getting the file is canceled. In the web client, the behavior is not changed, so it is now uniform with the behavior of thin and thick client applications.	In both thin and thick clients, when a file was obtained interactively using the GetFile() method with the "open file" option, the search for associated application was performed (by the file extension). If an associated application was found, the file was opened using this application. If an associated application was not found, getting the file was canceled. The web client displayed a system dialog box for selecting an application to open the file.	Eliminated the difference in the web client, thin client, and thick client behavior.
File operations. Web client.	The File object constructor with a file name parameter is available regardless of the Synchronous call usage mode for extensions and add-ins configuration property value. Configuration verification and refactoring no longer treat the File constructor with a file name parameter as a legacy synchronous call. Execution of this constructor no longer causes an exception in 1C:Enterprise mode. In the web client execution of File constructor with a file name parameter no longer requires installing the file system extension. The descriptions of File constructor without parameters and File.BeginInitialization() methods are removed from the documentation. The File.BeginInitialization() method is supported for compatibility purposes.	The File object constructor with a file name parameter was available when the Synchronous call usage mode for extensions and add-ins configuration property was set to Use or Use with warnings. Configuration verification and refactoring treated the File constructor with a file name parameter as a legacy synchronous call. If the Synchronous call usage mode for extensions and add-ins configuration property was set to Do not use, execution of this constructor caused an exception in 1C:Enterprise mode. In the web client execution of File constructor with a file name parameter required installing the file system extension.	Operations with the File object that do not require access to the file system (such as getting a file extension) no longer require installing the file system extension.
Internet-enabled functionality.	IDs of email messages received using IMAP do not depend on whether you specify the mailbox by name or use the default one. Once you disable the compatibility mode, the option to map messages to each other using the InternetMailMessage.MessageID property becomes available. This change is not implemented in 8.3.5 compatibility mode.	IDs of email messages received using IMAP did not depend on whether you specified the mailbox by name or used the default one.	You can unambiguously identify each email message, regardless of the selected mailbox. This simplifies the algorithm for distinguishing between received and new messages.
Web client. System requirements.	The list of supported web browsers includes Google Chrome for x86-64 architecture. The platform uses 32-bit versions of add-ins and extensions with this browser.	The list of supported web browsers did not include Google Chrome for x86-64 architecture.	Extended list of supported web browsers.
Data composition system.	When columns of a data composition system report template are output to a value tree or a value table, invalid characters are removed from column names. This change is not implemented in 8.3.5 repository compatibility mode.	When columns of a data composition system report template were output to a value tree or a value table, the column names matched the field names.	Eliminated unexpected system behavior.
Add-ins.	In the add-in development technology, Mozilla Firefox and Google Chrome support (for all Windows, Linux, and MacOS X architectures) is now uniform. The xulrunner utility is no longer required for building add-ins and is removed from the distribution kit. It is recommended that you build new installer packages (.msi and .sh) for Mozilla Firefox and create a new archive with version 40.* specified in the manifest. For support of earlier platform versions, also add legacy (.xpi) packages to the archive with version 31.0 specified in the manifest. The add-in development technology documentation and examples are updated accordingly.	Add-ins created for Mozilla Firefox and Google Chrome were different. The xulrunner utility was used to build Mozilla Firefox add-ins.	Support of add-ins for browsers that no longer support legacy add-in creation functions is implemented.
Predefined data.	The configuration check that is always performed before database configuration update includes a check for uniqueness of predefined item names. No duplicate predefined item names are allowed for any configuration object. If duplicate predefined items are found, this is reported to the message window but does not prevent the configuration update.	The configuration check that is always performed before database configuration update did not include a check for uniqueness of predefined item names.	Improved reliability of configuration updates for configurations that include predefined data.

Table of contents

Renamed objects

Object	The old name	The new name
The name of the URLProcessing event handler parameter is changed for form decoration, form field extension for a label, and managed form objects.	URL	FormattedStringURL
Parameter of the AutoCompleteText and TextEditEnd event handlers of the form text box extension.	Parameters.	DataGetParameters.
The method that obtains the most accurate location provider is renamed. The former name is supported for compatibility purposes.	GetMostAcurateProvider().	GetMostAccurateProvider().
English name of CryptoCertificate.BeginUnloading() method. The former name is supported for compatibility purposes.	BeginUnload().	BeginUnloading().
English name of BeginCheckingExistence() method. The former name is supported for compatibility purposes	BeginCheckingExist().	BeginCheckingExistence().

Table of contents

Mobile platform

Functionality	After	Before	Result of changes
Client application.	Faster startup of mobile applications.	Insufficient startup speed of mobile applications.	Improved usability of mobile applications.
Development tools. Data display.	The set of data stored in picture archives that include variants is modified. The manifest file manifest.xml, which is included in the archive, stores descriptions of picture variants. Custom names for pictures designed for specific display resolutions are allowed. Template pictures (pictures that have transparent background, which is displayed using the current text color) are supported. It is recommended that you store template pictures in PNG format.	Picture variants were described by their file names. A manifest file was not included. Template pictures were not supported.	You can use more of mobile application system appearance design features.
Full-text search.	In the mobile platform, you can use full-text search. The full-text search index is updated automatically upon data modification. The search is not morphological. Additional dictionaries and text extraction are not supported. The index is updated when the mobile platform is not performing any server calls or background jobs.	The mobile platform did not support full-text search.	You can use full-text search in the mobile platform.
System requirements.	The Google Play store now considers mobile applications optimized not only for phones but also for tablet PCs. The change takes effect when you rebuild the mobile application using the new mobile platform and then republish the application to Google Play.	The Google Play store considered mobile applications optimized for phones only.	Tablet PC users can see mobile applications in the default Google Play list. Searching by title is not necessary.
Calendars.	During the creation of data composition fields, if they include calendar or contact data, you can specify just a field name, without specifying its data type. Creation of data composition fields with data types specified is supported forn compatibility purposes.	During the creation of data composition fields, if they included calendar or contact data, specifying the full field name with its data type was required.	The system behaves as described in the documentation. Simplified interaction with calendars and contacts in some scenarios.
Window management.	The option to handle the change of mobile device display parameters is now available. The OnChangeDisplaySettings event handler is implemented. The event occurs when the client application display parameters are changed. The Width and Height properties of the ClientDisplayInformation object store the actual values (which depend on the screen orientation).	This feature was not provided. The platform could not detect the changes of display parameters. The Width and Height properties of the ClientDisplayInformation object stored constant (canonical) values.	You can handle the display size changes caused by mobile device orientation changes or by connecting the mobile device to external displays. You can create applications with better usability.
Multimedia support.	Photo shoot and video recording quality control implemented (for Android only). Camera control for photo shoots and video recording is implemented. In the MultimediaTools object, for the PhotoSupported() and VideoRecordingSupported() methods, the CameraType parameter is implemented. In the MultimediaTools object, for the MakePhoto() method, the CameraType, Resolutions, Quality, and Monochrome parameters are implemented. For the MakeVideoRecording() method of the MultimediaTools object, the CameraType and Quality parameters are implemented. For the MultimediaTools object, the GetSupportedCameraResolutions() method is implemented.	These features were not provided.	Extended capabilities for mobile device cameras.
Printing.	On the mobile platform, you can print spreadsheet documents. Printers that use PCL3 and ZPL protocols are supported. WiFi and Bluetooth are used for connecting to printers (only for Android).	This feature was not provided.	You can print spreadsheet documents from mobile applications.
Configuration properties.	The documentation now contains the description of the mobile platform compatibility mode: It cannot be managed from Designer. It is not changed when an infobase is migrated to a new platform version. It is set during the infobase creation as its mobile platform version. It is changed to the new mobile platform version when an infobase is migrated to a new mobile platform version. The documentation also describes the correspondence of PC platform versions and mobile platform versions.	The mobile platform compatibility mode was not described in the documentation.	The documentation is updated with the latest information.
Managed forms. Development tools.	Asynchronous dialog box operations are available to mobile platform developers. Selecting Mobile device in the Use purposes configuration property does not change the Modality usage mode configuration property.	Only synchronous dialog box operations were available to mobile platform developers. When the Mobile device value was selected in the Use purposes configuration property, a request to confirm the change of the Modality usage mode configuration property value was displayed (only if the change was required).	Applied solution development for the mobile platform is simplified. Developers no longer need to support two sets of dialog box operations, one for the mobile platform and the other one for the PC platform.
1C:Enterprise script.	In the mobile platform, the language of generated names of form items, form attributes, form commands, form parameters, and structure properties is defined by the value of the Script variant configuration property.	In the mobile platform, the language of generated names of form items, form attributes, form commands, form parameters, and structure properties was English only if the default configuration language was English. Otherwise it was Russian.	The mobile platform behavior is uniform with the PC-based platform behavior.
Development tools.	Push notification and local notification support is implemented. This feature relies on Apple push notification service and Google Cloud Messaging. The option to display the number of notifications that are not yet processed is implemented: mobile application icon badges (for iOS) or status bar notifications (for Android). Devices running Android 4.1 or later display the notifications diferently from devices with earlier Android version. A dedicated service provided by 1C Company is implemented to simplify the development of notifications for applied solutions that run on the PC platform. Notification senders can choose between using this service, Apple push notification service, and Google Cloud Messaging. For the mobile platform, the DeliverableNotifications global context property, the DeliverableNotificationManager object, and the DeliverableNotification object are implemented. For the PC platform, the DeliverableNotificationSend global context property, the DeliverableNotificationSendManager object, and the DeliverableNotification object are implemented. For mobile applications, the Push notifications and Local notifications permissions are implemented. The mobile application builder supports building mobile applications that use notifications.	This feature was not provided.	You can use standard user notifications in mobile applications. Notifications can be generated either by a mobile application on the mobile device (local notifications) or by an applied solution running on a PC (push notifications).
Dynamic lists.	Improved performance of dynamic list opening. The process of loading list data now has a visual presentation.	The process of loading dynamic list data had no visual presentation and took more time.	Optimized dynamic list operations.
Internet-enabled functionality.	The following mobile platform features support secure connection (HTTPS): HTTP operations POP3 and SMTP email operations Support of IMAP email operations (including secure connection) is implemented. Support of client certificates and certification authority center certificates stored in files is implemented. In the mobile platform the FileClientCertificate, FileCertificationAuthorityCertificates, and OpenSSLSecureConnection objects are implemented, together with the corresponding properties of the HTTPConnection, InternetMailProfile, and InternetMail objects.	The mobile platform did not support the following features: Secure connection for HTTP, POP3, and SMTP operations IMAP email operations Client certificate operations and authority center certificate operations.	The mobile platform supports secure operations with email and with other resources.
Error handling.	In the mobile platform for developers, you can obtain error details (the Details button in the error dialog box) and information for technical support (in the About 1C:Enterprise window).	Error details and information for technical support were not available in the mobile platform.	Improved issue diagnostics in the mobile platform for developers.
Interface.	New interface for the mobile platform client application, with a large number of improvements. The most significant changes are: The interface style is derived from the Taxi interface, but optimized for mobile devices to maximum extent. The interface appearance is revamped. This change affects the form design, primary colors, and the look of form items. The interface now matches the modern mobile interface standards. The main application menu is revised. The main section command interface is revised. Navigation options are revised. A form and main section command interface can be both present on the start page. Form command bar placement and generation rules are modified. The option to display a form navigation panel is implemented. The text input field is optimized for touch screen devices. The form title is no longer duplicated in the form body. Users have the option to create a list item when selecting a value from a drop-down list. Form item context menus are supported. Fields that require filling are not highlighted. New display options for page groups are implemented. Search in dynamic lists is implemented. It is based on full-text search. A dynamic list can be sorted by tapping a column header. Table operations are significantly revised, including scrolling, table item selection, and row rearrangement. In managed form tables the multiple selection option is implemented. The option to update a list by pulling the list down or up when the first or last row is on the screen ("pull to refresh") is implemented. The approach to handling the current row of a managed form table is changed. A managed form table is automatically scaled to fit displayed data by height, unless it displays dynamic list data. Spreadsheet documents can be scaled using gestures. User message appearance is revised. Subsystems are supported (and available in the interface). The radio button field and the track bar field are implemented. For a managed form table the RefreshRequestProcessing event is implemented. For the FormPagesRepresentation system enumeration the Swipe value is implemented. For a managed form table the RefreshRequest property is implemented. The Move up/Move down standard table commands are removed. For a managed form command the Use current row and Associated table properties are implemented (not available from 1C:Enterprise script). For a managed form button the Representation in context menu property is implemented (not available from 1C:Enterprise script). Many other features are implemented. The full list of changes is quite long, therefore it is recommended that you read the chapter about mobile application development in 1C:Enterprise Developer Guide.	The mobile application interface was similar to managed application interface version 8.2.	The mobile application interface meets the modern requirements to mobile interfaces. Improved mobile application usability. New interface uses the same color scheme and style as the Taxi interface, at the same time it is optimized for mobile devices.
Managed forms.	For devices that run Android operation system, predictive text input in multiline text boxes is implemented (with optional automatic correction of the entered text). This feature is available when it is enabled in the virtual keyboard settings.	This feature was not provided.	Improved usability for text input.
Mobile application builder.	In mobile application builder, you can publish an application to Apple App Store and Google Play directly from the builder. The mobile application builder help describes how to connect to Google Play Market.	This feature was not provided. Mobile applications required manual publishing.	Publishing mobile applications to Apple App Store and Google Play is simplified.
Dynamic lists.	The option to specify dynamic list settings using 1C:Enterprise script is implemented. The DynamicList.SettingsComposer property is now available on the mobile platform. The following objects are implemented: DataCompositionSettingsComposer, DataCompositionUserSettings, and DataCompositionSettings, as well as their constructors and methods. Their methods are not available on the mobile platform. The DataCompositionUserSettingsItemCollection object is implemented.	This feature was not provided.	Работа с настройками динамического списка на мобильной платформе приближена к возможностям платформы для персонального компьютера.
Dynamic lists. Interface.	When the selection mode is on, dynamic list rows that represent parent groups have left arrows displayed.	When the selection mode was on, dynamic list rows that represented parent groups did not have left arrows displayed.	Improved navigation of hierarhical dynamic lists in the selection mode.

Table of contents

Library updates

The libxml2 library is updated from version 2.6.23 to version 2.9.1.
The libxslt library is updated from version 1.1.24 to version 1.1.28.
The OpenSSL library is updated from version 1.0.0o to version 1.0.0s.
The libpng library is updated from version 1.2.19 to version 1.6.19.
The libtiff library is updated from version 3.7.0 to version 4.0.3.
Known vulnerabilities of cURL library are elimitaned.

Table of contents

Transition from the previous version to the version 8.3.6

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.6.
Some features that are added in version 8.3.6 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.

Table of contents

Version 8.3.5

Version 8.3.5 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.5

New functionality and changes

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.3.4 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, and 8.3.3.	In version 8.3.5 you can run configurations created in version 8.3.4 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.5 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.4 for working with the infobase even after the transition to version 8.3.5. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Development tools.	In Designer, new icons for external data source tables and cubes are implemented.	Pictures for external data source tables and cubes were different.	Icons for external data source tables and cubes are uniform with other platform pictures.
Development tools.	In Designer, you can filter objects by parts of names, synonyms, comments, or presentations. The filter is available in the following windows: Configuration window Configuration object selection dialog box Type editing dialog box Object properties window For the Subsystem configuration object, a quick filter is implemented in the configuration window. The filter is available from the Subsystem objects context menu command of the object. In the configuration window, you can set a quick filter for configuration repository objects locked by the current user.	This feature was not provided. Only filtering by objects included in subsystems was available.	Improved usability for developers.
Interface.	1C:Enterprise script provides tools for managing start page (desktop) form contents and positions. The StartPageForms object is implemented. For the StartPageSettings object, the GetForms() and SetForms() methods and the default constructor are implemented. The global context method RefreshInterface() rebuilds the start page (desktop) based on the settings from the system settings storage.	The StartPageSettings object stored the differences between the start page (desktop) settings of the client application and the settings specified in Designer. 1C:Enterprise script did not provide tools for managing form contents and positions.	You can manage contents and positions of the client application start page (desktop) forms using 1C:Enterprise script.
Administration tools.	For the Purpose column of value table returned by the GetDBStorageStructureInfo() method, new purposes are specified. The full list of database table purposes is available in the description of the GetDBStorageStructureInfo() method in the Syntax Assistant.	The list of table purposes did not fully describe the current database schema.	The purposes of database scheme tables are described more clearly.
Data exchange.	For exchange plans, the ThisNode standard attribute is implemented. It specifies whether the exchange plane node describes the current infobase. For the ExchangePlanObject object, the DataExchange property is implemented. Only the Load property can be used in this property. The DataExchange property is used for disabling the uniqueness check of the ThisNode item when exchange plan items are edited or deleted. This change is not implemented in 8.3.4 compatibility mode.	The ThisNode standard attribute was not available in exchange plans. Replacing the exchange plan node that described the current infobase was impossible. The ExchangePlanObject object did not have the DataExchange property.	You can define ThisNode items in a distributed infobase in a session that does not use separators. You can replace the data item that describes the current infobase in the exchange plan.
Managed forms.	For managed form text boxes, the EditTextChange event is implemented. This event occurs when one of the following actions modifies the text box content: Typing in the text box Copying text from the clipboard Running Undo or Redo command Canceling input by pressing ESC The event occurs before the AutoComplete event.	There was no event that occurred when text box content was modified. Actions triggered by this modification could be performed in the AutoComplete event handler (with limitations).	In managed forms, complete implementation of the following scenario is available: text being typed in a text box is used as a filter parameter in the linked dynamic list.
Development tools.	New features in the module editor: Find all usage instances of an export variable, procedure, or function in the entire configuration. Convert a selected code fragment to a separate procedure or function. Rename a local variable, procedure, or function. Insert a comment block that describes the function or procedure purpose, parameters, and return value before the function or procedure declaration. Convert modal calls to nonmodal calls (in a limited set of cases). Convert procedures or functions to types that can be used in sequences of asynchronous calls. Convert a selected code fragment to a separate procedure or function suitable for using in sequences of asynchronous calls. Find all usage instances of modal methods in the specified module. Convert all modal methods that are found to their asynchronous analogs. Create notification processing events for methods that lock the interface. Commands that perform these functions are located in the Refactor submenu of the module text editor context menu and in the Configuration section of the Designer main menu.	These features were not provided.	Improved efficiency of routine operations performed by developers.
Managed forms.	In text boxes that display values of StandardBeginningDate type, in the date input mode, the AutoComplete (on value input) and TextEditEnd (on generating a value based on the input string) event handlers are implemented. This change is not implemented in 8.3.4 compatibility mode.	In text boxes that display values of StandardBeginningDate type, in the date input mode, the AutoComplete (on value input) and TextEditEnd (on generating a value based on the input string) event handlers were not implemented.	The behavior of text boxes linked to values of StandardBeginningDate type in the date input mode is identical to behavior of text boxes linked to values of Date type.
Client application.	The option to follow a navigation link during client application startup is implemented, with the navigation link passed as a parameter. This feature is implemented for the 1C:Enterprise launcher, thin and thick clients, the GotoURL() method, the standard full-text search form, and the new Go to link command in the startup window. Only external navigation links (which contain infobase connection settings) are supported. When following a link, the platform attempts to use running client application instances connected to the infobase specified in the navigation link. In 8.3.4 version compatibility mode, the GotoURL() method is not modified. The /url startup option is implemented for the launcher, thin client, and thick client.	This feature was not provided. Users could only follow external links when they accessed the infobase using the web client.	Simplified access to infobase data if a link to this data is provided by third-party tools, such as email.
Internet-enabled functionality.	For the InternetMailMessage object, the GetSourceData(), SetSourceData(), and GetSourceText() methods are implemented. These methods are intended for getting original email messages without changing the encoding and processing source texts of messages whose encoding was changed.	This feature was not provided.	You can save email messages to files and load them from files, provided that they comply with RFC 822 URL9, and you can also perform custom processing of email message source texts.
Data display. Charts.	Animated charts are implemented. The Animation property is implemented for the Chart object. The ChartsViewSettings object is implemented. The chart display settings are stored in the system settings storage. This change is not implemented in 8.3.4 compatibility mode.	This feature was not provided.	More chart display options are available.
Web services and HTTP services. Data exchange. Database operations. Web client and web service publishing tools.	1C:Enterprise infobase data can be retrieved and modified using the OData protocol (read more) v3 (read more). The following data presentation is supported: atom-xml. Enabling this feature does not require modification of applied solution, it is performed using a web server publication. The enableStandardOData attribute is implemented for <point> tag in the default.vrd file. In 8.3.4 version compatibility mode, all configuration objects that support OData protocol are available through this interface. If the compatibility mode is disabled, the access to objects is managed using the SetStandardODataInterfaceContent() method.	Universal access to 1C:Enterprise infobase data was only available on Windows operating systems and was based on COM/OLE features. It was not available on Linux. The option to access data using web services implemented in applied solutions was also available.	Extended integration features for 1C:Enterprise data, including data access from external Linux systems, which does not require modification of applied solutions .
Configuration repositories.	Optimized selective comparison of forms, access rights, and command interface fragments in scenarios where the configuration repository is located on a network drive or on a repository server. Local data cache is implemented for configuration repositories. You can manage the size and location of local and global repository caches using the configuration repository administration settings dialog box or cfgrepo.conf configuration files. These files are located in the cfgrepo subdirectory of the infobase service files directory (for the local cache) or in the configuration repository directory (for the global cache). The following features are implemented for batch Designer startup mode: Clearing the global configuration repository cache (the /ConfigurationRepositoryClearGlobalCache command-line option) Clearing the local configuration repository cache (the /ConfigurationRepositoryClearLocalCache command-line option)	The selective comparison of forms, access rights, and command interface fragments lacked efficiency if the configuration repository was located on a network drive or on a repository server. Editing the size and location of the global configuration repository cache was not available. The local cache for configuration repository data was not available.	Selective comparison and some other configuration repository features are optimized. You can manage the size and location of configuration repository data cache.
Dynamic lists.	Extended search capabilities in tables that display dynamic lists. A standalone search string box that provides full-text search is implemented. Search by current cell value is available. The search history is implemented. The current search state is clearly visible. The search result includes items that have search words located both in a single column and in different columns. In each column, search by a single value is available (the Find in search results option is not supported). For automatically created forms that contain tables linked to dynamic lists, the set of items related to search in dynamic lists is modified (together with their appearance). The search dialog box layout is modified. The new FormItemAddition managed form item stores additional properties of form items. Extensions of form items intended for displaying a search string, a view status, and a search control are implemented. For the FormTable managed form item, the predefined items SearchString, ViewStatus, and SearchControl, and also properties SearchStringLocation, ViewStatusLocation, and SearchControlLocation are implemented. The search history is stored in the system settings storage with the following key: Common/TableSearchHistory/<Form name>.<Table name>. The SearchControl picture is added to the picture library.	Search in tables was performed using the search dialog box. The option to search a column by multiple values (the Find in search results check box) was available. The search dialog box had a different layout. There was no simple way to determine whether the search is applied to a table (except for checking the availability of the Cancel search button if it was present on the command bar).	The search in managed form tables is improved, it is clearly visible whether the search is applied to a table.
Web services and HTTP services.	Developers can create HTTP services in applied solutions. Developers can access HTTP request body, headers, and line. Publishing HTTP services is similar to publishing web services. To access HTTP services, use URLs of the following format: http://<host name>/<base name>/hs/<resourсe identifier>. You can create HTTP services in the Common/HTTP services branch of the configuration tree. The following objects are implemented: HTTPServices, HTTPService, HTTPServiceRequest, and HTTPServiceResponse.	This feature was not provided. Only access to web services implemented in the applied solution was available.	You can create services that have the following advantages over web services: Simpler implementation. Less amounts of data transferred. Less computing power is required to parse a response. A different usage model (RESTful services).
Client application. Database operations.	The Hibernated session state is implemented, which is intended for preserving sessions after unexpected connection losses. Sessions that require licenses release the occupied licenses once they are hibernated. If a connection is assigned to a hibernated session, the session loses its Hibernated state. During the recovery from hibernation, sessions that require licenses attempt to obtain licenses. If a license cannot be obtained, the session is terminated. The option to set a timeout for automatic shutdown of hibernated sessions is implemented. If a connection to the client is closed by the 1C:Enterprise server, the session is hibernated(instead of being terminated). For the ISessionInfo object, the following properties are implemented: Hibernate, PassiveSessionHibernateTime, and HibernateSessionTerminateTime. New global context methods are implemented: SetPassiveSessionHibernateTime(), GetPassiveSessionHibernateTime(), SetHibernateSessionTerminateTime(), and GetHibernateSessionTerminateTime(). The hibernation timeout and the timeout for closing hibernated sessions can be set in Designer, in the infobase parameters dialog box.	This feature was not provided. If a client application was inactive for 20 minutes, the session was closed.	In the client/server mode, in some scenarios the client application continues functioning even when the client computer stays in hibernation mode for a long time.
Data composition system.	In the data composition system, new options are implemented for comparison of string data: BeginsWith, NotBeginsWith, Like, and NotLike.	This feature was not provided.	Extended features for filtering by string expressions in reports created using the data composition system and in dynamic lists.
Applied objects.	For catalog, chart of characteristic types, chart of accounts, chart of calculation types configuration objects, the GetPredefinedNames() method is implemented.	This feature was not provided.	You can get the flag indicating that a configuration object has predefined items, as well as the full list of predefined item names. Using this list, you can check whether data items are set for all predefined items.
External data sources.	You can write data to external data source tables. This feature is intended for integration with other applications, external sources should not be used as applied solution data storages.	This feature was not provided. External data source table data was read-only.	New options for integration with information systems and databases.
Queries.	A query wizard for managed mode is implemented. For the QueryWizard object, the Show() method is implemented. The following pictures are added to the picture library: Rename, Attribute, Dimension, Resource, NestedTable, QueryWizardShowChangesTables, QueryWizardCreateNestedQuery, QueryWizardCreateTempTableDescription, QueryWizardReplaceTable, QueryWizardTableParameters, QueryWizardCreateTempTableDropQuery QueryWizardTempTableDescription, QueryWizardGroupTempTables, QueryWizardTempTable, QueryWizardNestedQuery, and CustomExpression.	This feature was not provided.	New features for using queries in managed applications.
Queries.	An object model intended for modification of query texts is implemented. The QuerySchema object is implemented.	This feature was not provided.	You can modify queries from 1C:Enterprise script without analyzing the query text.
Spreadsheet documents.	You can insert pictures in spreadsheet document cells. You can specify text position relative to the picture in a cell (or an area of cells) of a spreadsheet document. A picture is linked to a cell where it is inserted. For the SpreadsheetDocumentRange object, the following properties are implemented: Picture, PictureSize, PictureHorizontalAlign, PictureVerticalAlign, TextPositionRelativeToPicture, and PictureParameter.	Pictures could only be inserted in spreadsheet documents as images that were not linked to any specific cell (or an area of cells).	Improved usability of pictures in spreadsheet documents.
System requirements.	Alt Linux SPT 6.0 distribution kit is supported.	This distribution kit was not supported.	New Linux distribution kit is supported.
Data composition system.	For the DataCompositionFilter object, the default constructor is implemented.	This feature was not provided.	In a mobile application, you can set a filter for a list of contacts.
Event log.	The _$Data$_.TotalsMaxPeriodUpdate event with presentation Data.Modify maximum calculated totals period is implemented. The event is registered when the SetMaxTotalsPeriod() or SetMinAndMaxTotalsPeriods() method is called. The _$Data$_.TotalsPeriodUpdate event is used for compatibility purposes.	The _$Data$_.TotalsPeriodUpdate event was registered when the maximum totals period was set.	The event log displays actions that set the totals period more consistently.
Linux. Client application.	1C:Enterprise searches for the ImageMagick library by name libMagickWand-6.Q16.	1C:Enterprise did not search the ImageMagick library by name libMagickWand-6.Q16.	During the startup, 1C:Enterprise is not shut down if the ImageMagick library was renamed and then reinstalled.
DBMS operations.	Microsoft SQL Server 2014 DBMS is now supported.	Microsoft SQL Server 2014 DBMS was not supported.	New Microsoft SQL Server version is now supported.
Developer tools.	For the Technological log configuration file editor (read more) and User action log conversion (read more), data processors, which are distributed via 1c-dn.com, the English interface is implemented. Both data processors are rewritten using the English variant of 1C:Enterprise script.	The Technological log configuration file editor and User action log convertor data processors had Russian interface only. Both data processors were written using the Russian variant of 1C:Enterprise script.	Simplified usage and modification of the Technological log configuration file editor and User action log convertor data processors for non-Russian-speaking developers.
Development tools.	In the "dump configuration to files" feature, the approach to dumping standard attribute data is modified. Only attributes whose properties differ from the default values (for the given attribute) are dumped. Changing properties of a single standard attribute results in dumping all of the standard attributes of the configuration object. The same behavior is implemented for loading: if an XML file contains a description of a standard attribute, it is loaded to the configuration even if the description of the standard attribute contains only default values. An external data processor intended for deleting descriptions of standard attributes with default values from XML dump files is implemented. The data processor can be used only with files dumped by 1C:Enterprise version 8.3.5. You have to use it once before loading the dumped files back to the configuration.	While dumping configuration files, standard attribute data was always dumped, even if all of the standard attribute properties had default values.	Reduced configuration file size. Reduced number of "different" objects found when comparing configurations after dumping and subsequent loading.
Predefined data. Applied objects. Common attributes / Data separation.	You can edit the flag that shows whether predefined data is initialized in a data area or in the entire infobase. The GetPredefinedDataInitialization() and SetPredefinedDataInitialization() methods are added for catalog managers, charts of characteristic types, charts of accounts, and charts of calculation types. This change is not implemented in 8.3.4 compatibility mode.	Editing the flag that shows whether predefined data is initialized in a data area or in the entire infobase was not available.	Extended capabilities for processing predefined data. You can inform the system at any time that predefined data in a data area or in the entire infobase is initialized (or not initialized). In a distributed infobase, when you remove infobase subordination to the master node, you can specify that all of the predefined data items are created in the infobase whose subordination is being removed.
System requirements.	Microsoft Windows Server 2012 R2 (x86-64) is now supported.	Microsoft Windows Server 2012 R2 (x86-64) was not supported.	New version of the Microsoft operating system is now supported.
Server clusters. Administration tools.	You can use an external utility for generating dumps when the platform stops responding. In the logcfg.xml file, the externaldump attribute of the dump element is implemented. The dumper.exe utility, which is now included in the platform delivery kit, is implemented.	Dumps were generated by the process that stopped responding.	Eliminated the issue where the system stopped responding while generating a dump for a process that stopped responding.
Data exchange.	The instructions for unbinding an infobase from the root node and restoring a configuration in a distributed infobase node, which take into account the specifics of predefined data usage, are available in the platform documentation.	This information was not available in the documentation.	The documentation contains recommendations for using distributed infobases that include predefined data.
Client application. Managed forms.	In thin and thick client applications, the system behavior based on the Modality usage mode configuration property value is modified. For thin and thick client applications, the EnableCheckModal startup parameter is implemented. If EnableCheckModal is not used, modal methods are executed without any warnings or exceptions. If EnableCheckModal is used, executing a modal method generates a warning or an exception (depending on the Modality usage mode configuration property value). When an applied solution is started from Designer, the EnableCheckModal parameter is automatically added to the applied solution command line (this behavior cannot be disabled). The web client behavior is not modified: the command-line parameter is not used. The web client always generates a warning or an exception (depending on the Modality usage mode configuration property value) when modal methods are executed.	The modal method behavior was based on the Modality usage mode configuration property value only. Depending on this property value, modal methods were executed with warnings or exceptions. This behavior could not be changed using command-line parameters.	You can use external data processors that include modal methods in applied solutions where modality is disabled.
System requirements.	Support of Microsoft Windows 8.x operating system is implemented.	Microsoft Windows 8.x operating system was not supported.	Extended list of supported operating systems.

Table of contents

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Client application installation.	While the client application is being updated via the Internet, a dialog box displaying the progress of downloading the distribution kit from the server is being displayed. You have the option to cancel the download.	While the client application was being updated, the progress of downloading the distribution kit was not displayed.	Improved process of updating the client application using Internet services: the progress is displayed and the download can be canceled.
Client application.	The Help window is opened like any other form: In the Forms in separate windows mode, it is opened in a separate window. In the Forms in tabs mode, it is opened in a tab. In the Taxi mode, it is opened in the main window working area. If help is opened from a form that locks the entire interface, it is opened on top of all windows and locks the entire interface. If help is opened from a modal form, it is opened in a modal form. The help command bar is modified. The search is started either when the focus leaves the search text box or when the user clicks Find.	Help was always opened in a new window, regardless of the main application window interface settings. The help command bar had different content. The search started while the search expression was still being typed (during a pause in the typing).	The behavior of the Help window is unified with other forms.
Configuration installation.	New splash screen in the configuration installation wizard.	The configuration installation wizard used a different splash screen.	The configuration installation wizard and the platform installation wizard have uniform looks.
Client application.	If OpenID authentication is available in an infobase, once you run the thin client and select the infobase, the authentication dialog box will display the name of the last authenticated user.	The user name box in the OpenID authentication dialog box was always empty.	The user name box behavior is uniform for all authentication methods.
Predefined data.	When a catalog, chart of characteristic types, or chart of accounts folder is marked for deletion, unmarked for deletion, or deleted, the platform checks whether the user has enough rights to access subordinate predefined objects.	When a catalog, chart of characteristic types, or chart of accounts folder was marked for deletion, unmarked for deletion, or deleted, the platform did not check whether the user had enough rights to access subordinate predefined objects.	The platform does not allow deletion of a catalog, chart of characteristic types, or chart of accounts folder if the folder contains a predefined item and the user does not have the right to delete that item interactively.
Web client.	When the web client is started in Google Chrome web browser on MacOS X operating system, the message that the web browser is not supported is not displayed.	When the web client was started in Google Chrome web browser on MacOS X operating system, the message that the web browser was not supported was displayed.	Improved usability of applied solution startup in the web client that is started in Google Chrome web browser on MacOS X operating system (the message is removed). Support of this web browser is subject to further discussion.

Table of contents

Optimization

Functionality	After	Before	Result of changes
Common attributes / Data separation. File mode.	In separated infobases that run in the file mode, query execution is optimized.	In separated infobases that ran in the file mode, query execution lacked efficiency.	Improved performance of separated infobases that run in the file mode.
Managed forms.	In some scenarios, forms are opened faster.	Opening forms was not optimized.	Improved system performance in some scenarios.
Database operations.	Improved performance of establishing a connection to an infobase that is running in the file mode and located on a network resource.	The performance of establishing a connection to an infobase that was running in the file mode and located on a network resource was insufficient.	For the second and following users, improved performance of establishing a connection to an infobase running in the file mode and located on a network resource.
1C:Enterprise script.	Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties.	The performance of the following operations was insufficient: execution of 1C:Enterprise script methods and getting configuration object properties.	Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties.
Accounting registers.	Improved performance of writing to accounting registers for record sets that contains no more than 10 records.	When a record set with no more than 10 records was written to an accounting register, the writing performance was insufficient.	Optimized accounting register operations.
DBMS operations. Accounting registers. Common attributes / Data separation.	In the client/server mode with IBM DB2 or Oracle Database DBMS, improved performance of writing to accounting registers that are included in the contents of common attributes used as separators.	In the client/server mode with IBM DB2 or Oracle Database DBMS, the performance of writing to accounting registers included in the contents of common attributes that were used as separators was insufficient.	Optimized accounting register operations in the client/server mode with IBM DB2 or Oracle Database DBMS.

Table of contents

Changes that affect system behavior

Functionality	After	Before	Result of changes
Defined types.	The list of types that can be included in defined types is significantly extended. You can use defined types in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators. The algorithm of the configuration check for correct usage of defined types is modified: a defined type is considered valid (in each usage instance) if all types that form the defined type are valid when the check is performed. The configuration check algorithm is not modified in 8.3.4 compatibility mode.	The list of types that could be included in defined types was significantly shorter. The configuration check was performed as follows: check whether the defined type only includes allowed types, and check whether the defined type is not included in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators.	New defined type usage options in applied solution development. Particularly, integration of applied solutions with third-party subsystems is now simpler.
Development tools.	The order of standard attributes in the standard attributes window and in the role settings is modified. The form wizard allows adding predefined data name fields to forms.	The list of standard attributes in the standard attributes window and in the role settings was not ordered. The form wizard did not allow adding predefined data name fields to forms.	Display of standard attributes is uniform with other system features.
Client application.	For text documents, the Save as command now saves the document encoding, provided that one of the following encodings is used: ANSI, OEM, UTF-8, or UTF-16. Otherwise, the UTF-8 encoding is set. Closing the Save as dialog box by clicking Cancel does not modify the encoding of the open document. This change is not implemented in 8.3.4 compatibility mode.	For text documents, the Save as command set the UTF-8 encoding for the document being saved, regardless of the encoding that was used when the document was opened. Closing the Save as dialog box by clicking Cancel set UTF-8 encoding for the open document.	Eliminated unexpected system behavior.
Managed forms. Dynamic lists.	In the Customize form dialog box, the DataVersion field cannot be added to a form.	In the Customize form dialog box, the DataVersion field could be added to a form.	Eliminated unexpected system behavior.
Background and scheduled jobs.	At the start of a background job, the SessionParametersSetting event handler is run after the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on).	At the start of a background job, the SessionParametersSetting event handler was run prior to the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on).	Eliminated unexpected system behavior.
Common attributes / Data separation. Information registers. Accumulation registers. Accounting registers. Calculation registers.	The configuration check and database configuration update include the check whether registers affecting a sequence are included in the same separator content as the documents included in the sequence. If a register affecting a sequence is included in separator content and a document included in a sequence is not included in the content of this separator, the separator is ignored when sequence boundaries are updated in 1C:Enterprise mode.	The check for correspondence between separators included in a document sequence and registers affecting this sequence was not performed.	Eliminated unexpected system behavior.
Temporary storages.	The volume of data transferred between the client and the server cannot exceed 4 GB (in the serialized form) in the following cases: Setting a session parameter Single call of the PutToTempStorage() method Single call of the PutFile() or PutFiles() method An attempt to transfer more than 4GB leads to an unrecoverable error.	During an attempt to transfer more than 4GB of data (in serialized form) to the server, the client application stopped responding.	Eliminated unexpected system behavior.
Internet-enabled functionality.	The cURL library is updated to version 7.32. It supports new options, such as downloading files with Cyrillic names from FTP servers.	The cURL library version 7.18.2 was used.	Resolved some issues of the previous library version.
XML and XDTO support.	If an error related to an attempt to write an invalid character to an XML object occurs at the server side, an unrecoverable error is not generated at the client side, and the user is not prompted to restart the client application. The error can be handled using the Try...Except syntax.	If an error related to an attempt to write an invalid character to an XML object occurred at the server side, the unrecoverable error was generated at the client side, and the user was prompted to restart the client application.	Eliminated unexpected system behavior.
XML and XDTO support.	If the FindDisallowedXMLCharacters() method finds an incomplete surrogate Unicode pair, it returns the position of the first character of the incomplete pair.	If the FindDisallowedXMLCharacters() method found an incomplete surrogate Unicode pair, it returned the position of the character that followed the first character of the incomplete pair.	Eliminated unexpected system behavior.
Managed forms.	In a text box that is in the "choice from the list" mode and displays an empty reference, clicking the Cancel button is ignored.	In the text box that was in the "choice from the list" mode and displayed an empty reference, clicking the Cancel button displayed a dialog box with Undefined text.	Eliminated unexpected system behavior.
Navigation links.	When a navigation link is followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation link are ignored. This feature is implemented in the following scenarios: The GotoURL() script method Following a navigation link from the Go to link dialog box (including the scenario when the link is pasted from the clipboard) Adding a link to Favorites from the Go to link dialog box	When navigation links were followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation links were ignored. Users had to delete these characters manually.	Improved management of navigation links.
XML and XDTO support. Web services.	When string values are read using the XMLReader object or obtained using a web service, line feed characters keep their original format (they are not converted). This change is not implemented in 8.3.4 compatibility mode.	When string values were read using the XMLReader object or obtained using a web service, the following replacements were made: Combinations of line feed characters 0x0D+0x0A (CR+LF) and 0x0D (CR) were replaced with 0x0A (LF). Combination of characters 0x0A+0x0D (LF+CR) was replaced with 0x0A+0x0A (LF+LF).	Eliminated unexpected system behavior.
Spreadsheet documents. XML and XDTO support.	Settings of text boxes located in spreadsheet documents can now be serialized to XDTO. A spreadsheet document deserialized from XDTO is equivalent to its source.	During XDTO serialization of spreadsheet documents and the following deserialization, text box settings were lost.	Settings of text boxes located in spreadsheet documents are saved after dumping/loading configuration to/from XML files.
Development tools.	In the Evaluate expression dialog box and in the Immediate window, expressions are not calculated twice in the following cases: Opening a value that has properties Viewing a property as a collection of values in a separate window Viewing property values in a separate window intended for viewing a collection Viewing a string value in a separate window	In the Evaluate expression dialog box and in the Immediate window, expressions were calculated twice in the following cases: Opening a value that has properties Viewing a property as a collection of values in a separate window Viewing property values in a separate window intended for viewing a collection Viewing a string value in a separate window	Eliminated the issue that introduced inaccuracies to the calculated expression result because the expression could only be calculated once (at the current debugging step).
Configuration repositories.	You can perform selective comparison of form modules without building a form comparison report. The Form (module) command is added to the following context menus: Perform selective comparison with the repository object, Perform selective comparison with the configuration object, and Perform selective comparison of object versions.	During selective comparison of forms, two comparisons were performed: the comparison of form modules and the comparison of forms. Two reports were displayed as a result of comparison.	Improved usability of selective comparison. Comparison of form modules is now a separate command.
Data composition system.	In data composition system, the automatically generated title of a field linked to data retrieved using "." (dot) from a Ref field of a tabular section contains the field presentation only. In particular, a field related to the TabularSection.Ref.Number attribute will have the Number title. This change is not implemented in 8.3.4 compatibility mode.	In data composition system, the automatically generated title of a field linked to data retrieved using "." (dot) from a Ref field of a tabular section contained the Ref word and a presentation of the data attribute retrieved using "." (dot).	Improved appearance of reports.
Managed forms.	Pessimistic lock of data described by the main form attribute is performed for the following actions in text boxes: Clicking the drop-down list button Attempting to create an item from the drop-down list Attempting to open a choice list Starting text input If the lock cannot be set, the action is not performed.	Pessimistic data lock was set for the following actions in text boxes: Attempting to open a choice list Starting text input	Pessimistic data lock is set for all actions that change text box contents.
XML and XDTO support. Development tools.	In the "dump configuration to files" feature, XML file format is changed for the following configuration parts: managed forms, dynamic list settings, graphical schema items, geographical schemas, functional option content, and field lists. Tag names now match the names used in 1C:Enterprise script, the XML element name spelling is unified. The dump format is more compact and clear. The properties filled with default values are not dumped. Dynamic list settings are dumped to a single element, which has the data composition schema settings format. Managed forms dumped using the previous platform versions cannot be loaded by the latest platform version.	In the "dump configuration to files" feature, XML files that stored managed forms, dynamic list settings, graphical schemas, geographical schemas, functional option content, and field lists had a different format.	XML files that store configuration data are more compact and better structured.
Charts of accounts. Accounting registers. Data exchange.	While a chart of accounts item is being written with DataExchange.Load property set to True, new extra dimension types are checked for uniqueness. The unique ones are added to the table of extra dimension values, and the nonunique values are not added, which eliminates possible errors.	If a chart of accounts item was being written with DataExchange.Load property set to True, the check for uniqueness of extra dimensions was not performed. This could cause errors while items were being added to the table of extra dimension values.	The order of loading chart of accounts data and data of linked accounting registers does not matter.
Development tools.	In the property palette, the Sort alphabetically command sorts properties by presentation (if displaying property names is disabled) or by name (if displaying property names is enabled). If a property does not have a name, the sorting is always performed by text presentation.	In the property palette, the Sort alphabetically command sorted properties by presentation.	The sorting command behavior depends on object property presentations.
Data composition system.	In the data composition system, the conditional appearance with Fields header usage area is applied to an area of a vertical template that contains names of displayed fields. The conditional appearance with Group usage area is applied to an aria of vertical template that contains values of displayed fields. This change is not implemented in 8.3.4 compatibility mode.	In the data composition syste, the conditional appearance with Group usage area was applied to all areas of a vertical template.	Improved usability of data composition system conditional appearance.
Thick client.	If more than two parameters are passed to the Insert() method of the TableBoxColumns object, an error is generated. This change is not implemented in 8.3.4 compatibility mode.	Up to five parameters could be passed to the Insert() method of the TableBoxColumns object, while only two parameters were used. No errors were generated.	Eliminated unexpected system behavior.
Event log.	The event log format is modified. The log is now stored in an SQLite database. The log file has .lgd extension. The log location is not changed. The SQLite log format is the default format for new infobases. The performance of accessing event log data is improved. Existing event logs can be converted to a new format. Conversion back to the legacy format is not supported. The CopyEventLog() and ClearEventLog() methods are implemented. The event log stores time in UTC format. The standard event log viewer supports new log file format (.lgd). In the standard event log viewer form the command for viewing a log stored in a file is renamed to More - View from file.	The event log had text format. In the standard event log viewer form the command for viewing a log stored in a file had the following name: More - Load from file.	Improved performance when accessing event log data. Improved event log reliability. Better name for the command for viewing a log stored in a file.
Event log.	Deletion of a large number of event log records (more than 10 million) takes much less time. You can terminate the reducing of event log size by pressing Ctrl+Break in Designer or by closing the session using administrative tools (as a result, a part of records is deleted, and the rest are not deleted).	The performance of event log record deletion was insufficient. Reducing the event log size could not be terminated.	Reducing the size of a large event log takes reasonable time. This operation can be terminated if needed.
Spreadsheet documents.	When a spreadsheet document is saved to a PDF file, a single document copy is saved. The Copies spreadsheet document property is ignored. To include multiple copies into the PDF file, use the WriteFileForPrinting() method of the RepresentableDocumentBatch object. This change is not implemented in 8.3.4 compatibility mode.	When a spreadsheet document was saved to a PDF file, the file contained the number of document copies specified in the Copies property.	Eliminated unexpected system behavior.
Client application. Development tools.	In Designer and thick client, customization of the search result selection background is available.	In Designer and thick client, the search result background color could not be customized.	Users can specify search result selection background color that fits their text editor settings.
Data exchange. Common attributes / Data separation.	In a session that does not use any separators, while session changes are being registered, the Update right is not required for tables of objects being registered. For sessions that use separators, the following features are implemented: Changes can be registered for an empty record set that is subordinate to a recorder. If any of the separators required for the record set are not used in a session, the separator values are obtained from the corresponding recorder fields. If the full set of separator values cannot be obtained using a recorder available in the memory, an error is generated and the change registration is stopped.	In a session that did not use any separators, while session changes were being registered, the Update right was required for tables of objects being registered. For sessions that used separators, registering changes for empty record sets that were subordinate to recorders was not available.	In separated mode, changes are registered correctly.
Common attributes / Data separation. Database operations.	New options for FindMarkedForDeletion(), FindByRef(), and DeleteObjects() methods: You can specify data areas that will be searched for references or where objects will be deleted. You can include configuration objects to (or exclude configuration objects from) search or deletion. For value tables that are returned by the FindByRef() and DeleteObjects() methods, a new column is implemented. It contains separator values that define the data area where the found object or the object that prevents deletion of another object is located. The DeleteObjects() method returns a value of Number type, which stores the number of deleted objects.	The search for references, search for objects marked for deletion, and deletion of marked objects were performed only in data available in the current session with the current separator values. Including individual configuration objects to (or excluding configuration objects from) search or deletion was not available. The value tables that were returned by the FindByRef() and DeleteObjects() methods did not contain columns with separator values. The DeleteObjects() method was a procedure.	You can customize the deletion of marked objects, especially in separated infobases. You can design more detailed messages about deletion results (total objects deleted, total objects not deleted, and so on).
Defined types.	In Designer, properties palette contents for objects that have defined type are generated based on the actual type that describes the defined type.	The properties palette contents for objects that had defined types were always displayed as if all of the objects had complex type, regardless of their actual types.	Property customization for objects that have defined types is now similar to property customization for objects whose types are specified explicitly.
Software licensing.	In the license activation dialog box, each PIN code is entered in a single text box, which includes an input mask (in all license acquisition scenarios). During license activation by phone, each Licensing Center response line is entered in a single text box, which contains an input mask). Pressing Tab switches between these text boxes. The license registration page contains the descriptions of activation options for 5-, 10-, and 20-user licenses. Extended error diagnostics during license activation is implemented.	In the license activation dialog box, each PIN code was entered in 5 text boxes (in all license acquisition scenarios). During license activation by phone, the license activation dialog box had 5 text boxes for entering each Licensing Center response line. Pressing Tab switched between the text boxes and response lines. Help for various license activation methods was not available directly in the dialog box. Some license activation error messages had complicated descriptions that might not be clear to users.	The software license activation dialog box is improved. PINs can be pasted from the clipboard. Improved usability of entering the response from the Licensing Center during license activation by phone. The error messages are clearer to users.
Common attributes / Data separation.	In version 8.2.16 or earlier compatibility mode, configuration checks and database configuration updates include the check whether each document journal is included in contents of at least one common attribute, and if it does, the appropriate diagnostics is performed. The configuration is not updated in this case.	In version 8.2.16 or earlier compatibility mode, the configuration check did not detect configuration errors if document journals were included in contents of common attributes, and therefore such errors did not prevent the configuration update.	The system cannot become inconsistent due to the fact that in version 8.2.16 or earlier document journals could not be included in common attribute contents.
Data composition system.	The GroupPlacement parameter of the data composition system does not affect the displaying of totals. This change is not implemented in 8.3.4 compatibility mode.	Grouping totals were not displayed if the GroupPlacement data composition system parameter was set to End or None for the selected grouping.	Eliminated unexpected system behavior.
Spreadsheet documents.	For cells that have single-line height, tooltips that do not fit a single text line are displayed as multiple text lines. This change is not implemented in 8.3.4 compatibility mode.	For cells that had single-line height, tooltips were displayed as single text lines. If tooltip text did not fit a single line, it ended with "...."	Eliminated unexpected system behavior.
Spreadsheet documents.	In the thin client, when a spreadsheet document is obtained from the server, empty rows located in document cells are preserved. This change is not implemented in 8.3.4 compatibility mode.	In the thin client, when a spreadsheet document was obtained from the server, empty rows located in document cells were lost.	Eliminated data loss during the transfer of spreadsheet documents from the server to the client.
Managed forms.	In a managed form table cell that has a drop-down list available and the Directly editing mode set, pressing Down Arrow or Up Arrow keys moves the selection to another cell and does not open the drop-down list. The drop-down list is only opened when a new row is added. To open the drop-down list, press Ctrl+Down Arrow.	In a managed form table cell (with the Directly editing mode set), pressing Down Arrow or Up Arrow keys might open a drop-down list. This eliminated the option to add a new row by pressing Down Arrow.	Eliminated unexpected system behavior.
Data composition system.	When a data composition template is generated, expressions for calculating details that contain fields unavailable due to functional options are removed from predefined templates. This change is not implemented in 8.3.4 compatibility mode.	When a data composition template was generated, details expressions were copied from the predefined templates without any modifications.	During report generation, errors do not occur when templates include fields unavailable due to functional options.
Client application.	In managed mode, if any connection issues or server-side issues occur, the client application allows to repeat a request, interrupt the operation, or shut down the application.	If any connection issues or server-side issues occurred, users were not allowed to repeat their requests. In most cases the client application was simply shut down.	The client application is more robust against connection issues or 1C:Enterprise server issues.
Mobile application.	If the interface compatibility mode is set to Taxi and then the Use purposes configuration property is set to Personal computer and Mobile device, the Interface compatibility mode property is automatically set to Taxi. Version 8.2 allowed. If changing the Use purposes property requires modification of Modality usage mode and Interface compatibility mode configuration property values, the user is prompted to confirm the change.	Selecting the Mobile device value in the Use purposes configuration property made the following changes in configuration properties without any warnings: The Interface compatibility mode property was set to Version 8.2. The Modality usage mode property was set to Use.	Designer behaves as expected.
Software licensing.	Users that do not have administrative rights can activate software licenses. In this scenario the license is activated for the current user.	Only users with administrative rights could activate licenses.	A user without administrative rights that does not have write access to the directory where license files for all computer users are located still can activate a software license.
Predefined data. Data exchange. Common attributes / Data separation.	When predefined data is changed, changes are only registered for items that are actually modified, added, or deleted. When the compatibility mode is changed from Version 8.3.2 (or earlier) to Version 8.3.3 (or later), all predefined item changes are registered. When the compatibility mode is changed from Version 8.3.3 (or later) to Version 8.3.2 (or earlier), registration of all predefined items is removed. When changes are registered for predefined items: If the configuration object where predefined items are changed and the exchange plan where the changes are registered do not have common separators, the changes are registered for all nodes of the exchange plan. If the configuration object where the predefined items are changed and the exchange plan where the changes are registered have common separators, the changes are only registered for those exchange plan nodes where separator values match the separator values of predefined items.	When predefined data belonging to a specific object was changed, all predefined items of this object were registered as if they were changed. Predefined item changes were registered for all exchange plan nodes available from the session where the predefined items were changed.	When object predefined data is changed, object change registration tables do not significantly increase in size.
Managed forms. Web client.	In the web client, if a managed form table cell contains multiple text lines, only lines that fit the cell height are shown. If the text does not fully fit, ellipsis (…) is added to the end of the last line. In Microsoft Internet Explorer 8 web browser, the ellipsis is not displayed. In the thin client, text in managed form table cells better fits the cell height.	In the web client, if a managed form table cell contained multiple text lines, the lines might be cut in the manner that made them unreadable (only the upper character halves were displayed and the lower ones were cut). The ellipsis was not added to the end of the last line. In the thin client, sometimes text in managed form table cells did not fit the cell height well, a redundant empty line was added to the bottom of the cell.	Eliminated unexpected system behavior.
Data composition system.	While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items are removed: Items that include references to fields disabled by functional options Items that include references to fields unavailable due to access rights restrictions Items linked to data composition schema fields that no longer exist This change is not implemented in 8.3.4 compatibility mode.	While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items were removed: Items that included to fields disabled by functional options Items that included references to fields unavailable due to access rights restrictions	Improved system stability.
Database operations.	You can load the infobase dump file (*.dt) that was generated with the following conditions: The dump was created in the file mode . 1C:Enterprise version 8.3.4 was used for dumping. Filled aggregates of turnover accumulation registers were available in the infobase. In some scenarios, the aggregates of turnover accumulation registers are cleared after the loading.	Loading the infobase dump file (*.dt) was not available if the file was generated with the following conditions: The dump was created in the file mode . 1C:Enterprise version 8.3.4 was used for dumping. Filled aggregates of turnover accumulation registers were available in the infobase.	Eliminated unexpected system behavior.
Data display.	Text fragments found during a search by substring are displayed in a uniform way (bold font and green text) in the following cases: In managed form text box drop-down lists In favorites In history In dynamic lists In the full-text search form	The substrings that were found had different looks.	Uniformed look for different features.
XML and XDTO support.	For charts of accounts and charts of calculation types, the Predefined field of predefined tabular sections is available for writing. In charts of accounts and charts of calculation types, the predefined records of predefined tabular sections can include only predefined items. During a serialization of a chart of accounts item or a chart of calculation types item to XML(XDTO), the Predefined item, which matches the Predefined property, is written. During the deserialization, the Predefined item value is written to the Predefined property only if the compatibility mode is disabled. This change is not implemented in 8.3.4 compatibility mode.	For charts of accounts and charts of calculation types, the Predefined field of predefined tabular sections was read-only. During the serialization of a chart of account item or a chart of calculation types item to XML(XDTO), the Predefined item was not generated.	During data exchange between configurations, the flags of predefined data are no longer lost in the chart of accounts and chart of calculation types items.
Managed forms.	Getting a choice form in a slow connection scenario is implemented identically to getting forms in other scenarios.	Getting a choice form in a slow connection scenario was implemented differently from getting forms in other scenarios, it included caching the form.	Increased relaibility for getting choice forms in a slow connection scenario.
Applied objects.	During the restructuring of hierarchical predefined data, if an item parent is not found during the update, the item is moved to the top level. During the creation or restructuring of predefined data, if references to subordinate items are missing from predefined tabular sections, rows with missing references are deleted. Upon deletion, the platform generates a diagnostics message or an event log record, and the tabular section row numbering is updated accordingly. This change is not implemented in 8.3.4 compatibility mode.	Invalid references to parent items or subordinate items in predefined data might cause errors during infobase retructuring.	Increased system stability in the scenario where predefined data items contain invalid references to parent or subordinate items.
Command interface.	In the Taxi interface the scaling of pictures in the sections panel of the web client is now identical to that of the thin client. The picture height is calculated as follows: If any of the pictures have height more than 48 pixels, they are scaled to the height of 48 pixels. If all of the pictures have height less that 48 pixels, the section panel height is calculated based on the maximum picture height, while smaller pictures are centered at their respective positions.	In the Taxi interface of the web client 48x48 pixel squares were reserved for section panel pictures. The size of larger pictures was reduced proportionally and smaller pictures were centered within those squares. The section panel height was never reduced.	The Taxi interface behavior in the web client is unified with that of the thin client.
Spreadsheet documents. XML and XDTO support.	When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file is not important.	When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file was important.	Spreadsheet documents serialized to XDTO using 1C:Enterprise version 8.3.4 and earlier can be read without errors.
Third-party software.	The OpenSSL library is updated to version 1.0.0r.	OpenSSL version 1.0.0m was used.	Eliminated OpenSSL security issues.
Web client.	The web client is optimized for Google Chrome 37 web browser. The managed form issues where text did not fit the desired area are eliminated.	The web client had issues related to displaying text in Google Chrome 37 web browser.	Improved Google Chrome 37 web browser support.
DBMS operations.	Improved reliability of PostgreSQL DBMS operations in certain scenarios.	Insufficient reliability of PostgreSQL DBMS operations in certain scenarios.	Improved reliability of PostgreSQL DBMS operations.
Regional settings.	For Russia, a single one-hour time zone shift is applied in line with Federal Law #248-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.	The platform did not reflect the changes introduced by Federal Law #248-FZ.	The time offset changes introduced by the new law are implemented.
Add-ins.	A section describing add-in limitations is added to the Add-in development technology document (read more).	The Add-in development technology document did not describe add-in limitations.	Improved add-in technology description.
Client application. Development tools.	When the thick client (1cv8) is started in ordinary application mode, the performance indicator window is not displayed.	When the thick client (1cv8) was started in ordinary application mode, the performance indicator window was not displayed.	The display of performance indicators in ordinary applications is disabled because they are rarely used in this mode.

Table of contents

Changes that require modification of configuration and administrative settings

Functionality	After	Before	Result of changes
Dynamic lists.	Dynamic lists cannot be ordered by extra dimension fields of accounting registers. An attempt to order a dynamic list by these fields (for example, by clicking the column header) does not result in a server call. This change is not implemented in 8.3.4 compatibility mode.	An attempt to order a dynamic list by extra dimension fields of accounting registers generated an error message and initiated a server call, which did not retrieve any data.	Dynamic lists do not allow ordering that does not make sense, therefore the system behaves as expected (from the user’s point of view).
Applied objects.	An attempt to set a value to ThisObject or AdditionalProperties attribute of a CatalogObject, ExchangePlanObject, or ChartOfCharacteristicTypesObject raises an exception. An attempt to set a value to the DataExchange attribute of a CatalogObject or ChartOfCharacteristicTypesObject raises an exception. This change is not implemented in 8.3.4 compatibility mode.	An attempt to set a value to ThisObject or AdditionalProperties attribute of a CatalogObject, ExchangePlanObject, or ChartOfCharacteristicTypesObject did not raise an exception, and the value was not set. An attempt to set a value to the DataExchange attribute of a CatalogObject or ChartOfCharacteristicTypesObject did not raise an exception, and the value was not set.	Unified processing of the specified properties: an attempt to set a value for a read-only attribute raises an exception.
Client application. Server clusters.	If the client and server application versions do not match, the search for client application distribution kit is performed in the following order: Search in the 1C:Enterprise installation directory (the InstalledLocation property in 1cestart.cfg and 1cescmn.cfg files) Search in the directories specified as locations for distribution files of new versions (the DistributiveLocation property in 1cestart.cfg and 1cescmn.cfg files, and the CommonCfgLocation property in the 1cestart.cfg file) Search by the URL that is returned in the server exception about the mismatch of client and server application versions (the PublishDistributiveLocation parameter in the conf.cfg file and the pubdst attribute of the ws tag in the default.vrd file) Search using Internet services for getting the client application distribution kit	If the client and server application versions did not match, the search for client application distribution kit was performed in the following order: Search in the 1C:Enterprise installation directory (the InstalledLocation property in 1cestart.cfg and 1cescmn.cfg files) Search in the directories specified as locations for distribution files of new versions (the DistributiveLocation property in 1cestart.cfg and 1cescmn.cfg files, and the CommonCfgLocation property in the 1cestart.cfg file) Search by the URL, that is returned in the server exception about the mismatch of client and server application versions (the PublishDistributiveLocation parameter in the conf.cfg file and the pubdst attribute of the ws tag in the default.vrd file) Search using Internet services for getting the client application distribution kit	Search for updates behaves as expected: search in the local network precedes search using Internet services.
Common attributes / Data separation.	The SetPredefinedDataUpdate() and SetInfoBasePredefinedDataUpdate() methods can only be executed in sessions that do not have any separators (in addition to the fact that they require the Administration right). This change is not implemented in 8.3.4 compatibility mode.	The SetPredefinedDataUpdate() and SetInfoBasePredefinedDataUpdate() methods could be executed in any session, provided that the user had the Administration right.	Users cannot change the infobase predefined data update mode if they do not have the required rights.
Navigation links. Client application.	The ReferencesArray parameter of the GetURLsPresentations() function is mandatory. The return value of this function is always an array. For input array items whose presentations cannot be obtained, the matching output array items contain UNDEFINED. This change is not implemented in 8.3.4 compatibility mode.	The ReferencesArray parameter of the GetURLsPresentations() function was not mandatory. In cases when a parameter value presentation could not be obtained by its value, uniform system behavior across all client applications was not guaranteed.	The GetURLsPresentations() function is uniform across all client applications.
Web client.	In the web client, performing the Execute() operator ends in exception.	In the web client, calling the Execute() operator was ignored and no diagnostic messages were displayed.	Implemented applied solution error diagnostics (for calling the Execute() operator in the web client).
Spreadsheet documents.	In the SpreadsheetDocumentRange object, the TopBorder, RightBorder, BottomBorder, and LeftBorder properties contain the UNDEFINED value if the corresponding border is not the same for all cells. This change is not implemented in 8.3.4 compatibility mode.	In the SpreadsheetDocumentRange object, values of the TopBorder, RightBorder, BottomBorder, and LeftBorder properties were retrieved from the properties of a random cell within the specified range	Eliminated unexpected system behavior.
Data composition system.	In data composition system batch queries, when a temporary table is created, if the table fields are not used by the next queries of the batch and the table is not included in required joins, the query that creates the table is removed from the batch. This change is not implemented in 8.3.4 compatibility mode	In data composition system batch queries, temporary tables were deleted from the batch if the table fields were not used by the next queries of the batch and the table was not used in other queries of the batch that also created temporary tables.	Improved management of temporary tables in the data composition system.
Data exchange. Information registers.	Changes in information registers that have dimensions of UUID type that are included in the main filter are recorded correctly. In tables that store the register change records, fields describing dimensions of UUID type have UUID type.	Changes in information registers that had dimensions of UUID type were recorded incorrectly. In tables that stored the register change records, fields describing dimensions of UUID type had BinaryData type.	Eliminated unexpected system behavior. In exchange plans containing information registers with dimensions of UUID type that are included in the main filter, registering all dimensions is required.
1C:Enterprise script. Common objects.	In the thin client, the following types are not available: ValueTableRow, ValueTableColumnCollection, ValueTableColumn, CollectionIndexes, CollectionIndex, ValueTreeRowCollection, ValueTreeRow, ValueTreeColumnCollection, and ValueTreeColumn. This change is not implemented in 8.3.4 compatibility mode.	In the thin client, the following types were available: ValueTableRow, ValueTableColumnCollection, ValueTableColumn, CollectionIndexes, CollectionIndex, ValueTreeRowCollection, ValueTreeRow, ValueTreeColumnCollection, and ValueTreeColumn.	Eliminated unexpected system behavior.
Managed forms.	In managed form text boxes, the TextEditEnd event handler is not called when the spin buttons are clicked. This change is not implemented in 8.3.4 compatibility mode.	In managed form text boxes, the TextEditEnd event handler was called when spin buttons were clicked.	Eliminated unexpected system behavior.
Applied objects. Managed forms.	When an object is created from a dynamic list filtered by an attribute of Date type, object attributes of that type are filled from the filling data. This change is not implemented in 8.3.4 compatibility mode.	When an object was created from a dynamic list filtered by an attribute of Date type, object attributes of that type were not filled from the filling data. For such attributes, the standard FillingValues parameter of the new item form contained values of the StandardBeginningDate type passed from the dynamic list filters.	Eliminated unexpected system behavior.
Managed forms.	In managed form text boxes, if editing a string with an input mask results in a string that matches an empty input mask, an empty string is recorded to the form attribute displayed in the text box. If the string has fixed length, the string consists of spaces. This change is not implemented in 8.3.4 compatibility mode.	In managed form text boxes, if editing a string with an input mask resulted in a string that matched an empty input mask, a string that contained spaces and fixed input mask characters was recorded to the form attribute displayed in the text box.	When a text box is cleared, an empty string is recorded to the linked attribute regardless of the input mask availability. In text boxes linked to attributes of Text type with the input mask set, the automatic "incomplete" mark is displayed correctly.
Managed forms.	In managed form text boxes, the procedure of generating a drop-down list during input by string is modified. The procedure is described in the documentation. This change is not implemented in 8.3.4 compatibility mode.	In managed form text boxes, the following procedure was used for generating a choice list during input by string: Search by beginning of the string is performed and the first 10 results are added to the list. If the list contains less than 10 items, search by substring is performed and its results are added to the list until it contains 10 items. If the list still contains less than 10 items, results of search by other fields available for search during input by string are added to the list.	In managed form text boxes, eliminated issues in the procedure of drop-down list generation when search is performed both by beginning of string and by substring.
Managed forms.	Getting the list of desktop forms is implemented. For the Forms in tabs and Taxi interface modes, the ClientApplicationWindows collection contains a separate item that describes the start page (desktop). The Content property of this item contains the list of forms available on the start page (desktop). For the Forms in separate windows interface mode, the ClientApplicationWindows collection contains ClientApplicationWindow objects that describe forms located on the desktop. For the ClientApplicationWindow object, the StartPage and Content properties are implemented. The GetContent() method of the ClientApplicationWindow is supported for compatibility purposes. This change is not implemented in 8.3.4 compatibility mode.	This feature was not provided. For the Forms in tabs and Taxi interface modes, the ClientApplicationWindows collection did not contain objects describing the start page (desktop). For the Forms in separate windows interface mode, the ClientApplicationWindows collection did not contain objects describing forms opened on the desktop.	Developers can access forms located on the start page (desktop) using 1C:Enterprise script.
Automated testing.	For subordinate objects of the TestedApplication object, the TestedClientApplicationWindow object is implemented. The object describes the start page (desktop). Forms (objects of TestedForm type) included in the start page (desktop) content are subordinate to the TestedClientApplicationWindow object that describes the start page (desktop). For the TestedClientApplicationWindow object, the StartPage property is implemented. This change is not implemented in 8.3.4 compatibility mode.	The TestedClientApplicationWindow object that described the start page (desktop) was not included in the subordinate objects of the TestedApplication object. Forms included in the start page (desktop) were subordinate to the TestedClientApplicationWindow object that had its IsMain property set to True.	You can access forms located on the start page (desktop) from 1C:Enterprise script using automated testing tools.
Common attributes / Data separation. Data exchange.	An exception that does not cause application termination occurs when predefined data is registered for an unseparated configuration object in a separated exchange plan from a session that uses all separators.	An exception that caused application termination occurred when predefined data was registered for an unseparated configuration object in a separated exchange plan from a session that used all separators.	Eliminated issues that resulted in application termination.
Common attributes / Data separation. Data exchange.	If a configuration object does not use all separators where it is included, calling the InitializePredefinedData() method does not initialize predefined data items for this object. This change is not implemented in 8.3.4 compatibility mode.	If a configuration object did not use all separators where it was included, calling the InitializePredefinedData() method caused an error.	The InitializePredefinedData() method can be used in any session, not only when all separators are used.
DBMS operations. Data composition system. Dynamic lists.	For the LIKE query language operation, search in dynamic lists, and filter in the data composition system, the search template length is limited. The limit depends on the DBMS type. If the template length exceeds the limit, an error is generated, which does not lead to 1C:Enterprise shutdown.	For the LIKE query language operation, search in dynamic lists, and filter in the data composition system, if the search template exceeded 1024 characters, this could cause a DBMS error and 1C:Enterprise shutdown.	1C:Enterprise is not shut down when a search template is too long.
Applied objects.	The value of the IsFolder field is correctly passed to the PresentationGetProcessing handler. This change is not implemented in 8.3.4 compatibility mode.	The value of the IsFolder field passed to the PresentationGetProcessing handler was inverted.	Eliminated unexpected system behavior.
Managed forms.	The managed form visibility setting is stored in the system setting storage with a purpose use key. The object key is generated as follows: <Full form name>/<Purpose use key>/FormSettings. This change is not implemented in 8.3.4 compatibility mode.	The managed form visibility setting was stored in the system setting storage without a purpose use key. The object key was generated as follows: <Full form name>/FormSettings.	You can use a single form for different use purposes, with custom display settings for each use purpose.
Data composition system.	Data composition system expressions are calculated in the safe mode. This change is not implemented in 8.3.4 compatibility mode.	The safe mode was not used when data composition system expressions were calculated.	Improved security of executing reports that might use insecure methods from common modules.
Managed forms.	In managed form tables, you can start dragging from an available table cell only. This change is not implemented in 8.3.4 compatibility mode.	In managed form tables, dragging from any table cell was allowed. When an attempt to drag an unavailable cell was made, the currently selected cell was dragged instead.	Eliminated unexpected system behavior.
Data composition system.	The Text parameter of conditional appearance that is specified for the Fields header usage area is applied to grouping field headers. This change is not implemented in 8.3.4 compatibility mode.	The Text parameter of conditional apperance was never applied to grouping field headers.	Eliminated unexpected system behavior.
Data composition system.	The data composition template generator always generates the VerticalLevel property for nested reports. The parent report level is added to the value of this property. This change is not implemented in 8.3.4 compatibility mode.	Parent report groupings were not taken into account when nested reports were displayed.	Parent report groupings affect nested reports: nested reports are displayed at the same grouping level as the parent report.
Managed forms.	For managed form fields, the PeriodField field type is implemented. It is intended for simplifying selection of periods of several full months. For managed form field extensions for calendar fields, the Border property is implemented. It specifies border parameters for the calendar field. The dialog box that was used in the following scenarios is modified: Period selection for dynamic lists Standard period selection for text boxes that display values of StandardPeriod type The StandardPeriodEditDialog object dialog box This change is not implemented in 8.3.4 compatibility mode.	For managed form fields, the PeriodField field type was not available. For managed form field extensions for calendar fields, the Border property was not available. A different dialog box was used in the following scenarios: Period selection for dynamic lists Standard period selection for text boxes that display values of StandardPeriod type The StandardPeriodEditDialog object dialog box If the period variant was not custom, a drop-down list containing available options was opened in the input field.	The period selection dialog box is improved.
Managed forms.	In managed form tables, if a row is added because editing the previous row is finished or by pressing the Down Arrow, and then the row is neither edited from 1C:Enterprise script nor edited interactively, the new row is automatically deleted once the selection is moved away from it. This change is not implemented in 8.3.4 compatibility mode.	In managed form tables, if a row was added because editing the previous row was finished or by pressing the Down Arrow, and then the row was not edited interactively, the new row was automatically deleted once the selection was moved away from it.	Eliminated unexpected system behavior.
Managed forms.	While a text box choice history is being filled, the check for deleted items is performed. A value presentation is removed from the list if its data was deleted in the current session or its data was deleted in another session but the presentation of deleted data was obtained in this session. If a value is deleted after the choice history is generated, when a user attempts to select this value, a warning is displayed, the value is not selected, and the item is removed from the history list. The feature is implemented for thin and web clients.	Deleted values were displayed in text box choice history as Object not found items.	References to objects that are no longer available for selection are removed from the choice history.
Managed forms.	In managed forms, the length of the PurposeUseKey property value is limited to 128 characters. An attempt to set a value longer than 128 characters or open a form with this property value longer than 128 characters ends with a exception. This change is not implemented in 8.3.4 compatibility mode.	In managed forms, the length of the PurposeUseKey property value was not limited.	Simplified diagnostics of issues related to PurposeUseKey value being too long.
Data access restrictions.	For each configuration object that is included in separator content and has tabular sections, a data access restriction check is performed (after writing) if the access restriction conditions include attributes from the object tabular section. As a result, a message about insufficient access rights might be displayed in situations where it was not displayed earlier.	For configuration objects that were included in separator content and had tabular sections, data access restriction checks were not performed (after writing) if the access restriction conditions included attributes from the object tabular sections.	Eliminated unexpected system behavior.
Predefined data. Charts of accounts. Charts of calculation types.	The following rules now apply during infobase restructuring: A row of a predefined tabular section of a chart of accounts or a chart of calculation types, which is added in 1C:Enterprise mode and refers to a predefined item, is marked predefined if a predefined row that refers to the same item is added in Designer mode. When a predefined row is deleted from a predefined tabular section of a chart of accounts or a chart of calculation types, the actual row is not deleted. Instead, it loses the "predefined" flag. In addition to that, the order of tabular section rows might be changed to ensure that all of the predefined items are at the top. This change is not implemented in 8.3.4 compatibility mode.	In a chart of accounts, adding a predefined extra dimension type in Designer mode was impossible if the extra dimension type was added in 1C:Enterprise mode earlier. When an attempt to delete a predefined row from a predefined tabular section of a chart of accounts was made, the actual row was deleted. Charts of calculation types had the following behavior: In 1C:Enterprise version 8.2.12 or earlier, the behavior was the same as in 1C:Enterprise version 8.3.5. In 1C:Enterprise versions 8.2.13–8.3.4, if a base, leading, or displacing calculation type that was added earlier in 1C:Enterprise mode was then added in Designer mode, a duplicate calculation type entry was generated. When a predefined row was deleted from a predefined tabular section of a chart of calculation types, the actual row was deleted.	Editing predefined tabular sections no longer might cause data losses. Editing the list of extra dimension types of a predefined account in Designer might result in a message that the account's maximum number of extra dimension types is exceeded.
Accounting registers. Accumulation registers. Information registers. Calculation registers.	In a value table obtained by the Unload() method of an accounting register, accumulation register, calculationregister, or information register record set, the value of the LineNumber column is equal to the line number in the record set. This change is not implemented in 8.3.4 compatibility mode.	In the value table obtained by the Unload() method of an accounting register, accumulation register, calculation register, or information register record set, the value of the LineNumber column was equal to the index of the record set index.	Eliminated unexpected system behavior.
Client application. Internet-enabled functionality.	The TLS protocol is recommended for secure connections as it is more secure. The SSL protocol version 3.0 is disabled by default. If the web server used for thin client connections can use SSL version 3.0 for connecting to a web server, you can use the thin client command-line option /HttpsAllowSSLv3. SSL version 3.0 is not used (by default) with the HTTPConnection, FTPConnection, InternetMail, WSProxy, WSReference, and WSDefinition objects, when connecting to the configuration repository, and in Debugger. If you need to use SSL version 3.0 in these scenarios, use the AllowSSLv3 option in the conf.cfg file. For the conf.cfg configuration file, the AllowSSLv3 option is implemented. For the InternetMail object in version 8.3.5 and earlier compatibility mode and in earlier 1C:Enterprise versions: On Windows, you can enable the SSL protocol version 3.0 by editing the system register. On Linux, the availability of SSL protocol version 3.0 is defined by the OpenSSL library version.	The SSL protocol version 3.0 was used for secure connections.	Improved security of connections established by client applications that work over the Internet.
Web client. Add-ins.	The file system extension and the cryptography extension are modified (for all supported Windows web browsers). The reason is that the NPAPI technology is no longer supported in Google Chrome browser. New extension versions perform all file and cryptography operations asynchronously (using notifications). To be able to use 1C:Enterprise extensions and browser extensions, you are required to install a dedicated web browser extension. The web client prompts you to install that extension once you attempt to enable a browser extension. On the client side, add-ins, the file system extension, and the cryptography extension run asynchronously. Synchronous add-in, file system extension, and cryptography extension operations are supported on the client side for compatibility purposes. Refactoring applied solutions, including those that have add-ins, is required to support synchronous operations: change method calls to calls of BeginCalling<MethodName>() asynchronous methods, change reading property values to calls of BeginGetting<PropertyName>() asynchronous method, change setting property values to calls of BeginSetting<PropertyName>() asynchronous method. Refactoring add-ins is not required. The platform automatically adds prefixes and asynchronous behavior support to add-in methods. The SynchronousExtensionAndAddInCallUseMode configuration property is implemented. If the property is set to Do not use, NPAPI-based extensions are not loaded in the web client and, as a result, synchronous methods cannot be executed. In other cases, an attempt to load an NPAPI-based extension is performed. If an extension is successfully loaded, both synchronous and asynchronous methods can be executed. For more information, see the documentation. Previous extension versions can be uninstalled in a regular way. Improved add-in development technology (read more). The following global context methods are implemented: BeginAttachingCryptoExtension(), BeginAttachingFileSystemExtension(), BeginAttachingAddIn(), BeginCopyingFile(), BeginMovingFile(), BeginDeletingFiles(), BeginFindingFiles(), BeginCreatingDirectory(), BeginGettingTempFilesDir(), BeginGettingDocumentsDir(), BeginGettingUserDataWorkDir(), BeginGettingFiles(), BeginPuttingFiles(), BeginRequestingUserPermission(), and BeginRunningApplication(). For the CryptoManager object, a constructor without parameters is implemented, and also the following methods: BeginInitialization(), BeginEncrypting(), BeginSigning(), BeginGettingCryptoModuleInformation(), BeginGettingCertificatesFromSignature(), BeginGettingCertificateStore(), BeginVerifyingSignature(), BeginCheckingCertificate(), and BeginDecrypting(). For the CryptoCertificate object, a constructor without parameters is implemented, and also the following methods: BeginInitialization() and BeginUnload. For the CryptoTools object, the BeginGettingCryptoModuleInformation() method is implemented. For the CryptoCertificateStore object, the BeginAdding(), BeginFindingByThumbprint(), BeginFindingBySerialNumber(), BeginFindingBySubject(), BeginGettingAll(), and BeginDeleting() methods are implemented. For the FileDialog object, the Show() method is implemented. For the File object, a constructor without parameters is implemented, and also the following methods: BeginInitialization(), BeginGettingModificationTime(), BeginGettingHidden(), BeginGettingReadOnly(), BeginGettingSize(), BeginGettingModificationUniversalTime(), BeginCheckingExist(), BeginSettingModificationTime(), BeginSettingHidden(), BeginSettingReadOnly(), BeginSettingModificationUniversalTime(), BeginCheckingIsDirectory(), and BeginCheckingIsFile(). You can use the refactoring feature to convert synchronous extension and add-in methods to their asynchronous counterparts. New refactoring settings are available.	The file system extension and the cryptography extension were implemented using the NPAPI technology. The extension methods were executed synchronously. In Google Chrome web browser synchronous execution of methods from add-in APIs was possible.	The platform supports asynchronous add-in, cryptography extension, and file system extension operations in the web client, which ensures Google Chrome support. Important! Support of synchronous operations in Google Chrome is disabled by default since version 42 (April 2015) and discontinued since version 45 (September 2015). Therefore, synchronous 1C:Enterprise script methods will stop working in Google Chrome even if you use a platform version that supports them.
Web client. Add-ins.	The add-in technology (read more) no longer supports add-in development for Safari web browser for Windows.	The add-in technology supported add-in development for Safari web browser for Windows.	The outdated web browser is no longer supported. The Apple company stopped updating Safari web browser for Windows.
Add-ins.	The add-in development technology supports Mozilla Firefox web browser versions 31.0 and later. It is recommended that you build a new installer package for Mozilla Firefox using the new adapter. It is also recommended that you remove installer packages for Mozilla Firefox versions 30.0 and earlier from the add-in archive. The add-in development technology does not support Mozilla Firefox web browser versions 30.0 or earlier. Adapters for Mozilla Firefox versions 30.0 or earlier are removed.	The add-in development technology did not support Mozilla Firefox web browser versions 31.0 or later. The add-in development technology supported Mozilla Firefox web browser versions 30.0 and earlier.	The add-in development technology supports the latest versions of Mozilla Firefox web browser (31.0 or later). The add-in development technology does not support older versions of Mozilla Firefox web browser (30.0 or later).

Table of contents

Renamed objects

Object	The old name	The new name
The names of AddressData object properties are changed. For compatibility purposes, the previous names are supported.	Street House	PrimaryAddressString AdditionalAddressString
In the event log, presentations of the following events are modified: _$Data$_.TotalsMinPeriodUpdate and _$Data$_.TotalsPeriodUpdate.	_$Data$_.TotalsMinPeriodUpdate Data. Modify totals period	Data. Modify minimum calculated totals period Data. Modify maximum calculated totals period

Table of contents

Mobile platform

Functionality	After	Before	Result of changes
Dynamic lists. Queries.	Custom queries, including queries that generate dynamic lists, are now available in the mobile platform.	This feature was not provided in the mobile platform.	In mobile applications, you can use dynamic lists generated based on custom queries, and use queries to the infobase for implementing various features, such as checking balance while posting documents
Managed forms.	Faster form opening and faster execution of context server calls.	Insufficient performance of form opening and execution of context server calls.	Improved user experience by improving the performance of form operations.
Applied objects.	Predefined items are created at the first call of the corresponding table. Calling the SetPredefinedDataUpdate() method before the first call modifies the flag that shows whether predefined data is created.	Predefined items were only created when mobile application configuration was updated. After calling the SetPredefinedDataUpdate() method, predefined data was only modified during the next mobile application configuration update.	Mobile platform behavior is uniform with that of PC platform version 8.3.3.
Background and scheduled jobs.	Background jobs are now available in the mobile platform.	This feature was not provided in the mobile platform.	Background jobs are available in mobile applications.
Access rights. Functional options.	In the mobile platform, the following features are available: Functional options and functional option parameters. Roles (limited support). Role management of item visibility and availability for forms and for the command interface. A role setting for form visibility on the start page. After functional options and roles are applied, the first form from the list of available forms is displayed. Infobase users (limited support). Limitations of the implemented features are described in the documentation.	These features were not provided in the mobile platform.	Extended features for applied solution interface management.
Database operations.	The EraseInfoBaseData() global context method is implemented.	This feature was not provided on the mobile platform.	On the mobile platform, you can delete all infobase data.
Development tools.	In Designer, support of Android Debug Bridge (adb) is added. Now you can start a mobile application from Designer on a mobile device emulator or on a physical device connected to a computer.	This feature was not provided.	Easier development and debugging of mobile applications for Android OS.
Internet-enabled functionality. Telephony.	New features: Send and receive emails using the built-in mail client of a mobile device. The MailTools object is implemented. Send and receive SMS and MMS messages. The SMSMessage object is implemented. Dial phone numbers. The TelephonyTools object is implemented. Access the call history filterred by call type(incoming, outgoing, or missed).The CallLog object is implemented. The limitations of the telephony tools on supported operating systems are listed in documentation.	Sending SMS messages and making calls was available with some limitations using parameters of the RunApp() and GotoURL() methods. Access to the call history and sent email messages from the built-in email client was not available.	Easy access to mobile device functionality: SMS and MMS, call history, and making calls.
System requirements.	The configuration property RequiredMobileApplicationPermissions, specifies permissions that mobile application will require on Android: Multimedia Geolocation Reading and writing contacts Reading and writing calendar events Access to telephony The Mobile application builder uses the specified permissions.	This feature was not provided.	You can specify permissions required for your mobile applications more clearly.
Multimedia tools.	Scanning barcodes using the mobile device camera is supported. For the MultimediaTools object, the following methods are implemented: BarcodeScannerScanning(), ShowBarcodeScanning(), and CloseBarcodeScanning().	This feature was not provided.	New mobile platform feature.
Development tools.	In Designer, you can edit pictures with variants. You can convert images to images with variants and back.	You could only load pictures with variants without editing them.	Creating images for mobile applications became easier.
Access to mobile device features.	Access to mobile device contact lists, both local and linked to specific accounts, is implemented. The following objects are implemented: ContactManager, ContactData, AccountContactData, LocalContactKey, ContactAccount, ContactDataItem, and ContactDataItemInstantMessaging.	This feature was not provided.	You can access mobile device contacts.
Access to mobile device features.	Access to mobile device calendars linked to specific accounts is implemented. The following objects are implemented: CalendarManager, CalendarAccount, LocalCalendarKey, LocalCalendarEventKey, CalendarEventData, AccountCalendarEventData, CalendarData, and AccountCalendarData.	This feature was not provided.	You can access mobile device calendars.
Location tools.	For the AddressData object, the AddressString property is implemented. It stores an address fragment starting from the street.	This feature was not provided.	The AddressData object functionality is extended. It can be used not only for geolocation purposes, but also for storing various types of contact information.
Development tools.	The mobile platform distribution kit mobile.zip now includes the version.txt file. The file contains the version number of the mobile platform delivered in the archive.	This feature was not provided.	Simplified identification of the mobile platform version, including scenarios that use Mobile application builder.
Mobile application builder.	The mobile application builder, which is included in the mobile platform, is improved: The temporary user directory is no longer used for building. An explicitly defined directory is used instead, the path to this directory must contain ASCII characters only. The build date of each mobile application is recorded (and displayed). You can save graphic assets and mobile configurations to the hard disk. When the mobile platform version 8.3.5 is loaded, the version number is obtained automatically from the version.txt file, which is included in the mobile platform distribution kit (mobile.zip). Android SDK version 17 or later is required for building mobile applications for Android. For files that contain graphic assets, the check whether the file contains a full set is implemented (the check is also performed when the file is loaded). Files that contain graphic assets support icons for devices with high density screens (size 144 x 144 pixels, file name Android\icon-144x144.png). Other improvements are implemented.	The mobile application builder had the following features: The temporary user directory was used for building mobile applications. The mobile application could not be built for Android if the name of the user on whose behalf the build was performed contained non-ASCII characters. Mobile application build dates were not recorded. Saving graphic assets and mobile configurations to the hard disk was not available. Android SDK version 17 was required for building mobile applications for Android, other versions were not supported. The mobile platform did not support icons for Android devices with high density screens.	The usability of the mobile application builder is improved.
Client application.	The text displayed on the mobile platform splash screen is translated to all localization languages.	The text displayed on the mobile platform splash screen was always displayed in Russian.	Eliminated unexpected system behavior.
Common objects.	The option to run external applications on mobile devices and get the results of their execution is implemented. This feature is only available on operating systems of Android family. The MobileDeviceApplicationLaunch and MobileDeviceApplicationLaunchExtrasData objects are implemented.	This feature was not provided.	Simplified applied solution integration with mobile applications, including the option to get mobile application execution result. This feature is only available on operating systems of Android family.
Development tools.	During the building of an Xcode project, the "executable" attribute is set for the 1cem file included in the project.	During the building of an Xcode project, the attributes of the 1cem file included in the project were not changed.	Eliminated the problem that occurred when a project file was rebuilt on an operating system of Windows family: the "executable" attribute of the 1cem file was cleared.
Data display. Mobile application builder.	In the mobile platform, graphical assets for iPhone 6 and iPhone 6 Plus devices are implemented: splash screens: 750x1334, 2208x1242, and 1242x2208 icons: 87x87 and 180x180 In the mobile application builder, support of graphical assets for iPhone 6 and iPhone 6 Plus devices is implemented.	The mobile platform and mobile application builder did not support graphical assets required for iPhone 6 and iPhone 6 Plus devices.	New Apple mobile devices are supported.

Table of contents

Transition from the previous version to the version 8.3.5

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.5.
Some features that are added in version 8.3.5 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.
1C:Enterprise version 8.3.5 cannot share a configuration repository with any of the earlier 1C:Enterprise versions. In this scenario users of the earlier versions receive a diagnostic error message.

Table of contents

Version 8.3.4

Version 8.3.4 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.4

New functionality and changes

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.3.3 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, and 8.3.2.	In version 8.3.4 you can run configurations created in version 8.3.3 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.4 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.3 for working with the infobase even after the transition to version 8.3.4. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Common objects.	In the RepresentableDocumentBatchItems object, the optional parameter DocumentAddress is implemented for the Add() and Insert() methods. This parameter stores the address of the temporary storage for the document being saved.	This feature was not provided.	Improved usability of generating document batches for saving and printing.
Spreadsheet documents.	You can save spreadsheet documents in HTML 5 format. Сharts and grafic primitives are saved in SVG format; free text rotation is supported.	This feature was not provided.	You can save spreadsheet documents in HTML 5 format.
Background and scheduled jobs.	When specifying a value for the Parameters property of the BackgroundJobs object or for the Parameters property of the Execute() method of the ScheduledJob object, you can omit any number of last parameters, provided that their default values are defined in the method that implements the background or scheduled job.	During the start of a background or scheduled job, if any number of last parameters with default values specified were not specified explicitly, an exception was raised.	You can modify methods implementing background or scheduled jobs by adding new parameters to the end of the parameter list, provided that their default values are defined. In this case modification of previously created code fragments that describe creation of background or scheduled jobs is not required.
Development tools.	In Designer, the following module editor features are available: Selecting all entries of the identifier marked by cursor location Selecting all entries of an identifier marked by a double-click Selecting pairs of opening and closing 1C:Enterprise script clauses (including brackets): Procedure ... EndProcedure, If ... EndIf, and so on Selecting identifiers is disabled by default. To use this feature, enable it in Designer options dialog box. Selecting the search expression is available in Designer, thick client, and thin client.	This features were not provided.	The 1C:Enterprise script editor is improved.
External data sources.	External data sources support all features of the MySQL query language. In the ExternalDataSourceConnectionParameters object, the MySQL value is implemented for the DBMS property. In the technological log, the DBMySQL property is implemented for the DBMS property of the EDS event..	External data sources did not support all features of the MySQL query language.	Dynamic lists, temporary tables, and other platform features are now supported for MySQL external data sources.
Interface.	Management of client application interface content from 1C:Enterprise script is implemented. The objects ClientApplicationInterfaceContentSettings, ClientApplicationInterfaceContentSettingsGroup, and ClientApplicationInterfaceContentSettingsItem are implemented. Calling the RefreshInterface() global context method rebuilds interface panels according to the settings from the system storage. For the ClientApplicationInterfaceSettings object, a constructor and methods GetContent() and SetContent() are implemented.	The ClientApplicationInterfaceContentSettings object stored the differences between the client application settings and the settings specified in Designer. Interface management from 1C:Enterprise script was not supported.	1C:Enterprise script-based management of application interface panel visibility and positions.
Automated testing.	For the TestedFormField object, the WaitForDropListGeneration() method is implemented.	This feature was not provided.	The option to wait while a dynamic list is being generated is now available. You can use it when the generation takes significant time.
Interface.	A new display option intended for improving the view of item-heavy forms without introducing any significant form changes is available in the Taxi interface. The Scale property is implemented for managed forms. The property is only available if the Interface compatibility mode configuration property is set to Version 8.2. For the ClientSettings object, the ClientApplicationFormScaleVariant property is implemented. This property modifes the scale of all forms in the applied solution for a specific user.	This feature was not provided. There was no simple way to make a form compact.	For applications designed for Version 8.2 interface and not yet migrated to Taxi, a new option that regulates the scale of managed form items is implemented. You can modify both a scale of a single form (which is not yet redesigned for Taxi interface mode) and the scale of the entire application (you might need this if the applied solution runs on a computer with a low-resolution or small-sized display). The scale of a single form is specified in Designer, while the scale for the entire application is specified in the settings for a specific user.
Managed forms.	Passing additional parameters to an object creation form that is opened from a managed form text box is implemented (in addition to passing filters and standard parameters). Choice forms are used for storing additional parameters and passing them to item creation forms. Additional parameters are specified in choice parameters and choice parameter links using parameter naming forms (the parameter names must have the Additional. prefix). When item creation is initiated from a text box, these parameters are passed directly to the item creation form. When item creation is initiated from a drop-down list in a text box, they are first passed to the list form and then, when item creation is actually initiated, they are passed to the item creation form. The standard parameter AdditionalParameters of Structure type is implemented for managed form extensions of objects, catalogs, documents, charts of characteristic types, business processes, tasks, and dynamic lists. For dynamic list table extensions, the AdditionalCreateParameters property of FixedStructure type is implemented.	Filter values could be passed from text fields to item creation forms as filling values. Additional parameters could not be passed.	You can pass additional parameters (that are not filter options) to an item creation form that is opened from a text box.
Managed forms.	You can enable or disable history for text fields linked to data of the following types: catalog, document, business process, task, chart of characteristic types, chart of calculation types, chart of accounts, or exchange plan. The ChoiceHistoryOnInput property of configuration objects, configuration object attributes, and form items defines whether the history is enabled.	This feature was not provided.	For text fields whose business logic does not require keeping the history of values, you can disable the history.
Managed forms.	You can use the DropListWidth property to specify minimum width of drop-down lists for managed form text fields. The actual list width is the minimum value of the following: the property value and the stabdard width (40 characters).	Drop-down lists in text fields had fixed width (40 characters).	You can increase the width of drop-down lists that contain long items.
Configuration repositories.	In Designer batch mode, the following features are available: Creating a configuration repository (/ConfigurationRepositoryCreate command-line option) Creating a configuration repository user(/ConfigurationRepositoryAddUser command-line option) Copying users from another configuration repository (/ConfigurationRepositoryCopyUsers command-line option)	This feature was not provided. Configuration repository administrators only could create new configuration repositories and users interactively.	You can automate administrative operations on configuration repositories, including automatic creation of repositories for project parts that are being developed independently.
Dynamic lists. Document journals.	In document journals, you can use "Create" commands parametrized by the type of document being created. In a dynamic list that has a document journal table specified as its main table, a document creation button that opens a submenu with the list of documents available for the current user can be generated automatically. For dynamic list form table extensions, a standard CreateByParameter command is implemented. For the Button form item, the Parameter property is implemented. It is available only if the button is linked to the CreateByParameter command. For the BeforeAddRow event handler of form tables, the Parameter parameter is implemented. It is used for passing document type values during document creation. This change is not implemented in 8.3.2 compatibility mode.	In a dynamic list that has a document journal specified as a main table, a single Create command that did not open submenus was available. Running this command opened a dialog box for selecting document type. The type of document being created was not passed to the BeforeAddRow event handler of the form table linked to the dynamic list.	In document journals that contain a small number of document types, you can simplify the type selection during document creation. Easy and fast generation of individual buttons for creating documents of specific types on the form command bar.
Server clusters.	Licenses with a limited number of simultaneous sessions are implemented for the 1C:Enterprise server. The limitations apply to the following sessions: Designer (except for sessions intended for infobase creation) Thin client Web client Thick client External connection Licenses can be activated for both 32-bit and 64-bit server versions. The server cluster that uses this license type can only contain a single working server.	This feature was not provided. 1C:Enterprise server did not have limitations for the number of simultaneously connected users.	Extended list of supported licenses for 1C:Enterprise server. New delivery option focused on using the server in small businesses or subsidiaries.
Internet-enabled functionality.	The thin client supports the TLS protocol since 1C:Enterprise version 8.3.4.428. For the thin client, the /HttpsForceSSLv3 command-line option is implemented. It forces the system not to use the TLS protocol (if the connection is established using a web server), even if the web server supports this protocol.	1C:Enterprise versions 8.3.4.408 (and earlier) and 8.2.19 did not support the TLS protocol.	You can use the TLS protocol when needed.
National settings.	The following Mongolian locales are supported: mn - Mongolian mn_Cyrl - Mongolian (Cyrillic) mn_MN - Mongolian (Mongolian) mn_Mong - Mongolian (Traditional Mongolian) mn_Mong_CN - Mongolian (Traditional Mongolian, PRC)	Mongolian locales were not supported.	When 1C:Enterprise is started on a computer with Mongolian national settings, it is not shut down unexpectedly.

Table of contents

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Web client.	In Mozilla Firefox web browser, wordings in the web browser extension installation dialog box are clarified. The user is explicitly offered to install the extension.	The web browser extension installation dialog box offered the user to enable the extension.	For the web browser extension, the installation process is clearly differentiated from enabling the installed extension.
Advanced error handling.	Improved dump generation algorithm in the event of unexpected shutdown. The dump is generated even if a new exception occurs while the first exception is being processed.	If a new exception occurred while an exception was being processed, the dump was not generated.	The frequency of cases where the cause of an unexpected shutdown cannot be found by analyzing dumps is reduced.
Client application.	In the web client, the following managed system forms are revised: Select font dialog box Search and replace dialog box in spreadsheet documents Performance indicator dialog box In all managed system forms, the Help button is located in the command bar, instead of the More (All actions) menu.	Managed system forms had different layouts.	Managed system forms are improved.
Internet-enabled functionality. Client application.	Microsoft Internet Explorer 11 web browser is now supported.	Microsoft Internet Explorer 11 web browser was not supported.	The new version of Microsoft web browser is now supported.

Table of contents

Optimization

Functionality	After	Before	Result of changes
Configuration properties.	Configuration change checks are optimized. The execution time is reduced for the following configuration check operations: Executing the ConfigurationChanged() method Starting a 1C:Enterprise client Reading changes using the ReadChanges() method of an exchange plan manager.	The performance of configuration change checks lacked efficiency.	Improved performance of configuration change checks.
Web client.	Improved web client performance with the Taxi interface when a large number of forms are open.	The web client performance with the Taxi interface when a large number of forms were open lacked efficiency.	Improved web client performance in the Taxi interface mode.
Server clusters. Applied objects.	In the client/server mode, the impact of the numbering service on transaction start and end times is reduced, even when the numbering service is not used within the transaction. In the client/server mode, the performance of the numbering service with a large number of prefixes is improved.	In the client/server mode, the numbering service had negative impact on transaction start and end times, even when the numbering service was not used within the transaction. In the client/server mode, the performance of the numbering service with a large number of prefixes lacked efficiency.	Improved performance in the client/server mode when the numbering service is actively used with a large number of prefixes, e.g. in infobases with a large number of areas.
Managed forms.	Editing a large number of text lines in text boxes with the MultiLine property set to Yes was sped up for both thick and thin clients	The performance of text boxes that contained a large number of text lines was insufficient.	Reduced response time while editing large multiline texts in text boxes.
Configuration repositories.	For configuration repositories that do not use the compatibility mode, performance is improved for the following action types: Open a configuration bound to the repository Connect to the repository Store objects to the repository Update a configuration from the repository, retrieve objects, and cancel object locks Store objects to the repository while multiple users are working simultaneously	The specified operations lacked efficiency.	Improved performance of configuration repository operations.
Web client.	In Microsoft Internet Explorer 8 web browser, rounded borders of controls are not displayed in order to increase performance.	In Microsoft Internet Explorer 8 browser, rounded borders of controls were displayed.	Improved performance in Microsoft Internet Explorer 8 web browser.
Linux.	Performance of Linux clients is impoved for some scenarios.	In some scenarious, Linux clients lacked efficiency.	Improved performance of Linux clients.

Table of contents

Changes that affect system behavior

Functionality	After	Before	Result of changes
Applied objects.	Before restructuring an infobase, the platform checks whether user-created object attributes or tabular sections with reserved names are present in exchange plans. The list of reserved names in English includes: Ref, Code, Description, DeletionMark, ThisObject, DataVersion, AdditionalProperties, SentNo, and ReceivedNo. The list or reserved names in Russian includes: Ссылка, Код, Наименование, ПометкаУдаления, ЭтотОбъект, ВерсияДанных, ДополнительныеСвойства, НомерОтправленного, and НомерПринятого. If any exchange plan contains attributes or tabular sections with names listed above, the infobase cannot be restructured. This change is not implemented in 8.3.3 compatibility mode.	Before restructuring an infobase, the platform did not check whether object attributes and tabular sections with reserved names were present in the exchange plans.	The system behaves as expected during infobase restructuring.
Applied objects.	In the FillCheckProcessing() handler, if the Cancel parameter is set to True, event subscription execution is interrupted for the following objects: catalogs, documents, register record sets (including recalculations), document sequences, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks. This change is not implemented in 8.3.3 compatibility mode.	In the FillCheckProcessing() handler, if the Cancel parameter was set to True, event subscription execution was never interrupted.	The system behaves as expected.
Common attributes / Data separation. Managed locks.	In sessions that do not use separators, when data is being written or deleted, managed locks are set not only by reference and explicitly specified fields, but also by common attributes that serve as separators and include the object being written or deleted. The common attributes that are not separators can be used in the DataLockFields configuration object property. The DataLockFields list of attributes cannot contain common attributes that serve as separators in the Independently and simultaneously mode. You can specify such attributes as names for lock spaces of DataLock objects. If the separator value used in the DataLock object differs from the separator value used in the session, an exception is raised. These changes are implemented for the following object types: Catalogs Documents Charts of characteristic types Charts of accounts Charts of calculation types Exchange plans Business processes Tasks Constants	In sessions that did not use separators, when data was being written or deleted, managed locks were set only by reference and explicitly specified fields. The common attributes that were not separators could not be used in the DataLockFields configuration object property. Such common attributes could not be used as names for lock spaces of DataLock objects.	The number of lock collisions is reduced. In sessions that do not use separators, you can modify data in any data areas within a lock space provided that the data does not belong to the area where the lock has been set. For example, a lock is set to the Products catalog in the O1 area. You can modify data in any areas where the separator value is not equal to O1.
Spreadsheet documents.	When a spreadsheet document is saved to a PDF file, charts (Chart, GanttChart, and Dendrogram objects) are saved in the vector format.	When a spreadsheet document was saved to a PDF file, charts were saved as bitmap images.	The resulting PDF file size is reduced. Charts are resized when the file display area is changed in the PDF file viewer program.
Configuration repositories.	The history of comments entered by users when they store objects to the configuration repository is implemented. The history stores last 20 comments. Users can enter comments (which are saved to the history) when they lock repository objects. Users can select comments from the history when they store objects to the repository.	Comments that users entered when they stored objects to configuration repositories were not saved to a history.	In the configuration repository, improved usability of repeated object storing operations related to a single task, such as step-by-step implementation of a single feature.
Access rights.	You can specify multiple roles to be used for defining access rights when the user list is empty. The DefaultRoles configuration property is implemented. The DefaultRole property is supported for compatibility purposes. If the compatibility mode is disabled, accessing the DefaultRole property raises an exception. In 8.3.3 version compatibility mode, you can only specify a single role in the DefaultRoles property.	Only a single role could be specified as the default one.	Simplified development of applied solutions that can be run with or without user list.
Applied objects.	For configuration objects that can contain predefined data, you can set the PredefinedDataName property to a value of a custom type, which consists of the # character and the text presentation of a unique identifier.	The value of the PredefinedDataName property could be set only in the load mode (when the DataExchange.Load property was set to True).	You can load predefined data from files that have custom format.
Automated testing.	For user action log entries that are generated as a result of user interaction with managed form fields, buttons, groups, tables, and decorations, the name attribute is implemented. It stores the name of the form item accessed by user. The user action log conversion data processor includes the option that defines how the search for form items is performed: by presentation or by name.	Form item presentations were recorded to the user action log. The user action log conversion data processor only supported search for form items by item presentation.	The automated testing is more reliable. Search for form items by name is available, which eliminates the dependence of automated tests on localization language, item presentation typos, item presentation uniqueness, and so on.
Spreadsheet documents.	Spreadsheet documents are printed with the scale specified in their print options. This change is not implemented in 8.3.3 compatibility mode.	On some printers, spreadsheet documents were printed at 200% scale.	If a spreadsheet document is printed using a scale different from 100%, the system behaves as expected.
Dynamic lists.	In dynamic list filters, you can specify tabular section fields of objects that are used in the query that generates the dynamic list. This change is not implemented in 8.3.3 compatibility mode.	Tabular section fields of objects could not be used in dynamic list filters.	The list of dynamic list features is extended.
Dynamic lists.	During the retrieval of dynamic list data, dynamic list settings that are disabled by functional options are deleted. This change is not implemented in 8.3.3 compatibility mode.	Settings disabled by functional options were not removed from dynamic list settings.	Unexpected system behavior is eliminated.
Interface.	The colors of the sections panel and current section command panel in the Taxi interface are changed. When the current section command panel orientation is vertical, its title is not displayed. The presentation of current section command panel is changed to current section function panel.	The colors of the sections panel and current section command panel in the Taxi interface were different. If the current section command panel orientation was vertical, its title was displayed.	Better usability inTaxi interface mode.
Development tools. Configuration repositories.	You can quickly view the selective change history of configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. Selective history is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, objects included in exchange plans, styles, main section working areas, flowcharts, forms, help pages, predefined items, command interface fragments, and role rights. To view the selective history, right-click anywhere in any of the repository dialog boxes or in the configuration comparison window, and then click View selective history. In the Filter repository versions dialog box, filter by properties of selected configuration objects is added. Viewing selective history is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.	This feature was not provided. Only the full object change history was available.	Improved usability of configuration repository. Viewing the history of items that are parts of configuration objects is simplified.
Web client and web service publishing tools.	In Designer, in the dialog box for publishing the web client and web services: You can manage execution of background jobs in file mode (the allowexecutescheduledjobs attribute of the ws tag). You can specify whether web services are published by default (the pointEnableCommon attribute of the ws tag).	Managing execution of background jobs in file mode and specifying whether web services are published by default were only available when publishing was performed using the webinst utility (based on a template). The publishing dialog did not provide access to managing these features.	You can specify all of the options available in the default.vrd file during interactive publishing.
Spreadsheet documents.	You can use the ViewScalingMode property of spreadsheet document form extension to specify how the spreadsheet document will be displayed: as in platform version 8.2 or enlarged.	This feature was not provided. Reports with large fonts looked too large in the Taxi interface mode.	You can scale displayed spreadsheet documents that have custom (large) fonts.
Dynamic lists.	In dynamic lists, presentation fields cannot be used in filters, groupings, or ordering. Searching by presentation fields is not available.	In dynamic lists, presentation fields could be used in filters, groupings, or ordering. Search by presentation fields was available.	Unexpected system behavior is eliminated.
External data sources. Data composition system. Queries.	In external data sources, you can use functions specified in them. A function can return a value, or a table, or nothing. You can specify types of external data source tables: table or expression (this is required to describe functions that return tables). To call an external data source function, use one of the following query language expressions: ExternalDataSource.< Source name>.Table.<Table function name>(<Parameter 1>,...,< Parameter N>) ExternalDataSource.<Source name>.<Function name>< Parameter 1>,...,< Parameter N> You can call functions using the object model. This can be performed with either external data source managers or external data source table managers. In the picture library, the ExternalDataSourceFunction is implemented.	External data sources did not support functions.	The external data source functionality is extended.
Data composition system.	If an aggregate function is used in the RecordsFilter parameter of the EvalExpressionWithGroupArray() or EvalExpressionWithGroupValueTable() functions, an error is generated. This change is not implemented in 8.3.3 compatibility mode.	Using aggregate functions in the RecordsFilter parameter of the EvalExpressionWithGroupArray() and EvalExpressionWithGroupValueTable() functions did not generate an error.	Unexpected system behavior is eliminated.
Web client.	In Microsoft Internet Explorer 10 web browser, in managed form text boxes, the Clear input system button is removed.	In Microsoft Internet Explorer 10 web browser, in the managed form text box, the Clear input system button had the same functionality as the Clear button, which was added by the platform.	Eliminated web client appearance differences between Microsoft Internet Explorer 10 and other web browsers.
Configuration repositories.	The Update configuration from repository command is executed without displaying a dialog box if new objects are found in the repository. New objects are automatically created in the target configuration.	The Update configuration from repository command opened a dialog box if new objects were found in the repository. If a configuration was updated using Designer batch mode and new objects were found in the repository, the update was not performed.	Applied solution configurations can be updated automatically (for example, using the a batch file). You can include the update in various scheculed tasks, such as automated testing. The configuration update no longer requires interactive actions, which can pause the batch file execution.
Interface.	The splash screens for Designer and all types of client applications are modified: borders are used instead of shadows.	The splash screens had shadows.	Eliminated splash screen drawing issues in a number of scenarios.
Common objects.	Checks that determine whether defined type contents are valid are performed for each defined type call in the following scenarios: during configuration verification before saving a configuration. The check is only performed when the Compatibility mode configuration property is set to Version 8.3.3 or None. If the compatibility mode is set to version earlier than version 8.3.3, defined type contents are only checked for the presence of external data source functions.	The checks whether defined type contents were valid were only performed when the dialog box for specifying configuration object attribute type was generated. When a configuration was saved, the checks whether defined type contents were still valid were not performed for each defined type call.	Eliminated several potential issues that could occur during the development of applied solutions with defined types.
Managed forms.	In 8.2.16 version compatibility mode, if a text box does not have the selection list mode enabled, its drop-down lists do not contain the selection list specified in the text box properties.	In version 8.3.3, drop-down lists in text boxes always contained the choice lists specified for these text boxes.	Redesign is not required for applied solutions that run in version 8.2.16 compatibility mode.
Standard functions. Common attributes / Data separation.	The standard Delete marked objects data processor attempts to set the exclusive mode for object deletion if the configuration compatibility mode is set to Version 8.3.3 or later (including the None value of the Compatibility mode property). If the configuration has Version 8.3.2 or earlier compatibility mode, the exclusive mode is only set for sessions that do not use separators or in configurations that are not separated.	The standard Delete marked objects data processor attempted to set the exclusive mode for object deletion only if deletion was performed either in a session that did not use separators or in a configuration that was not separated. The compatibility mode did not affect the criteria for setting exclusive mode.	You can delete marked objects in sessions that use separators.
Applied objects.	An automatically assigned object number is reused if the transaction where the object was written is cancelled, regardless of the value of the Objects Autonumbering Mode configuration property.	If the Objects Autonumbering Mode configuration property was set to Do not Release Automatically, an object number was not reused when the transaction where the object was written was canceled.	Eliminated unexpected system behavior.
XML and XDTO support.	When data is deserialized from XML- or XDTO-serialized files, the Predefined items are ignored for tabular sections of charts of accounts and charts of calculation types. If such items are found, no errors occur and data is deserialized successfully.	During the attempt to deserialize items of a chart of accounts or a chart of calculation types, having the Predefined item in a tabular section resulted in an exception and the deserialization could not be performed.	You can load data serialized in later versions of 1C:Enterprise (version 8.3.5 and later).
Third-party software.	The OpenSSL library is updated to version 1.0.0m.	OpenSSL version 1.0.0l was used.	Eliminated OpenSSL security issues.

Table of contents

Changes that require modification of configuration and administrative settings

Functionality	After	Before	Result of changes
Information registers.	For information registers with Enable totals for retieving slice first or Enable totals for retrieving slice last property enabled, the Active and LineNumber fields are removed from the list of fields of information register slice first/last virtual tables. If Enable totals for retieving slice first or Enable totals for retrieving slice last property is disabled, the Active and LineNumber fields are included in the slice first/last virtual tables.	The Active and LineNumber fields were included in the list of fields of information register slice first/last virtual tables.	The system behaves as expected. In managed forms, the form items linked to the Active and LineNumber fields are removed automatically.
Managed locks.	Managed transaction locks (the DataLockFields property) cannot be set by attributes of objects of the following types: string of unlimited length, value storage, characteristic value type, and complex types that include these types. The check is performed during the configuration check, and an error message is displayed if any field does not comply with the limitations.	It was recommended that you did not use attributes of the following types in managed locks: string of unlimited length, value storage, characteristic value type, and composite types that included these types. During the configuration check, the check for managed locks by attributes of these types was not performed.	The configuration performance is optimized. Improved quality control during configuration development.
Access rights.	The IsInRole() function raises an exception in the following cases: A value that is not a string and not a Role configuration object is passed as a parameter. A name of a role that does not exist is passed. This change is not implemented in 8.3.3 compatibility mode.	The IsInRole() function did not check the parameter value and returned True even when the passed role was missing from the configuration.	The system behaves as expected.
Data composition system.	When data composition is performed from 1C:Enterprise script, the platform checks whether the privileged mode is enabled while getting the list of available fields. This change is not implemented in 8.3.3 compatibility mode.	When data composition was performed from 1C:Enterprise script, the platform did not check whether privileged mode was enabled.	If privileged mode is enabled, data composition can include fields that users cannot access.
Web services.	The values of the WSParameterDirection system enumeration are corrected: The InOut item represents the InOut value. The Out item represents the Out value. This change is not implemented in 8.3.3 compatibility mode.	The values of the WSParameterDirection system enumeration represented the following: The InOut item represented the Out value. The Out item represented the InOut value.	Unexpected system behavior is eliminated.
Data exchange.	A flag that specifies whether predefined data should be updated for the entire infobase is now available. It can be set both in 1C:Enterprise script and in the command line. In the 1C:Enterprise mode, the predefined data update procedure checks the flag that is set for the entire infobase (in addition to checking the flags set for individual configuration objects, checking the flags set for infobase data, and checking the infobase type: master/not distributed infobase or subordinate infobase). The global context methods SetInfoBasePredefinedDataUpdate() and GetInfoBasePredefinedDataUpdate() are implemented. The command-line option /SetPredefinedDataUpdate is implemented for Designer batch mode. This change is not implemented in 8.3.3 compatibility mode.	The check whether predefined data should be updated was based on infobase data and metadata flags and on the infobase type.	You have the option to set predefined data update flags easily for infobases that are disconnected from distributed systems for maintenance. Also, the following scenario is now supported: exchange in a nondistributed infobase between two similar applications where predefined data is set in one of the applications and should be replicated to the other one during the exchange.
Applied objects.	In the thick and thin clients, the WriteParameters parameter is implemented for the AfterWrite handler of managed form extension handlers for constants, information register records, and register record sets. In version 8.3.3 or earlier compatibility mode, the parameter always has the Undefined value. The description of the WriteParameters parameter is added to the AfterWrite Syntax Assistant entry.	The AfterWrite handler of managed form extension handlers for constants, information register records, and register record sets lacked the WriteParameters parameter. The description of the WriteParameters parameter was missing from the AfterWrite Syntax Assistant entry.	Unexpected system behavior is corrected.
Dynamic lists. Functional options.	The main managed form attribute of Object(CatalogObject, DocumentObject, and so on) type is disabled if a functional option disables the corresponding configuration object. The main managed form attribute of DynamicList type is disabled if a functional option disables a configuration object that is used a main table for the dynamic list. In both cases, only functional options without parameters are taken into account.	In 1C:Enterprise version 8.2, the main form attribute of Object type was not disabled even if any functional option disabled the corresponding configuration object. In 1C:Enterprise version 8.3, the main form attribute of Object type was disabled if a functional option disabled the corresponding configuration object. All functional options were taken into account. In the previous 1C:Enterpise versions, the main form attribute of DynamicList type was disabled if a functional option disabled the configuration object that was used as a main table of the dynamic list. All functional options were taken into account.	The system behaves as expected. In particular, the following issue is eliminated: Editing a form changes a functional option parameter (directly or indirectly). The new parameter value causes the functional option to disable the configuration object that is the main form attribute. The disabled configuration object clears the entire object form.
Managed forms.	If the interface compatibility mode is set to Version 8.2, text boxes have the following specifics: When a text box is activated, a drop-down list is not opened. For the DropListButton property of the managed form field extension for a text box, the Auto value is interpreted as False. For the ChoiceButtonRepresentation property of the managed form field extension for a text box, the Auto value is interpreted as ShowInInputField. For the ChoiceButton property of the managed form field extension for a text box, the Auto value is interpreted as in 1C:Enterprise version 8.3.2. Clicking the Down Arrow button opens a choice form, not a drop-down list.	In Version 8.2 interface compatibily mode,the text box behavior was identical to the text box behavior in Taxi interface compatibility mode.	For users who migrated to 1C:Enterprise version 8.3 while keeping Version 8.2 interface compatibility mode, the system behavior is similar to previous versions.
System requirements.	Microsoft Windows 2000 operating system is no longer supported.	Microsoft Windows 2000 operating system was supported.	An outdated operating system is no longer supported.
Client application.	Client computers that run operating systems of Windows family require Microsoft Internet Explorer web browser version 7.0. On computers with Microsoft Internet Explorer version 6.0 or earlier, users of thick and thin clients of version 8.3.4 or later might experience various issues.	Client computers that run operating systems of Windows family required Microsoft Internet Explorer web browser version 6.0 or later.	The out-of-date web browser is no longer supported. The platform features that use Microsoft Internet Explorer now require Microsoft Internet Explorer version specified in the platform system requirements.

Table of contents

Renamed objects

Object	The old name	The new name
A property of managed form extension for text fields. The former name is supported for compatibility purposes.	ListSelWidth	DropListWidth
The English name for the Choose() method of the QueryResult and QueryResultSelection objects is changed. The former name is supported for compatibility purposes.	Choose()	Select()
The button linked to the Cancel command in the managed report form extension, report settings form, and report variant form. The former name is used in version 8.3.3 compatibility mode.	FormCancel	FormCancelEdit

Table of contents

Mobile platform

Functionality

After

Before

Result of changes

System requirements.

Mobile platform now supports x86 Intel CPU-based devices that run Android OS. The mobile platform for x86 architecture is provided in a separate file.

The mobile platform distribution kit contains the following files:

1cem-arm.apk, the developer's mobile platform for ARM architecture
cem-x86.apk, the developer's mobile platform for x86 architecture
prjandroid-arm.zip, the mobile platform for building mobile applications (for ARM architecture)
prjandroid-x86.zip, the mobile platform for building mobile applications (for x86 architecture)

The mobile platform did not support x86 Intel CPU-based architecture.

More devices are now supported.

Development tools.

Mobile application builder is a new applied solution intended for building mobile applications. It has the following features:

Storing mobile configurations
Storing mobile platforms (starting from version 8.3.4)
Storing graphic assets
Building mobile applications
Storing the built mobile applications

Mobile application builder can build mobile applications for Android x86 operating systems.

It can also perform full building of mobile applications for iOS using a Mac computer with Xcode installed.

The configuration is delivered together with the mobile platform distribution kit. The data processor used for building mobile applications is removed from the mobile platform distribution kit.

Building can be performed using any Android SDK version.

A data processor was used for building mobile applications. It was included into the mobile platform distribution kit.

Simplified building of mobile applications. Building mobile applications for iOS no longer requires additional steps.

System requirements.

Android version 2.2 is no longer supported.

Android version 2.2 was supported.

Support of the obsolete operating system version has ended.

Table of contents

Transition from the previous version to the version 8.3.4

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.4.
Some features that are added in version 8.3.4 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.
During the transition to version 8.3.4, if your infobase runs in the file mode, we recommend that you perform infobase verification and repair with the Compressing Infobase tables check box selected.

Table of contents

Version 8.3.3

Version 8.3.3 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 version 8.2 to the version 8.3.3
Transition from the previous version to version 8.3.3

New functionality and changes

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.3.2 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, and 8.3.1.	In version 8.3.3 you can run configurations created in version 8.3.2 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.3 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.2 for working with the infobase even after the transition to version 8.3.3. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Managed forms.	You can specify settings for vertical scaling of form elements, namely the minimum element height, at the development stage in Designer using the new VerticalScroll property. If a form has a vertical scroll bar and the command bar is located above or below all form elements and occupies the entire form width, the area being scrolled does not include the command bar.	Managed form elements could be reduced to the default minimum height by reducing the form height. If a managed form had a vertical scroll bar, the area being scrolled included all form elements.	Elements of managed forms with vertical scroll bars cannot be compressed below the minimum height guaranteeing comfortable work. The command bar with important form commands, such as Write and close, is always available because it is not included in the area being scrolled.
Managed forms. Web client.	In the web client, if the VerticalScroll property of the managed form is set to UseIfNecessary, reducing the vertical form size never leads to reducing the vertical size of the form elements to the point where they can no longer be used.	In the web client, reducing the vertical form size could lead to reducing the vertical size of the form elements to the point where they could no longer be used.	Eliminated situations when reducing the vertical form size led to reducing the vertical size of the form elements to the point where they could no longer be used.
Development tools.	In the built-in script editor, you can group an arbitrary number of lines in the same way as they are grouped in some syntax units (conditions or cycles). #Region and #EndRegion preprocessor instructions are implemented. These instructions are ignored during script execution. A template for creating a script fragment with line grouping is added to the set of standard templates.	This feature was not provided. Only a few script syntax units allowed line grouping.	Improved usability for working with source text. You can group parts of source text in a logical way and hide text that is not used at the moment.
External data sources.	Support of the following OLAP sources is added to the external data sources mechanism: Microsoft SQL Server Analysis Services IBM InfoSphere Warehouse Oracle Essbase Requests to OLAP sources and errors that occur during the request execution are recorded to the EDS event of the technological log. The following pictures are added to the picture library: ExternalDataSourceCube, ExternalDataSourceCubeDimensionTableObject.	External data sources provided access to relational tables only.	Both relational data and OLAP sources can be used when creating reports based on data from external systems (external data sources).
Interface.	You can get the resolution and DPI of monitors connected to a computer in the client application (thin client, thick client, web client) and at the server. For the external connection, the GetClientDisplayInformations() method returns UNDEFINED. The information on characteristic of client computer monitors is passed through at the session start and when the RefreshInterface() method is called.	You could get the information on monitors connected to a computer only on the mobile platform.	You can determine the number of monitors connected to the computer where the application is being executed, as well as their characteristics.
Data composition system.	For conditional appearance elements, you can specify areas where the given conditional appearance element will be used. This feature is not used in dynamic lists. This change is not implemented in 8.3.2 compatibility mode.	The conditional appearance was applied both to data area and area header, without further customization	Extended formatting capabilities for complex reports.
Web client and web service publishing tools.	Infobases, web services, and mobile applications can be published from Designer that is running on Linux. Publishing can only be performed to Apache web servers and only if Designer is running under root account.	Publishing of infobases and web services on Linux was possible only using the webinst utility. Publishing mobile applications was not available on Linux.	Eliminated some Designer limitations on Linux.
Linux.	You can create distribution kits in the Linux version of Designer. The platform distribution files now include an installation program that installs templates and updates for applied solutions that run on Linux. The installation program supports both 32-bit and 64-bit Linux versions. The installation program shares the list of Linux operating systems with the client application.	Creation of distribution kits was not available on Linux.	You can install templates and update applied solutions on Linux operating systems.
Autorun.	The Autorun application is capable of running on Linux. The application supports both 32-bit and 64-bit Linux versions. The application shares the list of Linux operating systems with the client applications. The following properties are added to the Element section of the autorun.lst configuration file: CommandWindows, CommandLinux, and RunAsRoot. The properties specify how a given item is executed in various operating systems.	The Autorun application was not available for Linux systems. The autorun.lst configuration file did not include CommandWindows, CommandLinux, and RunAsRoot properties.	You can create applied solution distribution kits that include the Autorun application and are delivered on removable media that can be used to install the solution on both Windows and Linux operating systems.
Applied objects. Managed forms.	Objects of reference types can be created while data is being entered in a form. A new property of configuration objects and form elements is implemented for this feature. The form element property manages the visibility of the command that creates a choice list element. The feature is implemented for catalogs, documents, charts of characteristic types, charts of accounts, charts of calculation types, business processes, tasks, and exchange plans. The command for creating a choice list element is not available in version 8.3.2 compatibility mode.	This feature was not provided. Users had the option to open the choice form and create an object there, and then select the created object.	Improved usability in cases when object creation is required while data is being entered.
Managed forms. Development tools.	In the managed form editor, the list of elements available for adding to the form now includes a usual group without a title.	In the managed form editor, in order to create a usual group without a title, a developer had to add a usual group and then change the properties that define whether the title is displayed.	Improved usability of editing managed forms when groups are used for defining element positions on the form.
Managed forms. Development tools.	During the generation of event handlers for client form elements and commands, you can specify which procedures will be generated: A client handler only A client handler and a server procedure (to be executed outside of a context) that is called from the handler A client handler and a context server procedure that is called from the handler A context server procedure cannot be generated for those client handlers where calling context server procedures is not recommended.	When a client handler was generated, this only included the generation of the handler itself. The associated procedures were not generated.	Simplified development of forms where actions that are called at client are executed at server. Developers no longer have to create the server method manually and then add the method call to the client handler body.
Configuration repositories.	The data storage format of the configuration repository is modified. Repository objects are stored in the file system. The 1cv8ddb.1CD file stores information on changed objects. The compatibility mode is implemented for the configuration repository. The new storage format is available only if the compatibility mode is disabled. Optimization of configuration repository data is introduced. The optimization procedure is available both from the repository administration window and by using the ConfigurationRepositoryOptimizeData command-line option when Designer is started in batch mode. The format of configuration repository files is not intended for reading or writing by any tools other than 1C:Enterprise.	All configuration repository data was stored in the 1cv8ddb.1CD file. Optimization of the configuration repository was not available.	Significantly increased number of changes (versions) that can be stored in the configuration repository.
Development tools. Client application.	The infobase selection dialog box and the two authentication dialog boxes (for access to infobases and configuration repositories) that are displayed during the start of a client application or Designer can be disabled. To disable them, use the DisableStartupDialogs command-line option for the 1cv8.exe/1cv8 file. If the command-line that starts a client application or Designer contains errors that led to displaying these dialog boxes in earlier platform versions, the dialog boxes are not displayed; diagnostic messages are generated instead. These messages are recorded to the file that stores service messages (the Out command-line option).	During the start of client application or Designer in the batch mode, provided that infobase parameters or authentication parameters contained any errors, modal dialog boxes that prompted users to enter the correct parameters were displayed. This paused the execution of the entire batch.	When Designer is started in batch mode - especially if Designer is started from another application or service - it is now possible to avoid the hard-to-detect situations when Designer attempts to create a selection dialog box for parameters that cannot be specified interactively, and therefore stops responding.
Localization.	The NumberInWords() and PeriodPresentation() global context methods support French language. The language code is as follows: fr, fr_CA. Values of the NumerationItemOptions parameter of the NumberInWords() method are specified similar to English, Finnish, and Kazakh languages.	The NumberInWords() and PeriodPresentation() global context methods did not support French language.	Improved presentation of information for French-speaking users.
Managed forms. Full-text search.	For the FullTextSearchList object, you can disable the search by presentations of configuration objects. Use the MetadataUse property of this object to enable or disable this feature.	The search by presentations of configuration objects could not be disabled.	You can search by data only, without seaching by presentations of configuration objects at the same time.
1C:Enterprise script.	For the Array, Structure, and Map collections implemented constructors that create these objects based on the corresponding fixed collections (FixedArray, FixedStructure, and FixedMap). Recursive conversion is performed for arrays—a fixed array item that is a fixed array itself is recorded to a regular array.	Fixed collections could be converted to their regular analogs only by using program loops.	Simplified editing of values stored in fixed collections.
Common attributes / Data separation.	Exclusive access can be set for a data area. Exclusive access is not compatible with any data locks set by other sessions in this area. Exclusive access to a data area must be explicitly set or removed using the SetExclusiveMode() method. When a background job is started from a session that set exclusive access to a data area, the background job obtains exclusive access and the parent session loses exclusive access until the parent session is completed. At this time, changing data from the parent session is not available. Exclusive access is returned to the parent session after the background job completion. When a session switches to a different area, this does not affect the list of areas where the session has exclusive access. Exclusive access to an area prohibits the following actions: Creation of new sessions with the same set of separators. Access to the area-contained data from enveloping areas. Setting exclusive access in enveloping areas. Setting shared managed locks for an area is ignored if exclusive access is set for this area.	Exclusive access to a data area could not be set. Instead, you only could set an exclusive managed transaction lock to all area-contained data.	You can perform consistent changes of the data area even if they cannot be included into a transaction.
Common objects.	The DataHashing object can calculate the SHA1 and SHA256 hash functions.	The DataHashing objects could calculate only the MD5 and CRC32 hash functions.	The list of supported hash functions is extended.
Applied objects.	You can create defined types. A defined type consists of one or several allowed types, and it has a unique name. Defined data types can be used as types of configuration object attributes. Defined types cannot be included in complex types and cannot be used as data types for charts of characteristic types. If you want to run the applied solution on a previous platform version, you have to remove all defined types from the configuration.	This feature was not provided.	You can create a type that can be used for defining types of specific attributes. For example, in a universal multipurpose configuration fragment, you can describe attributes that refer to data that will be defined when the fragment is included into a specific configuration.
Mobile application.	You can choose a ZIP archive containing multiple pictures of different sizes, instead of a single picture, for the application. This option is targeted for mobile applications that can be used in devices with different screen resolutions. The following mobile device screen types are supported: devices with screen resolution below 140 DPI devices with screen resolution from 140 to 180 DPI and Apple devices with standard screens devices with screen resolution from 180 to 270 DPI devices with screen resolution over 270 DPI and Apple devices with Retina screens Each picture corresponds to specific screen settings of the target device. It is recommended that you use the PNG format for the archived pictures and you create the archive without compression. For the Picture object, the ChoiceSet property is implemented.	This feature was not provided. On the mobile platform, the developer had to specify multiple picture versions for various screen resolutions using 1C:Enterprise script.	Simplified process of creating applications intended for running on both PC and mobile devices. The developer only has to provide pictures for different display resolutions, and they do not have to write the script for resizing the pictures before displaying them in the 1C:Enterprise mode.
Accumulation registers. Accounting registers.	In accumulation and accounting registers, the interval for storing totals by periods can be limited. You can specify both the lower and the upper boundary of the interval. Totals within this interval can be recalculated automatically when totals outside of the interval are changed. Totals by periods are not stored outside of the interval. They are calculated by register record tables when needed. For accumulation register managers and accounting register managers, the following methods are implemented: SetMinTotalsPeriod(), GetMinTotalsPeriod(), and SetMinAndMaxTotalsPeriods(). The totals storage limits are taken into account when the chart of accounts is changed, when register records are generated, when totals are recalculated, and when balance is obtained by balance accumulation and accounting registers. When totals are enabled, periods are only recalculated if they contain actual changes. This change is not implemented in 8.3.2 compatibility mode.	Totals were stored by all periods later than the period of calculated totals for the register. When register records were changed for a prior period, all totals were recalculated for periods later than the modified date. When using totals was turned on, all register totals were also recalculated.	This change reduces database size and optimizes performance of administrative operations. This decreases the system load for databases that store data for long periods (several years), and where changes in prior periods are performed on regular basis but regular data retrieval (using totals) is performed within a limited time interval from the current date.
Add-ins.	The add-in creation functionality includes the option to display interactive messages to users and the option to store values between sessions in a local web browser cache. The add-in development technology documentation (http://1c-dn.com/library/add_in_creation_technology/) is updated by enhancing examples and adding new versions of web browser adapters.	The add-in creation functionality did not include the option to display interactive messages to users or the option to store values between sessions in a local web browser cache.	When a web browser add-in attempts to access local resources, warnings can be displayed. They are similar to warnings available in the built-in platform features.
Web client. Spreadsheet documents. Printing documents.	Documents intended for printing can be combined into batches. To print the entire batch, you only have to start printing once. You can specify printing options for batches. Batches can be nested. A batch can be written to a single PDF file, which simplifies printing in the web client. The RepresentableDocumentBatch object is implemented.	Batch printing was not available in the web client. To print a set of documents, the user had to click the Print button for each single document.	Improved usability of printing muptiple documents (with different printing options) in the web client. To print a batch of documents, the user has to start printing once (regardless of the number or documents in the batch), and the printing options (including page orientation and the number of copies) will be set for each individual document.
Server clusters.	In the client/server mode, security profiles are implemented for the purpose of managing applied solution access to the following external resources on 1C:Enterprise server: file system, COM objects, add-ins, operating system applications, Internet resources, privileged mode, external reports and data processors, and global context methods Execute() and Eval(). A security profile can be assigned to each infobase; a security profile can also be assigned to the source code that is executed in the safe mode. For the purposes of software cluster administration: ISecurityProfile object is implemented. ISecurityProfileVirtualDirectory object is implemented. ISecurityProfileCOMClass object is implemented. ISecurityProfileAddIn object is implemented. ISecurityProfileExternalModule object is implemented. ISecurityProfileApplication object is implemented. ISecurityProfileInternetResource object is implemented. For the IServerAgentConnection object, the following methods are implemented: GetSecurityProfiles(), RegSecurityProfile(), UregSecurityProfile(), CreateSecurityProfile(), GetSecurityProfileVirtualDirectories(), RegSecurityProfileVirtualDirectory(), UnregSecurityProfileVirtualDirectory(), CreateSecurityProfileVirtualDirectory(), GetSecurityProfileCOMClasses(), RegSecurityProfileCOMClass(), UnregSecurityProfileCOMClass(), CreateSecurityProfileCOMClass(), GetSecurityProfileAddIns(), RegSecurityProfileAddIn(), UnregSecurityProfileAddIn(),CreateSecurityProfileAddIn(), GetSecurityProfileUnSafeExternalModules(), RegSecurityProfileUnSafeExternalModule(), UnregSecurityProfileUnSafeExternalModule(), CreateSecurityProfileUnSafeExternalModule(), GetSecurityProfileApplications(), RegSecurityProfileApplication(), UnregSecurityProfileApplication(), CreateSecurityProfileApplication(), GetSecurityProfileInternetResources(), RegSecurityProfileInternetResource(), UnregSecurityProfileInternetResource(), and CreateSecurityProfileInternetResource(). For the IInfoBase object, the following properties are implemented: SecurityProfileName and SafeModeSecurityProfileName. The type of the SafeMode parameter (used in the Create() and Connect() methods of external report and data processor managers and in the SetSafeMode() global context method) was changed from BOOLEAN to STRING. The type of value returned by the SafeMode() global context method was changed from BOOLEAN to STRING. When this parameter (or returned value) has STRING type, it stores the security profile name. Similar changes are implemented in: Cluster administration utility (rac) – the profile mode is implemented, and the update command of the infobase mode is modified. Java API for server administration.	This feature was not provided.	You can limit access of applied solutions to the resources of the system in which they run by using administrative tools (without modification of the applied solution source code). The functionality of the source code that is executed in the safe mode (for example, code developed by user) can be extended while preserving the required security level. For example, you can use security profiles to organize individual temporary storage directories for each data area, or describe the list of Internet resources available for use in a specific infobase.
Automated testing.	The following objects are implemented: TestedCommandInterfaceButton, TestedCommandInterfaceGroup, and TestedWindowCommandInterface. For tested objects, the GetObject() method is implemented. Its set of parameters is similar to that of the FindObject() and FindObjects() methods. If the object is not found, the GetObject() method raises an exception. Methods for testing user messages are implemented. The list of properties and methods for managing tested objects is extended. You can get the form name, the current window, the command interface, and so on. You can get the information on the last error that occurred in the tested client application. For the TestedApplication object, the methods GetActiveWindow() and GetCurrentErrorInfo() are implemented. For the TestedClientApplicationWindow object, the methods GetCommandInterface(), GetUserMessageTexts(), and ChooseUserMessage() are implemented. For the TestedForm object, the FormName property and the methods FindDefaultButton(), CurrentModified(), and GetCommandBar() are implemented, while the Close() method is moved to the TestedClientApplicationWindow object. For the TestedFormField object, the methods CurrentModeIsEdit() and GetEditText() are implemented, and the methods BeginEditCurrentArea() and EndEditCurrentArea() are modified. For the TestedFormTable object, the method CurrentModeIsEdit() is implemented, and the methods ChangeRow(), EndEditRow(), GotoPreviousRow(), GotoNextRow(), Expand(), and Collapse() are modified. For objects that describe tested form elements, the methods GetToolTipText(), CurrentVisible(), CurrentEnable(), CurrentReadOnly(), GetContextMenu(), and GetCommandBar() are implemented.	The application window command interface could not be tested automatically. Operations on user messages were not available during the automated testing.	You can test the application window command interface automatically. In test scenarios, simplified the processing of errors that occur when attempts to get non-existent objects are made.
Dynamic lists.	Dynamic list settings can be saved automatically. For managing this feature, the Auto save user settings property is implemented for dynamic lists. For storing settings, the dynamic list settings storage is implemented. For managed form tables linked to dynamic lists, the following functionality is implemented: commands for saving and restoring settings, and events for implementing custom responces to saving, restoring, or editing dynamic list settings. The view mode of the dynamic list (list, tree, or hierarchical list) is stored together with form element settings. You can edit user settings of a dynamic list in a separate group of the form that displays the dynamic list. For that purpose, the User settings group property is implemented. Dynamic list settings can be edited in a separate common form, which is specified using the Default dynamic list settings form configuration property. For the DynamicList object, the SettingsComposer property is implemented, which is similar to the corresponding property of report objects. This change is not implemented in 8.3.2 compatibility mode.	For dynamic lists, only the following settings were saved automatically: filters (that were restored with disabled usage flag) and conditional appearance. To save and restore other settings, developers had to create custom algorithms in 1C:Enterprise script.	Improved usability of dynamic lists for end users. Simplified development of dynamic lists with quick access to filters for developers. Development of custom algorigthms for saving or restoring dynamic list settings is not required.
Managed forms.	A new permission allowing end users to expand or collapse a managed form group (only vertically) was added. If the permission is granted, a user can collapse the group (hide all of the items that are included in the group). For managed form groups, the following properties are implemented: Behavior, ControlRepresentation, ShowLeftMargin, and CollapsedRepresentationTitle. Only usual groups with displayed titles can be collapsed.	This feature was not provided. The only available method to hide unused items was to change their visibility.	Hiding form items that are rarely used is available. This decreases the amount of data that is displayed to an end user. To view the hidden data, an end user can expand the group.
Development tools.	On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed is displayed in the message window.	On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed was displayed in a modal window.	Developers no longer have to close modal dialog boxes many times when they attempt to perform mass modification of objects that cannot be modified (for example, objects stored in a configuration repository that are not locked).
Interface.	A new client application interface type "Taxi" is implemented. The Taxi interface includes a large number of changes, with the following highlights: A whole new view: enlarged fonts, increased spacing between elements in forms, modified color scheme and form element layout, enlarged form elements. Improved application navigation: focus on a single-window functionality, single purpose panels (such as history or favorites), switching back and forward between previously opened windows, and so on. Extended main application window settings: developers can define the content and location of panels for the applied solution, at the same time users can arrange these panels as they like. A system form for the full-text search. The form navigation panel is located in the upper part of the form. The message window is located in the lower part of the form and is only visible when there are messages to display. The performance meter is displayed in a separate application window panel, not in a separate window. In the History panel, records are grouped by days with their opening time displayed. You can search for history items and add them to Favorites. In the Favorites panel, you can search for items, rename them, and "pin" important ones at the top of the list. Use the iTaxi command-line option of the client application for the forced start of this interface mode (provided that using Taxi is allowed in the applied solution). You can also switch between interface modes using the client application settings window. The following configuration properties are implemented: InterfaceCompatibilityMode - specifies which interface modes are available in the applied solution. ClientApplicationInterface - stores the list of panels used by default in the client application, as well as their positions. DefaultSearchForm - specifies the search form that is used for the full-text search in application data. If the form is not specified, the system full-text search form is used. A brand new look for the calendar. For the managed form calendar field, the following properties related to the new features are implemented: HeightInMonths, WidthInMonths, and ShowMonthsPanel. These properties are only used in the Taxi interface. For the ClientApplicationInterfaceVariant object, the ClientApplicationInterfaceVariant property is implemented (it is used for getting the interface mode), and the global context method ClientApplicationInterfaceCurrentVariant(). The ClientApplicationBaseFontCurrentVariant() global context method is implemented. It gets the size of the base font in the client application. For the UserWorkFavoritesItem object, the Important and Presentation properties are implemented. In the Taxi interface, the Desktop is renamed to Start page (the related commands are renamed accordingly). The Dashboard section of the section pane is used for accessing the command interface. In the Taxi interface: The All actions menu is renamed to More. The default presentations of standard commands in forms are changed, as well as command presentations in the command panel and in the More menu. The presentations of form item groups are changed. The link to the start page (desktop) of the applied solution has the following format: e1cib/navigationpoint/startpage. Start page (desktop) settings are stored with the settings key StartPage/WindowSettings (for Taxi interface, StartPage/Taxi/WindowSettings). In the managed form editor, switching between interface 8.2 and Taxi modes in the preview window is implemented.	The interface implemented in platform version 8.2 was used in managed applications.	Improved applied solution navigation, improved usability, development according to modern interface design trends.
Interface.	The NormalTextFont style font used as a basis for size calculation for other style fonts except the TextFont is implemented. The actual choice of font depends on the interface mode of the applied solution (Taxi or interface 8.2).	This feature was not provided.	Using the new font (and the fonts based on it) allows storing fort size proportions for managed form elements in both interface modes.
Interface.	The MainSectionPicture configuration property is implemented. In this property, you can specify a picture that will be used for the main section (desktop) in the section panel.	The desktop had a fixed picture that could not be changed.	You can create a uniform graphic design for your applied solution, and you can create a desktop look that will be friendly to the primary audience of the solution.
Development tools.	A context tooltip can be displayed for the parameters of the function or procedure that is being edited in the module text editor. If the method has several syntax variants, you can select the required variant. Automatic parsing of procedure and function comments for displaying them in context tooltips is implemented. Procedure and function comments can be sorted for displaying in the context tooltip. The comment format is described in the documentation and complies with the applied solution development standards. Procedure and function templates that comply with this format are included into the distribution kit. The option that shows or hides the context tooltips is implemented in Designer. In the source code editor, you can open the context tooltip by pressing Ctrl+Shift+Spacebar.	In Designer, context tooltip for procedure and function parameters was not available. The context tooltip was only available for names of applied solution procedures and functions. Comments to procedures and functions were not used for getting information on their parameters.	Improved usability of writing source codes. The Syntax Assistant is not required for a quick reference on the order and types of procedure or function parameters.
Administration tools.	The documentation describes DBMS setup and maintenance features that can be used for 1C:Enterprise administration.	The documentation did not describe the administration tools that could be used without violating the license agreements.	You can use DBMS features that do not affect the structure of data used by 1C:Enterprise (the changes that are made do not affect the restructuring and are saved after the restructuring).
Managed forms.	For fields of check box and radio button types, the tumbler look is implemented (several adjacent buttons where the active value has a different color). For managed form fields of these types, the properties CheckBoxType and RadioButtonsType are implemented.	This feature was not provided.	New presentation features. Improved usability for touch interfaces.
Database configuration updates. Server clusters.	Infobase restructuring is required when a chart of characteristic types is modified or when a chart of accounts where a chart of characteristic types is used as an extra dimension,is modified. The following changes are implemented in the background restructuring procedure: You cannot create, edit, or delete exchange plan items if the exchange plan requires the restructuring. The restructuring is performed during the processing phase. You cannot create, edit, or delete chart of characteristic types items if the chart is specified as an extra dimension for a chart of accounts and this chart of accounts requires restructuring. In this case the restructuring of the chart of characteristic types is performed during the processing phase. The SetPredefinedDataUpdate() method cannot be called during the background restructuring.	Charts of characteristic types were restructured when they were modified. All charts of characteristic types and exchange plans were restructured when the changes were applied (during the background restructuring).	In the background database configuration update, the specifics of changing some data structures are taken into account. This prevents mismatching of object data.
System requirements.	Microsoft Windows Server 2012 (x86-64) is now supported.	Microsoft Windows Server 2012 (x86-64) was not supported.	New version of the Microsoft operating system is now supported.
Data display.	If the Interface compatibility mode configuration property is set to Taxi or Taxi.Version 8.2 enabled, the Help picture from the picture library corresponds to the Taxi interface.	The appearance of the Help picture in the picture library did not depend on the configuration property values.	The appearance of the Help button depends on the interface mode.

Table of contents

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Printing documents.	Changed behavior of print status forms in managed applications in thin and thick clients: In the Forms in tabs form opening mode, print status forms are opened in separate windows. The form is opened in a modal window so that users cannot interact with the interface during printing. The form cannot be closed by clicking the "X" button. The form cannot be resized.	The print status form had different behavior.	Improved usability of printing documents.
Linux.	The Primary Selection clipboard is now supported (data is copied to this clipboard when a text fragment is selected, without the need to press any keys). Copying to the Primary Selection clipboard is supported for the following form elements: Text box Text document field Formatted document field Spreadsheet document field Insertion from the Primary Selection clipboard (available by pressing the middle mouse button) is supported in text boxes.	This feature was not provided.	Improved usability of client application for users with Linux experience.
Managed forms. Functional options.	If a text box is linked to an attribute of complex type where all types except one are disabled by access rights or functional options, when user attempts to select a value in the text box, the choice value form is opened. This change is not implemented in 8.3.2 compatibility mode.	If a text box was linked to an attribute of complex type, when a user attempted to select a value in the text box, the type selection dialog box, was displayed even if the list of types contained a single value.	Users do not have to select from a single value in the type selection dialog box.
Automated testing.	On closing an application, if the log of user actions is being recorded at the moment, a request for saving the log is sent.	On closing the application, unsaved data from the log of user actions was lost.	Reduced chance of losing unsaved data from the log of user actions when the application window that initiated recording to the log of user actions is closed.
Web client.	During the startup of the web client, the check for a pop-up window blocker is only performed if the separate window interface is used and modal windows are enabled. The check for a pop-up window blocker is performed after the user authentication.	The check for a pop-up window blocker was always performed during the web client startup.	Users are not prompted to specify the pop-up blocker settings when it is not required.
Interface.	On interface mode change, the user is prompted to restart the client application.	Changing interface mode did not prompt to restart the client application.	The procedure of changing the interface mode became more user-friendly: the system now informs the user what they have to do to have the changes take effect.
Standard functions.	The following changes are implemented in the standard functions: Event log: The set of commands in the form command bar is changed, as well as the command presentations. The procedures for enabling and disabling the filter are revised. You can view log entry data by clicking the link in the corresponding log column. You can filter records by date and time. Find references to object: You can search for references to a reference that is found (from the context menu). Manage full-text search: The form is revised. Enabling or disabling full-text search is performed without opening additional forms. Post documents: The form is revised. Active users: You can open the event log filtered by user by clicking a hyperlink in the User column.	Standard function dialog boxes were less user-friendly.	Improved usability of standard functions.
Web client.	The documentation includes recommendations for choosing a web browser for low-performance computers.	The documentation did not include recommendations for choosing a web browser.	Recommendations for choosing a web browser are available.
Web client.	In Microsoft Internet Explorer web browser, notification windows do not fade out of view when they are closed automatically.	In Microsoft Internet Explorer web browser, notification windows faded out of view when they were closed automatically.	Improved performance of notification windows in Microsoft Internet Explorer web browser.

Table of contents

Optimization

Functionality	After	Before	Result of changes
DBMS operations. Accumulation registers. Queries.	Optimized performance of accumulation register virtual tables when obtaining totals with a filter that does not include all dimensions.	Insufficient performance of accumulation register virtual tables when obtaining totals with a filter that did not include all dimensions.	Performance of accumulation register virtual tables is increased.
Server clusters.	Creation of new sessions is optimized.	Creating of new sessions was performed inefficiently.	Optimized performance when establishing connections to the 1C:Enterprise server in the following cases: Simultaneous connections from a large number of client applications. Connection of a new client application to a cluster that already runs a large number of sessions.
Information registers.	Improved performance of independent, non-periodic information registers that have more than 1 dimension. This change is not implemented in 8.3.2 compatibility mode.	Insufficient register performance.	Increased speed of writing to a register, especially when a large number of users are working.
Applied objects.	Optimized selections from catalogs and charts of characteristic types for certain scenarios.	In certain scenarios performance of selections from catalogs and charts of characteristic types was inefficient.	Increased performance of selections from catalogs and charts of characteristic types in certain scenarios.
Dynamic lists.	Improved dynamic list performance in client/server mode when a large number of users are working.	In certain scenarios dynamic list performance was insufficient.	Improved dynamic list performance in certain scenarios.
Server clusters.	Optimized processing of session data for some scenarios.	In some scenarios processing of session data was inefficient.	Improved performance and scalability of 1C:Enterprise servers.
Accumulation registers.	Optimized execution of queries to turnovers registers with a large number of dimensions that include aggregates (for some scenarios). This change is not implemented in 8.3.2 compatibility mode.	In some cases execution of queries to turnovers registers with a large number of dimensions that included aggregates was inefficient.	You can use aggregate functions in more scenarios than before.
DBMS operations.	In order to optimize some queries to IBM DB2 DMBS, the recommendation to run the db2set DB2_OVERRIDE_BPF=5000 command and then restart the DBMS is included into the documentation. Methods of detecting situations when the optimization is required are also described in the documentation.	Some queries to IBM DB2 DBMS were performed inefficiently.	Optimized performance during the execution of some types of IBM DB2 DBMS queries.
Information registers.	For periodic information registers that are subordinate to recorders, the Active field is listed in the following indexes: By period By dimensions By dimension The Active field is the last one in these indexes. After changing the compatibility mode, full infobase restructuring must be performed for rebuilding indexes. This change is not implemented in 8.3.2 compatibility mode.	The Active field was not included in the list of indexes of periodic information registers subordinate to recorders.	Improved performance when retrieving the first and the last slices.
Server clusters.	1C:Enterprise server is optimized to reduce memory usage and fragmentation.	In some scenarios, 1C:Enterprise server used memory inefficiently. This led to memory fragmentation and increased memory consumption.	Reduced memory consumption of 1C:Enterprise server, and lower memory fragmentation. This allows to reduce the number of planned 1C:Enterprise server restarts and improves the system stability.
DBMS operations.	Indexes of attributes with additional ordering include deletion marks and all fields that are indexed with additional ordering. This data is added to the end of the index.	Indexes of attributes with additional ordering did not include deletion marks and all fields that were indexed with additional ordering.	Improved performance of dynamic lists filtered by multiple attributes (including the deletion mark).
Managed forms.	Optimized performance of displaying managed forms after server calls (both explicit and implicit ones) that change the form appearance.	Forms were not displayed fast enough when their appearance was changed from 1C:Enterprise script.	Optimized performance of displaying forms, for example, when the displayed title of a form element is modified.
Common attributes / Data separation.	Once the version 8.3.2 compatibility mode is disabled, optimization is performed on the structure that stores data on the table separators connected to objects included in the separator contents. When the version 8.3.2 compatibility mode is enabled, the reverse restructuring of the database tables is performed.	The structure that stored separator data was not optimal.	Improved performance due to the changes in the structure that stores separator data.
Server clusters.	In server cluster, the algorithm for balancing the working process load is optimized. The following parameters are used in addition to parameters used in the previous versions to define the available server performance: size of CPU queue, current processor load, and number of CPU cores. Values used for defining the available server performance are recorded to the TXT property of the CLSTR event in the technological log. To obtain performance parameters, the user on whose behalf the 1C:Enterprise server is running must be included in the Performance Log Users group.	In the server cluster, the algorithm for balancing the working process load took less number of parameters into account.	Improved reactivity of the load balancing algorithm. The algorithm defines overloaded CPUs and stops sending new tasks to them.
Managed forms.	Optimized performance of opening managed forms with multiline text boxes that contain a large number of line breaks.	Performance of opening forms with multiline text boxes containing a large number of line breaks was not high enough.	Forms with multiline text boxes that contain a large number of line breaks are opened faster.

Table of contents

Changes that affect system behavior

Functionality	After	Before	Result of changes
Software licensing.	Licenses for basic configurations are available on Linux.	Basic version licenses for Linux were unavailable.	You can run basic 1C:Enterprise configuration versions on Linux.
Applied objects.	Infobase object autonumbering logic is revised. The check for number or code uniqueness (including automatically generated codes and numbers) is always performed while the object is being written. The message informing the user that a number or code is not unique now specifies the value of the non-unique number or code. Numbers or codes that are no longer used are never re-assigned automatically, even when the desired prefix is not specified explicitly. In the event when the desired prefix is not specified explicitly, the platform forms a number or code as follows: it selects the greatest of the prefixes that match the specified pattern and then adds the next subsequent number (prefixes are compared according to their alphabetical order, for example, B is greater than A).	The uniqueness check was not performed for automatically generated numbers or codes while the object was being written. The message informing the user that a number or code was not unique did not include the value of the non-unique number or code. Numbers or codes that were no longer used might be re-assigned automatically in the event when the desired prefix was not specified explicitly–the platform might assign a code that was used before when its prefix matched the specified pattern and the prefix was not the greatest one among those matching the pattern (prefixes are compared according to their alphabetical order, for example, B is greater than A).	Increased stability and reliability of infobase object autonumbering. Messages informing the user that a number or code is not unique now contain more information. The autonumbering is more logical: numbers or codes are always issued in the ascending order.
Applied objects.	If a text value presentation cannot be calculated during debugging, the string Error getting value presentation is returned as a text presentation.	If a text value presentation could not be calculated, Designer might stop responding.	Improved system stability during debugging.
Managed forms.	Visibility of the command for switching to the calculation register (in a recorder form) is set to True by default. This change is not implemented in 8.3.2 compatibility mode.	Visibility of the command for switching to the calculation register (in a recorder form) was set to False by default.	Default visibility of commands for switching to registers is the same for all registers.
Managed forms.	When attributes of Number type that have minimum or maximum values set are cleared interactively, the attribute values after clearing cannot exceed the specified limits. This change is not implemented in 8.3.2 compatibility mode.	When attributes of Number type were cleared interactively, their minimum and maximum values were ignored.	Users cannot enter data that does not meet the conditions specified by the developer.
Applied objects.	When a spreadsheet document is saved to a .docx file, image border styles are preserved. This change is not implemented in 8.3.2 compatibility mode.	When a spreadsheet document was saved to a .docx file, images always had borders.	More accurate export of spreadsheet document styles to .docx format.
Applied objects.	When a spreadsheet document is saved to a .docx file the following spreadsheet document print options are preserved: paper size page orientation scale pagination margins headers and footers repeating rows displaying headers and footers on the first page This change is not implemented in 8.3.2 compatibility mode.	Print options were not preserved when a spreadsheet document was saved to a .docx file.	Improved usability of spreadsheet documents saved in .docx format.
Data composition system.	When a user field is added to data composition system settings and the source of available settings is not specified, the file name is generated using the language of the current script variant. This change is not implemented in 8.2.16 compatibility mode.	When a user field was added to data composition system settings and the source of available settings was not specified, the file name was generated in English.	The data composition system behavior is uniform with behavior of similar platform features.
File operations.	The look and behavior of the file selection dialog box (including the FileDialog object) in Windows Vista and later Windows versions complies with the standards of these operating systems. In Windows XP and earlier and in the web client the look of the dialog box is not changed.	In Windows Vista and later, an outdated file selection dialog box was used.	The look of the file selection dialog box corresponds to the operating system being used.
File operations.	If both Directory and FullFileName are specified for a FileDialog object, the dialog box is opened in the specified directory and with the specified file name.	If both Directory and FullFileName were specified for a FileDialog object, the dialog box ignored the specified directory and used the directory that was obtained from the full file name.	Improved usability of the file choice dialog.
Automated testing.	Wildcard support implemented for the InputText() method of the TestedFormField object.	The automated testing mechanism did not support wildcards in text input fields.	Extended functionality of the automated testing system.
Dumping/loading configurations to files.	When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName. Configurations dumped using earlier platform versions cannot be loaded.	When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName.	Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.	When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName. Configurations dumped using earlier platform versions cannot be loaded.	When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName.	Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.	When dumping a configuration to XML files, names of standard commands of managed forms follow this convention: Form.StandardCommand.CommandName. Configurations dumped using earlier platform versions cannot be loaded.	When dumping a configuration to XML files, names of standard commands followed this convention: FormStdCommand.CommandName.	Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.	When dumping a configuration to XML files, names of managed form commands follow this convention: Form.Command.FormCommandName. Configurations dumped earlier will not be loaded.	When dumping a configuration to XML files, names of managed form commands followed this convention: FormCommand.FormCommandName.	Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.	When dumping a configuration to XML files, names of standard commands of managed form elements follow this convention: Form.Item.ElementName.StandardCommand.StandardCommandName. Configurations dumped earlier will not be loaded.	When dumping a configuration to XML files, the standard commands of managed form elements followed this convention: Form<ElementType>.ElementName.StandardCommandName.	Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.	When a configuration is dumped to files: References to missing configuration objects are dumped as text presentations of identifiers of missing configuration objects. Properties of the ManagedForm element of a managed form that make sense only in the 1C:Enterprise mode are not dumped. For attributes and elements of managed forms, the internal identifiers required for saving their settings are dumped. For elements of business process flowcharts, element identifiers are dumped.	When a configuration was dumped to files: References to missing configuration objects were ignored. Properties of the ManagedForm element of a managed form that made sense only in the 1C:Enterprise mode were dumped. For attributes and elements of managed forms, the internal identifiers required for saving their settings were not dumped. For elements of business process flowcharts, element identifiers were not dumped.	In dumping/loading of configurations, the following improvements are implemented: User settings are preserved when a configuration is dumped and then loaded. The accuracy of configuration comparison (after a configuration is dumped and then loaded) is increased.
Managed forms.	When Esc is pressed in a text box (except multiline text boxes), the following actions are performed: If the initial text box content was modified in any way, the text box reverts to the initial content. If the initial content was not modified, the text box does not process pressing the Esc key and passes the processing to the form.	Pressing Esc was always processed by the form. The text box did not perform any actions if Esc was pressed while the text was being edited.	You can cancel editing a value in a text box.
Managed locks.	The maximum number of managed locks is 100 000 (exceeding this limit locks the entire lock space).	The maximum number of managed locks was 20 000 (exceeding this limit locked the entire lock space).	Improved user experience when using transactions with a large number of locks (more than 20 000) in a single lock space.
Information registers. Data exchange.	When a set of information register records is passed to the SelectChanges() method as a filter value, the system behavior depends on the compatibility mode: In version 8.2.16 or earlier compatibility mode, the selection includes data that does not match the filter criteria defined by the record set; In version 8.3.1 or later compatibility mode (or if the compatibility mode is not used), the selection only contains data that exactly matches the filter criteria.	When a set of information register records was passed to the SelectChanges() method as a filter value, the system behavior did not depend on the compatibility mode. In version 8.2.16 or earlier, the selection included data that did not match the filter criteria defined by the record set In version 8.3.1 or later, the selection only contained data that exactly matched the filter criteria.	Improved compatibility with previous platform versions.
Dynamic lists.	In the data composition system and query wizard, syntax units enclosed in braces {} do not lead to errors in dynamic lists.	In the data composition system and query wizard, syntax units enclosed in braces led to errors in dynamic lists in some cases.	Better stability of dynamic list.
Cryptography.	The value of the CryptoModuleName parameter in the CryptoManager object wizard is case insensitive.	The value of the CryptoModuleName parameter in the CryptoManager object wizard was case sensitive.	The system behavior complies with common standards.
Managed forms. Ordinary forms.	In managed and ordinary forms, if the second parameter (FormElement) of the ChooseFromMenu() method is a managed form table, a managed form, a table box, or an ordinary form, the menu that is opened using this method is displayed in the following location: For a table box or a managed form table, the menu is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table if the current cell cannot be determined. For a form, the menu is displayed in the upper left corner. This change is not implemented in 8.3.2 compatibility mode.	If the second parameter (FormElement) of the ChooseFromMenu() method was a managed form table, a managed form, a table box, or an ordinary form, the menu was displayed in the following location: For a table box or a managed form table, the menu was displayed in the lower left corner of the element passed as the parameter value. For a form, the menu was displayed in the lower left corner of the current form element. If the current form element could not be determined, the menu was displayed in the lower left corner of the form. In the web client, the menu was displayed in the center of the screen.	Uniform behavior when the system opens similar menus (e.g. context menu in a managed form table) or the applied solution opens such menus (using the ChooseFromMenu() method).
Managed forms. Ordinary forms.	In managed and ordinary forms, if the second parameter (FormElement) of the ChooseFromList() method is a managed form table, a managed form, a table box, or an ordinary form, the list that is opened using this method is displayed in the following location: For a table box or a managed form table, the list is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table, if the current cell cannot be determined. For a form, the list is displayed in the upper left corner. This change is not implemented in 8.3.2 compatibility mode.	If the second parameter (FormElement) of the ChooseFromList() method was a managed form table, a managed form, a table box, or an ordinary form, the list was opened in the following way: For a table box or a managed form table, the list was displayed in the lower left corner of the element passed as the parameter value. For a form, the list was displayed in the lower left corner of the current form element. If the current form element could not be determined, the list was displayed in the lower left corner of the form. In the web client, the list was displayed according to form settings because a system form was used to display it.	Uniform behavior when executing similar actions (the ChooseFromMenu() and ChooseFromList() methods).
Development tools.	You can search and replace in the ChoiceParameters property of configuration objects. The search and replace algorithm is modified for the ChoiceList and ChoiceParameterLinks configuration objects. The search and replace are performed: For the ChoiceParameters property: in the Name and the Value columns (including fixed array elements). The search is performed on values of String type. For the ChoiceList property: in the Presentation column and in the Value column if the value has the String type. For the ChoiceParameterLinks property: in the Name column. Every time the search string is found, the search/replace procedure is paused and a message prompting to resume the procedure is displayed. Search in the LinkByType property of configuration objects is no longer supported.	Search and replace in the ChoiceParameterLinks property of configuration objects was performed only in the Name column. Search and replace in the ChoiceList property of configuration objects was performed only in the Presentation column. Search and replace was not performed in the ChoiceParameters property of configuration objects. Search could be performed in the LinkByType property of configuration objects.	The search and replace operations in configuration object properties are now uniform to similar operations in texts.
Development tools.	The presentation of the ChoiceParameters property of configuration objects in the object properties editing window is changed. If a value of any property element is a fixed array, presentations of array values are used. The presentation of the ChoiceList property of configuration objects in the object properties window is changed. A presentation now consists of both list item values and their presentations (if the presentations are specified).	If an element of a ChoiceParameters property was a fixed array, its presentation was a FixedArray string. For the ChoiceList property of configuration objects, the presentation in the object properties window was generated from the list item values only.	Improved usability of ChoiceParameters and ChoiceList properties in Designer.
Managed forms.	Improved look and behavior of drop-down lists in text box fields that can be edited and contain data of reference type, enumerations, or system enumerations: If a field contains data of reference type or an enumeration, the field includes the choice button, and the characters typed in the field do not match any choice list values, the Click show all to select item message is displayed in the list. If the drop-down list is displayed and a value is selected in it, pressing Tab, Shift+Tab, or Enter selects the current value from the list. Clicking another form element does not select the current value; the list is closed instead (same effect as pressing Esc). The selection is not moved to the form element that was clicked. If the drop-down list is not displayed and the characters typed in the field uniquely identify a choice list value, pressing Tab, Shift+Tab, or Enter selects this value. Clicking another form element also selects this value. If the drop-down list is not displayed and the characters typed in the field match multiple choice list values, pressing Tab, Shift+Tab, or Enter opens the drop-down list. Clicking another form element also opens the drop-down list.	The drop-down list had a different look and behavior.	Improved usability of text box fields that contain data of reference type, enumerations, or system enumerations.
Accumulation registers.	You can enable the aggregates mode for any turnovers accumulation register, regardless of the actual presence of aggregates in metadata. In the client/server mode you can create new optimal aggregates (and remove outdated ones) when aggregates are being rebuilt in 1C:Enterprise mode. This change is not implemented in 8.3.2 compatibility mode.	Developers had to add aggregates in Designer to keep the list of optimal aggregates up to date.	Simplified support of optimal aggregate list: you only have to rebuild aggregates on regular basis.
Managed forms.	In text boxes containing data of reference type, only the color of the text presentation of the value is changed on element activation.	In text boxes containing data of reference type, the color of the entire field changed on element activation.	Better text box usability. A tooltip can be displayed in a text box linked to data of reference type if the text box is first in the tab order of the form.
Development tools. Configuration repositories.	You can perform quick comparison of selected configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. Selective comparison is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, exchange plan content objects, styles, desktop workspaces, maps, forms, online help pages, predefined items, command interface fragments, and role rights. To run the selective comparison command, right-click anywhere in any of the repository dialog boxes or in the compare configurations window, and then click Perform selective comparison with the configuration object. Selective comparison of configuration objects is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.	This feature was not provided. When comparison was initiated for a specific object, full comparison of two configurations was performed. The focus in the comparison window was set to that object.	Improved usability of configuration repository. Optimized comparison procedure when it is performed for a single configuration object.
DBMS operations.	Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later is now available. All of the required settings are specified automatically by the installation program of the patched PostgreSQL version unless a cluster created by the standard PostgreSQL version is found on the computer.	Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later was not available.	1C:Enterprise supports clusters created by the following versions of PostgreSQL DBMS: PostgreSQL 8.1.5-X.1C - 9.1.2-1.1C PostgreSQL 9.2.1-2.1C Standard version of PostgreSQL provided that the cluster locale is identical to the infobase locale. You can upgrade or downgrade 1C:Enteprise without upgrading or downgrading the associated PostgreSQL instance; this does not require any manual configuration. Note that once you migrate to a new PostgreSQL version, you cannot use 1C:Enterprise version 8.3.2 or earlier. This only applies to new infobases that were created using PostgreSQL 9.2.1-2.1C. Do not create infobases using PostgreSQL 9.2.1-2.1C if you are planning to access them from earlier platform versions.
Managed forms.	If the ChoiceDataGetProcessing event handler of the enumeration manager returns an empty list and the formal parameter StandardProcessing returned by this handler is set to False, the returned list is used for filling the choice list. This change is not implemented in 8.3.2 compatibility mode.	If the ChoiceDataGetProcessing event handler of the enumeration manager returned an empty list and the formal parameter StandardProcessing returned by this handler was set to False, the client application filled the choice list by all enumeration values.	The system behaves as expected when a developer decides to disable selection of enumeration values.
Standard functions.	In the default event log form, filter presentation is localized.	In the default event log form, filter presentation was always displayed with Russian names of event log columns.	The filter presentation is uniform with other platform features.
Configuration repositories.	Optimized the reference integrity check algorithm for configuration repository operations (storing and retrieving) on objects that are deleted from the repository and objects that reference to deleted ones. In some cases, it is not necessary to lock objects that contain references to objects being deleted during the deletion. The reference integrity check algorithm used when deleting objects from the repository is uniform with the reference integrity check algorithm used when deleting objects from a configuration that is not bound to a repository. This change is not implemented in 8.3.2 compatibility mode.	The reference integrity check algorithm for configuration repository operations was not optimized. The reference integrity check algorithm used when deleting objects from a repository was different from the reference integrity check algorithm used when deleting objects from a configuration that was not bound to a repository.	Eliminated problems that occurred when deleting objects from configurations because of the reference integrity check differences. Storing deleted objects to the configuration repository is optimized.
Managed forms.	In the managed mode of the thick client, if the In list editing mode is selected for a configuration object, calling the OpenValue() method or clicking the Open button in the text input area opens the regular list form, provided that the following conditions are met: The In list editing mode is selected. A regular list form exists and it is selected as a default or additional one. Using regular forms in the managed application is allowed in this applied solution. The list or object managed form that is used as a default or additional one is missing. In all other cases, this opens the object form. This change is not implemented in 8.2.16 compatibility mode.	In the managed mode of the thick client, if the In list editing mode was selected, calling the OpenValue() method or clicking the Open button in the text input area opened the managed list form.	To display configuration objects that have the In list editing mode set, or for editing their elements, the system opens the regular list form. This behavior is more consistent than before.
Development tools.	The following changes are implemented in the configuration comparison feature: The parent node of predefined data elements is excluded from the comparison. Missing help data is considered identical to empty help data. Additional properties of the ManagedForm managed form element that make sense only in the 1C:Enterprise mode are excluded from the comparison.	When configurations were compared: The node to which predefined data items were subordinate was included into the comparison. Missing help data was considered different from empty help data. Additional properties of the ManagedForm managed form element that make sense only in the 1C:Enterprise mode were included into the comparison.	The configuration comparison is perfomed as expected.
Managed forms.	When a choice list is generated for form fields linked to data of EnumRef type, it is based on the choice parameters and choice parameter links of the form element. This change is not implemented in 8.3.2 compatibility mode.	When a choice list was generated for form fields linked to data of EnumRef type, the choice parameters and choice parameter links were not taken into account.	The choice list generation for enumerations is uniform with other similar system features.
Internet-enabled functionality.	For the InternetMailProfile object, the SMTPAuthentication property (which is obsolete) is set to SMTPAuthenticationMode.Default. This change is not implemented in version 8.2.16 compatibility mode.	For the InternetMailProfile object, the obsolete property SMTPAuthentication was set to SMTPAuthenticationMode.None.	The default settings of the authentication method is the safest among those supported by the mail server.
Internet-enabled functionality.	If the SMTPSecureAuthenticationOnly property of the InternetMailProfile object is set to TRUE, authentication attempts are performed independently of other settings. User authentication on the SMTP server is not performed in the following scenarios: The SMTPUser property of the InternetMailProfile object is an empty string. The SMTPAuthentication property of the InternetMailProfile object is set to SMTPAuthenticationMode.None. The POP3BeforeSMTP property of the InternetMailProfile object is set to TRUE.	User authentication on the SMTP server was not performed if the name of the SMTP server user was not specified (the SMTPUser property of the InternetMailProfile object).	User authentication on the SMTP server can be performed using a POP3 server if the SMTPSecureAuthenticationOnly property is not set. The value of the SMTPUser property of InternetMailProfile object does not affect this behavior. At the same time, the authentication is not performed if the mail server does not support the secure authentication methods. When connecting to a mail server, you can exclude insecure authentication methods from the list of available ones.
Software licensing.	If a license acquisition dialog box appears at the start of the client application, the first page of the dialog box specifies which kind of license (server or client) the application requires. A hyperlink to 1C:Licensing center contact information is displayed on the license registration pages and on the page that appears when license activation is not successful. A dialog box that displays 1C:Licensing center contact information is added. When a user types a PIN code or a response from a licensing center operator in the license aсquisition dialog box, once they have completed a text field, the cursor moves to the next field automatically.	If a license acquisition dialog box appeared at the start of the client application, the first page of the dialog box did not specify which kind of license (server or client) was not found. The license registration pages and the page that appeared when license activation was not successful only contained information how to find 1C:Licensing center contacts in the printed documentation. When a user typed a PIN code or a response from a licensing center operator in the license aсquisition dialog box, the cursor did not move to the next field automatically.	Improved usability of license acquisition dialog box.
Spreadsheet documents. Web client.	The web client now supports text orientation in spreadsheet document cells.	The web client did not support text orientation in spreadsheet document cells.	Extended formatting capabilities for spreadsheet documents in the web client.
Server clusters.	When a cluster service is reassigned from one cluster manager to another, the service status is replicated to the new cluster manager and the service is shut down on the former cluster manager, which releases the resources used by the service. The status is replicated for the following services: object locks, numbering, and background restructuring. In the technological log, the <SRVC> event is implemented. It describes the following operations with cluster services: starting, stopping, and various alerts. Descriptions of operations being executed are generated in the Descr property. Each cluster manager stores its session data in a dedicated directory. You can choose how a working process is selected when a new connection is created: by available performance or by available memory. If the selection is performed by available memory, either the working process that currently maintains connections to the infobase is used, or the working process that is running on the server and has the maximum amount of available memory. In the cluster properties, the Load balancing mode property is implemented. For the IClusterInfo object, the LoadBalancingMode property is implemented. For starting a background job, the working process that maintains the session that initiated the background job is selected with the highest priority (this rule is ignored if the selection is performed by available memory). You can specify a priority for each assignment rule. If several identical assignment rules are found during assignment rule selection and all other conditions are equal, the rule with the highest priority is used. Assignment rules now have the Priority property. For the IAssignmentRule object, the Priority property is implemented. In the cluster mode of the server cluster administration utility (rac), the load-balancing-mode parameter is implemented for the create and update commands. Similar changes are implemented in the Java server administration API. When determining available working process performance, the CPU load of the working server and the number of threads in the execution queue are taken into account, in addition to other factors.	In some cases, used resources were not released after the reassignment of services. The status was not replicated for the following services: object locks, numbering, and background restructuring. In the technological log, there were no events that described operations with cluster services. Data belonging to all sessions was stored in a single directory, which could lead to access collisions. When a background job was created, the working process for handling the job was always selected by available performance. If several identical assignment rules were found during assignment rule selection, the rule that was applied could not always be determined unambiguously. When available working process performance was determined, the CPU load and the number of threads in the execution queue were not taken into account.	Increased fault tolerance of clusters. Improved quality and manageability of load balancing between cluster servers. A new setting ensures efficient memory usage when a cluster maintains a large number of infobases with a small number of sessions from each infobase.
Managed forms.	For unavailable groups, colors of the title and border (line) are changed.	For unavailable groups, the title and border (line) had different colors.	The look of unavailable groups is uniform with the look of other unavailable elements.
Applied objects. Common attributes / Data separation. Access rights. Data exchange. Mobile application.	Predefined data is available for configuration objects included in separator contents in the Independent and Shared mode. Predefined items can be linked to any data elements of matching type. The linking is optional. If data elements are not linked, the predefined data is considered empty. For configuration objects that can contain predefined data, the PredefinedDataName property is implemented. Support of predefined data items that refer to deleted predefined items is implemented. Identical references to predefined items are never generated, even for objects included in separator contents in the Independent mode, and even for items that belong to different areas. The GetPredefinedItemName() method is declared deprecated is only supported for compatibility purposes. Predefined data is registered in exchange plans like any other data. You can manage creation and update of predefined data in the infobase using the new configuration object property PredefinedDataUpdate and the new methods GetUpdatingPredefinedData() and SetPredefinedDataUpdate(). The global context method InitializePredefinedData() is implemented. Using this method, you can create data objects for predefined items that are not linked to any data (in the current data area). Access rights and restrictions are specified simultaneously for the Predefined and PredefinedDataName fields. These features are also implemented for the mobile platform. The new access rights InteractiveDeletePredefinedData, InteractiveSetDeletionMarkPredefinedData, InteractiveClearDeletionMarkPredefinedData, and InteractiveDeleteMarkedPredefinedData are implemented. They specify whether editing of predefined data is allowed. Restrictions for editing predefined data in charts of accounts and charts of calculation types are eliminated. Predefined data can be marked for deletion, and it can be completely deleted. A chart of accounts must be included into the contents of all separators that contain all extra dimensions used in the chart. The infobase restructuring process is modified. This change is not implemented in 8.3.2 compatibility mode.	Predefined data was not available for configuration objects included in separator contents in the Independent and Shared mode. Predefined data could not be linked to any existing data object. Each predefined item had identical references in all data areas. During data exchange in a distributed infobase, predefined data was replicated only together with applied solution configuration changes. Creation and update of predefined data were not available.	You can use predefined data in all separation modes. Predefined data management is more flexible than before.
Interface.	In the help topics, links to external resources are opened in the default web browser of the operating system.	In the help topics, links to external resources were opened in the built-in web browser of 1C:Enterprise.	Improved usability of viewing the resources that are opened by clicking links in the help topics.
Interface.	For new users, the interface mode is set to Forms in tabs, provided that the platform version compatibility mode is not used and the interface compatibility mode is set to Version82 or Version82TaxiAllowed.	For new users, the interface mode was set to Forms in separate windows.	The Forms in tabs interface is the default option for new users. This interface mode provides better usability.
Interface.	For a text box in a managed form table, the drop-down list is always opened at the start of editing.	For a text box in a managed form table, the drop-down list was opened at the start of editing only if the editing was started using the mouse.	Quick access to the drop-down list is implemented for text boxes located in managed form tables.
Common attributes / Data separation. 1C:Enterprise script.	After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state matches the state that the data area had when it was accessed for the first time. In particular: Tables of enumerations are not modified. If the version 8.3.2 or later compatibility mode is set, predefined data values revert to the values specified in Designer or to the default values. If the compatibility mode is disabled, predefined data items will be created on the first attempt to access them. In the exchange plans, the values of ThisNode element attributes revert to the default values. Values of nonseparated constants revert to the default values, while values of separated constants are deleted.	After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state did not match the state that the data area had when it was first accessed: Tables of enumerations were removed. For nonseparated objects, the predefined data values were saved. In the exchange plans, the values of ThisNode element attributes were saved. Constant values were preserved.	After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the state of the data area now reflects its initial state much better than it did in the previous platform versions.
Application appearance.	New splash screens are implemented for Designer, client application, Autorun program, and the installation program. The splash screen size (and the size of the applied solution splash screen template) is 600 x 255 pixels.	Splash screens that were used for various parts of the system had different looks. The size of the applied solution splash screen template was 305 x 110 pixels.	The new splash screens better fit the new user unterface.
Managed forms.	When a value is entered or selected in a text box, it is converted to the text box value type, and then the value presentation is displayed in the text box. This change is not implemented in 8.3.2 compatibility mode.	When a value was entered or selected in a text box, the resulting text displayed in the box might not match the entered or selected value.	The system behaves as expected. Eliminated incorrect system behavior.
Client application.	The message that is displayed before updating a client application using an insecure connection is clarified.	The message was not clear enough.	The message describes the situation more clearly.

Table of contents

Changes that require modification of configuration and administrative settings

Table of contents

Renamed objects

Object	The old name	The new name
The name of calculating register recalculation manager type is changed. This change is not implemented in version 8.3.2 compatibility mode.	CalculationRegisterRecalcs.<Calculation register name>	RecalculationManager.<Calculation register name>
English names of the following script objects are changed: External data source table record (ExternalDataSourceTableRecord); External data source record set (ExternalDataSourceTableRecordSet). This change is not implemented in 8.3.2 compatibility mode.	ExternalDataSourceRecord; ExternalDataSourceRecordSet.	ExternalDataSourceTableRecord; ExternalDataSourceTableRecordSet.
For turnovers accumulation register managers and for accounting register managers, the methods for setting and getting the totals period are renamed. For compatibility purposes, the previous names are supported.	GetTotalsPeriod() SetTotalsPeriod()	GetMaxTotalsPeriod() SetMaxTotalsPeriod()
For objects that describe form elements being tested, the name of the property that contains the element title is changed.	Title	TitleText
The names of the UsualGroupRepresentation system enumeration items are changed. For compatibility purposes, the previous names are supported.	Line Margin GroupBox	WeakSeparation NormalSeparation StrongSeparation
The names of the methods for getting and setting the client application window caption are changed. For compatibility purposes, the previous names are supported.	GetApplicationCaption SetApplicationCaption	GetClientApplicationCaption SetClientApplicationCaption
The name of the configuration property that describes the desktop command interface is changed.	DesktopCommandInterface	MainSectionCommandInterface
The name of configuration property that describes the desktop workspace (the starting page) is changed.	DesktopWorkingArea	StartPageWorkingArea
The names of settings that store start page (desktop) parameters. In version 8.3.2 compatibility mode, use the old names. When the compatibility mode is changed, the saved settings keys are changed as well.	Common/DesktopSettings Desktop/NavigationPanel/CommandInterfaceSettings Desktop/ActionsPanel/CommandInterfaceSettings	Common/StartPageSettings MainSection/NavigationPanel/CommandInterfaceSettings MainSection/ActionsPanel/CommandInterfaceSettings.
The name of the type that describes the object containing start page (desktop) settings is changed. For compatibility purposes, the previous name is supported.	DesktopSettings	StartPageSettings
The Russian name of the TestedFormField object method, which ends the editing of the current area, is changed.	ЗавершитьРедактированиеТекущейОбласти()	ЗакончитьРедактированиеТекущейОбласти()

Table of contents

Mobile platform

Functionality	After	Before	Result of changes
System requirements.	For iOs-based devices, the iOS version 4.x is not supported. The minimum iOS version is 5.1. For Android-based devices, the minimum RAM size is 256 MB.	iOS version 4.x was supported. Android-based devices required 100 MB of RAM to run 1C:Enterprise.	System requirements for the mobile platform are revised.
Managed forms.	In the mobile application, the extended tooltop can be used, except the Balloon option.	Extended tooltips were not available in mobile applications.	On the mobile platform, you can create tooltips for form elements using a variety of tooltip design options.
Common objects.	Geolocation functions and multimedia tools (photos, audio- and videorecording) provided by mobile devices are available in mobile applications. The following geolocation functions are implemented: GeographicCoordinates, LocationData, LocationProviderInformation, LocationTools, AddressData. The LocationTools global context property is implemented. Global context methods GetAddressByLocation(), GetLocationByAddress(), and ShowOnMap() are implemented. The GeographicalSchemaCoordinates type is renamed to GeographicCoordinatesp; it is used in geolocation functions. The GeographicalSchemaCoordinates type name is supported for compatibility purposes. The MultimediaData and MultimediaTools objects are implemented to support processing multimedia features. The MultimediaTools global context property is implemented.	These features were not provided.	Geolocation and multimedia functions of mobile device perating systems are now available in the mobile platform. You can add features for defining the current location, making photos of incoming items, and so on.
Development tools.	The configuration check verifies whether the conifiguration language code meets the ISO standard. It is recommended that you use ISO-compliant language codes.	The language codes were not checked for compliance with ISO standard.	Reduced chance of incorrect mobile platform language selection based on the mobile device language.
1C:Enterprise script.	Common modules that reuse returned values are now supported	This feature was not provided.	On the mobile platform, you can optimize getting the same data multiple times during a single session or a single server call.
Predefined data.	While a mobile application is being updated, metadata objects are compared by their internal identifiers. When a mobile application is updated to version 8.3.3, the corresponding restructuring is performed.	While a mobile application was being updated, metadata objects were compared by their names.	You can rename metadata objects while preserving the object data.
Data display.	The mobile platform picture format is replaced by the format that supports several screen resolutions of mobile devices.	All mobile platform pictures had the same resolution.	The sizes of system pictures displayed on mobile device screens depend on the screen resolutions.
Backups.	When an infobase is created on iOS-based devices, the directory containing the application data is marked as excluded from the backup. When the infobase data is modified (object form extension data and register data is recorded), the directory with application data is marked for backup and the backup is initiated using the system tools.	On iOS-based devices, the infobase directory was marked for backup since it was created.	The application behavior meets the requirements of the Apple company to user data backup.
Spreadsheet documents.	On the mobile platform, resolved issues with displaying spreadsheet documents that have a large number of rows and columns.	In some cases displaying a spreadsheet document with a large number of rows and columns on the mobile platform led to an unexpected shutdown.	Improved mobile platform stability when processing large spreadsheet documents.
Internet-enabled functionality.	For the mobile platform, the HTML-document field is implemented. The HTML-document field has the following specifics: The Document and Output properties are not supported. The OnClick event is fired only during the attempt to switch to a new page. At this time, all properties of the EventData parameter except Href contain the UNDEFINED value. The Href property contains the address of the new page.	The HTML-document field was not supported on the mobile platform.	In mobile applications, displaying HTML pages in forms is implemented. For example, you can create a manual for your configuration.
Interface.	On mobile devices with Android OS, you can change the order of items in the list of applications.	On mobile devices with Android OS, changing the order of items in the list of applications was not available.	Improved usability of the list of applications. User can arrange applications in any order.
Data composition system.	Processing data composition system details on the mobile platform is implemented (this includes opening values and remote processing of the details). For mobile platform, the DataCompositionDetailsID object is implemented.	On the mobile platform, reports that contained data composition system details could not be opened.	On the mobile platform, reports can be generated using the data composition system. Report that contains details can be opened on the mobile platform.
Mobile application development.	In the Mobile application creation wizard data processor, you can specify a key for Google Maps. You can also specify a logo for screen resolution 950×1136 (iPhone 5 screen) in this data processor.	These features were not provided.	You can use the Mobile application creation wizard data processor for creating mobile applications that utilize new mobile platform features (geocoding support). Support of iOS-based devices was improved as well.
Internet-enabled functionality.	For the objects HTTPConnection, WSProxy, WSDefinitions, and InternetMailProfile, and for the CreateWSProxy() method, the option to set a timeout for interaction with a network resource is implemented. User names and passwords that are passed to WSProxy, WSDefinitions, and HTTPConnection objects can contain special characters, except ":". You can encode (the EncodeString() method) and decode (the DecodeString() method) custom text strings for using them in URLs. Encoding is performed in compliance with the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt). You can process HTTP request headers and return codes, as well as get and set request bodies as strings or binary data. The HTTPRequest and HTTPResponse objects are implemented. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	On the mobile plaform, the following features are available: Setting timeouts for interaction with network resources Using characters that do not belong to the ASCII character set in user names and passwords Generating URLs and getting values from them according to the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt) when custom text is added to a URL Generating HTTP requests, processing responses, and interacting with REST services from 1C:Enterprise script
1C:Enterprise script.	The CurrentUniversalDateInMilliseconds() function is implemented. It gets the number of milliseconds that passed since January 1, year 0001, 0:00:00 UTC. The attempt to assign a value to a fixed structure item raises an exception. In value tables, serialization of index descriptions is implemented. The index contents are not serialized but restored during deserialization. The hash function value can be calculated based on MD5 and CRC32 algorithms using the DataHashing object. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	On the mobile platform, you can do the following: Measure time intervals more precisely. For example, this can be handy for getting the duration of a specific action. Use fixed structures in a similar way to other fixed collections. Restore the value table state in more detail during its deserialization. Quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools.
Managed forms.	When specifying values of managed form fields or tables, you can specify data stored in a specific row of a form attribute that is a table (but not a dynamic list). Data belonging to dynamic lists that are currently not displayed on a managed form is not read during the operations that involve the managed form. For attributes of String type that have fixed length and are located in managed form tables, table boxes, or spreadsheet documents, the appearance of the mark that indicates that the field must be filled is modified. The following style fonts are implemented: SmallTextFont, LargeTextFont, and ExtraLargeTextFont. For the Font type, the Scale property is implemented. It defines increase or decrease of the font relative to the initial size. For groups of "usual group" or "page" type, you can set the background color of form group extensions using the BackColor property. The URLProcessing handler is implemented for the Label form field, Decoration form field of Label type, and managed form. The handler is called when a user clicks a formatted string with a hyperlink in a field. Extended appearance customization options for form fields of label type and decorations of label type. In usual groups with limited width, the size of managed form buttons can vary depending on the width, which is similar to the behavior of other form items in a group with limited width. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	On the mobile platform, you can do the following: Edit data stored in specific rows of form table data in separate fields. Get fast access to managed forms with dynamic lists located on different pages. Ensure that the behavior of the mark that indicates that the field must be filled is the same for all attribute types. Specify font size in a form relative to the form base font, without using absolute font size values. Improve form usability by highlighting group colors. Create a handler for each hyperlink represented as a formatted string. Use more appearance customization options in managed forms. When the size of a usual group is limited, the algorithm used for resizing group items is the same for all item types.
Applied objects.	User presentations are implemented for database objects of the following types: Catalog, Document, and ExchangePlan. In document journals, the attribute containing the document number has fixed length if all documents included in the journal have the number field of String type with fixed length. Otherwise, the journal attribute has variable length. A value obtained from an unfilled table attribute, value tree, or tabular section is equal to the default value of the column attribute type, with the type qualifier taken into account. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	On the mobile platform, you can do the following: Get nonstandard data presentations in various scenarios. Get document numbers in a uniform way, regardless of the method used to obtain the document numbers: either from the document itself or from the document journal. Generate default values in the same way as they are generated on the PC-based platform.
Command interface.	In the information register record form, if the OnlyInActions property of the Copy command has the Auto value, the system behavior is changed. This value now means that the command is located in the More (or All actions) menu only. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	On the mobile platform, you can specify the same default location for the Copy command in information register records set forms and in the item forms.
Charts.	New types of charts are implemented: Funnel 3D funnel Normalized funnel 3D normalized funnel The antialiasing mode is implemented for charts. You can connect series of charts to each other. The semitransparency mode is implemented for charts. The Indicator property is implemented for the tape graph chart. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	Extended chart features on the mobile platform.
Information registers.	For periodic information registers, the totals for getting first and last slices are implemented. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	On the mobile platform, you can get first and last slices, which represent data as of the last (current) moment in time, much faster.
Spreadsheet documents.	If a fixed area is larger than the displayed area, the spreadsheet document does not use the fixation. The algorithm for horisontal cell placement in different rows is modified. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	On the mobile platform you can: Improve usability of reports that contain areas with left or top fixation. Improve usability of spreadsheet documents.
XML and XDTO support.	If a message to a user contains characters incompatible with XML format (in the thick or thin client), the error XML text contains invalid characters in X position is generated. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	The processing of characters that are incompatible with XML format on the mobile platform is uniform with processing them on the PC-based platform.
Data display.	Formatted strings are available (the FormattedString type). You can use a formatted string as: Data for the "label field" form items Title for form items of decoration type MessageText parameter of the DoMessageBox() method QueryText parameter of the DoQueryBox() method	This feature was not provided on the mobile platform.	On the mobile platform, the text presentation capabilities are improved.
XML and XDTO support.	During the import of XSD schema, if the target namespace definition is missing in the schema, a diagnostic message is displayed.	During the import of XSD schema, when any problems occurred while loading the XSD schema, a diagnostic message was not displayed.	Improved diagnostics during XSD schema import.
Managed forms. Command interface. Common objects.	You can specify the Arbitrary type for a subordinate attribute of a managed form attribute (for example, a value table column or a value tree column). For managed forms, the URL and AutoURL properties are implemented. You can use the URL property to get a link to the main form of the object. For the GetForm(), OpenForm(), and OpenFormModal() methods, the URL parameter is implemented. Its value is assigned to the URL property of a form when the form is obtained or opened. Navigation links to lists are implemented. For a form whose main attribute is a dynamic list with a main table specified, the navigation link points to the list of the object specified as the main table. Following the link opens the main form of the list. You can use navigation links to global command interface commands. The format of navigation links to navigation points generated by standard commands is modified. Changes made to a table of totals storage settings for accumulation registers are applied within a transaction. Values of the ReadOnly and Protection properties are preserved when a spreadsheet document is passed between the client and the server. For the NumberInWords() global context method, the AU formatting option is implemented. The TextReader and TextWriter objects are implemented. This functionality is similar to the PC-based platform functionality.	This feature was not provided on the mobile platform.	Some mobile platform features are now uniform with PC-based platform.
Mobile application.	The mobile platform supports all of the interface languages that are supported in the PC-based platform. The mobile platform delivery that supports only English and Russian interface languages is also available. The content of the mobile platform distribution kit is modified.	The mobile platform supported English and Russian interface languages only.	The system part of the mobile platform interface supports more languages than before.
Development tools.	If the Use purposes configuration property is set to Mobile device only, other configuration settings are changed automatically: The Modality usage mode property is set to Use. The Interface compatibility mode is set to Version 8.2.	If the Use purposes configuration property was set to Mobile device only, other configuration properties were not changed automatically.	For configurations being developed for mobile platform only, eliminated the chance to save configuration property values that are incompatible with mobile platform limitations.

Table of contents

Transition from the version 8.2 to the version 8.3.3

Conversion of configurations, infobases, external data processors, and external reports is not required during the upgrade from the version 8.2 to version 8.3.3.
To use certain features of version 8.3.3 you have to disable the compatibility mode. The structure of certain database objects is modified when disabling or enabling the compatibility mode. Note that to be able to work with infobases created using 1C:Enterprise version 8.2 you have to set the compatibility mode to the Version 8.2.16.
In order to use certain optimization improvements, you have to restructure data related to the optimization areas. To restructure data, you can use the Verify and repair mode, or perform forced restructuring of the required objects.
Simultaneous operating of 1C:Enterprise 8.3.3 and earlier 1C:Enterprise versions with a single file infobase is not supported. In this case a diagnostic error message is displayed.
It is recommended that you revise the list of infobases. Infobases that are present in the list when version 8.3.3 is installed in most cases have version 8.2 or 8.1 (because it is the default version, which is set automatically when an infobase is created or added to the list). Therefore, in order to open an infobase in 8.3.3 (using the program that starts 1C:Enterprise), you have to specify the required version in the list of infobase startup settings, or specify the version directly in the infobase settings.
At the first start of server cluster version 8.3.3 on the computer that has previous versions of ther server cluster installed, the content of the cluster register file (1CV8Reg.lst) is converted to a new format. The register of the server cluster 8.3.3 is stored in the file 1CV8Clst.lst, in the same directory as the cluster register of the previous versions. There is no data synchronization between cluster registers of different versions after the first start of server cluster 8.3.3.
To perform the conversion of the cluster register from version 8.2 to version 8.3 once more, stop the server cluster 8.3, delete the server cluster 8.3 register (the 1CV8Clst.lst file), and then start the server cluster 8.3.3.
To increase the performance of the configuration repository in a scenario when a repository server is used, disable the compatibility mode of the configuration repository. To access the configuration repository using earlier 1C:Enterprise versions, enable the compatibility mode of the configuration repository. The conversion process can take significant time.
Changed the full-text search index format. For efficient full-text search when using input by string, it is recommended that you clear and update the full-text search index during the transition to 1C:Enterprise version 8.3.3. It is also recommended that you clear and then update the full-text search index during the transition to earlier platform versions.
For infobases that use the OpenID authentication, you have to change the publishing settings in the default.vrd file.

Table of contents

Transition from the previous version to version 8.3.3

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.3.
Some features that are added in version 8.3.3 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.
Simultaneous operating of 1C:Enterprise 8.3.3 and earlier 1C:Enterprise versions with a single file infobase is not supported. In this case a diagnostic error message is displayed.
To increase the performance of the configuration repository in a scenario when a repository server is used, disable the compatibility mode of the configuration repository. To access the configuration repository using earlier 1C:Enterprise versions, enable the compatibility mode of the configuration repository. The conversion process can take significant time.
Changed the full-text search index format. For efficient full-text search when using input by string, it is recommended that you clear and update the full-text search index during the transition to 1C:Enterprise version 8.3.3. It is also recommended that you clear and then update the full-text search index during the transition to earlier platform versions.
For infobases that use the OpenID authentication, you have to change the publishing settings in the default.vrd file.

Table of contents

Version 8.3.2

Version 8.3.2 includes known bug fixes and functionality modifications.

New functions and changes
New functions and changes in the 1C:Enterprise mode
Optimization
Changes altering the system behavior
Changes that require changes to the configuration and administrative settings
Transition from the previous version to the version 8.3.2

New functions and changes

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.3.1 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1, 8.2.13, and 8.2.16.	In version 8.3.2 you can run configurations created in version 8.3.1 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.2 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.1 for working with the infobase even after the transition to version 8.3.2. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Development tools.	Automated configuration testing is implemented for managed applications. The testing is written in 1C:Enterprise script (using the appropriate script objects); it emulates a sequence of interactive actions and checks the results of their execution. Automated testing is supported for thin, thick, and web clients, both in file and client/server modes. The test does not require making any changes in the configuration being tested. Implemented the option of recording interactive user actions in a managed application for later use in a 1C:Enterprise script-based scenario, which reproduces the actions (http://its.1c.ru/db/metod81#content:5014:1).	This feature was not provided.	Better development quality can be achieved due to automated testing of the applied solution interface.
Development tools. Applied objects.	Implemented XDTO serialization for pivot charts. Templates of spreadsheet documents that contain pivot charts can be dumpled to XML files.	This feature was not provided.	All configuration objects can be dumped to files.
Mobile application.	Mobile application development is supported, with target operating systems iOS and Android. Applications can run on mobile devices in the offline mode; permanent Internet connection is not required. Application data exchange through the Internet can be implemented using standard 1C:Enterprise tools. The development is performed in Designer; the managed application development model is used. The subset of functionality used for PC application development is supported. The resulting applications can run both on PC and mobile devices.	This feature was not provided. Mobile application development was only supported in the mobile extension for handheld devices (and only for Microsoft Windows Mobile and Microsoft Windows CE operating systems).	You can develop applications for devices with iOS and Android operating systems using 1C:Enterprise platform tools. Data exchange between mobile applications and PC applications is available.

Table of contents

New functions and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Client application.	If an error that leads to system shutdown occurs, the error text is displayed in the technical support information window.	In some cases the error that led to system shutdown was not displayed in the technical support information window.	Improved usability of information for technical support.

Table of contents

Optimization

Functionality	After	Before	Result of changes
Applied objects.	Reduced verification and repair time for document journals.	For large journals the "Verify and Repair" operation might take significant time.	Reduced time of the "Verify and Repair" operation for document journals.
Development tools.	Optimised memory usage when comparing configurations and updating modified configurations.	Comparison and merging of large configurations might cause issues related to high memory usage.	Comparison and merging of large configurations no longer requires customized OS settings.

Table of contents

Changes altering the system behavior

Functionality	After	Before	Result of changes
Command interface.	In the information register record form the system behavior has been changed in the case when the OnlyInAllActions property of the Copy command is set to Auto. This value now means that the command is only present in the All actions menu. This change is not implemented in 8.3.1 compatibility mode.	The Auto value of the OnlyInAllActions property of the Copy command meant that the command was present both in the command bar and in the All actions menu.	The behavior of the Copy command in the information register record form is unified with its behavior in forms of other objects.
Window management.	Relative positions of the user notification window and the window showing server calls are changed. The default position of the user notification window is the bottom right corner of the workspace area. The default position of the window showing server calls is the bottom left corner of the workspace area.	On Windows operating system, default window positions depended on the taskbar position. On Linux operating system, default window positions were not defined.	Unified default positions for the user notification window and the window showing server calls in different operating systems. Eliminated indeterminate behavior on Linux operating system.
Web client.	When a pop-up window is blocked by the pop-up blocker in Google Chrome web browser, the browser displays a related setup instruction in a new tab.	The browser setup instruction was displayed in a new browser window (not in a new tab)	Better usability of web browser setup.
Applied objects.	A value obtained from an empty table of values attribute, a value tree, or a tabular section matches the default value of the column attribute type (the type qualifier is taken into account). This change is not implemented in version 8.2.16 compatibility mode.	A value obtained from an empty table of values attribute, a value tree, or a tabular section matched the default value of the column attribute type, but the type qualifier was not taken into account.	The default value generation is uniform throughout the system.
Client application. DBMS operations. System requirements. Configuration repositories.	The mechanism of shared work with infobase files and configuration repository files is revamped. Shared work with infobases and configuration repositories is supported for both Windows and Linux users. For the files 1Cv8.1CD, 1Cv8tmp.1CD, 1Cv8.1CL, 1Cv8tmp.1CL, and for some other files the system creates auxiliary files that have the same names with .cfl extension added (for example, 1Cv8.1CD.cfl). These files have zero size and are never deleted on closing client applications. Shared work with a file infobase is only possible if all client applications have the same version number. The number of simultaneous connections to a file infobase is limited to 1024.	The mechanism of shared work with the file infobase and the configuration repository did not take into account some pecularities of Linux file system.	Shared work with the file infobase and the configuration repository is available to both Windows and Linux users. Issues related to multiuser work with file infobases and configuration repositories on Linux operating system are eliminated.
Data display.	When you create a formatted string in Designer (in the dialog for editing a formatted string), you can use style elements (font face and color). The formatted string stores references to style elements that were used during its creation. Converting style elements to actual fonts and colors (dereferencing) is performed when the string is displayed.	The dialog for editing a formatted string did not have options for specifying style elements. Formatted strings that were created using 1C:Enterprise script and included style elements actually contained explicit font and color values (not the references).	Improved usability of formatted string creation. You can simultaneously change the formatting of all text fragments that have the same style element applied to them.
Internet-enabled functionality.	If you use the InternetMail object with a mail server where secured StartTLS connection is set up to use the same ports as unsecured connection, the StartTLS connection is established. This change is not implemented in version 8.2.16 compatibility mode.	If you used the InternetMail object with a mail server where secured StartTLS connection was set up to use the same ports as unsecured connection, the StartTLS connection was not established.	You can establish a secured StartTLS connection to a mail server.
Spreadsheet documents.	When the Join() method of a spreadsheet document is called, the properties StayWithNext, PageTop, and PageBottom of a spreadsheet document cells area are only copied when joining is performed for the area located beyond the right border of the resulting document. This change is not implemented in version 8.2.16 compatibility mode.	When the Join() method of a spreadsheet document was called, properies of a spreadsheet document cells area were always copied.	The Join() method handles page breaks during the output to a spreadsheet document.
Server clusters.	Removing a server cluster or a working server from the cluster console requires a confirmation.	Removing a server cluster or a working server from the cluster console did not require a confirmation.	The chance of accidentally removing a server cluster or a working server from the cluster console is decreased.
Administration tools.	The URL parameter is added to the CheckInfoBases method of the WebCommonInfoBases internet service. It allows "redirection" of infobase list requests to another internet service (provided that the other service has the same method descriptions). The other internet service can have different authentication settings.	Internet service "redirection" was not available. All web service calls used the same authentication.	When retrieving the list of infobases through internet services, you have the option to use multiple services with different authentication requirements. This allows implementing scenarios of the following type: the check for infobase list changes does not require authentication, but retrieving the list requires authentication.
Applied objects. Information registers.	Attributes, common attributes (that are not separators), and resources are not read implicitly when record sets are written to information registers. Rights to read attributes, common attributes (that are not separators), and resources are not required when writing a recordset to an information register.	Rights to read attributes, common attributes (that are not separators), and resources were required when writing a recordset to an information register.	Access right restrictions for read operations are not checked when writing a record set to an information register.

Table of contents

Changes that require changes to the configuration and administrative settings

Functionality

After

Before

Result of changes

Data display.

If a message to a user contains characters incompatible with XML format (in thick or thin client), the error XML text contains invalid characters in X position is generated.

This change is not implemented in version 8.3.1 compatibility mode.

If a message to a user contained characters incompatible with XML format, the thick and thin clients did not display any error message.

Uniform system behavior for handling characters incompatible with XML format.

Applied objects.

If you explicitly specify the Encoding property of the InternetMailAttachment object, the outgoing email message is generated with explicitly specified attachment encoding.

This change is not implemented in version 8.2.16 compatibility mode.

The Encoding property of the InternetMailAttachment object was ignored during the generation of outgoing email message.

Explicitly specified attachment encoding ensures that the emal client displays the attachment name and content correctly whenever email message encoding is different from the attachment encoding.

Spreadsheet documents.

The algorithm for calculating horizontal cell positions is changed. If total width of several adjacent cells is identical for different rows, such blocks of adjacent cells have equal width in all rows and therefore have common vertical borders.

This change is not implemented in version 8.2.16 compatibility mode.

If total width of several adjacent cells was identical for different rows, the cells might have different width in different rows, and therefore might not have common vertical borders.

Improved usability of spreadsheet documents.

Table of contents

Transition from the previous version to the version 8.3.2

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.2.
Some features that are added in version 8.3.2 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.

Table of contents

Version 8.3.1

Version 8.3.1 does not include changes introduced in version 8.2.17.

Version 8.3.1 includes known bug fixes and functionality modifications.

Improved the list of new and updated features:

Keywords and interface texts are color-coded (it is the same formatting that is used in the documentation).
Sections describing behavior in the compatibility mode have color background.
The list structure is updated, providing more details and better usability (only for version 8.3.1 or later).

New functions and changes
New functions and changes in the 1C:Enterprise mode
Optimization
Changes altering the system behavior
Changes that require changes to the configuration and administrative settings
Renamed objects
Upgrade from the previous version to version 8.3.1

New functions and changes

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.2.16 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1 and 8.2.13.	1C:Enterprise provides compatibility of configurations developed using version 8.3.1 or later with previous platform versions.
Designer. Cross-platform architecture.	The client application for Linux operating system is available. It includes thin client, thick client, and Designer. It supports file and client/server operation modes. Thin client can connect to infobases using a web browser. Limitations of the client application for Linux are listed in the documentation. Installation of multiple 1C:Enterprise versions is not supported. Shortcuts for noninteractive startup application, thin client, and thick client are added to the application menu of Linux desktop environment. They are located in the Finance subsection of the Office section.	Only the 1C:Enterprise server and the web client were available for Linux operating system.	You can develop applied solutions and run client applications on Linux operating system.
Thin client access over the Internet.	The thin client is now HTTPS-enabled, thanks to client certificate support. The following client certificate storage options are supported: file, Windows certificate store, and NSS certificate store. The following command line options for specifying certificate parameters are implemented: HttpsCert, HttpsCA and HttpsNSS. Client applications for Linux operating system do not support Windows certificate store, and HttpsCert, and HttpsCA command line options.	The thin client was not HTTP-enabled, and client certificates were not supported.	The thin client is HTTP-enabled, and client certificates are supported.
Web links.	Web services can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).	Web services could not operate using HTTPS with client certificates.	Web services are operational in cases when the server side requires a client certificate to use HTTPS.
Internet-enabled functionality.	HTTP and FTP connections can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).	HTTP and FTP connections could not operate using HTTPS with client certificates.	HTTP and FTP connections are operational in cases when the server side requires a client certificate to use HTTPS.
1C:Enterprise script.	You can calculate the value of hash function by MD5 and CRC32 algorithms using the DataHashing object.	Calculating the hash function required the use of third-party (add-ins, etc.) tools.	You can quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools.
External data sources. Common attributes / Data separation.	A common attribute can include an external data source. Connection parameters for such external data sources are stored by separator values. If a separator is not used in a session, the separator is treated as an independent value for storing connection parameters. Data located in tables of external data sources is not separated by separator values.	Common attributes could not include external data sources.	You can specify connection parameters for each data area in the infobase. This provides you with the option to access either different infobases with the same structure, or a single infobase with different connection parameters.
Managed forms.	You can specify data located in a specific row of a form attribute that has table structure (except dynamic lists) as a value of a managed form field or table.	This feature was not provided.	You can implement such interface features as displaying report settings in separate form fields.
External data sources.	Operating system authentication is available when working with external data sources. The SessionOSAuthenticationChange access right is implemented. It allows or denies changing the operating system authentication setting both in user settings and in current session parameters.	This feature was not provided.	You can establish connection to external data sources if the only authentication method available is operating system authentication.
Applied objects. Data display.	User presentations for data base objects of the following types: Catalog, Document, ChartOfAccounts, ChartOfCalculationTypes, ChartOfCharacteristicTypes, BusinessProcess, Task, ExchangePlan, Table. Implemented the PresentationFieldsGetProcessing and PresentationGetProcessing event handlers for object manager modules of these types. This change is not implemented in version 8.2.16 compatibility mode.	Modification of database objects using script tools was not allowed.	Custom presentations for database objects. The option to obtain presentations for external data source tables when the field that provides the presentation is not specified. The option to obtain presentations of objects that include localized data.
External data sources. 1C:Enterprise script.	You can search for references to objects of external data source tables using the FindByRef() global context method or Find references to object standard function. The search is performed both in infobase tables and in external data source tables.	Searching for references to objects of external data sources tables using the FindByRef() global context method or Find references to object standard function was not available.	You can search for references to objects of external data source tables.
External data sources.	The AllRefsType() method is implemented for the ExternalDataSourceTablesManager object.	This feature was not provided.	Implementation of missing features for working with external data sources.
External data sources.	The OpenValue() global context method allows opening the following value types: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey.	The OpenValue() global context method did not allow opening the following value type: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey.	Implementation of missing features for working with information registers and external data sources.
Database configuration updates. Server clusters.	Background database configuration update is implemented. The update is supported in client/server mode only. It is available when the data structure is modified. The update does not require long-lasting exclusive access to the infobase. The exclusive access is required at the final stage of the background update for a short period of time. The database configuration update service is implemented for a server cluster. A system background job that performs the background database configuration update is implemented. The GetDataBaseConfigurationUpdate() global context method and the DataBaseConfigurationUpdate object are implemented. For the /UpdateDBCfg Designer batch mode command line option, the following parameters are implemented: -Dynamic, -BackgroundStart, -BackgroundCancel, -BackgroundFinish, -BackgroundSuspend,and -BackgroundResume. The following events are implemented in the event log: _$InfoBase$_.DBConfigBackgroundUpdateStart, _$InfoBase$_.DBConfigBackgroundUpdateFinish, _$InfoBase$_.DBConfigBackgroundUpdateCancel, _$InfoBase$_.DBConfigBackgroundUpdateSuspend, and _$InfoBase$_.DBConfigBackgroundUpdateResume.	An update of database configuration with modified data structure was possible only in the exclusive mode.	The update of database configuration with significant changes in its data structure does not cause long application downtime for end users. You have the option to perform dynamic infobase configuration update in Designer batch mode. The option is available for both background and regular updates.
1C:Enterprise script. File operations. Web client.	The TempFilesDir() method is implemented for the web client. The method is available when the file system extension is installed. The UserDataWorkDir() method is implemented. It provides access to the user directory created by the system. The method is available for thin, thick, and web clients. In the web client the method is available when the file system extension is installed. The DocumentsDir() method is implemented. It provides access to the default document directory of the operating system. The method is available for thin, thick and web clients. In the web client the method is available when the file system extension is installed.	Standard catalogs (user data directory and document directory) were inaccessible for standard tools. In the thick and thin clients the access could be implemented using third-party tools, which reduced 1C:Enterprise portability between operating systems and client applications types.	Access to certain standard directories on the client computer, which allows storing user file data in designed locations without using third-party tools.
Data display.	Formatted strings are available (FormattedString type). You can use formatted strings as: data for the form elements of Label type; title for the Decoration form element; MessageText parameter of the DoMessageBox() method QueryText parameter of the DoQueryBox() method.	Displaying text that included various formatting styles was only available for HTML documents and formatted documents.	Improved text presentation capabilities and usability.
1C:Enterprise script. Managed forms.	The URLProcessing handler is implemented for the form field Label, form field Decoration of Label type, and managed form. The handler is called if the following conditions are met: there is a formatted string in any of the specified form fields, it contains a hyperlink, and the Hyperlink property of the form element is set to False.	Implementing presentation of an entire form element as a hyperlink was allowed, but including multiple hyperlinks in a single field was not allowed.	The option to handle each hyperlink contained in a formatted string separately.
Command interface.	You can use navigation links to commands of the global command interface. Using a link executes the command. Support of navigation links to commands is implemented for the GotoURLGotoURL() global context method.	This feature was not provided.	Using a link can execute a command, and this feature can be used in the script.
Managed forms.	The URL property is implemented for managed forms. It is used for obtaining a link to the default object form. The AutoURL property is implemented for the managed form. The GetURL() method of the ClientApplicationWindow objects returns a value of the URL property (if the AutoURL property is set to False) or the standard link to the default form.	This feature was not provided.	You can specify the value of the navigation link obtained from the client application window.
1C:Enterprise script. Common attributes / Data separation. Applied objects.	Document journals can be included in contents of common attributes, which are not used as separators. For compatibility purposes, in infobases created in 1C:Enterprise version 8.2, the value of the Use property of the the common attribute content element is set to Do not use for document journals.	Common attributes could not be displayed in document journals.	Common attributes can be displayed in document journals.
Data display. Managed forms.	Implemented the following style fonts: SmallTextFont, LargeTextFont, ExtraLargeTextFont. For the Font type the Scale property is implemented. It specifies increase or decrease of the font size relatively to the original size.	The only method of specifying font size in a managed form was setting absolute font size.	You can specify the size of the form font relatively to the base font of the form, without using absolute font size values.
Server clusters. 1C:Enterprise script.	The SafeCallMemoryLimit property is implemented for the IWorkingProcessInfo object. It specifies the amount of memory (in bytes) that the application can use during a single server call. The SafeWorkingProcessesMemoryLimit property for the IWorkingServerInfo object is implemented. It specifies maximum amount of memory (in bytes) available for all running processes on a given working server.	No tools for limiting memory usage were available. It might cause problems in some situations - for example, when users customized reports that selected large amounts of data.	Server stability improved. If a specific session consumes a large amount of memory, it does not cause emergency shutdown of the entire server cluster. Instead, the client application that causes the memory consumption is shut down.
Server clusters. 1C:Enterprise script.	While a working process is executing a script in the client/server infobase mode, the stack is monitored to prevent it from overflowing.	Infinite recursion might lead to emergency shutdown of the working process of the server cluster.	Stability of server cluster operation improved.
Server clusters. 1C:Enterprise script.	For the ISessionInfo and IInfoBaseConnectionInfo objects the following properties are implemented: MemoryCurrent - size of memory (in bytes), used from the beginning of the current call; MemoryLast5Min - size of memory (in bytes), used by calls during the last 5 minutes; MemoryAll - size of memory (in bytes), used by calls since the beginning of the session; InBytesCurrent - number of bytes read from the disk since the start of the current call; InBytesLast5Min - number of bytes read by the session from the disk during the last 5 minutes; InBytesAll - number of bytes read from the disk by the session since the beginning of the session; OutBytesCurrent - number of bytes written to the disk by the session since the beginning of the current call; OutBytesLast5Min - number of bytes written to the disk by the session for the last 5 minutes; OutBytesAll - number of bytes written to the disk by the session since the beginning of the session. Similar properties are implemented in the cluster console for the list of sessions, list of connections, and connection properties dialog.	This feature was not provided.	Monitoring tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.
Technological log. Server clusters.	Extended the list of properties for the <call> event of the technological log when the event is generated for the rphost process (the process property is set to rphost), and also when the rphost process performs a call to virtual system resources. The following properties are added: Report - metadata object name of the report being executed; Method - name of the called method; SessionID - session number; Memory - size of memory (in bytes) that was occupied and not released during the call; MemoryPeak - size of memory (in bytes) that was occupied and not released during the call. The peak value; InBytes - number of bytes read from the disk during the call; OutBytes - number of bytes written to the disk during the call; Context - event context.	The listed properties were absent from the <call> event.	Technological log tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.
Common attributes / Data separation. 1C:Enterprise script.	You can delete data from a specific data area or from the entire infobase. The following data can be deleted: Applied object data Settings storage data History List of users Time zone settings The Administration right is required for deletion. The deletion can be performed: using the /EraseData command line option of the Designer batch mode using the EraseInfoBaseData() global context method The _$InfoBase$_.EraseData event is implemented in the event log.	It was impossible to delete a specific data area.	You can delete a data area that is no longer needed (for example, data belonging to a subscriber that stopped using the system).
Server clusters. Software licensing.	The licensing service is implemented for the server cluster. The license search algorithm is modified.	The licensing service was not present.	You have the option to bind a software license to a specific computer, which is intended for running the licensing service only and will not be subject to hardware changes.
Development tools.	Dumping configurations to files and loading configurations from files is implemented. Most objects are dumped to .xml files. Modules are dumped to the text files. Pictures are dumped to files in their original format, help information is dumped to .html files. Vendor configurations are dumped to configuration files (.cf). Ordinary forms and interfaces are dumped to binary files. Dump configuration to files and Load configuration from files commands are added to the Configuration menu. Dump configuration files and Load configuration files commands are removed from the Configuration menu, but you can restore them using the main menu settings dialog. The DumpConfigToFiles and LoadConfigFromFiles command line options are implemented.	Limited set of data was dumped and loaded: modules, help information, templates, rights, and pictures. Other configuration data was not dumped. Dump configuration files and Load configuration files commands from the Configuration menu were used for dumping and loading data.	You can analyze and modify configurations using third-party tools.
Data display. Managed forms.	You can specify the background color for form group extensions of regular groups and pages using the BackColor property. If the background color of a group is different from Auto and the group is displayed as a Group box, the group box (including the title) is filled with the specified background color.	The option to specify background color for form groups was not provided.	The color highlighting of groups improves visibility of form elements and the overall usability of forms.
Common attributes / Data separation.	New global context methods for managing the safe mode of data separation are available in 1C:Enterprise script: SetDataSeparationSafeMode and DataSeparationSafeMode. They duplicate the functionality of the safe attribute in the zone tag of the default.vrd file.	Switching to the safe mode of data separation was only available by editing the file default.vrd and only if the web server connection to the infobase (the HTTP protocol) was used.	The new methods enable safe execution of code fragments called from sessions that do not use separator values (but are intended to run in specific data areas, without any way to change the area accidentally).
Event log. OpenID authentication.	In case of successful or unsuccessful OpenID authentication the Session.Authentication or Session. Authentication error events are generated in the event log.	OpenID authentication events were not written to the event log.	You can obtain information about OpenID authentication events from the event log.
Event log. OpenID authentication.	For infobases that are OpenID providers the OpenIDProvider.PositiveAssertion event is implemented. It is generated in case of a positive response to the authentication request. If the response to the authentication request is negative, the OpenIDProvider.NegativeAssertion event is generated in the event log of the infobase.	This feature was not provided.	Improved tools for administration of OpenID providers.
Development tools.	You can view the values of the form element properties Font, TitleFont, FooterFont and ChoiceList in a separate window when editing of these properties is disabled.	These properties could not be viewed if the object was not locked in the repository or was supported.	If an item is not locked in the configuration repository or is supported, you can view its font style and choice list without disabling support and without locking the object in the repository.
Server clusters.	When logon to or logout from an infobase that requires a client license is performed, the platform can notify an external application using web service methods. In response to logon notification, the external application can allow or deny the start of the session. This option is only available in client/server infobase mode. For specifying web service parameters, the following properties are implemented: External session manager property of the infobase in the cluster console ExternalSessionManagerConnectionString property of the IInfoBaseInfo object. If a web service for external session management is unavailable, the system behavior is determined using the following properties: Required usage of external session manager property of the infobase in the cluster; ExternalSessionManagerRequired property of the IInfoBaseInfo object. The external session manager service is implemented on the server. Parameters of invoked web services are listed in the documentation.	The only option to limit the number of simultaneous sessions was appropriate modification of the applied solution. A platform mechanism for performing this task was not available.	A platform mechanism for monitoring the number of simultaneously used licenses for various applied solutions, which does not require modification of these applied solutions.
Web client. Add-ins.	You can use add-ins in Google Chrome and Safari web browsers (for operating systems of Windows family and Mac OS X). The Mac OS value is implemented for the PlatformType system enumeration. A file system extension is available for these browsers on operating systems of Windows family and Mac OS X. A cryptographic extension is available for these browsers on operating systems of Windows family only.	Add-ins, file system extension, and cryptographic extension were not supported for Google Chrome and Safari web browsers.	A file system extension and cryptographic extension (for operating systems of Windows family only) are available for Google Chrome and Safari web browsers. Add-ins can be created for all supported web browsers.
Pictures.	Processing pictures from the script with help of the new PictureProcessor object. The following options are available: Selecting a significant picture part Rotating a picture	This feature was not provided.	A way to process pictures before placing them in a spreadsheet document. Usage examples: Select a seal from a photo Rotate a picture by a specified angle to align a signature
Charts.	The managed form editor allows interactive setup for the following attribute types: Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema. You can open the interactive setup dialog box from the property panel of the attribute.	Only the following ways to set up the Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema objects were available: through 1C:Enterprise script, or by putting a set up object to a template and then putting the object from the template to a form element at form creation.	This feature facilitates development.
Data display.	New parameter AU for the global context method NumberInWords(). It is only used in the English locale (en, en_XX). It defines the number notation, classic or compact. In the classic notation "and" is always used between the word "hundred" (or "thousand" or "million") and the word representing the last two decimal digits. For example, 150 is "one hundred and fifty", while 100 is "one hundred" and 50 is "fifty". In the compact notation "and" is omitted.	The compact notation was always used for converting numbers to English words.	Correct number-to-word conversion according to the common practice rule in European countries.
Charts of characteristic types.	You can use the ALLOWED keyword when retrieving a list of characteristics, provided that the list was defined using one of the following: the CHARACTERISTICS keyword of the query language or the dialog box for specifying object characteristics. If you retrieve the list of characteristics using a query, you have the option to use the ALLOWED keyword there.	The ALLOWED keyword was not used when retrieving lists of characteristics.	Data access restrictions are implemented for tables that store property lists (for example, charts of characteristic types).
Data composition system.	Fields from data sets that are not connected can be displayed in details. For DataCompositionTemplateRecordsDataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects, the DataSets properties are implemented. The property value is an array containing names of data sets whose details are displayed. The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects is deprecated. It is recommended that you do not use this property, although it is supported for compatibility purposes. Calling the DataSet property throws an exception if the DataSets property contains an array with more than one item.	It was impossible to display fields from data sets that were not connected. The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords contained the name of the dataset whose details were displayed.	You can create complex analytic reports.
External data sources.	The FormGetProcessing event is implemented in the manager module of external data source table.	This feature was not provided.	The default form of the external data source can be redefined when the external data source is opened or obtained.
External data sources.	Hierarchical lists can be organized for object data of external data sources. The ParentField and UnfilledParentValue attributes are implemented for the Table metadata object. Hierarchical object tables can be used in the data composition system, queries, and dynamic lists.	This feature was not provided.	You can work with hierarchical data in external data sources.
External data sources. Queries. Data composition system.	You can use temporary tables when working with external data sources. Temporary tables are created directly in the database of the external data source. The following syntax is used for calling temporary tables:ExternalDataSource.<External data source name>.TempTable.<Temp table name>.	This feature was not provided.	You can create complex reports based on external data source tables.
Charts of characteristic types. Data composition system.	When creating object characteristics using the Additional characteristics of metadata object dialog, if the list of characteristics is not obtained from the chart of characteristic types, the characteristic value type is defined by the attribute type specified in the Value field attribute of this dialog. If this attribute is not specified, the characteristic value type is Boolean. When object characteristics are specified using the CHARACTERISTICS query language extension of the data composition system, if the TYPE property is not specified, the characteristic type is defined by the value type obtained in the CHARACTERISTICVALUES property. If the CHARACTERISTICVALUES property is not specified, the characteristic value type is Boolean.	When object characteristics were specified using the Additional characteristics of metadata object dialog or the CHARACTERISTICS query language extension, if the list of characteristics was not obtained from the chart of characteristic types, the characteristic value type was Boolean.	You can store characteristic types in catalogs, and you can modify characteristic types using a complex type of the attribute that stores the characteristic value (e.g., type of information register resource).
1C:Enterprise script.	Serialization of value table index descriptions is implemented. The index content is not serialized, but restored during deserialization.	Value table indexes were lost during serialization/deserialization.	More complete restoration of value table state during deserialization.
Charts.	New types of charts are implemented: Funnel 3D funnel Normalized funnel 3D normalized funnel The following properties are implemented for the Chart object: FunnelNeckHeight, FunnelNeckWidth, and FunnelSpace. These properties are applicable for the new charts types only.	This feature was not provided.	New chart functionality.
Charts.	Antialiasing mode is implemented for charts. SplineMode and SplineStrain properties are implemented for the Chart object. These properties are applicable to the following chart types: line, stacked line, area, stacked area, normalized area, ceil graph, tape graph, waterfall, funnel, and 3D funnel, and also for the following chart types, which have the Indicator flag set for the series: column, 3D column, bar, 3D bar, stacked column, 3D stacked column, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.	This feature was not provided.	New chart functionality.
Charts.	You can connect series of charts with each other. For the Chart object the following properties are implemented: ValuesBySeriesConnection, ValuesBySeriesConnectionLines, and ValuesBySeriesConnectionColor. These properties are applicable to the following chart types: stacked column, 3D stacked column, stacked bar, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.	This feature was not provided.	New chart functionality.
Charts.	The semitransparency mode is implemented for charts. SemitransparencyMode and SemitransparencyPercent properties are implemented for the Chart object. These properties are applicable to the following chart types: area, bar graph, pyramid graph, ceil graph, tape graph, waterfall, funnel, 3D funnel, and 3D normalized funnel.	This feature was not provided.	New chart functionality.
Charts. Data composition system.	For the objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance the following properties are implemented: ChartType.ValuesBySeriesConnection, ChartType.ValuesBySeriesConnectionLines, ChartType.ValuesBySeriesConnectionColor, ChartType.SplineMode, ChartType.SplineStrain, and ChartType.SemitransparencyMode. These properties are used for setting data composition template parameters.	This feature was not provided.	New chart management options in the data composition system.
Data composition system.	In the data composition system expression language the following aggregate functions are implemented: Every(), Any(), Stddev_Pop(), Stddev_Samp(), Var_Samp(), Var_Pop(), Covar_Pop(), Covar_Samp(), Corr(), Regr_Slope(), Regr_Intercept(), Regr_Count(), Regr_R2(), Regr_AvgX(), Regr_AvgY(), Regr_SXX(), Regr_SYY(), and Regr_SXY().	These aggregate functions were not provided in the data composition system expression language.	The new functions facilitate creation of complex analytic reports.
Data composition system.	In the data composition system expression language the following functions are implemented: ACos(), ASin(), ATan(), Sin(), Cos(), Tan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Round(), Int(), ValueType(), and Type().	These functions were not provided in the data composition system expression language.	The new functions facilitate creation of complex analytic reports.
Data composition system.	New aggregate function Rank() in the data composition system expression language. The function returns a sequence number of the current record in the current grouping, provided that all records of the current grouping are sorted in the specified order.	This aggregate function was not provided in the data composition system expression language.	The new functions facilitate creation of complex analytic reports.
Data composition system.	New aggregate function ClassificationABC() in the data composition system expression language. The function returns the class number: 1 – class "А", 2 – class "B", 3 – class "C".	This aggregate function was not provided in the data composition system expression language.	The new function facilitates creation of complex analytic reports.
Spreadsheet documents.	The Merge command is added to the shortcut menu of a spreadsheet document. It is also accessible through a keyboard shortcut Ctrl+M.	Merging cells of a spreadsheet document was only available by using the menu command Table - Merge or clicking the corresponding toolbar button.	Improved usability of spreadsheet documents containing a large number of merged cells.
Charts.	The Indicator property is supported for the tape graph chart: when antialiasing is disabled, the series with the Indicator property set are displayed semitransparently on the entire chart area, overlapping other series.	This feature was not provided.	New chart functionality.
Managed forms.	You can specify the Arbitrary type for a subordinated attribute of a managed form attribute (e.g., column of a value table, column of a value tree, etc.).	It was impossible to store some data types (such as a references to external data source tables) in subordinated attributes of managed form attributes.	You can store references to external data source tables in subordinated attributes of managed form attributes.
Data display.	You can manage duplex printing of spreadsheet documents, graphical schemas (using script and interactively), and text documents (interactively only). System enumerations DuplexPrintingType and PagePlacementAlternation are implemented.	This functionality was only available from a printer driver.	You can explicitly specify the duplex printing option in some use cases.
Development tools. Web client and web service publishing tools.	In the dialog for publishing to the web server you can edit all tags present in the default.vrd file. You can edit custom default.vrd files in this dialog. The descriptor parameter of the webinst utility allows you to perform publishing by template. The generated default.vrd file is used as a template.	A limited set of tags present in the default.vrd file was available for editing in the dialog for publishing to the web server. The option to publish by template was unavailable in the webinst utility, which limited the capabilities of automatic publication. E.g., publishing of web services using the utility was impossible.	You can edit all tags of the default.vrd file interactively, and you can create templates for the future automatic publication. Using templates allows publishing web services using the command line utility.
Client application installation.	You can set up the update of thin client distribution kit and downloading the list of common infobases using an HTTP connection or a web service. If versions of client and server applications do not match, the thin client is downloaded and installed automatically. The following parameters of the 1cestart.cfg file are implemented : InternetService - address of the web service for updating of the thin client distribution kit and the list of common infobases, WebCommonInfoBases - address of the web service for downloading the list of common infobases, WebDistributiveLocation - address of the web service for updating the thin client distribution kit. You can specify a link to the thin client distribution kit in the following configuration files: In the default.vrd file using the pubdst attribute; In the conf.cfg file using the PublishDistributiveLocation parameter.	Automatic update of the thin client and downloading of list of common infobases were only available in a local network.	You can update the thin client distribution kit and download the list of common infobases without creating common directories. This allows you to obtain an up-to-date version of the distribution kit and the current list of infobases from a remote network.
DBMS operations.	DBA rights are not required for creating infobases in Oracle Database. The following actions cannot be performed without DBA rights: creating a database (data schema) deleting a data base (data schema) using the cluster management console	DBA rights were required for creating infobases in Oracle Database.	Increased security of DBMS operations. New scenario of creating an infobase without DBA rights, provided the database (data schema) already exists.
Internet-enabled functionality. 1C:Enterprise script.	Encoding of text strings is implemented (the global context method EncodeString()). It simplifies the following operations: Converting a text string to a format that allows using it as a part of a URL Converting a URL string to a RFC 1738-compliant format Decoding of text strings is implemented (method DecodeString()).	This feature was not available.	Easier generation of URLs containing non-English characters.
Administration tools.	You can create a self-extracting archive (SFX archive) of a client application and upload it to a web site. You can include the client application distribution kit and the 1CEStart.cfg configuration file, which is used for installing the client application, into the archive. The created executable file is only intended to run on Windows operating systems. The self-extracting archive is generated using the 1CEClientSetupMake.exe utility, which is distributed via ITS (http://its.1c.ru/db/metod81#content:4914:1).	This feature was not provided.	Simplified installation of client applications on the client computer for infobase access over the Internet (instead of using the web client).

Table of contents

New functions and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of change
Standard functions.	The search for references to external data source tables is available for the standard function Find references to object, which operates in the managed mode.	It was impossible to find references to objects of external data sources tables using the standard function Find references to object.	You can search for references to external data source objects using a standard function.
Spreadsheet documents.	In a spreadsheet document that is in the read-only mode, you can expand and collapse groups not only using a mouse, but also using keyboard shortcuts and the shortcut menu of the spreadsheet document.	In a spreadsheet document that was in the read-only mode, expanding and collapsing groups could only be performed using a mouse.	Improved usability of spreadsheet documents.
Navigation links.	In the In tabs form opening mode when a form is opened by clicking a navigation panel command and the navigation link is requested, if the managed form property AutoUrl is set to True, the form returns a link to the object displayed by the form. Otherwise, it returns the value of the Url property of the managed form.	In the In tabs form opening mode forms opened by clicking navigation panel commands returned links to navigation points.	You can open a list form in a separate window using the shortcut menu of the tab title.
Managed forms.	If the EditMode property of a managed form table cell is set to Directly, pressing the Enter key in this cell moves the cursor to the next editable cell in this row. If the cell is last in a row, the cursor is moved to the first editable cell of the next row. If there is no next row and the managed form table has the Autoinput new row property set to True, a new row is added.	In the row editing mode pressing the Enter key finished editing the table cell and did not move the cursor to the next cell.	Pressing the Enter key is handled in the same way in the new row input mode and in the row editing mode. This simplifies working with the platform and enhances editing table data using the keyboard.
Managed forms.	While editing a cell of a managed form table with EditMode property set to Directly: Pressing the Ins key adds a new row; Pressing PgUp or PgDn moves one table page up or down; Pressing Ctrl+Home or Ctrl+End moves to the first or to the last table row.	These features were not provided.	Improved usability of managed form tables.
Managed forms.	In managed forms, in automatic table row adding mode, you can delete rows by pressing Alt+Shift+Del. A row is deleted in the following cases: The row does not contain any data, and you click in any area outside the new row. The row does not contain any data, and you move to another row using the keyboard. You can use this keyboard shortcut even while you are editing a table row.	This feature was not provided.	Improved usability of managed form tables.
Managed forms.	If you press the Down Arrow key while the cursor is in the last row of a managed form table, a new row is added. If you press the Up Arrow key while the cursor is in a new row and the new row is still empty, this row is deleted. If you move the cursor from top to bottom by holding down the Down Arrow key, the cursor will stop at the last row of the managed form table. To add a new row, release the Down Arrow key and press it again.	Pressing the Down Arrow key did not create a new row. Pressing the Up Arrow key did not undo the creation of a new row.	Improved usability of managed form tables.
Managed forms.	For attributes of String type that have fixed length, the automatic marking of incomplete attributes is modified. The change affects attributes located in managed form tables, table boxes or spreadsheet documents. The check whether the attribute is performed using the ValueIsFilled() method, so the value of String type is considered incomplete if it does not contain any any characters except spaces.	An attribute was considered incomplete only if it contained a blank string.	Unified the behavior of marking of incomplete attributes.
Web client.	When the web client is started in a web browser that is not in the list of supported ones, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per week.	The check for supported web browsers was not performed.	The user receives a warning if they use an unsupported web browser or an unsupported version of a supported browser.
Web client.	When the web client is started in a web browser whose version is not supported, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month.	The check for supported browser versions was not performed.	The user receives a warning when they use an unsupported web browser or an unsupported version of a supported browser. It is recommended that they change their browser version when they receive the warning.
Web client.	When the web client is started in Microsoft Internet Explorer version later than those available during the platform development, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month.	The check for supported Microsoft Internet Explorer versions was not performed.	The user is notified if their Microsoft Internet Explorer version was not tested for compatibility with 1C:Enterprise.
Technological log.	You can write information about working with external data sources to the technological log. For this purpose, the <EDS> event is added to the configuration file of the technological log.	Working with external data sources was not reflected in the system technological log.	A tool for analyzing problems that might occur while working with external data sources.
Technological log.	You can have all operations that affect server cluster functioning (for example, operations performed during data replication between cluster services) written to the technological log. For this purpose, the <CLSTR> event is added to the technological log configuration file.	Events that were generated during the execution of operations that affected server cluster functioning were not reflected in the technological log.	A tool for analyzing server cluster issues.
Server clusters. Administration tools.	Cross-platform administration server (RAS) is implemented for administering the server cluster. The application can run both as a standalone application and a service (daemon). The administration server is installed with 1C:Enterprise server. The cross-platform command line utility (RAC) is implemented for the administrator server. The utility is installed with 1C:Enterprise server. Administration utility version and administration server version may differ. The utility provides the same administration functionality as program cluster administration tools (the V82.ComConnector COM object), except operating system authentication of the administrator in infobases, clusters, or working servers. The utility does not support this feature. An interface for working with the administration server using Java is also implemented. The interface is distributed via ITS (together with its description and usage example) (http://its.1c.ru/db/metod81#content:4985:1).	Tools for 1C:Enterprise server cluster administration were only available for Windows operating system as a cluster administration console and as V82.ComConnector COM object. Linux tools for server cluster administration were not provided.	You can administer 1C:Enterprise server cluster using the command line in various operating systems (Windows and Linux), and also from Java programs.

Table of contents

Optimization

Functionality	After	Before	Result of changes
DBMS operations.	Optimized performance of Oracle DBMS queries that include complex conditions for data access restrictions.	Insufficient performance of queries that include complex conditions for data access restrictions.	Improved performance of operations with data access restrictions in Oracle Database.
Applied objects.	Working with memory is optimized for some mechanisms.	Insufficient performance in certain scenarios.	Improved overall system performance in some scenarios.
Queries.	When executing a query, for all IN HIERARCHY conditions with the same parameter value a single temporary table per batch query is generated.	When executing a query, for IN HIERARCHY conditions with the same parameter value several temporary tables were generated.	Improved the performance of queries containing the same parameter values in several IN HIERARCHY operations.
Queries.	When executing a query, for all IN conditions with the same list of values a single temporary table per batch query (for storing the list) is used.	When executing a query, for IN conditions with the same list of values several temporary tables were generated, one for each condition.	Improved the performance of queries containing the same list of values in several IN operations.
Queries.	Improved performance of queries that include the IN HIERARCHY expression. Improved performance of queries that include performing data composition system operations on external data sources by using the IN GROUP and IN GROUP FROM THE LIST expressions.	Insufficient performance of query and report selections in some cases when hierarchy conditions were used.	Improved performance of query and report selections in some cases when hierarchy conditions are used.
Server clusters. Client application.	The amount of memory consumed by server working processes is significantly reduced. Reduced client application startup time. The effect is especially noticeable on configurations having large volumes of metadata.	Inefficient use of memory on configurations having large volumes of metadata.	Memory requirements for servers with configurations having large volumes of metadata are reduced.
DBMS operations.	For PostgreSQL and Oracle Database, optimized recording register records with update of account register totals. The optimization is achieved by introducing a new index. The performance increase takes effect after restructuring accounting registers and disabling the compatibility mode.	The data structure did not allow using the existing indexes at their full potential, which led to insufficient system efficiency.	Improved performance of operations with accounting registers in PostgreSQL and Oracle Database DBMS.
DBMS operations.	Improved performance of requests to main tables when Oracle Database is used.	Response time for some DBMS requests was sub-optimal.	Improved performance of database requests. This includes a significant increase in the speed of configuration updates that require infobase structure updates.
DBMS operations.	Optimized some accounting register-related DBMS requests. In particular, optimized requests that include filters by account.	Inefficient usage of DBMS capabilities.	Improved performance for "heavy" accounting register requests (such as, when creating accounting reports or performing month-end closing).
DBMS operations.	Optimized operations with temporary tables in Microsoft SQL Server, as well as operations with objects that use temporary tables: accumulation registers, accounting registers, sequences, and so on.	Insufficient performance in case of heavy usage of temporary tables.	Improved performance in case of heavy usage of temporary tables in Microsoft SQL Server.
Web client.	Faster start of the web client on slow connections.	A large amount of service information was obtained during the start of the web client.	Faster start of the web client on slow connections.
DBMS operations.	Improved performance of operations with Microsoft SQL Server DBMS in the following cases: reading and writing data; loading infobase from the *.dt file (if the recovery mode is set to Simple or Bulk-logged); infobase restructuring (if the recovery mode is set to Simple or Bulk-logged).	Inefficient usage of DBMS capabilities.	Improved performance of operations with infobases that use Microsoft SQL Server DBMS.
Accounting registers.	Improved performance of accounting register operations in the following cases: writing record sets with up to ten records and with several hundred records; obtaining totals for a given time; generating reports that use the accounting register. The performance increase takes effect after infobase restructuring.	Insufficient performance of accounting register operations in certain use cases.	Improved performance of operations with accounting registers containing a large amount of data.
DBMS operations.	The performance of operations with PostgreSQL is improved by changing the index structure. The optimization applies both to new infobases and to existing ones (after restructuring their databases).	Cluster indexes were not used in PostgreSQL operations; regular indexes were created instead.	Faster execution of PostgreSQL operations.
DBMS operations.	You can use separate table spaces for indexes (the v81c_index space) and for data (the v81c_data space) in PostgreSQL. Table spaces are not created automatically; a database administrator creates them. If no additional table spaces are created, the default table space (pg_default) is used.	Using a single table space might decrease the performance (due to storage medium overload or performance limitations).	Balancing system performance by recording table spaces to multiple storage media in PostgreSQL.
Web client.	Faster opening of the following forms in the web client: Forms located on the main window tabs Forms that block windows of their owner forms	Delays when opening forms in the web client.	Faster form opening, which improves user experience.
Queries.	Improved performance retrieving a selection by group (with a large number of records) from a result of a query containing a TOTALS clause.	Insufficient performance when retrieving a selection by group from a result of a query that contains totals.	Improved performance when processing results of queries that contain totals.
Server clusters.	Improved server performance and scalability when processing reference data types.	Insufficient server performance when processing reference data types.	Improved server performance when processing reference data types.
DBMS operations.	Temporary tables containing data of unrestricted length are temporary in IBM DB2 version 8.7 and later.	For data of unrestricted length, permanent tables were created and then deleted after use.	System tables cannot get locked. Improved user experience in case when a large number of users are working simultaneously.
DBMS operations.	Certain operations with IBM DB2 are optimized.	Insufficient usage of IBM DB2 capabilities.	Faster execution of IBM DB2 operations.
DBMS operations. Accounting registers.	Faster processing of accounting register data during database configuration update in the client/server infobase mode.	Insufficient performance when reconfiguring accounting registers.	Faster processing of accounting register data during their reconfiguration.
Information registers.	Totals are implemented for periodic information registers. They are intended for retrieving first and last slices, provided that the following conditions are met: using totals is allowed (in metadata); using totals is enabled (in the 1C:Enterprise mode); slice retrieval conditions do not include date; slice retrieval conditions only include dimensions and separators; data access restrictions for the register only include dimensions and separators. Properties EnableTotalsSliceFirst and EnableTotalsSliceLast are implemented for information registers. Methods RecalcTotals(), SetTotalsUsing(), and GetTotalsUsing() are implemented for information register managers. Access right TotalsControl is implemented for information registers. The Verify and Repair action in Designer includes recalculation of first and last slices if the Recalculating totals option is enabled in the Verifications and modes list and using totals is enabled for the register.	Each slice retrieval resulted in execution of a query to the main register table, with calculation of resource values.	Faster retrieval of first and last slices for the first and the last (current) moments of time.
Development tools.	Optimized memory usage in the following cases: operations with configurations that are on support loading and dumping the 1cv8.dt file This change is not implemented in 8.2.16 compatibility mode.	In some cases working with configurations that are supported by vendor configurations of large size was impossible.	Reduced RAM usage when working with vendor configurations of large size.

Table of contents

Changes altering the system behavior

Functionality	After	Before	Result of change
DBMS operations.	If a database query contains more than 400 levels of expression nesting, an exception occurs but the system is not shut down. This change is not implemented in 8.2.16 compatibility mode.	If a database query contained more than 400 levels of expression nesting, the system performed emergency shutdown.	The system stability increased, preventing shutdowns when executing complex queries.
Attribute fill checks. Functional options.	Attributes disabled by a functional option are not included in the list of checked attributes of the FillCheckProcessingAtServer() handler. This change is not implemented in 8.2.16 compatibility mode.	When generating the list of checked attributes, functional options were not considered.	Application developers do not need to programmatically exclude attributes disabled by functional options from the check.
Queries.	If there is a list of totals with a grand total in the query result, unloading the query result using the Unload method (QueryResultIteration.ByGroups) of the QueryResult object results in a tree with a single node with the grand total, while nodes for groupings located in the query after the grand total become the tree elements. This change is not implemented in 8.2.16 compatibility mode.	If there was a list of totals with a grand total in the query result, unloading of the query result using the Unload method (QueryResultIteration.ByGroups) of the QueryResult object created a tree with several nodes of the same level: the grand total and groupings located in the query after the grand total.	The query behavior provides more comfortable work with totals when unloading the result to a tree.
Data composition system.	When a data composition result is exported to a collection of values, columns containing calculated fields will have value types specified in the calculated fields. If the calculated field value type is not specified, the value type for the corresponding column is determined automatically based on the calculated field expression. This change is not implemented in 8.2.16 compatibility mode.	When a data composition result was exported to a collection of values, the value types for columns that contained calculated fields were always determined automatically based on the calculated field expressions.	You can specify the calculated field type explicitly in cases when automatic type definition is difficult or impossible.
Client/server interaction.	When the server version is changed, sessions running at the time when the server manager is started are not deleted automatically. When a client application that uses a web server is shut down due to the client/server version difference exception, an attempt to delete the session at the server is made.	When the server version was changed, the message Session is missing or deleted was generated. Furthermore, users did not receive messages that clearly described the problem	When the platform version is changed at the server, users receive messages stating that the client application version and the server version differ (instead of the messages stating that the session is missing or deleted).
Configuration repositories.	Working with configuration repository is only possible if the repository version matches the Designer version.	The check whether the repository version matches Designer version was not performed.	Prevention of compatibility problems when the configuration repository server and Designer have different versions.
Configuration repositories.	When Designer operates in batch mode, if the location of the infobase that is bound to the repository is changed, the infobase is rebound to the repository and no warnings are displayed. When the location check is performed for the infobase bound to the repository, the name of computer from which the connection to the infobase in established is ignored for client/server infobases and for file infobases located on network drives.	In batch mode, a warning about the infobase location change was displayed and user response was expected. When the location check was performed for the infobase bound to the repository, the name of computer from which the connection to the infobase was established was taken into account for client/server infobases and file infobases located on network drives.	In batch mode, an attempt to access a copy of an infobase bound to the repository from the repository user account that is used for accessing the original infobase will lead to disconnecting the original infobase from the repository. A warning about the infobase location change is not displayed for client/server infobases and for file infobases located on network drives if the connections differ only by the name of computer from which the connection is established.
DBMS operations.	The following clustered indexes are created when using IBM DB2 DBMS: for object tables - primary key (reference); for tables of totals between accounts - by period; for information registers - Dimensions, Dimensions+Period, Recorder+Number, Dimensions+Period+Recorder+Number, and Dimensions+Period (depending on register type).	When using IBM DB2 DBMS the following indexes were created: for object tables - index by the primary key was not clustered; for tables of totals between accounts - no clustered index; for information registers - clustered indexes were used only in the following cases: Recorder, Dimensions, Dimensions+Period (depending on register type).	Unified approach to the implementation of object indexes in various DBMS.
Export to Microsoft Excel.	When a spreadsheet document is exported to Microsoft Excel 97 or Microsoft Excel 2007 format, cells of the spreadsheet document that are left-aligned are exported together with their general formatting. This change is not implemented in 8.2.16 compatibility mode.	When a spreadsheet document was exported to Microsoft Excel 97 or Microsoft Excel 2007, cell values were converted to numbers in the following cases: a number is recognized in the string content, and there is no text data after the number; a number is recognized in the string content, and text data is following it, but the cell is right- or center-aligned.	If a cell of a spreadsheet document contains a numeric value, which is intended to be used as text, and the value is left-aligned (e.g., the cell contains a product code or article), when the spreadsheet document is exported to Microsoft Excel format, the cell value is not converted to a number. This simplifies the use of the converted document (including editing and comparison).
1C:Enterprise script. Managed forms.	For methods GetForm(), OpenForm(), and OpenFormModal() the URL parameter is implemented. Its value is assigned to the URL property of received or opened forms, unless the parameter value is Undefined. Furthermore, the AutoURL property of received or opened forms is set to False. For the CommandExecuteParameters object the URL property is implemented. The property usage example is added to the command module example.	This feature was not provided.	You can specify a navigation link for a form that is being opened. The navigation link can be used later in the interactive mode (e.g., stored in the history).
Infobase users.	When you press Shift+Del in the list of infobase users, a warning is displayed.	Pressing Shift+Del in the list of infobase users deleted a user without a warning.	Prevention of accidental deletion of infobase users.
Software licensing.	If an application license is not found during the start of the application, the differences between the current hardware settings and hardware settings at the moment when the license was obtained are written to the license search log. This information is only written for software licenses.	Information on differences in hardware settings was not listed in the license search log.	Simplified diagnostics of software license problems when the license is not issued due to hardware settings differences.
DBMS operations. Managed locks.	When working with Microsoft SQL Server version 2005 or later, if the configuration uses the managed locks mode, row versioning is used. The READ_COMMITED_SNAPSHOT transaction isolation level is used. Consistent read is used for reading data outside of transactions.	Microsoft SQL Server 2005 and later was running in the lock mode. The READ_COMMITED transaction isolation level was used. "Dirty" read was used for reading outside of transactions.	The implemented modifications lead to: reducing the number of locks and deadlocks while executing transaction queries; elimination of errors when executing out-of-transaction queries involving frequently modified applied objects; obtaining consistent out-of-transaction report results at report execution time.
Managed forms. Data composition system.	You can implement quick choice user settings as a set of form fields in a separate group. You can manage location and other parameters of this group. The User settings group property is implemented for managed form extension for reports. You can create user settings items using the CreateUserSettingsFormElements() method of managed form extension for reports. Before settings elements are created, all existing elements are deleted from the group. Forms that are created automatically (report and user settings forms) include dedicated groups with elements used for editing settings. The OnUpdateUserSettingSetAtServer event is implemented for managed report form extension. The event is called in the following cases: when the report form is created; after the report variant is loaded; after the report variant is changed; after user modification of settings. Presentation of automatically generated report forms is changed: report variant presentation moved to report title; the variant selection button moved to report command bar, etc. This change is not implemented in 8.2.16 compatibility mode.	Quick choice user settings were edited in a special table located in the form. The form for editing user settings contained a table for editing all user settings. There was a field with current report presentation and a button for selecting report variant in the report form.	Improved report settings usability - they are displayed similarly to other form elements because standard form elements (text box, check box, etc.) are used instead of tables for editing settings.
Event log.	When event log is being read, events are not filtered by current separator value if the separator is conditionally disabled in the current session.	When event log was being read, records were filtered by value of a conditionally disabled separator.	Eliminated the differences between event log functioning in infobases without separators and infobases with conditionally disabled separators.
DBMS operations.	Internal implementation of several query executions for PostgreSQL, IBM DB2, and Oracle Database is modified. This change is not implemented in 8.2.16 compatibility mode.	The implementation took advantage of DBMS specifics to a lesser extent.	Improved the internal implementation of query executions for specific DBMS.
Command interface.	Navigation links to lists are implemented. A navigation link request to a form whose main attribute is a dynamic list with the main table specified returns a navigation link to the list of the object specified as the main table. This link opens the default list form. Support of navigation links to lists is implemented for the GotoURLGotoURL() global context method. This change is not implemented in 8.2.16 compatibility mode.	Navigation links to lists were not provided.	Users can store links to lists in history and favorites.
Configuration comparison reports.	The configuration comparison report no longer includes added and removed objects whose access rights exactly match their default access rights.	Added and removed objects whose access rights exactly matched their default access rights were included in the report.	The report no longer displays redundant information that does not help in merging data.
Third-party software.	Migrated from OpenSSL 1.0.1 to OpenSSL 1.0.0g.	OpenSSL version 1.0.1 was used.	An HTTP server query error is no longer displayed when the thin client is started.
Applied objects.	Value length for Description length and Order length properties of Chart of accounts objects is limited by 628 characters. The current value length is only checked when an attempt to change it is made.	Value length for Description length and Order length properties of Chart of accounts objects was not limited.	Increased platform stability. Prevention of infobase corruption (in the file mode). Prevention of performance losses.
Queries.	If a script generated by the query wizard includes result processing, the name of the variable where the result is stored is QueryResult. This change is not implemented in 8.2.16 compatibility mode.	In certain cases (for example, when a query was created with the option to display the processed result in a report), a naming conflict occurred between variable names created by the wizard and attribute names of the report form whose module contained this code. As a result, the generated code did not work properly.	Eliminated naming conflicts between variable names created by the query wizard and report form attribute names (for queries that include result processing).
Data composition system.	A query field used in a union operation becomes unavailable to filters if it has the NULL value in all parts of the union. This change is not implemented in 8.2.16 compatibility mode.	If a query field used in a union operation had the NULL value in all parts of the union, filters were applied at the data set level of data composition template, not inside the query.	When the UNION or UNION ALL expression is used in a query that retrieves a data set of the data composition system (with automatic filling of available settings), if a filter is applied to a field attribute, the filter is only applied to the parts of the union where the given attribute exists. When a filter is applied to a field, it is only applied to the parts where the field expression is not equal to NULL.
Event log.	The .elf extension is removed from the Files of type list in the open file dialog box in the thick client and Designer. Opening event logs in the .elf format is still supported. To open an .elf file, select the Event log (*.lgf) file type and then enter the file name, including the elf extension.	The list of file extensions in the open file dialog box in the thick client and Designer included both .lgf and .elf extensions.	Removed obsolete user interface options.
Event log. Data display.	Events related to canceled transactions are displayed in gray in the ordinary form of the event log (in the same way as they are displayed in the managed form of the event log). This change is not implemented in 8.1 compatibility mode.	Events related to canceled transactions were displayed in black in the ordinary form of the event log.	Unification of display of ordinary and managed forms of the event log.
Standard functions. Data display.	Object presentation in standard functions Find references to object and Delete marked objects is modified. Names of metadata objects types are removed from object presentations.	In standard functions Find references to object and Delete marked objects object presentation contained the name of metadata object type.	System-standard object presentation is introduced.
Accumulation registers. Accounting registers. Common attributes / Data separation. Server clusters.	Changes in the table of storage settings for accumulation and accounting register totals are performed within a transaction. While tables are being modified, managed data locks are applied to the corresponding lock namespace. A cache for storing totals storage settings for working processes is implemented.	Changes in the tables of storage settings for accumulation and accounting register totals were performed outside a transaction. Each retrieval of totals storage settings was performed using a database query.	Elimination of conflicts that might occur during the modification of totals storage settings tables from multiple simultaneous sessions that have identical data separator values. Reducing the number of database queries and improving parallel processing for sessions that use separators.
Common attributes / Data separation. Accounting registers. Accumulation registers.	If separators are deleted or separator types are modified, during the next update of database configuration records in the tables of totals storage settings for accounting and accumulation registers are merged according to the new sets of separators.	If separators were deleted or separator types were modified, the following situations might occur: Inserting records with identical values in a table of totals storage settings. Database update errors due to attempts to insert records with identical values.	Improved reliability of operations during database configuration updates caused by deleting separators or modifying separator types.
Text operations.	Implemented recording a byte order mark (BOM) to the beginning of files generated by the TextWriter object if the following conditions are met: the file to be recorded does not yet exist, the FinishWriter constructor parameter is set to True, and the text encoding is set to UTF-8. This change is not implemented in the compatibility with 8.2.16 mode.	A byte order mark (BOM) was not added to the beginning of files generated by the TextWriter object if the following conditions were met: the file to be recorded does not yet exist, the FinishWriter constructor parameter is set to True, and the text encoding is set to UTF-8.	A byte order mark (BOM) ensures unique identification of text encoding used in a file.
XML and XDTO support.	During the import of XSD schema, if definition is missing from the target namespace schema, a diagnostic message is displayed.	During the import of XSD schema, if any loading problems occurred, a diagnostic message was not displayed.	Improved diagnostics during XSD schema import.
DBMS operations.	The documentation describes the specifics of working with the following DBMS: Oracle Database and PostgreSQL.	The documentation did not contain enough details about the specifics of working with the following DBMS: Oracle Database and PostgreSQL.	Documentation is expanded to clarify DBMS usage specifics during configuration development.
Spreadsheet documents.	While you are changing the selection area in a spreadsheet document, if the selection area contains rows with different formatting, the platform switches to the row selection mode. Then, if the platform previously was in cell selection mode and after another selection change all selected rows have the same formatting, the platform switches back to the cell selection mode.	The only ways to select rows with different formatting were using headers of spreadsheet document rows or the Alt+Shift+Arrows key combination.	Simplified copying of data from spreadsheet documents with different row formatting.
Web client. Spreadsheet documents.	Users can edit spreadsheet documents in the web client. The Table main menu is modified in the web client. Clipboard is implemented for spreadsheet documents in Google Chrome web browser. The clipboard is available within a single browser instance working with a single infobase.	This feature was not provided (except editing cells with values, changing the display mode of groupings, freezing rows and columns, and changing column width).	Users can edit spreadsheet documents after they are generated in the web client.
Client application. Web client. Designer. Spreadsheet documents.	In the Table menu of thin client, web client, thick client, and Designer, the Cells submenu is implemented. It includes some of the commands that were previously located in the Table menu, and some new commands.	The Cells submenu was not available in the Table menu of thin client, web client, thick client, and Designer.	Improved usability of spreadsheet documents. Menu items intended for working with spreadsheet document cells are grouped into a single submenu.
Dynamic update.	Improved reliability of dynamic update in various situations.	In certain situations dynamic update worked improperly.	Improved reliability of dynamic update operations.
Managed forms.	If a width limit is set for a regular group in a managed form, the size of buttons within the group is adjusted (similar to adjusting the size of other elements included in the group).	A width limit set for a regular group might not affect the size of buttons within the group.	Unified the algorithm of adjusting element sizes when a width limit is set for a regular group.
Data display. Managed forms.	Tooltips of managed form items can have one of the following types: displayed directly in the text box, displayed near the form item, and opened clicking a button (in a pop-up window). If a tooltip is not specified for a form item, the command bar button linked to this item also does not have a tooltip. You can use the InputHint property, which contains tooltip text, to display a tooltip directly in the text box. This type of tooltip is unavailable for text boxes that display data of Number and Date types. To manage the display of tooltips and their appearance, the ExtendedTooltip and TooltipDisplay properties are implemented for the following form controls: field, table, group, button, and decoration of Text type.	Tooltips were only available in pop-up windows of form items. If a tooltip was not specified for a form item, its title was used as a tooltip for the command bar button linked to this item.	You can manage tooltip formatting and tooltip positions.

Table of contents

Changes that require changes to the configuration and administrative settings

Functionality	After	Before	Result of change
1C:Enterprise software system.	1C:Enterprise version is changed to 8.3. Installation directories are changed: For Windows: C:\Program Files\1cv8; For Linux: /opt/1С/v8.3. Names of installation files are changed: For Windows: 1CEnterprise 8.msi; For Linux: 1С_Enterprise83. Names of COM objects are changed: V83.Application, V83.ComConnector. The server service name is : For Windows: 1C:Enterprise 8.3 Server Agent; For Linux: srv1cv83. The default name of the user on whose behalf the server service starts is usr1cv8. Default template directory is changed: %APPDATA%\1C\1Cv8\tmplts. Add-in installation directory is changed: %APPDATA%\1C\1Cv8\ExCompT.	1C:Enterprise version was 8.2. Installation directories had the following names: For Windows: C:\Program Files\1cv82; For Linux: /opt/1С/v8.2. Installation files had the following names: For Windows: 1CEnterprise 8.2.msi; For Linux: 1С_Enterprise82. COM objects had the following names: : V82.Application, V82.ComConnector. The server service had the following name: For Windows: 1C:Enterprise 8.2 Server Agent; For Linux: srv1cv82. The default name of the user on whose behalf the server service started was usr1cv82. Default template directory was %APPDATA%\1C\1Cv82\tmplts. Add-ins installation directory was %APPDATA%\1C\1Cv82\ExCompT.	Due to the version number change, names and identifiers that include the version number are changed.
Applied objects.	In a document journal the attribute containing the document number is generated with fixed length if all documents included in the journal have a number field of String type of fixed length. Otherwise, the journal field will have variable length. This change is not implemented in 8.2.16 compatibility mode.	In a document journal the attribute containing the number of documents was always generated with fixed length.	The document number is retrieved in a uniform way, which does not depend on the retrieval method (from the document itself or from the document journal).
Spreadsheet documents.	When any of the spreadsheet document methods Show(), Print(), Hide(), and Write() is called at server or in an external connection with the SpreadsheetDocumentFileType parameter set to XLS95, an exception occurs. This change is not implemented in 8.2.16 compatibility mode.	When the method was called at server or in an external connection, this did not lead to an error, but the method did not perform any actions either.	Simplified detection of configuration errors related to specifying incorrect file type when working with a spreadsheet document at server or in an external connection.
Queries.	Specifying type qualifiers in the Type() function of the query language is not allowed. This change is not implemented in 8.2.16 compatibility mode.	Specifying type qualifiers for the Type() function was allowed, but it did not affect the returned values.	Implemented a check that eliminates the chance to misuse the query language syntax.
Spreadsheet documents.	Print scaling of a spreadsheet document does not affect its margin size. This change is not implemented in 8.2.16 compatibility mode.	Print scaling of a spreadsheet document affected its margin size.	Independent management of margin size and print scaling.
Data composition system.	When data composition result is put into a collection of values, fields belonging to different groups and referencing to the same data composition field are put in the same collection column. This change is not implemented in 8.2.16 compatibility mode.	When data composition result was put into a collection of values, fields belonging to different groups and referencing to the same data composition field were put in different collection columns.	Output of the result to a collection is performed in the same way as output of the result to a spreadsheet document.
Command interface. 1C:Enterprise script.	Format of navigation links to navigation points generated by standard command is modified to the following: e1cib/navigationpoint/Purchases/Catalog.Products.OpenList (example link). The former navigation link format is also supported. This change is not implemented in 8.2.16 compatibility mode.	Navigation links to navigation points generated by standard commands had the following format: e1cib/navigationpoint/Purchases/Catalog.Products.Command.OpenList (example link).	Unified usage of metadata names.
DBMS operations. External data sources.	If the Name in the data source property of an external data source field contains a value enclosed in single straight quotation marks, when a DBMS query is generated, this value is not enclosed in double straight quotation marks. Otherwise, if the field value contains special characters, it is enclosed in double straight quotation marks. This change is not implemented in 8.2.16 compatibility mode.	If the Name in the data source property of an external data source field contained special characters (including single straight quotation marks), the value was enclosed in double straight quotation marks.	Compatibility with DMBS that use different field description syntaxes in their query and database fields (for example, MySQL).
Software licensing.	The search for available licenses covers all folders where they might be located.	The search for available licenses only covered *.lic files stored in the first folder of the list and skipped any other folders where the license files might be located, regardless of whether the license was found in the first folder.	Increased flexibility of the licensing mechanism. Elimination of problems that occured when the license files were located in multiple folders (for example, the first folder that was searched contained a server license, while another folder contained a multiuser license).
Managed forms.	In managed forms, the platform does not read data from hidden dynamic lists. When a form is opened, the value of the CurrentRow attribute of the managed form table connected to the dynamic list is Undefined. The CurrentRow attribute value is changed at the moment when the table is displayed to the user. This change is not implemented in 8.2.16 compatibility mode.	In managed forms, the platform read data from all dynamic lists, whether they were displayed on the form or not.	Reduced time for opening forms that contain multiple pages with dynamic lists.
Functional options. Managed forms.	Behavior of the following form elements related to functional options is modified: Form attributes of reference type are disabled if configuration objects that determine their type are disabled by functional options. Form attributes of complex type are disabled if functional options disable all types that form the complex type. Form attributes of <Type>Object type (e.g., the main attribute of the form) are disabled if configuration objects that determine their type are disabled by functional options. Form tables are disabled if they display data belonging to attributes disabled by functional options. Types are not included in type selection dialogs (e.g., in text boxes connected with attributes of complex types) if configuration objects that determine these types are disabled by a functional option. Information on types disabled by functional options is cached at the client and is cleared in 20 minutes or when the RefreshInterface() method is called. This change is not implemented in 8.2.16 compatibility mode.	Attributes and form elements had the following behavior: Form attributes of reference type were not disabled when configuration objects that determined their type were disabled by functional options. Form attributes of <Type>Object type were not disabled if configuration objects that determined their type were disabled by functional options. Form tables were not disabled if they displayed data belonging to attributes disabled by functional options. Type selection dialogs contained all types, including those disabled by functional options.	Increased effect of default functional option values on the data composition system. Unification of functional option effect on various application elements.
Functional options. Data composition system.	Functional option effect on the data composition system is modified: A data composition system field becomes unavailable if it is connected to attributes whose types are disabled by functional options. A query table and attributes of this table become unavailable if a functional option disables the configuration object forming this table. This change is not implemented in 8.2.16 compatibility mode.	The data composition system did not disable fields or query tables connected to data whose type was disabled by functional options.	Increased automatic effect of functional options on the data composition system. Unification of functional option effect on various application elements.
Functional options. Command interface.	Commands of the command interface become unavailable in the following cases: An attribute, which is a command parameter, is disabled by a functional option. A command parameter type is disabled by a functional option. If the command parameter has complex type, the command becomes unavailable if all of the parameter types are disabled. This change is not implemented in 8.2.16 compatibility mode.	The command availability was not changed if the availability of the attribute, which was used as a parameter for the command, was changed, or when the command parameter type was disabled by a functional option.	Increased effect of functional options on the data composition system. Unification of functional option effect on various application elements.
Data composition system. Spreadsheet documents.	You can fix rows and columns of a spreadsheet document using the FixedLeft and FixedTop output parameters. If the fixed area exceeds the displayed area, the fixing is automatically turned off.	The data composition system always used fixing of rows and columns in reports. In spreadsheet documents the fixed area might be larger than the displayed area.	Improved usability of row and column fixing in reports. Users can disable fixing in reports when they find it inconvenient. Fixing is disabled automatically when it does not allow scrolling of the spreadsheet document.
Managed forms.	It is recommended that you use methods SetObjectAndFormConformity() and GetObjectAndFormConformity(). Methods SetObjectAndFormAttributeConformity() and GetObjectAndFormAttributeConformity() are declared deprecated, they are only supported for compatibility purposes.	Methods SetObjectAndFormAttributeConformity() and GetObjectAndFormAttributeConformity() were not declared deprecated.	New methods with enhanced functionality are implemented, while the old ones that provide similar functionality are declared deprecated.
Lock manager.	When using the Range object constructor, an exception is thrown if the left range boundary is greater than the right one. This change is not implemented in 8.2.16 compatibility mode.	Using the Range object constructor was allowed when the left boundary of the range was greater than the right one.	Elimination of unpredictable behavior of the managed locks manager. Elimination of developer errors.
Managed locks.	When a managed lock is set in the file mode of the infobase, types are validated for the values located in the DataSource attribute of the DataLockItem object. This change is not implemented in 8.2.16 compatibility mode.	Validation of the value types was not performed in the file mode.	Unified behavior in the file and client/server modes. Easier detections of errors in the applied solution.
1C:Enterprise script.	An attempt to assign a value to an item of a fixed structure causes an exception. This change is not implemented in 8.2.16 compatibility mode.	An attempt to assign a value to an item of a fixed structure did not cause an exception, and the value was not assigned.	Behavior of fixed structures is similar to behavior of other fixed collections.
Web client. System requirements.	Mozilla Firefox versions 3.0 and 3.5 are no longer supported.	Mozilla Firefox versions 3.0 and 3.5 were supported.	Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported.
Web client. System requirements.	Microsoft Internet Explorer version 6.0 is no longer supported. The warning that was displayed when the web client was started in Microsoft Internet Explorer 6.0 is changed to the warning about unsupported web browser.	Microsoft Internet Explorer version 6.0 was supported.	Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported.
Spreadsheet documents.	Whenever a spreadsheet document is transferred between the client and the server, the values of its ReadOnly and Protection properties are preserved. This change is not implemented in 8.2.16 compatibility mode.	Whenever a spreadsheet document was transferred between the client and the server, the values of its ReadOnly and Protection properties were set to False.	Whenever a spreadsheet document is transferred between the client and the server, its properties are preserved in a uniform way.
Formatted documents.	Formatted document object model is extended. The document text consists of paragraphs of various types, which are included in the paragraph collection. A paragraph consists of items included in the formatted document item collection. Functionalities for paragraph and item management are implemented. Methods GetItems() and GenerateItems() return the array of formatted document items located between the specified bookmarks. Method FindText() returns the formatted document area (FormattedDocumentRange object) that contains the specified text. The ItemType parameter type in methods Add() and Insert() of the FormattedDocument object was changed. Methods Add() and Insert() of the FormattedDocument object return the added/inserted item. You can add a picture by specifying its URL (in text format). It is recommended that you do not add or insert pictures using binary data, this options is present for compatibility purposes only. It is recommended that you use the Picture object for inserting pictures.	Formatted document text was not represented as an object model.	You can implement various text processing algorithms that are based on standard formatting elements (paragraphs, lists, and so on). Automated text generation is now simpler.
Data access restrictions.	If the Update right of an object includes data access restrictions with conditions that apply to tabular section attributes, writing the object after it was modified is only allowed if tabular section data before and after the modification match the data access restrictions. Requests from data access restrictions to tabular sections increase the processing time. This change is not implemented in 8.2.16 compatibility mode.	If the Update right of an object included data access restrictions with conditions that applied to tabular section attributes, then whenever tabular section attributes were modified, their compliance with the data access restrictions was not be verified.	Data access restrictions apply to object data and object tabular section data in a uniform way.
DBMS operations.	For complex Oracle Database queries of certain type, DBMS request generation rules are modified. Cases that led to DBMS errors are eliminated. A slowdown in DBMS request execution can occur if there are many join operations. It is recommended that you do not use queries with a large number of join operations. This change is not implemented in 8.2.16 compatibility mode.	When executing complex Oracle Database queries of certain type, DBMS errors might occur in some cases.	Improved stability when using Oracle Database.
Internet-enabled functionality.	You can use secure versions of SMTP and POP3. The following properties are implemented for the InternetMailProfile object: SMTPUseSSL, POP3UseSSL, IMAPSecureAuthenticationOnly, SMTPSecureAuthenticationOnly, and POP3SecureAuthenticationOnly. POP3 supports the GetMessageCount() method of the InternetMail object. It is recommended that you do not use SMTPAuthentication and POP3Authentication properties of theInternetMailProfile object, as well as SMTPAuthenticationMode and POP3AuthenticationMode enumerations. SMTPAuthentication and POP3Authentication properties, as well as SMTPAuthenticationMode and POP3AuthenticationMode enumerations are supported for compatibility. It is recommended that you use SMTPSecureAuthenticationOnly and POP3SecureAuthenticationOnly properties of the InternetMailProfile object.	The InternetMail object did not supportsecure versions of SMTP and POP3.	You can use secure versions of SMTP and POP3.
Internet-enabled functionality.	Default values are changed for InternetMailProfile object properties that store port numbers: The default SMTPPort value is 0, which means port 25 for nonsecure connections and port 465 for secure connections. The default POP3Port value is 0, which means port 110 for nonsecure connections and port 995 for secure connections. The default IMAPPort value is 0, which means port 143 for nonsecure connections and port 993 for secure connections. This change is not implemented in 8.2.16 compatibility mode.	The InternetMailProfile object properties that store port numbers had the following default values: SMTPPort - 25. POP3Port - 110. IMAPPort - 143.	Simplified port setup for the InternetMailProfile object. In most cases the default port values suffice.
Managed forms.	Changed the behavior of the drop-down list in form fields that contain reference data types, enumerations, or system enumerations. Changed the look and behavior of the drop-down list. The system storage settings now store the history of previously selected values (the ChoiceHistory setting). If user-generated lists, using a value of the FormattedString type as a value presentation is allowed. This change is not implemented in 8.2.16 compatibility mode.	The drop-down list had a different look and behavior. The choice list did not appear in the drop-down list.	Better usability of fields, which display data of reference types, enumerations, or system enumerations.
Linux.	The configuration utility for Linux is named config_system.	The configuration utility for Linux was named config_server.	The new utility name provides a better description of its purpose because it performs the environment check not only at the server side, but also at the client application side.
Administration.	The location.cfg configuration file stores the list of directories where 1C:Enterprise searches for system data. During the installation of version 8.3, the search for data (user profiles, configuration files, software license files, etc.) belonging to version 8.2 is performed in directories available to the current user. If directories with data belonging to version 8.2 are found, then location.cfg files are generated in the directories intended for storing data in version 8.3. These files contain links to directories with data from version 8.2. Therefore, installing the new version does not require transferring all data and settings from version 8.2 directories to version 8.3 directories.	This feature was not provided.	After installing version 8.3, you can use a single list of settings for version 8.2.16 and version 8.3.
Software licensing.	If the software license is activated "for all users" or using 1C:Enterprise server, the following directory is used for storing software licenses: on Windows: %ALLUSERSPROFILE%\Application Data\1C\licenses (%ALLUSERSPROFILE%\1C\licenses - for Windows Vista and later); on Linux: /var/1C/licenses. The directory is created during 1C:Enterprise installation. Rights for accessing the created directory are granted depending on the operating system being used: On Windows, read and write rights are granted to the user under whose account the server service runs. If the service is not installed, the rights for accessing the directory are not changed. On Linux, the user group grp1cv8 is created. All users under whose names the server daemon runs must be included into this group. The following rights are set for the created directory: owner - root, rights - read and write; owner group - grp1cv8, rights - read and write; other users are granted the read only right. Only users with administrative rights can obtain a client license "for all users".	The following directory was used for storing the software license files: on Windows: %ALLUSERSPROFILE%\Application Data\1C\1Cv82\Conf (%ALLUSERSPROFILE%\1C\1Cv82\Conf for Windows Vista and later); on Linux: ~/.1cv82/conf. On Windows, the directory was used when the software license was activated "for all users", and on Linux - when the software license was activated using 1C:Enterprise server.	Administration of software license files is made easier. 1C:Enteprise versions 8.2.16 and 8.3 can use the same set of licenses when their software licenses are activated "for all users" or using 1C:Enterprise server.
Server clusters. Administration tools.	The server cluster administration scheme is modified. The management of cluster processes and function distribution between these processes are performed automatically, and therefore the option to manage them manually is removed. You can affect the automatic distribution process by creating service cluster assignment rules or working server connection rules. The server cluster is functional until at least one working server marked as central server is running. The server cluster availability is defined by the Fault tolerance level parameter (the maximum number of working servers that can become unavailable without service interruption). In the cluster console, the server cluster is displayed by its name (the Cluster name property), not by its port. The software tools for administering server cluster version 8.3 are not compatible with the software tools for administering server cluster version 8.2. The SessionFaultToleranceLevel property is implemented for the IClusterInfo object. For the IWorkingServerInfo object the following properties are implemented: MainServer, ClusterMainPort, DedicatedManagers, InfoBasesPerWorkingProcessLimit, ConnectionsPerWorkingProcessLimit, and WorkingProcessMemoryLimit. The IAssignmentRule object is implemented, it allows to manage the functionality of working servers. The list of required functionality assignments is available via the IServerAgentConnection object and the cluster console. For the IServerAgentConnection object the following methods are implemented: RegAssignmentRule(), UnregAssignmentRule(), GetAssignmentRules(), CreateAssignmentRule(), and ApplyAssignmentRules(). The properties of IWorkingProcessInfo, IClusterManagerInfo, and IClusterServiceInfo objects are read-only. For the IServerAgentConnection object the following methods are removed: CreateWorkingProcessInfo(), RegWorkingProcess(), UnregWorkingProcess(), StartWorkingProcess(), StopWorkingProcess(), SetWorkingProcessUsage(), SetClusterMultiProcess(), SetWorkingProcessCapacity(), SetClusterDescription(), CreateClusterManagerInfo(), RegClusterManager(), UnregClusterManager(), RegClusterService(), UnregClusterService(), CreateStandbyClusterItem(), RegStandbyCluster(), UnregStandbyCluster(), and GetStandbyClusterList(). The IStandbyClusterItem object is deleted. The SyncPort property is deleted for the following objects: IWorkingProcessInfo, IClusterManagerInfo, IWorkingServerInfo, and IClusterInfo.	Management of cluster processes and function distribution between these processes could only be performed manually. The server cluster was displayed in the cluster console as a port number. The fault tolerance level could not be set.	Working processes are managed automatically, so that the load distribution in the server cluster is improved. At the same time, an administrator can specify working servers where certain cluster services or connections will be executed (using rules). For example, they can move the license management service to a separate working server with minimal configuration changes, or execute certain background jobs at the working server that is running Windows operating system.
Server clusters.	On Linux operating system, a server is not automatically started after it is installed.	On Linux operating system, servers were automatically started after they were installed.	A server is not started in the environment that is not fully configured. To configure the environment, you have to run the config_system utility first, and then you can start the server.

Table of contents

Renamed objects

Object	The old name	The new name
Column groups in the user settings table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1.	<Table name>ColumnGroupSettings; <Table name>ColumnGroupValues.
Column groups in the data parameters table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1; <Table name>ColumnGroup2; <Table name>ColumnGroup3.	<Table name>ColumnGroupParameterAndPeriodValue; <Table name>ColumnGroupParameter; <Table name>ColumnGroupPeriodValue; <Table name>ColumnGroupParameterValue.
A column group in the available fields table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupAvailableField.
Column groups in the group fields table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1; <Table name>ColumnGroup2; <Table name>ColumnGroup3; <Table name>ColumnGroup4; <Table name>ColumnGroup5.	<Table name>ColumnGroupGroupField; <Table name>ColumnGroupFieldAndType; <Table name>ColumnGroupPeriod; <Table name>ColumnGroupField; <Table name>ColumnGroupBeginOfPeriod; <Table name>ColumnGroupEndOfPeriod.
Column groups in the selected fields table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1; <Table name>ColumnGroup3; <Table name>ColumnGroup2.	<Table name>ColumnGroupSelectedField; <Table name>ColumnGroupHeaderAndPlacement; <Table name>ColumnGroupHeader; <Table name>ColumnGroupField.
Column groups in the filter table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup2; <Table name>ColumnGroup3; <Table name>ColumnGroup4; <Table name>ColumnGroup1.	<Table name>ColumnGroupFilter; <Table name>ColumnGroupMainFilterItems; <Table name>ColumnGroupLeftValue; <Table name>ColumnGroupRightValue; <Table name>ColumnGroupApplication.
A column group in the order table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupField.
Column groups in the output parameters table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1; <Table name>ColumnGroup2; <Table name>ColumnGroup3.	<Table name>ColumnGroupParameterAndPeriodValue; <Table name>ColumnGroupParameter; <Table name>ColumnGroupParameterValue; <Table name>ColumnGroupParameter.
A column group in the user field case variants table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupValue.
A column group in the appearance fields table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupField.
A column group in the gauge chart quality bands table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupBackColor.
Column groups in the filter conditions table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1.	<Table name>ColumnGroupValueAndPeriod; <Table name>ColumnGroupPeriod.
Column groups in the report variant form elements of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	GoToReportSelectedFields1; GoToReportFilter1; GoToReportOrder1; GoToReportConditionalAppearance1; GoToReportOutputParameters1.	GoToReportSelectedFieldsFromInaccessibleSelectedFields; GoToReportFilterFromInaccessibleFilter; GoToReportOrderFromInaccessibleOrder; GoToReportConditionalAppearanceFromInaccessibleConditionalAppearance; GoToReportOutputParametersFromInaccessibleOutputParameters.
Russian presentation for the ReportSettings command of the report form is changed.	Настройка ....	Настройки ....
English and Russian presentations for the LoadReportSettings command of the report form are changed.	Select setting .... Выбрать настройку ...	Select settings .... Выбрать настройки ...
English and Russian presentations for the SaveReportSettings command of the report form are changed.	Save setting ... Сохранить настройку ...	Save settings ... Сохранить настройки ...
Presentation of the StandardSettings command in the report variant form is modified.	Standard setting.	Standard settings.
Field containing name of saved settings in the Save settings dialog is changed.	Name of saved setting.	Name of saved settings.

Table of contents

Upgrade from the previous version to version 8.3.1

Conversion of configurations, infobases, external data processors, and external reports is not required during the upgrade from the previous version to version 8.3.1.
To use certain features of version 8.3.1 you have to disable the compatibility mode. The structure of certain objects is modified when disabling or enabling the compatibility mode. Note that to be able to work with infobases created using previous 1C:Enterprise versions you have to enable the compatibility mode. In order to use certain optimization improvements, you have to restructure data related to the optimization areas. To restructure data, you can use the Verify and repair mode, or perform forced object restructuring.
It is recommended that you revise the list of infobases. Infobases that are present in the list when version 8.3 is installed in most cases have version 8.2 or 8.1 (because it is the default version, which is set automatically when an infobase is created or added to the list). Therefore, in order to open an infobase in 8.3, you have to specify the required version in the list of infobase startup settings, or specify the version directly in the infobase settings.
At the first start of server cluster version 8.3.1 on the computer hat has previous versions of ther server cluster installed, the content of the cluster register file(1CV8Reg.lst) is converted to a new format. The register of the server cluster 8.3.1 is stored in the file 1CV8Clst.lst, in the same directory as the cluster register of the previous versions. There is no data synchronization between cluster registers of different versions after the first start of server cluster 8.3.1.
To perforrm the conversion of the cluster register from version 8.2. to version 8.3 once more, stop the server cluster 8.3, delete the server cluster 8.3 register (the 1CV8Clst.lst file), and then start the server cluster 8.3.

Table of contents

Functionality	After	Before	Result of changes
DBMS operations. Queries.	In applications that use PostgreSQL DBMS, the conversion of LIKE `TEXT%` query language operation to an SQL query operation is optimized. This change is not implemented in 8.3.10 compatibility mode.	In applications that used PostgreSQL DBMS, the conversion of LIKE `TEXT%` query language operation to an SQL query operation was not optimal.	In applications that use PostgreSQL DBMS, improved performance of search by beginning of a string in the query language.
Full-text search.	The access rights verification for full-text search results is optimized in scenarios where the search returns over 100 results. This change is not implemented in 8.3.10 compatibility mode.	The performance of access rights verification for full-text search results in scenarios where the search returned over 100 results was insufficient.	Reduced time of getting full-text search results for users with access right restrictions in scenarios where the search returns over 100 results.
Spreadsheet documents.	The performance of CheckPut() method of spreadsheet document is improved.	The performance of CheckPut() method of spreadsheet document was insufficient.	Faster data output to a spreadsheet document in scenarios that include the check whether the output area fits a single page.
External reports and data processors. Server clusters. Client application.	Improved performance of loading external reports and data processors in client applications and on 1C:Enterprise server. Intensive work with external reports and data processors does not cause lags.	The performance of loading external reports and data processors in client applications and on 1C:Enterprise server was insufficient. Intensive work with external reports and data processors caused lags.	Eliminated 1C:Enterprise server lags in scenarios that involve inrtensive work with external reports and data processors.
Internet-enabled functionality.	Improved 1C:Enterprise performance and scalability in scenarios that involve using HTTPConnection and FTPConnection objects on 1C:Enterprise server (if these connections belong to different sessions).	1C:Enterprise performance was significantly reduced in scenarios that involved using HTTPConnection and FTPConnection objects on 1C:Enterprise server (if these connections belonged to different sessions).	Improved 1C:Enterprise server performance in scenarios that involve multiple HTTP or FTP connections from different sessions.
DBMS operations.	Improved performance of operations with temporary tables in scenarios that involve the following Microsoft SQL Server versions: 2012, version 11.0.5548.0 or earlier 2014, version 12.0.2430.0 or earlier 2016	The performance of operations with temporary tables in scenarios that involved some Microsoft SQL Server versions was insufficient.	Improved performance of operations with temporary tables in scenarios that involve some Microsoft SQL Server versions.
Cryptography support. Internet-enabled functionality.	On Windows, improved the performance of cryptography operations and operations over SSL and TLS protocols in scenarios where these operations are running simultaneously in a large number of sessions.	On Windows, the performance of cryptography operations and operations over SSL and TLS protocols was insufficient in scenarios where these operations were running simultaneously in a large number of sessions.	On Windows, improved the performance of cryptography operations and operations over SSL and TLS protocols in scenarios where these operations are running simultaneously in a large number of sessions.
Background and scheduled jobs. Configuration extensions.	The performance of starting background jobs is improved in infobases that run in file mode and use extensions.	The performance of starting background jobs in infobases that ran in file mode and used extensions was insufficient.	Eliminated unexpected system behavior.
Development tools.	The performance of the following Designer operations is improved: Opening 1C:Enterprise script editor Extended module check	The performance of the following Designer operations was insufficient: Opening 1C:Enterprise script editor Extended module check	Improved perfromance of frequently used development tools.
System requirements.	The size of executable files of 1C:Enterprise is reduced.	Executable files of 1C:Enterprise required more disk space.	Reduced 1C:Enterprise requirements to available disk space.
Development tools.	In 1C:Enterprise script editor, the performance of the following operations is improved: Opening large modules Opening context help Switching to method or variable declaration Module syntax check	For large modules, the performance of 1C:Enterprise script editor was insufficient.	Improved usability for application developers.
Infobase operations.	Improved the performance of loading infobases from .dt files in systems that use IBM DB2.	Loading infobases from .dt files in systems that used IBM DB2 took more time.	Reduced time of moving infobases in systems that use IBM DB2.
Managed locks. Server clusters.	The 1C:Enterprise server performance in scenarios with simultaneous posting of large documents (dozens of thousands of lines) is improved.	Simultaneous posting of large documents (dozens of thousands of lines) could hang the server cluster.	Improved performance of 1C:Enterprise server under heavy load.
Spreadsheet documents.	The performance of drawing spreadsheet documents with a lot of pictures in hidden rows is improved.	Drawing spreadsheet documents with a lot of pictures in hidden rows took more time.	Improved performance of operations with spreadsheet documents that contain a lot of pictures in hidden rows.
DBMS operations.	Optimized operations with large temporary tables in PostgreSQL.	The performance of operations with large temporary tables in PostgreSQL was insufficient.	Improved performance of operations with large temporary tables in PostgreSQL.
DBMS operations.	Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized.	The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient.	Improved performance of temporary table operations.
Infobase operations.	In file infobases that contain large amounts of metadata, improved performance of metadata restructuring. The performance of restructuring data tables has not changed.	In file infobases that contained large amounts of metadata, metadata resturcturing took more time.	If a configuration contains a large amount of metadata and its metadata structure has changed, the performance of restructuring file infobases based on this configuration is improved.

Functionality	After	Before	Result of changes
Internet-enabled functionality. Web client. System requirements.	The web client no longer supports Microsoft Internet Explorer versions 8 and 9.	The web client supported Microsoft Internet Explorer versions 8 and 9.	Legacy versions of Microsoft web browser are no longer supported.
1C:Enterprise script. Development tools.	In the thin and web clients, detection of attempts to assign a value to a nondeclared variable whose name matches a common module name is implemented. As a result, in this scenario the value is not assigned and an error message is generated. This change is not implemented in 8.3.10 compatibility mode.	In the thin and web clients, attempts to assign a value to a nondeclared variable whose name matched a common module name were not detected. In the web client, this caused an unexpected shutdown of the client application.	Eliminated unexpected system behavior.
Queries.	The Move() method of QuerySchemaQueryBatch, QuerySchemaOperators, QuerySchemaColumns, QuerySchemaIndexExpressions, QuerySchemaOrderExpressions, and QuerySchemaTotalCalculationFields objects shifts the specified collection element by the specified number of positions. This change is not implemented in 8.3.10 compatibility mode.	The behavior of the Move() method was different from the standard one: For QuerySchemaQueryBatch and QuerySchemaOperators objects, the method moved the element found by index specified in the first parameter to the position that was calculated as a maximum of the first and second parameters. For QuerySchemaColumns, QuerySchemaIndexExpressions, QuerySchemaOrderExpressions, and QuerySchemaTotalCalculationFields objects, the method moved the element found by index specified in the first parameter to the position specified in the second method parameter.	The behavior of the Move() methods is unified with the behavior of Move() methods in other collections.
Managed forms. Dynamic lists. Access rights.	If the current user does not have enough rights to access form items related to table or form extensions for dynamic lists, the items are hidden, regardless of the method used to add them (added explicitly by application developers or automatically by the extensions). This change is not implemented in 8.3.10 compatibility mode.	If the current user did not have enough rights to access form items related to table or form extensions for dynamic lists, the items were hidden only if they were added automatically by the extensions. If they were added explicitly by application developers, they were still visible (but not available to the user). This was applicable to the following commands: The Edit command (if the main dynamic list table was a filter criterion). The Delete command (if the main dynamic list table was an external data source table). The OutputList, SaveDynamicListSettings, and LoadDynamicListSettings commands of any dynamic list.	Eliminated unexpected system behavior.
Dynamic lists.	You can hide folder pictures in hierarchical dynamic lists. To hide the pictures, clear the RowPictureDataPath property of the table that displays the hierarchical dynamic list. This change is not implemented in 8.3.10 compatibility mode.	Hiding folder pictures in hierarchical dynamic lists was not available. Clearing the RowPictureDataPath property of the table that displayed the hierarchical dynamic list did not hide the pictures.	Eliminated unexpected system behavior.
Client application installation.	The timeout for downloading a client application distribution kit over HTTP is removed. You can cancel downloading by clicking Cancel in the dialog box that displays the progress.	Downloading a client application distribution kit over HTTP was terminated if it took more than 600 seconds.	Downloading a client application distribution kit using a slow connection channel is now possible.
Common objects.	In the TextReader object constructor, if LineSplitter parameter is omitted, this is treated as setting it to Chars.LF. If ConvertibleSplitterOfLines parameter is omitted, this is treated as setting it to Chars.LF + Chars.CR. This change is not implemented in 8.3.10 compatibility mode.	In the TextReader object constructor, if LineSplitter or ConvertibleSplitterOfLines parameter was omitted, this was treated as setting it to a blank string.	Eliminated unexpected system behavior. The values of omitted parameters now match the Syntax Assistant descriptions.
Infobase operations.	A composite index that includes attributes with Index property set to Index with additional ordering no longer depends on the attribute order. The order of the atttributes in the index is fixed. The index is rebuilt during the first object restructuring after disabling compatibility mode. This change is not implemented in 8.3.10 compatibility mode.	A composite index that included attributes with Index property set to Index with additional ordering depended on the attribute order. If the order was changed, the platform rebuilt the index.	The effect of the attribute order on the database index structure is reduced.
Queries.	The attempt to execute a query that contains MIN() or MAX() aggregate function with the following parameter types generates an error: UUID and system enumeration UUID and any primitive type System enumeration and any primitive type This change is not implemented in 8.3.10 compatibility mode.	The attempt to execute a query that contained MIN() or MAX() aggregate function with the following parameter types did not generate an error: UUID and system enumeration UUID and any primitive type System enumeration and any primitive type Such a query might return an incorrect result or cause an unexpected shutdown.	Eliminated unexpected system behavior.
Queries.	A query that contains ISNULL() or CASE() operation that applies to result of MAX() or MIN() function (provided that parameters of these functions include values of UUID type or system enumerations, and provided that the other operand of ISNULL() or CASE() is a value of primitive type or another system enumeration) returns the correct result. This change is not implemented in 8.3.10 compatibility mode.	A query that contained ISNULL() or CASE() operation that applied to result of MAX() or MIN() function (provided that parameters of these functions included values of UUID type or system enumerations, and provided that the other operand of ISNULL() or CASE() was a value of primitive type or another system enumeration) returned UNDEFINED.	Eliminated unexpected system behavior.
Charts.	In charts that use the default palette, the default colors of chart scales and series are changed. New system enumeration value is implemented: ChartColorPalette.SoftAdaptive. This change is not implemented in 8.3.10 compatibility mode.	In charts that used the default palette, the default colors of chart scales and series were different.	Imoroved view of charts with default settings.
Managed forms.	In the standard processing of a ChoiceDataGetProcessing event handler of configuration object managers, correct handling of Undefined value of Parameters.SearchString parameter is implemented. If this value is set to Undefined, the system behavior is similar to quick choice, it returns the list of all database items for this configuration object. This change is not implemented in 8.3.10 compatibility mode.	In the standard processing of a ChoiceDataGetProcessing event handler of configuration object managers, if Parameters.SearchString parameter was set to Undefined, it was treated as an empty search string.	Eliminated unexpected system behavior.
Queries.	In the Parameters collection of the Query object, the parameter type used in a comparison operation (>, >=, <, <=, =, <>) applies to both operation parameters, however, their type qualifiers do not have to be identical. For example, if the first parameter is a string, you can specify a string of unlimited length as a second parameter. This change is not implemented in 8.3.10 compatibility mode.	In the Parameters collection of the Query object, the parameter type used in a comparison operation (>, >=, <, <=, =, <>) and its type qualifier were applied to both operation parameters.	Eliminated unexpected system behavior.
Data composition system.	When you add a condition with Empty comparison type to a query, the data composition system adds the condition to a nested query in the right part of a left join only if it cannot add the condition to the parent query. Otherwise, it never adds such conditions to nested queries. This change is not implemented in 8.3.10 compatibility mode.	When a condition was added to a query, the data composition system always attempted to add the condition to a nested query. If the nested query was located in the right part of a left join, the condition was duplicated in the parent query.	When a query includes a nested query located in the right part of a left join, the data composition system provides a more predictable result.
File operations.	The CreateDirectory() and BeginCreatingDirectory() methods generate exceptions if the directory name contains invalid characters. This change is not implemented in 8.3.10 compatibility mode.	The CreateDirectory() and BeginCreatingDirectory() methods did not analyze the directory name. If the directory name contained invalid characters, the directory was not created and no error messages were generated.	1C:Enterprise checks whether the names of directories to be created are valid.
Managed forms.	A managed form group with HorizontalAlignInGroup property set to Center is centered relative to the parent group. This change is not implemented in 8.3.10 compatibility mode.	A managed form group with HorizontalAlignInGroup property set to Center was aligned left relative to the parent group.	Eliminated unexpected system behavior.
Managed forms.	If ShapeRepresentation property of a managed form button is set to None and its BackColor property is set to any value except Auto, the button has transparent background. This change is not implemented in 8.3.10 compatibility mode.	If ShapeRepresentation property of a managed form button was set to None and its BackColor property was set to any value except Auto, the button background color was taken from the BackColor property.	Eliminated unexpected system behavior.
Web client, web service, and HTTP service publishing tools.	If an application is published to a web server using webinst utility with -descriptor option, the pubdst, pubdst32, and pubdst64 attributes of the root point element are copied from the publication template to the resulting default.vrd file.	If an application was published to a web server using webinst utility with -descriptor option, the pubdst, pubdst32, and pubdst64 attributes of the root point element were not copied from the publication template to the resulting default.vrd file.	Eliminated unexpected system behavior.
Documentation.	The description of SessionParameters.Clear() method in Syntax Assistant now states that calling this method requires the right to change all session parameters that are used in the method (possibly all parameters available in the session).	The description of SessionParameters.Clear() method in Syntax Assistant was incorrect.	The Syntax Assistant topic is now up-to-date.
Managed forms.	If a managed form attribute is created using 1C:Enterprise script, it can be accessed only with ThisObject. prefix. This change is not implemented in 8.3.10 compatibility mode.	In some scenarios, managed form attributes created using 1C:Enterprise script could be accessed without ThisObject. prefix.	Eliminated unexpected system behavior.
Administration tools.	New version of Java-based 1C:Enterprise Administrative Service API, which is compatible with 1C:Enterprise 8.3.11, is available (read more).	The previous version of Java-based 1C:Enterprise Administrative Service API was compatible with 1C:Enterprise versions 8.3.10 and earlier.	You can select Java-based 1C:Enterprise Administrative Service API version that is compatible with your 1C:Enterprise version.
System requirements.	The minimum system requirements for some operating systems of Windows family have changed: Windows XP Service Pack 3 Windows Vista Service Pack 2 Windows 7 Service Pack 1 Windows Server 2008 Service Pack 2 Windows Server 2008R2 Service Pack 1 The system requirements for other Windows versions have not changed. If an operating system does not match the requirements, 1C:Enterprise generates a warning with a recommendation to install the required update. If you choose the installation option that does not have user interface and the operating system does not match the requirements, the cluster console and the COM connection module are not registered. 1C:Enterprise distribution package for Windows includes Visual C++ Redistributable for Visual Studio 2015. 1CEClientMakeSetup utility requires Visual C++ Redistributable to generate distribution packages for platform versions 8.3.11 and later.	The minimum system requirements for some operating systems of Windows family were: Windows XP Service Pack 3 (the installer did not check whether the service pack was installed) Windows Vista Windows 7 Windows Server 2008 Windows Server 2008R2	The platform installer installs the required redistributables and displays warnings about unsupported operating systems.
System requirements. Administration.	1C:Enterprise distribution packages for Windows and macOS include HASP Device Driver 7.60.	1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 6.60.	1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver.

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.
Web services and HTTP services.	Every time a method of a web or HTTP service is called, the compiled service module is cashed.	Every time a method of a web or HTTP service was called, the service module was compiled.	Improved system performace in scenarios that include a large number of web or HTTP services calls.
Accounting registers. DBMS operations.	Improved performance of the following accounting register record set operations for infobases running in file mode or in client/server mode with PostgreSQL: Write a record set Read a record set Open a record set form	The performance of the following accounting register record set operations was insufficient in infobases running in file mode or in client/server mode with PostgreSQL: Write a record set Read a record set Open a record set form	Optimized accounting register operations for some DBMS.
DBMS operations.	Optimized query plan generation for PostgreSQL version 9.6.3. This improves the performance of complex queries that use data access restriction templates. Optimization is available for PostgreSQL versions 9.6.3-2.1C and later.	In PostgreSQL, performance of complex queries that used data access restriction templates was insufficient, in some cases applications might stop responding during query execution.	Improved performance of PostgreSQL operations initiated from 1C:Enterprise.

Functionality	After	Before	Result of changes
Internet-enabled functionality.	The NSSSecureConnection object and NSS certificates cannot be accessed from 1C:Enterprise script. This change is not implemented in 8.3.6 compatibility mode.	1C:Enterprise system supported NSS certificates.	Future platform versions will not support NSS certificates.
Common objects.	In the thin client, the ValueStorage.Get() method raises an exception. This change is not implemented in 8.3.6 compatibility mode.	In the thin client, the ValueStorage.Get() method did not raise an exception and returned the Undefined value instead. Running this method in the web client raised an exception.	Uniform system behavior across multiple client applications.
Interface. Managed forms.	The choice history generation rules for managed form text boxes are modified. In particular, the frequency of history item usage is taken into account. The history consists of up to 7 items, which include both frequently used and last used values. The history generation rules are described in detail in the documentation. The system storage of managed form text box choice history stores a value of the ChoiceHistorySettings type. This change is not implemented in 8.3.6 compatibility mode.	The choice history generation rules for managed form text boxes were different. The history stored 5 last values. The system storage of managed form text box choice history stored a value of the Array type.	Improved usability of managed form text box choice history.
Managed forms.	New algorithm for automatic arrangement of managed form items is implemented. As a result, item positioning is improved, new item placement options are added, changing some item properties on the client does not require a server call (this includes expanding or collapsing groups and showing or hiding form item addition extension for view status), rules for automatic generation of form separators are modified, and more. In many cases toggling form item visibility no longer requires a server call. Detailed description of this feature is provided in the documentation. In the managed form editor, quick preview of a form with specific screen resolution and specific screen orientation is available. For the ChildFormItemsGroup system enumeration, the HorizontalIfPossible value is implemented. The AutoMaxWidth, MaxWidth, AutoMaxHeight, and MaxHeight properties are implemented for the following objects: managed form field extension for a label field, text box, picture field, spreadsheet document field, text document field, formatted document field, calendar field, progress bar field, track bar field, chart field, Gantt chart field, dendrogram field, geographical schema field, HTML document field, graphical schema field, period field, planner field, and for managed form items of table, decoration, and button types. For managed form items of form, group, and page types the following properties are implemented: HorizontalSpacing, VerticalSpacing, ItemsAndTitlesAlign, ChildItemsHorizontalAlign, and ChildItemsVerticalAlign. For managed form fields of field, table, decoration, group, button, and addition types, the HorizontalAlignInGroup and VerticalAlignInGroup properties are implemented. For managed form item addition extensions for search string, search control, and view status, the AutoMaxWidth and MaxWidth properties are implemented. For managed form groups, the ThroughAlign property is implemented. For the VerticalFormScroll system enumeration, the UseWithoutStretch value is implemented. For managed form group extension for a usual group, the United property is implemented. For managed form group extension for a page, the VerticalScrollOnReduceSize property is implemented. This change is not implemented in 8.3.6 compatibility mode. The HorizontalStretch and VerticalStretch properties are implemented for the following objects: managed form extensions for graphical schema field and HTML document field, and managed form buttons. For managed form item addition extension for search control, the HorizontalStretch property is implemented. The ChildFormItemsWidth property of form, page, and usual group objects is obsolete and only supported in version 8.3.6 compatibility mode. In configurations that do not use compatibility mode, this property is ignored.	A different algorithm was used for arranging managed form items.	In managed forms, automatic item arrangement is revised. New arrangement options are available. Several known managed form issues are eliminated.
Web services and HTTP services.	If a configuration includes HTTP services, saving a configuration with compatibility mode lower than Version 8.3.5 is not allowed.	Saving configurations was performed without checking the correspondence between configuration compatibility mode and the availability of HTTP services in the configuration.	Eliminated unexpected system behavior.
Common objects.	Synchronous call usage mode for extensions and add-ins configuration property value is taken into account by the following methods: Read() method of theTextDocument object Write() method of theTextDocument, SpreadsheetDocument, FormattedDocument, and GraphicalSchema objects WriteFileForPrinting() method of the RepresentableDocumentBatch object	The Synchronous call usage mode for extensions and add-ins configuration property was ignored by the listed methods.	Eliminated unexpected system behavior.
Server cluster.	The following background job names are used for specifying requirements of functionality purposes: Scheduled job: BackgroundJob.ScheduledJob.<Metadata object name>. Input by string: BackgroundJob.InputByString.<Full metadata object name>. Report: BackgroundJob.GenerateReport.<Full report metadata object name>. External report: BackgroundJob.GenerateReport.<Full report metadata object name>. Search in list: BackgroundJob.DynamicListSearch.<Full form name>.<Name of form table linked to the list>. Background restructuring: SystemBackgroundJob.DBConfigUpdate. This change is not implemented in 8.3.6 compatibility mode.	The following background job names were used for specifying requirements of functionality purposes: Background job: BackgroundJob.CommonModule.<Module name>.<Method name>. Input by string: BackgroundJob.SystemBackgroundJob. Report: BackgroundJob.Report. External report: BackgroundJob.Report. Search in list: BackgroundJob.SystemBackgroundJob. Background restructuring: SystemBackgroundJob.	Background job names comply with the internal platform requirements, Background job names are more precise.
Queries.	The ValueType() query language function returns UNDEFINED when UNDEFINED is passed as the function parameter. This change is not implemented in 8.3.6 compatibility mode.	The ValueType() query language function returned NULL when UNDEFINED was passed as the function parameter.	Eliminated unexpected system behavior.
Server cluster.	You can restrict access to cryptography features using security profiles. For ISecurityProfile object, the CryptographyAllowed property is implemented (programmed administration of server clusters using COM objects). For ISecurityProfile object, the getCryptographyAllowed() and setCryptographyAllowed() methods are implemented (Java server administration interface). For the server cluster command-line utility (rac) the crypto parameter for the profile command is implemented. This change is not implemented in 8.3.6 compatibility mode.	The option to restrict access to cryptography features using security profiles was not provided.	Extended security profile capabilities.
Access rights.	The access rights check for document journal graph attributes performed using the AccessRight() method with User/Role parameter specified takes into account the availability of all objects included in the journal graph content. The AccessRight() result is cached by the platform, which is similar to caching reusable return values. This change is not implemented in 8.3.6 compatibility mode.	The access rights check for document journal graph attributes performed using the AccessRight() method with User/Role parameter specified did not take into account the availability of all objects included in the journal graph content. The AccessRight() result was not cached by the platform.	Eliminated unexpected system behavior. Improved performance of access rights check for applied solutions with a large number of roles, and for file mode infobases on low-performance computers. This improves the performance of form opening in the listed scenarios.
Localization.	The option to specify the first day of the week is implemented. It can be accessed in Designer (on the Administration menu, click Regional infobase settings). When you create an infobase using platform version 8.3.7 or later without compatibility mode set, the first day of the week value is set to Auto. It is defined based on the Language (Country) property in regional infobase settings. The choice of the first day of the week affects the following features: 1C:Enterprise script methods: BegOfWeek(), EndOfWeek(), WeekOfYear() Query language functions: BeginOfPeriod(), EndOfPeriod(), Week() Data composition system functions: BeginOfPeriod(), EndOfPeriod(), Week(), and functions of nested fields of Date type: BegOfWeek, EndOfWeek, WeekOfYear Scheduled job schedules Balance virtual tables and balance and turnover virtual tables of accumulation registers Balance virtual tables and balance and turnover virtual tables of accounting registers This change is not implemented in 8.3.6 compatibility mode.	The first day of the week was always Monday.	Better usability in countries where the first day of the week in not Monday.
Spreadsheet documents.	You can edit multilingual spreadsheet documents in managed forms, provided that these documents are templates. The list of languages is obtained directly from a template. In managed forms, spreadsheet documents are edited and displayed using the language specified in the LanguageCode spreadsheet document property. Strings in other languages are never changed. The SpreadsheetDocument.Template property is implemented. This change is not implemented in 8.3.6 compatibility mode. The FillPropertyValues() method never copies the Template property (regardless of the compatibility mode).	In managed forms, spreadsheet documents were always edited using the current language. When the platform displayed a spreadsheet document: The thin client did not use the LanguageCode property. The web client used the LanguageCode property. When spreadsheet document text was edited using 1C:Enterprise script, strings in the current language were written and strings in other languages were lost.	You can edit multilingual spreadsheet documents in 1C:Enterprise mode.
Applied objects.	When the Presentation field of the TasksByPerformer virtual table is generated, the fact that the presentation of the corresponding Task object can be redefined is taken into account. This change is not implemented in 8.3.6 compatibility mode.	When the Presentation field of the TasksByPerformer virtual table was generated, the fact that the presentation of the corresponding Task object could be redefined was not taken into account. The default presentation was always used instead.	Eliminated unexpected system behavior.
Queries.	The query object model is improved. The Find() method is implemented for the following objects: QuerySchemaIndexExpressions, QuerySchemaExpressions, QuerySchemaOrderExpressions, QuerySchemaAvailableFields, QuerySchemaAvailableTableParameters, QuerySchemaTableParameters, QuerySchemaFields, QuerySchemaColumns, QuerySchemaTableForUpdate, and QuerySchemaAvailableTables. The FindByName() and FindByAlias() methods are implemented for the following objects: QuerySchemaQuerySourceJoins and QuerySchemaSources. The FindByExpression() method is implemented for the following objects: QuerySchemaTotalCalculationFields and QuerySchemaTotalExpressions. The QuerySchemaTotalCalculationFields.FindByColumnName() method is implemented. The QuerySchemaTotalExpressions.FindByField() method is implemented. The QuerySchemaSources.GetRootSources() method is implemented. New Add() method variant is implemented for the following objects: QuerySchemaOrderExpressions, QuerySchemaQuerySourceJoins, QuerySchemaTablesForUpdate, and QuerySchemaTotalExpressions. For the QuerySchemaFields.Add() method the optional Column parameter is implemented. The SourceAlias parameter of QuerySchemaQuerySourceJoins.Add() method can have values of the following types: String and QuerySchemaSource. The QuerySchemaTotalExpressions.Add() method parameter can have values of the following types: String, QuerySchemaColumn, and QuerySchemaExpression. The behavior of QuerySchemaTotalCalculationFields.Add() method is modified for scenarios when its parameter has a value of String type. The QuerySchemaNestedTable.Fields property has QuerySchemaFields type. Passing a text containing a batch query or a table drop query to the QuerySchemaSelectQuery.SetQueryText() method raises an exception. The "For a nested table" variant of the QuerySchemaExpressions.Add() method is declared obsolete. This change is not implemented in 8.3.6 compatibility mode.	These features were not provided. The QuerySchemaNestedTable.Fields property had QuerySchemaExpressions type. If a text containing a batch query was passed to the QuerySchemaSelectQuery.SetQueryText() method, the first query in the batch was used. If a text containing a table drop query was passed to the QuerySchemaSelectQuery.SetQueryText() method, an empty query was created. The "For a nested table" variant of the QuerySchemaExpressions.Add() method was available.	Improved usability of query object model.
Data composition system.	In the data composition system, the data set link type is replaced with inner link if a filter containing only fields from the data set being linked is applied. Conditions that do not include inner links are added to the RecordsFilter property of groupings that contain at least one data set with fields used in these conditions. This change is not implemented in 8.3.6 compatibility mode.	In the data composition system, the data set link type was always set to inner link when a filter included a linked data set field.	Eliminated unexpected system behavior when fields from multiple data sets were used in a filter.
Navigation links.	The GotoURL method parameter value is not decoded prior to passing it to the operating system (the original link is passed). This change is not implemented in 8.3.6 compatibility mode.	The GotoURL method parameter value might be decoded prior to passing it to the operating system: In 8.3.4 or earlier compatibility mode it was not decoded (the original link was passed). In 8.3.5 and 8.3.6 compatibility modes it was decoded.	Eliminated unexpected system behavior.
Configuration extensions.	Writing an extension to an infobase is available in the following cases: the session that performs the writing is not running in the safe mode, or the session security profile allows this operation. When attaching an extension, the platform does not check whether the extension fits the session security profile restrictions.	Writing an extension to an infobase was only available if the session was running in the safe mode, When attaching an extension, the platform checked whether the extension fit the session security profile restrictions.	Security profiles process extensions in the same way as they process external reports and data processors.
Applied objects.	If a new object number (this includes document, catalog item, chart of characteristic types item, business process, and task numbers) is issued inside a transaction, it is reused even if the autonumbering mode is set to Do not Release Automatically, including scenarios where the object is not written inside the transaction. The Do not Release Automatically autonumbering mode only affects the numbers issued outside transactions. In other words, if a number is issued outside a transaction and it is not used (because the object is not written), it is not reused in the Do not Release Automatically mode, and it is reused in the Release Automatically mode.	If a new object number (this included document, catalog item, chart of characteristic types item, business process, and task numbers) was issued inside a transaction and the object was not written, that number was not reused in the Do not Release Automatically mode.	Reduced number of unused object numbers in scenarios where object numbers are issued in transactions and those objects are not written.
Client application. Data display.	If you want to use fonts other than Auto in your applied solutions, it is recommended that you select from the following fonts: 1C:Enterprise style fonts: Small text font Normal text font Large text font Very large text font Vector fonts from the "MS Core Fonts" collection: Andale Mono Arial Arial Black Comic Sans MS Courier New Georgia Impact Times New Roman Trebuchet MS Verdana Webdings If you use a font that is not listed here, from items might not be displayed correctly in some modes (including client applications).	The list of recommended fonts was not available.	A list of fonts recommended for use to ensure uniform applied solution appearance across environments is now available.
Managed forms.	The algorithm that calculates the font size based on the font properties specified for a fortm item is changed. This might lead to the change of the font scale for the form items that have the Scale part of the Font property set to a nondefalut value. This change is not implemented in 8.3.6 compatibility mode.	In some cases the Scale part of the Font property of form items was ignored, so that the text displayed on a form item had the default size.	Eliminated unexpected system behavior. In some cases the font size of form items might change.