Test version of 1C: Enterprise platform 8.3.19
Let's start from the end: in June, a test version of the 1C: Enterprise 8.3.19 platform was released. The most important change, which can encourage the transition to the latest update of the 1C platform, concerns the optimization of the DBMS, namely the query that the system uses when accessing the virtual tables of balances and turnovers of the accounting register.
This call is reused in every system and affects a fairly large number of metadata objects, is used in most reports, as well as for the logic of documents posting. That is, query performance has been improved.
- , (). , , , – RLS. , .
- , , , .
- , - .dt-. , , .
:
- , , .
- , . .
- A useful change affected exchange plans: the methods RegisterChanges () and DeleteRegisterChanges () can now respectively register and delete changes for an arbitrary set of data objects. They are passed in the form of a specific parameter, the value of which is an array of data. The action for all objects in the passed array will be performed within one transaction with the minimum number of requests used. Now, for example, it is much easier to register / delete, for example, linked registers for directories or documents.
- Methods for forcing the display mode of the report execution result have appeared for reports.
The material was prepared with the support of the Telegram channel " News from the 1C World "
Announcement 8.3.20
The latest version 8.3.19, although still a test version, has become an important step towards the emergence of the "twenty", which promises to be the development of extensions: support for definable types, plans of characteristic types and general attributes.
This is what was often not enough for normal work with extensions when finalizing typical configurations, since some of the improvements had to be done in the extension, and some in the configuration itself, which did not add convenience. You will not have to change the procedures that described the types of configuration objects, for example, References.TypeAllRefs () .Types (), in a future version such methods will also include objects created in extensions.
It should also be possible to add your own predefined elements to your own extension directories. Now it will be easier to integrate them into your extensions and into standard BSP mechanisms, and, accordingly, into current 1C configurations using BSP.
1C: Artist (X)
In the first half of the year, 1C announced the development of the current version of "1C: Executor" - "1C: Executor (X)", which has an architecture that allows "1C: Executor (X)" to work as a "native" application in Windows operating systems and Linux (support for macOS is planned in the future), and does not require pre-installation of JRE.
Let me remind you that "1C: Executor" is the original cross-platform command interpreter of its own strongly typed and case-sensitive scripting language, which was released just a year earlier - in June 2020.
The delivery of "1C: Executor" includes its own integrated development environment "1C: Executor IDE", which is based on "1C: Enterprise Development Tools (EDT)". For "1C: Executor IDE" you need to pre-install the corresponding runtime environment - Java Runtime Envinronment (JRE), created specifically to run applications developed using the Java language.
As part of the product development strategy, the vendor announces its “accelerated” version, which it plans to develop in parallel with the “universal” one:
- "1C: Contractor (U)" - a universal (U - Universal) version of the product that requires Java to be installed;
- "1C: Executor (X)" - edition delivered as X - eXecutable file executable by the target operating system, only slightly inferior in functionality to the universal version.
The architecture of "1C: Executor (U)" is still the most optimal and efficient for executing scripts that require a large amount of computation.
Payment for the speed of 1C: Contractor (X) - no dynamic loading of the connected libraries. Accordingly, this feature of its implementation will not allow users to install and use them on their own.
Even in the release description when "1C: Contractor" was released, many developers noticed that the syntax of its language received significant differences from the built-in language of the 1C platform. Perhaps one of the significant differences is its strong / static typing, which is typical for compiled languages of a lower level.
In compiled languages, the requirements for determining the type of a variable at the stage of its declaration is necessary for the compiler to know in advance how much RAM it needs to allocate, thereby increasing the speed of execution of an already compiled program.
After the announcement of "1C: Contractor (X)", based on the declared scenario of its use, it is clear that the second stage in the product development strategy is also aimed at increasing the speed of operations and productivity. Nevertheless, in my opinion, the question of exactly what large volumes of computations the product is being prepared for remains open.
1C: KIP 2.1.8
1C has been actively promoting a package of tools for testing and improving system performance since the year before last. In release 2.1.8, the product developers focused their attention on "Scenario testing" (3.0.24.1), which now has the functionality that users have long awaited:
- You can create a series of "manual steps" with a corresponding description of the actions of each step.
- Test scripts can now automatically handle the appearance of dialog boxes by following predefined steps in the active Form.
- There are new types of steps:
- Run 1C batch command - allows you to execute 1C command line action packages;
- Perform file operation - automates interaction with the file system. - A new interface has appeared for comparing test scenarios, which allows you to visually see their similarities and differences.
Let me remind you that the previous version of the application received a tool for working with manual tests, which made it possible to "manually" develop a test plan and its structure, save and run tests as needed, but automatically generate reports based on the results.
In addition, the new update "KIP Agent" has received the ability for remote administration, and now it has access to remote collection of data, in particular, about installed versions of the platform and available databases.
1C: tester
For those for whom “Scenario testing” is too difficult and does not need it at all, we released a new configuration “1C: Tester”. It allows you, without programming knowledge, to quickly start testing small 1C systems using simple scenarios, setting simple testing situations.
The application will allow you to describe a scenario of a functionality test that simulates the progress of users' work, including those for working with external services, log work, and receive analytics on errors. An interesting opportunity for a very simple creation of scripts in manual or automatic mode, allows you to quickly configure and launch them, and modify them already in the course of execution.
Data Conversion 3.1
Here I will say briefly, version 3.1 has a number of advantages, the most important of which is the ability to develop rules in both EnterpriseData and XML formats. Now you can automatically:
- Load a description of the configuration / metadata (from the 1C storage, from the storage in EDT format, the catalog of the unloaded 1C configuration in XML files);
- Upload the developed exchange rules;
- Develop exchange rules (based on applications of the same type, where internal labels are compared).
Integration library with 1C: Document Flow 1.1.18.3
Let me remind you right away that this library is necessary for those who independently integrate the functionality of working with 1C: Document Management into their configurations and who need always up-to-date capabilities. Now in version 1C: ERP 2.5.6.17 the library version 1.1.15.1 is still built in, and in version 1C: ERP 2.5.7.78 even the previous version is 1.1.17.2. But in the new version of 1C: ZUP - 3.1.18, the ability to coordinate an application for recruiting through 1C: Document Flow has already been implemented, with which you can now set up seamless integration for this document.
1C: Application design system 2.0.2
In the new DSS, in the "Organizer" added no less than a system of planning and accounting of working time, as well as "My calendar". If you still don't have a planning and time tracking system, it's time to start using it in DSS. Several bugs have been fixed, however, there are only a few of them in this configuration.
Besides:
- Development and Testing have also undergone significant revision. Now it is possible to maintain various branches of development. Branches developed both in the configuration repository and in the git repository are supported.
- Added reading and writing of test scripts via the git server API. Now you can store test scripts in the context of git branches.
- In connection with the implementation in Branch Development, error registration has also been improved for this functionality.
- The mechanism for working with patches has been significantly improved.
- In the process tasks, each task has been added independent resources that do not depend on the parent task. In the previous version, it was only possible to distribute the resources of the parent task.
- It is also now possible to load data on the result of assembly execution on the CI server into the DSS. Added reports to represent the loaded data.
As we can see, 1C “does not sleep”, although, as a rule, all the most significant updates come out in the second half of the year. Well, let's wait for the news.
To keep abreast of the latest innovations and regularly monitor new 1C technological tools, subscribe to the Telegram channel " News from the 1C World ", which publishes really important news with expert comments.