• Common modules
• Object modules for all object types
• Manager modules for all object types
• Session module
• Managed application module
• External connection module
• Command modules

The option to adopt ordinary form modules and ordinary application modules is not available.Therefore, you can adopt any module except for modules that are used solely in ordinary applications.

The following operations are now available:

• Call any methods of the extended module from the extending module
• Add event handlers to adopted modules of abovementioned types

Export methods and variables of the extended module form the uniform context of the extended module.

Adopted form modules are now handled differently.

You have the option to allow or deny extending all modules of abovementioned types (the all module extensions security profile property). You have the option to provide a list of modules where extension is allowed (the Modules available for extension property) or where extension is denied (the Modules not available for extension property).

You have the option to create common modules in configuration extensions.

For ISecurityProfile object, the following properties are implemented: AllModulesExtension, ModulesAvailableForExtension, and ModulesNotAvailableForExtension (software administration of server clusters based on COM objects).

For ISecurityProfile interface, the following methods are implemented: getAllModulesExtension(), setAllModulesExtension(), getModulesAvailableForExtension(), setModulesAvailableForExtension(), getModulesNotAvailableForExtension(), and setModulesNotAvailableForExtension() (Java interface for server administration).

In the server cluster command-line utility (rac), for the profile command, the following parameters are implemented: all-modules-extension, modules-available-for-extension, and modules-not-available-for-extension.

Adopted form modules were handled differently.

The option to specify which modules can be extended was not available.

New security profile options related to configuration extensions.

• Automatic reuse of the current session when a new request comes from the same user.
• Session lifetime management using HTTP request headers.

For web services and HTTP services, the ReuseSessions and SessionLifetime properties are implemented. If a web service or HTTP service is a native configuration extension object, these properties are read-only.

The following additions to the default.vrd file are implemented:

• <standardOData> element, which is subordinate to <point> element.
• reuseSession, sessionMaxAge, poolTimeout, and poolSize attributes for <point> and <service> elements.

The enableStandardOData attribute of the <point> element is deprecated.

If a web service or HTTP service is a native configuration extension object and it is either not published in the default.vrd file or published without the session reuse option, session reuses are not available for that service.

• If a text is selected or the cursor is located at the beginning of a paragraph, pressing Tab increases the indent.
• Otherwise pressing Tab adds a tab character.

The FormattedDocumentBookmark object is linked to a character within a paragraph, not to a character position. If a text is changed, the bookmark position better matches its original position.

• Specifying byte order
• Operations with memory buffer that stores binary data
• File operations where files are treated as binary data
• Byte-by-byte data access
• Reading and writing some data types (String and Number).

The following objects are implemented: BinaryDataBuffer, Stream, FileStream, MemoryStream, DataReader, DataWriter, DataReadingResult, FileStreamsManager. The BinaryData.Size() method is now available in the web client.

For the BinaryData.Write() method, the option to write data to a stream is implemented.

The OpenStreamForReading() method is implemented, it opens a stream for reading binary data specified in the BinaryData object.

• -AllUsers. Perform registration for all computer users.
• -CurrentUser. Perform registration for the current user.
• -Auto. Automatically select registration mode based on the user rights, without displaying any questions.

The behavior of the /regserver option without parameters is not changed.

The ConversionToCanonicalXML object is implemented. For the XMLCanonicalizationType system enumeration, the following values are implemented: CanonicalXML1_1 and CanonicalXML1_1WithComments.

The XMLCanonicalizingWriter and DOMCanonicalization objects are deprecated. These objects do not support Canonical XML 1.1 specification.

Running Designer with the /IBRestoreIntegrity parameter is recommended if a previous database configuration update (performed either interactively or in batch mode) have not been completed successfully because of unexpected Designer shutdown or power outage.

• Infobase.Set predefined data update
• Infobase.Predefined data update
• Data.Set predefined data initialization
• Data.Predefined data initialization
• Data.Add predefined data
• Data.Modify predefined data
• Data.Delete predefined data
• Data.Initialize predefined data data not found

GOST R 34.10-2012 and GOST R 34.11-2012 algorithms are not supported.

• Predefined data item flag and name.
• Data attribute presentations. The ____Presentation field name suffix is used for getting presentations. Presentation fields are only available for use in the $select operator and only if you specify them explicitly.
• Specific attributes of tabular sections or record sets (in the $select operator).

The option to add roles to configuration extensions is implemented, this requires the use of 1C:Enterprise script. In Designer, the only operation available for such roles is deletion.

The option to apply data access restirictions added in a configuration extension to the resulting configuration is implemented through the use of security profiles (the access rights extension property).

For the ISecurityProfile object, the RightExtension and RightExtensionDefinitionRoles properties are implemented (for the technology of programmatic cluster administration based on COM objects).

