New functions and changes
- Microsoft SQL Server 2012 DBMS is now supported.
- Mozilla Firefox 15 web browser is now supported (Windows, Linux).
- You can use the Native Client to access Microsoft SQL Server. If both servers are located at the same computer, you can use the SHARED MEMORY protocol in the Native Client (available since Microsoft SQL Server 2005).
- The following functionalities are added to 1C:Enterprise script: switching between form opening modes (in separate windows or in tabs); showing or hiding the Sections, Navigation, and Action panels; and managing client connection speed.
The following properties are implemented for the ClientSettings object: ClientConnectionSpeed, ApplicationFormsOpenningMode, ShowSectionPanel, and ShowNavigationAndActionsPanels.
The SectionPanelRepresentation property is implemented for the CommandInterfaceSettings object.
- The web client and web services can be published at Microsoft Internet Information Services 8.0 web server. You can have them published both from Designer or by using the webinst utility.
- You can get the number of milliseconds that passed since January, 1, year 0001, 0:00:00 UTC using the CurrentUniversalDateInMilliseconds() function.
- The privileged session mode is implemented. In this mode the access rights and data access restrictions are not verified. The privileged mode can be enabled only on session start and only for a user that has administrative rights. To enable the privileged session mode, use the UsePrivilegedMode option of the client application command line (also works for the web client) or prmod=1 option in the connection string.
Changes altering the system behavior
- User names and passwords that are passed to WSProxy, WSDefinitions, and HTTPConnection objects can contain special URL characters, except colon (:).
- The thin client can authenticate at a web server accepting HTTP Basic authentication user names and passwords in UTF-8 encoding.
- In the training version, the maximum number of items is increased for business processes, tasks, catalogs, documents, charts of characteristic types, charts of calculation types, charts of accounts, exchange plans, information register record sets, accounting register record sets, accumulation register record sets, and calculation register record sets.
The current limitations are:
- maximum number of records in account tables: changed from 500 to 2000;
- maximum number of records in main object tables: changed from 200 to 2000;
- maximum number of records in object tabular sections: no changes (1000 records);
- maximum number of records in record sets: changed from 1000 to 2000.
- The software license activation dialog box is now more intuitive and user-friendly.
The option to activate a software license for a specific user is removed; activation is always performed for all users on the computer.
- The algorithm for printing spreadsheet documents from the web client was modified. The number of copies specified in the Copies field is added to the PDF or HTML document prepared for sending to printer. The Collate and PerPage properties are also taken into account.
- Improved view of dotted lines when printing PDF spreadsheet documents from a web client that is running in Google Chrome web browser.
To have the dotted lines printed correctly in spreadsheet documents in Google Chrome, and also to ensure the correct size of all printed elements, it is recommended that you set the PrintAccuracy property of the spreadsheet document to Accurate.
- Status codes for 1C:Enterprise errors returned to a client by the web server comply with generally accepted standards. Trapping errors with 4XX codes is not recommended because this hinders regular application functioning. Errors 500, 502, and 503 are used as intended and can be trapped.
Changes that require changes to the configuration and administrative settings
- For non-predefined catalog items, the GetPredefinedItemName() catalog manager method returns the following:
- for 1C:Enterprise of versions up to 8.2.13 (including 8.2.13), an empty string;
- for 1C:Enterprise of versions 8.2.14–8.2.16 (including 8.2.16), the UNDEFINED value;
- for 1C:Enterprise of version 8.2.17 and later, an empty string.
- If a client application connected to a 1C:Enterprise server via a web server receives an exception in plain text or HTML format (instead of internal 1C:Enterprise exception format), the client application still will display the server response. The thin client supports the text/plain format. the web client supports text/plain and text/html formats.
- Web browser setup process is changed for all supported versions of Mozilla Firefox. To have access to full platform functionality in this browser, you have to install 1C:Enterprise Extension. You will be prompted to install the extension on the first start of the web client on your computer. Alternatively, you can use the main menu command Tools - Web browser setup to open the dialog for installing and updating 1C:Enterprise Extension.
Transition from the previous version to the version 8.2.17
- Conversion of configurations, infobases, external data processors, and external reports is not required during the transition from the previous version to version 8.2.17.
- The issue with license compatibility for basic configurations versions is resolved.
The thin and thick clients of 1C:Enterprise version 184.108.40.206 or later recognize digital signatures that were generated by any platform version.
Digital signatures generated by 1C:Enterprise version earlier than 220.127.116.11 are not recognized by the following clients:
- Thin clients of 1C:Enterprise version 8.2.14, 8.2.15, and 8.2.16
- Thick and thin clients of 1C:Enterprise version 8.2.13 or earlier