Changes that require modification of configuration and administrative settings




Functionality After Before Result of changes
1C:Enterprise script.
During the compilation of 1C:Enteprise script texts, unknown compilation directives cause errors.

This change is not implemented in 8.3.8 compatibility mode.

Unknown compilation directives did not cause compilation errors. Better control of source texts. Reduced number of issues that are hard to detect (typos in compilation directives).
Queries.
When a transaction is rolled back from the temporary table manager, all temporary tables created within the transaction are deleted. In file databases, temporary tables created within a query transaction are not available in that query after rolling the transaction back (this behavior is now uniform with scenarios that use other DMBS).

This change is not implemented in 8.3.8 compatibility mode.

When a transaction was rolled back from the temporary table manager, temporary tables created within the transaction were not deleted. In file databases, the option to use temporary tables created in a transaction that was rolled back was available. In scenarios that used other DBMS, this option was not available. Uniform 1C:Enterprise behavior in scenarios that use different DBMS.
Navigation links.
An attempt to execute the GetURL() method for a value that cannot provide an URL generates an exception.

This change is not implemented in 8.3.8 compatibility mode.

An attempt to execute the GetURL() method for a value that cannot provide an URL had the following result:
  • In the thin client, the method returned a blank string.
  • In the web client, an exception was generated.
Unified system behavior in different client applications.
Window-based interface.
Error handling.
If the Timeout parameter of the DoQueryBox(), ShowQueryBox(), DoMessageBox(), or ShowMessageBox() method has a negative value, an exception is generated.

This change is not implemented in 8.3.8 compatibility mode.

If the Timeout parameter of the DoQueryBox(), ShowQueryBox(), DoMessageBox(), or ShowMessageBox() method had a negative value:
  • In the thin client, the timeout was counted from 4 294 967 295.
  • In the web client, the value was not substituted.
Eliminated unexpected system behavior. Unified system behavior in different client applications.
Managed forms.
The option to monitor the usage of context server calls (including implicit calls) in form event handlers where such calls are prohibited at run time is implemented. If you enable this option, diagnostics messages are added to the message window.

To enable or disable this option, use the /EnableCheckServerCalls command-line option of the client application. The option to run the client application from Designer is implemented, with this command-line option available.

A tool for monitoring the usage of context server calls in form event handlers where such calls were prohibited was not available. Improved diagnostics of incorrect usage of 1C:Enterprise programming interfaces.
DBMS operations.
If a parameter of the In operation of the query language is a value table with a column of String type longer that 1024 characters or BinaryData type longer that 2048 bytes, an exception is generated during the query execution. If a parameter of the In operation of the query language was a value table with a column of String type longer that 1024 characters or BinaryData type longer that 2048 bytes, the query might or might not be executed, depending on the DBMS. More predictable query results on different DBMS. Improved system reliability.
Client application.
Managed forms.
At the thick client startup, the Synchronous call usage mode for platform extensions and add-ins configuration property is ignored and all synchronous methods are executed without any warnings or exceptions.

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

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

At the thick client startup, the Synchronous call usage mode for platform extensions and add-ins configuration property was not ignored.

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

Removed checks for synchronous method calls in applied solutions intended to run in thick client only.
Queries.
During the query generation, the query builder (in Designer and in the thick client) and the QuerySchema object (in the thick client) generate aliases for all fields of the first query (in a set of unions) for each query in a batch.

This change is not implemented in 8.Х.Х repository compatibility mode.

During the query generation, the query builder (in Designer and in the thick client) and the QuerySchema object (in the thick client) generated aliases only for expression fields and for fields used for ordering and totals calculation. Unified behavior of query builder and the QuerySchema object in different client applications.
Managed forms.
The following object keys are used for storing desktop separator positions:
  • HomePage/WindowSettings
  • HomePage/Taxi/WindowSettings

Once you turn the compatibility mode off, the keys are renamed. If you set the compatibility mode to Version 8.3.8, the initial names are applied again.

When you export a configuration to a set of XML files, the file that stores the HomePageWorkingArea property (former StartPageWorkingArea property) has a different name.

This change is not implemented in 8.3.8 compatibility mode.

The following object keys were used for storing desktop separator positions:
  • StartPage/WindowSettings;
  • StartPage/Taxi/WindowSettings.
The object key names better reflect their purpose.
Spreadsheet documents.
If auto grouping or rows is enabled, new groupings inherit the name and visibility from the area that is displayed in the grouping header area.