For the ISecurityProfile object, the RightExtension and RightExtensionDefinitionRoles properties are implemented (for the Java administration server interface).

For the server cluster command-line utility (rac), the right-extension and right-extension-definition-roles parameters of the profile command are implemented.

• The Check applicability command in the Configuration extensions window
• 1C:Enterprise script methods
• Designer batch mode option

When a client application is started, extension compatibility issues are no longer displayed in the message window. Instead, they are added to the information for technical support (which is available from the About 1C:Enterprise window). If any compatibility issues are encountered, a warning dialog box is also displayed, with a link to the full list of issues.

For the ConfigurationExtensions object, the CheckCanApplyAll() and GetCurrentSessionApplicationIssuesInformation() methods are implemented. For the ConfigurationExtension object, the CheckCanApply() method is implemented.

For Designer batch mode, the /CheckCanApplyConfigurationExtensions command-line option is implemented.

For the Configuration extension management standard function, the Check applicability when adding and loading extensions check box is implemented.

When an extension was attached, the diagnostics messages were displayed in the message window.

The PredefinedDataUpdate system enumeration is now available in the thin and web clients.

For all metadata objects, the ChangedByConfigurationExtensions() method is implemented. It defines whether a configuration object is available in the current session.

1C:Enterprise server was the only 1C:Enterprise component that had a 64-bit version.

Issues caused by insufficient memory for operations with large configurations (such as comparing and merging configurations) are eliminated.

Support of scrolling with 2-finger gestures in all directions is implemented for all controls that have scroll bars.

The effect of 1-finger gestures depends on control type:

• Horizontal gesture:
• Scrolling in spreadsheet documents, tables, or forms
• Selection in text documents, multiline text boxes, formatted documents, planner fields, and HTML document fields
• Selection or dragging in graphical and geographical schemas
• Vertical gesture:
• Selection or dragging in geographical schemаs
• Scrolling in other form controls that support vertical scrolling

The tap detection area is expanded for the following controls:

• Check boxes in form tables
• Buttons that expand or collapse tree branches in form tables
• Buttons that move through hierarchical lists in form tables
• Hyperlinks in command bars
• Buttons with hidden borders
• Cells in form field extensions for period fields

For graphical schemas, support of scaling using the scaling gesture is implemented.

For tapping form buttons and command bar buttons, a visual effect is implemented.

• Module check
• Configuration check

The performance of 1C:Enterprise script execution in client applications was insufficient.

The time required to create an initial image of a client/server infobase is significantly reduced.

If a 1C:Enterprise server cluster connection to PostgreSQL DBMS is idle for 30 minutes, it is released.

1C:Enterprise server cluster did not release idle connections to PostgreSQL DBMS.

To apply this optimization to an existing infobase, perform infobase verification and repair with the Reindexing infobase tables check box selected. Once the restructuring is completed, the optimization is applied to all restructured objects.

If lock escalation causes a conflict with other locks, the escalation is not performed and an attempt to set the requested lock is made instead. This can lead to a total of more than 100 000 locks in a single area.

In scenarios where a single transaction uses a large number of managed locks with slight differences (for example, a single dimension varies), it is recommended that you set a single managed lock where the value of that dimension is not set.

Improved system reliability in scenarios with large numbers of simultaneous locks.

For the chart of calculation types table that stores serial numbers of calculation type displacements, a nonunique index by displacement number is implemented. As a result, simultaneous editing of a single chart of calculation types in different data areas of a separated infobase never requires waiting for lock releases.

To apply this optimization to existing infobases, perform the infobase verification and repair operation with the Restructure infobase tables option selected.

For the chart of calculation types table that stored serial numbers of calculation type displacements, a nonunique index by displacement number was not available.

In large databases and especially separated databases, reduced number of table-level locks for the following tables: actual action period table of a calculation register and table that stores serial numbers of calculation type displacements.

Faster execution of SliceFirst() and SliceLast() information register manager methods.

• Designer displays a warning dialog box, providing the options to continue the operation or cancel it.
• The execution of the webinst utility is not interrupted, but it displays a warning.

In the calendar used to enter a date in a text box, selection of the current date by clicking the Today hyperlink is implemented.

In the thin and thick clients, in the calendar used to enter a date in a text box, selecting a date that does not belong to the current month adds this date to the text box.

In the calendar used to enter a date in a text box, clicking the Today hyperlink set the focus to the current day of the month in the month currently selected in the calendar.

In the thin and thick clients, selecting a date that did not belong to the current month activated the selected month in the calendar field. In the web client, this added the selected date to the text box.

Unified system behavior in different client applications.

