Version 8.3.13

Version 8.3.13

Version 8.3.13 includes known bug fixes and functionality modifications.

Finished the beta testing of the Designer agent mode.

Transition from the previous version to the version 8.3.13

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.13.
Some features that are added in version 8.3.13 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
It is recommended that you uninstall your HASP Device Driver and then install HASP Device Driver 7.63, which is a part of 1C:Enterprise distribution package.

Changes performed after version publication

Functionality	After	Before	Result of changes
Interface.	In Taxi interface the command check in the menu now displays the same way in different displaying options and different client application types.	The command check in the menu could be different depending on displaying options and client application types.	The command check in the menu now displays the same way.
Data composition system.	If a filter is added to a query of composition schema data set that includes union, this filter is added to every part of the union. If a particular union part does not contain a field that is used in the filter, this field is replaced by NULL. This change is not implemented in version 8.3.12 compatibility mode.	If a filter was added to a query of composition schema data set that includes union, this filter was added to parts of the union that contained the field that was used in the filter.	Unified filter operations in data composition system between the union data set and query data set, where the query contained a union.
Internet-enabled functionality.	The parameters of the following FTPConnection object methods were renamed in the Syntax Assistant: Get() and Put(). This change is available in the Syntax Assistant only.	The parameters of the following FTPConnection object methods were different in the Syntax Assistant: Get() and Put().	The names of the FTP methods parameters became more clear.
Mobile device-specific features. Mobile platform. Mobile client.	The DeliverableNotification.Title value is now displayed when a notification is shown on iOS version 8.2 and later mobile device.	The DeliverableNotification.Title value was available on Android only.	Improved notifications on iOS.
Collaboration system. Mobile platform. Mobile client.	The collaboration system notifications now contain the sender name. The noncontext conversation title is displayed in the notification title.	The collaboration system notifications did not contain the sender name. The noncontext conversation title was displayed both in the notification title and text.	Improved collaboration system notifications.
Internet-enabled functionality.	macOS certificate store is now supported. New objects: MacOSCertificationAuthorityCertificates, MacOSCertificateSelectMode, and MacOSClientCertificate. macOS certificate store support is added to object OSCertificationAuthorityCertificates. New -macos parameter for /HttpsCA and /HttpsCert command-line options of the client application. New technological log event: <MACCERT>.	macOS certificate store was not supported. Secured connection was only available if certificates were stored in files.	You can use the system certificate store to establish secured connection on macOS.
Collaboration system.	The client application agent supports multiple versions of the collaboration system server's exchange protocol. New 1ceclac application is provided. The client application agent's directory structure is changed.	The client application agent supports a single version of the collaboration system server's exchange protocol.	The client application agent supports the previous versions of the collaboration system server's exchange protocol.
Dynamic lists.	The following restrictions apply to search in dynamic lists: The search string cannot exceed 1000 characters. The search string cannot contain more that 20 words. If the search string does not comply with the listed requirements, an exception is generated. For details on splitting the search string into words, see 1C:Enterprise documentation.	There were no restrictions to search in dynamic lists.	Improved application server reliability when searching in dynamic lists.
Dynamic lists. Data composition system.	When opening report forms or dynamic list forms, if user settings are not available in the storage, the system performs the following actions: Items with unavailable or missing fields are deleted from the main dynamic list settings and report option settings that are marked as user settings. Items with unavailable or missing fields are deleted from the default user settings. BeforeLoadUserSettingsAtServer and OnLoadUserSettingsAtServer event handlers are executed. New UseDefaultSettings parameter for BeforeLoadUserSettingsAtServer and OnLoadUserSettingsAtServer event handlers. The Set default settings command of report and dynamic list forms performs the following actions: Items with unavailable or missing fields are deleted from the main dynamic list settings and report option settings that are marked as user settings. Items with unavailable or missing fields are deleted from the default user settings. If the user settings of a dynamic list or a report option were not changed on the client (interactively or from 1C:Enterprise language) since the form was opened, the current user settings are deleted from the system storage when the form is closed Method DataCompositionSettingsComposer.Refresh() with parameter DataCompositionSettingsRefreshMethod.Full performs the following actions: sets the Use flag to False for main settings items that lost their linking to available fields, and deletes items of main settings and user settings that are marked as user settings but contain fields absent from the collection of available fields or not available for the current functional options and rights. This change is not implemented in version 8.3.12 compatibility mode.	When opening report forms or dynamic list forms, if user settings were not available in the storage, the system performed the following actions: Items with unavailable or missing fields were not deleted from the main dynamic list settings and report option settings that were marked as user settings. Items with unavailable or missing fields were not deleted from the default user settings. BeforeLoadUserSettingsAtServer and OnLoadUserSettingsAtServer event handlers were not executed. The Set default settings command of report and dynamic list forms had the following behavior: Items with unavailable or missing fields were not deleted from the main dynamic list settings and report option settings that were marked as user settings. Items with unavailable or missing fields were not deleted from the default user settings. If the user settings of a dynamic list or a report option were not changed on the client (interactively or from 1C:Enterprise language) since the form was opened, the default settings generated based on the main dynamic list settings or on the current report option settings were saved as user settings when the form was closed. Method DataCompositionSettingsComposer.Refresh() with parameter DataCompositionSettingsRefreshMethod.Full set the Use flag to False for main settings items that lost their linking to available fields.	Unavailable fields cannot be added to the default user settings of reports or dynamic lists.
Data analysis.	If a data set contains an even number of elements, its median is calculated as the arithmetic mean of the two middle elements of the ordered set. In particular, this rule applies to data sets that contain two elements. This change is not implemented in version 8.3.12 compatibility mode.	If a data set contained an even number of elements, its median was calculated as follows: For data sets with more than 2 elements, the arithmetic mean of the two middle elements of the ordered set. For data sets with 2 elements, the value of the second element.	Eliminated unexpected system behavior.
Internet-enabled functionality.	For SMTP operations, added support of NOTIFY parameter of RCPT command and RET parameter of MAIL command. This provides support for mail delivery receipts described in RFC 1891. InternetMailMessage.DeliveryReceiptAddresses property is deprecated. This property is only available in Version 8.3.12 compatibility mode. Note that some SMTP server implementations or some of their settings can prevent receiving mail delivery receipts. It is recommended that you do not use DeliveryReceiptAddresses property of InternetMailMessage object. Use the following properties instead: ReadReceiptAddresses and RequestReadReceipt to receive read receipts. RequestDeliveryReceipt to receive delivery receipts.	Instead of delivery receipts, read receipts were generated.	Eliminated unexpected system behavior. Both delivery and read receipts are now available.
Internet-enabled functionality.	If a mailbox does not contain any messages matching the IDs specified in the parameter of InternetMail.GetMessagesFlags() method, the method returns a blank map. This change is not implemented in version 8.3.12 compatibility mode.	If a mailbox did not contain any messages matching the IDs specified in the parameter of InternetMail.GetMessagesFlags() method, the method generated an exception.	Eliminated unexpected system behavior.
Spreadsheet documents.	An attempt to save a spreadsheet document with pictures in 1C:Enterprise 7.7 format on a server or in an external connection generates an exception. Only spreadsheet documents without pictures can be saved in this format.	An attempt to save a spreadsheet document with pictures in 1C:Enterprise 7.7 format on a server or in an external connection resulted in generation of a corrupted document that could not be opened.	Eliminated unexpected system behavior.
Managed forms.	If the Width property of a form field is not 0 and horizontal stretching is not applied, this property defines the field width without the input field buttons (Select, Clear, and others). The resulting field width is equal to the sum of the Width value and all button widths. This change is not implemented in version 8.3.12 compatibility mode.	If the Width property of a form field was not 0 and horizontal stretching was not applied, this property defined the field width as follows: If input field buttons were available, it defined the field width without the buttons. If input field buttons were not available, the actual width was slightly greater than the specified one. Thus, adding or removing input field buttons could change the field width.	Eliminated unexpected system behavior.
Collaboration system.	If several applications share a collaboration server, the message counter of the client application agent is incremented once per message.	If several applications shared a collaboration server, the message counter of the client application agent was incremented several times (once per application).	Eliminated unexpected system behavior.
Add-ins. macOS.	Client applications running on macOS now support add-ins based on Native API. The add-in technology documentation and examples are updated accordingly (read more).	Client applications running on macOS did not support add-ins based on Native API.	Client applications running on macOS now support add-ins.
Add-ins. Mobile platform. Mobile client.	For add-ins intended to run on iOS, you can specify a set of properties to be included in the application properties (file info.plist). The properties required by the add-in are added by the Mobile application builder. The add-in technology documentation is updated. (read more)	This feature was not provided. Add-ins could not add properties to the info.plist file.	Development of add-ins intended to run on iOS is more convenient.
Collaboration system. Client application.	When a collaboration system notification is deleted from the notification center, the conversation is marked as read. Deleting a notification here means either deleting a single notification or clearing the notification list.	When a collaboration system notification was deleted from the notification center, the conversation was not marked as read. Deleting a notification here means either deleting a single notification or clearing the notification list.	The collaboration system behavior is more logical and predictable.
Data composition system. XML and XDTO support.	When XDTO deserialization is applied to data composition parameters, only parameters that are included in the list of the available parameters of the current platform version are deserialized. No deserialization attempts are performed for parameters that are not included in the list of available ones. This ensures successful restoration of parameters.	When XDTO deserialization was applied to data composition parameters, the platform attempted to deserialize all of the serialized parameters. Attempts to restore data composition settings using an earlier platform version where the list included parameters unavailable in the current version generate errors.	You can use an earlier platform version to restore data composition schemas and data composition settings saved in a later platform version. At that, data composition parameters available only in the later version are ignored.
Managed forms. Client application.	If a form table does not have a current row (for example, it is blank) and a column group is hidden from the table header, its parent column group is also hidden from the header. If a form table has a current row and a column group is shown in the header, its nested column group is shown in the header only if the current row contains cells that belong to the nested group. This change is not implemented in version 8.3.12 compatibility mode.	If a form table did not have a current row (for example, it was blank) and a column group was hidden from the table header, its parent column group was shown in the header as a blank column. If a form table had a current row and a column group was shown in the header, its nested column groups were always shown in the header.	Eliminated unexpected system behavior.
Data composition system.	Predefined resource templates that describe intersections of table row groupings (template type: Title or Footer) with table column groupings (template type: Grand Total Title or Grand Total Footer) are displayed in a report even if the resource fields are not displayed in the table columns. This change is not implemented in version 8.3.12 compatibility mode.	In data composition system tables, if resource fields were not displayed in table columns, predefined resource templates were not displayed for row totals.	Eliminated unexpected system behavior.
Data history.	In a data structure that is generated by the DataHistoryManager.GetVersionDiff() method and describes moving a table row: The RowNumberInBeforeChangeVersion property contains the number that the row had before applying any of the version changes. The RowNumberInAfterChangeVersion contains the number that the row has after applying all of the version changes. This change is also applied to the standard version difference report.	In a data structure that was generated by the DataHistoryManager.GetVersionDiff() method and described moving a table row: The RowNumberInBeforeChangeVersion property contained the number that the row had after applying all of the previous changes but before applying the current change. The RowNumberInAfterChangeVersion contained the number that the row had after applying the current change.	Eliminated unexpected system behavior. The row numbering is now more intuitive.
Managed forms.	If a form input field contains modified data and it is not the current form item, an attempt to set its Visible, Enabled, or EditText property to False or set its ReadOnly property to True results in the following: TextEditEnd event handler is called. After the TextEditEnd event handler is completed, if the StandardProcessing parameter is set to True: If a valid value is generated from the field text, the OnChange event handler is called. If a valid value cannot be generated from the field text, the input field value is set to the value of the attribute linked to the input field. After the TextEditEnd event handler is completed, if the StandardProcessing parameter is set to False and a valid value cannot be generated from the field text, the input field value is set to the value of the attribute linked to the input field. If a form input field contains unmodified data and it is not the current form item, an attempt to set its Visible, Enabled, or EditText property to False or set its ReadOnly property value to True results in closing the drop-down list (if the list was open). This change is not implemented in version 8.3.12 compatibility mode.	Setting the Visible property of an input field to False results in the following: If the field is linked to a text value, its value is generated from the field text and then the OnChange event handler is called. If the field is linked to a reference value and a user has not finished filling it, the resulting field state might be inconsistent.	Eliminated unexpected system behavior.
Mobile client. Internet-enabled functionality.	Mobile clients can connect to infobases over HTTPS. The infobase access parameters of the mobile client now include the client certificate source and the server certificate verification options. The client certificate source can be an application certificate store or a file (for iOS and Android). The source of root certificates for server certificate verification can be a system certificate store, application certificate store, or file (for iOS and Android).	This feature was not provided.	Added new mobile client features.
Mobile client. Managed forms.	In the mobile client, customization of form command bars is implemented. A new form property: MobileDeviceFormCommandBarContent. In the mobile client, the property content (unless it is blank) is displayed in the form command bar, replacing the default command bar. Including a form command bar into the MobileDeviceFormCommandBarContent property content is not supported. If a form group title is defined but not displayed, the title is considered when generating the title of an automatically collapsed group on the mobile client.	In the mobile client, form command bar customization was not supported. If a form group title was defined but not displayed, the title was not considered when generating the title of an automatically collapsed group on the mobile client.	Form customization on the mobile client is upgraded.

