Version 8.3.24
Version 8.3.24 includes known bug fixes and functionality modifications.
- New functionality and changes
- New functionality and changes in the 1C:Enterprise mode
- Optimization
- Changes that affect system behavior
- Changes that require modification of configuration and administrative settings
- Renamed objects
- Mobile version of "1C:Enterprise"
- Transition from the previous version to the version 8.3.24
New functionality and changes
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | New value for the Compatibility mode configuration property: Version 8.3.23. | Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.22 was available. | You can run configurations developed in versions 8.3.23 and earlier in version 8.3.24 without changing the configuration and data structures. This way, you can migrate to version 8.3.24 without changing the configuration, then make required changes, and disable compatibility mode. You can also use version 8.3.23 after migration to version 8.3.24. You can do it both before you disable compatibility mode and after you enable it again. |
| Internet-enabled functionality. | Now you can use CryptoPro to establish a secure HTTP connection. You can manage the check mode of server certificate revocation using 1C:Enterprise language. New object: CryptoProSecureConnection. New system enumeration: ServerTLSCertificateRevocationCheckMode. New property: OpenSSLSecureConnection.ServerTLSCertificateRevocationCheckMode. New parameter for the OpenSSLSecureConnection object constructor: ServerTLSCertificateRevocationCheckMode. New feature: the HTTPConnection object constructor can get the CryptoProSecureConnection object as a SecureConnection parameter value. | Previously you were unable to use CryptoPro to establish a secure HTTP connection. Managing the check mode of server certificate revocation using 1C:Enterprise language was unavailable. | Advanced secure HTTP connection features. |
| Speech recognition. | Now you can restrict local speech recognition for 1C:Enterprise system using the following tools:
|
This feature was not provided. Previously you were unable to restrict local speech recognition. | Now you can forcibly restrict local speech recognition. However, you can still use remote speech recognition. |
| Binary data storage. | Now you can use any external data storage accessible over Amazon S3 as a binary data storage. New global context property: BinaryDataExternalStorages. To access the settings of a binary data storage and an external binary data storage, the Administration right is required. The standard function of binary data storage management is now improved. | This feature was not provided. Previously you were able to store binary data only on the computer running 1C:Enterprise server cluster. | Advanced binary data storage features. |
| Binary data storage. | Now you can eliminate duplicates of repeating data (deduplication). Deduplication occurs both when writing data and in the background. New properties for the BinaryDataStorageInformation object: StoredDataSizeOnDisk and DeduplicatedItemsCount. | This feature was not provided. | A binary data storage can take up less disk drive space if the same data is placed in the storage. |
| Binary data storage. | When using a binary data storage, you can now do the following:
|
These features were not provided. | Advanced administration features of the binary data storage. |
| Standalone server. Binary data storage. | Now the standalone server supports binary data storages. New --binary-storage-data command is implemented for the command line of the standalone server startup. | This feature was not provided. | Now the standalone server allows using binary data storages. |
| Using the clipboard. | Now you can use the operating system clipboard. New global context property: ClipboardTools. New event handlers for the application module and the client application form module: OnPasteFromClipboard. New methods for the FileRef object: GetAsStringAsync() and GetAsBinaryDataAsync(). The clipboard is unavailable on mobile devices. | This feature was not provided. | Now you can use the clipboard of the current operating system. |
| Administration tools. Configuration extensions. | Now you can restructure tables of infobase configuration extensions while verifying and repairing the infobase: New item in the Verify and repair infobase dialog box: Restructuring of configuration extension tables. New parameter for the /IBCheckAndRepair command of Designer batch mode: RebuildConfigurationExtensions. If the verification process detects that there is no extension table, such table will be created if the verification and repair mode is enabled. | This feature was not provided. | Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features. |
| Administration tools. Configuration extensions. | Now you can verify and repair an infobase in specific separated infobase areas: New capabilities in the Verify and repair infobase dialog box: you can specify data areas for running verification and repair. New parameter for the /IBCheckAndRepair command of Designer batch mode: -Z. It allows you to specify data areas for running verification and repair. If no separators are specified, the verification and repair operation is performed for the entire infobase. | This feature was not provided. | Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features. |
| Administration tools. Configuration extensions. | If only the Check logical integrity of configuration extensions or Restructuring of configuration extension tables parameters are selected when you configure infobase verification and repair, exclusive mode for the entire infobase is not required and not set.
The following locks are set for each processed area:
|
This feature was not provided. | Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features. |
| Collaboration system. | Now you can exchange files with WhatsApp if the collaboration system is integrated with it. | This feature was not provided. | Advanced features for integration with instant messaging systems. |
| Configuration extensions. External data sources. | Now you can create your own external data sources:
|
This feature was not provided. | Advanced configuration extension features. |
| Development tools. | New features for a conditional breakpoint when debugging applications:
|
Previously the dialog box for editing conditional breakpoints contained only a simple string for editing the breakpoint condition. When you pressed F9 on a disabled breakpoint, the breakpoint was deleted and all the settings were lost. You were unable to transfer breakpoints using the keyboard, the mouse, and the clipboard. | Simplified application debugging. Extended breakpoint capabilities. Enhanced setting of conditions for conditional breakpoints. |
| Charts. Data composition system. | Changed the display of pie and doughnut charts, including 3D charts. Now you can manage the display of pie and doughnut charts. When rendering pie and doughnut charts, the value of the LabelLocation property is applied. New properties for the Chart object: BeginAngle, EndAngle, and Chart3DDepth. For the Chart.LabelLocation property, the default value will be Auto. New properties for the DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance data composition system objects: ChartType.BeginAngle, ChartType.EndAngle, and ChartType.Chart3DDepth. This change is not implemented in version 8.3.23 compatibility mode. | These features were not provided. For the Chart.LabelLocation property, the default value was Edge. | Advanced display features for pie charts. |
New functionality and changes in the 1C:Enterprise mode
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Standard functions. | Now you can manage the history usage settings of the standard Data change history function. | This feature was not provided. | You can manage the data change history directly from the standard function without any third-party tools. |
| Collaboration system. | Now you can mark messages as read in collaboration system conversations. You can see the mark in a thin client, a thick client, and a web client. In a mobile client, the mark is not displayed. However, other client applications show that a message is read in the mobile client.
You can see the read status in context conversations where the number of message senders and recipients is less than 100. You can also see the read status in noncontext conversations where:
|
This feature was not provided. | Collaboration system conversations are now more user-friendly. |
| Collaboration system. | When you send a message in a noncontext conversation, the conversation moves to the top in all your sessions in the infobase. This change is implemented in the thin, thick, and web clients. | Previously, the order of your noncontext conversations in several sessions could differ. | Collaboration system conversations are now more user-friendly. |
| Web services and HTTP services. | Now you can specify how many background jobs must run to perform the initial population of copy tables for the standard function of database copy management. New parameter in the Database copy parameters form: Number of filling jobs. | This feature was not provided. Previously the initial population of copy tables required four background jobs. You could not change this number manually. You could only use 1C:Enterprise language for this purpose. | Now the administrator can manage the volume of the initial population of database copy tables. |
| Technological log. | When you run thin and thick client applications, you can now generate a technological log using the video module of the collaboration system. You can also generate abnormal termination dumps for the video module. You can configure it using the standard file for the technological log setup: logcfg.xml. If you use 32-bit 1C:Enterprise running on a 64-bit operating system, you cannot use an external application to create abnormal termination dumps. Abnormal termination of the video module is dumped during the process. New technological log events: <VIDEOCALL>, <VIDEOCONN>, <VIDEOSTATS>. | This feature was not provided. | Now you can send the information to the technical support easier and faster when you face any issues with the video module of the collaboration system. |
| Administration tools. | Now installed platform versions can be deleted automatically. They will be deleted with a separate process with a lower priority. The deletion process will not affect your operations. You can set up the parameters to automatically delete versions in the dialog box of the interactive launcher setup. Now you can specify one or several system versions that must not be automatically deleted. New parameters for the 1cestart.cfg and 1cescmn.cfg configuration files: AutoUninstall, AutoUninstallAfter, DontUninstallVersion. | This feature was not provided. Previously you had to delete unused versions manually or write batch files to delete them. | Simplified system administration in terms of deleting 1C:Enterprise versions that you no longer use. |
| Web client. | When you perform some long-running operations in the web client, the mouse cursor switches from the main mode to "busy". | In the web client, the cursor was always in the main mode. | The web client is now more user-friendly. |
| Configuration extensions. Spreadsheet documents. | Now it is faster to receive a template that was extended with multiple configuration extensions for the first time. The extended template is cached for further use. The cache is stored until you change the template to be extended or the extension that contains an improvement for this template. | Previously, the first receipt of a template extended with multiple configuration extensions took more time. | Templates that are extended with multiple configuration extensions are now faster and easier to use. |
Optimization
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Database copies. | Initial population of a database copy for metadata objects with tables is now faster. | Initial population of a database copy for metadata objects with tables took more time. | Initial population of a database copy for metadata objects with tables is now faster. |
| Server clusters. | Server cluster computers (network, RAM, and CPUs) have become less loaded when there are many users. The server cluster is now more stable. | When there were many users, the server cluster consumed more RAM, CPUs, and network connections. | Improved server cluster stability in configurations with a large number of users. |
| Server clusters. Administration tools. | Optimized logical and referential integrity check in client/server mode when verifying and repairing infobases. New parameter for the /IBCheckAndRepair command of Designer batch mode: -JobsCount. It identifies the number of system background jobs used for infobase verification and repair. | Infobase was verified and repaired sequentially by infobase tables. | Infobase verification and repair now take less time. |
| Collaboration system. | Improved sound quality during video calls. | Sound quality during video calls was worse. | Improved sound quality during video calls. |
| Full-text search. | Improved relevance of full-text search results. For this upgrade to take effect, clear the full-text search index and recreate it on platform version 8.3.24. 1C:Enterprise platform versions 8.3.23 and earlier will clear the index if it was built by platform version 8.3.24. | Previously, full-text search returned results ordered by a set of criteria that ensured low result relevance. | Improved relevance of full-text search results. |
| Full-text search. | Data indexing by full-text search now takes less time. The size of intermediate files used for indexing is reduced. | Data indexing for full-text search took more time and required more space for temporary files used for indexing. | Data indexing for full-text search takes less time. |
Changes that affect system behavior
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| DBMS operations. | Now you can terminate unnecessary sessions of a user and continue the current session after user authentication. You can do it if there are other sessions of this user in this infobase after authentication and you cannot start a new session without closing them.
This feature is implemented after authentication is fully completed in the following situations:
|
This feature was not provided. | Simplified solution of issues that arise during user authentication when limiting the number of sessions after an unnecessary application freezes, crashes, or is unavailable. |
| Dumping configurations to files/Restoring configurations from files. | The format version of configuration dump to XML files is 2.17. | The format version of configuration dump to XML files was 2.16. | Configuration dump to XML files supports new platform features. |
Changes that require modification of configuration and administrative settings
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Linux. | 1C:Enterprise installer for Linux is supplied in a zip archive. The archive includes the installAsRoot application, which allows you to easily perform installation on behalf of the superuser (root). During the installation, an attempt is made to install all the Linux components necessary for the platform to run. If the attempt fails, the batch manager message is displayed as an error message. During the installation, only one shortcut to the interactive launcher is created. To create other shortcuts, use the Create shortcuts launcher option or the desktops_icons parameter of the batch system installation. During the installation, a platform uninstaller shortcut is created. Shortcut names created by the installer became shorter and better reflect the actions the shortcuts perform. Shortcut names are now displayed in several lines. | Previously it was more complicated to install 1C:Enterprise on Linux. The installer did not attempt to install the Linux components necessary for the system to run. Error messages displayed during the installation were not clear enough. | Simplified installation, startup, and uninstallation of 1C:Enterprise on a computer running Linux. |
| Standalone server. | During database configuration update, the standalone server outputs the ID of the new infobase generation to the standard output stream.
New feature: mode of partial import of external properties for selective metadata object import from xml files. In this mode, you do not need to import metadata objects these properties belong to. You can also import form modules without importing the forms. New partial parameter for the following commands:
|
This feature was not provided. | Database configuration update by a standalone server is now faster in some scenarios. |
| Navigation links. | URLs generated with the GetInfoBaseURL() method in the URL receipt dialog box with the selected External link checkbox contain separators that you can use in the current session of the separated infobase. If you receive a link in the web client or thin client connected via the web server, the URL will contain separators that do not generate the infobase address. You can specify the separators similarly to the Z command-line option of the client application startup. When you start the client application with the URL parameter, the application searches for the client application based on the separator values specified in the URL. Similar actions are performed when you follow an external URL from the Go to link dialog box, from the global search string, and using the GoToURL() method. This change is not implemented in version 8.3.23 compatibility mode. | URLs generated with the GetInfoBaseURL() method in the URL receipt dialog box with the selected External link checkbox did not contain values of the current session separators for the separated infobase. | When you follow an external URL generated in a separated infobase, the values of the separators that were used in the session where the URL was received are considered. You will open objects in the same data area where you received the URL. |
| Dynamic lists. | Now you can exclude fields that are of the flexible type and contain more than 100 types from the list of dynamic list fields that can be used to order the list. This upgrade is ignored in 8.3.23 version compatibility mode. | The list of fields that you can use to order a dynamic list was not limited by the size of the flexible type of a dynamic list field. | Now when you configure a dynamic list, you are less likely to create a sorting that will slow down the dynamic list operation or lead to the list malfunction. It can happen due to a DBMS error that occurs when you try to display the list. |
| Data display. Client application form. Spreadsheet document. | In spreadsheet documents, you can use formatted strings in cells and drawings. Now you can export such spreadsheet documents to the following formats:
|
This feature was not provided. | Now you can improve spreadsheet document appearance. |
| Configuration repositories. | Now you can set up the configuration repository so that it is required to specify a password when creating a user. The repository creation assistant now has a page with password requirements: minimum password length and password complexity check. You can edit these parameters in the repository administration dialog box. If you specify the minimum password length as 0, it will be possible to create users without entering a password. In the repository user list, you can see a column with all user passwords. New parameters for the /ConfigurationRepositoryCreate command of Designer batch mode: -MinPasswordLength and -CheckPasswordComplexity. New parameters for the global cfgrepo.conf settings file of the configuration repository: cfgrepo.users.minPasswordLength and cfgrepo.users.checkPasswordComplexity. It is recommended that administrators of configuration repositories analyze user lists in repositories they administer and set passwords for all users. | You were unable to set up the configuration repository so that it required a password when creating a user. | Now it is less likely that any repository user without a password changes the configuration located in the repository. |
| Data history. | Changes made in the OnWrite() event handlers are not included in a data version to save. | A data version that was saved to the history included changes made in the OnWrite() event handlers. | Eliminated unexpected system behavior. |
| Cryptography support. | Now it is easier to initialize the cryptography manager. You can use the cryptography manager wizard where you need to select only the interactive mode. Parameters for each operation are identified by the operation context. Now you can specify encryption, hash, and signature algorithms that you will use to perform an operation using the OID algorithm. You can still specify algorithms by naming them but OID is better for clear identification. Now you can set the priority for hash and encryption algorithms. New properties for the cryptography manager: HashAlgorithmDefinition and EncryptAlgorithmDefinition. Now you can receive certificates not only from encrypted or signed data but also from an arbitrary certificate storage. New methods for the cryptography manager: GetCertificates() and GetCertificatesAsync(). Do not use the following methods as they are outdated: GetCertificatesFromSignature(), GetCertificatesFromSignatureAsync(), and BeginGettingCertificatesFromSignature(). Now you can search for a key container for the used certificate on the local computer. New methods for the cryptography manager: FindKeyContainer() and FindKeyContainerAsync(). Now you can specify a certificate and an access password to the private key that can be used to decrypt data. New parameters for the Decrypt(), DecryptAsync(), and BeginDecrypting() methods: Certificate and PrivateKeyAccessPassword. New property: CryptoModuleInformation.CryptoModuleType. | Previously, you had to specify a cryptography module name, type, and path when initializing the cryptography manager. You were able to specify algorithms used for an operation only by the name. You were unable to specify the priority for hash and encryption algorithms. Algorithms specified in the cryptography manager methods could be ignored when performing an operation. You were unable to receive a list of certificates from encrypted data. You were able to receive the list only from the data signature (the GetCertificatesFromSignature(), GetCertificatesFromSignatureAsync(), and BeginGettingCertificatesFromSignature() cryptography manager methods). You were unable to check whether there was a key container for the used certificate on the computer. When you decrypted data, you could specify only one recipient of decrypted data. | Simplified operations with the cryptography manager in main scenarios. |
| Standalone server. | Removed the following standalone server parameters:
|
Previously the standalone server parameters mistakenly specified that users could set a password to access the debug server on the standalone server. The specified password was never used. | Eliminated the error in the standalone server parameters. |
Renamed objects
| Object | The old name | The new name |
|---|---|---|
| English name of the NotifyDescription parameter in 1C:Enterprise language methods. |
|
|
Mobile version of "1C:Enterprise"
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile platform. Mobile application builder. | Now compatibility mode processing in the mobile platform corresponds to the similar platform behavior on a personal computer. Designer exports information about the configuration compatibility mode to the 1cema.xml and 1cemca.xml files. The mobile application builder considers the compatibility mode when building mobile applications. If the configuration compatibility mode does not correspond to the mobile version used to build the mobile application, the build will be completed with errors. | Previously, the compatibility mode depended on the version of the mobile platform where you initially created the infobase or updated the configuration. The mobile application builder did not check the compatibility mode between the configuration and the mobile platform used to build the mobile application. | Eliminated unexpected system behavior. |
| Mobile platform. Mobile client. | Mobile platform and mobile client with standalone mode now support type collections. | This feature was not provided. | Advanced 1C:Enterprise mobile platform features. |
| Mobile platform. Mobile client. Mobile device-specific features. | The mobile platform and the platform for a personal computer are now available on the server for the following objects: MultimediaData, DocumentScanningQualityParameters, and DocumentScanningPage. | This feature was not provided. | Simplified operations with documents that are scanned not to be sent to the recognition service but to be saved to the infobase. |
| Mobile platform. Mobile client. Mobile application builder. Mobile device-specific features. | Now the mobile version of 1C:Enterprise supports Huawei Mobile Services (HMS). You can use the map and get an address by coordinates and vice versa, use geolocation zones, notifications, ads, and in-app purchases. New system enumeration value: DeliverableNotificationSubscriberType.HPK. New parameter for the GetAccessToken() method of the manager for sending deliverable notifications: SubscriberType. The method contains three parameters now. The GetAccessToken() method with two parameters is now outdated. New system enumeration value: InAppPurchaseService.HuaweiInAppPurchase. In the mobile application builder, you can now specify which services the built mobile application will support (including the ability to disable both services). If both service sets are used on a mobile device, the Google service set has the priority (you cannot set the priority). Now you can disable both service sets if the built application does not use the mobile service features (the built application size will decrease). You cannot publish the built application to the Huawei AppGallery store from the mobile application builder. | Previously, Huawei Mobile Services (HMS) were not supported in the mobile version of 1C:Enterprise. You were unable to use the full mobile version capabilities on Huawei devices. | More mobile services are now supported. |
| Mobile client. Speech recognition. | Now you can use speech recognition in the mobile client (including in standalone mode). Speech recognition is not supported on mobile devices. Server methods of speech recognition are not supported in the mobile application server and the mobile standalone server. New functionality: SpeechToText. If this functionality is not required in the application you build, an attempt to access the speech recognition tools in the built application will cause a runtime exception. | Speech recognition was not supported in the mobile client. | Advanced 1C:Enterprise mobile client features. |
| Mobile platform. Mobile client. System requirements. | Android 13 is now supported in the mobile 1C:Enterprise version. Android 4.4 is no longer supported in the mobile 1C:Enterprise version. The mobile 1C:Enterprise version supports Android versions 5.0-13.
For mobile applications running on Android 13 or later:
|
Previously the mobile 1C:Enterprise version supported Android versions 4.4-12. | Now the mobile 1C:Enterprise version supports the latest Android versions. |
| Mobile device-specific features. | The mobile application no longer requires a user permission to access the application document directory. If the Access to all files functionality is disabled, you will see a message that the required functionality is disabled when you try to access files outside the data directory. New functionality: Geofences. It manages operations with geofences. | When you started an application for the first time, the system requested access to the application's document directory. When you tried to access a file outside the application's document directory, a file access error was generated. Operations with geofences depended on the Geolocation in background functionality. | Eliminated unexpected system behavior. The collaboration system behavior is more logical. |
| Mobile platform. Mobile client. Mobile device-specific features. | On the mobile version, you can get files that the user shared from other applications on a mobile device. When you set up the feature, you can specify that the mobile application will process some specific file extensions or all extensions. New global context property: LaunchShareRequestData. New event handler of the application module: IncomingShareRequestCommandGenerateProcessing(). New properties for the MobileApplicationFunctionalities system enumeration: IncomingShareRequests and AllIncomingShareRequestsTypesProcessing. | This feature was not provided. | In a 1C:Enterprise-based mobile application, you can now receive files that were shared from other applications using a standard feature of the respective mobile operating system. |
Transition from the previous version to the version 8.3.24
- Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.24.
- Some features that are added in version 8.3.24 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
- For the full-text search to improve the search result relevance, clear the full-text search index and recreate it on platform version 8.3.24.
- To use the geofence functionality in the mobile client version 8.3.24:
- Save the infobase configuration using version 8.3.24. You can set the required configuration compatibility mode.
- Enable the geofence functionality if it is disabled (Designer - Configuration property - Used mobile application functionality).
- Specify a text of the Notification position permission in the same dialog box.
- Save the database configuration.
- Export the mobile client configuration.
- Build a new mobile application version with the new configuration version.
- Update the mobile application on client devices.