1C:Enterprise 8.3.5. New functionality and changes.

Version 8.3.5 includes known bug fixes and functionality modifications.


New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.4 is added to the list of available values of the Compatibility mode property. Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, and 8.3.3. In version 8.3.5 you can run configurations created in version 8.3.4 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.5 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.4 for working with the infobase even after the transition to version 8.3.5. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Development tools.
In Designer, new icons for external data source tables and cubes are implemented.Pictures for external data source tables and cubes were different.Icons for external data source tables and cubes are uniform with other platform pictures.
Development tools.
In Designer, you can filter objects by parts of names, synonyms, comments, or presentations. The filter is available in the following windows:
  • 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.

This feature was not provided.

Only filtering by objects included in subsystems was available.

Improved usability for developers.
Interface.
1C:Enterprise script provides tools for managing start page (desktop) form contents and positions.

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.

The StartPageSettings object stored the differences between the start page (desktop) settings of the client application and the settings specified in Designer.

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

You can manage contents and positions of the client application start page (desktop) forms using 1C:Enterprise script.
Administration tools.
For the Purpose column of value table returned by the GetDBStorageStructureInfo() method, new purposes are specified. The full list of database table purposes is available in the description of the GetDBStorageStructureInfo() method in the Syntax Assistant.The list of table purposes did not fully describe the current database schema.The purposes of database scheme tables are described more clearly.
Data exchange.
For exchange plans, the ThisNode standard attribute is implemented. It specifies whether the exchange plane node describes the current infobase.

For the ExchangePlanObject object, the DataExchange property is implemented. Only the Load property can be used in this property. The DataExchange property is used for disabling the uniqueness check of the ThisNode item when exchange plan items are edited or deleted.

This change is not implemented in 8.3.4 compatibility mode.

The ThisNode standard attribute was not available in exchange plans. Replacing the exchange plan node that described the current infobase was impossible.

The ExchangePlanObject object did not have the DataExchange property.

You can define ThisNode items in a distributed infobase in a session that does not use separators.

You can replace the data item that describes the current infobase in the exchange plan.

Managed forms.
For managed form text boxes, the EditTextChange event is implemented. This event occurs when one of the following actions modifies the text box content:
  • 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.

There was no event that occurred when text box content was modified. Actions triggered by this modification could be performed in the AutoComplete event handler (with limitations).In managed forms, complete implementation of the following scenario is available: text being typed in a text box is used as a filter parameter in the linked dynamic list.
Development tools.
New features in the module editor:
  • 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.

These features were not provided.Improved efficiency of routine operations performed by developers.
Managed forms.
In text boxes that display values of StandardBeginningDate type, in the date input mode, the AutoComplete (on value input) and TextEditEnd (on generating a value based on the input string) event handlers are implemented.

This change is not implemented in 8.3.4 compatibility mode.

In text boxes that display values of StandardBeginningDate type, in the date input mode, the AutoComplete (on value input) and TextEditEnd (on generating a value based on the input string) event handlers were not implemented.The behavior of text boxes linked to values of StandardBeginningDate type in the date input mode is identical to behavior of text boxes linked to values of Date type.
Client application.
The option to follow a navigation link during client application startup is implemented, with the navigation link passed as a parameter. This feature is implemented for the 1C:Enterprise launcher, thin and thick clients, the GotoURL() method, the standard full-text search form, and the new Go to link command in the startup window. Only external navigation links (which contain infobase connection settings) are supported. When following a link, the platform attempts to use running client application instances connected to the infobase specified in the navigation link. In 8.3.4 version compatibility mode, the GotoURL() method is not modified.

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

This feature was not provided.

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

Simplified access to infobase data if a link to this data is provided by third-party tools, such as email.
Internet-enabled functionality.
For the InternetMailMessage object, the GetSourceData(), SetSourceData(), and GetSourceText() methods are implemented. These methods are intended for getting original email messages without changing the encoding and processing source texts of messages whose encoding was changed.This feature was not provided.You can save email messages to files and load them from files, provided that they comply with RFC 822 URL9, and you can also perform custom processing of email message source texts.
Data display.
Charts.
Animated charts are implemented. The Animation property is implemented for the Chart object. The ChartsViewSettings object is implemented. The chart display settings are stored in the system settings storage.

This change is not implemented in 8.3.4 compatibility mode.

This feature was not provided.More chart display options are available.
Web services and HTTP services.
Data exchange.
Database operations.
Web client and web service publishing tools.
1C:Enterprise infobase data can be retrieved and modified using the OData protocol (read more) v3 (read more). The following data presentation is supported: atom-xml.

Enabling this feature does not require modification of applied solution, it is performed using a web server publication.

The enableStandardOData attribute is implemented for <point> tag in the default.vrd file.

In 8.3.4 version compatibility mode, all configuration objects that support OData protocol are available through this interface. If the compatibility mode is disabled, the access to objects is managed using the SetStandardODataInterfaceContent() method.

Universal access to 1C:Enterprise infobase data was only available on Windows operating systems and was based on COM/OLE features. It was not available on Linux. The option to access data using web services implemented in applied solutions was also available.Extended integration features for 1C:Enterprise data, including data access from external Linux systems, which does not require modification of applied solutions .
Configuration repositories.
Optimized selective comparison of forms, access rights, and command interface fragments in scenarios where the configuration repository is located on a network drive or on a repository server.

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)
The selective comparison of forms, access rights, and command interface fragments lacked efficiency if the configuration repository was located on a network drive or on a repository server.

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

Selective comparison and some other configuration repository features are optimized.

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

Dynamic lists.
Extended search capabilities in tables that display dynamic lists. A standalone search string box that provides full-text search is implemented. Search by current cell value is available. The search history is implemented. The current search state is clearly visible. The search result includes items that have search words located both in a single column and in different columns. In each column, search by a single value is available (the Find in search results option is not supported).

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.

Search in tables was performed using the search dialog box. The option to search a column by multiple values (the Find in search results check box) was available. The search dialog box had a different layout. There was no simple way to determine whether the search is applied to a table (except for checking the availability of the Cancel search button if it was present on the command bar).The search in managed form tables is improved, it is clearly visible whether the search is applied to a table.
Web services and HTTP services.
Developers can create HTTP services in applied solutions. Developers can access HTTP request body, headers, and line.

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.

This feature was not provided.

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

You can create services that have the following advantages over web services:
  • Simpler implementation.
  • Less amounts of data transferred.
  • Less computing power is required to parse a response.

A different usage model (RESTful services).

Client application.
Database operations.
The Hibernated session state is implemented, which is intended for preserving sessions after unexpected connection losses. Sessions that require licenses release the occupied licenses once they are hibernated. If a connection is assigned to a hibernated session, the session loses its Hibernated state. During the recovery from hibernation, sessions that require licenses attempt to obtain licenses. If a license cannot be obtained, the session is terminated. The option to set a timeout for automatic shutdown of hibernated sessions is implemented. If a connection to the client is closed by the 1C:Enterprise server, the session is hibernated(instead of being terminated).

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.

This feature was not provided.

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

