Version 8.3.15 – 1Ci Support

Version 8.3.15 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
Mobile version of "1C:Enterprise"
Demo configuration changes
Changes made after the publication of the version
Transition from the previous version to the version 8.3.15

New functionality and changes

Functionality	After	Before	Result of changes
Configuration properties.	For configuration property Compatibility mode, new value Version 8.3.14 is now implemented.	Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1-8.3.13 was available.	Configurations developed using 1C:Enterprise platform version 8.3.14 or earlier can now run on version 8.3.15 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.15 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.14 after the migration to version 8.3.15, even if you disable the compatibility mode (simply enable it again).
1C:Enterprise script.	If some errors occur, a stack of calls leading up to the error (not related to nested exceptions) is now displayed in detailed error description. In 1C:Enterprise Development Tools, call stack navigation is now available.	If an error message occurred, detailed error description did not include a call stack leading to the line with error (except for nested exceptions).	Improved diagnostics of application errors.
Internet-enabled functionality. Administration tools. Event log.	Implemented two-factor authentication. New data for event log events: _$Session$_.Authentication, _$Session$_.AuthenticationError, _$User$_.New, _$User$_.Update. Implemented the following event log events: _$Session$_.AuthenticationFirstFactor, _$InfoBase$_.SecondFactorAuthTemplateNew, _$InfoBase$_.SecondFactorAuthTemplateUpdate, _$InfoBase$_.SecondFactorAuthTemplateDelete	This feature was not provided.	Expanded user authentication options. More secure user authentication is available now.
Charts. Data composition system.	New feature: doughnut and 3D doughnut charts. New properties for the ChartType system enumeration: Donut and Donut3D. Implemented the Chart.DonutChartInnerRadius property. Implemented the ChartType.DonutChartInnerRadius parameter for the following objects: DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance.	This feature was not provided.	New chart features.
Spreadsheet documents.	Now you can specify a formatted string as a spreadsheet document header or footer. Included the FormattedString type in types of the following properties of the SpreadsheetDocumentHeaderFooter object: LeftText, CenterText, and RightText. With an editor of spreadsheet document headers and footers, you can edit a formatted string. When you start editing the relevant field with the header or footer text, the check box of output of the relevant header or footer to the spreadsheet document is selected automatically. Upon exporting a spreadsheet document, formatting of headers and footers is saved in the following formats: PDF (.pdf), Microsoft Office OpenXML (.xlsx and .docx), Microsoft Excel (.xls), and Open Document Spreadsheet (*.ods). For more information on how to use a formatted string for displaying headers and footers, see 1C:Enterprise documentation	This feature was not provided.	Expanded spreadsheet document export features.
Spreadsheet documents.	New feature: you can save a spreadsheet document to PDF/A-1 (a format for long-term storage). When you save to PDF/A-1 format, remember the following: Document is written as PDF 1.4. Duplex printing is not supported. Transparency is not supported. Implemented the SpreadsheetDocumentFileType.PDF_A_1 system enumeration value.	This feature was not provided.	Expanded spreadsheet document export features.
macOS. Collaboration system.	Client applications running under macOS now support collaboration system video calls.	This feature was not provided.	Implemented collaboration system features under macOS.
Data composition system.	New feature: you can save changes upon closing a form for the report settings form and the form for editing a report option. User prompt is generated before saving. The upgrade is valid only if the StandardProcessing parameter of the BeforeClose form event handler is set to True.	This feature was not provided. Upon closing the form, changes in the form were lost.	Reduced risk of losing changes made in the report settings form or the report option form in case of incorrect closing of the editing form.
Database copies. Information registers. Accumulation registers. Standard functions.	New feature: you can transfer not all register data but data only for a specific period to a copy for information registers and accumulation registers. This feature is available only for a standard replication. New property: DatabaseCopyContentItem.Filter. New feature for the Database copy management standard data processor. You can set filter by a period for information registers and accumulation registers. New feature: upon defining the query place, you can analyze a period condition in addition to the existing checks.	This feature was not provided.	Extended database copy management features. Improved performance of the database copy management feature by reducing data passed to a copy.
Database operations. Common attributes / Data separation.	New feature: you can get the data size that this data occupies in DBMS tables (including a specific data area). Upon calculating the size, the size of data history, extensions, and platform service tables (indexes, etc.) is not considered. New global context method: GetDataBaseDataSize().	This feature was not provided.	New feature: you can estimate the size of data available in a database area or table.
Configuration extensions.	New feature: you can mark a managed extension property so that a mismatch of this property in the extended configuration and in the extension will not block the extension use, but a user will get a message stating that the property value in the extension and the property value in the extended configuration do not match.	This feature was not provided.	New feature: informing of changes of some extended configuration properties is available. Changing such properties does not block extension use, but this change must be processed by the extension developer separately.
Configuration extensions. Development tools.	New feature: you can map extended configuration objects and extensions by IDs. Implemented the feature helping to resolve conflicts upon rename conflicts. Mapping objects by IDs can be disabled. New property for the configuration extension: Support mapping to extended configuration objects by internal IDs. New property for adopted extension objects: Extended configuration object.	Extended configuration objects and extensions were mapped only by names.	Simplified diagnostics of renaming an extended configuration object adopted to an extension. Now there is a feature for resolving conflicts upon such rename.
Configuration extensions.	Upon creating a new extension, the Compatibility mode extension property is no longer a managed property.	Upon creating a new extension, the Compatibility mode extension property was a managed property.	Simplified development and applicability of extensions.
Data display.	New pictures are added to the picture library: Notify, DontNotify, DontDisturb, and SendMessage.	The listed pictures were not available in the picture library.	The picture library is upgraded.
Configuration extensions.	New feature: you can adapt extended configuration methods. An extended method is fully copied to an extension where changed code is enclosed by preprocessor directives. During application, it is checked whether the extended method is not changed in relation to the method in the extension. New annotation: ChangeAndValidate. New preprocessor directives: Delete and Insert. You can change one method only in one extension. If two extensions that extend the same method using the ChangeAndValidate annotation are found, only one extension will be applied to the infobase. If a method change in the extended configuration is found, three-way merge using an external application only is available. If an external application for comparing and merging modules is not configured in Designer, merge will be unavailable.	Making changes to the method with control of module source code consistency was unavailable.	Simplified extended configuration method extension if a small method change is required.
Web client.	When you start the web client on mobile devices, there is no message prompting that the used web browser version is not supported. New feature: partial support of the web client on mobile devices. Full support of the web client on mobile devices is not implemented. Fixed problems that occur in the web client on mobile devices in main scenarios.	Web client was supported on iPad tablets only.	Web client is partially available on mobile devices.
Common objects.	New feature: upon solving a system of linear equations, you can search for connected components of various types for graphs built based on a system of linear equations. Implemented the ComponentsGetMethod parameter of the SolvingLinearEquationsSystems.GetConnectedComponents() method. In 8.3.14 version compatibility mode, this parameter value will be StronglyConnectedComponentsWithoutLinkRequirementWithinComponents.	This feature was not provided.	Advanced features for solving a system of linear equations.
Collaboration system.	New link to collaboration system messages. Implemented the CollaborationSystemStandardCommand.GetMessageURL system enumeration value.	This feature was not provided.	Now you can obtain links to specific collaboration system messages.
Managed forms.	New feature: a flag field of a client application form can be displayed as an off-on switch. New property of the CheckBoxType.Switch system enumeration. In version 8.3.7 or earlier compatibility mode and in platform version earlier than 8.3.15, the CheckBoxType property value set to the Switch value is the Auto value.	This feature was not provided.	Extended system presentation features.
Managed forms.	The client application displays a text document, a spreadsheet document, a graphical schema, and a picture in the client application system form. This is available in the following cases: When you create or open a document using the File menu. When you call the Show() method of the relevant 1C:Enterprise language object or the ShowValue() method for the Picture type object. When you drag a file from the operating system. When you open a collaboration system attachment. A form with a displayed spreadsheet document or graphical schema has a command bar making editing of the relevant document easier. New events for a form field extension for a spreadsheet document, a text document, and a graphical schema: BeforeWrite, AfterWrite and BeforePrint. This change is not implemented in version 8.3.14 compatibility mode.	The client application displayed a text document, a spreadsheet document, a graphical schema, and a picture in special forms. Such forms did not have command bars.	Editing platform documents is now more convenient and intuitive. You can now process saving and printing of a text document, a spreadsheet document, and a graphical schema.
Managed forms.	Implemented the option to manage the command home position in the command bar: In the More actions menu only. In command bar only. Both (a command bar and the More actions menu). Determine automatically. New form button property: LocationInCommandBar. The OnlyInAllActions form button property is deprecated and supported for compatibility purposes only. Implemented automatic filling of the LocationInCommandBar property based on the OnlyInAllActions property. Now this mode is available for the client application form button when there is no more than one button linked to one command inside the automatically filled group. New client application button property: CommandUniqueness. New property for the picture field extension and the Picture kind decoration: Scale. This property is ignored in version 8.3.6 or earlier compatibility mode.	For a client application form command, only an indication that a command was located either in the command bar or in the More actions menu was available.	Improved options for creating command interface of the client application form.
Data display.	New pictures are added to the picture library: ZoomOut and ZoomIn.	The listed pictures were not available in the picture library.	The picture library is upgraded.
Managed forms.	The following features are available for the Planner object: Control of planner item representation if there is not enough space in the field: show all items by changing the line height or saving the line height, and show the More actions menu. Implemented the Planner.ItemsBehaviorOnLackOfSpace property. You can set the minimum column height and width of the planner. As a result, instead of constant reduction of planner items, it will be possible to save the minimum item size and add a scroll bar if items do not fit the form field. New properties for the Planner object: ColumnMinWidth, AutoColumnMinWidth, RowMinHeight, and AutoRowMinHeight. Freeze a dimension title and a time scale of the planner. Fixed objects will be visible for a user upon scrolling the planner. New properties for the Planner object: FixDimensionsHeader and FixTimeScaleHeader.	These features were not provided.	New planner features.
Collaboration system.	New feature: you can define a list of selecting collaboration system users upon creating a context conversation message, a noncontext conversation message, or a video call. You can now create a form of selecting collaboration system users. New event for the ClientApplicationForm object and client application module: CollaborationSystemUserAutoComplete. New event for the ClientApplicationForm object and client application module: CollaborationSystemUserChoiceFormGetProcessing. New сonfiguration property: DefaultCollaborationSystemUserChoiceForm. You can now get a context conversation ID in the client application form (on the client application side). Implemented the BeginGettingConversation() method.	There was no option to override a list of selecting collaboration system users upon selecting a user. Earlier, you could get a context conversation ID on the server side only.	New collaboration system operations for selecting users upon creating messages, conversations, and video calls.
Interface.	Updated the Taxi interface. New appearance includes the following main changes: Main application window (running under Windows) has no title by default. Created the main panel containing access to primary tools of the command interface. Tools panel commands are reallocated between other interface items. The tools panel is no longer available as a separate panel. The system command bar is no longer available. Changed the main menu components and location. Changed the appearance of auxiliary windows and dialog boxes. Created a global search bar displayed in the main panel of the main application window. Global search bar is unavailable in the following main window modes: kiosk, workplace, and full-screen workplace. You can set up search behavior using 1C:Enterprise language. Implemented the GlobalSearch global context property. New application module events: OnGlobalSearch and OnGlobalSearchResultChoice. New feature: using the search bar, you can open a link, an external resource URL, perform arithmetic operations, and so on. New command Search everywhere in the context menu of some form items (with supported selection). The search is carried out using the search bar. New Get link button in the auxiliary window title. Implemented the StrFindAndHighlightByAppearance() global context method that allows you to highlight some substrings in the string. The ClientApplicationInterfaceContentSettingsItem object cannot be created for the ToolsPanel panel. The tools panel is ignored in the settings of the main application window panels. New methods for the ClientApplication object: GetOSTitleRepresentation() and SetOSTitleRepresentation(). The Default search form сonfiguration property is deprecated. We recommend that you use global search feature instead.	The Taxi interface had different appearance.	Improved application navigation, increased usability, and developed the interface in accordance with modern trends in interface creation.
Spreadsheet documents.	Upon editing spreadsheet document headers and footers, automatic calculation of the page field size is available now if the specified header or footer cannot be placed in the current page field sizes. To calculate the size, click Ok in the headers and footers editing form and page parameter setting form. New feature: you can get the header or footer size. New feature: you can get the page field size. New methods for the SpreadsheetDocument object: CalculateHeaderSize(), CalculateFooterSize(), GetPrinterTopMarginSize(), GetPrinterBottomMarginSize(), GetPrinterLeftMarginSize(), and GetPrinterRightMarginSize().	This feature was not provided. Earlier, you could pick the size of fields, headers, and footers only manually or iteratively.	New feature: spreadsheet document page fields can be set automatically according to the specified header or footer.
Full-text search.	Implemented search by meaningful word parts. In search results, a word is now highlighted if it has a meaningful part. New feature: you can specify meaningful word parts in user dictionaries of full-text search. New item for a description file of a user dictionary of full-text search: <Roots>. To enable search by meaningful word parts, rebuild a full-text search index. It works automatically if the Russian language is selected in regional infobase settings or a user dictionary of full-text search with a list of meaningful word parts is specified for the infobase. New methods for full-text search manager: GetSeparationOfCompositeWordsMode() and SetSeparationOfCompositeWordsMode().	This feature was not provided.	Improved full-text search usability.
Dumping configurations to files/Restoring configurations from files.	If you need to dump configuration information (the DumpConfigToFiles command of Designer batch mode) in a file with objects to dump (the listFiles dump command parameter), specify the Configuration ID. There is no need to specify a configuration name.	If you needed to dump configuration information (the DumpConfigToFiles command of Designer batch mode) in a file with objects to dump (the listFiles dump command parameter), you needed to specify the Configuration ID and a configuration name (dot-separated).	Simplified configuration dump to XML files.
Collaboration system.	Now you can block a collaboration system user. A blocked user cannot interact with the collaboration system. Now you can determine a linked infobase user by a collaboration system user. New properties for the CollaborationSystemUser object: IsLocked and InfoBaseUserID. Implemented the GetUsers() method for the collaboration system manager. Standard data processor of collaboration system management supports blocking and unblocking of collaboration system users.	These features were not provided.	New operations with collaboration system users. Now you can disable a user from the collaboration system, for example, if a user is fired.
Data display.	New pictures are added to the picture library: ExclamationDialog, QuestionDialog, StopDialog, and InformationDialog.	The listed pictures were not available in the picture library.	The picture library is upgraded.