This change is not implemented in 8.3.8 compatibility mode.

If auto grouping or rows was enabled, new groupings inherited the name and visibility from the area that was displayed inside the grouping. Eliminated unexpected system behavior.
Common objects.
If the DBMSNames parameter of the GetDBStorageStructureInfo() method

has a value of non-Boolean type, an exception is generated.

This change is not implemented in 8.3.7 compatibility mode.

A value of any type could be passed to the DBMSNames parameter of the GetDBStorageStructureInfo() method. Eliminated unexpected system behavior.
Spreadsheet documents.
In spreadsheet documents, when a text is displayed with nonhorizontal orientation, it has the same font size as regular text.

This change is not implemented in 8.3.8 compatibility mode.

In spreadsheet documents, when a text was displayed with nonhorizontal orientation, it had bigger font size than regular text. Eliminated unexpected system behavior.
DBMS operations.
Changing the data lock timeout in the Infobase options dialog box in Designer requires administrative rights in a nonseparated session and sets exclusive infobase access mode. If an exclusive lock cannot be set, a message with a list of sessions preventing the lock is displayed, it includes the retry option.

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

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

Changing the data lock timeout in the Infobase options dialog box or using the SetLockWaitTime() 1C:Enterprise script method was allowed in infobases running in shared mode. Eliminated the issues related to database operations that appeared in some scenarios.
XML and XDTO support.
For the XMLWriter.OpenFile() method, the AddBOM parameter is implemented. It shows whether the resulting file includes a BOM. This feature was not provided. Integration with systems that do not expect BOMs in their input XML files is now available.
Administration tools.
System requirements.
In the file infobase, the check for client application versions is implemented. Access to the infobase is only allowed if the versions of all client applications match. If the versions do not match, an error is displayed. An attempt to access an infobase using multiple versions from the following list generated an exception: 8.2.19 to 8.3.4, 8.3.6, and 8.3.7.

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

Increased reliability of file infobases. Simultaneous access to a single infobase using different 1C:Enterprise versions is not allowed.
ZIP archive operations.
The path separator of the ZipFileEntry object depends on the operating system.

This change is not implemented in 8.3.8 compatibility mode.

The path separator of the ZipFileEntry object was always a slash mark (/) and did not depend on the operating system. ZIP file operations use the same file path separators as other file operations.
Data composition system.
When data composition template composer generates parameter names, it does not assign parameter names that are already used in the data composition schema.

This change is not implemented in 8.3.8 compatibility mode.

When data composition template composer generated parameter names, it could assign parameter names that were already used in the data composition schema. Eliminated unexpected system behavior.
Administration tools.
When 1C:Enterprise establishes a secure connection (HTTPS) to the Licensing Center, it automatically selects the root certificate store of the operating system.

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

When 1C:Enterprise established a secure connection (HTTPS) to the Licensing Center, it searched the file cacert.pem for a secure connection certificate. Reduced number of issues related to interaction with the Licensing Center.
Configuration extensions.
For the execution of some configuration object handlers and subscriptions, disabling the safe mode is implemented. Once a handler or subscription is executed, the safe mode and the security profile are restored.

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

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

The option to disable the safe mode using 1C:Enterprise script tools was not provided. You have the option to access objects that have events that require privileged mode in their object modules from configuration extensions and external data processors executed in safe mode.
Internet-enabled functionality.
TLS 1.2 protocol is used to establish secure connection because it provides additional security. You can force the use of TLS 1.0 protocol when establishing thin client connection to a web server using the command-line option /HttpsForceTLS1_0.

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

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

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

TLS 1.0 protocol was used to establish secure connections. Increased security of thin client Internet connections.
Internet-enabled functionality.
If an SMTP server cannot send an email message to one or several recipients, the InternetMail.Send() method returns a map where recipients are keys and SMTP server diagnostic messages are values.

This change is not implemented in 8.3.8 compatibility mode.

If an SMTP server could not send an email message to one or several recipients, the InternetMail.Send() method generated an exception. You can determine which recipients cannot be reached by email and view the reasons provided by the SMTP server.
Development tools.
Configuration properties.
Dumping configurations to files/Restoring configurations from files.
When a configuration is exported to files, the format of Compatibility mode configuration property in the resulting file is different. The new format eliminates possible loss of compatibility mode data during the import. When a configuration with Compatibility mode property set to Do not use was exported to files, the property value was exported as Do not use. Then, if that configuration was imported using a later 1C:Enterprise version, the imported compatibility mode value was incorrect. Eliminated the chance to lose compatibility mode data after exporting and importing a configuration.

