ZIP archive support is implemented using the zipArchive library.

The ZIPCompressionMethod.BZIP2 system enumeration value is implemented.

The Info-ZIP library was used for ZIP archive support. The BZIP2 compression method was not supported.

Improved support of ZIP archives (including the support of national characters in file names). You can use the prevalent archive file format on Linux.

Configuration support settings management was only available in the interactive mode.

For the WSProxy object constructor, the Location parameter is implemented.

For the WSReferenceManager.CreateWSProxy() method, the Location parameter is implemented.

A web service could be used only if it was located at the address specified in a WSDL file imported to the applied solution (a WS reference configuration object).

Only streaming API and object model were supported for JSON.

For the JSONWriterSettings constructor, the EscapeSlash parameter is implemented. For the JSONWriterSettings object, the EscapeSlash property is implemented.

The EscapeSlash property is used by the JSONWriter.WriteValue() method.

You can publish Internet services belonging to configuration extensions to web servers.

In the default.vrd file, the publishExtensionsByDefault attribute is implemented for ws and

httpServices elements.

The GetCurrentInfoBaseSession() global context method is implemented. The InfoBaseSession.GetBackgroundJob() method is implemented.

The only way to determine the session type was getting all infobase sessions and iterating through them.

The BeginWriting() method is implemented for the following objects: TextDocument, SpreadsheetDocument, FormattedDocument, and GraphicalSchema.

The BeginReading() method is implemented for the following objects: TextDocument and GraphicalSchema.

The RepresentableDocumentBatch.BeginWritingFileForPrinting method is implemented.

For the Issuer and Subject properties of the CryptoCertificate object the Street field is implemented.

Each of the Issuer and Subject structure fields of the CryptoCertificate object is accessible by:

• Mnemonic key (for example, CN)
• UUID key (for example, OID2_5_4_3 for the CN field).

Name length for new configuration objects is limited by 80 characters. Existing configuration objects can have names longer than 80 characters until you attempt to edit their names.

1C:Enterprise script modules are dumped to .bsl files.

In the dump configuration files dialog box you can select the dump format: flat or hierarchical.

The Format parameter is implemented for /DumpConfigToFiles Designer batch mode command-line option. The new parameter describes the dump format.

By default configurations are dumped to hierarchical file structures.

No length restrictions were applied to configuration object names.

1C:Enterprise script modules were dumped to .txt files.

You can simultaneously load a configuration from files and update database configuration.

For the /LoadConfigFromFiles Designer batch mode command-line option, the following parameters are implemented: -files (files to load) and -listfile (file containing a list of files to load).

In the technological log, the CONFLOADFROMFILES event is implemented.

Only restoring the entire configuration from files was available.

The dialog box with automatic debug item attachment settings is refactored.

Debug server (dbgs) is implemented, it can be started from the command line, and also as an operating system service. The new debug protocol is not supported on Linux servers in the scenario where 1C:Enterprise starts automatically during operating system startup.

The following command-line options are implemented for the server agent (ragent): /debug, /debugServerAddr, /debugServerPort, and /debugServerPwd.

For the client application the following command-line option is implemented: /debug.

In default.vrd file, for the <debug> element, the protocol attribute is implemented.

In comcntrcfg.xml file, for the <config> element, the protocol attribute is implemented.

• Pictures cannot be localized.
• The option to build a platform distribution kit is not provided.

If the dump files do not include a version number, they are treated as version 1.0-compliant.

Files are always dumped in the format that matches the 1C:Enterprise platform version.

A configuration can be restored from files only if the version of the files is earlier than or equal to the version supported by the 1C:Enterprise platform.

The result of the check is displayed in the About 1C:Enterprise dialog box.

The Designer interface includes new commands related to this functionality. The following global context methods are implemented: GetConfigurationID, GetLicensingClientName, GetLicensingClientAdditionalParameter, SetLicensingClientParameters, AttachLicensingClientParametersRequestHandler, and DetachLicensingClientParametersRequestHandler.

For the conf.cfg configuration file, the LicConfigDebugTimeouts parameter is implemented. The parameter is used to reduce the check interval.

The implementations of this functionality are subject to future announcement.

In the system menu, context menu of the opened windows panel, and form title context menu, the corresponding commands are implemented.

This options requires installing a browser extension. The web client propmts the user to install the extension first time they attempt to access the clipboard using context menu commands. If the extension is not installed, the clipboard can be only accessed using keyboard shortcuts.

Clipboard access using context menu commands was not supported.

• Opening a subsystem editor window
• Including an object into a subsystem
• Setting a filter by subsystem in the configuration tree window

• Loading and rendering geographical schemas
• Selecting an object in a geographical schema field

• Number of data lock waits in the file DBMS.
• Time required for loading an infobase object from a DBMS in the client/server mode.
• Number of waits due to internal 1C:Enterprise server locks during bulk reading of infobase objects from a DBMS.
• DBMS load (due to a significant decrease of the number of transactions).

• Form opening
• Queries
• Functional options
• Predefined data
• Reusable return values
• Data access using "." (dot)

The Show in list menu (in a document form) does not contain list forms disabled by functional options.

The Show in list menu (in a document form) contained list forms disabled by functional options.

When a scheduled job is started or completed in an infobase, this does not affect the performance of other infobases in the cluster.

Improved system reliability in the following scenarios:

• Database configuration update
• Background jobs
• Dynamic update

When a scheduled job was started or completed in an infobase, this affected the performance of other infobases in the cluster.

The system reliability was insufficient in several scenarios.

In default.vrd file, for the pool item, the serverPingPeriod and serverPingTimeout attributes are implemented.

In the web server publishing dialog box, the Check period and Check timeout properties are implemented.

In the technological log, for the CONN event, the list of logged events related to the detection of connection losses between processes in a single cluster is extended.

The option to edit a variable value during debugging is implemented.

The option to view all local variables of a method being debugged in a dedicated window is implemented.

The state of folders (expanded or collapsed) in the immediate window and in the local varibles window is preserved when switching to the next debug step.

If you use the Break command (Shift+F5) to close an application being debugged, the modal exit confirmation dialog box is never displayed.

The option to edit a variable value during debugging was not provided.

The option to view all local variables of a method being debugged in a dedicated window was not provided.

The state of folders (expanded or collapsed) in the immediate window and in the local varibles window was not preserved when switching to the next debug step.

Using the Break command (Shift+F5) to close an application being debugged sometimes opened the modal exit confirmation dialog box.

• Read() method of theTextDocument object
• Write() method of theTextDocument, SpreadsheetDocument, FormattedDocument, and GraphicalSchema objects
• WriteFileForPrinting() method of the RepresentableDocumentBatch object

When attaching an extension, the platform does not check whether the extension fits the session security profile restrictions.

When attaching an extension, the platform checked whether the extension fit the session security profile restrictions.

• TemplateLanguageCode.

• LanguageCode.

