This article is an announcement of a new feature.
It is not recommended that you rely on this article to learn how to use the feature.
The new feature will be described in detail in the documentation for the appropriate version.
For a complete list of changes in the new version, see the v8Update.htm file.
Planned for version 8.3.22
We continue to develop extension features based on requests of our partners and users.
In the current version, only templates of the "Spreadsheet document" type can be replaced.
Replacing both common and metadata object templates in extensions will become available in version 8.3.22. In 1C:Enterprise mode, in the configuration with extensions, previously implemented strategies (merging or replacement) will be applied for templates of the "Spreadsheet document" type. The template from the most recently used extension will be applied for other types.
Changing properties that contain strings to be localized
In versions before 8.3.22, properties that contained strings to be localized could not be changed.
It will be possible in version 8.3.22. You will be able to change the following properties:
- Editing format
- Command tooltip
- Extended presentation
- List presentation
- Extended list presentation
- Object presentation
- Extended object presentation
- Record presentation
- Extended record presentation
This way, you will be able to adapt the configuration for specific deployments using extensions. For example, create a note or a tooltip to match certain deployment specifics and so on. Moreover, you will be able to change a property in all configuration languages.
Checking methods upon extension applicability verification in Designer
Sometimes the number of method parameters can change in a new version. If such method is redefined in the extension, the extension method cannot be executed and the configuration method is executed instead.
In some cases, a method can be deleted from the configuration. If such method is redefined in the extension, the code of the redefined method will never be executed.
Extension developers need to track such situations and deal with them in a certain way.
If such situations arise in the current version, a warning that an extension method failed is displayed only in 1C:Enterprise mode and only when the main configuration method is called. It makes finding and fixing such methods more difficult for extension developers.
In version 8.3.22, such methods will be checked in Designer mode. Two checks for methods that are not standard event handlers will be added to the "Extension applicability verification" command:
- Checking whether the method specified in annotation exists in the main configuration.
- Checking whether method parameters in the extension match parameters in the main configuration (number and pass-by-value modifiers).
Adapting extensions in case of changes in the main configuration will be easier for developers.