Table of contents

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Dynamic lists. Managed forms.	Typing a text in a form table linked to a dynamic list does not lead to an input focus change and search start if the following conditions are met: Form item addition Search bar is available in the form. For the form table, the Search upon character input property is set to Do not use. This change is not implemented in version 8.3.14 compatibility mode.	Typing a text in a form table linked to a dynamic list led to an input focus change and search start if the following conditions are met: Form item addition Search bar is available in the form. For the form table, the Search upon character input property is set to Do not use.	Eliminated unexpected system behavior.
Standard functions.	For the Active users standard function, the list update button is moved to the beginning of the list form command bar.	For the Active users standard function, the list update button was located at the end of the list form command bar.	Unified list update command location in various forms of standard functions.
Standard functions. Server clusters.	New standard function: Server management. This function is similar to the cluster management console. It requires a server cluster administration server for all servers to be administered. Server operations are carried out using the ServerAdministration object. For a list of functional differences between the standard function and the cluster console, see 1C:Enterprise documentation. The standard function system requirements are the same as the system requirements of the ServerAdministration object.	This feature was not provided. Interactive server cluster administration was available from the cluster management console only.	Interactive server cluster administration is now available not only under Windows. Cluster administration tools are available in the client application using the All functions dialog box.
Standard functions. Data history.	Implemented the standard function that allows you to view data history, set an arbitrary filter, and update data history interactively.	Viewing data history of a certain data object only was available in the platform. Custom filter setup to view history was unavailable.	Extended interactive data history operations.
Managed forms. Interface. Collaboration system.	Upon form scaling, the scale is shown on a logarithmic scale. 100% value is in the middle of the scale. New feature: you can click a middle button to: Close search state items (in a dynamic list). Remove recipients from collaboration system context conversations. Remove attachments from unsent collaboration system messages.	Upon form scaling, the scale was shown on a linear scale. 100% value was at the beginning of the scale. You could close search state items (in a dynamic list), remove recipients from context conversations of the collaboration system, and remove attachments from unsent messages of the collaboration system only using the required object control (X in the right part of the item).	Improved application interface usability.