In the client/server mode, in some scenarios the client application continues functioning even when the client computer stays in hibernation mode for a long time.
Data composition system.
In the data composition system, new options are implemented for comparison of string data: BeginsWith, NotBeginsWith, Like, and NotLike.This feature was not provided.Extended features for filtering by string expressions in reports created using the data composition system and in dynamic lists.
Applied objects.
For catalog, chart of characteristic types, chart of accounts, chart of calculation types configuration objects, the GetPredefinedNames() method is implemented.This feature was not provided.You can get the flag indicating that a configuration object has predefined items, as well as the full list of predefined item names. Using this list, you can check whether data items are set for all predefined items.
External data sources.
You can write data to external data source tables.

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

This feature was not provided.

External data source table data was read-only.

New options for integration with information systems and databases.
Queries.
A query wizard for managed mode is implemented. For the QueryWizard object, the Show() method is implemented.

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.

This feature was not provided.New features for using queries in managed applications.
Queries.
An object model intended for modification of query texts is implemented. The QuerySchema object is implemented.This feature was not provided.

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

Spreadsheet documents.
You can insert pictures in spreadsheet document cells. You can specify text position relative to the picture in a cell (or an area of cells) of a spreadsheet document. A picture is linked to a cell where it is inserted.

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

Pictures could only be inserted in spreadsheet documents as images that were not linked to any specific cell (or an area of cells).Improved usability of pictures in spreadsheet documents.
System requirements.
Alt Linux SPT 6.0 distribution kit is supported.This distribution kit was not supported.New Linux distribution kit is supported.
Data composition system.
For the DataCompositionFilter object, the default constructor is implemented.This feature was not provided.In a mobile application, you can set a filter for a list of contacts.
Event log.
The _$Data$_.TotalsMaxPeriodUpdate event with presentation Data.Modify maximum calculated totals period is implemented. The event is registered when the SetMaxTotalsPeriod() or SetMinAndMaxTotalsPeriods() method is called.

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

The _$Data$_.TotalsPeriodUpdate event was registered when the maximum totals period was set.The event log displays actions that set the totals period more consistently.
Linux.
Client application.
1C:Enterprise searches for the ImageMagick library by name libMagickWand-6.Q16.1C:Enterprise did not search the ImageMagick library by name libMagickWand-6.Q16.During the startup, 1C:Enterprise is not shut down if the ImageMagick library was renamed and then reinstalled.
DBMS operations.
Microsoft SQL Server 2014 DBMS is now supported.Microsoft SQL Server 2014 DBMS was not supported.New Microsoft SQL Server version is now supported.
Developer tools.
For the Technological log configuration file editor (read more) and User action log conversion (read more), data processors, which are distributed via 1c-dn.com, the English interface is implemented. Both data processors are rewritten using the English variant of 1C:Enterprise script.The Technological log configuration file editor and User action log convertor data processors had Russian interface only.

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

Simplified usage and modification of the Technological log configuration file editor and User action log convertor data processors for non-Russian-speaking developers.
Development tools.
In the "dump configuration to files" feature, the approach to dumping standard attribute data is modified. Only attributes whose properties differ from the default values (for the given attribute) are dumped. Changing properties of a single standard attribute results in dumping all of the standard attributes of the configuration object. The same behavior is implemented for loading: if an XML file contains a description of a standard attribute, it is loaded to the configuration even if the description of the standard attribute contains only default values.

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.

While dumping configuration files, standard attribute data was always dumped, even if all of the standard attribute properties had default values.Reduced configuration file size. Reduced number of "different" objects found when comparing configurations after dumping and subsequent loading.
Predefined data.
Applied objects.
Common attributes / Data separation.
You can edit the flag that shows whether predefined data is initialized in a data area or in the entire infobase. The GetPredefinedDataInitialization() and SetPredefinedDataInitialization() methods are added for catalog managers, charts of characteristic types, charts of accounts, and charts of calculation types.

This change is not implemented in 8.3.4 compatibility mode.

Editing the flag that shows whether predefined data is initialized in a data area or in the entire infobase was not available.Extended capabilities for processing predefined data. You can inform the system at any time that predefined data in a data area or in the entire infobase is initialized (or not initialized). In a distributed infobase, when you remove infobase subordination to the master node, you can specify that all of the predefined data items are created in the infobase whose subordination is being removed.
System requirements.
Microsoft Windows Server 2012 R2 (x86-64) is now supported.Microsoft Windows Server 2012 R2 (x86-64) was not supported.New version of the Microsoft operating system is now supported.
Server clusters.
Administration tools.
You can use an external utility for generating dumps when the platform stops responding.

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.

Dumps were generated by the process that stopped responding.Eliminated the issue where the system stopped responding while generating a dump for a process that stopped responding.
Data exchange.
The instructions for unbinding an infobase from the root node and restoring a configuration in a distributed infobase node, which take into account the specifics of predefined data usage, are available in the platform documentation.This information was not available in the documentation.The documentation contains recommendations for using distributed infobases that include predefined data.
Client application.
Managed forms.
In thin and thick client applications, the system behavior based on the Modality usage mode configuration property value is modified. For thin and thick client applications, the EnableCheckModal startup parameter 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.

The modal method behavior was based on the Modality usage mode configuration property value only. Depending on this property value, modal methods were executed with warnings or exceptions. This behavior could not be changed using command-line parameters.You can use external data processors that include modal methods in applied solutions where modality is disabled.
System requirements.
Support of Microsoft Windows 8.x operating system is implemented.Microsoft Windows 8.x operating system was not supported.Extended list of supported operating systems.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Client application installation.
While the client application is being updated via the Internet, a dialog box displaying the progress of downloading the distribution kit from the server is being displayed. You have the option to cancel the download.

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

Improved process of updating the client application using Internet services: the progress is displayed and the download can be canceled.
Client application.
The Help window is opened like any other form:
  • 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.

Help was always opened in a new window, regardless of the main application window interface settings.

The help command bar had different content.

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

The behavior of the Help window is unified with other forms.
Configuration installation.
New splash screen in the configuration installation wizard.The configuration installation wizard used a different splash screen.The configuration installation wizard and the platform installation wizard have uniform looks.
Client application.
If OpenID authentication is available in an infobase, once you run the thin client and select the infobase, the authentication dialog box will display the name of the last authenticated user.The user name box in the OpenID authentication dialog box was always empty.The user name box behavior is uniform for all authentication methods.

Predefined data.
When a catalog, chart of characteristic types, or chart of accounts folder is marked for deletion, unmarked for deletion, or deleted, the platform checks whether the user has enough rights to access subordinate predefined objects.When a catalog, chart of characteristic types, or chart of accounts folder was marked for deletion, unmarked for deletion, or deleted, the platform did not check whether the user had enough rights to access subordinate predefined objects.The platform does not allow deletion of a catalog, chart of characteristic types, or chart of accounts folder if the folder contains a predefined item and the user does not have the right to delete that item interactively.
Web client.
When the web client is started in Google Chrome web browser on MacOS X operating system, the message that the web browser is not supported is not displayed.When the web client was started in Google Chrome web browser on MacOS X operating system, the message that the web browser was not supported was displayed.Improved usability of applied solution startup in the web client that is started in Google Chrome web browser on MacOS X operating system (the message is removed). Support of this web browser is subject to further discussion.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Common attributes / Data separation.
File mode.
In separated infobases that run in the file mode, query execution is optimized.

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