Mobile version of 1C:Enterprise

Functionality	After	Before	Result of changes
Mobile device-specific features.	Push notifications on Android use Firebase Cloud Messaging service. It is recommended to transfer push notifications to this platform in current applications. Implemented the DeliverableNotificationSubscriberType.FCM enumeration value. The Google Cloud Messaging service is supported for compatibility purposes and is not recommended for use. The DeliverableNotificationSubscriberType.GCM value is obsolete and supported for compatibility purposes. The GoogleCloudApplicationNumber parameter of the ReceiveNotificationSubscriberID() method is optional on Android.	Push notifications on Android used Google Cloud Messaging service.	The legacy push notifications delivery service is no longer used. Transfered to the latest version of the service.
Mobile device-specific features. Mobile platform. Mobile client.	Implemented the capability of managing the camera backlight interactively (on Android and Windows Phone) and from the 1C:Enterprise script (on all mobile operating systems). Implemented the DeviceTools global context property. Implemented the CameraBacklightType parameter of the MultimediaTools.MakePhoto() method. You can now use a camera flash as a flashlight. Implemented the DeviceTools global context property. Implemented the FlashlightSupported() and TurnFlashlightOn() methods of the device tools manager.	Managing the camera backlight from the 1C:Enterprise script was not available. Interactive managing of the camera backlight was available only on iOS. There was no option to use a camera flash as a flashlight.	Extended the mobile device camera operations.
Spreadsheet documents. Mobile platform.	A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC.	A PDF type document generated on the mobile platform was less similar to the same PDF type document generated on PC.	A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC.
Mobile device-specific features. Mobile client. Mobile platform.	Implemented acquiring purchase receipts feature in 1C:Enterprise mobile version. It is now available to validate the purchase receipt on a mobile device. Implemented the following InAppPurchasesManager object methods: PurchaseHistorySupported() GetPurchaseHistory() GetInAppPurchaseReceipts() GetInAppPurchaseReceiptsData(). The InAppPurchasesManager object is now available in the mobile client and in the mobile platform client. Implemented the InAppPurchasesValidationManager.ValidateInAppPurchaseReceiptAtMobileDevice() method on the mobile client and on the mobile platform client. The global context InAppPurchasesValidation property is now available on the mobile client and on the mobile platform client. Acquiring the list of internal purchases is now available in the mobile application builder purchase emulator.	Acquiring purchase receipts feature was not available. The InAppPurchasesValidationManager object and the InAppPurchasesValidation global context property were available only on the server of the PC platform.	Improved the internal purchases feature, provided by the appropriate application store.
Mobile platform.	Implemented the following form control properties: DisplayImportance for all controls CurrentRowUse and TableBehaviorOnHorizontalCompression for a form table. Implemented input hints for multiline input fields.	These features were available in the mobile client only.	Managed forms are now displayed the same way in different 1C:Enterprise mobile versions.

