Version 8.2.18 includes known bug fixes and functionality modifications.
New functions and changes
- For the <ws> tag of the default.vrd publishing file, the pointEnableCommon attribute is implemented. It specifies whether web services whose description does not include the enable attribute of the <point> tag will be published (this attribute defines whether a given web service will be published).
- Native clients for Microsoft SQL Server 2005 and Microsoft SQL Server 2012 are now supported.
- IBM DB2 version 10.1 database management system support.
- Subject and Issuer properties of the CryptoCertificate object can contain items with the following names (in addition to existing ones):
- SN – the string field corresponds to the value of the surname certificate field.
- GN - the string field corresponds to the value of the given name certificate field.
- T – the string field corresponds to the value of the title certificate field.
- The 1C:Enterpise server cluster numbering service is optimized. This prevents server performance degradation over time.
- Optimized performance of thin and thick clients connected to a network-located file infobase during simultaneous access by multiple users. Improved performance of various infobase operations, including opening and editing object forms, viewing list forms, writing objects, posting documents, and so on.
- Improved 1C:Enterprise server scalability under heavy load from a large number of users.
- Increased performance of StrLineCount() and StrGetLine() functions when they are executed in thin client, thick client and on the server.
- Optimized receiving mail using the InternetMail object.
- Optimized performance of the ValueIsFilled() function when the function parameter is an expression that consists of getting a property of any nesting level for any variable (either using "dot" or using the  operator).
- In the document journal table, added indexing by the Ref field. This provides performance optimization for dynamic lists of document journals and for the search by string in document journals.
- Optimized generation of Microsoft SQL Server DBMS queries:
- Reduced number of dublicate query plans.
- Reduced number of query compilations.
- Reduced query plan cache size.
- Faster response of certain queries.
- Improved query plan generation in certain cases.
- Optimized performance of dynamic lists and dynamic database sampling in descending order, and these operations are further optimized for Microsoft SQL Server environment.
The restructuring operation is optimized for Microsoft SQL Server environment as well.
- In the client/server mode with enabled managed locks, modified the process of generating new references to infobase objects. References are always generated sequentially for all 1C:Enterprise server connections to the DBMS server. This provides reduced fragmentation of tables and indexes in the database, as well as optimization of insertion and read operations on database table records.
- Optimized performance of load balancing in a server cluster.
- Optimized retrieving of applied objects from the database in the following cases: calling the GetObject() method for an applied object that does not have a tabular section, and getting properties from a reference using "." (dot).
- Optimized performance of 1C:Enterprise server while executing queries to objects with data access restrictions.
- Optimized performance of Microsoft SQL Server operations that use the IN (...) construction with a single list value.
- Optimized performance while starting client applications, background jobs, and scheduled jobs.
- Optimized system performance under heavy load due to frequent background job execution and web service calls.
- Reduced time for opening managed forms.
The optimization has the maximum effect in the following scenario: a thin client is connected to a network-located file infobase with simultaneous access by multiple users.
- Improved performance of certain types of queries in the file infobase. For example:
- Queries of type SELECT TOP 1 ...
- Comparison of two lists using the IN operator: ... (Object, Invoice) IN (&ListOfObjectsAndBatches) ...
- Optimized performance of client applications connected to a network-located file infobase. It is recommended that you compress the infobase table after bulk data changes.
- In the web client, optimized performance of opening and scrolling of spreadsheet documents that contain a large number of columns.
Changes affecting the system behavior
- In a web client that is running in Google Chrome, calling the GetFile() method does not open an additional browser window.
- If the extension for cryptoprotection is enabled in a web client that is running in Microsoft Internet Explorer, the dialog box where the user is prompted to confirm accessing the private key or the file system on their computer is opened on top of all other windows.
- When an exception occurs in a server method of a managed form, the client application displays the form that has exactly the same appearance as the form on the server side had at the moment of exception. This prevents situations when changes in the form appearance that were performed on the server before the exception occurred are not transferred to the client side of the application.
- In the web client that runs in Google Chrome version 26, the File upload dialog box is modified. To upload a file, drag it to the File upload dialog box and click OK.
Changes requiring changes to the configuration and administrative settings
- The distribution kit for Windows includes the HASP driver version 6.51.29439.1. The name of the file that installs or removes the driver is haspdinst.exe. The new version number is included in the names of the Start menu shortcuts.
- On Linux, in the PathToCryptoModule parameter (the second parameter of the CryptoManager object constructor), you can specify paths to multiple libraries that simultaneusly implement an interface similar to Microsoft Crypto API. The paths are separated by ":" (colon). This provides support for all versions of the CryptoPro provider for Linux.
To ensure compatibility with both old and new CryptoPro versions, it is recommended that you specify the PathToCryptoModule parameter of the CryptoManager object constructor as follows: /opt/cprocsp/lib/amd64/libcapilite.so:/opt/cprocsp/lib/amd64/libcapi10.so:/opt/cprocsp/lib/amd64/libcapi20.so
- You can use HTTP query headers, process return codes, get and set the query body as a string or binary data. The HTTPRequest, HTTPResponse objects are implemented.
For the HTTPConnection object, the following changes are implemented:
- The Put(), Post(), Get(), and Delete() methods return values of HTTPResponse type.
- For Put(), Post(), Get(), and Delete() methods, the syntax for processing HTTP requests generated by 1C:Enterprise script is implemented.
- The OpenID pass-through authentication protocol implementation is revised. The implementation corresponds to the Direct Identity version 2.0 mode of the OpenID protocol.
Modified format of the OpenID provider address in the default.vrd file (the url attribute of the rely item): httрs://<address of the OpenID provider infobase>/e1cib/oid2op. The default authentication lifetime is 24 hours. Maximum duration of authentication is 168 hours.
Modified the protocol for interaction between the relying party and the OpenID provider.
In the authentication dialog box, you can disable storing authentication data.
For web client, implemented a dialog box for entering the user name and password on the OpenID provider side.
- The add-in technology now supports Mozilla Firefox browser version 19.0. You can use add-in adapters for Mozilla Firefox 19.0 in the later versions of the web browser without recompiling the adapters. It is recommended that you specify only the minimum version of the web browser in the add-in manifest file.
Transition from the previous version to the version 8.2.18
- Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.2.18.
- To create an index by the Ref field in a document journal table, you can do one of the following:
- Make changes that lead to restructuring of one or several selected document journals.
- Restructure the tables during the verification and repair of the infobase.
- For infobases that use the OpenID authentication, you have to change the publishing settings in the default.vrd file.
- For the file infobase, it is recommended that you perform the compression of infobase tables after transition from any of previous versions.
- If the current configuration is updated to a new version that has version 8.2.16 or later compatibility mode set and the update is performed using 1C:Enteprise version 8.2.15 or earlier, this can lead to mismatches between metadata description and database structure. Starting the configuration in 1C:Enterprise mode also becomes unavailable, an error occurs during the startup and the system is shut down. Mismatches occur if any of the following configuration objects are used in the applied solution: scheduled job, constant, exchange plan, accumulation register, or accounting register.
To fix the issue, run the infobase verification and repair. The check for mismatches between metadata description and database structure is performed every time, regardless of the states of the check boxes in the Verifications and modes list. If the "verification and repair" operation is started in the verification only mode and mismatches are detected, a message describing the problem and the solution recommendations is displayed.