Improved performance of separated infobases that run in the file mode.
Managed forms.
In some scenarios, forms are opened faster.Opening forms was not optimized.Improved system performance in some scenarios.
Database operations.
Improved performance of establishing a connection to an infobase that is running in the file mode and located on a network resource.The performance of establishing a connection to an infobase that was running in the file mode and located on a network resource was insufficient.For the second and following users, improved performance of establishing a connection to an infobase running in the file mode and located on a network resource.
1C:Enterprise script.
Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties.The performance of the following operations was insufficient: execution of 1C:Enterprise script methods and getting configuration object properties.Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties.
Accounting registers.
Improved performance of writing to accounting registers for record sets that contains no more than 10 records.When a record set with no more than 10 records was written to an accounting register, the writing performance was insufficient.Optimized accounting register operations.
DBMS operations.
Accounting registers.
Common attributes / Data separation.
In the client/server mode with IBM DB2 or Oracle Database DBMS, improved performance of writing to accounting registers that are included in the contents of common attributes used as separators.In the client/server mode with IBM DB2 or Oracle Database DBMS, the performance of writing to accounting registers included in the contents of common attributes that were used as separators was insufficient.Optimized accounting register operations in the client/server mode with IBM DB2 or Oracle Database DBMS.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Defined types.

The list of types that can be included in defined types is significantly extended.

You can use defined types in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators.

The algorithm of the configuration check for correct usage of defined types is modified: a defined type is considered valid (in each usage instance) if all types that form the defined type are valid when the check is performed.

The configuration check algorithm is not modified in 8.3.4 compatibility mode.

The list of types that could be included in defined types was significantly shorter.

The configuration check was performed as follows: check whether the defined type only includes allowed types, and check whether the defined type is not included in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators.

New defined type usage options in applied solution development. Particularly, integration of applied solutions with third-party subsystems is now simpler.
Development tools.
The order of standard attributes in the standard attributes window and in the role settings is modified.

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

The list of standard attributes in the standard attributes window and in the role settings was not ordered.

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

Display of standard attributes is uniform with other system features.
Client application.
For text documents, the Save as command now saves the document encoding, provided that one of the following encodings is used: ANSI, OEM, UTF-8, or UTF-16. Otherwise, the UTF-8 encoding is set.

Closing the Save as dialog box by clicking Cancel does not modify the encoding of the open document.

This change is not implemented in 8.3.4 compatibility mode.

For text documents, the Save as command set the UTF-8 encoding for the document being saved, regardless of the encoding that was used when the document was opened.

Closing the Save as dialog box by clicking Cancel set UTF-8 encoding for the open document.

Eliminated unexpected system behavior.
Managed forms.
Dynamic lists.
In the Customize form dialog box, the DataVersion field cannot be added to a form.In the Customize form dialog box, the DataVersion field could be added to a form.Eliminated unexpected system behavior.
Background and scheduled jobs.
At the start of a background job, the SessionParametersSetting event handler is run after the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on).At the start of a background job, the SessionParametersSetting event handler was run prior to the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on).Eliminated unexpected system behavior.
Common attributes / Data separation.
Information registers.
Accumulation registers.
Accounting registers.
Calculation registers.
The configuration check and database configuration update include the check whether registers affecting a sequence are included in the same separator content as the documents included in the sequence.

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.

The check for correspondence between separators included in a document sequence and registers affecting this sequence was not performed.Eliminated unexpected system behavior.
Temporary storages.
The volume of data transferred between the client and the server cannot exceed 4 GB (in the serialized form) in the following cases:
  • 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.

During an attempt to transfer more than 4GB of data (in serialized form) to the server, the client application stopped responding.Eliminated unexpected system behavior.
Internet-enabled functionality.
The cURL library is updated to version 7.32. It supports new options, such as downloading files with Cyrillic names from FTP servers.The cURL library version 7.18.2 was used.Resolved some issues of the previous library version.
XML and XDTO support.
If an error related to an attempt to write an invalid character to an XML object occurs at the server side, an unrecoverable error is not generated at the client side, and the user is not prompted to restart the client application.

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

If an error related to an attempt to write an invalid character to an XML object occurred at the server side, the unrecoverable error was generated at the client side, and the user was prompted to restart the client application.Eliminated unexpected system behavior.
XML and XDTO support.
If the FindDisallowedXMLCharacters() method finds an incomplete surrogate Unicode pair, it returns the position of the first character of the incomplete pair.If the FindDisallowedXMLCharacters() method found an incomplete surrogate Unicode pair, it returned the position of the character that followed the first character of the incomplete pair.Eliminated unexpected system behavior.
Managed forms.

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

In the text box that was in the "choice from the list" mode and displayed an empty reference, clicking the Cancel button displayed a dialog box with Undefined text.Eliminated unexpected system behavior.
Navigation links.
When a navigation link is followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation link are ignored. This feature is implemented in the following scenarios:
  • 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
When navigation links were followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation links were ignored. Users had to delete these characters manually.Improved management of navigation links.
XML and XDTO support.
Web services.
When string values are read using the XMLReader object or obtained using a web service, line feed characters keep their original format (they are not converted).

This change is not implemented in 8.3.4 compatibility mode.

When string values were read using the XMLReader object or obtained using a web service, the following replacements were made:
  • Combinations of line feed characters 0x0D+0x0A (CR+LF) and 0x0D (CR) were replaced with 0x0A (LF).
  • Combination of characters 0x0A+0x0D (LF+CR) was replaced with 0x0A+0x0A (LF+LF).

Eliminated unexpected system behavior.
Spreadsheet documents.
XML and XDTO support.
Settings of text boxes located in spreadsheet documents can now be serialized to XDTO. A spreadsheet document deserialized from XDTO is equivalent to its source.

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

Settings of text boxes located in spreadsheet documents are saved after dumping/loading configuration to/from XML files.
Development tools.
  • 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
In the Evaluate expression dialog box and in the Immediate window, expressions were 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
Eliminated the issue that introduced inaccuracies to the calculated expression result because the expression could only be calculated once (at the current debugging step).
Configuration repositories.

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.

During selective comparison of forms, two comparisons were performed: the comparison of form modules and the comparison of forms. Two reports were displayed as a result of comparison.

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

Data composition system.
In data composition system, the automatically generated title of a field linked to data retrieved using "." (dot) from a Ref field of a tabular section contains the field presentation only. In particular, a field related to the TabularSection.Ref.Number attribute will have the Number title.

This change is not implemented in 8.3.4 compatibility mode.

In data composition system, the automatically generated title of a field linked to data retrieved using "." (dot) from a Ref field of a tabular section contained the Ref word and a presentation of the data attribute retrieved using "." (dot).Improved appearance of reports.
Managed forms.
Pessimistic lock of data described by the main form attribute is performed for the following actions in text boxes:
  • 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.

Pessimistic data lock was set for the following actions in text boxes:
  • Attempting to open a choice list
  • Starting text input
Pessimistic data lock is set for all actions that change text box contents.
XML and XDTO support.
Development tools.
In the "dump configuration to files" feature, XML file format is changed for the following configuration parts: managed forms, dynamic list settings, graphical schema items, geographical schemas, functional option content, and field lists. Tag names now match the names used in 1C:Enterprise script, the XML element name spelling is unified. The dump format is more compact and clear. The properties filled with default values are not dumped.

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.