Renamed objects

Object	The old name	The new name
The getting/setting HTML document methods of formatted document extension of the TestedFormField object. The former names are supported for compatibility purposes.	GetHTML() SetHTML()	GetDocumentHTML() SetDocumentHTML()

Changes that require modification of configuration and administrative settings

Functionality	After	Before	Result of changes
Data composition system. Charts.	The processor of data composition result output sets the automatic column width calculation for all cells in the spreadsheet document area that contains a chart. This change is not implemented in version 8.3.12 compatibility mode.	The processor of data composition result output did not set the automatic column width calculation for all cells in the spreadsheet document area that contained a chart.	Eliminated unexpected system behavior.
Data composition system.	If the predefined grouping templates are used during the table columns output, then the grand totals template height is automatically calculated to fit all resource headers. The template generator automatically increases the predefined grouping template height If it is less than the grand totals template height. This change is not implemented in version 8.3.12 compatibility mode.	If the predefined grouping templates were used in the table columns output and the grand totals template height was greater than the predefined grouping templates height, some resource headers might not be displayed in the grand totals template.	Eliminated unexpected system behavior.
Collaboration system.	Implemented the CollaborationSystemManager.IsEnabled() method. It returns the following flags: The infobase is registered in the collaboration service. The infobase registration is active. There are collaboration system users in the infobase. The CollaborationSystemManager.InfoBaseRegistered() method returns whether the infobase is registered in the collaboration service and the registration is active. This change is not implemented in version 8.3.12 compatibility mode.	The CollaborationSystemManager.InfoBaseRegistered() method returned the following flags: The infobase was registered in the collaboration service. The infobase registration was active. There were collaboration system users in the infobase.	You can now get the information about the infobase registration and the collaboration system availability separately.
Spreadsheet documents.	The spreadsheet document width and height (PageHeight and PageWidth properties) are limited to 5000 mm. This change is not implemented in version 8.3.12 compatibility mode.	The spreadsheet document width and height (PageHeight and PageWidth properties) were unlimited.	Eliminated problems of the spreadsheet document with large pages export to other formats.
Data composition system.	If an unavailable property of a data composition system object is accessed, an exception is thrown. The UserSettingPresentation property of DataCompositionFilter, DataCompositionSelectedFields, DataCompositionConditionalAppearance objects. The UserSettingPresentation, Presentation, LeftValue, Application, Parent properties of the DataCompositionFilterItem object. The UserSettingPresentation, Presentation, Application, Parent, GroupType, Items properties of the DataCompositionFilterItemGroup object. The UserSettingPresentation, Presentation, Fields, Filter, UseInGroup, UseInHeader, UseInFieldsHeader, UseInHierarchicalGroup, UseInOverall, UseInFilter, UseInParameters properties of the DataCompositionConditionalAppearanceItem object. The UserSettingPresentation, NestedParameterValues, Parent, Parameter (only when setting the property value) properties of the DataCompositionSettingsParameterValue object. The UserSettingPresentation, ID, Name, Choice, Filter, OutputParameters, GroupFields, Order, Parent, State, Structure, ConditionalAppearance properties of the DataCompositionGroup, DataCompositionTableGroup, DataCompositionChartGroup objects. The UserSettingPresentation, Choice, ID, Name, Columns, OutputParameters, Parent, Strings, ConditionalAppearance properties of the DataCompositionTable object. The UserSettingPresentation, Choice, ID, Name, OutputParameters, Parent, Sreies, Points, ConditionalAppearance properties of the DataCompositionChart object. The UserSettingPresentation, ID, ObjectID, Name, Settings, Parent properties of the DataCompositionNestedObjectSettings object. The UserSettingPresentation and ViewMode properties of the DataCompositionSettingStructureItemCollection object. This change is available only if the parent of the DataCompositionSettingStructureItemCollection object is a DataCompositionSettingStructure type object that is included in the DataCompositionUserSettingsItemCollection collection. This change is not implemented in version 8.3.12 compatibility mode.	Accessing the listed above properties of the user settings objects was meaningless and did not throw an exception.	Eliminated the incorrect accessing to data composition system object properties.
Background and scheduled jobs.	The maximum size of serialized background job parameters is 1 GB. Otherwise an exception is thrown. If the version 8.3.12 compatibility mode is set, an exception is thrown if the size of serialized background job parameters is greater than 2 GB.	If the size of serialized background job parameters was greater than 2 GB the session was abnormally terminated.	Improved background jobs stability. Decreased the background job impact on the system performance if very large parameters were sent.
Dynamic lists.	The OnChange event occurs once per deleting dynamic list rows in the thin client. This change is not implemented in version 8.3.12 compatibility mode.	The OnChange event might occur multiple times when dynamic list rows were deleted in the thin client. The number of event calls depended on the deleted rows number: less or equal to 100 rows. The number of event calls was equal to the rows number. more than 100 rows. The event was called once.	Eliminated unexpected system behavior.
Common objects.	The Font object constructor returns the Common style text font if the FontName constructor parameter is not specified. This change is not implemented in version 8.3.12 compatibility mode.	The Font object constructor returned Dialog and menu font if the FontName constructor parameter was not specified.	Eliminated unexpected system behavior.
System requirements. Linux.	The ImageMagick library from the 1C:Enterprise platform distribution package is used.	The ImageMagick library from the operating system was used.	Reduced the number of issues that might arise due to the incorrect ImageMagic library version in the operating system.
Managed forms.	The AddRow(), ChangeRow(), CopyRow() and EndEditRow() methods of the ManagedFormTable object do not perform any actions if their related interactive commands are not available. This change is not implemented in version 8.3.12 compatibility mode.	The behavior of the AddRow(), ChangeRow(), CopyRow() and EndEditRow() methods of the ManagedFormTable object depended on the client application type. In the thin client they performed the related actions. In the web client no actions were performed.	Eliminated unexpected system behavior.
Development tools.	The English version of ID, attribute name and metadata object name is now saved in the configuration merge settings file. The following actions are performed when reading the configuration merge settings file: attempt to read IDs in English. If failed, attemt to read IDs in Russian.	The version of ID, attribute name and metadata object name that were saved in the configuration merge settings file, depended on the configuration script variant.	The result of the configuration merge settings loading does not depend on the configuration script variant.
Web client. File operations.	Improved web client file operations. Implemented the new file selection dialog box. It supports multiple file choice and dragging. The file system extension is not required for this dialog box. Implemented the limited editing of the file selection dialog box BeginPutFile() and BeginPuttingFiles() methods. The BeginPutFile() method does not require the file system extension installed. Added the option to manage specific parameters of files before transfering them to server. Implemented the BeforeBeginPuttingFilesNotificationDescriprion parameter of the BeginPutFile() and BeginPuttingFiles() methods. Implemented the FullName and FileID properties of the TransferredFileDescription object. The Name property of the TransferredFileDescription contains only the transferred file name. The BeginPutFile() method allows other calls and methods in the thin client. This change is not implemented in version 8.3.12 compatibility mode. You can now drag files on the following form items: managed form field extension for a picture, managed form decoration extension for a picture, and managed form table. Implemented the FileDragMode property of the listed above managed form items. Implemented the FileRef object. The PutFile(), PutFiles(), and GetFiles() methods are deprecated. It is recommended to rework file operations in applications that use the web client.	The file operations in the web client were limited if the file system extension was not installed. In the thin client, while the BeginPutFile() method was being executed, calls of other methods were not allowed. The TransferredFileDescription.Name property contained the full file name.	Expanded the file operations in the web client that do not require the file system extension installed. The web client supports and handles the file dragging.
Charts.	If the chart data contains non-numeric values (NULL or Undefined), the chart behavior can be specified. Implemented the NonnumericValueUse and PointsConnectionAcrossSkippedValues properties of the Chart object. Implemented the ChartType.NonnumericValueUse and ChartType.PointsConnectionAcrossSkippedValues properties of the following objects: DataCompositionOutputParameterValues, DataCompositionChartOutputParameterValues, DataCompositionAreaTemplateChartAppearance. If displaying of a series marker is disabled (ChartMarkerType.None is set) and a series value in some point is separated (values in the next and previous points are omitted), then this value is displayed as a circle. The width of the circle line equals to the series line width. Chart lines connections are now rounded. This change is not implemented in version 8.3.12 compatibility mode.	The chart behavior could not be specified if the chart data contained non-numeric values. If displaying of a series marker was disabled (ChartMarkerType.None was set) and a series value in some point was separated (values in the next and previous points were omitted), then this value was not displayed on a chart. The chart lines connection was not rounded.	Expanded operations with charts.
Automated testing.	The TestedFormTable.Expand() method can now expand subordinate nodes on the next level of the selected node only. Implemented the WithSubordinates parameter of the TestedFormTable.Expand() method. This change is not implemented in version 8.3.12 compatibility mode. It is recommended to review and rework all code fragments with the TestedFormTable.Expand() method.	The TestedFormTable.Expand() method expanded the selected node and all subordinate nodes.	The automated testing features now correspond the 1C:Enterprise platform capabilities.
Data composition system. Dynamic lists. External data sources.	If a dynamic list field in a report may be NULL, the following ordering rule is applied to that field: NULL values come first. If a dynamic list field is based on an external data source table field, and the external data source contains the CASE ... WHEN selection that might return NULL, the following ordering rule is applied to that field: NULL values come first. This change is not implemented in version 8.3.12 compatibility mode.	If a dynamic list was ordered by a field that might be NULL , rows with NULL and with the default field type value were placed together. If a dynamic list was ordered by a field that was based on the external data source table of any type, the final ordering depended on the DBMS type.	Dynamic list ordering by the field that might be NULL rule is now the same as the other objects ordering rule.
Managed forms.	When the AutoMarkIncomplete property of a managed form table is set to True, the MarkIncomplete property of that table obtains the correct value after the script execution. This change is not implemented in version 8.3.12 compatibility mode.	The MarkIncomplete property of a managed form table was refreshed only when the table was refreshed or the current table cell was changed.	Eliminated unexpected system behavior.
Queries.	The IS NULL function returns FALSE if it is applied to the combination of virtual fields. The IS NULL function returns TRUE if it is applied to the combination of virtual fields and the expression without virtual fields that returns NULL. The IS NULL function returns FALSE if it is applied to the combination of virtual fields and the expression without virtual fields that does not return NULL. This change is not implemented in version 8.3.12 compatibility mode. It is recommended to review all IS NULL functions in existing applications.	The IS NULL function returned FALSE if it was applied to the combination of virtual fields or to the combination of virtual fields and the expression without virtual fields.	Eliminated unexpected system behavior.
File operations. Server clusters.	If a security profile that blocks access to the file system is set in the infobase, the TempFilesDir() and GetTempFileName() global context methods return paths with separators, provided by the current operating system.	If a security profile that blocked access to the file system was set in the infobase, the TempFilesDir() and GetTempFileName() global context methods returned paths with separators, provided by the Linux operating system.	Eliminated unexpected system behavior.
File operations.	If the parameter of the following File object methods is set to date before the January 1, 1601 in the Windows operating system, these methods throw the File access denied exception: SetModificationTime() SetModificationUniversalTime() BeginSettingModificationTime() BeginSettingModificationUniversalTime(). All errors of File object methods throw the same exception.	If the parameter of the following File object methods was set to date before the January 1, 1601 in the Windows operating system, these methods returned the random date: SetModificationTime() SetModificationUniversalTime() BeginSettingModificationTime() BeginSettingModificationUniversalTime().	Eliminated unexpected system behavior.
Data composition system.	If the CASE operation is used in the data composition system calculated expression, and the resulting field type is unknown (it is a values table field or the field type is not specified) and the ELSE section contains the Undefined value, the result field type in the result values collection will be set to Custom (the type description will be blank). This change is not implemented in version 8.3.12 compatibility mode.	If the CASE operation was used in the data composition system calculated expression, and the resulting field type was unknown (it was a values table field or the field type was not specified) and the ELSE section contained the Undefined value, the result field type in the result values collection would be NULL.	Eliminated unexpected system behavior.
Managed forms.	Only methods with the Export keyword are available in expressions containing ThisObject. This change affects from module as well as other modules, where ThisObject is passed. This change is not implemented in version 8.3.12 compatibility mode.	All methods were available in expressions containing ThisObject.	Eliminated unexpected system behavior.
Data composition system.	If a filter with the filled/not filled comparison type is used in the data composition system settings and this filter is applied to the calculated field, which type is custom, Characteristics type, or any reference type, then the filter will consider types, included in the Characteristic, custom type or any reference type. This change is not implemented in version 8.3.12 compatibility mode.	If a filter with the filled/not filled comparison type was used in the data composition system settings and this filter was applied to the calculated field, which type was custom, Characteristics type, or any reference type, then the filter ignored types, included in the Characteristic, custom type or any reference type.	Eliminated unexpected system behavior.
Queries.	If a temporary table is created by the INTO clause, the temporary table field with NULL value has a compound data type. This compound data type includes the following types: Number with 1.0 precision String of 1 character DateTime Boolean NULL It is recommended to review all temporary table fields that might have NULL value. This change is not implemented in version 8.3.12 compatibility mode.	If a temporary table was created by the INTO clause, the temporary table field with NULL value had NULL type.	Temporary table fields with NULL values are now available in expressions that do not support NULL value. The CAST() function can be used in such cases.
Functional options.	If a functional option value is stored in a periodic information register resource, it is obtained from the slice last. The date from the functional option Period parameter, or the current date (if the functional option Period parameter is not specified) is used as a slice last date. This change is not implemented in version 8.3.12 compatibility mode.	If a functional option value was stored in a periodic information register resource, it was calculated by the logical OR operation across all stored resource values, if only the Period parameter was specified.	Eliminated unexpected system behavior. The system behavior is now compliant to documentation.
Managed forms.	Managed form table rows are filtered if there are multiple filter items and the first item filter value is Undefined. This change is not implemented in version 8.3.12 compatibility mode.	Managed form table rows were not filtered if there were multiple filter items and the first item filter value was Undefined.	Eliminated unexpected system behavior.