When the thick client is started from Designer, the /EnableCheckExtensionsAndAddInsSyncCalls option is not passed to the client. The behavior of the thin client and the web client in this scenario is not changed.

The behaviour of configuration verification and refactoring is not changed: they display warnings for all synchronous methods calls and recommend conversion to asynchronous methods.

When the thick client was started from Designer, the /EnableCheckExtensionsAndAddInsSyncCalls option was passed to the client.

The SetLockWaitTime() method requires administrative rights in a nonseparated session, sets an exclusive database lock (if it was not set earlier), and throws an exception if the exclusive lock cannot be set.

The change of the data lock timeout is applied immediately to all DBMS except IBM DB2. Changing the lock timeout in IDB DB2 requires a database restart.

In some cases simultaneous access to a single infobase with different platform versions was allowed, where one version was 8.2.18 or earlier and the other one was in range 8.3.1-8.3.3.

If the Internet connection uses a proxy server that decrypts secure connection (HTTPS) traffic, the system administrator must add the certificates that sign the proxy server certificate to the trusted root certificate store of the operating system.

You can disable the safe mode manually using the SetSafeModeDisabled() and GetSafeModeDisabled() global context methods. These methods are not available in configuration extensions.

The list of handlers where the safe mode is automaticly disabled is provided in the documentation.

HTTPConnection, FTPConnection, and WSProxy objects automatically select TLS 1.2 protocol, regardless of the specified client certificate source.

For the conf.cfg configuration file, the ForceTLS1_0 parameter is implemented.

Simultaneous use of /HttpsForceTLS1_0 and /HttpsForceSSLv3 command-line options in the thin client is not supported.

Eliminated unexpected system behavior.

• StartPageForms.

• HomePageForms.

• StartPageSettings.

• HomePageSettings.

• StartPageWorkingArea.

• HomePageWorkingArea.

• StartPage.

• HomePage.

• StartPage.

• HomePage.

• ItemsAndTitlesAlign.

• ItemsAndTitlesAlignVariant.

The File.GetMobileDeviceLibraryFilePresentation() method is implemented. It returns the file presentation for displaying on the mobile device.

You can use mobile device library file names (with the content schema) in constructors of the following objects: File, BinaryData, Picture, and MobileDeviceApplicationRun. You can also use them as parameters for the following global context methods: RunApp(), GotoURL(), FileCopy(), MoveFile(), DeleteFiles(), and FindFiles().

The MobileDeviceLibraryDirectory() global context method is implemented. It returns a path to a mobile device library (a picture, audio, or video library).

For the TelephonyTools object, the CallsHandlingSupported(), AttachCallsHandler(), and DetachCallsHandler() methods are implemented. The TelephonyTools.CallsHandlingSupported() method returns True on Android only.

• The option to play a sound or vibration alert is implemented. The MultimediaTools.PlaySoundAlert() method is implemented.
• The option to play audio data of various types is implemented. Playing is performed using the default application provided with the operating system. The option to stop playing is implemented. For the MultimediaTools object, the PlayAudio(), StopAudioPlayback(), and GetAudioDuration() methods are implemented.
• The option to read text using the screen reader provided with the operating system is implemented. The option to stop reading is implemented. For the MultimediaTools object, the PlayText(), StopTextPlayback(), and TextPlaybackSupported() methods are implemented.

In Designer, the option to create data composition schemas for reports that run in mobile applications is implemented.

You can export a mobile configuration from Designer to 1cema.zip format, which includes the add-ins used in the configuration.

In the mobile application builder, the option to build applications with add-ins is implemented.

Add-in development technology documentation and examples are updated (read more).

• Display a command bar button as a hyperlink.
• Set horizontal picture alignment on a managed form button.
• Set gaps between command bar buttons.
• Set command bar button shapes (except for buttons located in popups).
• Set the view of managed form buttons.
• For text boxes, support of CreateButton and ChoiceButtonRepresentation properties is implemented.
• For text boxes, support of EditTextChange and Creating events is implemented.

Support of BorderColor, BackColor, TitleTextColor, and TitleFont properties is implemented for buttons of CommandBarButton and CommandBarHyperlink type and for form group extensions for popups.

The InternetConnectionInformation global context property is implemented.

For the ContactManager object, the GlobalContactsKeySupported() method is implemented.

For the CalendarsManager object, the GlobalCalendarsKeysSupported() and GlobalEventsKeysSupported() methods are implemented.

The GlobalContactKey parameter of the AccountContactData object constructor is no longer supported. The values of properties that describe global contact keys, calendars, and calendar events depend on the result of the function that checks the availability of global key operations. If global key operations are not supported, requests to these values return blank strings.

Availability of LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects on the mobile application server is implemented.

The LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects were not available on the mobile application server.