1C:Enterprise 8.3.11. New functionality and changes.

Version 8.3.11 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.11

New functionality and changes

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, ReadHistoryOfMissingData, UpdateDataHistory, UpdateHistoryOfMissingData, UpdateDataHistorySettings, UpdateDataHistoryVersionComment, ViewDataHistory, EditDataHistoryVersionComment, and RevertToDataHistoryVersion. 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(), CheckAgainstBitMask(), 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 DMBS. 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 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 Visible 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 Move() 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.
Collaboration system.	Local collaboration system server is now available. The server is provided as a standalone distribution kit, 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.

Table of contents

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 Suspend notifications. 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 following commands are added to the Table section of the main application menu: Align pictures (Align section) Resize pictures (Size section) Auto space multiple pictures (Auto space 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 is 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

Optimization

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: ShowGridLines, GridLine, GridLineColor, LabelFont, LabelColor, LabelOrientation, MaxLabelLines, LabelAngle, LabelFormat, ScalePosition, ScaleLine, ScaleLineColor, ScaleStep, ScaleMarkPosition, and ScaleLabelPosition. The following properties of ChartPlotArea object are deprecated, they are supported solely for compatibility purposes: ShowSeriesScaleLabels. Use SeriesScale.ScaleLabelPosition instead. ShowPointsScaleLabels. Use PointsScale.ScaleLabelPosition instead. ShowValuesScaleLabels. Use ValuesScale.ScaleLabelPosition instead. ShowScaleValueLines. Use ValuesScale.ShowGridLines 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 ScalePosition MaxLabelLines ScaleMarkPosition ScaleLabelPosition	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 during the creation of 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 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 file names on Windows. 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 file names on Windows. 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.	When debugging over TCP, debugger no longer stops responding when calculating an expression or editing a variable value.	When debugging over TCP, debugger might stop responding when 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.	Parsing 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).	Parsing 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.

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 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.
The name of the system enumeration that describes chart scale label orientation. The previous name is supported for compatibility purposes.	ChartLabelsOrientation.	ChartLabelOrientation.
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.

Table of contents

Mobile platform

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 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 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.

Table of contents

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.

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 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.

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 the LineSplitter parameter is omitted, this is treated as setting it to Chars.LF. If the 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 the 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.

1C:Enterprise Developer's Community