• Size and alignment group (contains the Align left command)
• Size and alignment group (contains the Align top command)
• Group group (contains the Auto space: horizontal command)
• Group group (contains the Bring to front command)
• Group group (contains the Send to back command)

• Horizontal alignment
• Vertical alignment
• Distribute
• Bring forward
• Send backward

The mobile application builder supports building mobile applications that require this extension.

The SearchDirection system enumeration is implemented.

The mobile platform for Windows Phone supports all mobile platform features available on other operating systems, excluding:

• Conversion of geographical coordinates to addresses and back, and ShowOnMap() global context method
• Barcode scanning
• Phone call log
• Printing
• Receiving text messages
• Notifications
• Contacts
• Calendars

The mobile platform specifics are described in the documentation.

The mobile platform distribution file mobile.zip is complemented with new data.

New builder parameters are added:

• The option to build applications for Windows operating system
• Support of graphic assets required for Windows operating system

Publishing of built applications to Windows Store is not supported.

When loading mobile platform data from the mobile.zip file to mobile platform builder, you have the option to load only mobile operating systems that are present in the archive.

The option to specify different application IDs for different mobile operating systems is supported.

The option to export developer certificates from the mobile application builder database is implemented.

Attempts to load the mobile platform from the mobile.zip file to mobile application builder were only successful if the file contained platform versions for both Android and iOS.

A single mobile application ID was assigned for Android and iOS builds.

Exporting developer cerificates from the mobile application builder database was not supported.

The ManagedForm.ExecuteNavigation() method and the NavigationProcessing managed form event are implemented.

To access the full list of bookmarks, on the Edit menu, click Bookmarks.

When deleting a configuration object, you have the option to search for the object name usage instances in the entire configuration.

When modifying or deleting a managed form item, attribute, or parameter, the check for usage instances of its name in the form module is performed. When renaming an item, attribute, or parameter, you have the option to update its name usage instances in the form module.

The Find references to object operation now includes the search in module texts.

You can specify whether you want to use these options in the Designer options window.

In the TimeScalePosition system enumeration, the following values are implemented: Left and Right (when applied to a Gantt chart, both are treated as Top).

Infobases could be bound to repositories only interactively.

For managed forms, the ExecuteNavigation() method and NavigationProcessing event handler are implemented.

In the client application, in the sections panel editor, the following section view features are available:

• In Version 8.2 interface compatibility mode:
• Picture
• Text
• PictureAndText
• In Taxi interface compatibility mode:
• Picture
• Text
• PictureAndText
• PictureOnTopAndText

Extended section view capabilities for the sections panel in the Taxi interface.

The only commands available in the web client are print and preview.

In the Russian interface some of the graphical schema commands are renamed to the following:

• Выровнять по левому краю
• Выровнять по правому краю
• Выровнять по верхнему краю
• Выровнять по нижнему краю
• Переместить вперед
• Выровнять по центру
• Выровнять по середине

In the Russian interface some of the graphical schema commands had different names:

• Выровнять влево
• Выровнять вправо
• Выровнять вверх
• Выровнять вниз
• Переместить вверх
• Выровнять по центру горизонтально
• Выровнять по центру вертикально

The 32-bit and 64-bit versions of the utility are available for Windows and Linux operating systems.

File change monitoring was only available using third-party tools. Monitoring of database object changes was not available.

If the platform uses POP3, an attempt to use this parameter when it is set to False generates an exception.

The platform behavior in 8.3.5 compatibility mode is not changed (for the part where the parameter is set to False).

• If the parameter was not specified, the flag indicating whether a message was read was not set for messages retrieved from the mail server.
• If the parameter was specified, the flag was set.

The following methods are implemented for the managed form table extension for dynamic lists:

• GetPerformingDataCompositionScheme()
• GetPerformingDataCompositionSettings()

The SpreadsheetDocumentValueReadingMode system enumeration is implemented. For the Read() method of the SpreadsheetDocument object, the ValueReadingMode parameter is implemented.

Support of pasting areas copied to the clipboard from Microsoft Excel and OpenOffice Calc documents is implemented.

The following objects can be serialized to or deserialized from JSON: primitive types, Array, FixedArray, Structure, FixedStructure, Map, and FixedMap.

The JSONReader and JSONWriter objects are implemented. The WriteJSON(), ReadJSON(), WriteJSONDate(), and ReadJSONDate() global context methods are implemented.

One could implement processing JSON data using 1C:Enterprise script tools.

You can store various data types in JSON format, which provides an alternative to other formats, such as XML.

For the standard OData interface, getting responses in JSON format is implemented.

Using JSON format minimizes the volume of data transferred between the client and the server.

If a logical expression was required for describing a selection field, you had to use a selection clause.

Logical expressions in the WHERE clause could be connected only by AND, OR, and NOT logical operators, and they could not be composite.

For the cluster, the Server errors threshold and Terminate corrupted processes properties are implemented.

For the IServerAgentConnection object, the SetClusterRecyclingErrorsCountTheshold() and SetClusterRecyclingKillProblemProcesses() methods are implemented.

For the rac utility, the --errors-count-threshold and --kill-problem-processes command-line options are implemented.

For the technological log, the ATTN event is implemented.

• For the TestedClientApplicationWindow, the StartPage property is implemented.
• Navigation between windows is implemented. For the TestedClientApplicationWindow object, the GotoStartPage(), GotoNextWindow(), GotoPreviousWindow(), and CloseUserMessagesPanel() methods are implemented.
• New options for testing managed form fields:
• Create an item. For the TestedFormField object, the Create() method is implemented.
• Cancel editing field data. For the TestedFormField object, the CancelEdit() method is implemented.
• Open a drop-down list, wait for drop-down list generation, and select a list item. For the TestedFormField object, the OpenDropList(), CloseDropList(), ExecuteChoiceFromDropList(), WaitForDropListGeneration(), and DropListIsOpen() methods are implemented.

For the DataCompositionUserSettings object, the Filter, Order, Selection, ConditionalAppearance, and Structure columns are implemented.

The report user settings form and the dynamic list user settings form are modified: instead of text boxes with the option to open editors (filter, order, and so on), tabs with tables are implemented to provide uniformity with the data composition schema editor in Designer.

The Settings command of the report form is displayed in the main form command bar.

The report and dynamic list user settings forms had a different layout.

The Settings command of the report form was available in the More menu.

The HTTPConnection object could only be used to call the GET, PUT, POST, and DELETE methods.

For the external session management web service, the onHibernateSession() and onWakeupSession() methods are implemented.

For external session management web service connection string, the optional parameters are implemented: tout sets an external session management web service response timeout, and wsver specifies the external session management web service interface version. The new features are only available if the wsver parameter is set to 2.

The full-text search index update operations are recorded to the tecnological log. In the tecnological log, the FTEXTCheck and FTEXTUpd events are implemented. In the technological log the ftextupd item is implemented.

For the QuerySchemaSources object, the Alias parameter of the Add() method is implemented.