Table of contents

Optimization

Table of contents

Changes that affect system behavior

Functionality	After	Before	Result of changes
Data composition system.	If a type of one of the operands in a data composition system expression is arbitrary, the resulting expression will also have an arbitrary type. This change is not implemented in version 8.3.14 compatibility mode.	If a value with an arbitrary type was present in a data composition system expression, an arbitrary type was ignored upon calculating the resulting expression time.	Eliminated unexpected system behavior.
Interface.	Edited pictures in the client application interface (and in the picture library) for the spreadsheet document commands used for collapsing and expanding all groups.	Pictures in the client application interface (and in the picture library) for the spreadsheet document commands used for collapsing and expanding all groups were different.	Now pictures of the spreadsheet document commands used for collapsing and expanding all groups of the spreadsheet document better correspond to performed actions.
Development tools.	In the form editor, the Action property of the adopted form command contains a name of the method, which is a command handler in the extended configuration. Navigation to the command handler is unavailable.	In the form editor, the Action property of the adopted form command contains a name of the method, which is a command handler in the extended configuration. Navigation to the command handler generated an error.	Eliminated unexpected system behavior.
Queries.	Query language operation CASE will be considered a constant and replaced with a constant if all operation branches contain only constant expressions. Therefore, operation CASE can be used in constant parameters of virtual tables if all branches of operation CASE contain only constant expressions. If an operand of operation CASE contains NULL in query totals, then the operation result will be a value specified in ELSE or NULL if it is absent. This change is not implemented in version 8.3.14 compatibility mode.	Query language operation CASE was not replaced with a constant and could not be used in constant parameters of virtual tables. Upon calculating operation CASE in query totals, if the operation operand contained NULL, the operation result was NULL.	Eliminated unexpected system behavior.
Managed forms.	New feature: you can change properties of client application form items without calling a server: Decoration: Decoration label extension: Form group extension for a command bar: Form group extension for a page: Form group extension for a normal group: Button Form field extension for picture field:	This feature was not provided. Accessing the specified properties of client application form items required a server call.	Reduced client/server interaction upon managing a client application form using 1C:Enterprise language.
Collaboration system.	Implemented the following features in the collaboration system interface: Upon editing a message, the cursor is placed at the end of the message text. Upon sending a message, trailing spaces are trimmed in the message. You can open a collaboration system user profile by clicking the user avatar. The unread mark is cleared in a conversation if any of the following actions is carried out: Click a link in a message. Click a username or a user avatar. Click an attachment in a message. Click a message action. Right-click (open the context menu). When the default collaboration system form is first opened, the first conversation is not activated. In the thick and thin client applications, you can select a notification in the notification center by clicking a message picture. The upgrade is ignored in the web client. Changed the standard user group picture in the drop-down list of user selection.	The collaboration system interface had different behavior: Upon editing a message, the cursor was not placed at the end of the message. Upon sending a message, leading and trailing spaces were trimmed. A user profile was opened by clicking a username. When the default collaboration system form was first opened, the first conversation was activated. In the thick and thin client applications, you could select a notification in the notification center only by clicking a message text. In the web client, you could select a notification by clicking a message text or a message picture.	Improved collaboration system interface.
Data composition system.	Commands Generate, Print, Save, and Compact mode will be added to the report form command bar (with enabled automatic filling) if a property of the report form Report result is set. If a property of the report form Report result is not set, commands Generate, Print, Save, and Compact mode will not be added to the report form command bar, which is filled in automatically. This change is not implemented in version 8.3.14 compatibility mode.	Commands Generate, Print, Save, and Compact mode were always added to the report form command bar with enabled automatic filling.	Eliminated unexpected system behavior.
Charts.	If a format is not set explicitly for number presentations in the chart settings, the default format (considering regional infobase settings) will be applied to the numbers. This change is not implemented in version 8.3.14 compatibility mode.	If a format was not specified explicitly for number presentations in the chart settings, no specific formatting was applied to the numbers.	Eliminated unexpected system behavior.
Managed forms.	If an input field is in the list selection mode, you can search for the value as follows: First, presentations are searched by the beginning of the line if the presentation is specified explicitly. Then search considering a list value type is carried out: This change is not implemented in version 8.3.14 compatibility mode.	If the input field was in the list selection mode, search was carried out by the beginning of the line for all types in the specified presentation or if the presentation was not specified, search was carried out in a string value presentation from the selection list.	Now search in input fields, which use a selection list, is more predictable and better meets user expectations.
Collaboration system.	New feature: in the collaboration system, you can manage a number of received notifications for context and noncontext conversations. You can disable notifications of a conversation, receive notifications only for the messages to a user, or receive notifications of all messages. This feature can be set up using both user interface and 1C:Enterprise language. Implemented methods GetWatchMode() and SetWatchMode() for noncontext conversations. Implemented the User parameter for the GetWatchMode() and SetWatchMode() methods. Implemented the following methods of the collaboration system manager: SetConversationNotificationRepresentation() and GetConversationNotificationRepresentation().	Previously, you could only disable all notifications in a collaboration system. The GetWatchMode() and SetWatchMode() methods were used for context conversations only.	Expanded capabilities of the collaboration system interface.
Managed locks. Collaboration system.	New feature: now in the client application (thin, thick, and web client), you can unlock object lock set by another user or the same user in another session. An object lock is a lock set interactively upon editing an object in the form or using methods Lock(), LockDataForEdit(), and LockFormDataForEdit(). Now when you find a lock, you can start a conversation with a lock initiator in collaboration system (if the infobase supports the collaboration system).	This feature was not provided.	Simplified operations with infobase data in some cases.
Interface.	Implemented the following features for dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox() (in all client applications and Version 8.2 and Taxi interfaces): Updated the dialog boxes. If a title is not specified for a dialog box (in the relevant method parameter), this dialog box is opened without a title. Upon creating dialog boxes, scaling set for all forms in the Taxi interface is considered. Changed pictures displayed in the relevant dialog boxes in the Taxi interface.	Dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox() had different appearance and did not consider form scale in Taxi interface.	Improved appearance of dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox().
Spreadsheet documents.	Text orientation set for a spreadsheet document cell area is considered upon text output if the Windows system font is selected as a font. This change is not implemented in version 8.3.14 compatibility mode.	If the Windows system font was selected as a font of a spreadsheet document cell area, text orientation set for a spreadsheet document cell area was not considered upon text output.	Eliminated unexpected system behavior.
Data composition system.	Now you can apply conditional appearance of a column of a data composition system report table to the entire column if one of the following usage areas is selected for a conditional appearance item: In group, In hierarchical group, or <Everywhere>. This change is not implemented in version 8.3.14 compatibility mode.	If usage area In group, In hierarchical group, or <Everywhere> was selected for a conditional appearance item upon applying appearance of a column of a data composition system report table, appearance could be specified for a table header and column total only.	Eliminated unexpected system behavior.
Managed forms.	If a client application form contains one of the following items: a spreadsheet document field, a text document field, a graphical schema field, an HTML document field, a formatted document field, a geographical schema field, or a planner field, a submenu containing Print, Save, and Preview commands is generated in the form title. If there is more than one above-listed item in the form, menu commands are available for the current item of the specified type. Preview command is not displayed in the web client.	This feature was not provided.	Improved form usability.
macOS.	Add-ins work correctly in thin client (macOS) and Safari. Add-in revisions are not required.	Add-ins worked incorrectly in Safari but worked correctly in thin client (running under macOS).	Eliminated unexpected system behavior.
Queries.	The following query language functions can be used as virtual table parameters that can have constant values only: SUBSTRING(), YEAR(), QUARTER(), MONTH(), DAYOFYEAR(), DAY(), WEEK(), WEEKDAY(), HOUR(), MINUTE(), and SECOND(). You can use them only if all parameters have constant values in the specified functions. In this case, the calculated function value is added as a parameter value. This change is not implemented in version 8.3.14 compatibility mode.	The following query language functions could not be used as virtual table parameters that can have constant values only: SUBSTRING(), YEAR(), QUARTER(), MONTH(), DAYOFYEAR(), DAY(), WEEK(), WEEKDAY(), HOUR(), MINUTE(), and SECOND().	Now you can use date/time functions as parameters that can take only constant values, and virtual register tables in the query language. This is possible only if functions have constant values as parameters.
Spreadsheet documents.	Now you can edit (both interactively and using 1C:Enterprise language) page parameters of a spreadsheet document converted into compact mode. For a compact spreadsheet document, you can now call the SetHorizontalStretch() method. Upon editing a compact spreadsheet document, both the compact document and the original document are changed.	A compact spreadsheet document did not support setting up page parameters.	Settings of spreadsheet document parameters for print and view are now more convenient.
Managed forms.	In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsHorizontalAlign property set to Left, Center, or Auto (which is the same as Left or Center), all last form items or group items, for which the HorizontalAlignInGroup property value is set to Right up to the item, for which the HorizontalAlignInGroup property value is not equal to Right, are aligned right. In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsVerticalAlign property set to Top, Center, or Auto (which is the same as Top or Center), all last form items or group items, for which the VerticalAlignInGroup property value is set to Bottom up to the item, for which the VerticalAlignInGroup property value is not equal to Bottom, are aligned bottom. This upgrade is ignored in 8.3.13 version compatibility mode.	In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsHorizontalAlign property set to Left, Center, or Auto (which is the same as Left or Center), only the last item in a form or a group was aligned right. In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsVerticalAlign property set to Top, Center, or Auto (which is the same as Top or Center), only the last item in a form or a group was aligned bottom.	Eliminated unexpected system behavior.
Mobile application builder.	New feature: cleanup of the Mobile application builder cache directory. Artifacts saved to the cache directory more than 30 days ago are deleted. Temporary build directories remaining after unexpected build termination or interruption are also deleted. This does not require setup and is fully automatic.	The Mobile application builder cache could increase in size only. The Mobile application builder did not provide cleanup of unused cached artifacts.	Stopped the uncontrolled growth of the Mobile application builder cache directory. The builder caches only the artifacts used during build for the last 30 days.
Full-text search. Server clusters.	The full-text search string cannot contain more than 1,000 words. An error occurs upon excess. Functional words and search operators are not considered when counting the number of words.	The number of words in the full-text search string was not limited. Specifying a very large number of words in the search string could significantly reduce server cluster performance.	Improved application stability. Reduced risk of affecting the application responsiveness as a whole by specifying a very large full-text search string.
Database operations.	Enhanced database integrity check upon database configuration update. Several database tables can no longer get the same internal number. In this case, an exception is thrown and the database is not updated.	Upon database configuration update, internal numbers of database tables were not checked for uniqueness. As a result, various unexpected errors could occur when using the information system.	Eliminated unexpected system behavior.
File operations.	If thin client connects to the infobase via web server using HTTPS protocol, upon using the GetFile(), GetFiles(), BeginGettingFiles(), BeginGetFileFromServer(), and BeginGetFilesFromServer() methods, reauthentication on the web server is no longer required.	If thin client connected to the infobase via web server using HTTPS protocol, upon using the GetFile(), GetFiles(), BeginGettingFiles(), BeginGetFileFromServer(), and BeginGetFilesFromServer() methods, reauthentication on the web server was required.	Eliminated unexpected system behavior.

