Version 8.3.12

Version 8.3.12

Version 8.3.12 includes known bug fixes and functionality modifications.

Finished the beta testing of the application debug by HTTP protocol option.

New functionality and changes

Functionality	After	Before	Result of changes
Configuration properties.	For configuration property Compatibility mode, new value Version 8.3.11 is now implemented.	Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.10 was implemented.	Configurations developed using 1C:Enterprise platform version 8.3.11 or earlier can run on version 8.3.12 without any changes to configuration or to data structures. This allows for transition to version 8.3.12 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.11 after the transition to version 8.3.12, even if you disabled the compatibility mode (if you did, enable it again).
Client application.	On 64-bit Windows, you can set the bitness of a client application at application startup. In the Startup window settings dialog box, the option to specify the application bitness is implemented. This value is stored to the DefalutVersion parameter of 1CEStart.cfg file. In the infobase properties, the option to specify the bitness of the client application used with this infobase is implemented. This value is stored to the AppArch parameter of ibases.v8i file. The command-line option /AppArch is implemented for the thin and thick client applications.	This feature was not provided. On 64-bit Windows, users could not select the bitness of client applications.	On 64-bit Windows, the option to select the bitness of a client application is implemented. You can explicitly specify a 32-bit application in scenarios where a 64-bit application cannot work properly (for example, in a scenario where 64-bit add-ins are not available).
Configuration extensions.	The option to select the application area of configuration extensions, as well as activate or deactivate them, is implemented. The following application areas are available: the current data area and the entire infobase. When an extension is deactivated, it is not deleted from an infobase. For ConfigurationExtension object, implemented Scope and Active properties. The extension activation order is changed. Extensions that are applied to the entire infobase are activated first.	These features were not provided. Extensions were always attached to specific data areas. Disabling extensions without deleting them was not available.	More configuration extension management options. You can add configuration extensions to all of the infibase data areas at once. You can use this feature to apply hotfixes.
Collaboration system.	Automatic conversion of character sequences to pictures ("smileys") is implemented. Sound alerts for the following events are implemented: new message, incoming call, waiting for reply to a video call, and end of video call. Links to conversations, getting links to conversations, and opening links to conversations (both interactively and using GotoURL() method) are implemented. The option to add such links to Favorites is implemented. The option to get presentations of such links using GetURLsPresentations() method is implemented. In conversation messages, links to conversations are displayed as hyperlinks. In the thin and thick clients for Windows, taskbar blinking upon receiving a notification is implemented. In the main collaboration system form, a context menu is implemented for the conversation list. A context menu is implemented for collaboration system messages. For noncontext conversations, service collaboration system messages are implemented for the following events: conversation topic changed, a user joined/left a conversation. The search ignores service messages. The conversation participant list view is changed. Special marking for unsent outgoing messages is implemented. The collaboration system settings dialog box is implemented. The user picture (avatar) editor is implemented. The message list view is changed.	These features were not provided.	Improved collaboration system usability.
Data history.	Support of data history for charts of accounts and charts of characteristic types is implemented. For ChartOfAccountsObject and ChartOfCharacteristicTypesObject objects, methods SetDataHistoryVersionComment() and GetDataHistoryVersionComment() are implemented.	This feature was not provided.	Data history is now available for more objects.
Configuration extensions.	For native and adopted extension objects, the option to generate records in all adopted registers is implemented, except for turnover accumulation registers with aggregates.	This feature was not provided. Extension documents could generate records only in native information registers available in the extension.	Extended configuration extension capabilities.
Configuration extensions. Development tools. Settings storage.	The option to store configuration extensions in configuration repositories is implemented. All of the Designer batch mode command-line options that are related to configuration repositories support configuration extensions. For Designer batch mode, the following changes are implemented: -Extension parameter is implemented for the following command-line options: РЎonfigurationRepositoryAddUser, ConfigurationRepositoryBindCfg, ConfigurationRepositoryDumpCfg, ConfigurationRepositoryClearCache, ConfigurationRepositoryClearGlobalCache, ConfigurationRepositoryClearLocalCache, ConfigurationRepositoryCommit, ConfigurationRepositoryCopyUsers, ConfigurationRepositoryCreate, ConfigurationRepositoryLock, ConfigurationRepositoryOptimizeData, ConfigurationRepositoryReport, ConfigurationRepositorySetLabel, ConfigurationRepositoryUpdateCfg, ConfigurationRepositoryUnbindCfg, and ConfigurationRepositoryUnlock. ExtensionConfigurationRepository value is implemented for -FirstConfigurationType and -SecondConfigurationType parameters of CompareCfg command-line option. -FirstName, -FirstFile, -FirstVersion, -FirstName, -FirstFile, and -FirstVersion parameters are implemented for CompareCfg command-line option.	This feature was not provided. Configuration extensions could not be stored in configuration repositories, making development unnecessarily complicated.	Simplified group development and versioning of configuration extensions.
Configuration extensions.	Creation of enumerations in configuration extensions is now supported.	This feature was not provided.	Extended configuration extension capabilities.
Internet-enabled functionality.	Moving email messages between IMAP mailboxes is now supported. Method InternetMail.MoveToMailbox() is implemented. Getting and setting flags of IMAP email messages is implemented. For InternetMail object, methods GetMessageFlags() and SetMessageFlags() are implemented.	These features were not provided.	Extended support of IMAP email operations.
Charts. Data composition system.	Highlighting specific chart intervals and values is implemented. This feature is available for the following chart types: stock, open-high-low-close, all types of column charts, all types of bar charts (except for bar graph), line, step, stacked line, area (all types), scatter, bubble, radar (all types), and gauge. For Chart object, the following properties are implemented: ColorPaletteDescription, DataIntervalsColorPaletteDescription, ValueDataLines, PointDataLines, ValueDataIntervals, and PointDataIntervals. For ChartLabelArea, the following properties are implemented: Orientation and Angle. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, the following parameters are implemented: ChartType.ColorPaletteDescription, ChartType.DataIntervalsColorPaletteDescription, ChartType.ValueDataLines, ChartType.PointDataLines, ChartType.ValueDataIntervals, and ChartType.PointDataIntervals. The following properties and methods of Chart object are obsolete and not recommended for use: ColorPalette, GradientPaletteStartColor, GradientPaletteEndColor, GradientPaletteMaxColors, GetPalette(), and SetPalette().	This feature was not provided.	Additional chart layout features are introduced.
Spreadsheet documents.	Implemented representable document batch export to the following formats: XLS (Microsoft Excel 97-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later), and ODT (OpenDocument). You can export each spreadsheet document of the batch to a separate sheet of the resulting document. Implemented RepresentableDocumentBatchItem.Title property. Use it to specify the sheet name. Implemented Write() and BeginWriting() methods of RepresentableDocumentBatch object.	This feature was not provided.	You can save several 1C:Enterprise spreadsheet documents to the resulting XLS, XLSX, or ODT document.
Full-text search. Server clusters. Technological log.	In client/server mode, the option to set the number of background jobs that update the full-text search index is implemented. You can use requirements of functionality purpose to set the number of background jobs that update the full-text search index. For FullTextSearchManager object, the following methods are implemented: SetIndexingJobsCount() and GetIndexingJobsCount(). For FTEXTUpd technological log event, the following properties are implemented: MinDataId, MemoryUsed, BackgroundJobCreated, JobCanceledByLoadLimit, TotalJobsCount, and FailedJobsCount.	This feature was not provided. The update of the full-text search index was always performed as a single background job.	Improved performance of full-text search index updates (especially in scenarios with full index rebuilding).
Configuration extensions. Distributed infobases.	Support of configuration extensions in distributed infobases is implemented. For exchange plans, IncludeConfigurationExtensions property is implemented. For configuration extrensions, UseInDistributedInfobase and MasterNode properties are implemented.	This feature was not provided.	Extended configuration extension usage options. You can manage the replication of configuration extensions in distributed infobases.
Charts.	In charts, the option to manage automatic calculation of header, legend, and plot area sizes and positions is implemented. For ChartLegendArea, GanttChartLegendArea, PivotChartLegendArea, ChartPlotArea, GanttChartPlotArea, PivotChartPlotArea, ChartTitleArea, GanttChartTitleArea, and PivotChartTitleArea objects, property Placement is implemented. Property ShowLegend of Chart, GanttChart, and PivotChart objects is deprecated. Property ShowTitle of Chart, GanttChart, and PivotChart objects is deprecated.	Charts only provided the option to manage header and legend view.	Improved chart customization options.
Queries.	In the query language, extended support of UUID and ValueStorage types. The option to create temporary tables based on value tables that contain columns of these types is implemented. The option to use fields and expressions of UUID type in queries where IN is applied to a selection of multiple fields is implemented.	This feature was not provided.	Extended query language capabilities.
Data composition system.	In data composition settings, the option to use a period addition in scenarios where the reporting period does not match a regular calendar period is implemented. You can specify month size, either a calendar month or "4-5-5". In the latter case, a year is divided into 4 quarters. Each quarter has two 4-week months and the third 5-week month. For system enumeration DataCompositionPeriodAdditionType, the following values are implemented: YearFromBeginningOfPeriod DayFromBeginningOfPeriod QuarterFromBeginningOfPeriod MonthFromBeginningOfPeriod MinuteFromBeginningOfPeriod WeekFromBeginningOfPeriod HalfYearFromBeginningOfPeriod HourFromBeginningOfPeriod YearFromBeginningOfPeriod445 QuarterFromBeginningOfPeriod445 MonthFromBeginningOfPeriod445 HalfYearFromBeginningOfPeriod445	The data composition system always used period additions based on calendar beginning of quarter or year.	Simplified reporting in scenarios where the reporting period does not match a regular calendar period.
Managed forms.	For managed forms, collapsible pop-up groups are implemented. When a pop-up group is collapsed, a form displays its title; clicking the title opens a pop-up window, which contains all of the group items. In a form, you can view the content of a single pop-up group at a time. The option to toggle the state of collapsible and pop-up groups from 1C:Enterprise script is implemented. The following system enumeration value is implemented: UsualGroupBehavior.PopUp. For managed form group extensions for usual groups, the following methods are implemented: IsHidden(), Show(), and Hide(). For managed form group extensions, HiddenViewTitleBackgroundColor property is implemented.	These features were not provided.	New options for grouping managed form items.
Database configuration update.	In the optimized restructuring mechanism (version 2), added the support of restructuring configuration objects having at least one extension (that extends data) attached in any of the data areas. This is only applicable to restructuring main database configurations. Restructuring that is performed during extension updates does not use the optimized restructuring mechanism (version 2).	This feature was not provided. For main database configurations, if any of the areas had an extension (that extended data) attached, the regular restructuring mechanism (version 1) was used.	Improved interaction between platform mechanisms.
Automated testing.	For TestedFormField objects that represent form items of radio button, input field, and label (with hyperlink flag set) types, method GetDisplayedText() is implemented. It gets the text displayed on the item. For TestedFormField objects that represent form items of radio button and input field types, method GetChoiceListPresentation() is implemented. It gets a fixed array that contains presentations of the form item choice list.	This feature was not provided.	Extended automated testing capabilities.
Mobile client.	Implemented the mobile client, which is equivalent to the thin client running on a mobile device. Its interface is similar to mobile platform interface. The mobile client supports only HTTP connections to infobases. It does not support TCP connections. The exact match between the mobile client version and the server (or the web server extension) version is not required. The mobile client provides online access to the majority of the features available in the thin client and in the web client. The mobile client supports all mobile device-specific features, such as camera, location, and notifications. The collaboration system uses push notifications to deliver messages. Messages are delivered even if applications that generated them are not running or inactive. Mobile client applications are always built to run with a specific list of configurations. Changing the assortment of configuration objects in an infobase connected to a mobile client application is not supported. You can modify a configuration without modifying the assortment of its objects. If the assortment of objects changes, you have to republish the mobile application. A mobile client application cannot run with configurations that are not in the list because of application store requirements. The mobile client uses digital configuration signatures to check whether a configuration is in the list. Implemented automatic adjustment of configuration forms to mobile device screens. You can use new form item properties to modify the adjustment rules. In the managed form editor, implemented the form preview for mobile client mode. In the mobile client, the list of home page forms is identical to that of the thin and web clients (but different from the list of home page forms of the mobile platform). When you start an application, it displays the first form in the list, while the other forms are available through a menu. The mobile client supports add-ins. The mobile client does not support interactive opening of external reports and data processors. The mobile client can run configurations with compatibility mode Version 8.3.7 or later. In Designer, implemented commands for interactive start of the mobile client on a mobile device. The mobile application builder can now build mobile client applications. You can select the type of application to build: a mobile client application or a mobile platform application. Implemented MobileClient access right. Implemented MobileClient preprocessor command. In the Syntax Assistant, implemented a new availability option for objects, properties, and methods. For managed forms, implemented CollapseItemsByImportance property. For managed form items, implemented DisplayImportance property. It affects the adjustments of the form layout. For managed form tables, implemented CurrentRowUse and BehaviorOnHorizontalCompression properties. For form groups, implemented CurrentRowUse and AssociatedTable properties. For Designer batch mode, implemented the following command-line options and parameters: MobileClientWriteFile and MobileClientDigiSign options -MobileClient parameter for CheckModules and CheckConfig options -MobileClientDigiSign parameter for CheckConfig option Changed the content of the mobile platform distribution package (mobile.zip). Now it contains the mobile client files required to develop and build mobile applications, as well as distribute them through application stores. This feature is included for beta testing purpose only.	This feature was not provided. The mobile platform was capable of running specialized offline applications.	Mobile devices can be used in the new way now. You can now work online with all application features that were available on the thin client and on the web client without the significant configuration refactoring.
Administration tools.	In Designer batch mode, for command-line options CreateDistributionFiles and CreateDistributive, implemented parameter WarningAsError.	This feature was not provided.	You can apply stricter validation rules (treat all warnings as errors) to generation of application distribution kits.
Server clusters.	Implemented new values for session and connection attributes. They indicate the duration of cluster service calls initiated by a session or a connection. They are available in all administrative tools: the cluster console, COM connection, Java administrative API, and the administration server. Implemented the following IInfoBaseConnectionInfo object and ISessionInfo object properties: durationCurrentService вЂ“ the current cluster service operation time CurrentServiceName вЂ“ the current service name durationLast5MinService вЂ“ the total duration of cluster service calls within the last 5 minutes durationAllService вЂ“ the total duration of cluster service calls since the beginning of the session or the connection Added the same attributes to the session list, connection list, and the connection properties dialog box in the cluster console. Added the following parameters of connection list commands and session list commands for the cluster service command-line utility (rac): duration-current-service, current-service-name, duration-last-5min-service, and duration-all-service.	This feature was not provided.	The duration of cluster service calls initiated by a specific connection or a specific session is now available.
System requirements. Client application.	The client application for Linux needs the 1.4.3 version or higher of the webkitgtk-3.0 library installed.	The client application for Linux needed the 1.4.3 version or higher of the webkitgtk-1.0 library installed.	Unified the Linux and MacOs client applications operation.
Add-ins.	Implemented the new global context method DynamicAddInInstallationSupported(). It shows whether the add-in loading is available from the current infobase. The dynamic add-in loading is available only on Android mobile devices. Otherwise add-ins should be included in the mobile application and are available only from the Add-in type configuration templates. The dynamic add-in loading is available in the thick client, in the thin client, and in the web client (this behavior did not change).	Add-ins were available only from the mobile application and you could not load them from the infobase. You could not define the availability of dynamic add-in loading feature.	Now you can get the availability of dynamic add-in loading feature.

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Managed forms.	Keyboard navigation is now available for managed form decorations and fields, provided that they do not have the Hyperlink flag set and they display FormattedString values. Keyboard navigation provides the option to move between hyperlinks available in a formatted string.	This feature was not provided.	Improved managed form usability.
Web client. Spreadsheet documents.	In the web client, implemented all of the interactive spreadsheet document editing features that are available in other clients. Implemented the following spreadsheet document commands: AlignPictureLeft, AlignPictureCenter, AlignPictureRight, AlignPictureTop, AlignPictureMiddle, AlignPictureBottom, PicturesEqualWidth, PicturesEqualHeight, PicturesEqualSize, DistributePicturesVertically, DistributePicturesHorizontally, BringPictureForward, SendPictureBack, PringPictureToFront, and SendPictureToBack.	The options for interactive editing of spreadsheet documents were limited. The availability of interactive commands that affected spreadsheet document view was limited. Displaying row and column headers and grid lines was not supported.	Extended interactive spreadsheet document operations in the web client.
Spreadsheet documents.	In the thin client, in the paste special dialog box for spreadsheet documents, the option to include or exclude the following items is implemented: Merged cells Cell pictures Drawings Row and column groups Header and footer In this dialog box, the All check box is replaced with buttons that select and clear all of the check boxes available in the dialog box.	In the thin client, the paste special dialog box for spreadsheet documents did not provide the option to include or exclude the following items: Merged cells Cell pictures Drawings Row and column groups Header and footer In this dialog box, the All check box was available.	Extended paste special options for spreadsheet documents.
Interface.	In actions panel and navigation panel customization forms, the correct picture is set for Move to group command.	In actions panel and navigation panel customization forms, the picture of Move to group command was incorrect.	Eliminated unexpected system behavior.

