New Features in Version 8.3.24

Access to Clipboard via Code

In response to numerous requests from partners and users, the 1C:Enterprise language can now access the clipboard with code. The new functionality allows

• adding and retrieving text, images, and HTML documents to and from the clipboard;

• retrieving files from the clipboard as binary data;

• processing events of pasting images or files from the clipboard.

This feature should allow developers to implement various integration scenarios for office applications.

Outdated Versions Removal

You can now configure automatic removal of unused versions of the 1C:Enterprise platform. The process starts immediately after a user launches a thin or thick client to access the infobase. When the platform detects versions that are no longer in use, it displays a message requesting users to confirm the background removal. The removal is an individual process with low priority.

The mechanism parameters can be adjusted via the startup dialogue. You can

• specify versions that should never be removed;

• specify the versions to be removed if installed before the selected date;

• disable the removal mechanism.

The order of presentation of search results has changed. The new sorting algorithm compares the search phrase vs the object description. If an object has a date specified, the mechanism utilizes this info to define the object's relevance. Thus

• in documents, it is the date of the document;

• in periodic registers, it is the period;

• in other objects, the mechanism reviews attributes of type Date and picks the latest, earlier, or today's date.

Interface

• Tabular document cells can now include formatted strings. Use the context menu command or command bar button to switch to the formatted string mode. The improvement was introduced in response to numerous requests from partners and users.

• Expanded functionality for pie and donut charts include:

    o   option to set the depth for 3D charts (including 3D histograms);

    o   option to place captions immediately outside or inside sector boundaries;

    o   animation to display changes in chart values.

• External navigation links are now generated with the account of delimiters set in the session. This link lets you immediately access the required data area and open the desired form.

Binary Data Storage

• Binary data can now be stored on external storage that uses the S3 protocol, a.k.a. Simple Storage Service.

• The size of the data to be stored is decreased thanks to data deduplication, a compression mechanism that eliminates duplicate copies of data. The platform utilizes two deduplication methods: inline and post-processing deduplication. Inline deduplication occurs when the data gets written to storage. The system applies the process on the condition of a full-byte match. Post-processing deduplication is a background process that deals with the data already added to the storage. When processing, the system checks when the data was last accessed.

• Administrators can now utilize the following features:

    o   check the time a storage was cleaned up last time in order to schedule the removal of deleted objects;

    o   explicitly start storage cleanup to remove deleted objects;

    o   estimate the amount of data stored;

    o   retrieve information on the number of deduplicated items.

Collaboration System

• Several improvements were made based on the most popular requests from partners and users:

• Message status implemented: read, not read, read by some.

• The synchronization of conversation positions between different clients has been added. If, for example, you are using a computer and have a Collaboration System session open on your mobile, the conversation containing a new message goes up in the list not only on your computer (where the session is active) but also on the mobile.

• When interacting with WhatsApp Messenger, one can send not only text messages but also files, images, and videos.

• In video conferences, a speaking person is highlighted with a yellow frame.

• The sound quality for calls running within RDP sessions is improved.

New features:

• Breakpoint conditions can be defined per the name of a method located up the stack. The conditions are applied when the current procedure is called. The method name can be specified with a regular expression. With this, developers can, for example, activate breaks in a function or procedure only when these are called from a specific method.

• A breakpoint can be set to be triggered only after a specific number of hits to the string containing such a breakpoint. It can be helpful, particularly for debugging loops, when a break is only necessary at an exact loop pass.

• A message window can be displayed when a breakpoint is reached. A click on the message brings up the module section where the breakpoint is set. Also, the message can include a call stack and the number of breakpoint hits.

• Continue execution checkbox. With this item flagged, no actual stop will occur in the debugger after the breakpoint is triggered, and the code will continue. It is helpful when developers need only to output information into the service messages window for further analysis and do not need to stop the code execution itself.

• Option to move the breakpoint up and down the code with all specified parameters, as well as copy, cut, and paste it. It can be helpful during code modification when the string where we need to break code execution is moved above or below the breakpoint position. It is also useful for the quick creation of multiple breakpoints of the same type, for example, with the same message or condition.

• You can now add your own data sources and modify adopted ones.

• The procedure for infobase testing and correction has been improved so that it can be used for testing and correction of configuration extensions on a regular basis. The improvements include:

    o   option to run the procedure only for specific data areas;

    o   testing and modification of extensions no longer result in infobase exclusive lock.

Optimizations

• Infobase testing and correction mechanism requires less time to check infobase logical integrity when in client-server mode.

• The system requires less time to obtain a distribution address for updating a client application. As a result, the delays due to multiple user authorizations are a thing of the past.

• Designer operations Check modules and Check configuration... run faster.

• The network load when running a cluster of 1C:Enterprise servers is reduced due to cluster data cache.

• The upload of configuration into an infobase from XML files when using a standalone server is optimized. Once these changes are added in 1C:EDT, developers using 1C:EDT will notice a significant boost in the development–debugging scenario.

• The time of the first access to the extended layout of a tabular document containing several thousand rows is significantly reduced.

• In response to numerous requests from partners and users, you can now terminate your own sessions that interfere with accessing an infobase. For example, a user switches from one device to another, leaving the application running on the first one. On an attempt to sign in to the infobase, the user receives a message that all licenses are in use. Now, the user will see the list of his/her active sessions, terminate some or all of them, and sign in to the information database.

• The standard option for technicians Data change history now allows storing data history. This option can be accessed from the user interface. Also, it has no impact on configurations. Users can specify the objects to be included in the data history log or reset settings to defaults.

• Several improvements to simplify the installation of the 1C:Enterprise platform on Linux.

• Support for a certified CryptoPro CSP cryptographic protection tool to establish a secure TLS connection has been added.

• An option to customize the password policy for users of the configuration storage has been added.

• The procedure for initialization of the cryptography manager is now more straightforward.