In the "dump configuration to files" feature, XML files that stored managed forms, dynamic list settings, graphical schemas, geographical schemas, functional option content, and field lists had a different format.XML files that store configuration data are more compact and better structured.
Charts of accounts.
Accounting registers.
Data exchange.
While a chart of accounts item is being written with DataExchange.Load property set to True, new extra dimension types are checked for uniqueness. The unique ones are added to the table of extra dimension values, and the nonunique values are not added, which eliminates possible errors.If a chart of accounts item was being written with DataExchange.Load property set to True, the check for uniqueness of extra dimensions was not performed. This could cause errors while items were being added to the table of extra dimension values.The order of loading chart of accounts data and data of linked accounting registers does not matter.
Development tools.
In the property palette, the Sort alphabetically command sorts properties by presentation (if displaying property names is disabled) or by name (if displaying property names is enabled). If a property does not have a name, the sorting is always performed by text presentation.In the property palette, the Sort alphabetically command sorted properties by presentation.The sorting command behavior depends on object property presentations.
Data composition system.
In the data composition system, the conditional appearance with Fields header usage area is applied to an area of a vertical template that contains names of displayed fields.

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.

In the data composition syste, the conditional appearance with Group usage area was applied to all areas of a vertical template.Improved usability of data composition system conditional appearance.
Thick client.
If more than two parameters are passed to the Insert() method of the TableBoxColumns object, an error is generated.

This change is not implemented in 8.3.4 compatibility mode.

Up to five parameters could be passed to the Insert() method of the TableBoxColumns object, while only two parameters were used. No errors were generated.Eliminated unexpected system behavior.
Event log.
The event log format is modified. The log is now stored in an SQLite database. The log file has .lgd extension.

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.

The event log had text format.

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.

Improved performance when accessing event log data. Improved event log reliability.

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

Event log.
Deletion of a large number of event log records (more than 10 million) takes much less time.

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

The performance of event log record deletion was insufficient.

Reducing the event log size could not be terminated.

Reducing the size of a large event log takes reasonable time.

This operation can be terminated if needed.

Spreadsheet documents.
When a spreadsheet document is saved to a PDF file, a single document copy is saved. The Copies spreadsheet document property is ignored.

To include multiple copies into the PDF file, use the WriteFileForPrinting() method of the RepresentableDocumentBatch object.

This change is not implemented in 8.3.4 compatibility mode.

When a spreadsheet document was saved to a PDF file, the file contained the number of document copies specified in the Copies property.Eliminated unexpected system behavior.
Client application.
Development tools.
In Designer and thick client, customization of the search result selection background is available.In Designer and thick client, the search result background color could not be customized.Users can specify search result selection background color that fits their text editor settings.
Data exchange.
Common attributes / Data separation.
In a session that does not use any separators, while session changes are being registered, the Update right is not required for tables of objects being registered.

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.
In a session that did not use any separators, while session changes were being registered, the Update right was required for tables of objects being registered.

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

In separated mode, changes are registered correctly.
Common attributes / Data separation.
Database operations.
New options for FindMarkedForDeletion(), FindByRef(), and DeleteObjects() methods:
  • 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 search for references, search for objects marked for deletion, and deletion of marked objects were performed only in data available in the current session with the current separator values. Including individual configuration objects to (or excluding configuration objects from) search or deletion was not available.

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.

You can customize the deletion of marked objects, especially in separated infobases. You can design more detailed messages about deletion results (total objects deleted, total objects not deleted, and so on).
Defined types.
In Designer, properties palette contents for objects that have defined type are generated based on the actual type that describes the defined type.The properties palette contents for objects that had defined types were always displayed as if all of the objects had complex type, regardless of their actual types.Property customization for objects that have defined types is now similar to property customization for objects whose types are specified explicitly.
Software licensing.
In the license activation dialog box, each PIN code is entered in a single text box, which includes an input mask (in all license acquisition scenarios).

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.

In the license activation dialog box, each PIN code was entered in 5 text boxes (in all license acquisition scenarios).

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.

The software license activation dialog box is improved. PINs can be pasted from the clipboard.

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

The error messages are clearer to users.

Common attributes / Data separation.
In version 8.2.16 or earlier compatibility mode, configuration checks and database configuration updates include the check whether each document journal is included in contents of at least one common attribute, and if it does, the appropriate diagnostics is performed.

The configuration is not updated in this case.

In version 8.2.16 or earlier compatibility mode, the configuration check did not detect configuration errors if document journals were included in contents of common attributes, and therefore such errors did not prevent the configuration update.The system cannot become inconsistent due to the fact that in version 8.2.16 or earlier document journals could not be included in common attribute contents.
Data composition system.
The GroupPlacement parameter of the data composition system does not affect the displaying of totals.

This change is not implemented in 8.3.4 compatibility mode.

Grouping totals were not displayed if the GroupPlacement data composition system parameter was set to End or None for the selected grouping.Eliminated unexpected system behavior.
Spreadsheet documents.
For cells that have single-line height, tooltips that do not fit a single text line are displayed as multiple text lines.

This change is not implemented in 8.3.4 compatibility mode.

For cells that had single-line height, tooltips were displayed as single text lines. If tooltip text did not fit a single line, it ended with "...."Eliminated unexpected system behavior.
Spreadsheet documents.
In the thin client, when a spreadsheet document is obtained from the server, empty rows located in document cells are preserved.

This change is not implemented in 8.3.4 compatibility mode.

In the thin client, when a spreadsheet document was obtained from the server, empty rows located in document cells were lost.Eliminated data loss during the transfer of spreadsheet documents from the server to the client.
Managed forms.
In a managed form table cell that has a drop-down list available and the Directly editing mode set, pressing Down Arrow or Up Arrow keys moves the selection to another cell and does not open the drop-down list. The drop-down list is only opened when a new row is added.

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

In a managed form table cell (with the Directly editing mode set), pressing Down Arrow or Up Arrow keys might open a drop-down list. This eliminated the option to add a new row by pressing Down Arrow.Eliminated unexpected system behavior.
Data composition system.
When a data composition template is generated, expressions for calculating details that contain fields unavailable due to functional options are removed from predefined templates.

This change is not implemented in 8.3.4 compatibility mode.

When a data composition template was generated, details expressions were copied from the predefined templates without any modifications.During report generation, errors do not occur when templates include fields unavailable due to functional options.
Client application.
In managed mode, if any connection issues or server-side issues occur, the client application allows to repeat a request, interrupt the operation, or shut down the application.If any connection issues or server-side issues occurred, users were not allowed to repeat their requests. In most cases the client application was simply shut down.The client application is more robust against connection issues or 1C:Enterprise server issues.
Mobile application.
If the interface compatibility mode is set to Taxi and then the Use purposes configuration property is set to Personal computer and Mobile device, the Interface compatibility mode property is automatically set to Taxi. Version 8.2 allowed.

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.

Selecting the Mobile device value in the Use purposes configuration property made the following changes in configuration properties without any warnings:
  • The Interface compatibility mode property was set to Version 8.2.
  • The Modality usage mode property was set to Use.
Designer behaves as expected.
Software licensing.
Users that do not have administrative rights can activate software licenses. In this scenario the license is activated for the current user.Only users with administrative rights could activate licenses.

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.

