1C:Enterprise Development Tools 1.16.0.363 is available

1C:Enterprise Development Tools is an integrated new-generation environment for the development of 1C:Enterprise business applications. You can use 1C:EDTools alongside with 1C:Enterprise Designer. Applications developed with 1C:EDT are fully compatible with the latest 1C:Enterprise versions. Its advantages are compliance with the latest demands and requirements, and rapid evolution and enhancement capabilities for the development environment.

We optimized some often used operations, implemented a search among predefined elements, a search by the configuration object composition, switched EDT to a new Java version, improved configuration comparison/ merge, as well as implemented SVG-image displaying in the form’s preview mode in the version 1.16.

What’s new in 1C:Enterprise Development Tools 1.16:

• Optimization

1) Faster opening of large modules (more than 20 000 lines) and entering of text in such modules.

2) Improved productivity of 1C:EDT when working with several large configurations (such as 1C:ERP) in a single work area.

3) Faster request designer opening.

4) Faster search by exchange plan composition.

• Search for predefined elements

Now a user can search for some predefined elements when working in the configuration object editor on the Predefined bookmark. This functionality will be useful, for example, when editing a chart of accounts or charts of characteristic types.

• Search by the configuration object composition

We also added a searching feature in those configuration objects that have a Structure:

1) Subsystem

2) Functional option

3) Exchange plan.

• Java 11 support

Now 1C:EDT requires installed 64-bit Java Platform, Standard Edition version 11. In some cases, it is necessary to manually edit the 1cedt.ini file after installation of Java 11, learn more about it.

* Note: Most likely, EDT supports Java 12 and Java 13 but we didn’t carry out detailed testing for these versions.

Thanks to switching to Java 11, it will be easier for us in the future to support new Java versions.

• Reordering in the composition of configuration objects

Now 1C:EDT takes into account reordering of elements, included in the composition of subsystems, functional options, and exchange plans when comparing Git branches and receiving changes from the infobase in the project. Previously, EDT didn’t take into account such reordering – if the second source had some distinct order, it had no effect on a result.

Reordering of predefined elements of some configuration object is also taken into account. In the previous versions, not all objects could do this.

• Applying of reordering when merging

A user now can either apply a new order of merged catalogs, documents and attributes or refuse it. For this, a user will have two merging modes to choose: Take the order on the right or Do not change the order.

In future versions, we are going to implement the same feature for applying an order for other configuration objects as well.

• Merge of attributes of a composite type

We implemented an automatic merge of attributes of a composite type in case the type description is changed both in the main and in the second sources. Previously, in this case, a conflict change was detected. Now such changes are considered conflict if it is not possible to automatically merge them, and EDT requires the developer’s intervention.

In other cases, there will not be any conflict, and changes will merge automatically. It is convenient since the independent extension of a composite type in the main and in the second sources is quite an often scenario.

• Modules with conflict and non-conflict changes

If there are both conflict and non-conflict changes in the module at the same time, there will be a rule set by default for such modules. This rule, Merge with priority for the main source, allows automatic acceptance of all non-conflict changes on the right.

Previously, in this case, the Do not merge rule was set, then a user had to manually fill the checkbox for merging.

• Modules without text

Now, when comparing, there is the difference between a non-existent module and an existent module without any text. So, for example, if the main configuration has no modules, but the second configuration has a module without text, a user will see this difference when comparing. In the case of merging, the empty module will be added to the main configuration.

Previously, such situations were considered equivalent, and EDT didn’t add the empty module.

• Changing of UUID-objects as a result of a merge

Now, when comparing, a user will see the changes of UUID objects. Previously, UUID changes were neglected, and it was not available to ‘bring’ the object’s identificator from the 2nd source to the merge result.

Now there is such a feature, so a user can on his own permit or prohibit UUID object changing as a result of merging.

• “Show potential problems” filter

We added a new filter to the editor of configuration comparison/merge and named it Show potential problems.

Potential problems are conflicts and problem nodes. Problem nodes are those nodes that can lead to a ‘crash’ of the configuration as a result of a merge.

At present, there is only one situation that makes a node problem – UUID object changing. We cannot exclude that there will appear other situations in future versions in which nodes also may become problem.

• SVG-images in the form’s preview

This EDT version makes it possible to display SVG-images in the form’s preview panel when editing the form.

To evaluate new functionalities, please enter your 1С:Developer Network account and download 1C:Enterprise Development Tools v. 1.16.0.363