Table of contents

Changes that require modification of configuration and administrative settings

Functionality	After	Before	Result of changes
Data composition system.	Composer of data composition template does not use the presentation expression specified for the calculated field upon generating an expression of group and total records for calculated fields being resources. Thus, the presentation expression for calculated fields being resources will be displayed in the report in detailed records only. This change is not implemented in version 8.3.14 compatibility mode.	Composer of data composition template used an expression of the calculated field presentation being a resource in detailed, group, and total records.	Behavior of composer of data composition template is the same for calculated fields, data set fields, and calculated resource fields.
Queries. Data composition system.	Right joins are not replaced automatically with similar left joins upon processing query text with the query constructor, query scheme, data composition system, and report builder. This change is not implemented in version 8.3.14 compatibility mode.	Right joins were replaced automatically with similar left joins upon processing query text with the query constructor, data composition system, and report builder. If conversion failed to be performed, the connection was removed from the query.	Eliminated system behavior which could lead to an incorrect query.
File operations. Web client.	Implemented the BeginGetFileFromServer() and BeginGetFilesFromServer() global context methods. In the interactive mode, methods do not require installing a file system extension on web client. New feature: you can get several files from the server as an archive. The BeginRequestingUserPermission() method allows you to request user permission for new methods. The GetFile(), BeginGettingFiles(), and RequestUserPermission() methods are deprecated and supported for compatibility purposes. It is recommended that you use new methods in the application.	Current methods of receiving files from the server were not logical. Method of receiving several files from the server (BeginGettingFiles()) in the web client required a file system extension.	Getting files from the server is now more transparent and convenient. Now a file system extension is no longer required to use the web client in the interactive mode.
File operations. Web client.	Implemented the BeginPutFileToServer() and BeginPutFilesToServer() global context methods. In the interactive mode, the methods do not require installation of a file system extension on web client. New feature: displayed progress of placing a file to the server. New feature: cancel placing a file to the server. New feature: simultaneous transfer of several files from a client computer to the server. Files being transferred are specified using the file search string. The BeginRequestingUserPermission() method allows you to request user permission for new methods. The BeginPutFile(), BeginPuttingFiles(), and RequestUserPermission() methods are deprecated and supported for compatibility purposes. It is recommended that you use new methods in the application.	Existing methods of transferring files to the server (BeginPutFile(), BeginPuttingFiles()) did not allow to cancel placing files during transfer and display the transfer progress.	Putting files to the server is now more transparent and convenient. Now a file system extension is no longer required to use the web client in the interactive mode.
Database operations. Common attributes / Data separation. 1C:Enterprise script.	Method FindMarkedForDeletion() will search all available objects of the current data area only if the Undefined value is passed as a value of the first and the second method parameters. This change is not implemented in version 8.3.14 compatibility mode.	Method FindMarkedForDeletion() searched all available objects of the current data area only if the Undefined value was passed as a value of the first method parameter only.	Unified set of parameters and behavior of methods with similar actions.
Queries.	Query language behavior changes if: query is a merge of several queries, which are applied to a unified query and each merge query uses the TOP keyword. In this case, each query in the merge turns into a nested query with ordering. If any of the nested query does not have the TOP keyword, subquery is not built by ordering. It is recommended that you analyze when queries that meet these conditions are used. When the compatibility mode is disabled, performance result of such queries can be different from the performance result of this query in compatibility mode. This change is not implemented in version 8.3.14 compatibility mode.	Query language behavior if: query was a merge of several queries, which were applied to a unified query and each merge query used the TOP keyword, depended on the infobase option: For file mode: first ordering, then selection of top records. For client/server mode: first selection of the top ones (for each simple query). Ordering was not executed for simple queries. Ordering was executed only for merge result. Result repeatability was not guaranteed as the top items were selected from the query without ordering.	Implemented similar behavior of a query containing merge, ordering, and the TOP keyword in various infobase mode options.
Server clusters.	Upon editing a server cluster resource consumption counter, the counter is reset only if the Group property is changed. Implemented reset of a resource consumption counter instance: The Delete command is implemented for a resource consumption counter instance. The clear command is implemented for the rac counter command. The IAgentAdminConnection.clearAccumulatedValues() method is implemented for Java interface of server cluster administration. The AdministrationResourceConsumptionCounter.ClearAccumulatedValues() method is implemented in 1C:Enterprise language. Now you can get a list of resource consumption counter values: The accumalated-values command is implemented for the rac counter command. The IAgentAdminConnection.getAccumulatedResourceConsumptionCounterValues() method is implemented for Java interface of server cluster administration. The AdministrationResourceConsumptionCounter.GetAccumulatedValues() method is implemented in 1C:Enterprise language. For a resource consumption counter instance, a field containing measurement time is implemented. To get measurement time: The time property is implemented in the rac counter command output. The IresourceConsumptionCounterValue.getTime() method is implemented for Java interface of server cluster administration. The AdministrationResourceConsumptionCounter.Time property is implemented in 1C:Enterprise language.	Upon editing a server cluster resource consumption counter, the counter was reset if any of its properties were changed. Other features were not provided.	Improved administration of server cluster resource consumption. Simplified setting of counters and resource consumption restrictions. Now you can analyze changes of accumulated data.
Data composition system. Functional options.	In the data composition system, for the field separated by dot from the temporary table field or nested query, availability check includes checking that the field is not disabled with a functional option. This change is not implemented in version 8.3.14 compatibility mode.	In the data composition system, for the field separated by dot from the temporary table field or nested query, availability check did not include checking that the field is not disabled with a functional option. If a temporary table field or a nested query field was available, it was considered that all fields available via "." (dot) would also be available.	Eliminated unexpected system behavior.
Data composition system. Charts of characteristic types.	In the data composition system, a characteristic value type is considered upon getting a characteristic value (for any purpose, for example, sorting or filtering by it). If a value, which does not match the used characteristic value type, is written in the infobase, then NULL will be used instead. It is recommended that you analyze additional characteristics in the data composition system and make sure that the actual characteristic value type matches the type. This change is not implemented in version 8.3.14 compatibility mode.	In the data composition system, a characteristic value type is not considered upon getting a characteristic value (for any purpose, for example, sorting or filtering by it). Even if a value, which does not match the used characteristic value type, is written in the infobase, it will be used.	Improved performance of the data composition system with additional characteristics (charts of characteristic types) by reducing the number of tables used in queries.
Server clusters.	Changed rules and settings of 1C:Enterprise server cluster monitoring system. Optimized use of server RAM. In particular, both working process parameters and cluster manager parameters are used when determining the amount of used memory. New feature: server cluster setting, which allows you to specify whether a process dump is to be created when critical memory amount is exceeded. New feature: working server properties that describe a temporarily allowable amount of process memory, a time interval that describes exceeding time of a temporarily allowable amount of process memory, and a critical memory amount. The following settings are removed from the cluster properties: Allowed total memory. Period of exceeding the memory threshold. Threshold of server error variation. Settings that describe the amount of working process memory up to which server performance is considered to be sufficient, and the maximum working process memory are removed from the working process properties. However, the removed parameters will be saved in the cluster settings and used in a previous version of 1C:Enterprise. If you create a new cluster, some parameters will have the following default values: Force close corrupted processes – enabled. Close corrupted processes in 60 seconds. Upon creating a new working server, 256 connections per process will be established by default. If the removed parameters are changed in the cluster settings, it is recommended that you review the cluster settings and adjust them if necessary. Implemented the following objects: AdministrationCluster.WriteDumpWhenTerminatingByMemoryLimit property. TemporaryAllowedProcessesTotalMemory property for CriticalProcessesTotalMemory object, and TemporaryAllowedProcessesTotalMemoryExcessTimeLimit property for the AdministrationWorkServer object. IClusterInfo.KillByMemoryWithDump property. CriticalProcessesTotalMemory, TemporaryAllowedProcessesTotalMemory, and TemporaryAllowedProcessesTotalMemoryTimeLimit properties for the IWorkingServerInfo object. The following Java-based tools are implemented in the administration server interface: IsClusterRecyclingKillByMemoryWithDump() and setClusterRecyclingKillByMemoryWithDump() methods of the IClusterInfo interface. GetCriticalProcessesTotalMemory(), setCriticalProcessesTotalMemory(), getTemporaryAllowedProcessesTotalMemory(), setTemporaryAllowedProcessesTotalMemory(), getTemporaryAllowedProcessesTotalMemoryTimeLimit(), and setTemporaryAllowedProcessesTotalMemoryTimeLimit() methods of the IWorkingServerInfo interface. For the cluster service command-line utility (rac): Implemented the kill-by-memory-with-dump field for the cluster info command output. Implemented the kill-by-memory-with-dump parameter for the following commands: cluster update and cluster insert. Implemented the following command-line parameters for server insert and server update commands: critical-total-memory, temporary-allowed-total-memory, and temporary-allowed-total-memory-time-limit. The following properties are deprecated and supported for compatibility and interaction with previous cluster versions: ProcessMemoryLimit, MaxMemoryTimeLimit, and ProcessErrorCountLimit properties of the AdministrationCluster object. MaxMemorySize, MaxMemoryTimeLimit, and ErrorsCountThreshold properties of the IClusterInfo object.	Server cluster monitoring logic was different. Only working process parameters were used when determining the amount of used RAM. Maximum 128 connections per process were offered by default.	Optimized use of RAM by a server cluster.
Server clusters.	Upgrade: load balancing upon creating a new connection to the server cluster is updated. Upgrade: the algorithm to assess working process performance is updated.	Load balancing mechanism did not process some situations well enough. In particular, there was non-optimal working process load and load redistribution took a long time.	New connections will use available resources more evenly. Load redistribution among server clusters will be faster. Improved load balancing upon mass connections and disconnections of users to/from the server cluster.
Data history.	The version difference form contains information on moved rows in object tabular sections. A row number before and after movement is shown. After calling the GetVersionDifference() method, the following information will be available for the moved row: Property LineNumberAfterVersionChange is a new row number (after movement). Property LineNumberBeforeVersionChange is an old row number (before movement).	In the version difference form, the row number after change was adjusted considering actions performed between the first movement and the second movement, and the row number before change contained the row number in the version after change.	Eliminated unexpected system behavior.
Data history.	Upon using data history, now you can perform actions once a data version is written. New object manager module event (for objects that support data history): AfterWriteDataHistoryVersionsProcessing. New property available for objects that support data history: WriteDataHistory.AfterWriteDataHistoryProcessing. Use it to manage the need to call the AfterWriteDataHistoryVersionsProcessing event handler. Objects that require processing after writing data history are stored in a special queue. New method available for deleting objects from this queue: DataHistory.DeleteFromAfterWriteVersionsProcessing(). New configuration object property: ExecuteAfterWriteDataHistoryVersionProcessing. Now you can update data history once an object is written. History will be updated by a background job once an object write transaction is complete. New property: WriteDataHistory.UpdateHistoryImmediatelyAfterWrite. New configuration object property: UpdateDataHistoryImmediatelyAfterWrite. New data history manager method: ExecuteAfterWriteVersionsProcessing(). Now you can add new fields and tabular sections to a data history record. Tabular sections can be added only to those objects where metadata has tabular sections. New property: WriteDataHistory.AdditionalData. The GetMetadata() method (by a data version) of the data history manager returns information considering added properties and tabular sections. New methods for the WriteDataHistory object: AddAdditionalData() and AddAdditionalDataFieldPresentation(). Now you can cancel a data history record. New property: WriteDataHistoryParameters.Cancel. Implemented the WriteDataHistory.VersionComment property for a version comment record. The following methods of objects that support data history are deprecated and supported for compatibility purposes only: SetDataHistoryVersionComment() and GetDataHistoryVersionComment(). New parameters available for the UpdateHistory() method (in all syntax options) of the data history manager: ExecuteAfterWriteVersionsProcessing and AutoDeleteFromAfterWriteVersionsProcessing. Implemented manager module for constants. New system background jobs for processing after recording versions and for updating data history after recording.	These features were not provided.	Extended data history features.
Queries. Data composition system.	If the LIKE operation is used in the query language (also upon calculating a function in the TOTALS sentence) or the data composition system expression language in the infobase file mode, a special character specified inside the brackets using the ESCAPE keyword, works correctly. This change is not implemented in version 8.3.14 compatibility mode.	If the LIKE operation was used in the query language (also upon calculating a function in the TOTALS sentence) or the data composition system expression language in the infobase file mode, a special character specified using the ESCAPE keyword did not function inside the brackets.	Eliminated unexpected system behavior.
File infobase Queries.	In the file infobase, an addition operation and a subtraction operation of the query language are changed. Upon calculating length and precision of an operation type, preference is given to length rather than precision if the total length of 38 characters is exceeded. Therefore, if two numeric fields, the first of which has 20 characters and 0 precision and the second of which has 30 characters and 20 precision, are added together or subtracted, the resulting length will be 38 and the precision will be 18. If the second field contains a number with the last precision digits, the number will be cut by precision digits. Example: If you add 1,000,000,000,000,000,000 and 0.00000000000000000001, you get 1,000,000,000,000,000,000. If you add 1 and 0.00000000000000000001, you get 1. If you subtract 0.99999999999999999999 from 2,000,000,000,000,000,000, you get 1,999,999,999,999,999,999. This change is not implemented in version 8.3.14 compatibility mode.	Upon calculating length and precision of an operation type, preference was given to precision rather than length if the total length of 38 characters was exceeded. Therefore, if two numeric fields, the first of which had 20 characters and 0 precision and the second of which had 30 characters and 20 precision, were added together or subtracted, the resulting length would be 38 and the precision would be 20. Because of that, if the first number contained 20 characters in the integral part, a digit overflow error occurred as a result. This would be expressed by a number containing 9 in all parts. Example: If you add 1,000,000,000,000,000,000 and 0.00000000000000000001, you get 999,999,999,999,999,999.99999999999999999999. If you add 1 and 0.00000000000000000001, you get 1.00000000000000000001. If you subtract 0.99999999999999999999 from 2,000,000,000,000,000,000 you get 999,999,999,999,999,999.99999999999999999999.	Eliminated unexpected system behavior.
Collaboration system.	New feature: now you can register (and unregister) an infobase in the collaboration system on 1C:Enterprise server. New methods for the collaboration system manager: ExecuteInfoBaseRegistration() and CancelInfoBaseRegistration().	Earlier, you could register and unregister an infobase in the collaboration system on 1C:Enterprise client only.	Extended administrative actions in the collaboration system.
Managed forms. Data composition system.	Upon opening conditional appearance settings (saved in previous platform versions) with disabled compatibility mode, the following conditional appearance parameters of a form or a report will be set to default values: Conditional appearance items of a form (the DataCompositionParameterValue object): Line, Color, and Font. Conditional appearance items of a report (the DataCompositionAppearance object collection): Line, Color, Font, VerticalAlign, HorizontalAlign, Placement, TextPositionRelativeToPicture, and PictureSize. Changes are applied if values of these conditional appearance parameters are specified as a string and not values of a particular type. We recommend that you analyze where the above mentioned conditional appearance parameters are used and eliminate places where the parameters are set as a string. This change is not implemented in version 8.3.14 compatibility mode.	For some form or report conditional appearance parameters (the DataCompositionAppearance object collection), you could specify values (the DataCompositionParameterValue object) not only as values of particular types but also as a string. These parameters were the following: Conditional appearance items of a form: Line, Color, and Font. Conditional appearance items of a report: Line, Color, Font, VerticalAlign, HorizontalAlign, Placement, TextPositionRelativeToPicture, and PictureSize. You could see the following behavior: In conditional appearance of reports and upon reading parameter values from XML, a string was converted to a value matching the parameter type. Parameters were used with the values resulted from the conversion. In conditional appearance of dynamic lists, a string was not converted to a value. Default parameter values were used. In conditional appearance of forms (in thin client), a string was converted to a value. Parameters were used with the values resulted from the conversion. In conditional appearance of forms (in thin client), a string was not converted to a value. Default parameter values were used. In version 8.3.14, an error occurred in that case.	Eliminated unexpected system behavior.
Data composition system.	Upon calculating values of the data composition system fields listed below, the principle is applied: a if value of the resource, from which this field is received, is equal to 0 in the current grouping, the field value is also 0. These fields are the following: % total % in grouping % in hierarchy group % in row or series % in column or point % in row or series grouping % in column or point grouping % in row or series group % in column or point hierarchy group This change is not implemented in version 8.3.14 compatibility mode.	Upon calculating values of the following data composition system fields: % total % in grouping % in hierarchy group % in row or series % in column or point % in row or series grouping % in column or point grouping % in row or series group % in column or point hierarchy group you could see the following behavior: values were always divided by a parent grouping value or grand total, except for cases when the resource value in the grouping was equal to NULL. As a result, an exception could be thrown due to division by 0.	Eliminated unexpected system behavior.
Charts.	Upon assigning a new value to the Chart.DataSource property, first, the existing points and series are deleted, and then the new ones are created according to the new data source. After a new value is assigned, the current selection is cleared. We recommend that you remember the current selection before setting new data and restore it if necessary. This change is not implemented in version 8.3.14 compatibility mode.	Upon assigning a new value to the Chart.DataSource property, the existing points and series were not deleted and the selection was not cleared.	Eliminated unexpected system behavior.