Predefined data.
Data exchange.
Common attributes / Data separation.
When predefined data is changed, changes are only registered for items that are actually modified, added, or deleted.

When the compatibility mode is changed from Version 8.3.2 (or earlier) to Version 8.3.3 (or later), all predefined item changes are registered.

When the compatibility mode is changed from Version 8.3.3 (or later) to Version 8.3.2 (or earlier), registration of all predefined items is removed.

When changes are registered for predefined items:

  • If the configuration object where predefined items are changed and the exchange plan where the changes are registered do not have common separators, the changes are registered for all nodes of the exchange plan.
  • If the configuration object where the predefined items are changed and the exchange plan where the changes are registered have common separators, the changes are only registered for those exchange plan nodes where separator values match the separator values of predefined items.
When predefined data belonging to a specific object was changed, all predefined items of this object were registered as if they were changed.

Predefined item changes were registered for all exchange plan nodes available from the session where the predefined items were changed.

When object predefined data is changed, object change registration tables do not significantly increase in size.
Managed forms.
Web client.
In the web client, if a managed form table cell contains multiple text lines, only lines that fit the cell height are shown. If the text does not fully fit, ellipsis (…) is added to the end of the last line. In Microsoft Internet Explorer 8 web browser, the ellipsis is not displayed.

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

In the web client, if a managed form table cell contained multiple text lines, the lines might be cut in the manner that made them unreadable (only the upper character halves were displayed and the lower ones were cut).

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.

Eliminated unexpected system behavior.
Data composition system.
While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items are removed:
  • Items that include references to fields disabled by functional options
  • Items that include references to fields unavailable due to access rights restrictions
  • Items linked to data composition schema fields that no longer exist

This change is not implemented in 8.3.4 compatibility mode.

While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items were removed:
  • Items that included to fields disabled by functional options
  • Items that included references to fields unavailable due to access rights restrictions
Improved system stability.
Database operations.
You can load the infobase dump file (*.dt) that was generated with the following conditions:
  • 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.

Loading the infobase dump file (*.dt) was not available if the file was generated with the following conditions:
  • 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.
Eliminated unexpected system behavior.
Data display.
Text fragments found during a search by substring are displayed in a uniform way (bold font and green text) in the following cases:
  • In managed form text box drop-down lists
  • In favorites
  • In history
  • In dynamic lists
  • In the full-text search form
The substrings that were found had different looks.Uniformed look for different features.
XML and XDTO support.
For charts of accounts and charts of calculation types, the Predefined field of predefined tabular sections is available for writing. In charts of accounts and charts of calculation types, the predefined records of predefined tabular sections can include only predefined items. During a serialization of a chart of accounts item or a chart of calculation types item to XML(XDTO), the Predefined item, which matches the Predefined property, is written. During the deserialization, the Predefined item value is written to the Predefined property only if the compatibility mode is disabled.

This change is not implemented in 8.3.4 compatibility mode.

For charts of accounts and charts of calculation types, the Predefined field of predefined tabular sections was read-only.

During the serialization of a chart of account item or a chart of calculation types item to XML(XDTO), the Predefined item was not generated.

During data exchange between configurations, the flags of predefined data are no longer lost in the chart of accounts and chart of calculation types items.
Managed forms.
Getting a choice form in a slow connection scenario is implemented identically to getting forms in other scenarios.Getting a choice form in a slow connection scenario was implemented differently from getting forms in other scenarios, it included caching the form.Increased relaibility for getting choice forms in a slow connection scenario.
Applied objects.
During the restructuring of hierarchical predefined data, if an item parent is not found during the update, the item is moved to the top level.

During the creation or restructuring of predefined data, if references to subordinate items are missing from predefined tabular sections, rows with missing references are deleted. Upon deletion, the platform generates a diagnostics message or an event log record, and the tabular section row numbering is updated accordingly.

This change is not implemented in 8.3.4 compatibility mode.

Invalid references to parent items or subordinate items in predefined data might cause errors during infobase retructuring.Increased system stability in the scenario where predefined data items contain invalid references to parent or subordinate items.
Command interface.
In the Taxi interface the scaling of pictures in the sections panel of the web client is now identical to that of the thin client. The picture height is calculated as follows:
  • 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.
In the Taxi interface of the web client 48x48 pixel squares were reserved for section panel pictures. The size of larger pictures was reduced proportionally and smaller pictures were centered within those squares. The section panel height was never reduced.The Taxi interface behavior in the web client is unified with that of the thin client.
Spreadsheet documents.
XML and XDTO support.
When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file is not important.When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file was important.Spreadsheet documents serialized to XDTO using 1C:Enterprise version 8.3.4 and earlier can be read without errors.
Third-party software.
The OpenSSL library is updated to version 1.0.0r.OpenSSL version 1.0.0m was used.Eliminated OpenSSL security issues.
Web client.
The web client is optimized for Google Chrome 37 web browser. The managed form issues where text did not fit the desired area are eliminated.The web client had issues related to displaying text in Google Chrome 37 web browser.

Improved Google Chrome 37 web browser support.

DBMS operations.
Improved reliability of PostgreSQL DBMS operations in certain scenarios.Insufficient reliability of PostgreSQL DBMS operations in certain scenarios.Improved reliability of PostgreSQL DBMS operations.
Administration.
For Russia, a single one-hour time zone shift is applied in line with Federal Law #248-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.

The platform did not reflect the changes introduced by Federal Law #248-FZ.The time offset changes introduced by the new law are implemented.
Add-ins.
A section describing add-in limitations is added to the Add-in development technology document (read more).The Add-in development technology document did not describe add-in limitations.Improved add-in technology description.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Dynamic lists.
Dynamic lists cannot be ordered by extra dimension fields of accounting registers. An attempt to order a dynamic list by these fields (for example, by clicking the column header) does not result in a server call.

This change is not implemented in 8.3.4 compatibility mode.

An attempt to order a dynamic list by extra dimension fields of accounting registers generated an error message and initiated a server call, which did not retrieve any data.Dynamic lists do not allow ordering that does not make sense, therefore the system behaves as expected (from the user’s point of view).
Applied objects.
An attempt to set a value to ThisObject or AdditionalProperties attribute of a CatalogObject, ExchangePlanObject, or ChartOfCharacteristicTypesObject raises an exception.

An attempt to set a value to the DataExchange attribute of a CatalogObject or ChartOfCharacteristicTypesObject raises an exception.

This change is not implemented in 8.3.4 compatibility mode.

An attempt to set a value to ThisObject or AdditionalProperties attribute of a CatalogObject, ExchangePlanObject, or ChartOfCharacteristicTypesObject did not raise an exception, and the value was not set.

An attempt to set a value to the DataExchange attribute of a CatalogObject or ChartOfCharacteristicTypesObject did not raise an exception, and the value was not set.

Unified processing of the specified properties: an attempt to set a value for a read-only attribute raises an exception.

Client application.
Server clusters.
If the client and server application versions do not match, the search for client application distribution kit is performed in the following order:
  • 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
If the client and server application versions did not match, the search for client application distribution kit was performed in the following order:
  • 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 for updates behaves as expected: search in the local network precedes search using Internet services.
Common attributes / Data separation.
The SetPredefinedDataUpdate() and SetInfoBasePredefinedDataUpdate() methods can only be executed in sessions that do not have any separators (in addition to the fact that they require the Administration right).