You can use extensions to modify forms, create reports and data processors, and create new subsystems. You can apply a configuration extension both in 1C:Enterprise mode and in Designer. You can specify a custom extension set for each separated infobase area.

Support of Microsoft Information Services 10.0 web server is implemented.

Support of Microsoft Edge web browser is implemented, with the following limitations:

• Add-ins are not supported
• File system extension is not available
• Cryptography extension is not available

Microsoft Information Services 10.0 web server was not supported.

Microsoft Edge web browser was not supported.

Commands for specifying navigation and action panel settings are moved to the submenu to the right of the search field.

In the Taxi interface, pressing F10 opens the functions menu.

Commands for specifying navigation and action panel settings were displayed as links in the right part of the functions menu.

In the Taxi interface, pressing F10 opened the main menu.

To replace a splash screen in your applied solution, submit a request to 1C Company

In the Taxi or Forms in tabs interface mode, if the applied solution does not use modal calls, it does not require additional web browser setup.

The full-text search algorithm is optimized for scenarios where a user does not have access rights for some objects returned by the search.

The search for similar words might take a long time.

• Loading web client,. including scenarios with slow connection
• Opening forms
• General performance improvements in a variety of scenarios

The web client now uses Google Closure Compiler.

• A form has a large number of items.
• A form has a large number of attributes.
• The list of attributes and form items is significantly changed using 1C:Enterprise script.
• A large number of users are working with managed forms.

This type of restructuring is performed during the compressing of infobase tables (which is available from a Designer dialog box and as a command-line option), or during infobase verification with the chdfl utility with the Correct errors check box selected.

It is recommended that you always perform this optimization after you make any configuration changes (and the associated infobase restructuring) that result in database structure changes.

You can specify the external software in the Designer options dialog box.

Ready-to-use settings are available for the following external software:

• For Windows: Araxis Merge, KDiff3, TortoiseMerge, Perforce P4Merge, and DiffMerge
• For Linux: KDiff3 and Perforce P4Merge

You can specify settings for external software that is not on the list.

Only built-in Designer features were available for comparing and merging module texts.

• If the Title property of a managed form is not empty, its value is displayed in the window title in the preview area.
• Clicking a title if the preview area selects the entire form. Right-clicking the title opens the form context menu.

• Message headers
• Message body
• Message header parameter values, such as attachment file name.

Faster start of client applications in the file mode (when the background job manager is accessed during the startup).

• SSL is supported for POP3 and SMTP.
• Secure connection does not support checking server and client certificates.
• Descriptions of the InternetMail object methods that require IMAP connection now reflect that fact.
• The list of fields filled in the GetHeaders() method of the InternetMail object is provided.

The order of items in drop-down lists generated by the input by string feature with full-text search enabled matches the order of items returned by the full-text search algorithm.

The algorithm that generates presentations for Task objects in drop-down lists generated by the input by string feature is modified.

The order of items in drop-down lists generated by the input by string feature with full-text search enabled was not defined.

The algorithm that generated presentations for Task objects in drop-down lists generated by the input by string feature was different.

Improved 1C:Enterprise server stability during managed form operations.

To unbind a configuration from a repository, you can use the corresponding Designer command.

Improved representation of pictures in spreadsheet documents when viewed in the web client:

• Cells overlapped by a picture are not merged.
• Text and pictures in spreadsheet document cells can overlap each other.
• Eliminated issues that appeared when picture borders were close to cell borders.

Selecting pictures in spreadsheet documents was not supported. Spreadsheet documents had some picture-related issues.

Template pictures are used in applied solution development for the mobile platform.

Operations whose results were ignored are not performed.

• form button
• command bar button
• command bar
• separator

• form button
• command bar button
• command bar
• separator

This change is not implemented in 8.3.6 compatibility mode.

When a filter by time is applied to the event log (UnloadEventLog(), CopyEventLog(), or ClearEventLog() method), an event is included in the result even if the millisecond part of the actual event time exceeds the millisecond part of the time specified in the filter.

The behavior of the .lgd log is uniform with that of the .lgf log (regarding the event time presentation and filter functionality).

The NSSSecureConnection object will be unavailable for use in 1C:Enterprise script and in thin client HTTPS connection settings.

You can specify users on whose behalf the cluster manager (rmngr) and working processes (rphost) is started for each cluster on a given computer.

You can specify a custom cluster register directory for each cluster manager (rmngr) on a given computer.

The following parameters and parameter groups are implemented for the swpuser.ini file:

• the rmngr_user and rmngr_pass parameters
• the registry parameter
• the <PortName:> parameter group, which can contain all of the swpuser.ini file parameters.

• Operations with performance indicators. For the TestedApplication object, the GetAccumulatedPerformanceIndicators() and ClearAccumulatedPerformanceIndicators() methods are implemented.
• Support of the following managed form items: progress bar fields and track bar fields. The Tumbler radio button field type is now supported.
• Extended managed form table operations:
• Deletion mark management. For the TestedFormTable object, the SwitchRowDeleteMark() method is implemented.
• Setting row selection and getting selected rows. For the TestedFormTable object, the SelectAllRows() and GetSelectedRows() methods are implemented. For the GotoRow(), GotoFirstRow(), GotoLastRow(), GotoPreviousRow(), and GotoNextRow() methods, the Select parameter is implemented.
• Ordering table data. For the TestedFormTable object, the SetOrder() method is implemented.
• Expanding and collapsing managed form groups. For the TestedFormGroup object, the Collapse(), Expand(), and GetCurrentPage() methods are implemented.

The GetCurrentAreaText() method of the TestedFormField is declared obsolete. It is recommended that you use the GetAreaText() method of the TestedFormField object.

In the event of unexpected shutdown of a client application the user actions are automatically recorded to the user action log (provided that the user action log recording is enabled). A dump is also recorded to the dump directory.

The data processor that converts the log of user actions to a 1C:Enterprise script scenario is updated

URL2.

Progress bar fields, track bar fields, and the Tumbler radio button field type were not supported.

In the event of an unexpected shutdown of a client application, the user actions were not recorded to the user action log and the accumulated action log was lost.

• For style elements of Color type: the StyleColors system value set
• For style elements of Font type: the StyleFonts system value set
• For style elements of Border type: the StyleBorders system value set

If such elements are found, an error is displayed and the configuration is not saved.

Eliminated situations where two values with the same name were present in a single system value set whose values were connected to style elements.

This change is not implemented in 8.3.5 compatibility mode.

The documentation describes the actual platform behavior.

In the web client, the behavior is not changed, so it is now uniform with the behavior of thin and thick client applications.

The web client displayed a system dialog box for selecting an application to open the file.

In the web client execution of File constructor with a file name parameter no longer requires installing the file system extension.

The descriptions of File constructor without parameters and File.BeginInitialization() methods are removed from the documentation. The File.BeginInitialization() method is supported for compatibility purposes.

In the web client execution of File constructor with a file name parameter required installing the file system extension.