Table of contents

Mobile version of "1C:Enterprise"

Functionality	After	Before	Result of changes
Mobile client. Development tools.	In the form editor preview panel, rounded screen corners and displays with a cutout are supported now (for mobile devices on iOS). iPhone models X/XS/XS Max/XR are added to the list of devices for preview in the form editor.	This feature was not provided.	Designing forms for the latest iPhone devices is easier now.
Mobile device-specific features. Mobile client. Mobile platform.	Now you can put a stamp on a photo indicating a photo date and time, as well as a custom text. New object: PhotoStamp. Implemented the Stamp parameter of the MultimediaTools.MakePhoto() method.	This feature was not provided.	Expanded photo management capabilities.
Mobile device-specific features. Mobile platform. Mobile client.	For mobile applications on Android, the sound is recorded in MPEG4 using AAC codec. For mobile applications on any mobile operating system, the sound is recorded in stereo, the bitrate is 128 kbps, and the sample rate is 44 kHz. The MultimediaTools.MakeAudioRecording() method returns the MultimediaData object where the file extension is set to m4a and the MIME type is set to audio/mp4.	The sound quality and the MultimediaTools.MakeAudioRecording() method result depended on the used operating system: Android: 3gp and mono; the sample rate was 8 kHz. 3gp extension and audio/3gp MIME type. iOS: m4a and stereo; the sample rate was 44 kHz. m4a extension and audio/mp4 MIME type. Windows: m4a and mono; the sound quality was selected automatically. aac extension and audio/aac MIME type.	Unified audio information recording result on different mobile operating systems. You can listen to a sound recording made in 1C:Enterprise mobile platform using standard tools of operating systems on personal computers.
Background and scheduled jobs. Mobile client.	Now you can use the scheduled job dialog on the mobile client. New object available on the mobile client: ScheduledJobDialog.	Editing a schedule for a scheduled job was not available on mobile client.	Now you can edit a schedule for a scheduled job on mobile client.
Mobile client. Mobile application builder.	In mobile client, you can add an infobase to the list by scanning a QR code. This feature is available if the mobile client application is permitted to add an infobase with a custom address. This feature is also available in mobile version for developers. In mobile application builder, you can allow users to add infobases using QR codes. In addresses related to schema e1c://, you can use the following commands: /AddByQRCode to start QR code scanning. /AddInfoBase to add the infobase to the infobase list of the client application.	This feature was not provided.	Advanced features for adding infobases to the list in mobile client or mobile platform. Simplified procedure of adding infobases.

