New Features in Version 8.3.26

Collaboration System

We continue to enhance the Collaboration System. Version 8.3.26 includes several new features:

Optimized search within the discussions list.
Webhook integrations now support data transfer.
Reduced the likelihood of conflicts when multiple users simultaneously change the list of discussion participants.
Set a 45-second timeout for accessing the Collaboration System server.
Reduced the video server's reaction time to bandwidth limitations, improving the stability and quality of video calls.
Added automatic microphone volume adjustment, enhanced echo cancellation, and improved noise reduction for better sound quality in video calls.
Simplified the process of selecting a window or screen for sharing.
Improved screen sharing performance for users with low bandwidth connections.
During screen sharing, you can now:

Share individual windows instead of the entire screen.
Hide pop-up messages.

You can now generate an invitation link for external or internal users to join a discussion or video call. The invitation link provides access to the discussion's video room without calling the user and, if no restrictions were set when creating the link, grants access to the specific discussion. You can also create a link to the current video call.
Enhancements for discussions with a large number of participants:

Added a search function to the participant list.
In discussions with over 100 participants, a link is displayed instead of the full participant list, allowing you to open the complete list.
You can now create read-only discussions. Adding a message to such a discussion is possible using the 1C:Enterprise language.
The maximum number of discussion participants is now limited to 3000.

Reduced processor and network load during video calls for thin client and web client users. The load will no longer depend on the number of call participants.

Client Notifications: A New Mechanism

This new mechanism allows developers to send notifications from the server to client sessions. This improves system performance by eliminating the need for client applications to constantly poll the server to determine if an operation has completed.

Previously, this task could only be accomplished using the Collaboration System, which was complex and not always available in 1C:Enterprise applications. This new mechanism provides a simpler solution without relying on the Collaboration System.

Authentication

Expanded authentication capabilities:

You can now authenticate in a 1C:Enterprise application without a password by scanning a QR code. This is particularly useful in public environments (internet cafes, public Wi-Fi) where entered passwords could be observed by others or intercepted by malware. Here's how it works:

1. Authenticate in the mobile app.
2. To log in to the same application from a browser on a desktop computer, open a link in the browser.
3. In the authentication form, select login via QR code.
4. Scan the QR code with your mobile device.
5. 1C:Enterprise authenticates the user, granting access to the application on the desktop computer.

The authentication form has been redesigned to display all available authentication methods for the infobase. This simplifies switching between different methods and adding new ones.
You can now save the last successful authentication method in the infobase to automatically log in using the saved authentication data.
Added a search function to the participant list.
In discussions with over 100 participants, a link is displayed instead of the full participant list, allowing you to open the complete list.
You can now create read-only discussions. Adding a message to such a discussion is possible using the 1C:Enterprise language.
1C:Enterprise can now check the password when it is set or entered during authentication. This prevents users from setting easily cracked passwords (e.g., Password1). The password check can be performed against: a standard list of weak passwords included in 1C:Enterprise, an external public compromised password service (e.g., Have I Been Pwned), a custom list loaded from a file. Based on the check results, you can configure 1C:Enterprise to:

Allow login to the application.
Suggest changing the password. The user can still log in with the old password if they decline.
Require changing the password before allowing login.

The 1C:Enterprise application can now automatically end a session after a specified period of user inactivity.
You can now choose the algorithm used to hash user passwords for storage in the database: SHA-1, SHA-256, SHA-512, or PBKDF2-HMAC-SHA256. Previously, only SHA-1 was used.

Event Log

We have improved the event log to enhance corporate implementations:

Expanded logging of administrative actions.
Added logging of changes in permissions in roles and changes in user access rights.
Events about configuration changes now record a list of changed objects.

Cluster

We have made improvements to server cluster functionality:

You can now store cluster service data in different directories, instead of being limited to a single directory. This simplifies cluster management.
Connection break tracking parameters can now be configured without restarting the cluster.

Database Copies

We have introduced enhancements for managing database copies:

Implemented parallel updating of copy instances in background jobs. This will reduce the total update time for a copy consisting of multiple instances.
Added protection against using one physical database by multiple copies of an infobase.
If a non-critical exception occurs during query execution on a copy, the copy is no longer disconnected, as it was before. Other queries will be able to execute on this copy.

Binary Data Storage

We have enhanced binary data store functionality:

Implemented parallel storage of binary data in the built-in store and in the infobase. This uses a new block storage mode that allows storing binary data of any size in the database. If the servers hosting the built-in store fail, binary data operations will continue, using the database.
You can now select the object configuration details whose binary data will be placed in the store. Previously, all data exceeding the specified size was placed in the store.
We have improved the diagnostics of errors detected during testing and correction of the store.

Configuration Extensions

We have expanded configuration extension capabilities:

You can create custom document logs. These can register both custom and borrowed documents.
You can change the composition of borrowed XDTO packages.
For borrowed web services, you can change the composition of their XDTO packages.

Performance Optimizations

We have optimized the following in the server cluster:

Session data management.
Event logging in the technology log.
Server operation with a large number of cores.

We have optimized the cyclic reference check operation in the 1C:Enterprise language.
You can now create additional indexes for configuration objects. This will improve the performance of applied solutions in large deployments.
We have added new data writing modes to subordinate information registers and accumulation registers: merge, delete, and update. This will improve register performance:

In merge mode, new records are added, and existing records whose key field values match those being written are updated.
In update mode, new records are not added. Only existing records whose key field values match those being written are updated.
In delete mode, records whose key field values match those being written are deleted from the register.

Many configuration object managers now include a new method for retrieving a selection of data based on a specified set of references. This will increase the speed of batch processing of database objects.
In some scenarios, we have sped up the initial filling of a database copy.
In the client-server mode, we have reduced the time it takes to restart the client application from Designer.

Mobile Version of 1C:Enterprise

We have increased the target Android version to the current version: 14 (API level 34).

Other Improvements

If updating the client application through a web server is configured and the versions of the thin client and server do not match, the update download now starts immediately, without unnecessary questions for the user. This simplifies user work.
In the 1C:Enterprise language, you can now:

Get the dimensions and orientation of PDF document pages.
Manage archives in GZIP, RAR, 7-ZIP, XZ, and TAR formats.

The settings for the standard Data Change History function have been simplified.
You can now use an attached electronic signature, which is required for compliance with legislation. Previously, this type of electronic signature was not supported.
1C:Enterprise applications running on Linux now utilize the WebKit2 library included with the Linux distribution. Previously, the outdated WebKit1 library, which was supplied as part of the 1C:Enterprise platform, was used.