5.1.6. Specifying compatibility properties

Data lock control mode. Option of data lock management in transaction.

Objects automatic numbering mode. Determines, whether automatically retrieved object numbers are reused, if these have not been recorded to the database.

AutoFree value of this property is used to ensure the numbering mode similar to 1C:Enterprise 8.0. Numbers and codes retrieved automatically will be further used, if the object, which these have been retrieved for, has not been recorded.

NotAutoFree value of this property is used to select the numbering mode, when the numbers for the objects requiring continuous numbering are be assigned the numbers when being recorded and when the form is opened.

If the object (document, catalogue item, chart of characteristic types, business process or task) number has been allocated in transaction, it will be reused even in case if the NotAutoFree automatic numbering mode is enabled, including if the object has not been recorded during transaction.

NotAutoFree autonumbering mode affects only numbers assigned outside of the transaction. If the number is assigned outside the transaction and the code is not used (the object was not recorded), the number is not used in the NotAutoFree mode again, but it will be reused in the AutoFree mode.

Modality usage mode. Specifies if it is possible to use the methods, causing the modal windows to open, in the application. If the property is set to Use, it is possible to use modal windows without any restrictions. If the property is set to Do not use, it is not possible to use the modal windows in this application. The error is returned when attempting to use the methods (including during syntax check in the 1C:Enterprise language). Blocking windows must be used instead of the modal windows. If the property has Use with warning value, errors will not be returned when using modal windows, but a message will be output to message window, that modal windows cannot be used in this mode. When using this mode modal windows must be replaced with blocking.

Stating with 1C:Enterprise version 8.3.5 behavior of thin and thick client applications slightly changes. The behavior described above (for thick and thin client applications) will be observed only if /EnableCheckModal 1C:Enterprise startup command line parameter is used. If this parameter is not specified, the modal methods remain operable regardless of the Modality usage mode configuration property. In particular, such behavior allows using external data processors, written without considering Modality usage mode property, in configurations, written with a glance to setting this property to Do not use.

If 1C:Enterprise is started from Designer, the /EnableCheckModal startup command line parameter is set forcibly without an option to configure such behavior.

Synchronous platform extension and add-ins call use mode. Property controls the feature to use the synchronous calls of file system extensions, cryptography and add-ins. If the property is set to Use, the synchronous methods for extensions and add-ins will be available on client side. If the property is set to Do not use, synchronous methods become unavailable in Syntax Assistant, context help when editing modules and the extended configuration check reports errors if client-side synchronous calls are detected. It is recommended to use asynchronous methods in this case. Synchronous methods that perform operations with extensions and add-ins generate exceptions in 1C:Enterprise mode. Use with warnings mode is an intermediate option, where the use of synchronous methods is allowed, however, each such method generates a warning both in 1C:Enterprise mode and during the extended configuration check. Thick client generates actual value of this configuration property. When using thick client all the synchronous methods are executed without exceptions and warnings.

When using web client, running in Google Chrome or Mozilla Firefox, the following behavior is implemented:

The property is set to Do not use, the file system and cryptography extensions, which are represented by synchronous methods, do not load. The extensions, represented by the asynchronous modes, are used.
In other cases, when connecting the file system and cryptography extensions loading of extensions representing the synchronous methods is attempted. If the attempt is successful, the possibility to use both synchronous and asynchronous file system and cryptography methods is provided. If the "synchronous" file system and cryptography extensions are not operable, the extensions that provide asynchronous methods will be used.

Note that the support for synchronous methods in Google Chrome became disabled by default in version 42 (April 2015) and was completely removed in version 45 (September 2015). Mozilla Firefox does not support synchronous calls in web browser starting from version 43 (December 2015).

At the same time the above behavior will be observed if the /EnableCheckExtensionsAndAddInsSyncCalls client application startup command line parameter is used.

If 1C:Enterprise is started from Designer, the /EnableCheckExtensionsAndAddInsSyncCalls client application startup command line parameter is set forcibly without an option to configure such behavior. The exception from above is starting the thick client, for which this command line parameter is not set when starting from Designer.

Interface compatibility mode. This property manages the client application interface mode:

Version 8.2. Client application runs in version 8.2 interface. Switching to Taxi interface is not possible. This mode is not supported when using the web client.
Version 8.2. Allow Taxi. Version 8.2 interface is used by default. It is possible to switch to Taxi interface using parameters dialog box, ClientSettings object or command line. This mode is not supported when using the web client.
Taxi. Allow Version 8.2. Taxi interface is used by default. It is possible to switch to version 8.2 interface using parameters dialog box , ClientSettings object or command line. This mode is not supported when using the web client.
Taxi. Client application uses Taxi interface. Switching to 8.2 interface mode is not possible.

When using version 8.2 interface it is possible to switch between the interface in separate windows and interface in tabs.

Only Taxi interface is supported in the wen-client. If another interface compatibility mode is set in the configuration settings with the help of the embedded language or startup command line command, these settings are ignored and Taxi interface will be used.

If the Compatibility mode property is set to a value greater than Version 8.3.2 (Do not use, Version 8.3.3 and later), and the Interface compatibility mode property is set to Version 8.2 or Version 8.2. Allow Taxi, then the interface in tabs will be automatically set for new application users.

PictureLib.Help image is displayed in many ways, if Interface compatibility mode property is set to Taxi or Taxi. Allow Version 8.2 and in other cases.

You can edit the Table space usage mode property only if the configuration compatibility mode is 8.3.22 or earlier. If the configuration compatibility mode is later than Version 8.3.22, you cannot manage the Table space usage mode property but you can always use table spaces.

If the Table space usage mode property is enabled, you can use the infobase only in 1C:Enterprise 8.3.23 or in later versions. If you want to use an infobase of version 8.3.22 or earlier, move all database objects to the default namespace and disable table spaces.

Compatibility mode. The property controls the behavior of features, which has been changed in the new system version in comparison to the previous versions. This property may have the following values: Version 8.3.22, Version 8.3.21 ‑ Version 8.3.1, Version 8.2.16, Version 8.2.13, Version 8.1, and Do not use.

Using configuration with unknown compatibility mode is not supported. Unknown compatibility modes are the modes, that do not match the functions, implemented in the following 1C:Enterprise versions. For example, if the compatibility mode is set to Do not use in version 8.3.1, it will be considered unknown when opening the configuration in version 8.2.16. At the same time, if the compatibility mode is set to Version 8.2.16 in version 8.3.1, then when opening the configuration in version 8.2.16, it will be displayed as Do not use. If the specific version does not introduce a new compatibility mode, the effect of the Do not use mode will be similar to the previous version. If attempting to run or load a configuration with the unknown compatibility mode, an error will be displayed indicating the required version. Importing 1cv8.dt files generated in version 8.3.1 and later into 1C:Enterprise versions prior to 8.3.1 is not allowed. The only exception is when the Compatibility mode configuration property is set to Version 8.2.16 in 1C:Enterprise 8.3.1 and later.

When converting configurations of the 1C:Enterprise 8.1 versions (and earlier), the property assumes the Version 8.1 value. In general case, it may be said that when a configuration is opened with a later version of 1C:Enterprise, the Compatibility mode property will be set to the compatibility with the previous version if such mode is introduced in the new version.

If it is necessary to ensure the operation of the application in several 1C:Enterprise versions at once (including for the ones with a compatibility mode), then it is recommended to first receive the current version of the platform in areas of different code calls and then compare it with the compatibility mode (if necessary). However, it is not recommended to check the compatibility mode for the DontUse value.

The mobile platform compatibility mode has several differences:

Mobile platform compatibility mode is not managed by configuration properties (including the Compatibility mode property). However, this property exists "inside" the mobile application.
The setting of the compatibility mode value is performed when creating the infobase. The compatibility mode value will correspond to the version of the mobile platform that was used to create the infobase.
Updating the mobile platform version does not update the compatibility mode value.
When updating the mobile application infobase configuration, the compatibility mode is set to a value equal to the mobile platform version that was used to update the configuration.
Accordingly, all the methods of 1C:Enterprise language the behavior of which considers the compatibility mode will consider the compatibility mode generated as per the above rules.

<< Prev Next >>