Eliminated unexpected system behavior.

Spreadsheet documents.
The FillPropertyValues() method applied to a spreadsheet document copies the Template property of the spreadsheet document.

This change is not implemented in 8.3.8 compatibility mode.

The FillPropertyValues() method applied to a spreadsheet document did not copy the Template property of the spreadsheet document. The behavior implemented earlier to streamline migration to the previous version is no longer supported.
Administration tools.
Database operations.
In the file mode, the default format of new databases is 8.3.8. In the file mode, the default format of new databases was 8.2.14. The optimized file database format implemented in platform version 8.3.8 becomes the default one.
Internet-enabled functionality.
The Port property of FTPConnection object and the Port parameter of its constructor have the Number type.

This change is not implemented in 8.3.8 compatibility mode.

The Port property of FTPConnection object and the Port property of its constructor had String type. The constructor parameter accepted any data that could be converted to Number type. Eliminated unexpected system behavior.
Database operations.
After calling the GetDBStorageStructureInfo() method, tables that do not have presentations in the query language have empty strings for their names (TableName property) and their field names (FieldName property).

This change is not implemented in 8.3.8 compatibility mode.

After calling the GetDBStorageStructureInfo() method, tables that did not have presentations in the query language had their table name (TableName property) and field name (FieldName property) values equal to virtual table presentations. Eliminated unexpected system behavior.
HTML support.
Reading and writing XML documents containing <?xml does not generate an error message.

This change is not implemented in 8.3.8 compatibility mode.

Reading and writing XML documents containing <?xml generated an error message. Eliminated unexpected system behavior.
ZIP archive operations.
File names in ZIP archives are written in UTF8 encoding.

For the ZipFileWriter object constructor and the Open() method of the ZipFileWriter object, parameters that define file name encoding in ZIP archives are implemented. These parameters override the FileNamesEncodingInZipFile parameter in the conf.cfg file.

The default value of the FileNamesEncodingInZipFile parameter in the conf.cfg file is UTF8.

This change is not implemented in 8.3.8 compatibility mode.

File names in ZIP archives were written in UTF8 encoding and the current operating system encoding.

1C:Enterprise script did not provide methods to specify encoding of file names in ZIP archives.

The default value of the FileNamesEncodingInZipFile parameter in the conf.cfg file was OSEncodingWithUTF8.

1C:Enterprise script provides methods to specify the encoding of file names in 1C:Enterprise-generated ZIP archives.
Dynamic lists.
Dynamic list fields included in conditional form appearance item filters are always passed to the client, regardless of the value of the Use always field property or the availability of a visible linked column.

This change is not implemented in 8.3.7 compatibility mode.

Dynamic list fields included in conditional form appearance item filters were not automatically passed to the client. To ensure correct functioning of conditional appearance items, developers had to set the Use always property for such fields. Better usability for 1C:Enterprise developers.
Dynamic lists.
The recommendation to avoid using conditional form appearance for customizing dynamic list appearance if the desired effect can be achieved only by using conditional dynamic list appearance is added to the documentation. The recommendation to avoid using conditional form appearance for customizing dynamic list appearance if the desired effect can be achieved only by using conditional dynamic list appearance was not available in the documentation. 1C:Enterprise documentation is improved.
Data composition system.
In the composition of a data composition system template, the following operations are performed using additional data sets that are automatically generated by a template composer:
  • Getting fields
  • Applying filters to fields received using "." (dot) from fields that contain aggregate functions and are obtained from a query

This change is not implemented in 8.3.8 compatibility mode.

In the composition of a data composition system template, the following operations were performed within a query:

  • Getting fields
  • Applying filters to fields received using "." (dot) from fields that contain aggregate functions and are obtained from a query

This might generate incorrect results or errors.

Eliminated unexpected system behavior.
Data composition system.
In data composition schema templates, when parameters that can have both English and Russian names are generated, their names are generated in the language of the current 1C:Enterprise script variant.

This change is not implemented in 8.3.8 compatibility mode.

In data composition schema templates, when parameters that could have both English and Russian names were generated, their names were always generated in English. You can use Russian names of data composition schema parameters, which match the parameter names that are automatically retrieved from virtual tables.

Comments
0
Add comment