Table of contents

Demo configuration changes

In the form of the stored files list, you can see an example on how to use new file operation methods.
The check box is displayed as a switch in the MobileDeviceSettings common form and in the main form of the SalesAggregateManagement data processor.
Implemented the form for selecting collaboration system users (the FormCollaborationSystemUserSelection common form) to demonstrate processing of collaboration system user selection.
Implemented a global search demo example. The example is implemented in the application module and in common modules GlobalSearchClient and GlobalSearchServer.
New features for spreadsheet document headers and footers available in the HeaderFooter extension, which is delivered together with the demo configuration.

Table of contents

Changes made after the publication of the version

Functionality	After	Before	Result of changes
Database copies.	Initial population of a database copy is faster now if source data includes documents generating records in registers and containing a large number of rows in tabular sections.	Initial population of a database copy took more time if source data included documents generating records in registers and containing a large number of rows in tabular sections.	Upgrade: faster initial population of a database copy.
Collaboration system.	On overriding the selection list of collaboration system users, on creating a context conversation message, the need to disable a user notification (displayed in the user interface as No notification) is passed as a special value of the ChoiceData parameter of the CollaborationSystemUserAutoComplete data processor. A special value can be created using the constructor of the CollaborationSystemUserID object without specifying a collaboration system user ID. The Undefined value is no longer allowed as a value of the ChoiceData parameter of the CollaborationSystemUserID data processor.	On overriding the list of selecting collaboration system users, on creating a context conversation message, the need to disable a user notification (displayed in the user interface as No notification) was passed as the Undefined value, which prevented distinguishing notification disable and closing the user selection form without any choice.	Eliminated unexpected system behavior.
Managed locks.	In client/server mode, a pessimistic object lock will be unconditionally released by the server cluster if the following conditions are met: There is an attempt to release an object lock set by another user (in a remote client application). The collaboration system is used to release the lock. The remote client application did not release the lock 5 seconds after sending the collaboration system message.	In client/server mode, an attempt to release a pessimistic object lock resulted in the message stating that editing was not possible if the following conditions were met: There was an attempt to release an object lock set by another user (in a remote client application). The collaboration system was used to release the lock. The remote client application did not release the lock 5 seconds after sending the collaboration system message.	Eliminated unexpected system behavior.
Server clusters.	Improved failover cluster reliability.	Failover cluster was unreliable.	Improved failover cluster reliability.
Mobile client. Mobile platform. Mobile application builder.	1C:Enterprise mobile platform running Android now supports 64-bit processors.Mobile application builder creates 4 versions of application that targets Android upon building: 32-bit x86 application 32-bit ARM application 64-bit x86_64 application 64-bit ARM64 application. You can now publish 64-bit applications in Google Play. Changed files in the following mobile version distribution archive: mobile.zip.	Mobile platform 1C:Enterprise running Android supported 32-bit processors only. Mobile application builder could not build and publish 64-bit mobile application versions in Google Play.	Expanded list of supported processor architectures for a mobile version running Android. Built mobile applications running Android are larger now. Built mobile applications running Android now perform faster.
Mobile platform. Mobile client. Mobile application builder.	Some single mobile application permissions were replaced by multiple permissions in order to meet requirements of application store owners. The Telephony permission is replaced with: Dialing Read the phone log Call handling Automatically send text messages Get text messages Text message log. The Media permission is replaced with: Camera Microphone Music library Picture and video library Audio and video playback. New permissions are grouped by purpose and functional cohesion. Configurations exported by version 8.3.14 or earlier versions cannot be built using mobile version 8.3.15 or higher. The reverse is also true.	Mobile application permissions had a different composition.	Mobile application permissions include changed requirements of application store owners.
Mobile platform. Mobile client. Mobile application builder.	In Designer, you can now edit request bodies of permissions that are required by the mobile application. Request bodies of permissions that have an applied meaning for the user are editable. Mobile application builder allows you to build mobile applications that contain both configurations with the specified permission request bodies and configurations without them (exported in previous 1C:Enterprise platform versions).	Permission request bodies were not editable in Designer.	You can now specify permission request bodies that meet the mobile application requirements as accurately as possible.
Mobile platform. Mobile client. Global search.	Upgrade: global search is now available in 1C:Enterprise mobile version.	This feature was not supported in the mobile version.	Upgrade: 1C:Enterprise mobile version now has the features that were implemented earlier in 1C:Enterprise version for a personal computer.
Development tools.	Implemented the following changes in Syntax Assistant: Deprecated objects (properties, functions, procedures, etc.) are not deleted from Syntax Assistant but saved to it. Accessibility of deprecated objects (objects that are not yet available or not recommended for use in the current compatibility mode) in Syntax Assistant tree can be managed using the check box in Syntax Assistant settings: Display deprecated objects. Upgrade: an addition version, a depreciation version, and a version where significant information about an object was last edited can be displayed. For deprecated objects, objects recommended for usage instead of the deprecated object can be displayed now. Syntax Assistant item font is the same as the default web browser font. For Syntax Assistant content window, the width limit is 1,000 pixels. Decreased indents before and after bulleted lists. Regardless of the state of the Display deprecated objects setting check box, search using Ctrl+F1 always results in information about a Syntax Assistant object being displayed. Addition version information is filled in for all objects of Syntax Assistant. Deletion version information is filled in for all objects of Syntax Assistant. Objects recommended for replacement are filled in only if the object was declared deprecated in version 8.3.14 and above. Specified changes in Syntax Assistant are valid starting from version 8.3.15 and above.	Syntax Assistant did not have any information about object versions (of addition, depreciation, or change) and objects that are recommended for usage instead of the deprecated ones. Deprecated objects were deleted from Syntax Assistant. It was impossible to access such objects.	Syntax Assistant became more informative and useful for developers.
Mobile platform. Mobile client. Mobile device-specific features.	You can now use additional authentication to access mobile application features. Authentication is done by the used mobile operating system and includes authentication using biometrics (a fingerprint, face recognition, or iris recognition) or a password (pattern lock and so on). New global context property: AdditionalUserValidation. Upgrade: safe storage of confidential information on a user mobile device. Information is protected by the mobile operating system. You can now manage the need for additional authentication to access confidential information. New global context property: SecureStore.	These features were not provided.	Added functionality of 1C:Enterprise mobile version for additional user authentication and confidential information storage.
Client application installation.	Windows client application installer now supports Vietnamese language.	The Windows client application installer did not support Vietnamese.	Eliminated unexpected system behavior.
Data history.	Implemented the following features for standard Data history processor: Starting object queue data processor after writing versions. Removing objects from the object data processor queue after writing versions. These features are available from the data processor form using the More - Data history management command.	These features were not provided.	The standard data processor supports new features of the data history component previously implemented in the platform.
Collaboration system. Client application form.	When calling the BeginGetConversation() form method, a context conversation is created if the resulting context conversation is missing by the time the method is called.	When calling the BeginGetConversation() form method, the context conversation was not created.	When calling the BeginGetConversation() form method, a context conversation is automatically created if it was not created before..
Server clusters.	Optimized the final step of load balancing algorithm (in the selection mode with a performance priority) when the workflows selected in the previous steps differ in available performance.	The documents did not contain information on configuring web servers for the correct operation of the background jobs feature in the file infobase.	Optimized load balancing algorithm in a server cluster.
Web client, web service, and HTTP service publishing tools.	The documents contain information on configuring web servers for the correct background jobs feature operation in the file infobase.	The documents did not contain information on configuring web servers for the correct operation of the background jobs feature in the file infobase.	Updated platform documents.
File operations.	When using the BeginPutFile()/BeginPuttingFiles() methods, the downloaded file(s) are split into parts and the transfer to the server is performed in parts. As a result, the user interface remains operational. Also implemented the option to start putting new files, even if the previously started putting of files is not yet complete.	When using the BeginPutFile()/BeginPuttingFiles() methods, the uploaded file/files were transferred fully. The client application did not respond to user actions during the transfer. It was impossible to start putting a new file until the previously started putting of one or more files was completed.	Eliminated unexpected system behavior.
Calculation registers. Applied objects.	Implemented the feature to include sequences and recalculations in the common attributes. This change is not implemented in version 8.3.14 compatibility mode.	This feature was not provided.	Expanded the structure of configuration objects, which may be part of common attributes.