Changes that affect system behavior

Functionality	After	Before	Result of changes
Collaboration system.	Implemented the correct data area switching when a collaboration server is used. If the new data area is already registered in the collaboration server, this registration will be used.	This feature was not provided. The reconnection to the collaboration server was not performed if the data area was switched.	Eliminated unexpected system behavior.
Managed forms.	Changed the selected row view of the managed form table in the Taxi interface. The current row color now affects the selected row view.	The current row color did not affect the selected row view in the Taxi interface.	Improved the selected row view of the managed form table in the Taxi interface.
Development tools.	Modules locked with password are ignored in the Designer batch mode. A diagnostic message is displayed instead.	When modules locked with password were accessed in the Designer batch mode, the password request dialog box might be displayed.	Eliminated all interactive actions in the Designer batch mode, which does not support them.
Data display.	If the space is used as a group separator in the format string wizard the resulting format string the will use the nonbreaking space instead.	If the space was used as a group separator in the format string wizard the space was used in the resulting format string too.	Eliminated unexpected system behavior. Decreased number of issues caused by the incorrect group separator.
Collaboration system.	Implemented noncontext conversations with two participants (face-to-face). Other users can not take part in such conversations. Implemented the CollaborationSystemConversation.Group and CollaborationSystemConversationsFilter.Group properties. Implemented the capability to combine subscribers applications (infobases or data areas). Implemented the capability to match users of different applications. Implemented the capability to combine context conversations from different applications. Only the subscriber owner can perform the listed above actions. The Collaboration system management standard function can now merge applications, cancel applications merging, match users and context conversations. Implemented the CollaborationSystemUser.MappingKey property. Implemented the following methods of the collaboration system manager: CurrentApplicationID() GetApplication() GetSubscriberApplications() SetSubscriberApplicationLinks() CancelSubscriberApplicationLinks() GetSubscriberApplicationLinks().	These features were not provided. The collaboration might be established only within a single subscriber application.	Expanded the collaboration system capabilities.
Development tools.	Error and warnings that are generated by the metadata check, are now displayed as dbstru type messages. Implemented the DBRestuctError value for the error-type message. It describes the infobase restructuring error. Implemented the CommandFormatError value for the error-type message. It describes the invalid command format error.	Error and warnings that were generated by the metadata check, were displayed as log type messages.	Improved the diagnostics of issues that occur in the Designer agent mode.
Data composition system.	The composite type child fields are available in user settings if the user has the View right to at least one table of that type and the field itself. The composite type child field can be used in filters, sorting, conditional appearance and other available user settings. Implemented the RestrictGettingFieldsByRefByViewRight property of the DataCompositionProcessor.Initialize() method. This change is not implemented in version 8.3.12 compatibility mode.	If the user did not have the View right to at least one table of the composite type, there were no child fields of the locked type in the user settings.	The user can now obtain the child fields data that he has a View right on.
Charts.	The following options are now available in the chart type input field: The picture of a selected chart type is displayed in the input field. The picture of chart type is displayed in the chart type selection list. Implemented the autoselection when typing the chart name. Implemented the input field selection button that opens the chart type selection dialog box. Implemented the ChartTypeChooseDialog object. This change is not implemented in version 8.3.12 compatibility mode.	The chart type input field behavior was the following: There was no selected chart type picture in the input field. There was no chart type picture in the selection list. There was no autoselection when typing the chart name. There was no selection button that opened the chart type selection dialog box.	Improved the chart type selection in some scenarios.
Collaboration system.	The video call can not be performed if one of the participants do not have the microphone available. The appropriate message is generated. The collaboration system displays the microphone and camera diagnostic icons during the conversation.	The hardware diagnostics was not performed before and during the video call.	Eliminated unexpected system behavior.
Development tools.	The attribute or the tabular section can not be named Presentation if it is stored in the database. This change is not implemented in version 8.3.12 compatibility mode.	An attribute or a tabular section could be named Presentation, but this might cause different issues.	Eliminated unexpected system behavior.
Managed forms.	Implemented the following changes, when managed form tabs are displayed to the left or right of the Pages item: The height of tabs headers is not affected by the form height. You can now scroll tabs headers vertically if they do not fit the form height. You can use the wheel button to scroll tabs headers. You can now use touchscreen to scroll tabs headers in the thin client on Windows.	When managed form tabs were displayed to the left or right of the Pages, the tabs headers height was decreased to fit the form height.	Eliminated unexpected system behavior.
Managed forms. Mobile client.	The different form Auto values of managed form table HeightControlVariant property can now be used in configurations with version 8.3.7 or earlier compatibility mode.	The different form Auto values of managed form table HeightControlVariant property were used in configurations with version 8.3.10 or earlier compatibility mode.	Options of controlling the height of managed form table are now compliant with the mobile client.
Managed forms. Dynamic lists.	If the main table of the dynamic list has both groups and elements, the form conditional appearance is applied to columns that are not linked with the main table, regardless whether the current row displays either an element or a group of the main table. This change is not implemented in version 8.3.12 compatibility mode.	If the main table of the dynamic list had both groups and elements, the form conditional appearance was applied to columns that were not linked with the main table, in the following way: to a column that displays the common field (not expresiion) provided that the current row displays the main table element. otherwise the form conditional appearance is applied when the current row displays the main table group.	Eliminated unexpected system behavior.
Accounting registers.	If the Period adjustment property of an accounting register is greater than 0, the PeriodAdjustment standard attribute is displayed in the edit standard attributes form and becomes available in the StandardAttributes collection of the AccountingRegister metadata object (there is no PeriodAdjustment attribute in the StandardAttributes collection in version 8.3.12 compatibility mode).	The PeriodAdjustment standard attribute was not displayed in the edit standard attributes form and was not available in the StandardAttributes collection of the AccountingRegister metadata object.	Eliminated unexpected system behavior.