Optimization

Functionality	After	Before	Result of changes
Client application.	The client application interface rendering is now faster. The client application load on the operating system is reduced.	The client application interface rendering was slower and used more operating system resources.	Improved client application usability.
Background and scheduled jobs.	Background jobs now start faster.	Background job startup took more time.	Background jobs now start faster.
Binary data.	Optimized performance and memory usage of the following 1C:Enterprise script function: GetStringFromBinaryData(); GetStringFromBinaryDataBuffer(); GetHexStringFromBinaryData(); GetHexStringFromBinaryDataBuffer(); GetBase64StringFromBinaryData(); GetBase64StringFromBinaryDataBuffer().	The performance and memory usage of the following 1C:Enterprise script functions were insufficient: GetStringFromBinaryData(); GetStringFromBinaryDataBuffer(); GetHexStringFromBinaryData(); GetHexStringFromBinaryDataBuffer(); GetBase64StringFromBinaryData(); GetBase64StringFromBinaryDataBuffer().	Improved performance and stability of several functions that process binary data.
Configuration extensions.	Reduced database configuration update time for configuration extensions that do not affect the database structure.	The database configuration update time was longer if the configuration extension did not affect the database structure.	Reduced database configuration update time if the update includes applying changes to the configuration extensions that do not affect the database structure.