It is recommended that you build new installer packages (.msi and .sh) for Mozilla Firefox and create a new archive with version 40.* specified in the manifest. For support of earlier platform versions, also add legacy (.xpi) packages to the archive with version 31.0 specified in the manifest.

The add-in development technology documentation and examples are updated accordingly.

• URL

• FormattedStringURL

• Parameters.

• DataGetParameters.

• GetMostAcurateProvider().

• GetMostAccurateProvider().

The former name is supported for compatibility purposes.

• BeginUnload().

• BeginUnloading().

The former name is supported for compatibility purposes

• BeginCheckingExist().

• BeginCheckingExistence().

Template pictures were not supported.

The search is not morphological. Additional dictionaries and text extraction are not supported. The index is updated when the mobile platform is not performing any server calls or background jobs.

The change takes effect when you rebuild the mobile application using the new mobile platform and then republish the application to Google Play.

The OnChangeDisplaySettings event handler is implemented. The event occurs when the client application display parameters are changed.

The Width and Height properties of the ClientDisplayInformation object store the actual values (which depend on the screen orientation).

The platform could not detect the changes of display parameters.

The Width and Height properties of the ClientDisplayInformation object stored constant (canonical) values.

Camera control for photo shoots and video recording is implemented.

In the MultimediaTools object, for the PhotoSupported() and VideoRecordingSupported() methods, the CameraType parameter is implemented.

In the MultimediaTools object, for the MakePhoto() method, the CameraType, Resolutions, Quality, and Monochrome parameters are implemented. For the MakeVideoRecording() method of the MultimediaTools object, the CameraType and Quality parameters are implemented. For the MultimediaTools object, the GetSupportedCameraResolutions() method is implemented.

The documentation now contains the description of the mobile platform compatibility mode:

• It cannot be managed from Designer.
• It is not changed when an infobase is migrated to a new platform version.
• It is set during the infobase creation as its mobile platform version.
• It is changed to the new mobile platform version when an infobase is migrated to a new mobile platform version.

The documentation also describes the correspondence of PC platform versions and mobile platform versions.

The mobile platform compatibility mode was not described in the documentation.

Selecting Mobile device in the Use purposes configuration property does not change the Modality usage mode configuration property.

When the Mobile device value was selected in the Use purposes configuration property, a request to confirm the change of the Modality usage mode configuration property value was displayed (only if the change was required).

For the mobile platform, the DeliverableNotifications global context property, the DeliverableNotificationManager object, and the DeliverableNotification object are implemented.

For the PC platform, the DeliverableNotificationSend global context property, the

DeliverableNotificationSendManager object, and the DeliverableNotification object are implemented.

For mobile applications, the Push notifications and Local notifications permissions are implemented.

The mobile application builder supports building mobile applications that use notifications.

• HTTP operations
• POP3 and SMTP email operations

Support of IMAP email operations (including secure connection) is implemented.

Support of client certificates and certification authority center certificates stored in files is implemented.

In the mobile platform the FileClientCertificate, FileCertificationAuthorityCertificates, and OpenSSLSecureConnection objects are implemented, together with the corresponding properties of the HTTPConnection, InternetMailProfile, and InternetMail objects.

• Secure connection for HTTP, POP3, and SMTP operations
• IMAP email operations

Client certificate operations and authority center certificate operations.

The mobile platform supports secure operations with email and with other resources.

• The interface style is derived from the Taxi interface, but optimized for mobile devices to maximum extent.
• The interface appearance is revamped. This change affects the form design, primary colors, and the look of form items. The interface now matches the modern mobile interface standards.
• The main application menu is revised.
• The main section command interface is revised.
• Navigation options are revised.
• A form and main section command interface can be both present on the start page.
• Form command bar placement and generation rules are modified.
• The option to display a form navigation panel is implemented.
• The text input field is optimized for touch screen devices.
• The form title is no longer duplicated in the form body.
• Users have the option to create a list item when selecting a value from a drop-down list.
• Form item context menus are supported.
• Fields that require filling are not highlighted.
• New display options for page groups are implemented.
• Search in dynamic lists is implemented. It is based on full-text search.
• A dynamic list can be sorted by tapping a column header.
• Table operations are significantly revised, including scrolling, table item selection, and row rearrangement.
• In managed form tables the multiple selection option is implemented.
• The option to update a list by pulling the list down or up when the first or last row is on the screen ("pull to refresh") is implemented.
• The approach to handling the current row of a managed form table is changed.
• A managed form table is automatically scaled to fit displayed data by height, unless it displays dynamic list data.
• Spreadsheet documents can be scaled using gestures.
• User message appearance is revised.
• Subsystems are supported (and available in the interface).
• The radio button field and the track bar field are implemented.
• For a managed form table the RefreshRequestProcessing event is implemented. For the FormPagesRepresentation system enumeration the Swipe value is implemented. For a managed form table the RefreshRequest property is implemented.
• The Move up/Move down standard table commands are removed.
• For a managed form command the Use current row and Associated table properties are implemented (not available from 1C:Enterprise script). For a managed form button the Representation in context menu property is implemented (not available from 1C:Enterprise script).
• Many other features are implemented. The full list of changes is quite long, therefore it is recommended that you read the chapter about mobile application development in 1C:Enterprise Developer Guide.

The mobile application builder help describes how to connect to Google Play Market.

Mobile applications required manual publishing.

The DynamicList.SettingsComposer property is now available on the mobile platform.

The following objects are implemented: DataCompositionSettingsComposer, DataCompositionUserSettings, and DataCompositionSettings, as well as their constructors and methods. Their methods are not available on the mobile platform.

The DataCompositionUserSettingsItemCollection object is implemented.

• Configuration window
• Configuration object selection dialog box
• Type editing dialog box
• Object properties window

For the Subsystem configuration object, a quick filter is implemented in the configuration window. The filter is available from the Subsystem objects context menu command of the object.

In the configuration window, you can set a quick filter for configuration repository objects locked by the current user.

Only filtering by objects included in subsystems was available.

The StartPageForms object is implemented. For the StartPageSettings object, the GetForms() and SetForms() methods and the default constructor are implemented.

The global context method RefreshInterface() rebuilds the start page (desktop) based on the settings from the system settings storage.

1C:Enterprise script did not provide tools for managing form contents and positions.

• Typing in the text box
• Copying text from the clipboard
• Running Undo or Redo command
• Canceling input by pressing ESC

The event occurs before the AutoComplete event.

• Find all usage instances of an export variable, procedure, or function in the entire configuration.
• Convert a selected code fragment to a separate procedure or function.
• Rename a local variable, procedure, or function.
• Insert a comment block that describes the function or procedure purpose, parameters, and return value before the function or procedure declaration.
• Convert modal calls to nonmodal calls (in a limited set of cases).
• Convert procedures or functions to types that can be used in sequences of asynchronous calls.
• Convert a selected code fragment to a separate procedure or function suitable for using in sequences of asynchronous calls.
• Find all usage instances of modal methods in the specified module.
• Convert all modal methods that are found to their asynchronous analogs.
• Create notification processing events for methods that lock the interface.