Optimization

Functionality	After	Before	Result of changes
Information registers.	Implemented the cluster index based on dimensions of slice first and slice last physical tables of an information register. Disabled index uniqueness verification. Optimized performance of queries operating with slice tables. This index can be built the following ways: restructuring the information register database restructuring when the verification and repair operation is performed.	Physical slice first and slice last tables were not indexed. The performance of the queries operating with slice tables was not optimal.	Improved physical slice tables performance in configurations with large number of users. Eliminated deadlocks when updating the physical slice tables.
Full-text search.	Reduced the size of temporary files created during the update of full-text search index. This change affects infobases with many separators the most. The new temporary file format is used when the compatibility mode is disabled. This change is not implemented in version 8.3.12 compatibility mode.	Temporary files created during the update of full-text search index were significantly larger.	Reduced the disk space allocated for a full-text search index generating when the infobase contains many separators.
DBMS operations.	Improved performance of virtual turnover tables of accumulation and accounting registers when they are grouped by day, month, or year, or when the BeginOfPeriod() query language function is used. This change is available in all supported DBMS, except for Microsoft SQL Server versions earlier than 2012.	Performance of virtual turnover tables of accumulation and accounting registers when they were grouped by day, month, or year, or when the BeginOfPeriod() query language function was used, was suboptimal.	Improved performance of virtual turnover tables of accumulation and accounting registers.
Common objects.	Improved performance of the following ValueTreeRowCollection object methods: Remove(), Insert(), Index(), and Move().	The performance of the following ValueTreeRowCollection object methods was insufficient: Remove(), Insert(), Index(), and Move().	Improved performance of the value tree rows from 1C:Enterprise script.
External reports and data processors.	Improved performance of loading external reports and data processors opened by large number of users.	Loading external reports and data processors opened by large number of users was longer.	Improved performance of loading external reports and data processors opened by large number of users.
Background and scheduled jobs. Configuration extensions.	Improved performance of second and further background job startups if they use the same set of configuration extensions. This change is available In file mode.	In file mode second and further background job startups were longer even if they used the same set of configuration extensions.	Improved background job startups in the file mode if they are operating with configuration extensions.
Common objects.	Optimized filling and deleting rows of a table of values.	Filling and deleting rows of a table of values were longer.	Improved table of values performance.
Web client.	Optimized page titles (tabs) rendering in the web client.	Page titles (tabs) rendering in the web client was slow and suboptimal.	Eliminated unexpected system behavior.
Common attributes / Data separation.	Improved opening forms performance in a configuration that uses common attributes.	Forms opened relatively slow if a configuration used common attributes.	Forms in a configuration that uses common attributes now open faster.
Data composition system.	Sometimes the data composition system template composer attempts to sort the data set by the DBMS means. The data composition system does not use it's own means in these cases. But the composition result may be incorrect because the row comparison operations are different in various DBMS and 1C:Enterprise platform. This change is not implemented in version 8.3.12 compatibility mode.	Data composition system template composer always sorts the data set by the data composition system means.	Improved the sorting performance during the report building in some scenarios.
Data composition system.	Improved the data composition system template generation if the data composition schema is composed of many queries that generate temporary tables with many fields that are not used in the composition process.	The data composition system template generation process was longer if the data composition schema was composed of many queries that generated temporary tables with many fields that were not used in the composition process.	Improved complex reports with many temporary tables building performance.
Queries.	If a query contains an IN subquery then a join with table from the IN subquery is used instead. This change is performed only if it does not affect the query result. This change is not implemented in version 8.3.12 compatibility mode.	If a query contained an IN subquery, the DBMS always used this subquery.	Improved the DBMS query plan in some scenarios.
Development tools. Server clusters.	Improved the configuration database update performance when it is initiated from a debug session in client/server mode.	The configuration database update was longer when it was initiated from a debug session in client/server mode.	Improved the configuration database update performance when it is initiated from a debug session in client/server mode.
Spreadsheet documents.	Improved the CheckPut() method performance if a spreadsheet document contains multiple sheets.	The CheckPut() method performance for a spreadsheet document with many sheets was insufficient.	Improved performance of spreadsheet document display.
Spreadsheet documents.	Improved copying to clipboard performance. Improved the GetArea() spreadsheet document method performance when applied to the spreadsheet document area with multiple rows with custom column formatting.	Copying to clipboard performance and the GetArea() spreadsheet document method performance when applied to the spreadsheet document area with multiple rows with custom column formatting were insufficient	Improved performance of obtaining the spreadsheet document area with multiple rows with custom column formatting.
Spreadsheet documents. Web client.	Improved performance of spreadsheet document groups collapsing and expanding in the web client.	The collapsing and expanding of spreadsheet document groups in the web client was longer.	Improved spreadsheet document performance in the web client.
Background and scheduled jobs.	Improved the background jobs execution and waiting for their completion.	The background jobs execution and waiting for their completion were longer.	The background jobs execution and waiting for their completion are now faster.