Changes that affect system behavior

Functionality	After	Before	Result of changes
Charts.	The option to display Gantt chart intervals that would occupy less than 2 pixels in the current chart scale is implemented. They are displayed as 2-pixel intervals.	In some cases, Gantt chart intervals that would occupy less than 2 pixels in the current chart scale were not displayed.	Eliminated unexpected system behavior.
Data composition system.	The value of ResourcesAutoPosition data composition system parameter does not affect how column totals are displayed in data composition system reports. This change is not implemented in 8.3.11 compatibility mode.	In data composition system report spreadsheets, column totals were not displayed if ResourcesAutoPosition data composition system parameter was set to DontUse.	Eliminated unexpected system behavior.
Development tools.	In configuration comparison reports, the description of differences in XDTOPackages properties of Web service object is more detailed. The report includes the list of added and removed packages (with package names included) and their namespace data.	In configuration comparison reports, the description of differences in XDTOPackages properties of Web service object was less detailed.	Eliminated unexpected system behavior.
Charts. Spreadsheet documents.	In black-and-white view mode: Charts are displayed in black-and-white mode. Geographical schemas are displayed in black-and-white mode. Pictures and OLE objects are displayed in grayscale. In black-and-white printing mode: Charts are printed in black-and-white mode (this behavior is not changed). Geographical schemas are printed in black-and-white mode (this behavior is not changed). Pictures and OLE objects are displayed in grayscale. This change is not implemented in 8.3.11 compatibility mode.	In black-and-white view mode: Charts were displayed in full color. Geographical schemas were displayed in full color. OLE objects were displayed in full color. SVG, EMF, and WMF pictures were displayed in full color. Other pictures were displayed in grayscale. In black-and-white printing mode: Charts were printed in black-and-white mode. Geographical schemas were printed in black-and-white mode. OLE objects were printed in full color. SVG, EMF, and WMF pictures were printed in full color. Other pictures were printed in grayscale.	For spreadsheet document objects, eliminated differences between black-and-white view and black-and-white printing.
Charts.	The background patterns used in black-and-white chart printing are based on original chart colors. If a pattern based on an original color is already in use, the next available pattern is used instead. The total number of available patterns in increased to 27. This change is not implemented in 8.3.11 compatibility mode.	The background patterns used in black-and-white chart printing were based on original chart colors (no check for duplicate patterns). The total number of available patterns was 12.	Improved chart view for black-and-white printing.
External data sources.	During a configuration update, the platform checks whether the Group property of external data source cube commands and external data source dimension table commands is filled. If the property is not filled, the update is canceled. This change is not implemented in 8.3.11 compatibility mode.	During a configuration update, the platform did not check whether the Group property of external data source cube commands and external data source dimension table commands was filled.	Eliminated unexpected system behavior.
Data history. Configuration extensions.	Support of data history is added to native and adopted extension objects.	Native and adopted extension objects did not support data history.	Data history is available for configuration extensions.
Spreadsheet documents.	In spreadsheet document headers and footers, the option to specify the first page number is implemented. The following property is implemented: SpreadsheetDocument.FirstPageNumber. In the spreadsheet document headers and footers dialog box, the option to specify the first page number is implemented. When a spreadsheet document is exported to OpenXML or OpenDocument format, the first page number is exported to the respective document property.	This feature was not provided. The number of the first page was always 1.	You can generate spreadsheet documents that match the requirements of regulatory authorities.
Internet-enabled functionality.	The platform no longer uses the imaplib library. The behavior of InternetMail object is not changed. The functionality previously provided by the library is now provided by the platform.	1C:Enterprise used the imaplib library, which provided a part of InternetMail object functionality in compatibility modes Version 8.3.5 and earlier.	Improved platform stability and security.
Full-text search. Interface.	The standard full-text search form is updated. The History picture is added to the picture library.	The standard full-text search form looked differently.	Improved usability of the standard full-text search form.
Development tools.	The following features are added to the managed form editor: In the device selection menu (for mobile device view), the current device is marked. In the scale selection menu (for mobile device view), the current scale is marked. Scale options similar to scale options for personal computers are implemented in this menu. In the scale selection menu (for personal computer view), the current scale is marked. In the resolution selection menu (for personal computer view), the following features are implemented: Information about the current resolution. The option to select a display (the one where the Designer window is displayed). Information about typical DPI for each resolution. The option to select display resolutions 4K (38402160 pixels) and 5K (51202880 pixels).	These features were not provided.	Improved form editor usability.
Data composition system.	If a query parameter belongs to a query language expression that has a name, or the parameter is an independent expression, it is available for use in data composition system data parameteres (however, it is not visible to end users). This change is not implemented in 8.3.11 compatibility mode.	If a query parameter belonged to a query language expression that had a name, or the parameter was an independent expression, it was not included in the list of available data parameters of the data composition system.	Eliminated unexpected system behavior.
Dynamic lists.	If a column of a table linked to a dynamic list belongs to a column group with In cell grouping, in a document generated using the Output list command, the column header is taken from the managed form table column header. This change is not implemented in 8.3.11 compatibility mode.	If a column of a table linked to a dynamic list belonged to a column group with In cell grouping, in a document generated using the Output list command, the column header was: In the thin client, the form table column name. In the web client, the form table column header.	Eliminated unexpected system behavior.
Automated testing.	The option to set and get timeouts for automated testing operations is implemented. For TestedApplication object, methods SetActionTimeout() and GetActionTimeout() are implemented. Clarified wordings of error messages related to attempts to connect to and/or operate applications being tested.	The option to set and get timeouts for automated testing operations was not available. Wordings of error messages related to attempts to connect to and/or operate applications being tested were less detailed and less accurate.	You can set timeouts for automated testing operations. Improved diagnostics for automated testing errors.
Spreadsheet documents.	If a spreadsheet document has docked rows or columns, the lines that outline the docked areas are only displayed after the document has been scrolled vertically (for rows) or horizontally (for columns). This change is not implemented in 8.3.11 compatibility mode.	If a spreadsheet document had docked rows or columns, the lines that outlined the docked areas were always displayed.	Improved report view.
Managed forms.	If the width specified for a managed form group is less than the total width of its subordinate items (at their minimum possible sizes), the specified width value is ignored. Instead, the width is calculated as follows: For vertical groupings, the maximum value among the minimum width values of subordinate items. For horizontal groupings, the sum of minimum width values of all subordinate items plus the total width of gaps between them. This change is not implemented in 8.3.11 compatibility mode.	If the width specified for a managed form group was too small and some of the subordinate items could not fit even at their minimum possible sizes, the group still had the specified width.	Eliminated unexpected system behavior.
Queries.	An attempt to execute a query that contains a nested query with AUTOORDER keyword generates the following error: Nested queries cannot contain AUTOORDER operation.	An attempt to execute a query that contained a nested query with AUTOORDER keyword generated the following error: Nested queries cannot contain ORDER BY operation without TOP construction.	The error message is more accurate.
Configuration extensions.	Notifications related to applying configuration extensions have Important status. Therefore, they are available in the notification center and users who miss them can read them later.	Notifications related to applying configuration extensions had Information status. Therefore, they were not available in the notification center and, if errors occurred when applying configuration extensions, users who missed the notifications at the time they were generated missed them completely.	Better diagnostics of errors related to applying configuration extensions.
Data composition system. Dynamic lists.	When a new parameter that is a part of IN clause is added to a data set query, the data composition schema wizard automatically sets the option to use a value list as the parameter value. If a description of a query parameter that is a part of IN clause is missing from a data composition schema, the option to use a value list as the parameter value is automatically added to the available parameter of the source of available data composition settings. If a parameter of a dynamic list query is a part of IN clause, you can assign a value of value list type to this parameter in the dynamic list composition settings, and the dynamic list will pass the correct value list to the query. This change is not implemented in 8.3.11 compatibility mode.	The data composition schema wizard did not automatically set the option to use a value list as the value of a data composition schema parameter. If a parameter description was missing from a data composition schema, only a single value could be used as the parameter value. Dynamic lists processed query parameters of value list type incorrectly.	Eliminated unexpected system behavior. Improved data composition system behavior in scenarios where queries use value lists to set filters.
Data composition system.	In the data composition system, header templates (available for reports, tables, groupings, and charts) are not followed by blank line templates. As a result, a table or a chart header is always followed by a single blank line. This change is not implemented in 8.3.11 compatibility mode.	In the data composition system, header templates (available for reports, tables, groupings, and charts) were followed by blank line templates. As a result, a table or a chart header was always followed by two blank lines.	Eliminated unexpected system behavior. A table or a chart header is now followed by a single blank line instead of two blank lines.
Standard functions.	In the standard full-text search management function, the option to set the maximum size of objects to be indexed and the option to set the number of background jobs used for indexing are implemented. To set these parameters, use the dialog box that is opened using the Additional parameters button of the standard full-text search management function form.	This feature was not provided.	You can specify additional parameters for full-text search indexing.
Spreadsheet documents.	In the thin client, when a spreadsheet document is saved to a PDF file, if the spreadsheet page size is not specified, the page size setting of the current printer is used instead. This change is not implemented in 8.3.11 compatibility mode.	In the thin client, when a spreadsheet document was saved to a PDF file, if the spreadsheet page size was not specified, size A4 was used instead.	Eliminated unexpected system behavior.
Data display.	In Designer, thin client, and thick client, in the font selection dialog box, when you select a font by name (for example, "Arial"), the Scale value is applied to the resulting font. This change is not implemented in 8.3.11 compatibility mode.	In Designer, thin client, and thick client, in the font selection dialog box, when font was selected by name (for example, "Arial"), the Scale value was not applied to the resulting font.	Eliminated unexpected system behavior.
Data composition system.	In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag does not set that flag to its parent parameter. This change is not implemented in 8.3.11 compatibility mode.	In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag also set that flag to its parent parameter.	Eliminated unexpected system behavior.
Managed forms.	In the property palette, the field linked to the font property displays the font name, style, appearance (bold, italic, or strikethrough), and scale.	In the property palette, the field linked to the font property displays the font name and style.	You can view the current font parameters in the property palette, without opening the font dialog box.
Managed forms.	Implemented the new AlwaysHorizontal value of the ChildFormItemsGroup system enum. The Horizontal value of the ChildFormItemsGroup system enum is deprecated If the Horizontal value is used in the application, the PC platform will use the AlwaysHorizontal value, and the mobile platform will use the HorizontalIfPossible value instead. We recommend to replace the Horizontal by the HorizontalIfPossible value in applications in most cases. The AlwaysHorizontal value should be used only if a group must be horizontal on any screen, including mobile device screens. For example, if there is a group with an input field and a button with a picture and without text, linked to this field.	The following options of horizontal alignment of forms and form groups were available: Horizontal and HorizontalIfPossible.	The smooth conversion of previously created form to the mobile client usage is available.

