Collaboration System

We have improved the collaboration system:

• Added support for video calls in the thin client on Linux and macOS. Previously, video calls on these operating systems were only available in the web client.

• Enhanced video call quality: improved sound quality and fixed issues where parts of speech would drop out after muting and unmuting the microphone.

• Pressing the microphone mute button now only stops data transmission rather than physically disabling the microphone, improving sound quality during video calls.

• Introduced a raise hand feature during video calls, allowing participants to signal their desire to speak without interrupting others. The number of raised hands is displayed on the screen, enabling voting.

• Added search functionality for contextual discussions. This search operates as part of the global search and displays results alongside other data, marked with a group discussion icon.

• If you integrate the collaboration system with WhatsApp, you can now initiate a conversation with a client first. Previously, you could only reply after the client messaged you.

WebSocket Client (New Mechanism)

You can now use built-in tools in 1C:Enterprise to interact with external systems via the WebSocket protocol. Previously, external components were commonly used for this purpose, which was not always convenient.

A 1C:Enterprise applied solution can act as a WebSocket client. To establish connections and interact, you can use the new WebSocket Client configuration object and new types added to the 1C:Enterprise language. WebSocket client connections can be created in the thick client, thin client, web client, and on the server.

A new function for technical specialists allows management of active WebSocket clients.

The WebSocket protocol is used for integration with telephony services, digital signatures, message brokers like RabbitMQ and ZeroMQ, and other services.

Email-Based Authentication (New Mechanism)

We have implemented a new authentication method using email verification. It works as follows:

     1. The user’s email address is stored in the user list.

     2. When choosing email authentication, the user enters their email address.

     3. If the entered address matches the stored address, the application sends a randomly generated login code to that email.

     4. The user enters the code and gains access to the infobase.

This authentication method allows users to log in without remembering a password (useful for infobases accessed infrequently). Another use case is requiring users to set their own password upon first login instead of sending them a predefined one.

Cluster Enhancements

We have improved cluster management:

• You can now assign specific clients to selected cluster servers. Users performing resource-intensive operations (such as cost calculation, payroll calculation, or period closing) can be connected to dedicated servers, preventing them from affecting regular users. Previously, the platform automatically assigned users without manual control.

• We introduced the option to schedule cluster process restarts. You can set a schedule for the entire cluster or specific servers, ensuring that restarts occur when no critical long-running operations (such as cost calculation or updates using Designer) are in progress. Previously, only a general process lifespan setting was available, leading to unpredictable restart times.

• You can now forcibly terminate specific working processes to resolve problematic sessions. Previously, these processes could only be terminated automatically after a set timeout.

Large-Scale Implementations

Changes aimed at large-scale implementations:

The Data Accelerator can now store data on disk, solving two problems:

• After a server reboot or failure, there is no need to reload data from the database, which can be time-consuming.

• The stored data can exceed the available RAM, improving system performance with faster startup times.

Increased the maximum number of records in tabular sections of configuration objects (for example, employee records in payroll calculation documents). The row number length is now configurable, supporting up to nearly a billion records instead of the previous limit of under 100,000.

Optimized PostgreSQL-based applied solutions under high load (many concurrent users and active use of temporary tables):

• Improved 1C:Enterprise platform interaction with PostgreSQL.

• Sped up all operations, especially after cluster process restarts.

• Optimized temporary table clearing, deletion, and index removal.

• Enhanced performance when working with temporary tables in Microsoft SQL Server under high load, reducing execution times for operations like document posting.

Database Copies

We have improved database copy management:

• The standard Database Copy Management tool now provides detailed information about database copies and update processes, including update status, copy state, disconnection reasons, errors, and estimated update duration.

• New methods have been added to the 1C:Enterprise language to retrieve this information for custom implementations.

• The algorithm for handling insufficient memory during complex queries has changed. Instead of immediate disconnection, the copy is disabled for 60 seconds before allowing queries again. If errors persist three times in a row, the copy remains disabled until a forced update.

Binary Data Storage

We have enhanced binary data storage management:

Administration and command-line tools now support:

• Retrieving information about configured storage.
• Creating full and differential backups of embedded storage.
• Restoring embedded storage from backups.
• Removing unused data from storage.

New 1C:Enterprise language methods allow similar operations.

Improved flexibility in placing and using binary storage on external cloud S3 resources, addressing bucket and transfer size limitations.

External Components

We have enhanced external component management:

• You can now forcibly terminate a session that has frozen due to an external component in isolated mode, freeing up the associated license.

• Asynchronous constructors are now available for creating external component objects, ensuring proper execution order in web clients.

Optimization

Reduced the first startup time of the thin client (in both 1C:Enterprise and Designer modes) in file-based infobases after:

• Creating a new infobase
• Loading a database from a file
• Loading a configuration from a file
• Updating a database
• Clearing the cache

Improved cryptography performance on Linux:

• Optimized certificate chain building for verification and signing.
• Enhanced configurability of certificate verification logic.

Optimized writing performance in embedded binary storage, improving:

• Large file creation (several megabytes) in single-threaded mode.
• Small file creation (tens to hundreds of kilobytes).

Accelerated full-text search indexing (Version 1), reducing index size on large databases and decreasing file operations.
Technological log cleanup now runs asynchronously in a separate thread, avoiding system slowdowns.
Improved Designer search performance for object references.
A full search index for refactoring is now prebuilt in a background thread upon Designer startup, speeding up search, rename, and delete operations.

Mobile Version

• Updated the target Android version to API Level 35 (Android 15).

Other Improvements

• If you use the Designer in agent mode and need to update a configuration that requires switching the infobase to exclusive mode, you can now specify a message explaining the reason for ending sessions, as well as forcibly terminate active sessions. Previously, these options were only available when running the Designer as an application.

• We introduced the option to define the validity period of a cryptographic private key, after which creating an electronic signature must be blocked.

• We changed how the information register manager saves records. Now, if only resources or both resources and attributes change, a single update (to the existing record) is written to the data history. Previously, in any scenario, the data history contained two changes: the old record was removed and a new one was added.

• In the Designer, you can now manage extensions for base configuration versions. Previously, this was only possible in batch mode, in 1C:Enterprise mode, or via the 1C:Enterprise language.

• A formatted string can now be used in the Data Composition System:

• In predefined templates
  In conditional formatting as text

• You can use 1C:Enterprise language functions that return a formatted string

• A formatted string can now be used as the parameter value for a table document cell

• The Autorun and SetupV8 applications now support delivering a configuration in ZIP archive format.

• We have added support for PostgreSQL 16.

• We have dropped support for Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008.

• We have raised the minimum supported Firefox version to 68 (previously 52).

Full List of Changes

You can view the full list of changes on the ITS portal, as well as in the V8Update.htm file.

In a standard Windows platform installation, the V8Update.htm file is located at:
C:\Program Files\1cv8\8.3.27.1326\docs\en\

In a standard Linux platform installation, the file is located at:
/opt/1cv8/x86_64/8.3.27.1326/docs/en/

In a standard macOS platform installation, the file is located at:
/opt/1cv8/8.3.27.1326/docs/en/