Table of contents

Transition from the previous version to the version 8.3.15

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.15.
Some features that are added in version 8.3.15 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.
To make accounting register performance increase noticeable, disable the compatibility mode. Accounting registers will be restructured. If infobase size exceeds 10 GB, it is recommended that you use optimized tool of database configuration update for restructuring.

Functionality	After	Before	Result of changes
Queries.	New feature: the query language now has optimized calculations of expressions being virtual table parameters. This optimization is similar to optimization of standard query language expressions. This change is not implemented in version 8.3.14 compatibility mode.	The query language did not have optimized calculations of expressions being virtual table parameters.	Eliminated unexpected system behavior.
Linux.	Optimized use of RAM on Linux.	RAM was used less effectively on Linux.	Decreased RAM fragmentation and, as a result, decreased the amount of used RAM on Linux. Slightly improved application performance.
Queries. Server clusters.	Optimized execution of a query containing constant values in the selection list. Constant values from the query body are implemented by query parameters. This reduces the amount of plan recompilation in DBMS and, as a result, improves performance of the same queries if only their constant value is different.	This feature was not provided. Constant values were not used by parameters and were used directly in the query body.	Execution time of queries containing constant values is reduced in some cases. In particular, recalculation of register totals can take less time in client/server mode.
Managed locks.	Improved performance of the managed lock manager upon transaction completion if there are a lot of transactions that locked the key range of one space.	The managed lock manager spent more time on transaction completion if there were a lot of transactions that locked the key range of one space.	Parallel operation is improved in case of similar load generated by numerous sessions.
Configuration comparison and merging.	Optimized comparison/merge of configurations.	Comparison and merge of configurations took more time.	Comparison and merge of configurations is now faster.
Queries.	If the query text contains a condition with two constant expressions and each expression is not a string, the condition will be replaced with an expression result before passing the query to DBMS. This change is not implemented in version 8.3.14 compatibility mode.	Conditions which consisted of constant expressions were not simplified.	In some cases, query performance is improved.
Binary data.	Buffers used with objects of the FileStream type are reset only if the FileStream.ResetBuffers() method is executed explicitly.	Buffers used with objects of the FileStream type were reset: Upon executing the FileStream.ResetBuffers() method explicitly. Upon calling the FileStream.Close() method. Upon deleting the FileStream object.	Decreased load on a disk drive upon intensive operations with the FileStream type objects.
Data composition system.	Improved performance of the Value() function of the data composition system expression language.	The Value() function of the data composition system expression language worked more slowly.	Improved performance of the Value() function of the data composition system expression language.
DBMS operations. Queries.	Upon query execution, faster creation of a temporary table from a value table passed as a query parameter is available now.	Upon query execution, creation of a temporary table from a value table passed as a query parameter took longer time.	Upgrade: faster creation of a temporary table based on a value table using the query language.
Client application installation. System requirements.	Removed Microsoft VC++ Runtime Redistributable Package from thin client distribution package (for Windows).	Microsoft VC++ Runtime Redistributable Package was inside thin client distribution package (for Windows).	Reduced thin client distribution package for Windows.
System requirements.	Removed Microsoft Windows Installer 3.0 Package from platform distribution package (for Windows).	Microsoft Windows Installer 3.0 Package was inside platform distribution package (for Windows).	Reduced platform distribution package for Windows.
Data composition system.	Composer of data composition system template considers to be used only those fields that are used in the conditional appearance item of data composition only when this conditional appearance item is applied at least to one of the displayed fields (also upon applying conditional appearance to all fields). If conditional appearance item is not applied to any field, used fields are considered to be unused and are not added to the resulting query of the data composition template. Fields, which are not used in conditional appearance, are not added to the data acquisition query. This change is not implemented in version 8.3.14 compatibility mode.	Composer of data composition system template considered to be used all fields in conditional appearance item even if this conditional appearance item was not applied to any field. All fields, which were formally used in conditional appearance, were added to the data acquisition query.	Improved generation of the query of data composition system data acquisition.
Queries.	If a query with merges contains a false condition, the part of the merge with the false condition is not passed to DBMS. False conditions are detected only for Number or enumeration data type. Upon merge optimization, the platform can, if necessary, add a requirement for obtaining different records to the resulting query. This change is not implemented in version 8.3.14 compatibility mode.	This feature was not provided.	In some cases, query time will be decreased.
Server clusters.	Improved client connection transfer to a new working process upon automatic restart of the working process.	Client connection transfer to a new working process upon automatic restart of the working process took more time.	Transfer of existing sessions to a new working process now takes less time. Decreased (or totally eliminated) client application delay upon transfer. Significantly improved client application operation in interactive mode in this case.
Accounting registers.	Improved performance of virtual tables of the accounting register, updated totals upon writing register records, and recalculated accounting register totals. Increased stored data volume and slightly increased record set storage time. To make accounting register performance increase noticeable, disable the compatibility mode. Accounting registers will be restructured. If infobase size exceeds 10 GB, it is recommended that you use optimized tool of database configuration update for restructuring. This change is not implemented in version 8.3.14 compatibility mode.	Operations with virtual tables of accounting register, update of totals upon writing register records, and recalculation of accounting register totals took more time.	Data acquisition from accounting registers is faster now.
Accounting registers. Queries.	Improved query to accounting register if the query contains a condition of including the recorder in a list generated under a subquery: Recorder IN (subquery). This change is not implemented in version 8.3.14 compatibility mode.	Query to accounting register if the query contains a condition of including the recorder in a list generated under a subquery: Recorder IN (subquery), poor performance.	Improved data acquisition from the accounting register in some cases.
Queries.	If you execute a query in the infobase file mode with data from two tables and these tables are connected with an internal connection and there are indexes of link fields in both tables, then the first iteration is performed for the table with less records.	Number of records in tables was not analyzed upon executing a query in the infobase file mode with data from two tables and these tables were connected with an internal connection and there were indexes of link fields in both tables.	In some cases, improved query performance in the infobase file mode.
Data composition system.	Improved generation of data composition system template if a data composition schema query contains a lot of unions (400 or more unions).	Generation of data composition system template took a significant amount of time if a data composition schema query contained a lot of unions (400 or more unions).	Improved performance of the data composition system if there are a lot of unions in a data composition schema query.
Server clusters. DBMS operations.	Upgrade for PostgreSQL DBMS: better posting of large documents in the accounting register and improved RecordsWithExtDimensions virtual table.	Posting of large documents in the accounting register and operations with the RecordsWithExtDimensions virtual table took more time if PostgreSQL DBMS was used.	Optimized use of the accounting register if PostgreSQL DBMS is used.