Version 8.3.2
Version 8.3.2 includes known bug fixes and functionality modifications.
New functions and changes
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.1 is added to the list of available values of the Compatibility mode property. | Compatibility modes were available for the following platform versions: 8.1, 8.2.13, and 8.2.16. | In version 8.3.2 you can run configurations created in version 8.3.1 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.2 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.1 for working with the infobase even after the transition to version 8.3.2. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on). |
| Development tools. | Automated configuration testing is implemented for managed applications. The testing is written in 1C:Enterprise script (using the appropriate script objects); it emulates a sequence of interactive actions and checks the results of their execution. Automated testing is supported for thin, thick, and web clients, both in file and client/server modes. The test does not require making any changes in the configuration being tested. Implemented the option of recording interactive user actions in a managed application for later use in a 1C:Enterprise script-based scenario, which reproduces the actions (http://its.1c.ru/db/metod81#content:5014:1). | This feature was not provided. | Better development quality can be achieved due to automated testing of the applied solution interface. |
| Developing tools. Applied objects. | Implemented XDTO serialization for pivot charts. Templates of spreadsheet documents that contain pivot charts can be dumpled to XML files. | This feature was not provided. | All configuration objects can be dumped to files. |
| Mobile application. | Mobile application development is supported, with target operating systems iOS and Android. Applications can run on mobile devices in the offline mode; permanent Internet connection is not required. Application data exchange through the Internet can be implemented using standard 1C:Enterprise tools. The development is performed in Designer; the managed application development model is used. The subset of functionality used for PC application development is supported. The resulting applications can run both on PC and mobile devices. | This feature was not provided. Mobile application development was only supported in the mobile extension for handheld devices (and only for Microsoft Windows Mobile and Microsoft Windows CE operating systems). | You can develop applications for devices with iOS and Android operating systems using 1C:Enterprise platform tools. Data exchange between mobile applications and PC applications is available. |
New functions and changes in 1C:Enterprise mode
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. | If an error that leads to system shutdown occurs, the error text is displayed in the technical support information window. | In some cases the error that led to system shutdown was not displayed in the technical support information window. | Improved usability of information for technical support. |
Optimization
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Applied objects. | Reduced verification and repair time for document journals. | For large journals the "Verify and Repair" operation might take significant time. | Reduced time of the "Verify and Repair" operation for document journals. |
| Developing tools. | Optimised memory usage when comparing configurations and updating modified configurations. | Comparison and merging of large configurations might cause issues related to high memory usage. | Comparison and merging of large configurations no longer requires customized OS settings. |
Changes altering the system behavior
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Command interface. | In the information register record form the system behavior has been changed in the case when the OnlyInAllActions property of the Copy command is set to Auto. This value now means that the command is only present in the All actions menu. This change is not implemented in 8.3.1 compatibility mode. | The Auto value of the OnlyInAllActions property of the Copy command meant that the command was present both in the command bar and in the All actions menu. | The behavior of the Copy command in the information register record form is unified with its behavior in forms of other objects. |
| Window management. | Relative positions of the user notification window and the window showing server calls are changed. The default position of the user notification window is the bottom right corner of the workspace area. The default position of the window showing server calls is the bottom left corner of the workspace area. | On Windows operating system, default window positions depended on the taskbar position. On Linux operating system, default window positions were not defined. | Unified default positions for the user notification window and the window showing server calls in different operating systems. Eliminated indeterminate behavior on Linux operating system. |
| Web client. | When a pop-up window is blocked by the pop-up blocker in Google Chrome web browser, the browser displays a related setup instruction in a new tab. | The browser setup instruction was displayed in a new browser window (not in a new tab) | Better usability of web browser setup. |
| Applied objects. | A value obtained from an empty table of values attribute, a value tree, or a tabular section matches the default value of the column attribute type (the type qualifier is taken into account). This change is not implemented in version 8.2.16 compatibility mode. | A value obtained from an empty table of values attribute, a value tree, or a tabular section matched the default value of the column attribute type, but the type qualifier was not taken into account. | The default value generation is uniform throughout the system. |
| Client application. Operating with DBMS. System requirements. Configuration repository. | The mechanism of shared work with infobase files and configuration repository files is revamped. Shared work with infobases and configuration repositories is supported for both Windows and Linux users. For the files 1Cv8.1CD, 1Cv8tmp.1CD, 1Cv8.1CL, 1Cv8tmp.1CL, and for some other files the system creates auxiliary files that have the same names with .cfl extension added (for example, 1Cv8.1CD.cfl). These files have zero size and are never deleted on closing client applications. Shared work with a file infobase is only possible if all client applications have the same version number. The number of simultaneous connections to a file infobase is limited to 1024. | The mechanism of shared work with the file infobase and the configuration repository did not take into account some pecularities of Linux file system. | Shared work with the file infobase and the configuration repository is available to both Windows and Linux users. Issues related to multiuser work with file infobases and configuration repositories on Linux operating system are eliminated. |
| Display of information. | When you create a formatted string in Designer (in the dialog for editing a formatted string), you can use style elements (font face and color). The formatted string stores references to style elements that were used during its creation. Converting style elements to actual fonts and colors (dereferencing) is performed when the string is displayed. | The dialog for editing a formatted string did not have options for specifying style elements. Formatted strings that were created using 1C:Enterprise script and included style elements actually contained explicit font and color values (not the references). | Improved usability of formatted string creation. You can simultaneously change the formatting of all text fragments that have the same style element applied to them. |
| Internet-enabled functionality. | If you use the InternetMail object with a mail server where secured StartTLS connection is set up to use the same ports as unsecured connection, the StartTLS connection is established. This change is not implemented in version 8.2.16 compatibility mode. | If you used the InternetMail object with a mail server where secured StartTLS connection was set up to use the same ports as unsecured connection, the StartTLS connection was not established. | You can establish a secured StartTLS connection to a mail server. |
| Spreadsheet document. | When the Join() method of a spreadsheet document is called, the properties StayWithNext, PageTop, and PageBottom of a spreadsheet document cells area are only copied when joining is performed for the area located beyond the right border of the resulting document. This change is not implemented in version 8.2.16 compatibility mode. | When the Join() method of a spreadsheet document was called, properies of a spreadsheet document cells area were always copied. | The Join() method handles page breaks during the output to a spreadsheet document. |
| Server cluster. | Removing a server cluster or a working server from the cluster console requires a confirmation. | Removing a server cluster or a working server from the cluster console did not require a confirmation. | The chance of accidentally removing a server cluster or a working server from the cluster console is decreased. |
| Administration tools. | The URL parameter is added to the CheckInfoBases method of the WebCommonInfoBases internet service. It allows "redirection" of infobase list requests to another internet service (provided that the other service has the same method descriptions). The other internet service can have different authentication settings. | Internet service "redirection" was not available. All web service calls used the same authentication. | When retrieving the list of infobases through internet services, you have the option to use multiple services with different authentication requirements. This allows implementing scenarios of the following type: the check for infobase list changes does not require authentication, but retrieving the list requires authentication. |
| Applied objects. Information registers. | Attributes, common attributes (that are not separators), and resources are not read implicitly when record sets are written to information registers. Rights to read attributes, common attributes (that are not separators), and resources are not required when writing a recordset to an information register. | Rights to read attributes, common attributes (that are not separators), and resources were required when writing a recordset to an information register. | Access right restrictions for read operations are not checked when writing a record set to an information register. |
Changes that require changes to the configuration and administrative settings
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Display of information. | If a message to a user contains characters incompatible with XML format (in thick or thin client), the error XML text contains invalid characters in X position is generated. This change is not implemented in version 8.3.1 compatibility mode. | If a message to a user contained characters incompatible with XML format, the thick and thin clients did not display any error message. | Uniform system behavior for handling characters incompatible with XML format. |
| Applied objects. | If you explicitly specify the Encoding property of the InternetMailAttachment object, the outgoing email message is generated with explicitly specified attachment encoding.
This change is not implemented in version 8.2.16 compatibility mode. | The Encoding property of the InternetMailAttachment object was ignored during the generation of outgoing email message. | Explicitly specified attachment encoding ensures that the emal client displays the attachment name and content correctly whenever email message encoding is different from the attachment encoding. |
| Spreadsheet document. | The algorithm for calculating horizontal cell positions is changed. If total width of several adjacent cells is identical for different rows, such blocks of adjacent cells have equal width in all rows and therefore have common vertical borders. This change is not implemented in version 8.2.16 compatibility mode. | If total width of several adjacent cells was identical for different rows, the cells might have different width in different rows, and therefore might not have common vertical borders. | Improved usability of spreadsheet documents. |
Transition from the previous version to the version 8.3.2
- 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.2.
- Some features that are added in version 8.3.2 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.