Commands that perform these functions are located in the Refactor submenu of the module text editor context menu and in the Configuration section of the Designer main menu.

The /url startup option is implemented for the launcher, thin client, and thick client.

Users could only follow external links when they accessed the infobase using the web client.

Local data cache is implemented for configuration repositories. You can manage the size and location of local and global repository caches using the configuration repository administration settings dialog box or cfgrepo.conf configuration files. These files are located in the cfgrepo subdirectory of the infobase service files directory (for the local cache) or in the configuration repository directory (for the global cache).

The following features are implemented for batch Designer startup mode:

• Clearing the global configuration repository cache (the /ConfigurationRepositoryClearGlobalCache command-line option)
• Clearing the local configuration repository cache (the /ConfigurationRepositoryClearLocalCache command-line option)

Editing the size and location of the global configuration repository cache was not available. The local cache for configuration repository data was not available.

You can manage the size and location of configuration repository data cache.

For automatically created forms that contain tables linked to dynamic lists, the set of items related to search in dynamic lists is modified (together with their appearance). The search dialog box layout is modified.

The new FormItemAddition managed form item stores additional properties of form items.

Extensions of form items intended for displaying a search string, a view status, and a search control are implemented.

For the FormTable managed form item, the predefined items SearchString, ViewStatus, and SearchControl, and also properties SearchStringLocation, ViewStatusLocation, and SearchControlLocation are implemented.

The search history is stored in the system settings storage with the following key: Common/TableSearchHistory/<Form name>.<Table name>.

The SearchControl picture is added to the picture library.

Publishing HTTP services is similar to publishing web services.

To access HTTP services, use URLs of the following format: http://<host name>/<base name>/hs/<resourсe identifier>. You can create HTTP services in the Common/HTTP services branch of the configuration tree.

The following objects are implemented: HTTPServices, HTTPService, HTTPServiceRequest, and HTTPServiceResponse.

Only access to web services implemented in the applied solution was available.

• Simpler implementation.
• Less amounts of data transferred.
• Less computing power is required to parse a response.

A different usage model (RESTful services).

For the ISessionInfo object, the following properties are implemented: Hibernate, PassiveSessionHibernateTime, and HibernateSessionTerminateTime. New global context methods are implemented: SetPassiveSessionHibernateTime(), GetPassiveSessionHibernateTime(), SetHibernateSessionTerminateTime(), and GetHibernateSessionTerminateTime().

The hibernation timeout and the timeout for closing hibernated sessions can be set in Designer, in the infobase parameters dialog box.

If a client application was inactive for 20 minutes, the session was closed.

This feature is intended for integration with other applications, external sources should not be used as applied solution data storages.

External data source table data was read-only.

The following pictures are added to the picture library:

Rename, Attribute, Dimension, Resource, NestedTable, QueryWizardShowChangesTables, QueryWizardCreateNestedQuery, QueryWizardCreateTempTableDescription, QueryWizardReplaceTable, QueryWizardTableParameters, QueryWizardCreateTempTableDropQuery

QueryWizardTempTableDescription, QueryWizardGroupTempTables, QueryWizardTempTable, QueryWizardNestedQuery, and CustomExpression.

You can modify queries from 1C:Enterprise script without analyzing the query text.

For the SpreadsheetDocumentRange object, the following properties are implemented: Picture, PictureSize, PictureHorizontalAlign, PictureVerticalAlign, TextPositionRelativeToPicture, and PictureParameter.

The _$Data$_.TotalsPeriodUpdate event is used for compatibility purposes.

Both data processors were written using the Russian variant of 1C:Enterprise script.

An external data processor intended for deleting descriptions of standard attributes with default values from XML dump files is implemented.

The data processor can be used only with files dumped by 1C:Enterprise version 8.3.5. You have to use it once before loading the dumped files back to the configuration.

In the logcfg.xml file, the externaldump attribute of the dump element is implemented.

The dumper.exe utility, which is now included in the platform delivery kit, is implemented.

If EnableCheckModal is not used, modal methods are executed without any warnings or exceptions.

If EnableCheckModal is used, executing a modal method generates a warning or an exception (depending on the Modality usage mode configuration property value).

When an applied solution is started from Designer, the EnableCheckModal parameter is automatically added to the applied solution command line (this behavior cannot be disabled).

The web client behavior is not modified: the command-line parameter is not used. The web client always generates a warning or an exception (depending on the Modality usage mode configuration property value) when modal methods are executed.

While the client application was being updated, the progress of downloading the distribution kit was not displayed.

• In the Forms in separate windows mode, it is opened in a separate window.
• In the Forms in tabs mode, it is opened in a tab.
• In the Taxi mode, it is opened in the main window working area.
• If help is opened from a form that locks the entire interface, it is opened on top of all windows and locks the entire interface.
• If help is opened from a modal form, it is opened in a modal form.

The help command bar is modified.

The search is started either when the focus leaves the search text box or when the user clicks Find.

The help command bar had different content.

The search started while the search expression was still being typed (during a pause in the typing).

In separated infobases that ran in the file mode, query execution lacked efficiency.

The form wizard allows adding predefined data name fields to forms.

The form wizard did not allow adding predefined data name fields to forms.

If a register affecting a sequence is included in separator content and a document included in a sequence is not included in the content of this separator, the separator is ignored when sequence boundaries are updated in 1C:Enterprise mode.

• Setting a session parameter
• Single call of the PutToTempStorage() method
• Single call of the PutFile() or PutFiles() method

An attempt to transfer more than 4GB leads to an unrecoverable error.

The error can be handled using the Try...Except syntax.

In a text box that is in the "choice from the list" mode and displays an empty reference, clicking the Cancel button is ignored.

• The GotoURL() script method
• Following a navigation link from the Go to link dialog box (including the scenario when the link is pasted from the clipboard)
• Adding a link to Favorites from the Go to link dialog box

During XDTO serialization of spreadsheet documents and the following deserialization, text box settings were lost.

• In the Evaluate expression dialog box and in the Immediate window, expressions are not calculated twice in the following cases:
• Opening a value that has properties
• Viewing a property as a collection of values in a separate window
• Viewing property values in a separate window intended for viewing a collection
• Viewing a string value in a separate window

• Opening a value that has properties
• Viewing a property as a collection of values in a separate window
• Viewing property values in a separate window intended for viewing a collection
• Viewing a string value in a separate window

You can perform selective comparison of form modules without building a form comparison report. The Form (module) command is added to the following context menus: Perform selective comparison with the repository object, Perform selective comparison with the configuration object, and Perform selective comparison of object versions.

Improved usability of selective comparison. Comparison of form modules is now a separate command.

• Clicking the drop-down list button
• Attempting to create an item from the drop-down list
• Attempting to open a choice list
• Starting text input

If the lock cannot be set, the action is not performed.

• Attempting to open a choice list
• Starting text input