This change is not implemented in 8.3.4 compatibility mode.

The SetPredefinedDataUpdate() and SetInfoBasePredefinedDataUpdate() methods could be executed in any session, provided that the user had the Administration right.

Users cannot change the infobase predefined data update mode if they do not have the required rights.
Navigation links.
Client application.

The ReferencesArray parameter of the GetURLsPresentations() function is mandatory. The return value of this function is always an array. For input array items whose presentations cannot be obtained, the matching output array items contain UNDEFINED.

This change is not implemented in 8.3.4 compatibility mode.

The ReferencesArray parameter of the GetURLsPresentations() function was not mandatory. In cases when a parameter value presentation could not be obtained by its value, uniform system behavior across all client applications was not guaranteed.The GetURLsPresentations() function is uniform across all client applications.
Web client.
In the web client, performing the Execute() operator ends in exception.In the web client, calling the Execute() operator was ignored and no diagnostic messages were displayed.Implemented applied solution error diagnostics (for calling the Execute() operator in the web client).
Spreadsheet documents.
In the SpreadsheetDocumentRange object, the TopBorder, RightBorder, BottomBorder, and LeftBorder properties contain the UNDEFINED value if the corresponding border is not the same for all cells.

This change is not implemented in 8.3.4 compatibility mode.

In the SpreadsheetDocumentRange object, values of the TopBorder, RightBorder, BottomBorder, and LeftBorder properties were retrieved from the properties of a random cell within the specified rangeEliminated unexpected system behavior.
Data composition system.
In data composition system batch queries, when a temporary table is created, if the table fields are not used by the next queries of the batch and the table is not included in required joins, the query that creates the table is removed from the batch.

This change is not implemented in 8.3.4 compatibility mode

In data composition system batch queries, temporary tables were deleted from the batch if the table fields were not used by the next queries of the batch and the table was not used in other queries of the batch that also created temporary tables.Improved management of temporary tables in the data composition system.
Data exchange.
Information registers.
Changes in information registers that have dimensions of UUID type that are included in the main filter are recorded correctly.

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

Changes in information registers that had dimensions of UUID type were recorded incorrectly.

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

Eliminated unexpected system behavior. In exchange plans containing information registers with dimensions of UUID type that are included in the main filter, registering all dimensions is required.
1C:Enterprise script.
Common objects.
In the thin client, the following types are not available: ValueTableRow, ValueTableColumnCollection, ValueTableColumn, CollectionIndexes, CollectionIndex, ValueTreeRowCollection, ValueTreeRow, ValueTreeColumnCollection, and ValueTreeColumn.

This change is not implemented in 8.3.4 compatibility mode.

In the thin client, the following types were available: ValueTableRow, ValueTableColumnCollection, ValueTableColumn, CollectionIndexes, CollectionIndex, ValueTreeRowCollection, ValueTreeRow, ValueTreeColumnCollection, and ValueTreeColumn.Eliminated unexpected system behavior.
Managed forms.
In managed form text boxes, the TextEditEnd event handler is not called when the spin buttons are clicked.

This change is not implemented in 8.3.4 compatibility mode.

In managed form text boxes, the TextEditEnd event handler was called when spin buttons were clicked.

Eliminated unexpected system behavior.
Applied objects.
Managed forms.
When an object is created from a dynamic list filtered by an attribute of Date type, object attributes of that type are filled from the filling data.

This change is not implemented in 8.3.4 compatibility mode.

When an object was created from a dynamic list filtered by an attribute of Date type, object attributes of that type were not filled from the filling data.

For such attributes, the standard FillingValues parameter of the new item form contained values of the StandardBeginningDate type passed from the dynamic list filters.

Eliminated unexpected system behavior.
Managed forms.
In managed form text boxes, if editing a string with an input mask results in a string that matches an empty input mask, an empty string is recorded to the form attribute displayed in the text box. If the string has fixed length, the string consists of spaces.

This change is not implemented in 8.3.4 compatibility mode.

In managed form text boxes, if editing a string with an input mask resulted in a string that matched an empty input mask, a string that contained spaces and fixed input mask characters was recorded to the form attribute displayed in the text box.When a text box is cleared, an empty string is recorded to the linked attribute regardless of the input mask availability. In text boxes linked to attributes of Text type with the input mask set, the automatic "incomplete" mark is displayed correctly.
Managed forms.
In managed form text boxes, the procedure of generating a drop-down list during input by string is modified. The procedure is described in the documentation.

This change is not implemented in 8.3.4 compatibility mode.

In managed form text boxes, the following procedure was used for generating a choice list during input by string:
  • 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.
In managed form text boxes, eliminated issues in the procedure of drop-down list generation when search is performed both by beginning of string and by substring.
Managed forms.
Getting the list of desktop forms is implemented. For the Forms in tabs and Taxi interface modes, the ClientApplicationWindows collection contains a separate item that describes the start page (desktop). The Content property of this item contains the list of forms available on the start page (desktop).

For the Forms in separate windows interface mode, the ClientApplicationWindows collection contains ClientApplicationWindow objects that describe forms located on the desktop.

For the ClientApplicationWindow object, the StartPage and Content properties are implemented.

The GetContent() method of the ClientApplicationWindow is supported for compatibility purposes.

This change is not implemented in 8.3.4 compatibility mode.

This feature was not provided.

For the Forms in tabs and Taxi interface modes, the ClientApplicationWindows collection did not contain objects describing the start page (desktop).

For the Forms in separate windows interface mode, the ClientApplicationWindows collection did not contain objects describing forms opened on the desktop.

Developers can access forms located on the start page (desktop) using 1C:Enterprise script.
Automated testing.
For subordinate objects of the TestedApplication object, the TestedClientApplicationWindow object is implemented. The object describes the start page (desktop).

Forms (objects of TestedForm type) included in the start page (desktop) content are subordinate to the TestedClientApplicationWindow object that describes the start page (desktop).

For the TestedClientApplicationWindow object, the StartPage property is implemented.

This change is not implemented in 8.3.4 compatibility mode.

The TestedClientApplicationWindow object that described the start page (desktop) was not included in the subordinate objects of the TestedApplication object.

Forms included in the start page (desktop) were subordinate to the TestedClientApplicationWindow object that had its IsMain property set to True.

You can access forms located on the start page (desktop) from 1C:Enterprise script using automated testing tools.
Common attributes / Data separation.
Data exchange.
An exception that does not cause application termination occurs when predefined data is registered for an unseparated configuration object in a separated exchange plan from a session that uses all separators.An exception that caused application termination occurred when predefined data was registered for an unseparated configuration object in a separated exchange plan from a session that used all separators.Eliminated issues that resulted in application termination.
Common attributes / Data separation.
Data exchange.
If a configuration object does not use all separators where it is included, calling the InitializePredefinedData() method does not initialize predefined data items for this object.

This change is not implemented in 8.3.4 compatibility mode.