Changes that require modification of configuration and administrative settings

Renamed objects

Object	The old name	The new name
Parameters of CompareCfg command-line option of Designer batch mode that define the first and second configurations to be used in a comparison.	FirstConfigurationKey SecondConfigurationKey	FirstConfigurationType SecondConfigurationType
Batch Designer mode command-line options that apply to mobile device applications. The former names are supported for compatibility purposes.	MAUpdatePublication; MAWriteFile.	MobileAppUpdatePublication; MobileAppWriteFile.
Configuration and managed form use purposes. The former names are supported for compatibility purposes.	MobileDevice PersonalComputer	MobilePlatformApplication PlatformApplication
Spreadsheet document command groups. This change is not implemented in version 8.3.11 compatibility mode.	Print View Format Font Borders Alignment Groups Names PrintOptions Pictures Alignment1 Size Distribute Order Comments Cells Merging Insert InsertCells InsertColumns ShowHideCells Sizes Other Other1 Other2 Other3	CommandsPrint CommandsView CommandsFormat CommandsFont CommandsBorders CommandsAlignment CommandsGroups CommandsNames CommandsPrintOptions CommandsPictures CommandsPisturesAlignment CommandsSize CommandsDistribute CommandsOrder CommandsComments CommandsCells CommandsMerging CommandsInsert CommandsInsertCells CommandsInsertColumns CommandsShowHideCells CommandsSizes CommandsOther CommandsOtherUndo CommandsOtherClipboard CommandsOtherProperties