Dynamic list settings are dumped to a single element, which has the data composition schema settings format.

Managed forms dumped using the previous platform versions cannot be loaded by the latest platform version.

The conditional appearance with Group usage area is applied to an aria of vertical template that contains values of displayed fields.

This change is not implemented in 8.3.4 compatibility mode.

The log location is not changed. The SQLite log format is the default format for new infobases. The performance of accessing event log data is improved.

Existing event logs can be converted to a new format. Conversion back to the legacy format is not supported.

The CopyEventLog() and ClearEventLog() methods are implemented.

The event log stores time in UTC format. The standard event log viewer supports new log file format (.lgd).

In the standard event log viewer form the command for viewing a log stored in a file is renamed to More - View from file.

In the standard event log viewer form the command for viewing a log stored in a file had the following name: More - Load from file.

Better name for the command for viewing a log stored in a file.

You can terminate the reducing of event log size by pressing Ctrl+Break in Designer or by closing the session using administrative tools (as a result, a part of records is deleted, and the rest are not deleted).

Reducing the event log size could not be terminated.

This operation can be terminated if needed.

For sessions that use separators, the following features are implemented:

• Changes can be registered for an empty record set that is subordinate to a recorder. If any of the separators required for the record set are not used in a session, the separator values are obtained from the corresponding recorder fields.
• If the full set of separator values cannot be obtained using a recorder available in the memory, an error is generated and the change registration is stopped.

For sessions that used separators, registering changes for empty record sets that were subordinate to recorders was not available.

• You can specify data areas that will be searched for references or where objects will be deleted.
• You can include configuration objects to (or exclude configuration objects from) search or deletion.

For value tables that are returned by the FindByRef() and DeleteObjects() methods, a new column is implemented. It contains separator values that define the data area where the found object or the object that prevents deletion of another object is located.

The DeleteObjects() method returns a value of Number type, which stores the number of deleted objects.

The value tables that were returned by the FindByRef() and DeleteObjects() methods did not contain columns with separator values.

The DeleteObjects() method was a procedure.

During license activation by phone, each Licensing Center response line is entered in a single text box, which contains an input mask).

Pressing Tab switches between these text boxes.

The license registration page contains the descriptions of activation options for 5-, 10-, and 20-user licenses.

Extended error diagnostics during license activation is implemented.

During license activation by phone, the license activation dialog box had 5 text boxes for entering each Licensing Center response line.

Pressing Tab switched between the text boxes and response lines.

Help for various license activation methods was not available directly in the dialog box.

Some license activation error messages had complicated descriptions that might not be clear to users.

Improved usability of entering the response from the Licensing Center during license activation by phone.

The error messages are clearer to users.

To open the drop-down list, press Ctrl+Down Arrow.

If changing the Use purposes property requires modification of Modality usage mode and Interface compatibility mode configuration property values, the user is prompted to confirm the change.

• The Interface compatibility mode property was set to Version 8.2.
• The Modality usage mode property was set to Use.

A user without administrative rights that does not have write access to the directory where license files for all computer users are located still can activate a software license.

In the thin client, text in managed form table cells better fits the cell height.

The ellipsis was not added to the end of the last line.

In the thin client, sometimes text in managed form table cells did not fit the cell height well, a redundant empty line was added to the bottom of the cell.

• The dump was created in the file mode .
• 1C:Enterprise version 8.3.4 was used for dumping.
• Filled aggregates of turnover accumulation registers were available in the infobase.

In some scenarios, the aggregates of turnover accumulation registers are cleared after the loading.

• The dump was created in the file mode .
• 1C:Enterprise version 8.3.4 was used for dumping.
• Filled aggregates of turnover accumulation registers were available in the infobase.

• In managed form text box drop-down lists
• In favorites
• In history
• In dynamic lists
• In the full-text search form

• If any of the pictures have height more than 48 pixels, they are scaled to the height of 48 pixels.
• If all of the pictures have height less that 48 pixels, the section panel height is calculated based on the maximum picture height, while smaller pictures are centered at their respective positions.

Improved Google Chrome 37 web browser support.

• Search in the 1C:Enterprise installation directory (the InstalledLocation property in 1cestart.cfg and 1cescmn.cfg files)
• Search in the directories specified as locations for distribution files of new versions (the DistributiveLocation property in 1cestart.cfg and 1cescmn.cfg files, and the CommonCfgLocation property in the 1cestart.cfg file)
• Search by the URL that is returned in the server exception about the mismatch of client and server application versions (the PublishDistributiveLocation parameter in the conf.cfg file and the pubdst attribute of the ws tag in the default.vrd file)
• Search using Internet services for getting the client application distribution kit

• Search in the 1C:Enterprise installation directory (the InstalledLocation property in 1cestart.cfg and 1cescmn.cfg files)
• Search in the directories specified as locations for distribution files of new versions (the DistributiveLocation property in 1cestart.cfg and 1cescmn.cfg files, and the CommonCfgLocation property in the 1cestart.cfg file)
• Search by the URL, that is returned in the server exception about the mismatch of client and server application versions (the PublishDistributiveLocation parameter in the conf.cfg file and the pubdst attribute of the ws tag in the default.vrd file)
• Search using Internet services for getting the client application distribution kit

In tables that store the register change records, fields describing dimensions of UUID type have UUID type.

In tables that stored the register change records, fields describing dimensions of UUID type had BinaryData type.

This change is not implemented in 8.3.4 compatibility mode.

• Search by beginning of the string is performed and the first 10 results are added to the list.
• If the list contains less than 10 items, search by substring is performed and its results are added to the list until it contains 10 items.
• If the list still contains less than 10 items, results of search by other fields available for search during input by string are added to the list.

This change is not implemented in 8.3.4 compatibility mode.

This change is not implemented in 8.3.4 compatibility mode.

The feature is implemented for thin and web clients.

As a result, a message about insufficient access rights might be displayed in situations where it was not displayed earlier.

New extension versions perform all file and cryptography operations asynchronously (using notifications).

To be able to use 1C:Enterprise extensions and browser extensions, you are required to install a dedicated web browser extension. The web client prompts you to install that extension once you attempt to enable a browser extension.

On the client side, add-ins, the file system extension, and the cryptography extension run asynchronously. Synchronous add-in, file system extension, and cryptography extension operations are supported on the client side for compatibility purposes. Refactoring applied solutions, including those that have add-ins, is required to support synchronous operations:

• change method calls to calls of BeginCalling<MethodName>() asynchronous methods,
• change reading property values to calls of BeginGetting<PropertyName>() asynchronous method,
• change setting property values to calls of BeginSetting<PropertyName>() asynchronous method.

Refactoring add-ins is not required. The platform automatically adds prefixes and asynchronous behavior support to add-in methods. The SynchronousExtensionAndAddInCallUseMode configuration property is implemented. If the property is set to Do not use, NPAPI-based extensions are not loaded in the web client and, as a result, synchronous methods cannot be executed. In other cases, an attempt to load an NPAPI-based extension is performed. If an extension is successfully loaded, both synchronous and asynchronous methods can be executed. For more information, see the documentation.