If a configuration object did not use all separators where it was included, calling the InitializePredefinedData() method caused an error.The InitializePredefinedData() method can be used in any session, not only when all separators are used.
DBMS operations.
Data composition system.
Dynamic lists.
For the LIKE query language operation, search in dynamic lists, and filter in the data composition system, the search template length is limited. The limit depends on the DBMS type. If the template length exceeds the limit, an error is generated, which does not lead to 1C:Enterprise shutdown.For the LIKE query language operation, search in dynamic lists, and filter in the data composition system, if the search template exceeded 1024 characters, this could cause a DBMS error and 1C:Enterprise shutdown.1C:Enterprise is not shut down when a search template is too long.
Applied objects.
The value of the IsFolder field is correctly passed to the PresentationGetProcessing handler.

This change is not implemented in 8.3.4 compatibility mode.

The value of the IsFolder field passed to the PresentationGetProcessing handler was inverted.Eliminated unexpected system behavior.
Managed forms.
The managed form visibility setting is stored in the system setting storage with a purpose use key. The object key is generated as follows: <Full form name>/<Purpose use key>/FormSettings.

This change is not implemented in 8.3.4 compatibility mode.

The managed form visibility setting was stored in the system setting storage without a purpose use key. The object key was generated as follows: <Full form name>/FormSettings.You can use a single form for different use purposes, with custom display settings for each use purpose.
Data composition system.
Data composition system expressions are calculated in the safe mode.

This change is not implemented in 8.3.4 compatibility mode.

The safe mode was not used when data composition system expressions were calculated.

Improved security of executing reports that might use insecure methods from common modules.
Managed forms.
In managed form tables, you can start dragging from an available table cell only.

This change is not implemented in 8.3.4 compatibility mode.

In managed form tables, dragging from any table cell was allowed. When an attempt to drag an unavailable cell was made, the currently selected cell was dragged instead.Eliminated unexpected system behavior.
Data composition system.
The Text parameter of conditional appearance that is specified for the Fields header usage area is applied to grouping field headers.

This change is not implemented in 8.3.4 compatibility mode.

The Text parameter of conditional apperance was never applied to grouping field headers.Eliminated unexpected system behavior.
Data composition system.
The data composition template generator always generates the VerticalLevel property for nested reports. The parent report level is added to the value of this property.

This change is not implemented in 8.3.4 compatibility mode.

Parent report groupings were not taken into account when nested reports were displayed.

Parent report groupings affect nested reports: nested reports are displayed at the same grouping level as the parent report.
Managed forms.
For managed form fields, the PeriodField field type is implemented. It is intended for simplifying selection of periods of several full months.

For managed form field extensions for calendar fields, the Border property is implemented. It specifies border parameters for the calendar field.

The dialog box that was used in the following scenarios is modified:

  • Period selection for dynamic lists
  • Standard period selection for text boxes that display values of StandardPeriod type
  • The StandardPeriodEditDialog object dialog box

This change is not implemented in 8.3.4 compatibility mode.

For managed form fields, the PeriodField field type was not available.

For managed form field extensions for calendar fields, the Border property was not available.

A different dialog box was used in the following scenarios:

  • Period selection for dynamic lists
  • Standard period selection for text boxes that display values of StandardPeriod type
  • The StandardPeriodEditDialog object dialog box

If the period variant was not custom, a drop-down list containing available options was opened in the input field.

The period selection dialog box is improved.
Managed forms.
In managed form tables, if a row is added because editing the previous row is finished or by pressing the Down Arrow, and then the row is neither edited from 1C:Enterprise script nor edited interactively, the new row is automatically deleted once the selection is moved away from it.

This change is not implemented in 8.3.4 compatibility mode.

In managed form tables, if a row was added because editing the previous row was finished or by pressing the Down Arrow, and then the row was not edited interactively, the new row was automatically deleted once the selection was moved away from it.Eliminated unexpected system behavior.
Managed forms.
While a text box choice history is being filled, the check for deleted items is performed. A value presentation is removed from the list if its data was deleted in the current session or its data was deleted in another session but the presentation of deleted data was obtained in this session. If a value is deleted after the choice history is generated, when a user attempts to select this value, a warning is displayed, the value is not selected, and the item is removed from the history list.

The feature is implemented for thin and web clients.

Deleted values were displayed in text box choice history as Object not found items.References to objects that are no longer available for selection are removed from the choice history.
Managed forms.
In managed forms, the length of the PurposeUseKey property value is limited to 128 characters. An attempt to set a value longer than 128 characters or open a form with this property value longer than 128 characters ends with a exception.

This change is not implemented in 8.3.4 compatibility mode.

In managed forms, the length of the PurposeUseKey property value was not limited.

Simplified diagnostics of issues related to PurposeUseKey value being too long.
Data access restrictions.
For each configuration object that is included in separator content and has tabular sections, a data access restriction check is performed (after writing) if the access restriction conditions include attributes from the object tabular section.

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

For configuration objects that were included in separator content and had tabular sections, data access restriction checks were not performed (after writing) if the access restriction conditions included attributes from the object tabular sections.Eliminated unexpected system behavior.
Predefined data.
Charts of accounts.
Charts of calculation types.
The following rules now apply during infobase restructuring:
  • A row of a predefined tabular section of a chart of accounts or a chart of calculation types, which is added in 1C:Enterprise mode and refers to a predefined item, is marked predefined if a predefined row that refers to the same item is added in Designer mode.
  • When a predefined row is deleted from a predefined tabular section of a chart of accounts or a chart of calculation types, the actual row is not deleted. Instead, it loses the "predefined" flag.

In addition to that, the order of tabular section rows might be changed to ensure that all of the predefined items are at the top.

This change is not implemented in 8.3.4 compatibility mode.

In a chart of accounts, adding a predefined extra dimension type in Designer mode was impossible if the extra dimension type was added in 1C:Enterprise mode earlier. When an attempt to delete a predefined row from a predefined tabular section of a chart of accounts was made, the actual row was deleted.

Charts of calculation types had the following behavior:

  • In 1C:Enterprise version 8.2.12 or earlier, the behavior was the same as in 1C:Enterprise version 8.3.5.
  • In 1C:Enterprise versions 8.2.13–8.3.4, if a base, leading, or displacing calculation type that was added earlier in 1C:Enterprise mode was then added in Designer mode, a duplicate calculation type entry was generated. When a predefined row was deleted from a predefined tabular section of a chart of calculation types, the actual row was deleted.
Editing predefined tabular sections no longer might cause data losses.

Editing the list of extra dimension types of a predefined account in Designer might result in a message that the account's maximum number of extra dimension types is exceeded.

Accounting registers.
Accumulation registers.
Information registers.
Calculation registers.
In a value table obtained by the Unload() method of an accounting register, accumulation register, calculationregister, or information register record set, the value of the LineNumber column is equal to the line number in the record set.

This change is not implemented in 8.3.4 compatibility mode.

In the value table obtained by the Unload() method of an accounting register, accumulation register, calculation register, or information register record set, the value of the LineNumber column was equal to the index of the record set index.Eliminated unexpected system behavior.
Client application.
Internet-enabled functionality.
The TLS protocol is recommended for secure connections as it is more secure. The SSL protocol version 3.0 is disabled by default.

If the web server used for thin client connections can use SSL version 3.0 for connecting to a web server, you can use the thin client command-line option /HttpsAllowSSLv3.

SSL version 3.0 is not used (by default) with the HTTPConnection, FTPConnection, InternetMail, WSProxy, WSReference, and WSDefinition objects, when connecting to the configuration repository, and in Debugger. If you need to use SSL version 3.0 in these scenarios, use the AllowSSLv3 option in the conf.cfg file. For the conf.cfg configuration file, the AllowSSLv3 option is implemented.

