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

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.

Only the 1C:Enterprise infobase could be used as the OpenID authentication provider in the web client.

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.

The application startup splash could not be disabled.

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

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.

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.

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

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.

The spreadsheet document could not be transformed to fit the width of the small screen.

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.

The information about the configuration or the configuration update was not available.

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

You can now adopt the exchange plan data (create exchange plan attributes, tabular sections, and tabular section attributes).

The exchange plan data could not be adopted.

• DefaultDataHistoryChangeHistoryForm
• DefaultDataHistoryDataVersionForm
• DefaultDataHistoryVersionDifferenceForm.

Implemented DataHistoryVersionFilterDialog and DataHistoryUsersChooseDialog objects.

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

The only available option was to cycle HTML document DOM model and perform actions with its items.

Implemented the following InternetMailProfile object properties: TokenAuthentication and AccessToken.

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.

• Getting the number of columns that contain data. Implemented the GetDocumentDataAreaHorizontalSize() method.
• Getting the number of rows that contain data. Implemented the GetDocumentDataAreaVerticalSize() method.

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 object history could be displayed in the object form or the register record form only.

Implemented the CreateConstantValueKey() method of the constant manager.

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.

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.

The distribution package is now compatible to any supported operating system.

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

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

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

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.

The performance of the queries operating with slice tables was not optimal.

This change is available in all supported DBMS, except for Microsoft SQL Server versions earlier than 2012.

The reconnection to the collaboration server was not performed if the data area was switched.

A diagnostic message is displayed instead.

Decreased number of issues caused by the incorrect group separator.

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

The collaboration might be established only within a single subscriber application.

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.

The collaboration system displays the microphone and camera diagnostic icons during the conversation.

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

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.

• SetModificationTime()
• SetModificationUniversalTime()
• BeginSettingModificationTime()
• BeginSettingModificationUniversalTime().

All errors of File object methods throw the same exception.

• SetModificationTime()
• SetModificationUniversalTime()
• BeginSettingModificationTime()
• BeginSettingModificationUniversalTime().

The former names are supported for compatibility purposes.

• GetHTML()
• SetHTML()

• GetDocumentHTML()
• SetDocumentHTML()

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.

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.

Interactive managing of the camera backlight was available only on iOS.

There was no option to use a camera flash as a flashlight.

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.

The InAppPurchasesValidationManager object and the InAppPurchasesValidation global context property were available only on the server of the PC platform.

• DisplayImportance for all controls
• CurrentRowUse and TableBehaviorOnHorizontalCompression for a form table.

Implemented input hints for multiline input fields.