Previous extension versions can be uninstalled in a regular way.

Improved add-in development technology (read more).

The following global context methods are implemented: BeginAttachingCryptoExtension(), BeginAttachingFileSystemExtension(), BeginAttachingAddIn(), BeginCopyingFile(), BeginMovingFile(), BeginDeletingFiles(), BeginFindingFiles(), BeginCreatingDirectory(), BeginGettingTempFilesDir(), BeginGettingDocumentsDir(), BeginGettingUserDataWorkDir(), BeginGettingFiles(), BeginPuttingFiles(), BeginRequestingUserPermission(), and BeginRunningApplication().

For the CryptoManager object, a constructor without parameters is implemented, and also the following methods: BeginInitialization(), BeginEncrypting(), BeginSigning(), BeginGettingCryptoModuleInformation(), BeginGettingCertificatesFromSignature(), BeginGettingCertificateStore(), BeginVerifyingSignature(), BeginCheckingCertificate(), and BeginDecrypting().

For the CryptoCertificate object, a constructor without parameters is implemented, and also the following methods: BeginInitialization() and BeginUnload.

For the CryptoTools object, the BeginGettingCryptoModuleInformation() method is implemented.

For the CryptoCertificateStore object, the BeginAdding(), BeginFindingByThumbprint(), BeginFindingBySerialNumber(), BeginFindingBySubject(), BeginGettingAll(), and BeginDeleting() methods are implemented.

For the FileDialog object, the Show() method is implemented.

For the File object, a constructor without parameters is implemented, and also the following methods: BeginInitialization(), BeginGettingModificationTime(), BeginGettingHidden(), BeginGettingReadOnly(), BeginGettingSize(), BeginGettingModificationUniversalTime(), BeginCheckingExist(), BeginSettingModificationTime(), BeginSettingHidden(), BeginSettingReadOnly(), BeginSettingModificationUniversalTime(), BeginCheckingIsDirectory(), and BeginCheckingIsFile().

You can use the refactoring feature to convert synchronous extension and add-in methods to their asynchronous counterparts. New refactoring settings are available.

The platform supports asynchronous add-in, cryptography extension, and file system extension operations in the web client, which ensures Google Chrome support.

Important! Support of synchronous operations in Google Chrome is disabled by default since version 42 (April 2015) and discontinued since version 45 (September 2015). Therefore, synchronous 1C:Enterprise script methods will stop working in Google Chrome even if you use a platform version that supports them.

The add-in development technology does not support Mozilla Firefox web browser versions 30.0 or earlier.

Adapters for Mozilla Firefox versions 30.0 or earlier are removed.

The add-in development technology supported Mozilla Firefox web browser versions 30.0 and earlier.

The add-in development technology does not support older versions of Mozilla Firefox web browser (30.0 or later).

• Street
• House

• PrimaryAddressString
• AdditionalAddressString

• _$Data$_.TotalsMinPeriodUpdate
• Data. Modify totals period

• Data. Modify minimum calculated totals period
• Data. Modify maximum calculated totals period

• Functional options and functional option parameters.
• Roles (limited support). Role management of item visibility and availability for forms and for the command interface.
• A role setting for form visibility on the start page. After functional options and roles are applied, the first form from the list of available forms is displayed.
• Infobase users (limited support).

Limitations of the implemented features are described in the documentation.

• Send and receive emails using the built-in mail client of a mobile device. The MailTools object is implemented.
• Send and receive SMS and MMS messages. The SMSMessage object is implemented.
• Dial phone numbers. The TelephonyTools object is implemented.
• Access the call history filterred by call type(incoming, outgoing, or missed).The CallLog object is implemented.

The limitations of the telephony tools on supported operating systems are listed in documentation.

Access to the call history and sent email messages from the built-in email client was not available.

• Multimedia
• Geolocation
• Reading and writing contacts
• Reading and writing calendar events
• Access to telephony

The Mobile application builder uses the specified permissions.

For the MultimediaTools object, the following methods are implemented: BarcodeScannerScanning(), ShowBarcodeScanning(), and CloseBarcodeScanning().

• The temporary user directory is no longer used for building. An explicitly defined directory is used instead, the path to this directory must contain ASCII characters only.
• The build date of each mobile application is recorded (and displayed).
• You can save graphic assets and mobile configurations to the hard disk.
• When the mobile platform version 8.3.5 is loaded, the version number is obtained automatically from the version.txt file, which is included in the mobile platform distribution kit (mobile.zip).
• Android SDK version 17 or later is required for building mobile applications for Android.
• For files that contain graphic assets, the check whether the file contains a full set is implemented (the check is also performed when the file is loaded).
• Files that contain graphic assets support icons for devices with high density screens (size 144 x 144 pixels, file name Android\icon-144x144.png).
• Other improvements are implemented.

• The temporary user directory was used for building mobile applications. The mobile application could not be built for Android if the name of the user on whose behalf the build was performed contained non-ASCII characters.
• Mobile application build dates were not recorded.
• Saving graphic assets and mobile configurations to the hard disk was not available.
• Android SDK version 17 was required for building mobile applications for Android, other versions were not supported.
• The mobile platform did not support icons for Android devices with high density screens.

The MobileDeviceApplicationLaunch and MobileDeviceApplicationLaunchExtrasData objects are implemented.

This feature is only available on operating systems of Android family.

• splash screens: 750x1334, 2208x1242, and 1242x2208
• icons: 87x87 and 180x180

In the mobile application builder, support of graphical assets for iPhone 6 and iPhone 6 Plus devices is implemented.

• Selecting all entries of the identifier marked by cursor location
• Selecting all entries of an identifier marked by a double-click
• Selecting pairs of opening and closing 1C:Enterprise script clauses (including brackets): Procedure ... EndProcedure, If ... EndIf, and so on

Selecting identifiers is disabled by default. To use this feature, enable it in Designer options dialog box. Selecting the search expression is available in Designer, thick client, and thin client.

In the ExternalDataSourceConnectionParameters object, the MySQL value is implemented for the DBMS property.

In the technological log, the DBMySQL property is implemented for the DBMS property of the EDS event..

The objects ClientApplicationInterfaceContentSettings, ClientApplicationInterfaceContentSettingsGroup, and ClientApplicationInterfaceContentSettingsItem are implemented. Calling the RefreshInterface() global context method rebuilds interface panels according to the settings from the system storage.

For the ClientApplicationInterfaceSettings object, a constructor and methods GetContent() and SetContent() are implemented.

Interface management from 1C:Enterprise script was not supported.

This property modifes the scale of all forms in the applied solution for a specific user.

You can modify both a scale of a single form (which is not yet redesigned for Taxi interface mode) and the scale of the entire application (you might need this if the applied solution runs on a computer with a low-resolution or small-sized display).

The scale of a single form is specified in Designer, while the scale for the entire application is specified in the settings for a specific user.