For the InternetMail object in version 8.3.5 and earlier compatibility mode and in earlier 1C:Enterprise versions:

  • On Windows, you can enable the SSL protocol version 3.0 by editing the system register.
  • On Linux, the availability of SSL protocol version 3.0 is defined by the OpenSSL library version.
The SSL protocol version 3.0 was used for secure connections.Improved security of connections established by client applications that work over the Internet.
Web client.
Add-ins.
The file system extension and the cryptography extension are modified (for all supported Windows web browsers). The reason is that the NPAPI technology is no longer supported in Google Chrome browser.

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 file system extension and the cryptography extension were implemented using the NPAPI technology. The extension methods were executed synchronously. In Google Chrome web browser synchronous execution of methods from add-in APIs was possible.

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.

Web client.
Add-ins.
The add-in technology (read more) no longer supports add-in development for Safari web browser for Windows.The add-in technology supported add-in development for Safari web browser for Windows.The outdated web browser is no longer supported. The Apple company stopped updating Safari web browser for Windows.
Add-ins.
The add-in development technology supports Mozilla Firefox web browser versions 31.0 and later. It is recommended that you build a new installer package for Mozilla Firefox using the new adapter. It is also recommended that you remove installer packages for Mozilla Firefox versions 30.0 and earlier from the add-in archive.

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 did not support Mozilla Firefox web browser versions 31.0 or later.

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

The add-in development technology supports the latest versions of Mozilla Firefox web browser (31.0 or later).

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

Table of contents

Renamed objects

ObjectThe old nameThe new name
The names of AddressData object properties are changed. For compatibility purposes, the previous names are supported.
  • Street
  • House
  • PrimaryAddressString
  • AdditionalAddressString
In the event log, presentations of the following events are modified: _$Data$_.TotalsMinPeriodUpdate and _$Data$_.TotalsPeriodUpdate.
  • _$Data$_.TotalsMinPeriodUpdate
  • Data. Modify totals period
  • Data. Modify minimum calculated totals period
  • Data. Modify maximum calculated totals period

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
Dynamic lists.
Queries.
Custom queries, including queries that generate dynamic lists, are now available in the mobile platform.This feature was not provided in the mobile platform.In mobile applications, you can use dynamic lists generated based on custom queries, and use queries to the infobase for implementing various features, such as checking balance while posting documents
Managed forms.
Faster form opening and faster execution of context server calls.Insufficient performance of form opening and execution of context server calls.Improved user experience by improving the performance of form operations.
Applied objects.
Predefined items are created at the first call of the corresponding table. Calling the SetPredefinedDataUpdate() method before the first call modifies the flag that shows whether predefined data is created.Predefined items were only created when mobile application configuration was updated. After calling the SetPredefinedDataUpdate() method, predefined data was only modified during the next mobile application configuration update.Mobile platform behavior is uniform with that of PC platform version 8.3.3.
Background and scheduled jobs.
Background jobs are now available in the mobile platform.This feature was not provided in the mobile platform.Background jobs are available in mobile applications.
Access rights.
Functional options.
In the mobile platform, the following features are available:
  • 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.

These features were not provided in the mobile platform.Extended features for applied solution interface management.
Database operations.
The EraseInfoBaseData() global context method is implemented.This feature was not provided on the mobile platform.On the mobile platform, you can delete all infobase data.
Development tools.
In Designer, support of Android Debug Bridge (adb) is added. Now you can start a mobile application from Designer on a mobile device emulator or on a physical device connected to a computer.This feature was not provided.Easier development and debugging of mobile applications for Android OS.
Internet-enabled functionality.
Telephony.
New features:
  • 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.

Sending SMS messages and making calls was available with some limitations using parameters of the RunApp() and GotoURL() methods.

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

Easy access to mobile device functionality: SMS and MMS, call history, and making calls.
System requirements.
The configuration property RequiredMobileApplicationPermissions, specifies permissions that mobile application will require on Android:
  • Multimedia
  • Geolocation
  • Reading and writing contacts
  • Reading and writing calendar events
  • Access to telephony

The Mobile application builder uses the specified permissions.

This feature was not provided.You can specify permissions required for your mobile applications more clearly.
Multimedia tools.
Scanning barcodes using the mobile device camera is supported.

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

This feature was not provided.New mobile platform feature.
Development tools.
In Designer, you can edit pictures with variants. You can convert images to images with variants and back.You could only load pictures with variants without editing them.Creating images for mobile applications became easier.
Access to mobile device features.
Access to mobile device contact lists, both local and linked to specific accounts, is implemented. The following objects are implemented: ContactManager, ContactData, AccountContactData, LocalContactKey, ContactAccount, ContactDataItem, and ContactDataItemInstantMessaging.This feature was not provided.You can access mobile device contacts.
Access to mobile device features.
Access to mobile device calendars linked to specific accounts is implemented. The following objects are implemented: CalendarManager, CalendarAccount, LocalCalendarKey, LocalCalendarEventKey, CalendarEventData, AccountCalendarEventData, CalendarData, and AccountCalendarData.This feature was not provided.You can access mobile device calendars.
Location tools.
For the AddressData object, the AddressString property is implemented. It stores an address fragment starting from the street.This feature was not provided.The AddressData object functionality is extended. It can be used not only for geolocation purposes, but also for storing various types of contact information.
Development tools.
The mobile platform distribution kit mobile.zip now includes the version.txt file. The file contains the version number of the mobile platform delivered in the archive.This feature was not provided.Simplified identification of the mobile platform version, including scenarios that use Mobile application builder.
Mobile application builder.
The mobile application builder, which is included in the mobile platform, is improved:
  • 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 mobile application builder had the following features:
  • 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 usability of the mobile application builder is improved.
Client application.
The text displayed on the mobile platform splash screen is translated to all localization languages.The text displayed on the mobile platform splash screen was always displayed in Russian.Eliminated unexpected system behavior.
Common objects.
The option to run external applications on mobile devices and get the results of their execution is implemented. This feature is only available on operating systems of Android family.

The MobileDeviceApplicationLaunch and MobileDeviceApplicationLaunchExtrasData objects are implemented.

This feature was not provided.Simplified applied solution integration with mobile applications, including the option to get mobile application execution result.

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

Development tools.
During the building of an Xcode project, the "executable" attribute is set for the 1cem file included in the project.During the building of an Xcode project, the attributes of the 1cem file included in the project were not changed.Eliminated the problem that occurred when a project file was rebuilt on an operating system of Windows family: the "executable" attribute of the 1cem file was cleared.
Data display.
Mobile application builder.
In the mobile platform, graphical assets for iPhone 6 and iPhone 6 Plus devices are implemented:
  • 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.

The mobile platform and mobile application builder did not support graphical assets required for iPhone 6 and iPhone 6 Plus devices.New Apple mobile devices are supported.

Table of contents

Transition from the previous version to the version 8.3.5

  • Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.5.
  • Some features that are added in version 8.3.5 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
  • 1C:Enterprise version 8.3.5 cannot share a configuration repository with any of the earlier 1C:Enterprise versions. In this scenario users of the earlier versions receive a diagnostic error message.

1C:Enterprise Developer's Community