Mobile version of 1C:Enterprise

Functionality	After	Before	Result of changes
Managed forms.	On Android, context menus are displayed next to the items where they belong. Opening a context menu does not change the form layout.	The context menu was displayed at the top of a form. Opening a context menu changed the form layout and repositioned form items.	On Android, improved usability of accessing context menus of form items.
Mobile device-specific features.	Optimized MultimediaData object generation algorithm used during device camera operations.	The MultimediaData object generation algorithm used during device camera operations was not optimal.	Improved performance of device camera operations in mobile applications.
Interface.	Changed the calendar view on mobile devices: Better visibility of the current date Implemented switching between single and multiple date choices Added the context menu Added the Choice event	The calendar view on the mobile device was different: The current date marking was more subtle Switching between single and multiple date choices was unavailable (only multiple date choice was available) No context menu No Choice event	Improved calendar usability on mobile devices.

Changes performed after version publication

Functionality	After	Before	Result of changes
Web client.	Implemented the following features for file system extensions for Google Chrome and Mozilla Firefox: Web server certificate authentication (users are prompted to select the authentication certificate). Operating system authentication in the following scenario: a computer that runs the web client is not included in a domain, and the web server supports operating system authentication (users are prompted to specify the domain user name and password).	File system extensions for Google Chrome and Mozilla Firefox did not support the following: Web server certificate authentication. Operating system authentication in the following scenario: a computer that runs the web client is not included in a domain, and the web server supports operating system authentication.	Improved secure connection support. Improved web client security.
Web client.	In the web client, dragging spreadsheet document cells and pictures is implemented. If Ctrl is held down, they are copied, otherwise they are moved. The web client behavior is now identical to the thin client behavior. This change is not implemented in version 8.3.11 compatibility mode.	In the web client, dragging spreadsheet document cells and pictures was not supported.	New interactive spreadsheet document operations in the web client.
Automated testing.	If TestedFormField or a similar object is retrieved using FindObject() or FindObjects() method, its TitleText property always stores the title value set in Designer. This change is not implemented in version 8.3.11 compatibility mode.	If TestedFormField or a similar object was retrieved using FindObject() or FindObjects() method, if its title was explicitly specified in the form editor, a colon might be missing from the title.	Eliminated unexpected system behavior.
Managed forms.	Changing the availability of form items and groups in managed form tables does not require a server call. This change is not implemented in version 8.3.6 and earlier compatibility mode.	Changing the availability of form items and groups in managed form tables required a server call.	Optimized changing the availability of some managed form items.
Mobile platform. Mobile client.	Implemented the following features of the applications list in the mobile client and mobile application main menu: custom list ordering; alphabetical list ordering; common infobase list operations (only for the web client). Command-line parameters can be specified for each application in the applications list. The following command-line parameters are available in the mobile application and mobile client: N, P, ClearCache, C, WSA, OIDA, Autooff, DisableStartupMessahes, Z, UsePrivilegedMode, HttpsForceSSLv3, HttpsForceTLS1_0, O, L, VL, WSN, WSP, and URL. Implemented the application startup according with the set of supported command-line parameters.	These features were not provided.	New application list management operations. You can now specify command-line options to fine tune the application behavior at startup.
Managed forms.	In the mobile platform and in all client applications, if a form control that has minimum width does not fit the form, the control width is reduced below the minimum. This change is not implemented in version 8.3.11 compatibility mode.	If a form control that had minimum width did not fit the form, the control width was not reduced below the minimum.	Eliminated unexpected system behavior.
Data composition system.	Rows and columns can be docked when generating a grouping header template based on a predefined template. Columns are docked (FixLeft property of a data composition template area cell is set) if the FixLeft report setting is not set or is set to Auto. Rows are docked (FixTop property is set) if the FixTop report setting is not set or is set to Auto. This change is not implemented in version 8.3.11 compatibility mode.	Rows and columns were never docked when generating a grouping header template based on a predefined template.	Eliminated unexpected system behavior.
Queries.	If a query contains a UNION expression without the ALL keyword, a CAST AS Reference operation will return a single string with NULL value. ISNULL() function applied to a CAST AS Reference expression returns the correct result. This change is not implemented in version 8.3.11 compatibility mode	If a query contained a UNION expression without the ALL keyword, a CAST AS Reference operation might return multiple strings with NULL value. ISNULL() function applied to a CAST AS Reference expression might return an incorrect result.	Eliminated unexpected system behavior.
Collaboration system.	Clarified some of the collaboration system error messages.	Some of the collaboration system error messages were less clear.	The collaboration system error messages are more clear now.
Data composition system.	In the settings composer of the data composition system, when the source of available settings is specified, if a parameter value is a fixed array and the parameter can store a value list, the value list that includes all the values from the initial fixed array is stored to the parameter. This change is not implemented in version 8.3.11 compatibility mode	In the settings composer of the data composition system, when the source of available settings was specified, if a parameter value was a fixed array and the parameter could store a value list, a value list containing a single element with the default value of the parameter type was stored to the parameter.	Eliminated unexpected system behavior.
Managed forms.	Unified and improved appearance of managed form control tooltips that have ToolTipRepresentation property set to Button. This change is implemented for various types of managed form controls.	The appearance of managed form control tooltips that had ToolTipRepresentation property set to Button was not unified across different control types.	Unified tooltip appearance for various types of form controls.
Mobile platform. Mobile client. Managed forms. Internet-enabled functionality.	In mobile applications, for managed form field extension for an HTML document field, the Document property is now available. In mobile applications, for EventData parameter of OnClick event handler of managed form field extension for an HTML document field, Document and Href parameters are now available. Mobile platform notifications about calls of methods and properties that do not exist may be different from PC platform notifications.	These features were not provided. On mobile devices, HTML documents displayed in forms were inaccessible.	Extended HTML document capabilities for the mobile platform.
DBMS operations. System requirements.	Support of Microsoft SQL Server 2017 is implemented.	Microsoft SQL Server 2017 was not supported.	Support of Microsoft SQL Server 2017 is implemented.
Development tools.	For TextColor and BackColor properties of managed form buttons, both the property palette and the color selection dialog box now display the actual color values (if these properties are set to Auto or to any of the system style items).	For TextColor and BackColor properties of managed form buttons, both the property palette and the color selection dialog box displayed the color of the system style item (if these properties were set to Auto or to any of the system style items).	The property palette now displays property values more accurately.
Localization.	The French localization of the client applications is available.	This feature was not provided.	1C:Enterprise is available to French-speaking users.
Mobile client.	The information in the About dialog box in the mobile client was expanded.	There was less information in the About dialog box in the mobile client.	The About dialog box in the mobile client is now closer to the About dialog box in the thin client.
Mobile platform. Mobile client. Collaboration system.	Implemented the feature of receiving and processing push notifications from the collaboration system. The mobile device application should be built with push notifications extension enabled. Notifications are generated by the pushnotifications.1c.com service from 1C company. The registration in service is performed automatically.	The collaboration system did not generate mobile push notifications.	Reduced risk of missing the collaboration system notification when the application is not running, or is hidden, or when the user is operating in another infobase within a single application.
Internet-enabled functionality.	Implemented the feature of including external providers in the OpenID authentication process. For the specifics of external providers usage, refer to the documentation.	This feature was not provided.	Improved the OpenID authentication support.
Mobile platform. Mobile client.	The iPhone X screen is now supported in the 1C:Enterprise mobile version.	This feature was not provided.	The 1C:Enterprise mobile version interface is adapted to iPhone X.
Internet-enabled functionality.	1C:Enterprise 8 now supports cryptographic algorithms that meet the GOST R 34.10-2012 and 34.11-2012 requirements.	This feature was not provided.	Internet resources that demand the GOST R 34.10-2012 and 34.11-2012 compliance are now available in 1C:Enterprise 8.
Mobile platform. Mobile client. Mobile device-specific features.	1C:Enterprise platform does not support barcode scanning, making photos and videos on Windows Desktop. The following methods of the MultimediaTools object return False on Windows Desktop: BarcodeScanningSupported(), PhotoSupported(), VideoRecordingSupported().	The following methods of the MultimediaTools object returned True on Windows Desktop: BarcodeScanningSupported(), PhotoSupported(), VideoRecordingSupported().	Eliminated unexpected system behavior.
Pictures.	If the name of the picture from a picture library equals to the name of the configuration common picture, a warning will be generated during the database update. The database update process will not be interrupted. When accessing the picture by name, the configuration picture returns. When this warning appears, it is recommended to review picture names in the configuration.	If the name of a picture from a picture library was equal to the name of a configuration common picture, the database update could not be performed.	The database update is now available if the name of a picture from a picture library is equal to the name of a configuration common picture.
Mobile platform. Mobile client. Administration tools.	The 1C:Enterprise 8 mobile platform now supports OS authentication. The HTTPConnection object constructor supports the UseOSAuthentication parameter.	This feature was not provided.	The 1C:Enterprise 8 mobile platform is now sufficient when the OS authentication is required.
Data display. Mobile client.	The 1C:Enterprise mobile platform now displays messages of the same style as other mobile messages. Messages are generated by the ShowUserNotification() method with the UserNotificationStatus parameter set to UserNotificationStatus.Information.	If a message was generated by the ShowUserNotification() method with the UserNotificationStatus parameter set to UserNotificationStatus.Information, this message was not displayed.	Extended capabilities of the ShowUserNotification() method in the mobile client.
Mobile platform. Mobile client. Managed forms.	The command set and the appearance of the context menu of a managed form table row was changed in the 1C:Enterprise mobile version.	The command set and the appearance of the context menu of a managed form table row in the 1C:Enterprise mobile version were different.	Improved the 1C:Enterprise mobile interface.
Internet-enabled functionality.	Improved the analysis of the root certificate revocation. Implemented the option to specify the behavior of the platform when the root certificate revocation can not be verified unambiguously. Implemented the IgnoreServerCertificatesChainRevocationSoftFail parameter of the conf.cfg file. These changes are available in all Internet-enabled features of 1C:Enterprise platform.	The analysis of the root certificate revocation was the same regardless of the reason why the remote node was not validated. There was no option to specify the platform behavior when the root certificate revocation could not be verified unambiguously.	Improved diagnostics of Internet-enabled functionality. In some cases the option to specify the platform behavior is now available.
Mobile platform.	Implemented the database file validation in the verify and repair feature of the mobile platform. This feature checks whether the database file is corrupted and prompts several solutions.	These features were not provided. The verify and repair feature could not validate the database file. If the database file was corrupted the session was abnormally terminated.	Improved the database file diagnostics capabilities.
Configuration extensions.	If the active extension changes the database structure it can not be deleted. If you want to delete the extension you shoud deactivate it first. You will be prompted to confirm the deletion of the inactive extension that changes the database structure. Implemented the ConfigurationExtension.ModifiesDataStructure() method, which shows whether the configuration extension changes the database structure.	When the extension that changed the database structure was deleted no actions preventing the extension data loss were performed.	Reduced risk of configuration extension data loss.
Mobile client. Mobile application builder.	A web page where user can register in the infobase (or service) can now be specified in the mobile client. This page can be reached either automatically (if there are no registered infobases in the mobile client) or manually. You can now specify an URL with the personal account of services that contain infobases for the mobile client. The mobile client can now retrieve shared infobase lists from the server through special web services. You can specify multiple addresses of the same server, as well as addresses of multiple servers. The following options are now available when building a mobile application: Specifying starting page that will be displayed if the mobile client infobase list is empty. Specifying a custom URL in the infobase list. This URL will be displayed by the internal mobile client features. Specifying multiple web services that return shared infobase lists. Entering a custom web service URL to retrieve a shared infobase list. The e1c:// type hyperlinks are now supported as a starting page and an infobase list element in the mobile client. Implemented the AddToStartCfg command-line option for the mobile client. It adds an infobase in the mobile client infobase list. It can be placed in web pages, specified during the mobile application customization. OpenID authentication is not supported for accessing web-servers with shared infobase lists.	These features were not provided.	The registration of an infobase or a web service in the mobile client became more clear and simple.
Event log.	Implemented the following events: Managing users: Error adding a user (_$User$_.NewError), Error changing a user (_$User$_.UpdateError), Error deleting a user (_$User$_.DeleteError). Infobase operations: Truncate event log (_$InfoBase$_.EventLogReduce), Error truncating event log (_$InfoBase$_.EventLogReduceError), Error changing event log parameters (_$InfoBase$_.EventLogSettingsUpdateError), Error changing infobase parameters (_$InfoBase$_.InfoBaseAdmParamsUpdateError), Start dumping infobase to file (_$InfoBase$_.DumpStart), End dumping infobase to file (_$InfoBase$_.DumpFinish), Error dumping infobase to file (_$InfoBase$_.DumpError), Start restoring infobase from file (_$InfoBase$_.RestoreStart), End restoring infobase from file (_$InfoBase$_.RestoreFinish), Error restoring infobase from file (_$InfoBase$_.RestoreError), Error updating database configuration (_$InfoBase$_.DBConfigUpdateError), Error updating extension database configuration (_$InfoBase$_.DBConfigExtensionUpdateError). Extended the list of data types that are handled by the following events: _$Access$_.AccessDenied, _$InfoBase$_.EventLogSettingsUpdate. New events require the DataAdministration access right to view, except managing users events and the following ones: $InfoBase$_.DBConfigUpdateError, and _$InfoBase$_.DBConfigExtensionUpdateError.	There were less registered events and less handled data types.	Improved logging events.
Data composition system. Charts.	Some of the output parameters of the data composition system are only saved if their Use flag is set (the exact list of parameters depends on the configuration compatibility mode). In compatibility mode Version 8.3.10 or earlier: ChartType.PointsScale, ChartType.ValuesScale, and ChartType.SeriesScale. In compatibility mode Version 8.3.11 or earlier: ChartType.ColorPaletteDescription, ChartType.ReferenceBandsColorPaletteDescription, ChartType.ValuesReferenceLines, ChartType.ValuesReferenceBands, ChartType.PointsReferenceLines, ChartType.PointsReferenceBands.	All of the changes in the output parameters of the data composition system were saved. This could cause issues at opening data composition settings in the earlier versions of 1C:Enterprise.	Data composition settings related to charts are now usable in the earlier platform versions.
Web client.	The Mozilla Firefox add-on that provides access to 1C:Enterprise extensions and 1C:Enterprise add-ins is available in the add-on store https://addons.mozilla.org. The add-on is automatically updated to newer versions as they appear in the store.	The Mozilla Firefox add-on that provides access to 1C:Enterprise extensions and 1C:Enterprise add-ins was not available in the add-on store https://addons.mozilla.org. The add-on updates were delivered and installed with new 1C:Enterprise versions.	Updates of the Mozilla Firefox add-on are now transparent to users.
Mobile client. Mobile platform. Managed forms.	In the mobile version of 1C:Enterprise, in HTML document fields, full-featured editing of HTML page input fields is now available (if their contentEditable property allows editing). At that, all formatted document functionality is supported.	In the mobile version of 1C:Enterprise, in HTML document fields, full-featured editing of HTML page input fields was not available (if their contentEditable property allowed editing).	Extended HTML document functionality in the mobile version of 1C:Enterprise.
Internet-enabled functionality. Add-ins. Cryptography support. File operations.	Distribution packages of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer are converted into .exe files. Distribution packages in .cab format are considered obsolete, although supported. The add-in technology documentation is updated. (read more)	Distribution packages of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer were provided in .cab files.	Installation of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer is more convenient.