The standard parameter AdditionalParameters of Structure type is implemented for managed form extensions of objects, catalogs, documents, charts of characteristic types, business processes, tasks, and dynamic lists.

For dynamic list table extensions, the AdditionalCreateParameters property of FixedStructure type is implemented.

The ChoiceHistoryOnInput property of configuration objects, configuration object attributes, and form items defines whether the history is enabled.

• Creating a configuration repository (/ConfigurationRepositoryCreate command-line option)
• Creating a configuration repository user(/ConfigurationRepositoryAddUser command-line option)
• Copying users from another configuration repository (/ConfigurationRepositoryCopyUsers command-line option)

• Designer (except for sessions intended for infobase creation)
• Thin client
• Web client
• Thick client
• External connection

Licenses can be activated for both 32-bit and 64-bit server versions. The server cluster that uses this license type can only contain a single working server.

1C:Enterprise server did not have limitations for the number of simultaneously connected users.

For the thin client, the /HttpsForceSSLv3 command-line option is implemented. It forces the system not to use the TLS protocol (if the connection is established using a web server), even if the web server supports this protocol.

• mn - Mongolian
• mn_Cyrl - Mongolian (Cyrillic)
• mn_MN - Mongolian (Mongolian)
• mn_Mong - Mongolian (Traditional Mongolian)
• mn_Mong_CN - Mongolian (Traditional Mongolian, PRC)

Improved dump generation algorithm in the event of unexpected shutdown. The dump is generated even if a new exception occurs while the first exception is being processed.

• Select font dialog box
• Search and replace dialog box in spreadsheet documents
• Performance indicator dialog box

In all managed system forms, the Help button is located in the command bar, instead of the More (All actions) menu.

The execution time is reduced for the following configuration check operations:

• Executing the ConfigurationChanged() method
• Starting a 1C:Enterprise client

Reading changes using the ReadChanges() method of an exchange plan manager.

In the client/server mode, the performance of the numbering service with a large number of prefixes is improved.

In the client/server mode, the performance of the numbering service with a large number of prefixes lacked efficiency.

• Open a configuration bound to the repository
• Connect to the repository
• Store objects to the repository
• Update a configuration from the repository, retrieve objects, and cancel object locks
• Store objects to the repository while multiple users are working simultaneously

In sessions that do not use separators, when data is being written or deleted, managed locks are set not only by reference and explicitly specified fields, but also by common attributes that serve as separators and include the object being written or deleted.

The common attributes that are not separators can be used in the DataLockFields configuration object property.

The DataLockFields list of attributes cannot contain common attributes that serve as separators in the Independently and simultaneously mode. You can specify such attributes as names for lock spaces of DataLock objects. If the separator value used in the DataLock object differs from the separator value used in the session, an exception is raised.

These changes are implemented for the following object types:

• Catalogs
• Documents
• Charts of characteristic types
• Charts of accounts
• Charts of calculation types
• Exchange plans
• Business processes
• Tasks
• Constants

The common attributes that were not separators could not be used in the DataLockFields configuration object property. Such common attributes could not be used as names for lock spaces of DataLock objects.

In the configuration repository, improved usability of repeated object storing operations related to a single task, such as step-by-step implementation of a single feature.

The user action log conversion data processor includes the option that defines how the search for form items is performed: by presentation or by name.

The user action log conversion data processor only supported search for form items by item presentation.

When the current section command panel orientation is vertical, its title is not displayed. The presentation of current section command panel is changed to current section function panel.

If the current section command panel orientation was vertical, its title was displayed.

Selective history is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, objects included in exchange plans, styles, main section working areas, flowcharts, forms, help pages, predefined items, command interface fragments, and role rights. To view the selective history, right-click anywhere in any of the repository dialog boxes or in the configuration comparison window, and then click View selective history.

In the Filter repository versions dialog box, filter by properties of selected configuration objects is added. Viewing selective history is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.

• You can manage execution of background jobs in file mode (the allowexecutescheduledjobs attribute of the ws tag).
• You can specify whether web services are published by default (the pointEnableCommon attribute of the ws tag).

• ExternalDataSource.< Source name>.Table.<Table function name>(<Parameter 1>,...,< Parameter N>)
• ExternalDataSource.<Source name>.<Function name>< Parameter 1>,...,< Parameter N>

You can call functions using the object model. This can be performed with either external data source managers or external data source table managers.

In the picture library, the ExternalDataSourceFunction is implemented.

The external data source functionality is extended.

New objects are automatically created in the target configuration.

For information registers with Enable totals for retieving slice first or Enable totals for retrieving slice last property enabled, the Active and LineNumber fields are removed from the list of fields of information register slice first/last virtual tables.

If Enable totals for retieving slice first or Enable totals for retrieving slice last property is disabled, the Active and LineNumber fields are included in the slice first/last virtual tables.

The check is performed during the configuration check, and an error message is displayed if any field does not comply with the limitations.

During the configuration check, the check for managed locks by attributes of these types was not performed.

Improved quality control during configuration development.

In both cases, only functional options without parameters are taken into account.

In 1C:Enterprise version 8.3, the main form attribute of Object type was disabled if a functional option disabled the corresponding configuration object. All functional options were taken into account.

In the previous 1C:Enterpise versions, the main form attribute of DynamicList type was disabled if a functional option disabled the configuration object that was used as a main table of the dynamic list. All functional options were taken into account.

• Editing a form changes a functional option parameter (directly or indirectly).
• The new parameter value causes the functional option to disable the configuration object that is the main form attribute.
• The disabled configuration object clears the entire object form.

• When a text box is activated, a drop-down list is not opened.
• For the DropListButton property of the managed form field extension for a text box, the Auto value is interpreted as False.
• For the ChoiceButtonRepresentation property of the managed form field extension for a text box, the Auto value is interpreted as ShowInInputField.
• For the ChoiceButton property of the managed form field extension for a text box, the Auto value is interpreted as in 1C:Enterprise version 8.3.2.
• Clicking the Down Arrow button opens a choice form, not a drop-down list.

• ListSelWidth

• DropListWidth

• Choose()

• Select()

The mobile platform distribution kit contains the following files:

• 1cem-arm.apk, the developer's mobile platform for ARM architecture
• cem-x86.apk, the developer's mobile platform for x86 architecture
• prjandroid-arm.zip, the mobile platform for building mobile applications (for ARM architecture)
• prjandroid-x86.zip, the mobile platform for building mobile applications (for x86 architecture)

• Storing mobile configurations
• Storing mobile platforms (starting from version 8.3.4)
• Storing graphic assets
• Building mobile applications
• Storing the built mobile applications

Mobile application builder can build mobile applications for Android x86 operating systems.

It can also perform full building of mobile applications for iOS using a Mac computer with Xcode installed.

The configuration is delivered together with the mobile platform distribution kit. The data processor used for building mobile applications is removed from the mobile platform distribution kit.

Building can be performed using any Android SDK version.