New functionality and changes in the 1C:Enterprise mode

Functionality	After	Before	Result of changes
Collaboration system.	Converstation participants receive notifications in the conversation form if one of them is typing a message. The following user statuses are now available: offline, away, do not disturb, and online. The Away status is available in thick and thin clients on Windows only. Updated the new message notification. You can now start a conversation with user from the user information form. Updated the collaboration system main window. Updated Collaboration system management standard function. Updated registration and cancelling registration forms.	These features were not provided.	Improved the collaboration system interface.
Interface.	Implemented the following changes In the Taxi interface: Managed form cell indents are reduced proportionally to the managed form scale if it is less than 100%. Implemented the factor of proportionality. When the managed form scale is 80%, the table row height equals to the table row height in the compact mode, depending on the font and the screen DPI. Reduced left and right table cell indents. Reduced left and right indents of spreadsheet document columns generated by the Output list command.	The Taxi interface behaved the following way: There was no factor of proportionality in reducing the managed form table cell indents. Left and right table cell indents were wider. Left and right indents of a spreadsheet document columns generated by the Output list command, were wider.	Improved the spreadsheet document and managed form table appearance in managed form with custom scale.
Interface.	All incorrect links are displayed as a link (not link's presentation). When the user favorites settings dialog box is closed, incorrect links remain in the favorites list and can be used or edited. Implemented the URLPresentation.Presentation() method. The GetURLsPresentations() method always returns the array of URLPresentation objects. Each URLPresentation object in this array will have different values depending on the link. This change is not implemented in version 8.3.12 compatibility mode.	Incorrect links had a blank interface presentation and were not available. They were deleted from the user work history after the user favorites settings dialog box was closed. The GetURLsPresentations() method applied to an incorrect link returned Undefined.	Improved links performance.
Web client. Spreadsheet documents.	Eliminated spreadsheet document printing faults in the web client if the HTML print method is selected.	A spreadsheet document might be printed with faults in the web client if the HTML print method was selected.	Eliminated unexpected system behavior.

New functionality and changes

Functionality	After	Before	Result of changes
Configuration properties.	For configuration property Compatibility mode, new value Version 8.3.12 is now implemented.	Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.11 was implemented.	Configurations developed using 1C:Enterprise platform version 8.3.12 or earlier can run on version 8.3.13 without any changes to configuration or to data structures. This allows for transition to version 8.3.13 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.12 after the transition to version 8.3.13, even if you disabled the compatibility mode (if you did, enable it again).
DBMS operations. System requirements.	Support of PostgreSQL version 10.1 is implemented.	PostgreSQL version 10.1 was not supported.	Extended list of supported DBMS.
Collaboration system.	Implemented 1C:Enterprise. Startup and notifications application. It provides the following features: A single notification center for all client applications (including the web client). Displaying notifications from applications that are not running (available for infobases connected to the agent). Opening a specific conversation when a client application is started or a client application window is maximized. Disabling notifications from a specific infobase. Quick access to 1C:Enterprise applications. The application is available for Windows and Linux, and also for Google Chrome, Mozilla Firefox, and Microsoft Internet Explorer. Implemented the option to display the new messages from the collaboration system and the notification center when starting a client application. Implemented the DisplayUserNotificationList command-line option of the client application startup in the thin, thick, and web clients.	Notifications from a specific application were displayed on a computer only if the application was running on that computer.	The collaboration system notifications from a specific application are available even if the application is not running.
Web client.	In the web client an option to specify the OpenID authentication provider (or the list of providers) is implemented. Each specified provider must support the OpenID Connect protocol. The openidconnect parameter is added to the default.vrd file. Implemented the OidcSelectedProvider command-line option in the web client. This feature is not available if the infobase is published from Designer. This feature is available in the web client only.	This feature was not provided. Only the 1C:Enterprise infobase could be used as the OpenID authentication provider in the web client.	Expanded the authentication options list in the web client.
Automated testing.	For TestedFormDecoration and TestedFormField objects, implemented the ClickFormattedStringHyperlink() method. The method emulates clicking a hyperlink in a formatted string.	This feature was not provided.	Extended automated testing capabilities.
InterfaceConfiguration extensions. Mobile platform. Mobile client.	Implemented the option to create custom styles and style elements. The DefaultStyle configuration property is now available in the managed application. Styles and Style elements are now available in the Common metadata tree branch. Implemented the following system colors: NavigationColor AuxiliaryNavigationColor ActivityColor ImportantColor AccentColor In version 8.3.12 compatibility mode, style elements of Color and Font type that are included in a style retain their values, provided that the style was not used in the ordinary application and the values of those style elements were not changed. The color of several interface items was slightly changed. In configuration extensions, you can create and adopt styles and style elements. Configuration extensions can override the DefaultStyle property.	This feature was not provided.	New options for client application appearance management.
Client application.	The application startup splash can be disabled now. Implemented the DisableSplash command-line option. It is available in the thin, thick and web client.	This feature was not provided. The application startup splash could not be disabled.	Extended capabilities for 1C:Enterprise integration with third-party systems.
Configuration extensions.	The following objects can now be created in the configuration extension: chart of characteristic types chart of accounts chart of calculation types accumulation register accounting register calculation register Configuration extension native accumulation registers do not support aggregates. The records of native and adopted configuration extension documents can now include the configuration extension native registers.	This feature was not provided.	Extended configuration extension usage options.
Data display.	Implemented the text declension feature. Implemented the GetStringDeclensions() global context method.	This feature was not provided.	1C:Enterprise is now capable of declining various texts, for example, in reports and documents.
Background and scheduled jobs.	Implemented the option to wait for the completion of one or several background jobs within the specified period. For BackgroundJob and BackgroundJobsManager objects, implemented WaitForExecutionCompletion() method. The WaitForCompletion() method is deprecated. We recommend that you review your algorithms that involve background jobs. The message informing about waiting for the completion of a background job that is missing from the lists of running and completed jobs is more accurate. 1C:Enterprise can detect situations where the current user that does not have the Administration access right attempts to wait for the completion of a background job started by another user.	This feature was not provided. Waiting for completion of one or several background jobs was available. If the background job completed abnormally, an exception was thrown. The message informing about waiting for the completion of a background job that did not exist was not clear.	Simplified waiting for background job completion. Simplified other operations performing while waiting for background job completion.
Server clusters.	Implemented the feature that evaluates the CPU load during the following periods of time in the current session: during the current server call within the last 5 minutes within the whole session Added the following properties of the session data for the rac utility: cpu-time-current cpu-time-5min-last cpu-time-total Added the following properties of the ISessionInfo object: cpuTimeCurrent cpuTimeLast5Min cpuTimeAll. Implemented the CpuTime property of the <CALL> event. It stores the duration of completed server call in ms. You can now create various resource counters that can register different values, such as CPU load, memory load, input/output data size and so on. The cluster console is now capable of operating such resource counters. Added the following commands to the rac utility: counter update. Creates or edits the resource counter. counter remove. Deletes the resource counter. counter values. Displays the current counter value. counter list. Displays the current counter settings. You can now manage sessions depending on the resource counters values. If a specific session exceeds the particular resource limit, the following actions might be performed: terminating the server call and the whole session terminating the server call, but not the whole session (if possible) decreasing the priority of the current server thread logging the information in the technological log (<ATTN> event) The cluster console is now capable of setting the resource load limits. Added the following commands to the rac utility: limit update. Creates a limit. limit list. Displays the current limits list. A new feature that controls resource consumption level was implemented in the Java-interface of the 1C:Enterprise server cluster administration tool (read more).	These features were not provided.	You can set the resource load limits on the computer with cluster server. Improved system reliability.
Data composition system.	Implemented the DataCompositionUserSettings.GetMainSettingsByUserSettingID() method. This method returns the array of main settings by the user setting ID. It can be used to specify user settings properties that are otherwise read-only.	This feature was not provided.	Simplified access to user settings of the data composition system.
Spreadsheet documents.	Implemented the option to optimize the view of spreadsheet documents that do not fit the screen width (mostly on mobile devices). The optimization eliminates the need for horizontal scrolling. For spreadsheet document, implemented GetCompactDocument() method. It returns the compact version of a spreadsheet document. For spreadsheet document, implemented SetAutoWidth() method. It sets the horizontal stretching mode for spreadsheet document columns. For spreadsheet document, implemented ConvertToCompactMode() and RevertToDefaultMode() methods. They respectively create and delete a copy of a spreadsheet document that fits the width of a small screen. When a spreadsheet document is printed or saved, the original non-optimized spreadsheet document is used as a source. Implemented the ResultViewMode property of the report managed form field extension. It allows you to manage the report transformation. Implemented the Compact Mode command of the report managed form field extension. It allows you to edit the ResultViewMode property value. The current report view modes for the mobile client and other client applications are separately stored in the system settings storage.	These features were not provided. The spreadsheet document could not be transformed to fit the width of the small screen.	Improved spreadsheet document appearance on a small screen (for example the mobile device screen).
Metadata objects.	The option to analyze metadata, stored in .cf or .cfe file, is implemented. Implemented the ConfigurationMetadataObject constructor. You can now get the configuration name, version, and vendor from the .cf or .cfe file. Implemented the ConfigurationDescription object. You can now get the list of versions, suitable for the update, and the resulting version number from a .cfu file. Implemented the ConfigurationUpdateDescription object.	This feature was not provided. The information about the configuration or the configuration update was not available.	Simplified development of automated configuration updating and distribution packages creating tools.
Configuration extensions.	The following configuration properties can now be adopted: main section picture splash logo You can now adopt the Picture type objects by replacing the current picture. The following configuration extension properties can now be specified: brief extension information detailed extension information extension copyright vendor information address extension information address.	These features were not provided.	Extended configuration extension usage options.
Configuration extensions. Data exchange.	The extension native exchange plan can now include adopted objects. You can now adopt the exchange plan data (create exchange plan attributes, tabular sections, and tabular section attributes).	The extension native exchange plan could include the extension native objects only. The exchange plan data could not be adopted.	More configuration extension management options.
Data history.	You can now override default data history forms. Added the following properties of the Configuration object: DefaultDataHistoryChangeHistoryForm DefaultDataHistoryDataVersionForm DefaultDataHistoryVersionDifferenceForm. Implemented DataHistoryVersionFilterDialog and DataHistoryUsersChooseDialog objects.	Default data history forms overriding was not available.	Extended data history options.
Internet-enabled functionality.	Implemented the following HTML document options: Delete all document items of a certain category. Implemented the HTMLDocument.DeleteByCategory() method. Get a string with all readable text from the document. Implemented the HTMLDocument.ExtractPlainText() method. Select all document items by a specific filter. Implemented the HTMLDocument.FindByFilter() method. Delete all document items by a specific filter. Implemented the HTMLDocument.DeleteByFilter() method.	These features were not provided. The only available option was to cycle HTML document DOM model and perform actions with its items.	Simplified and improved the HTML document performance in particular scenarios (for example if you want to delete all <script> tags)
Internet-enabled functionality.	Emails can now use OAuth2 protocol together with IMAP protocol. Implemented the following InternetMailProfile object properties: TokenAuthentication and AccessToken.	This feature was not provided.	The email servers with the OAuth2 authentication protocol are now supported.
Queries.	A field with consequently increasing unique values can now be added to the temporary table. Implemented the RECORDAUTONUMBER() query language function. It is available for a temporary table only. The RECORDAUTONUMBER() function is not supported in the following cases: there is a UNION keyword on the top level query does not create a temporary table outside the selection list in expressions.	This feature was not provided.	Simplified adding the unique field with consequently increasing values to a temporary table.
Automated testing.	Implemented the following options of the spreadsheet document extension of the TestedFormField object: Getting the number of columns that contain data. Implemented the GetDocumentDataAreaHorizontalSize() method. Getting the number of rows that contain data. Implemented the GetDocumentDataAreaVerticalSize() method.	These features were not provided.	Extended automated testing capabilities.
Data history.	The option to handle the data version restoration in the object module and in the managed form module is now available. If a form displays one of the older object version, the version number is displayed in the form header. Implemented a dynamic list command that displays the selected object data history (if supported). It is available for users with ViewDataHistory access right. Implemented the VersionNumberSwitchToDataHistoryVersion managed form parameter. Implemented the GenerateFromDataHistoryVersionProcessing() event handler in the following modules: catalog object module document object module chart of accounts object module business process object module task object module information register record set module. This handler is called when the object is generated based on the data history version.	The developer could not handle the object version restoration. The object history could be displayed in the object form or the register record form only.	Extended data history options. Improved data history security.
Data display.	New pictures were added to the picture library: Conversations, NewConversation, Notifications.	The listed pictures were not available in the picture library.	More content for the picture library.
Data history.	Implemented the data history of exchange plans, charts of calculation types, and constants.	This feature was not provided.	Data history is now available for more objects.
Applied objects.	Implemented the ConstantValueKey object. Implemented the CreateConstantValueKey() method of the constant manager.	This feature was not provided.	Expanded constant management capabilities.
Development tools.	Implemented the option to create a macOS-compatible distribution package. The application distribution package now includes the .zip archive that contains the distribution file and the installer executable files for each supported operating system (Windows, Linux, macOS). The executable files now have the right parameters (Linux, macOS), so you can now unpack the distribution package and install the applicaton. Implemented the CreativeDistributivePackage command-line option of the Designer batch mode. The CreateDistributive command-line option of the Designer batch mode is deprecated.	Creating an application distribution package for Windows and Linux only was allowed. The application could not be installed on macOS. There was no option to create an application distribution package with correct executable files for each supported operating system. You had to specify the correct parameter in the Linux executable file to install the application.	You can now install the application on any supported operating system. The distribution package is now compatible to any supported operating system.
System requirements. Configuration repositories.	Implemented the 64-bit configuration repository server on Linux.	There was only the 32-bit configuration repository server available on Linux.	The functionality of configuration repository server is now fully available on 64-bit Linux.
Data history.	Implemented the option to force the update of data history of specific infobase object. Imolemented the UpdateHistory() method of the DataHistory object.	This feature was not provided. The data history update was available for all infobase objects at once only. If a specific object data history form was opened, some versions might not be displayed.	The specific object data history form now displays the full history.

Library updates

The LibEtPan library is updated to version 1.8.
The WebSocket library is updated to version 0.7.0.
The Micosoft JDBC Driver for SQL Server is updated to version 6.2.

Changes in demo configurations

Implemented the option to specify the image of the good by dragging it to the form of the good.
Expanded options of the user settings form if the collaboration system is linked to the infobase: install and update the client application agent, create or cancel the link between the application and the client application agent.
The new messages notification was changed to show the options of the StringWithNumber() function.