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