Transition from the previous version to the version 8.3.12

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

Changes in demo configurations

The demo configuration was renamed. New name is Demo application.
All documents in the demo application were dated the current year.

Functionality	After	Before	Result of changes
Settings storage.	If a report form is opened with UserSettingsKey parameter specified and UserSettings parameter missing: If settings with the specified key are found in the user settings storage, these settings are loaded. Otherwise the default user settings for the current report option are loaded. This change is not implemented in 8.3.11 compatibility mode.	If a report form was opened with UserSettingsKey parameter specified and UserSettings parameter missing: If user settings for the current report option were found in the system settings storage, these settings were loaded. Otherwise, if settings with the specified key were found in the user settings storage, these settings were loaded. Otherwise the default user settings for the current report option were loaded.	Eliminated unexpected system behavior.
Client application installation.	1C:Enterprise launcher searches for distribution packages of new 1C:Enterprise versions in the following directories: Setup (32-bit platform) and Setup64full (64-bit platform).	1C:Enterprise launcher searched for distribution packages of new 1C:Enterprise versions only in directories that contained specific versions (ignoring subdirectories).	Automatic client application updates support scenarios where client applications are both 32-bit and 64-bit.
Charts.	When OnIntervalEditEnd handler of a form item that displays a Gantt charts is executed: The chart interval is passed to Interval handler parameter. If CancelEdit handler parameter is set to False, all of the interval values are applied to the chart. If CancelEdit handler parameter is set to True, interval properties Begin and End are not applied to the chart, while the rest of the interval properties are applied. This change is not implemented in 8.3.11 compatibility mode.	When OnIntervalEditEnd handler of a form item that displays a Gantt charts was executed: A copy of the chart interval was passed to Interval handler parameter. The changes made in the passed interval were not applied to the chart.	The behavior of OnIntervalEditEnd handler of form items that display Gantt charts is more logical.
Event log.	Interactive editing of event log format is implemented. The new event log event _$InfoBase$_.EventLogSettingsUpdate indicates the format change. In file infobases, changing event log format requires exclusive infobase access. Global context method ClearEventLog() is deprecated and only applicable to logs that have SQLite format. It is recommended that you do not use this method. If selection from event log records takes a long time, you can abort it by deleting the session that initiated the selection. The following limitations are applied to time-consuming selections from the event log: In a nonseparated infobase: 4 sessions. In a separated infobase: 1 session per data area. The default event log format (the one that is selected in newly created infobases) is sequential format.	Interactive editing of event log format was not available. The default event log format (the one that was selected in newly created infobases) was SQLite format.	Interactive selection of event log format is now available. Applications no longer stop responding when performing time-consuming selections from the event log.
Temporary storages.	If the Address parameter of PutToTempStorage() method contains a value that was previously used in DeleteFromTempStorage() method, an exception is generated. This change is not implemented in 8.3.11 compatibility mode.	If an Address parameter value was previously used in PutToTempStorage() method and then in DeleteFromTempStorage() method, an attempt to use the value in PutToTempStorage() method again was only successful if it was a UUID of a form that was open at that time.	Eliminated unexpected system behavior.
Charts.	The algorithm of displaying stacked charts that have negative values is changed: For charts that support base values: For each point, calculate two sums: one less than the base value, the other one greater than the base value. Before stacking, subtract the base value from the current value. Stack the resulting value to one of the sums, depending on its sign. For charts that do not support base values: For each point, calculate two sums: a negative one and a positive one. Stack the current value to one of the sums, based on its sign. For each point, display two chart columns that represent the two sums. This change is not implemented in 8.3.11 compatibility mode.	In stacked charts, each point had a single column that represented the sum of all values (calculated with appropriate signs).	Eliminated unexpected system behavior.
Data composition system.	In data composition settings composer, when the source of user-defined settings is specified, if a data parameter value contains an array and the option to use a value list in this parameter is enabled, the parameter value is set to a value list containing all of the values from the source array. This change is not implemented in 8.3.11 compatibility mode.	In data composition settings composer, when the source of user-defined settings was specified, if a data parameter value contained an array and the option to use a value list in this parameter was enabled, the parameter value was set to a value list containing a single value (the default value for the parameter value type).	Eliminated unexpected system behavior.
Managed forms.	When form item properties DataPath, FooterDataPath, HeaderDataPath, TitleDataPath, and RowPictureDataPath are set from 1C:Enterprise script or a configuration with these properties is loaded from a file, if any of these properties contains a path that refers to a form item that has a row index, an error is generated. This change is not implemented in 8.3.11 compatibility mode.	When form item properties DataPath, FooterDataPath, HeaderDataPath, TitleDataPath, and RowPictureDataPath were set from 1C:Enterprise script or a configuration with these properties was loaded from a file, if any of these properties contained a path that referred to a form item that had a row index, no errors were generated. Such property values were set but they were actually ignored.	Eliminated unexpected system behavior.
Dynamic lists.	In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as Ref.Products.Product.[State of origin]) are not available for filtering, sorting, or grouping. This change is not implemented in 8.3.11 compatibility mode.	In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as Ref.Products.Product.[State of origin]) were available for filtering, sorting, or grouping. However, an attempt to set a filter by a value of such field returned an error.	Eliminated unexpected system behavior.
Data composition system.	If an expression of a calculated data composition system field is empty, NULL is substituted for the field value in detailed records. This change is not implemented in 8.3.11 compatibility mode.	If an expression of a calculated data composition system field was empty, an attempt to use the field in detailed records generated a "field not found" error.	Eliminated unexpected system behavior. The system behavior is improved in scenarios where a user selects a custom field with no expression specified.
Data composition system.	If calculation of EvalExpression() function result includes division by 0, the result of the expression calculated with this function is Division by zero. This change is not implemented in 8.3.11 compatibility mode.	If calculation of EvalExpression() function result included division by 0, the expression calculated with this function was fully calculated (Division by zero was used as the function result).	Eliminated unexpected system behavior.
Settings storage.	Each operation with the standard settings storage includes a check for SaveUserData access right. Calls of StandardSettingsStorageManager.SetDescription() method include a check for SaveUserData access right.	Operations with the standard settings storage included checks for SaveUserData access right only if they were performed from 1C:Enterprise script. Calls of StandardSettingsStorageManager.SetDescription() method did not include a check for SaveUserData access right.	Eliminated unexpected system behavior. In particular, commands related to dynamic list settings are no longer available to users that do not have SaveUserData access right.
Data composition system.	Items of conditional appearance of data composition system are applied using the following rules: More specific conditional appearance items have higher priorities (this behavior did not change).For example, if a report, a table, and a table grouping have conditional appearances, they are prioritized as follows: table grouping (the highest priority), table, and report (the lowest priority). Parts of a conditional appearance item are prioritized in accordance with their relative positions in the list: the lower the position, the higher the priority. This change is not implemented in version 8.3.11 compatibility mode.	Items of conditional appearance of data composition system were applied using the following rules: More specific conditional appearance items had higher priorities. Parts of a conditional appearance item were prioritized in accordance with their relative positions in the listвЂ”the lower the position, the higher the priority.The only exception to this rule was the list of conditional appearance items that included parts with specified filters and specified or unspecified formatted fields. In this case the conditional appearance items with formatted fields specified were applied first.	Eliminated unexpected system behavior.
Data composition system.	In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field affects the filter presentation. This change is not implemented in version 8.3.11 compatibility mode.	In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field did not affect the filter presentation.	Improved filter presentations in dynamic lists and data composition system-based reports.
Infobase operations.	When administrative infobase parameters are set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior is different from that of the previous versions. For details, see 1C:Enterprise documentation.	When administrative infobase parameters were set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior was different. This behavior was not documented.	Setting administrative infobase parameters is more intuitive and predictable.
Interface.	In managed applications, calls of SwitchInterface() global context method are ignored in all client modes. We recommend that you do not use ordinary forms in managed client application mode. This change is not implemented in version 8.3.11 compatibility mode.	In managed applications, calls of SwitchInterface() global context method displayed command bars.	Eliminated unexpected system behavior.
1C:Enterprise script.	When CurrentLanguage() global context function is called on the server, in the thick client, or in an external connection, it returns the interface language of the current user. If the current user is not specified, or the interface language is not specified, or the specified interface language is not included in the configuration, the function returns the default configuration language. The CurrentLanguage() function behavior is now uniform across all modes. This change is not implemented in version 8.3.11 compatibility mode.	When CurrentLanguage() global context function was called on the server, in the thick client, or in an external connection, if the interface language specified for the current user was not included in the configuration, the function returned Undefined. The CurrentLanguage() function behavior on the client and on the server was not uniform.	Eliminated unexpected system behavior.
Data composition system.	In a nested query included in the right part of a left join, its WHERE section does not include an explicitly specified field, and the parent query includes a different field with the same data composition name, the template composer does not include the filter to the nested query. To preserve the previous query behavior, explicitly specify a field in the WHERE section. This change is not implemented in version 8.3.11 compatibility mode.	When filling available data set fields, the template composer always included the filter in the nested query.	The result of automatic filling of available data set fields is more predictable.
Internet-enabled functionality.	In InternetMail.Logon() method, implemented authentication request with the user name and password if APOP authentication fails.	The InternetMail.Logon() method generated an exception if APOP authentication failed. The authentication attempt with the user name and password was not performed.	The user authentication on the mail server better complies with RFC 1939 standard.
Managed forms.	In OpenForm() method, changed the algorithm of searching for an open form instance. When a data processor form or a report form is opened, the search algorithm analyzes the owner of that form. When a main object form specified in the configuration or the overriding form specified in FormGetProcessing() handler is opened, if its owner is not specified, the owner window is not blocked, and a form instance is already open, the search will find it (in the thin and web clients). This change is not implemented in version 8.3.11 compatibility mode.	The following algorithm of searching for an open form instance was used. When a data processor form or a report form was opened, the search algorithm did not analyze the owner of that form. When a main object form specified in the configuration or the overriding form specified in FormGetProcessing() handler was opened, if its owner was not specified, the owner window was not blocked, and a form instance was already open, a new form instance was opened (in the thin and web clients).	Eliminated unexpected system behavior. Unified the algorithm that searches for an open form in different client application modes.