Version 8.3.19 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.18 is now implemented. | Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.17 was available. | Configurations developed using 1C:Enterprise platform version 8.3.18 or earlier can now run on version 8.3.19 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.19 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.18 after the migration to version 8.3.19, even if you disable the compatibility mode (simply enable it again). |
| Documentation. | New feature: objects available on a standalone mobile server can be selected for the Syntax Assistant. New availability mode for the Syntax Assistant: Standalone mobile server. This availability mode describes objects and methods available on the 1C:Enterprise server running on a mobile device in standalone mode of the mobile client. | In the Syntax Assistant, it was not possible to select objects available on a mobile device on the server side of the mobile client running in standalone mode. | New features of the 1C:Enterprise mobile version are considered in the Syntax Assistant. |
| Navigation links. | Now you can specify additional parameters in URLs. The composition of parameters depends on the URL kind. Now you can do the following:
In the get URL dialog box (if necessary), you can choose which URL to get at a specific place in the client application interface. New methods for the client application form extension for a report: GetReportURL(), GetCurrentReportOptionURL(), and GetCurrentReportSettingsURL(). New method for the client application form extension for a data processor: GetDataProcessorURL(). New methods for the client application form extension for a dynamic list: GetListURL() and GetCurrentListSettingsURL(). New client application form parameter for a dynamic list: TableDisplay. New method for the client application form extension for an object, a document, a catalog, a business process, a task, a chart of characteristic types, and an object of an external data source table: GetObjectURL(). New method for the client application form extension for an information register record and a record of an external data source table: GetRecordURL(). New feature: all the listed URL options can be received for the GetURL() global context method. New handlers for the client application form: GetURLsListProcessing and GetURLProcessing. New configuration property: URLsExternalDataStorage. Changed format of the XML configuration export. | These features were not provided. | Advanced navigation links features. |
| Client application form. | For form field extensions for an HTML document, a formatted document, a geographical schema, and the planner, implemented the BeforePrint event that occurs before an object is printed interactively. For form field extensions for an HTML document and a formatted document, implemented the BeforeWrite event that occurs before an object is written interactively. For form field extensions for an HTML document and a formatted document, implemented the AfterWrite event that occurs after an object is saved interactively. The Save command of the client application form called for a spreadsheet document does the following:
Once a spreadsheet document is saved, an operation completion notification appears. For all form item kinds that support saving (except a spreadsheet document), the value that matches the executing action is passed to the Copy parameter of the BeforeWrite event handler:
For a spreadsheet document or a report, the behavior is not changed when you select the Save command. | For all form item kinds that supported saving, the system behavior was the same when the Save and Save as commands were specified: the dialog box to select a file to be saved was generated. For all form item kinds that supported saving (except a spreadsheet document), the True value was always passed to the Copy parameter of the BeforeWrite event handler. For a spreadsheet document, when the Save command was selected for a spreadsheet document or a report, the False value was passed to the BeforeWrite handler in the Copy parameter. | Implemented the BeforePrint, BeforeWrite, and AfterWrite event handlers for all client application form items that support saving and printing. |
| Client application. | Changed icons of all 1C:Enterprise executable files and icons associated with different file extensions related to 1C:Enterprise. | Icons of executable and generated files of 1C:Enterprise were different. | Icons follow the same style. |
| Pictures. | SMIL animation of SVG images is now supported. SMIL animation is not supported in Microsoft Internet Explorer and Microsoft Edge up to version 18 inclusive. In web browsers that do not support SMIL animation, a static picture will be displayed. New feature: in a set of picture variants, you can specify a web browser the variant element is intended for. When a picture is output in a web browser, an attempt is made to define a variant for the used web browser first. We recommend that you use SVG images with SMIL animation to create animated pictures in the application. Such pictures take up little space and do not require large resources for their display. | This feature was not provided. | Animated SVG images can now be displayed. Animation is displayed in both ordinary client applications and the web client (except Microsoft Internet Explorer and Microsoft Edge up to version 18). |
| Dynamic lists. | The following features similar to the features provided in the data composition system are available for a dynamic list:
Changed the dynamic list settings editor. New properties for a dynamic list: Fields, FieldsToCalculate, and DataParameters. Changed the configuration XML dump format. The following dynamic list methods are deprecated: SetRestrictionsForUseInGroup(), SetRestrictionsForUseInFilter(), SetRestrictionsForUseInOrder(), GetRestrictionsForUseInGroup(), GetRestrictionsForUseInFilter(), and GetRestrictionsForUseInOrder(). We recommend that you use the UseRestriction dynamic list properties and the AttributesUseRestriction dynamic list fields. This change is not implemented in version 8.3.18 compatibility mode. | These features were not provided. | Simplified setup of dynamic list fields. In particular, you can now specify localized presentations of query fields displayed in a dynamic list. |
| Data composition system. Dynamic lists. | When you set up configuration object characteristics, you can now specify which configuration object field contains a characteristic name. Changing the characteristic presentation will not result in the loss of settings field of the data composition system or a dynamic list. New property: CharacteristicsDetails.DataPathField. The value that returns the Presentation virtual field is used as a characteristic presentation. A new field remains blank for existing characteristics. If you change a field that contains a characteristic name in the characteristic description, we recommend that you provide a mechanism that converts data composition settings by replacing the old characteristic name with a new one. Changed format of the XML configuration export. | The presentation of this characteristic was used as a characteristic name. Changing the characteristic presentation resulted in the loss of characteristics of data composition system settings and dynamic list settings. | Simplified creation of localized characteristic presentations in applications. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Collaboration system. | The client application on Windows uses the Video Tools module that matches the operating system bitness for video calls. | The client application on Windows used the Video Tools module that matched the client application bitness for video calls. | On a video call, computer resources are used more efficiently. |
| Client application. Web client. | Now the Taxi interface supports right-to-left languages (in thin and thick client applications). This mode is supported in the entire client application interface automatically. The need to change the interface is determined by the interface language or the configuration language. Now client applications support Arabic numbers and dates. When calculating placement of form items and other interface elements, Almarai font is used by default. If a right-to-left language is set as the current configuration language in Designer, then the form preview in the form editor will also be performed in the relevant format. Support of right-to-left languages has been implemented starting with version 8.3.7 compatibility mode. The web client now supports right-to-left languages for the planner and charts. | Right-to-left languages were supported in the web client only. | 1C:Enterprise is now available in right-to-left languages (using thin and thick client applications). |
| Spreadsheet documents. Data display. | If the length of the text within a cell exceeds 3276 characters in a spreadsheet document being saved in the Microsoft Excel format (Microsoft Excel 97 or Microsoft Office OpenXML), saving is terminated and an error message appears. | When saving a spreadsheet document in the Microsoft Excel format (Microsoft Excel 97 or Microsoft Office OpenXML), the length of the text within a cell was not checked. This could result in a document that Microsoft Excel could not open. | Saving in the Microsoft Excel format is more correct now. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Queries. | Improved query execution including when data access restrictions are used. Improved performance of the StrContains() function of the data access restriction expression. | Query execution (including queries that used data access restrictions) took more time. | Improved query performance. |
| Server clusters. | In a client/server infobase, loading from the .dt file is now faster as several background jobs are used for loading. To speed up significantly, we recommend that the server cluster and the DBMS are on the same computer or that the server cluster and the DBMS are interconnected with a high-bandwidth channel (1 GB/s or higher). For the /RestoreIB command of the Designer batch mode, implemented the JobsCount parameter that allows you to manage the number of used background jobs. | In a client/server infobase, loading from the .dt file was performed sequentially. | Upgrade: information is restored from the .dt file faster in a client/server infobase. |
| Common objects. | When solving systems of linear equations, reduced the time spent on obtaining a solution and the use of RAM. | Solving systems of linear equations took more time and required more RAM. | Improved solving systems of linear equations. |
| Server clusters. | Improved generation of a session list. New service: Service for retrieving a list of server cluster sessions. | Retrieving a session list took more time and could cause the system to hang on bulk retrieving the session list when load on the server cluster was heavy. | A possibility of system hanging on bulk retrieving a session list under heavy load is excluded. Reduced time of a single operation for retrieving a session list on a cluster with multiple servers. The time spent on simultaneous bulk retrieval of session lists is significantly reduced. |
| DBMS operations. | If you press the Write button several times in the object edit form (with the object unchanged), object tabular sections are not written to the DBMS upon each object record. | If you pressed the Write button several times in the object edit form, object tabular sections were written to the DBMS upon each object record. | Decreased DBMS load in some cases. |
| DBMS operations. Queries. | In a file infobase, executing a query that receives data with ordering and filtering by the field for which the index is built is faster now even if the IN operator that receives a large amount of data is used to impose a condition. | In a file infobase, executing a query that received data with ordering and filtering by the field for which the index was built was not optimal if the IN operator that received a large amount of data was used to impose a condition. | Improved file infobase performance. |
| Accounting registers. | Optimized the query used by 1C:Enterprise to access virtual tables of balance and turnovers of the accounting register. | The query used by 1C:Enterprise to access virtual tables of balance and turnovers of the accounting register was not optimal. | Improved performance of queries to the virtual table of balance and turnovers of the accounting register. |
| Data display. | Improved performance of the GetStringDeclension() and GetStringDeclensionByNumber() upon consecutive calls. For example, to get several case forms of the same phrase at once. | Several consecutive calls to the GetStringDeclension() and GetStringDeclensionByNumber() methods took more time. | Getting several case forms of the same phrase at once using the GetStringDeclension() and GetStringDeclensionByNumber() methods is faster now. |
| Automated testing. | Reduced the number of network calls when the FindObject(), FindObjects(), and GetObject() methods of automated testing are running. This improves the overall automated testing performance. | When the FindObject(), FindObjects(), and GetObject() methods of automated testing were running, a large number of network calls were made, which caused poor automated testing performance. | Improved automated testing performance, especially when the web client is used. |
| Data display. | Bulk retrieval of presentations of reference objects is now faster if only data passed to the handler is used to generate the presentation. This is reached by caching the presentations. If data that is not passed to the presentation generation handler is used to get the presentation, when the presentation changes in the object, the presentation will change in the handler only in 20 seconds. | Bulk generation of presentations of reference objects took more time as values used to get the presentation were cached and the presentation itself was calculated every time the presentation was required. | Receiving presentations of reference objects and related operations are faster now. For example, ordering a value table by a reference column will speed up. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Database copies. Queries. Data composition system. | Now you can control where a specific query or data composition will be executed: use only copies, only the main database, or mostly copies to execute a query, or select automatically. Thus, it became possible not to load the main database with a query that was created to be executed on a copy. New properties for the Query and DataCompositionOutputParametersValues objects: DatabasesCopiesUse and UsedDatabaseCopies. | The platform automatically selected where the query would be executed. If it was not possible to execute a query on a copy, the main database was used to execute the query. | It is now possible not to execute queries or reports on the main database that can affect the database performance and that were intended to be executed on a copy only. |
| Data composition system. | Once the report is generated, the server part of the data composition system notifies the client application initiated the report generation of report generation completion using the Collaboration System. This mechanism works in conjunction with the existing mechanism for determining whether report generation is completed (periodic polling of the system background job). | To determine whether report generation was completed, periodic polling of the system backgroud job generating the report was used. Each failed completion check increases the time interval after which the next check will be done. | If there is the Collaboration System, a user will know right away when long report generation is completed. If the Collaboration System is not connected to the infobase or is temporarily not functioning, the existing mechanism will be used. |
| Dynamic lists. | For the header of the table column displaying a dynamic list with an order setting item that cannot be disabled by a user:
As a result, the behavior of thin, thick, and web clients is the same when a user left-clicks the header of the dynamic list column whose ordering settings include an item that cannot be controlled by the user. | For the header of the table column displaying a dynamic list with an order setting item that could not be disabled by a user:
The behavior of thin, thick, and web clients was not uniform when a user left-clicked the header of the dynamic list column whose settings included an item that could not be controlled by the user. | Unified behavior of thin, thick, and web clients when a user left-clicks the header of the dynamic list column whose ordering settings include an item that cannot be controlled by the user. |
| Data display. | The behavior of the GetStringDeclensionsByNumber() method changes when generating a number:
This change is not implemented in version 8.3.18 compatibility mode. | When generating a numeral with an ending using the GetStringDeclensionByNumber() method, two-letter endings were always returned for ordinal and cardinal numbers. | Eliminated unexpected system behavior. |
| Database copies. | Now you can add objects included in separators to a database copy. On initial filling, the entire table is transferred. On change transfer, only the area that matches the separators of the current (transferred) transaction is transferred. To create a database copy (using the DatabaseCopyManager.Write() method) and update copy data (using the DatabaseCopyManager.Update() method), the DataAdministration access right is required. | It was possible to add only tables that were not part of separators or a table with conditionally disabled separators to a copy. | Now you can add separated application objects to a database copy. |
| Client application. | Now each infobase user can manage OpenIDConnect authentication. New property: InfobaseUser.OpenIDConnectAuthentication. Now you can end an authentication session according to the OpenID Connect standard. New property in OpenID Connect provider description–default.vrd file, <providers> item: endSessionEndpoint. | This feature was not provided. | Improved OpenID Connect support. |
| Licensing system. | Expanded the set of information displayed by the licensing utility (the ring license info command):
| The output of the ring license info command did not contain information about the license type and the license binding type, and did not contain a section with machine-readable information about the license. | Expanded the set of activated license information that can be obtained. Simplified obtaining information about licenses using various automation tools. |
| Charts. Data composition system. | Upgrade: a chart in a data composition system report better adjusts to the width of the screen showing the report. This change is not implemented in version 8.3.18 compatibility mode. | A chart in a data composition system report did not adjust well to the width of the screen showing the report. | Improved appearance of charts on low-resolution screens. |
| Queries. | If a query that generates a temporary table based on a value table retrieves a field separated by dot from another expression, a query language error is generated on executing such a query. We recommend that you analyze texts of queries to generate temporary tables to eliminate the modifiable behavior. This change is not implemented in 8.3.18 compatibility mode. | If a query that generated a temporary table based on a value table retrieved a field separated by dot from another expression, a runtime error was generated when executing this query in client/server mode and an incorrect value was placed in the temporary table value when executing this query in file mode. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | This feature is canceled. When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the Picture objects now behave as follows:
As a result of these changes, pictures in a spreadsheet document become less distorted when scaling a Microsoft Excel document. | When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the Picture objects behaved as follows:
| The result of saving a spreadsheet document in Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats meets expectations of users to a greater extent. |
| Data composition system. Functional options. | When calculating the availability of child fields used in data composition expressions, a check whether the field is not disabled using a functional option is performed for both the field itself and all parent fields of this field. This change is not implemented in version 8.3.18 compatibility mode. | When calculating the availability of child fields used in data composition expressions, a check whether the field was not disabled using a functional option was performed only for the field itself. Parent fields were not checked. | Upgrade: the availability of fields associated with functional options is checked in the same way in both the query language and the data composition system. |
| Data exchange. | For the RecordChanges() and DeleteChangeRecords() methods, it is now possible to register and unregister changes for an arbitrary set of data objects that are passed as an array in the Data parameter of these methods. The action for all objects in the passed array will be performed within a single transaction with the minimum number of queries used. | For the RecordChanges() and DeleteChangeRecords() methods, it was not possible to specify an array of objects to perform an action. | Executing the RecordChanges() and DeleteChangeRecords() methods is now faster when these methods must be applied to a large number of data objects. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. Client application installation. Administration tools. | Now you can update a client application using the web server when Microsoft Internet Information Services configured by default is used as a web server. Implemented support of the MIME type application/x-zip-compressed used by the web server for .zip files by default. | To update a client application using the web server when Microsoft Internet Information Services was used as a web server, you had to manually override the MIME type that the web server used to pass .zip files. | Administration of the Microsoft Internet Information Services web server is more convenient when a client application update is configured via the web server. |
| Administration tools. | When exclusive mode is set, you can now specify a human-understandable description of the reason why exclusive mode is set (what the session is doing) and terminate the session that set the exclusive access. New parameter for the SetExclusiveMode() method: Parameters. New global context method: GetExclusiveModeParameters(). New access right: ExclusiveModeCompletionOnStartSession. The message text about the reason for the inability to start a new session can be a formatted string or an HTML string generated from a formatted string. | When attempting to log into the infobase where exclusive mode was set, it was impossible to terminate such a session (even if it was possible to terminate the session according to the logic of the actions being performed) and it was not clear what was being done at that moment. | When exclusive mode is set, you can now specify a user-understandable text that explains why exclusive mode is set. A user can terminate the session that set exclusive access if the user rights and the logic of the actions performed allow such termination. |
| Predefined data. | Calling the PredefinedValue() method when a non-existent enumeration value is specified as a parameter value generates an exception. This change is not implemented in version 8.3.18 compatibility mode. | Calling the PredefinedValue() method when a non-existent enumeration value was specified as a parameter value returned an empty value. | Eliminated unexpected system behavior. |
| Administration tools. | The name of the distribution package of 1C:Enterprise server cluster for x86-64 architecture looks as follows: 1C:Enterprise 8 (x86-64) Server. | The name of the distribution package of 1C:Enterprise server cluster for x86-64 architecture looked as follows: 1C:Enterprise 8 (x86-64). | Now software names follow a single style for all software distribution packages for Windows. |
| Spreadsheet documents. Data composition system. | Now you can scale a picture so that the picture height matches the size of the font used in the item that displays the picture. New system enumeration property: PictureSize.ByFontSize. If a picture in a report cell is specified using the Picture conditional appearance parameter of the data composition system, the PictureSize parameter value equals the ByFontSize value (if the PictureSize parameter is not specified in conditional appearance). This change is not implemented in version 8.3.18 compatibility mode. We recommend that you use the ByFontSize picture display mode in a spreadsheet document when a picture in a cell is a marker. When using this picture display mode, the picture height does not affect the automatically calculated height of the spreadsheet document row and does not depend on the number of text rows displayed in the cell. | If a picture in a report cell was specified using the Picture conditional appearance parameter of the data composition system, the default value was not set for the PictureSize parameter and this parameter was not used (except if this parameter was specified explicitly). | Improved display of pictures in a spreadsheet document in cases where it is necessary to use a picture in the text so that the picture size automatically adjusts to the height of the font used. |
| Server clusters. Administration tools. | Now you can use partial Kerberos delegation for OS authentication if the server cluster is running Windows, the web server and the client application are each on their own computer, and this computer is different from the computer where the server cluster is running. For server cluster administration tools, a service principal name (SPN) can now be specified:
| This feature was not provided. OS authentication could only be performed with full Kerberos delegation if the server cluster was running Windows, the web server and the client application were each on their own computer, and that computer was different from the computer where the server cluster was running. | Now you can use OS authentication when accessed via the web server, without lowering the overall system security. |
| Data display. | Now you can automatically switch a report to compact mode (if necessary), regardless of how the report is generated: using the platform or the 1C:Enterprise language. New property of the client application form extension for a report: ViewModeUseOnSetResult. The property works together with the ResultViewMode property of the client application form extension for a report. Changed format of the XML configuration export. | If a report was generated using the 1C:Enterprise language, it was required to switch the report to compact mode (if necessary) manually. | For a developer, simplified report display on a form if the report is generated using the 1C:Enterprise language and it is necessary to consider that the report can be displayed on mobile devices. |
| Server clusters. | The value of the Temporarily allowed amount of process memory property of the working cluster server is used to restart working processes from memory and manage large call termination. You can use this property with a PROF license. | When working with PROF licenses, a value equal to 80% of the RAM of the computer where the server was running was used to restart cluster working processes and terminate large server calls. It was not allowed to change the Temporarily allowed amount of process memory property of the working cluster server with PROF licenses. | Administration of systems with PROF licenses is more convenient. |
| Spreadsheet documents. | Now you set the report display mode for reports using the 1C:Enterprise language. New methods for the client application form extension for a report form: GetResultViewMode(), GetCurrentResultViewMode(), and SetResultViewMode(). Changed the approach to storing information about the result display mode in the system settings storage. Information about the report display mode is stored in the system report storage when the display mode value to be set differs from the value specified in the configuration. In this case, the Auto value interpretation is ignored for various client types. The ResultViewMode property of the client application form extension for a report form is deprecated. | It was not possible to change the report result view mode using the 1C:Enterprise language. The value that the current client application took into account was stored in the system storage (the Auto value interpretation was not ignored). | Now you can manage report display using the 1C:Enterprise language. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile client. Automated testing. | Now you can use the mobile client as a test client. The mobile client in standalone mode can be a test client only during connection with the main server. Now you can record user actions on a mobile device and playback a test written earlier in the 1C:Enterprise language. New commands for the command-line to start the mobile client: /UILOGRECORDER and /TESTCLIENT. The developer mobile client is always started with the option to record user actions (with the /UILOGRECORDER command). If the mobile client is started with the /UILOGRECORDER command, the Record user actions item appears in the Mobile client tools menu. | This feature was not provided. | Now you can use the mobile client for automated testing of applications. |
| Error handling. | New values for the ErrorsCategories system enumeration:
| These error categories were missing in the ErrorsCategories system enumeration. | Improved mobile application error categorization. |
| Mobile device-specific features. | Now you can manage audio recording in the background. If this functionality is enabled, audio recording will continue when the application is minimized and the device screen is turned off. New system enumeration value: MobileApplicationFunctionality.AudioRecordingInBackground. | Background audio recording was not available. Audio information could be recorded only if the application was active. | Improved audio information operations in the mobile application. |
| Mobile client. | Upgraged the video call interface in the mobile client. In the mobile client, you can now view the screen of another device and share your own screen. The viewing screen cannot control the mobile device whose screen is being shared. | The video call interface in the mobile client was different. The mobile client did not support screen viewing and sharing. | Improved interaction system video calls in the mobile client. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Analytics - charts. | In a graph, the x-axis will show the time dimension by default. | The x-axis now showed the first added dimension. | The expected result is obtained more often without additional actions. |
| Analytics - dashboards. | The left dashboard panel shows folders, just like the desktop. | The left dashboard panel showed all charts, excluding folders. | It is now easier to navigate through charts on the dashboard. |
| Analytics - dashboards. | Decreased spacing between dashboard items. | Spacing between the dashboard items was larger. | The dashboard now contains more information. |
| Analytics - charts. | In table mode, you can now customize how totals will be placed: at the beginning or at the end of dimension values. | In table mode, totals were always displayed at the beginning of a dimension. | Improved appearance settings for table totals. |
| Analytics - expression language. | Implemented the FORMAT() function to format values in a chart. | The value was displayed in the default format. | You can now customize the required option to display values. |
| Analytics - charts. | When the chart type is switched, the chart retains roles of fields that are close in meaning. | When the chart type was switched, field roles were set to default values. | Switching the chart type requires fewer steps to achieve the desired chart appearance. |
| Analytics - sources. | When creating additional sources based on virtual tables, it is now possible to transfer parameters from report settings to a query. | It was not possible to define virtual table parameters in additional sources. | Additional sources based on virtual tables are now more efficient. |
| Analytics - expression language. | Implemented the PREVDATE() and VALUEFOR() functions to build comparative graphs for different time slices or other dimensions. Using these functions will allow you to compare similar indicators obtained for different periods of time or other analytical dimensions in the table. | For output to the table, it was not possible to use similar indicators obtained for different periods of time or other analytical dimensions. | You can now obtain the same indicators for different periods of time to build better charts. |
| Analytics - expression language. | Implemented the TOP() function that allows you to limit the number of values displayed in a report and combine the remaining values into a single total value. The setting is available from the dimension context menu. | This feature was not provided. | You can now build more descriptive charts. |
| Analytics - charts. | The chart editor now supports search for available fields in nested source structures (in nested references to catalog items and documents). | The search only worked for the top level of the hierarchy. | It is now easier to search for fields to be analyzed. |
| Analytics - charts. | The hierarchy can now be expanded by date similar to the directory hierarchy using the field hierarchy menu in a chart. | Periods in charts had to be refined manually. | It it now easier to manage dates in charts. |
| Analytics - charts. | You can now customize the legend location in the chart. | The position of the legend was fixed. | The chart appearance settings are now more flexible. |
| Analytics - charts. | Implemented tooltips and notes in the filter by date editor for universal formulas ("Current year", "Last year", and other). | This feature was not provided. | Help information is now available in the filter by date editor. |
| Analytics - charts. | The chart background now considers the currently enabled application theme. | The chart background was light regardless of the theme. | The chart background now matches the theme used. |
| Analytics - charts. | A tooltip can now be displayed for a field value if it does not fit within one cell in the table. | This feature was not provided. Field values were clipped to cell borders. | You can now see the full value in a table cell for any length of the text presentation of the value. |
| Analytics - charts. | The full date value can now be displayed in a chart using the context menu. | The full date could only be displayed by editing the formula. | It is now easier to manage dates. |
| Analytics - charts. | You can now smoothly adjust the size of the panel with data source fields. | The panel size was not customizable. | You can now use screen space more efficiently. |
| Analytics - dashboards. | When switching from the dashboard to the chart level, common dashboard filters can now be displayed and quickly enabled/disabled. | There were no common filters on the dashboard. | The user can quickly assess the filter impact on the dashboard data. |
| Analytics - other. | Implemented the command to open the web client of 1C:Enterprise infobase with which 1C:Analytics works. | It was not possible to quickly call the web client for the used 1C:Enterprise infobase. | It is now easier to use the infobase. |
| Analytics - desktop. | You can now batch copy/move objects on the desktop. | Objects on the desktop could only be copied and moved one at a time. | The desktop is now more user-friendly. |
| Analytics - desktop. | The path to objects can now be displayed upon desktop search. | Upon search, it was not clear where the object came from. | Desktop search is now more informative. |
| Analytics - charts. | Chart data is stored in the cache of 1C:Analytics for 24 hours. | Chart data was stored in the cache of 1C:Analytics until the web browser tab was reloaded. | The result is now more predictable. |
| Analytics - dashboards. | You can now copy dashboard widgets. | Dashboard widgets could not be copied. It was only possible to create a new widget that had to be configured manually. | Simplified dashboard setup. |
| Analytics - charts. | You can now set the display range of values on graph axes. | The display range of values on graph axes was adjusted automatically based on the displayed data. | Chart appearance customization is upgraded. |
| Analytics - sources. | When using virtual tables of balance and turnovers, balance by periods when there were no turnovers for dimension values can now be supplemented. The balance in the supplemented periods is equal to the balance of the last actual period preceding the supplemented period. | When using virtual tables of balance and turnovers, balance by periods were not displayed (there could be gaps in the data) if there were no turnovers for dimension values during these periods. | Data display is correct. |
| Analytics - expression language. | New date functions: DATEDIFF(), BEGINOFPERIOD(), and ENDOFPERIOD(). | This feature was not provided. | Extended the list of date functions. |
| Analytics - dashboards. | Implemented filter templates for Boolean and Date fields on the dashboard. | Filters of the specified types could only be set by a formula. | Simplified filter creation. |
| Analytics - sources. | Improved appearance of the dialog box that is displayed when updating sources of 1C:Analytics. The dialog box now displays more detailed information and does not block the system. | The dialog box that was displayed when updating sources of 1C:Analytics showed less information and blocked the system. | Improved appearance and behavior of 1C:Analytics when updating sources. |
| Analytics - expression language. | Implemented the ADD() function to change date and time values. | This feature was not provided. | Extended the list of date functions. |
| Analytics - charts. | Pressing ESC closes the field edit window only if the window field values are not changed. | Pressing ESC closed the field edit window regardless of whether the data in the window fields was changed or not, which could lead to data loss. | The system is now more predictable and user-friendly. |
| Analytics - expression language. | Improved context hint when editing expression code. | The context hint did not work well when editing expression code. | The expression editor is now more user-friendly. |
| Analytics - charts. | Improved chart labels. | When there were a lot of labels, they covered each other and the chart looked bad. | Improved appearance of charts. |
| Analytics - charts. | Improved grouping performance. | Grouping performance was non-optimal. | Improved data retrieval. |
You can find the demo configurations on the ITS disk Read more..
The list of used mobile application features now includes the following:
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Dumping configurations to files/Restoring configurations from files. | The format version of configuration dump to XML files is now 2.12. | The format version of configuration dump to XML files was 2.11. | The configuration dump to XML files now supports new platform features. |
| Data display. | New picture was added to the picture library: StartVideoConference | The listed picture was not available in the picture library. | The picture library is upgraded. |
| Full-text search. | Full-text search is now faster when the search is started from 1C:Enterprise language (including global search mechanisms) and filter by metadata is set (the FullTextSearchList.DataArea property). It will be faster if the full-text search index is built in version 8.3.7 and later compatibility mode. | When filter by metadata was set, full-text search was slow. | When filter by metadata is set, full-text search is faster. |
| Data composition system. | When conditional appearance is used in the Data Composition System, a conditional appearance element with the In overall usage area set is used to style templates of the overall resources horizontally and vertically in the table. This change is not implemented in 8.3.18 compatibility mode. | A conditional appearance element with the In overall usage area set was not used to conditionally style templates of the overall resources horizontally and vertically in the table. | Eliminated unexpected system behavior. |
| Pictures. Mobile platform. Mobile client. | The PictureToProcess object is now available in 1C:Enterprise mobile version. The following object methods are not implemented: SelectKeyArea(), SetColorDepth(), and SetDensity(). The features of other object properties and methods in this case can be found in Syntax Assistant. For the Picture object, the Width(), Height(), and FileSize() methods are now available in the mobile version. The ColorDepth(), GrayScale(), HorizontalDensity(), and VerticalDensity() methods always return Undefined in the mobile version. | In 1C:Enterprise mobile version, the PictureToProcess object and all methods of the Picture object were unavailable. | You can now implement some custom scenarios on mobile devices. For example, display thumbnails on the form (for more efficient use of mobile device resources). |
| Collaboration system. | You can now exchange a video stream only with the server upon group video calls. To do this, a special server application must be configured on the interaction server. | Group video calls were made in p2p mode. That is, the client application exchanged video streams with computers of all video call participants. | The load on the client computer upon a group video call and a large number of video call participants can now be reduced. Improved Collaboration System performance if a user has an asymmetric communication channel. |
| Mobile application builder. Mobile platform. Mobile client. | The distribution package of 1C:Enterprise mobile version contains requirements for the versions of the utilities used to build a mobile application. | The requirements for the utilities used to build a mobile application were not included in the mobile version distribution package. It was impossible for users to understand which utility versions to install to build a mobile application. | It is now possible to understand which versions of the utilities used to build a mobile application to install on the builder computer. If the versions do not match, troubleshooting is more understandable. |
| Licensing system. Analytics system. | You can now start a single 1C:Analytics client without a 1C:Analytics client license if no more than 5 client application sessions are connected to the infobase. | Starting 1C:Analytics client without its own license was not available. | The application developer can use 1C:Analytics for development purposes without the need to obtain a 1C:Analytics client license. |
| File operations. | Updated distribution package of Read more. file manager. The distribution package comes with an interface in all languages supported by 1C:Enterprise. | The distribution package of the file manager was available in two versions: only in Russian and in all languages supported by 1C:Enterprise. | Simplified file manager operations. Users no longer need to choose which distribution package they need. |
| Integration service. | You can now specify that receiving an integration service message will be processed outside a transaction. New property of the IntegrationServiceChannel configuration object: InTransaction. | Receiving an integration service message was always processed within a transaction. | You can now implement more flexible algorithms for integration service channels. |
| Collaboration system. | Optimized screen sharing module for thin, thick, and web clients. The new screen sharing module requires the Collaboration System server version 10 or later. To use the new screen sharing module in the web client, Google Chrome version 64 or later is required (in addition to the Collaboration System server version). The optimized version of the screen sharing module allows you to select a monitor to share (if there are multiple monitors), is faster, and loads the CPU of the computer used for sharing less. The previous screen sharing module is used if the subscriber cannot use the new module version in the video call. | The previous screen sharing module did not allow you to select a monitor to share, had lower performance, and loaded the CPU of the computer used for sharing more heavily. | Improved computer screen sharing when using Collaboration System. |
| Database copies. | Optimized execution of queries in a database copy when a large number of transactions are performed in the main database and data is transferred to the copy not very often. To enable optimization, restructure the infobase (by updating the configuration or on testing and patching). | Queries executed in a database copy were not optimized. | Improved performance of queries that can be executed on a database copy. |
| Spreadsheet documents. | Improved spreadsheet document switch to compact mode used on mobile devices. | Switching a spreadsheet document to compact mode was not optimal. | Improved spreadsheet documents view on mobile devices. |
| Mobile application builder. | Mobile Application Builder no longer supports the following features:
If you need to use these features, use Mobile Application Builder 8.3.18 or earlier. | Mobile Application Builder supported:
| Mobile Application Builder no longer supports obsolete technologies and mobile operating systems. |
| Mobile platform. Mobile client. Mobile application builder. | Starting from mobile version 8.3.19.52, you can build mobile applications for Android in the application bundle format (aab-file). Changed files in the mobile distribution package. With Mobile Application Builder, you can build applications in any format depending on the mobile version used to build the mobile application. With Mobile Application Builder, you can upload any built application option to the application store (but not both at the same time). Before importing version 8.3.19.52 or later to Mobile Application Builder, update the builder to the distribution package version. | 1C:Enterprise mobile version (including Mobile Application Builder) did not support building application bundles (aab files). | You can now build mobile applications and upload them to Google Play store. |
| Localization. | Localized client application interface for Turkmenian (tk). | This feature was not provided. | 1C:Enterprise is now available to Turkmenian-speaking users. |
| Mobile platform. Mobile client. Mobile device-specific features. | Improved recognition of DataMatrix codes using mobile device cameras:
The following changes are implemented when recognizing barcodes using mobile device cameras:
| DataMatrix code recognition did not work in some common situations. Scanning small barcodes with mobile device cameras was inconvenient. The pause between consecutive scans was 2 seconds. | Improved use of mobile device cameras to scan DataMatrix codes and other barcodes. |
| Database copies. | Improved performance of initial filling of a database copy. | Initial filling of a database copy took more time. | Improved performance of initial filling of a database copy. |
| Spreadsheet documents. | The Save command in spreadsheet documents works as follows:
This change is not implemented in 8.3.18 compatibility mode. | The Save command in spreadsheet documents was performed in the same way as the Save as command. | Eliminated unexpected system behavior. |
Version 8.3.18 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.17 is now implemented. | Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.16 was available. | Configurations developed using 1C:Enterprise platform version 8.3.17 or earlier can now run on version 8.3.18 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.18 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.17 after the migration to version 8.3.18, even if you disable the compatibility mode (simply enable it again). |
| Web client. | Support for the progressive web application (Progressive Web Apps, PWA) is implemented for the web client. A progressive web application is supported for Google Chrome version 73 and later, and if the web client is published using HTTPS protocol. The Display as a standalone application command is implemented in the Tools and Settings menu. The ProgressiveWebApplication global context property is implemented. The ProgressiveWebApplicationName web client start option is implemented. The progressiveWebApplication element is implemented for default.vrd file. | This feature was not provided. | Sending the web client application launch icon to the desktop is now available. The web client (in progressive web application mode) is started in a separate window, and not in a web browser window. |
| 1C:Enterprise script. | Updated asynchronous calls processing. Implemented the option to describe the method as an asynchronous, nonblocking analogue of a usual method. Asynchronous methods always return a Future object. The result of the asynchronous method is returned through this object. Implemented Asynch modifier used to describe the method. Implemented Future, AddInAsynchCallResult methods. Implemented Wait operator. The <MethodName>Asynch, Get<PropertyName>Asynch and Set<PropertyName>Asynch methods should be used to work with add-ins. These methods are added automatically by the platform; no add-in modification is required. For global context methods and 1C:Enterprise language objects starting with Show and Start, analogues with the Asynch name suffix are implemented. | This feature was not provided. Using asynchronous methods required using special notification handlers. | Using asynchronous methods was improved. |
| Internet-enabled functionality. Web client. | The feature to obtain information about the current computer network adapters MAC addresses is implemented in client applications (thin, thick and web client). Implemented NetworkAdapterInformation object. Install the extension to get information about the computer to use web client. Implemented StartInstallationOfExtensionToGetComputerInformation() and StartAttachingExtensionToGetComputerInformation() method. | This feature was not provided. | Getting MAC address of the client computer is now available if it is required to interact with external systems. |
| Localization. | Chinese language (zh, zh_CN) support is implemented for NumberInWords() method. | This feature was not provided. | Simplified the presentation of information for Chinese-speaking users. |
| DBMS operations. System requirements. | PostgreSQL DBMS 12 (x86-64) is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 12.2 is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| Common objects. | The DataHashing object can calculate the SHA512 hash function. | This feature was not provided. | The list of supported hash functions is extended. |
| Client application form. | Implemented the feature to specify a formatted string as the value of the Text property for the following planner items: PlannerItem, PlannerDimension, PlannerDimensionItem, PlannerBackgroundIntervalLabel, TimeScaleItemLabel. We have implemented the NewItemsTextType property for the Planner type form attribute, which allows to specify which text can be entered in new user-created planner items. Implemented the feature to set actions for the planner item. Implemented the PlannerItem.Actions property. You can specify various appearance properties (accessibility, picture, presentation, alignment, etc.) for each action. Implemented the feature to configure various system reactions to the selection of actions or clicking the hyperlinks in the planner items. The following events are implemented for planner field: OnURLClick, OnPlannerActionClick. Implemented the feature to create planner items that are not user-editable. Implemented the PlannerItem.EditingPermissionMode property. Implemented the feature to change the border color for planner background interval. Implemented the PlannerBackgroundInterval.BorderColor property. Implemented the feature to set the border for planner, planner background interval and planner item. Implemented the Border property for Planner, PlannerBackgroundInterval, PlannerItem objects. The Text parameter of BeforeCreate event of the planner extension for form field may have the values of Text and FormattedString type. The Text parameter of Add() method in PlannerDimensionCollection, PlannerDimensionItemsCollection and PlannerBackgroundIntervalLabelsCollection objects may have the values of Text and FormattedString type. The Text parameter of Insert() method in PlannerDimensionCollection, PlannerDimensionItemsCollection and PlannerBackgroundIntervalLabelsCollection objects may have the values of Text and FormattedString type. For system enumeration PlannerCommandSource the following new values are implemented: URL and Action. For system enumeration PlannerCommandGenerationParameters the URL, Action, Dimension values are implemented. For system enumeration StandardPlannerCommand the GotoURL, CopyURL, ExecuteAction values are implemented. | These features were not provided. | New planner use features. Implementing a more friendly user interface using a planner is now possible. |
| Global search. | Implemented the feature to set custom actions to the global search results. The set actions are displayed next to the global search result and are available for execution directly from the list of global search results. Implemented the GlobalSearchResultItem.Actions property. Implemented the OnGlobalSearchResultActionSelect application module event handler. | These features were not provided. | Enhanced global search results formatting options. |
| Configuration extensions. Administration tools. | Implemented the feature to use configuration extensions for the /MergeCfg Designer start command line command. The .cfe file may be used as command option. The -Extension option is implemented for this command to specify the extension, which the command will be executed for. | The /MergeCfg command did not allow to use the extensions. | Using extensions in automated scenarios in development, testing and maintenance of applications is now possible. |
| Configuration extensions. | Implemented the feature to expand the adopted objects attribute types, except for:
Selecting actions for individual types when comparing and combining the extensions was implemented. | This feature was not provided. | New extension features. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Collaboration system. | Implemented the feature to hide all important notifications with one click in 1C:Enterprise - Startup and Notifications application. This feature appears if three (or more) notifications appear. The button for clearing notifications in the notification center of the client application has Clear label now. | Hiding all important notifications with one click in 1C:Enterprise - Startup and Notifications application was not available. The button for clearing notifications In the notification center of the client application was called Clear notifications. | Improved using the notifications. A large number of notifications can be hidden in one action. |
| Collaboration system. | Implemented highlighting of new messages in an open conversation. Implemented an application title representation in the incoming video call title. Implemented a feature to insert pictures using Shift+Ins hot-key. When scrolling the list of messages up with the mouse wheel, the new messages are loaded automatically. When sending a message, the read flag for this conversation is set. Implemented caching of attachment files when they are received or opened (in the thin client) or received (in the web client). Implemented the feature to quote messages. Implemented the Quote command in the selected text context menu. The ">" character in the first position of the message line is the quotation flag. Implemented the feature to copy a message with attachments. For a client application running in Linux or Windows, the number of unread messages in the notification center is displayed as a number on the application icon in the taskbar and on the icon of the open notification list command. | These features were not provided. | Improved user operations in the collaboration system. |
| Web client. Add-ins. | 64-bit add-ins are now supported by the web client in 64-bit Google Chrome and Mozilla Firefox web browsers running Windows. | In 64-bit Google Chrome and Mozilla Firefox web browsers running Windows, the web client used 32-bit add-ins. | Improved support of 64-bit Google Chrome and Mozilla Firefox web browsers. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Standalone server. | Faster .DT file import to the infobase when using the standalone server management utility (ibcmd). | Importing a DT file to the infobase of a standalone server (using ibcmd utility) took longer. | Faster DT file import to the infobase of the standalone server. |
| Standard functions. | Faster opening of the standard function main form for event log browsing. | Opening the standard function main form for event log browsing took longer. | Improved event log browsing. |
| Server clusters. | The time to obtain a client license by the session is significantly reduced in the following cases:
| Obtaining licenses took a lot of time and significantly slowed down the sessions starting in case of mass starting (or restarting) of the client sessions. | Eliminated unexpected system behavior. |
| Data display. Server clusters. | Improved performance of the GetStringDeclensions() and GetStringDeclensionsByNumber() methods if the declension feature was used by several users at the same time when using client/server mode of the infobase. | If the GetStringDeclensions() and GetStringDeclensionsByNumber() methods are used by several users at the same time in the client/server mode of the infobase, execution of the methods took longer. | Eliminated unexpected system behavior. |
| Data access restrictions. | Improved performance of StrContains() function used in data access restriction templates. | Performance of StrContains() function used in data access restriction templates, was insufficient. | Improved performance of StrContains() function used in data access restriction templates. |
| DBMS operations. | When using queries from the platform to Microsoft SQL Server DBMS, their plans are cached in the same viewpoint of properties as when executing these queries from SQL Server Management Studio with default settings. This does not result in generation of a different query plan when the query is executed again in SQL Server Management Studio, which simplifies the analysis of the query operation. | When using the same query in Microsoft SQL Server DBMS directly from the platform and from SQL Server Management Studio, different query plans could be generated. | Simplified analysis of query plans that are used in Microsoft SQL Server DBMS. |
| Database copies. | Optimized the process of transferring completed transactions to the database copy. | The process of transferring completed transactions to the database copy took longer. | Faster transfer of data to the database copy. |
| Data composition system. Dynamic lists. | Faster opening of report and dynamic list settings, as well as generation of data composition templates, if child fields of fields for which a large number of characteristics are defined are used in the data composition settings. | If the data composition settings involve child fields of fields for which a large number of characteristics are defined, opening report and dynamic list settings, as well as generating data composition templates took a lot of time. | Faster opening of dynamic list and report settings forms. |
| Data access restrictions. | In data access restriction queries, a feature to replace subqueries that do not depend on the protected table with the result of their operation is implemented. Replacing one subquery for each protected table is supported. The result of calculating such subqueries is cached in the working process RAM. | Queries for data access restrictions were not subjected to additional processing and were always performed in their original form. | Improved performance of data access restriction queries. As a result of the change, the DBMS can plan a more efficient query. |
| Spreadsheet document. Processing PDF documents. | Improved spreadsheet document export to PDF performance. | Exporting a spreadsheet document to PDF required more time. | Improved performance of spreadsheet document export to PDF format. Possible reduced size of the resulting PDF document if the original spreadsheet document contains cells with changed text orientation. |
| Development tools. | Faster standalone configuration generation. | Standalone configuration generation took more time. | Faster standalone configuration generation. |
| Spreadsheet documents. | Improved performance of spreadsheet documents with numerous merged cells in a great number of rows. | Operations with a spreadsheet document with numerous merged cells in a great number of rows took more time. | Improved performance of spreadsheet documents. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Standalone server. | A partial import and export of configurations from files has been implemented for the standalone server management utility (ibcmd). The following items are implemented for the config export command:
The following commands are implemented for the config import command:
| The standalone server management utility (ibcmd) allowed only complete configuration import and export from/to files. | Expanded standalone server capabilities. |
| Internet-enabled functionality. | Implemented the feature to receive and set a custom text type for an email message when using InternetMail feature. Implemented CustomText value for the MailTextType enumeration. Implemented CustomTextType property for the InternetMailText object, which contains the actual text type from the email Content-Type property. If the platform cannot define the mail message type, the InternetMailText.TextType property is set to MailTextType.CustomText. The TextType parameter of the InternetMailTexts.Add() method may have a String type value. When generating the mail text that will be actually sent to the mail server, the charset parameter with the encoding specified in the InternetMailTexts.Encoding property will be added to (or replaced in) the Content-Type header. This change is not implemented in 8.3.17 version compatibility mode. | When using Internet mail, receiving the actual type of mail message was not available. If the platform could not define the mail message type, the InternetMailText.TextType property was set to MailTextType.SimpleText. When generating the text of the mail to be actually sent to the mail server, the charset parameter in the Content-Type header was not generated. | Improved working with emails such as meeting invitations that are sent from electronic calendars when using Internet mail. |
| Collaboration system. | Implemented a feature of creating a robot (bot) that runs on the 1C:Enterprise server (does not require a running instance of the client application) for the collaboration system. Implemented the CollaborationSystemBot object. The ProcessBots(), NewBot(), GetBot(), GetBots() methods were implemented for collaboration system manager. Implemented system background jobs for bot operations. Implemented the bot using features in the collaboration system management system data processor. | Implementing a robot (bot) required constantly running client application. Distinguished entity to describe bots was absent. | Simplified the robots (bots) creation in the collaboration system. A working robot does not require a running client application. |
| Server clusters. | New feature: parallel recalculation of register totals is available upon infobase restructuring, testing, and repair. System background jobs are used for recalculation. ID of such a background job is SystemBackgroundJob.RecalcTotals. Implemented the Number of totals recalculation job parameter for the Infobase parameters dialog box. There are 4 recalculation background jobs by default. New global context methods: GetTotalsRecalculationJobsCount() and SetTotalsRecalculationJobsCount(). | Register totals were recalculated sequentially upon infobase restructuring, testing, and repair for all required infobase registers. | New feature: totals are recalculated faster upon infobase restructuring, testing, and repair. |
| HTML support. | Availability of the HTMLDocumentShell.TemplateLanguageCode property in the Syntax Assistant was removed for the thick client. | The HTMLDocumentShell.TemplateLanguageCode property in the Syntax Assistant was available for the thick client. | Fixed bug in the Syntax Assistant. |
| Spreadsheet document. Processing PDF documents. | When saving a spreadsheet document to PDF, the JPEG pictures are saved in a compressed format. The picture format does not change. | When saving a spreadsheet document to PDF, the pictures were saved without using JPEG compression algorithms. | Reduced size of PDF documents if the original spreadsheet document contains JPEG images. |
| Configuration extensions. | Implemented a feature to continue full-fledged using of the configuration, if the extensions that perform data extension were not attached for some reason when starting the configuration. In this case, the default values for the corresponding types will be written in the extended attributes. | If not all extensions that perform data extension are attached on session start, the application could read the extended configuration data of successfully attached extensions without errors. At the same time, an attempt to write an object, which data is supplemented by a disabled extension, was not available. | An application that uses an extension, which performs data extension, remains fully functional (except for non-attached extensions), if not all extensions that perform data extension are attached. |
| Common objects. | The Russian letter "ё" is now supported by the GetStringDeclensions() and GetStringDeclensionsByNumber() methods. | The GetStringDeclensions() and GetStringDeclensionsByNumber() methods replaced "ё" with "е" and performed resulting string declension after that. | The Russian letter "ё" is no longer replaced with "е" when using GetStringDeclensions() and GetStringDeclensionsByNumber() methods. |
| 1C:Enterprise script. | The Number() function allows to convert exponential number representations to numbers only if the absolute value of that number order does not exceed 1,000. In the web client, the Number() function does not support conversion from the exponential number representation. | The Number() function allowed exponential number representations to be converted to numbers without limiting the order value. This could cause a very large memory consumption and a very large amount of time spent on arithmetic operations with these values. | Eliminated unexpected system behavior. |
| Add-ins. | The name of the temporary file, which the add-in is saved to before attachment, includes the name of the original add-in file. Thus, the full name of the add-in file consists of a prefix (assigned by the platform according to the standard algorithm for generating the temporary file name) and a suffix (which includes the name and extension of the original add-in file obtained from the add-in manifest). | The name of the temporary file, which the add-in is saved to before attachment, consisted only of an arbitrary temporary file name (with the .tmp extension) which was generated by 1C:Enterprise. | Simplified diagnostics of faults caused by problems in attached add-ins. Various event logs will clearly show the name of the add-in, in which the error occurred. |
| Applied objects. | If the main form attribute is ConstantsSet and there are no constants in the set when the form is opened (due to access right restrictions or displayed type restrictions), methods of reading data and writing data to an infobase are not called for the constant set upon opening or closing the form. | If the main form attribute was ConstantsSet and there were no constants in the set when the form was opened (due to access right restrictions or displayed type restrictions), unavailable infobase constants were filled in with defaults for their types. | Eliminated unexpected system behavior. |
| Client application form. | Changed the behavior of some buttons in the objects and record sets forms:
| The Delete, Reread, Mark for deletion, Activate and Copy commands were always available in the new object, information register records forms or external data source records. | Eliminated unexpected system behavior. |
| Common objects. | If the ConvertibleSplitterOfLines property is not set for DataReader object or is set to Chars.CR+Chars.LF, and the text file being read contains consecutive Chars.CR characters between the combinations of Chars.CR+Chars.LF, the ReadChars() method will be executed as follows:
This change is not implemented in 8.3.17 version compatibility mode. | If the ConvertibleSplitterOfLines property was not set for DataReader object or was set to Chars.CR+Chars.LF, and the text file being read contained consecutive Chars.CR characters between the combinations of Chars.CR+Chars.LF, the ReadChars() method could violate the sequence of characters (including permutation of characters, deletion and addition of Chars.CR or Chars.LF). | Eliminated unexpected system behavior. |
| Charts. | Improved the Gantt chart representation. This change is not implemented in 8.3.17 version compatibility mode. | The Gantt chart looked different. | Merging of connection lines is excluded, the number of connection lines of complex shape is reduced, the appearance of the chart items is improved on the Gantt chart. |
| Database configuration update. | When using the optimized infobase restructuring feature, the actual restructuring will be performed if:
| The optimized infobase restructuring feature always performed database tables restructuring if the following changes were made to the configuration objects:
| In some cases, significant improvement of the optimized infobase restructuring feature performance can be reached. |
| Data display. | If the parameter of the GetStringDeclensions() or GetStringDeclensionsByNumber() methods contains unequal number of opening and closing brackets or quotes, the platform will automatically fix this issue and decline the correct phrase. The resulting number of brackets or quotes will match the number of brackets or quotes in the parameter. | If the parameter of the GetStringDeclensions() or GetStringDeclensionsByNumber() methods contained unequal number of opening and closing brackets or quotes, the platform threw an exception. | The GetStringDeclensions() and GetStringDeclensionsByNumber() methods behavior became more logical. |
| Full-text search. | If a full-text search is used to search by the beginning of a line, all the results are highlighted in the search results representation, regardless of the number of results. | If a full-text search was used to search by the beginning of a line, and a large number of words were found that satisfied the search query as a result of the search, the found words may not be highlighted in the search results. | Eliminated unexpected system behavior. |
| Queries. | Query Wizard generates missing aliases of query fields using the same scheme as the query execution functionality. This change is not implemented in 8.3.17 version compatibility mode. | Query Wizard could generate missing aliases of query fields using a scheme different from the scheme used upon query execution. | Now automatic generation of aliases of query fields (in different platform tools) is consistent. |
| Collaboration system. | Implemented the standard collaboration system commands, which allow to copy the attachment and quote the message. Implemented the CopyAttachment and QuoteMessage values for CollaborationSystemStandardCommand system enumeration. Implemented the default constructor for CollaborationSystemUserIDCollection object. Implemented the VideoconferencesAreAvailable(), GetMaximumVideoconferenceParticipantsNumber() and StartVideoconference() methods for CollaborationSystemManager object. | These features were not provided. | Expanded the collaboration system usage capabilities. |
| Add-ins. Web client. | An attempt to use a non-existent add-in method or property in web client generates an error that can be caught in the Try–Except clause. The method or property is not called at all. The behavior in thick, thin, and web client applications is now the the same. | An attempt to use a non-existent add-in method or property in web client initiated a call from the web client. If a method or a property was missing, an error occurred only in the error handler specified in notification details. The error could not be caught in the Try–Except clause. | Web client behavior is now identical to thin and thick client behavior. |
| Mobile platform. Mobile client. | Implemented the HomePageSettings and HomePageForms objects on the mobile application server and the standalone mobile server. | The HomePageSettings and HomePageForms were not available on the mobile application server and the standalone mobile server. | Now you can customize the application home page on your mobile device. |
| Client application form. | In thick client and Designer, improved display of a table box whose header or footer contains numerous columns grouped into a composite multiline column using the Position of table box column property. | In thick client and Designer, a table box whose header or footer contained numerous columns grouped into a composite multiline column using the Position of table box column property, was displayed with delay. | Eliminated unexpected system behavior. |
| Data composition system. | The DCS template generator calculates the width (in cells) of each resource template displayed in a DCS table column as the maximum width of all templates displayed in this DCS table column (both generated and predefined templates). If predefined templates are specified for group and resource templates, the number of recourses specified for them in the data composition settings is not considered for such groups. This change is not implemented in 8.3.17 version compatibility mode. | The DCS template generator calculated the width (in cells) of each resource template displayed in a DCS table column based on all resources displayed in this template (in the data composition settings) and predefined templates. If the estimated template width was bigger than the predefined template width for a resource template specified for a table row/column intersection, the width of a template to create was equal to the estimated width. | Eliminated unexpected system behavior. |
| Data composition system. | When the Data Composition System groups by a calculated field, a presentation expression of this field (if specified) is used in this group and its nested groups when this field is displayed in the data composition result. This change is not implemented in 8.3.17 version compatibility mode. | When the Data Composition System grouped by a calculated field, a calculated field presentation was displayed in detailed records only. | Eliminated unexpected system behavior. |
| Client application form. | For a table that displays the value tree with one column, implemented the following algorithm for calculating the column width depending on the width of the text in rows of the tree being displayed:
For a table whose cell (not a complete row) is selected upon row selection, horizontal scrolling is done when you move between table rows or activate a row so that the text is fully displayed in the visible table area. If a text does not fit in the visible area, the text area is aligned to the left edge of the table. | For a table that displayed the value tree with one column, the column width and position of the text in a column did not depend on the text displayed in the tree. | Eliminated unexpected system behavior. |
| Configuration extensions. | When the ChangeAndValidate annotation is used in configuration extensions, the applicability check does not consider changes where empty strings and strings formed only with space and tab characters are added or deleted. | When the ChangeAndValidate annotation was used in configuration extensions, the applicability check considered changes where empty strings and strings formed only with space and tab characters were added or deleted. | Decreased the amount of false positives of the extension applicability check. |
| Spreadsheet document. Mobile platform. Mobile client. | Improved spreadsheet document conversion to compact mode (on a mobile device):
| The algorithm for spreadsheet document conversion to compact mode was different. The resulting spreadsheet document was not well suited for a mobile device. | Improved spreadsheet document display on a mobile device (compact spreadsheet document mode). |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration extensions. | Calling extended form methods from an extension using the Execute() method is no longer supported. Only the methods that are available through the ThisObject property can be called. It is recommended to analyze the extensions and refactor them, if necessary. This change is not implemented in 8.3.17 version compatibility mode. | Calling extended form methods from an extension using the Execute() method was supported. | A form extension can only use the documented interface for using an extended form. A “documented interface" refers to methods declared in a form module using the Export keyword. |
| Administration tools. | The service message output file, which is specified in the /Out command-line option of the client applications and Designer start, is generated in UTF-8. | The service message output file, which was specified in the /Out command-line option of the client applications and Designer start, was generated in the operating system encoding. | The service message output file is always generated in the same encoding, regardless of the operating system encoding. |
| Linux. System requirements. Standalone server. | When using Linux, the feature was implemented to simultaneously install several versions of 1C:Enterprise, including those that differ only in the last (fourth) digit of the number. Implemented automatic selection of the started client application version. Changed starting of the server cluster and the location of the srv1cv83 and srv1cv83.conf files. Implemented the feature to automatically update the client application over the network and from the web server. Implemented the feature to specify the location of client application distribution packages in the web client publishing dialog (in the Linux version of Designer). The PublishDistributiveLocationLinuxDEB64, PublishDistributiveLocationLinuxDEB32, PublishDistributiveLocationLinuxRPM64, PublishDistributiveLocationLinuxRPM32 parameters are implemented for conf.cfg file. Implemented the pubdstlindeb64, pubdstlindeb32, pubdstlinrpm64, pubdstlinrpm32 attributes for the <point> item of default.vrd file. Implemented the lindeb64, lindeb32, linrpm64, linrpm32 properties for the pubdst parameter of the standalone server configuration file. | These features were not provided. | Using several versions of 1C:Enterprise simultaneously is now available when using Linux. |
| Data display. | The Parameters parameter of StringWithNumber() method was renamed to NumberFormatString. A number format string similar to the Format() method can be passed to this parameter. The StringWithNumber() method generates a number representation considering the current session or the passed format string locale. | The StringWithNumber() method always generated a number representation considering the locale code passed as the method parameter and did not consider the current session locale. | Eliminated unexpected system behavior. The result of the StringWithNumber() method now matches the current session locale. |
| Applied objects. | The following changes have been implemented for document journals:
This change is not implemented in 8.3.17 version compatibility mode. | The following behavior of document journals was observed:
| Eliminated unexpected system behavior. |
| Collaboration system. | Reviewed the feature for working with actions in the collaboration system messages. The CollaborationSystemMessageActionsCollection type was implemented to generate the list of actions. The CollaborationSystemMessageActionsCollection becomes a value type for the CollaborationSystemMessage.Actions property. This change is not implemented in 8.3.17 version compatibility mode. Implemented the OnCollaborationSystemActionSelect event handler for application module. The AttachMessageActionHandler() and DetachMessageActionHandler() are collaboration system manager methods considered obsolete and are not recommended for use. It is necessary to change the algorithms for working with actions in the collaboration system messages in applications. | A list of values was used to specify the list of actions of the collaboration system. Setting the collaboration system message action handlers required using the AttachMessageActionHandler() and DetachMessageActionHandler() collaboration system manager methods. | Procedure of using actions is unified with the other platform features. |
| Data composition system. | If the data composition schema query contains union, and a filtering field is available for applying filter only (and is not available for selection) in several union parts, then the filter is applied only to the union parts where this field is available for filtering. It is recommended to review data composition schemas that contain queries with unions. This change is not implemented in 8.3.17 version compatibility mode. | When applying a filter to a data set query containing a union, the filter was applied to all the union sections if at least one section a filtering field available for filter. | The result of applying filter in the data composition schema has become more predictable. |
| Full-text search. | When setting the value of the FullTextSearchList.SearchArea property, an exception is thrown if the array being set contains an item that is not a metadata object. This change is not implemented in 8.3.17 version compatibility mode. | When setting the value of the FullTextSearchList.SearchArea property, the validation of the value being set was not performed, however, when an attempt was made to get the search result (FullTextSearchList.First Part() method), an exception was thrown with incomprehensible text. | Validation of parameters is aligned with standard practices. The error message now corresponds the detected error. |
| Charts. | The DataSource chart property is not available in the thin client and web client. When attempting to set the value of this property using 1C:Enterprise language, an error is generated. This change is not implemented in 8.3.17 version compatibility mode. | The attempt to set the DataSource chart property depended on the client application:
| Eliminated unexpected system behavior. |
| Charts. | Interactive chart editing with a set data source is not supported. This change is not implemented in 8.3.17 version compatibility mode. | For a chart with a set data source, the following behavior was observed when attempting to edit interactively:
| Eliminated unexpected system behavior. |
| Client application form. | Window settings for thin client, web client, mobile client and mobile platform are stored with different settings keys suffixes. When changing the configuration compatibility mode, the following actions are performed:
New settings keys are given in the documentation. If the configuration uses direct operation with the window settings, it is recommended to analyze the program code that interacts with the settings and make appropriate changes to it. This change is not implemented in 8.3.17 version compatibility mode. | These features were not provided. Settings were stored separately for the web client (one setting) and all other client applications (another setting). | The client application window settings for different types of client applications are stored separately and do not mix with each other. Implementing software operations with the window settings of a single type of client application is simplified. |
| Data composition system. | If condition Contains, Does not contain, Like, Not like, Begins with, or Does not begin with is specified for data composition filter set at the data set level and the condition string contains a single double quote ("""), Data Composition System escapes such characters automatically upon data composition template generation. This change is not implemented in 8.3.17 version compatibility mode. | If condition Contains, Does not contain, Like, Not like, Begins with, or Does not begin with was specified for data composition filter set at the data set level and the condition string contained a single double quote ("""), Data Composition System did not escape such characters upon data composition template generation. Executing such data composition might have caused an error. | Eliminated unexpected system behavior. |
| Information registers. | Only register records with the Activity property set to True are included in the result of a query to a virtual table of the SliceLast information register. This change is not implemented in 8.3.17 version compatibility mode. | All register records were included in the result of a query to a virtual table of the SliceLast information register, regardless of the Activity property value. | Eliminated unexpected system behavior. |
| Input by string. Global search. Dynamic list. Full-text search. | Implemented the search query complexity limitation. The overall search query length must not exceed 1000 characters and 32 words. The limitations are implemented for the following mechanisms:
In the parameter structure of the GetChoiceData() method, the LimitSearchString parameter that provides search without analyzing a search query is expected. Implemented the FullTextSearchList.LimitSearchString property. If this property is set to False, full-text search does not analyze a search query. This change is not implemented in 8.3.17 version compatibility mode. | There was no search query complexity limitation, except for the search string of a dynamic list where the search string was not to exceed 1000 characters and 20 words. | Complexity of a search query to built-in search tools is limited to avoid high server load and unexpected shutdown due to a complex search query. |
| Add-ins. | Examples from add-in development technology are switched to build with CMake. Static libraries for creating adapters for web browsers running Windows are built with Microsoft Visual Studio 2017 compiler that supports Windows XP. Developers who develop circulation add-ins must develop an add-in for all operating systems from the list of system requirements Read more.. Web client adapters for Windows must be built with Microsoft Visual Studio 2017 compiler that supports Windows XP. Developers whose add-ins are developed for a specific deployment case can use the compiler they used for supported operating system versions. Still, use Microsoft Visual Studio 2017 compiler that supports Windows XP to build web client adapters for Windows. Changes were made to development technology for add-ins (read more). | Examples from add-in development technology were built with Microsoft Visual Studio 2013. | A more modern set of tools is used to build demo add-ins. |
| Client application form. | A line that does not fit to width in decorations, label fields, or field headers is broken by a word separator closest to the form item edge. Upon disabling the compatibility mode, we recommend that you check that forms with texts that do not fit to width in decorations, label fields, or field headers are displayed correctly. This change is not implemented in 8.3.17 version compatibility mode. | A line that did not fit to width in decorations, label fields, or field headers could be broken by a word separator that was not closest to the form item edge. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile platform. Mobile client. | Implemented the feature to control the automatic image rotation when using the MultimediaTools.MakePhoto() method. To do this, the AutoRotate option is implemented in this method. | When using the MultimediaTools.MakePhoto() method, the mobile version always rotated the resulting image if the orientation of the phone at the time of taking the photo did not match the orientation of the resulting photo. | Improving the performance of taking photos by disabling the resulting photo turning is now possible. |
| Client application form. | Implemented the grouping of fields in a system form, which is generated for editing a form table row (not associated with a dynamic list), if such grouping is implemented in the table settings. Only the first level of grouping is displayed. Other grouping levels are not displayed. They are placed in the parent group of the first level instead. | All the table row fields were displayed in a list without grouping in a system form, which was generated for editing a form table row (not associated with a dynamic list). | Improved automatically generated form for editing a form table row. |
| Development tools. | Now you can set up module check in the standalone mode of a mobile client in Service – Parameters – Modules – Check. Implemented the Mobile client (standalone mode) and a standalone mobile server check box. | This feature was not provided. | Simplified real-time check of modules to be run in the standalone mode of a mobile client. |
| Printing tools. Mobile platform. Mobile client. | Now the mobile application supports printers that are supported by the used mobile operating system. You can switch between printing through the operating system and printing using the platform tools (printers that support PCL3 and ZPL languages) in infobase settings on your mobile device (in Service and settings - Settings) or in Mobile Application Builder (the Print mode application settings property). | 1C:Enterprise mobile platform supported only printers supporting PCL3 and ZPL languages. | Extended list of printers supported by 1C:Enterprise mobile platform. |
| Mobile platform. Mobile client. | Updated permission management for a mobile application built using Mobile Application Builder. Implemented the functionality mechanism that combines a mobile application permission and a text displayed to a user upon request for a permission. Included the mobile version functionality module in the mobile application. If the functionality is disabled, the matching module will not be included in the build and an attempt to use this functionality will generate a runtime exception (on a mobile device). Settings of mobile application functionalities can be accessed using the configuration property Used mobile application functionality. Before you build a configuration to be dumped using version 8.3.18, we recommend that you check that the required functionality is specified correctly for the configuration. | The mechanism of mobile application permission management was different. It did not affect the total size of an application to build. A disabled permission might not affect performance of a built application. | Now it is easier to manage the used mobile application functionality. When a developer specifies a functionality, they must also specify the text to be displayed to a user upon request for a permission and make this functionality available for use. |
The Assistant conversations features are moved to the OfficeManager bot.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Queries. Common attributes / Data separation. | In infobase file mode, execution of a query where an inner join between object data and its tabular section is being created is faster now. The upgrade is valid if an object used in a query is part of a common attribute that is a separator. | In infobase file mode, it took more time to execute a query where an inner join between object data and its tabular section was being created for an object included into the separator. | Eliminated unexpected system behavior. |
| Development tools. | Now you can press Ctrl+Alt+E to abort long-running operations on Windows. You can still press Ctrl+Break for this purpose. Both shortcuts can be used at the same time. | To abort long-running operations, you could press Ctrl+Break on Windows. | Now you can abort long-running operations on devices without the Break key. |
| Charts. | A chart tooltip is no longer covered by a formatted document field or the planner field. A chart tooltip is displayed without semitransparency if a thin or thick client application runs Linux or macOS. | A chart tooltip could be covered by a formatted document field or the planner field. It was impossible to view some tooltip information. | Eliminated unexpected system behavior. |
| Configuration extensions. | New feature: you can change data of a configuration object whose attribute types are changed by an inactive extension. When reading objects with attribute types modified by disabled configuration extensions, values stored in a database will be converted to configuration types, ignoring inactive extensions. On recording, only changed attributes will be updated. Information about disabled extensions is added to an error report. Changed the format of the report.json file to which collected error information is placed automatically. We recommend that you use this mode as emergency mode when you need to update an application infobase if there are extensions that are incompatible with a new configuration version. | It was not possible to change data of a configuration object whose attribute types were changed by an inactive extension. | Simplified configuration update if an extension that modifies attribute types of an extended configuration becomes inactive once the extended configuration is updated. |
| Mobile platform. Mobile client. Mobile application builder. | Now you can open the mobile application by clicking an URL. You can set up schemas and links the mobile application reacts to in Designer or Mobile Application Builder. Now the configuration supports navigation to the application when clicking an URL. New configuration property: MobileApplicationURLs. New handler in the application module: URLNavigationProcessing(). New global context method: GetExternalURL(). | This feature was not provided. The mobile application could not be called from another application, for example, when a hyperlink was placed in email. | Added new features for 1C:Enterprise mobile version. Now you can register specific URLs. When you click them in another application, the mobile application opens automatically. |
| System requirements. | 1C:Enterprise now supports Microsoft Windows Server 2019 (x86-64). | 1C:Enterprise did not support Microsoft Windows Server 2019 (x86-64). | The list of supported operating systems is extended. |
| Client application form. | In the client application form, you can now handle the following events of the form field extension for the planner field:
Implemented the event handler of the form field extension of the client application for the CheckDraggingInside planner field. For the event handler of the form field extension of the client application for the BeforeCreate planner field, the following parameters become return parameters: Start, End, DimensionsValues, and Text. | Dragging items within the planner field and changing the size of planner field items were not available. | New features for interactive editing of the planner field. |
| Error handling. | Implemented a new error category: a database copy error. Errors that occur while using database copies fall into this category. Implemented value of the ErrorCategory.DatabaseCopyError system enumeration. This change is not implemented in 8.3.17 compatibility mode.
| Errors that occurred while using database copies fell into the category of external data source errors. | Improved error categorization. |
| Spreadsheet documents. Web client. | Improved update of a spreadsheet document displayed in the web client with scale greater than 100% when editing text in cells. Once you finish editing text in a cell, the server is no longer called if the entered text fits the cell. | Once you finished editing text in a cell of a spreadsheet document displayed in the web client with scale greater than 100%, the server was called if the entered text fitted the cell. | Eliminated unexpected system behavior. |
| Internet-enabled functionality. | New property: NetworkAdapterInformation.IPAddress. The property contains a network adapter IP address that describes the NetworkAdapterInformation object. | This feature was not provided. | Expanded the network adapter information provided by 1C:Enterprise. |
| Full-text search. Error handling. | An attempt to search by a word for which a lot of matches are found generates an error. Reduced the full-text search index size for very large infobases. New system enumeration value: ErrorsCategories.FullTextSearchError. We recommend that you clear the full-text search index and build it again if the full-text search index size exceeds 50 Gb. When the previous platform version with the full-text search index built by platform version 8.3.19 is started, the index will be cleared and built again. | An attempt to search by a word for which a lot of matches were found could lead to unpredictable results. | Improved stability and fault tolerance of full-text search. |
| System requirements. DBMS operations. | Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
| The following Postgres Pro DBMS versions were not supported:
| Extended list of supported DBMS. |
| Mobile application builder. | The version of Mobile Application Builder now matches the number of the 1C:Enterprise mobile version the builder is supplied with. Thus, Mobile Application Builder that comes with the mobile version 8.3.18 has the version number 8.3.18.*. The fourth digit of the builder version number indicates the builder build number and has nothing to do with the fourth digit of the number of the mobile version of 1C:Enterprise. | Mobile Application Builder had the numbering that did not match the number of the mobile version of 1C:Enterprise. | The numbering of Mobile Application Builder is now more transparent and associated with its mobile version of 1C:Enterprise. |
| Mobile application builder. | Mobile Application Builder does not support mobile versions of 1C:Enterprise whose number (first three digits) is greater than the builder version number (first three digits). Mobile Application Builder 8.3.18 will not load the mobile version 8.3.19 and later. The builder still allows you to upload the previous mobile versions of 1C:Enterprise (8.3.17 and later). In Mobile Application Builder, you can now block loading of configurations whose format is not supported by the current builder version. | Mobile Application Builder did not have any restrictions on loading mobile configurations and mobile versions of 1C:Enterprise. This could lead to hard-to-diagnose issues when configurations or mobile versions not supported by the builder were uploaded to the builder. | Mobile Application Builder no longer supports loading of objects that it does not support. |
| Linux. System requirements. | The following Linux distributions are now supported:
The following Linux distributions are no longer supported:
| The following Linux distributions were supported:
| The list of supported Linux distributions is brought up-to-date. |
| Full-text search. | Changed the algorithm to perform the standard type of the Data global search. As a result, the search returns a more relevant result in less time. For the algorithm description, see the documentation. | When performing the standard type of the Data global search, the result might not match the search string well. | Improved relevance and performance of the standard type of the Data global search. |
| Licensing system. | For system distribution packages designed for Windows XP, HASP Device Driver version 7.63 is now included. The outdated haspds_windows.dll and hdinst_windows.dll files are removed from the distribution package. | For system distribution packages designed for Windows XP, HASP Device Driver version 7.92 that did not run on this operating system was included. | Windows XP users can install HASP Device Driver directly from the current 1C:Enterprise distribution package. |
| 1C:Enterprise script. | Improved performance of the Insert() and Get() methods of the Map object for cases when a reference to an infobase object is used as a map key. | The Insert() and Get() methods of the Map object showed poor performance when a reference to an infobase object was used as a map key. | Eliminated unexpected system behavior. |
| Mobile device-specific features. | Upgraged the in-app purchases mechanism. The purchases mechanism is based on the Google Play Billing 3 library. New parameters for the InAppPurchases.UpdatePurchaseInformation() method: PurchaseType and AutoConfirmation. New parameter for the InAppPurchases.BeginPurchasing() and InAppPurchases.PurchaseAsync() methods: AutoConfirmation. New methods for the InAppPurchasesManager object: PurchasesConfirmationSupported(), CheckConfirmation(), and ConfirmPurchase(). To build a mobile application that supports the new in-app purchases mechanism, use Mobile Application Builder version 8.3.18 or later. We recommend that you refactor the application to switch to the new in-app purchases interface. The old purchases mechanism is only supported in version 8.2.17 and earlier compatibility mode. | The in-app purchases mechanism was based on Google Play through Android Interface Definition Languages. | Upgrade: the mobile application monetization mechanism is now supported, which will be required when publishing in Google Play, starting in August 2021. |
| Integration service. | You can now get the state of connection to an external integration service. You can now receive and delete messages that are in the integration service channel. New methods for the manager of the external integration service channel: GetState(), SelectMessages(), and DeleteMessages(). | These features were not provided. The message when sent could only be out of date. If an error occurred while sending a message, this message blocked the channel. | New operations with messages in the channel of the external integration service. |
| Mobile application builder. Mobile platform. Mobile client. | In Mobile Application Builder, you can now build mobile applications for iOS if the build uses a Mac based on the Apple M1 processor and uses macOS Big Sur. | Mobile Application Builder did not support running a build of mobile applications for iOS when the build used a Mac based on the Apple M1 processor and used macOS Big Sur. | Mobile Application Builder now supports modern Apple computers and operating systems. |
| Client application. Client application installation. Administration tools. | On Linux, it is now possible to update the distribution package without additional configuration of the default.vrd file (via the distr directory of a specific version directory). For Linux and Windows, installation package files that contain all client applications are implemented. | Updating the distribution package without additional configuration of the default.vrd file (via the distr directory of a specific version directory) was supported only by client applications for macOS and Windows. | It is now easier to configure distribution of client application distribution packages when updating the 1C:Enterprise version on servers running Linux. |
| Web client. | The web client now supports URLs:
| These features were not available in the web client. | Web client URL features are now in line with the rest of the client applications. |
| Mobile application builder. | It is now easier to load configurations into Mobile Application Builder. The builder automatically determines which group to place the configuration to be loaded in. You can now view properties of the used configuration directly from the built mobile application card. For a configuration loaded into the builder, it is now possible to get a list of applications that include this configuration. | To load a new mobile configuration version, it was necessary to manually determine which group to load the configuration into, which was not very easy with a large list of used configurations. Mobile Application Builder did not provide an easy way to get a list of applications that used any configuration. It also did not allow you to quickly view the configuration properties in the built mobile application card. | Managing mobile configurations in Mobile Application Builder is now more convenient. |
| Mobile client. | The mobile client signature on the server is verified in accordance with the parameter value in the infobase settings. The parameter in the infobase settings is called Mobile client signature verification. New global context methods to access the parameter value: GetMobileClientSignatureVerificationMethod()/SetMobileClientSignatureVerificationMethod(). | The mobile client signature on the server was always verified, regardless of the parameter value in the infobase settings. The parameter in the infobase settings was called Mobile client signature verification on database configuration update. | You can now disable useless troubleshooting if the application is not used with the mobile client and the mobile client does not require configuration signature verification. |
| System requirements. Mobile platform. Mobile client. | Mobile applications built using mobile version 8.3.18.71 will meet the requirements of Google Play for new applications. The target SDK version is 30. To upload a mobile application to Google Play, build a mobile application using mobile version 8.3.18.71 or later. | Mobile applications built using mobile versions that are older than 8.3.18.71 could not be uploaded to Google Play after August 1, 2021. | 1C:Enterprise mobile version meets the requirements of Google Play. |
| Mobile platform. Mobile client. | New mobile version functionality: Access to all data. If a configuration has this functionality enabled, an Android mobile application that includes this configuration will have permission to access an arbitrary place (within the global restrictions of the operating system) in the file system of a mobile device. | Access to an arbitrary place in the file system of an Android device did not require any permission to be specified. | Improved compliance with the requirements set by Google for Android mobile applications. |
| Client application installation. Administration tools. Linux. | If 1C:Enterprise server is updated to version 8.3.20 or later and the client application update is set up via the server (any method), thin client 8.3.18 and 8.3.19 managed by Linux can be updated to version 8.3.20. To update the application, you can use not only distribution packages in .deb and .rpm formats but also in .run format (implemented in version 8.3.20). | The client application managed by Linux could be updated only using distribution packages in .deb and .rpm formats. After update to version 8.3.20, the client application could not be automatically updated to the current version. | Migration to version 8.3.20 is now as easy as migration to previous versions despite the changed file format of the distribution package. |
| macOS. System requirements. | macOS Big Sur (version 11) is now supported. Under macOS Big Sur the SystemInformation.Processor property always contains the x86_64 value. | 1C:Enterprise application did not work under macOS Big Sur (version 11). | Extended list of supported macOS versions. |
| Analytics system. | To execute data queries, the analytics system uses a session pool similar to a pool processing HTTP service queries. New session type: Analytics system query. To set up the pool, use the analytics element of the default.vrd file. 1C:Designer infobase publication interface does not support editing pool settings. | To execute data queries, the analytics system used background jobs. | Accelerated the analytics system queries to infobase data due to faster session initialization. |
| Processing PDF documents. | You can now convert a PDF document to grayscale. New methods for the PDFWriter object: ConvertToGrayScale() and ConvertToGrayScaleAsync(). | This feature was not provided. | Advanced PDF document features. |
| Database copies. | Improved performance of queries executed in a database copy. | Execution of queries in a database copy took more time. | Improved performance of queries executed in a database copy. |
| Data composition system. External data sources. | Fields of external data sources of the non-reference type received using dot syntax from another field become available in the source of available data composition settings. That means that such fields can be used in the data composition settings. | Fields of external data sources of the non-reference type received using dot syntax from another field were not available in the source of available data composition settings. That meant that such fields could not be used in the data composition settings. | Eliminated unexpected system behavior. |
| DBMS operations. | PostgreSQL version 10.18 (x86-64) is supported. | This version of PostgreSQL was not supported. | Extended list of supported PostgreSQL versions. |
| DBMS operations. | PostgreSQL version 11.13 (x86-64) is supported. | This version of PostgreSQL was not supported. | Extended list of supported PostgreSQL versions. |
| DBMS operations. | PostgreSQL version 12.8 (x86-64) is supported. | This version of PostgreSQL was not supported. | Extended list of supported PostgreSQL versions. |
| DBMS operations. | PostgreSQL version 13.4 (x86-64) is supported. | This version of PostgreSQL was not supported. | Extended list of supported PostgreSQL versions. |
| DBMS operations. | PostgreSQL version 14.0 (x86-64) is supported. | This version of PostgreSQL was not supported. | Extended list of supported PostgreSQL versions. |
| Analytics system. Standard functions. |
New features for the standard "Analytics system management" data processor:
| The standard "Analytics system management" data processor did not support virtual table parameters in queries to additional sources. For the list of additional sources, only additional source registration was available in the data processor. | The standard processor features are compliant with 1C:Enterprise features.
|
| System requirements. | Minimum system requirements are specified for platform components:
The user can now read in the documentation about recommended hardware to select an optimal hardware configuration. | Minimum system requirements for platform components were as follows:
| Specified some system requirements.
|
| System requirements. DBMS operations. | The system now supports Postgres Pro DBMS of the following versions (only for x86-64):
| These DBMS versions were not supported. | Extended list of supported DBMS. |
Version 8.3.17 includes known bug fixes and functionality modifications.
Thick client and Designer for macOS are out of beta.
Data Accelerator and database copy features now require a CORP license.
The feature testing license now does not provide access to the Data Accelerator and database copy features.
Added a beta testing server license for 1C:Analytics. It provides access to the 1C:Analytics, Data Accelerator, and database copy features.
New feature: license to start 1C:Analytics client. The number of concurrent sessions of 1C:Analytics client are determined by the license value. The license to start 1C:Analytics client can be PROF or CORP.
The license to start 1C:Analytics client is installed on a computer with 1C:Enterprise server cluster and allows you to:
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.16 is now implemented. | Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.15 was available. | Configurations developed using 1C:Enterprise platform version 8.3.16 or earlier can now run on version 8.3.17 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.17 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.16 after the migration to version 8.3.17, even if you disable the compatibility mode (simply enable it again). |
| Data display. | New pictures were added to the picture library:
Conversations image was updated. | The listed pictures were not available in the picture library. | The picture library is upgraded. |
| Error handling. | The following features related to the application running error processing were implemented:
ErrorProcessing global context property was implemented. Error Processing Settings Management standard function is now available, which allows you to configure error texts. BriefErrorDescription(), DetailErrorDescription(), and ShowErrorInfo() global context methods are deprecated. It is recommended to use the similar methods of the ErrorProcessing object. When running Linux, the libunwind library is used to get the application stack when an error occurs. | These features were not provided. Local processing of recoverable errors was available only. | You can now make error texts easier to understand by end users. Error processing in 1C:Enterprise language was improved. |
| Server clusters. Client application. | When in the client/server mode, you can by default delete temporary files created using GetTemporaryFileName() method on the side of the PC(s) running the server cluster in the following scenarios:
Temporary files are deleted as soon as you start 1C:Enterprise processes (client applications, server cluster processes) without delaying the start. | Temporary files were only deleted when the 1C:Enterprise processes were started. The system startup speed depended on the number of temporary files to be deleted. | 1C:Enterprise processes performance is improved, if there is a large number of temporary files generated by 1C:Enterprise itself. The risk of running out of space on the hard drivers where the temporary file directories are located is mitigated during prolonged operation without restarting and inaccurate application handling of the temporary files being created. The number of simultaneously existing temporary files with names that were obtained using GetTemporaryFileName() method was reduced. |
| Collaboration system. | Integration with external (with respect to the collaboration system) instant messaging systems was implemented for the collaboration system. Interaction with the following systems is now supported: Telegram, VKontakte. CollaborationSystemIntegration object is supported. CreateIntegration(), GetIntegration(), GetIntegrations(), GetExternalSystemTypes() and GetExternalSystemDescription() methods were implemented for CollaborationSystemManager object. CollaborationSystemUser.ExternalSystemType, CollaborationSystemUser.ExternalSystemUserID, CollaborationSystemConversion.Integration and CollaborationSystemConversationFilter.Integration properties were implemented. | This feature was not provided. | Expanded collaboration system capabilities. |
| Configuration extensions. | You can now borrow event subscriptions and create your own subscriptions in the extension. | This feature was not provided. | Extended configuration extension options. |
| Client application. Data display. System requirements. | You can save a spreadsheet document in Microsoft Excel 97 format in a client application running macOS. In Linux, to save in Microsoft Excel 97, use libgsf-v8 library included in 1C:Enterprise platform distribution package. Thus, libgsf-1 and libglib-2.0 libraries are no longer required. You cannot save a spreadsheet document in Microsoft Excel 95 format in Linux and macOS. | You could save a spreadsheet document in Microsoft Excel 97 format in Linux only. Nominally, you were able to save a spreadsheet document in Microsoft Excel 95 format in Linux and macOS. However, in practice this feature was unavailable. | Users of client applications running macOS can now save spreadsheet documents in Microsoft Excel 97 format. |
| Development tools. | A technical specialist mode is implemented for a managed client application. The following features are available in this mode for managed forms:
| This feature was not provided. It was difficult to determine which form is currently used in the client application. | Technical specialists operations as part of application development or deployment process were made easier. |
| Common objects. | You now can identify IP-address of a PC, where an infobase user session was started. IP-address cannot be determined in every instance and in every mode of operation. ClientIPAddress property was implemented for AdministrationSession and InfobaseSession objects. Now, IP-address of a client application can be displayed in the cluster console and standard server management processor. ISessionInfo.getClientIPAddress() property is now available in the administration server interface in Java language. Client-ip field is now available in the command-line utility (rac) of a server cluster. It displays values returned by session info command.. SessionNumber and ClientIPAddress parameters are now available for the onStartSession() method of external session management Web-service. New features are only available, if wsver is assigned 3. | This feature was not provided. | You now can identify IP-address of a PC, where an infobase user session was started. |
| Analytics system. | 1C:Enterprise is now integrated with 1C:Analytics (analytics system). In the publishing settings on the Web server, you can enable analytics system publication. In the Service and Settings menu, Analytics System command is now supported, thus allowing you to open a tab with analytics system in the web browser for the current user. Standard Analytics System Management function is supported to integrate it with the infobase. So far as global context is concerned, AnalyticsSystem property is available. AnalyticsSystemClient access rights are supported. 1C:Analytics is not included in distribution package. Information on this functionality is published separately. | This feature was not provided. | 1C:Enterprise is now integrated with 1C:Analytics (analytics system). |
| Data composition system. | You can pass temporary tables manager to data composition system. In the data composition system, you can use tables that do not exist in the infobase similarly with temporary tables in the query language. The TempTablesManager parameter is now available for the DataCompositionProcessor.Initialize() method. | This feature was not provided. You were able to use temporary tables in the data composition system only as part of a batch query. | Now, you can use pre-defined temporary tables, when a query is executed by the data composition processor. |
| Spreadsheet documents. Charts. | Now, you can manage the way an image selection box is displayed in a spreadsheet document in a client application form.
To expand the form field boundaries, DrawingsSelectionView property is supported for spreadsheet fields. This upgrade is ignored in 8.3.13 version compatibility mode. | This feature was not provided. When you selected a chart in a spreadsheet document available in the client application form, the said chart was always highlighted. | Now, it is much more easier to use charts in a spreadsheet document available in the form. |
| Data display. Сlient application form. | Nested dimension items can be created and text in background bands displayed in the Planner. The PlannerDimensionItem object now supports Items, Parent, and ShowItemsAreaOnlyForSubordinateItems properties. The PlannerDimensionItemsCollection.Find() method now supports IncludeSubordinates parameter. To expand the form field, planner filed supports the following:
Text parameter is available for Add() and Insert() methods (PlannerDimensionCollection and PlannerDimensionItemCollection objects). When you use this parameter, it is recommended to specify its value to avoid server calls getting presentations. | These features were not provided. | Now, you can implement a group of planner dimension items similarly to a group of spreadsheet or hierarchical catalog lines. |
| DBMS operations. System requirements. | The following Oracle Database DBMS versions are supported now:
| These Oracle Database DBMS versions were not supported. | Extended list of supported Oracle Database DBMS versions. |
| Integration service. | Integration service creating feature was implemented. Integration services allow to coordinate with the "External integration service" product. The IntegrationServices property of 1C:Enterprise language was implemented. Managing integration services was implemented in standard functions. "External Integration Service" is not included in distribution package. Information on this functionality is published separately. To use integration services, a license to test dedicated functionality is required. The integration services will not be available without a license to test the dedicated functionality. | This feature was not provided. | Interaction with "External Integration Service” was implemented. |
| Web client. | Language support with spelling from right to left is implemented for the web client. This mode is supported automatically in the entire client application interface, with the exception of the following form elements: planner, chart, Gantt chart, dendrogram, graphical schema field and graphical schema field. The requirement to change the interface is determined by the interface language or configuration language. The web client now supports Arabic formats for numbers and dates. When calculating the arrangement of form elements and other interface items, the default font is Almarai. The web client supports using specialized Arabic characters for writing arithmetic expressions. In such cases, the expressions are calculated correctly. | The web client did not support using of languages with right-to-left spelling. | It has become possible to use 1C: Enterprise (using a web client) in countries where the national language uses right-to-left spelling. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Web client. File operations. | As soon as you open an external report or data processor file on a web client (without a file system extension installed), there is no need to reopen the selected file after positive feedback to security warning. In a file opening dialog box on a web client, now you can select a filter to search files you need to open (if it is defined, when you open a dialog box). | As soon as you opened an external report or data processor file on a web client (without a file system extension installed), you needed to reopen the selected file after positive feedback to security warning. In a file opening dialog box on a web client, there was no option to define a filter to search files. | Now, you can open an external report or data processor on a web-client (without a file system extension installed) in a easier and user-friendly way. Moreover, it's much more easier to open other files on a web client now. |
| Data display. | Some platform images (including part of image library) now have different appearance (they were redrawn) and are now implemented in SVG format. In the Taxi interface windows appearance was modified. They are now generated by ShowUserNotification() and State() global context methods. | Some platform images (including part of image library) had different appearance, and they were implemented in PNG format. Appearance of windows generated in Taxi interface using ShowUserNotification() and State() global context methods was different. | Visual perception of 1C:Enterprise interface was improved. |
| Error handling. | As soon as you open a dialog box with information for technical support team, the entire text available in the input field is selected by default. | When you opened a dialog box with information for technical support team, text available in the input field was not selected. | Now, you can copy information for technical support team (if necessary) easier and without delay. |
| Global search. Client application. Web client. | The following global search commands are available:
Search Everywhere context menu command is available, only if a pointer is set on a word or you selected a text block. If no text block is selected, and a pointer is on a word, search is made using the said word or URL (whenever a pointer is placed on URL). In Search Everywhere command presentation in the menu a text block is added which will be searched, whenever you use this command. Whenever you use Safari browser on a web client, click the right mouse button in the input field, formated or text document to select the entire word with a pointer placed thereon (without further analysis of that word). Whenever you use a thin, thick or web client (other than Mozilla Firefox and Safari browsers), click the right mouse button in the input field to place a pointer in a position where the button was clicked. | Search Everywhere context menu command was available, only if there was a selected text block in the current form element. Search was made by the text block so selected. No text block so searched was added to Search Everywhere command presentation in the menu. | Global search usage was improved. |
| Web client. Spreadsheet documents. | The display of a spreadsheet document containing patterns in cells was optimized when using a web client in case of a slow connection. When saving a spreadsheet document containing patterns in cells in HTML format, the size of resulting HTML document was reduced. | Displaying a spreadsheet document containing patterns in cells took longer when using a web client in case of a slow connection. | Eliminated unexpected system behavior. |
| Full-text search. Standard functions. | So far as standard full-text search management function is concerned, you can check the current full-text search index for accuracy. Before you clear the current full-text search index, a warning is displayed notifying that you can abandon this procedure. | So far as standard full-text search management function was concerned, the current full-text search index was unavailable for accuracy verification. The current full-text search index was cleared with a prior warning on an unconditional basis. | Capabilities supported by the standard full-text search management function were expanded. Now, it is more difficult to clear full-text search index. |
| Web client. | The browser extension installation process was simplified (for Google Chrome and Mozilla Firefox browsers). The said extension is required to use file system, cryptography and add-in extensions. As soon as you install an extension for Google Chrome web browser, there is no need to restart your web client any more. | The browser extension installation process was complicated (for Google Chrome and Mozilla Firefox browsers). The said extension was required to use file system, cryptography and add-in extensions. As soon as you installed an extension for Google Chrome web browser, you needed to restart your web client. | Now, the web browser extension installation process is much more easier and user-friendly. |
| Collaboration system. | The collaboration system interface was modified as follows:
| Previously, the collaboration system interface was different. | Now, it is much more easier to use the collaboration system. |
| Standard functions. | The button for accepting changes is always available, and not only after changing the parameters in the dialog box for configuring full-text search parameters of full-text search standard processing management. The button itself is called OK. | The button for accepting the changes was only available after changing any parameter in the dialog box for configuring full-text search parameters of full-text search standard processing management. The button itself was called Set. | The interface of the parameter setting dialog box has been brought to the standard accepted in the platform. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Сlient application form. | Removal of rows from tables displayed in the client application form was optimized. | Previously, removal of rows from tables displayed in the client application form took more time. | Client application operation when rows are removed from the form table was improved. |
| Event log. | You can index event log files. Indexing is performed in the background. Indexes are stored in .lgx files in 1Cv8Log directory. Algorithms for sequential reading of event log files were optimized. No additional settings are required to enable indexing. Due to indexing, filtering of event log entries by indexed fields was significantly accelerated. When another infobase event log file is opened in Designer, indexing of this file is performed in the background and the index file is deleted after the work with the event log being viewed is finished. Separate Log Storage by Periods is set to Week for a new infobase. It is recommended to set separation for existing infobases, so that the size of a single log file is max 100 MB. Event logs created in the 1C:Enterprise of version 8.0 and 8.1 are no longer supported. | This feature was not provided. No event log files indexing was performed. Filtering of entries in event log files took a very long time, so far as large event log files were concerned. | Operations with event logs were accelerated. |
| Access rights. Server clusters. | When using the client/server mode, starting of the first session is accelerated to access the infobase, the configuration of which contains a large number of roles. | When using the client/server mode, starting of the first session to access the infobase, the configuration of which contained a large number of roles, took more time. | The time for server cluster inaccessibility for users during the working processes restart is reduced, and the start time of the first session for each infobase in working process is also decreased. |
| Server clusters. | When using the client/server mode, starting of the first session to access the infobase is accelerated. Acceleration is especially noticeable for configurations containing a large amount of metadata. | When using the client/server mode, starting of the first session to access the infobase took more time. | The time for server cluster inaccessibility for users during the working processes restart is reduced, and the start time of the first session for each infobase in working process is also decreased. |
| Common objects. | Accelerated solution of some systems of linear algebraic equations is enabled. AllowGraphReduction parameter is implemented for SolvingLinearEquationSystems.SolveLinearEquationSystems() method, which allows to control the calculation algorithm. SolvingLinearEquationSystems.GetGraphDepth() method is implemented to allow making the decision on AllowGraphReduction parameter value. | 1C:Enterprise showed insufficient search speed for solutions of some linear algebraic equations systems. | A finer customization of behavior of a tool designed to solve linear algebraic equations systems was implemented. |
| Queries. | Comparison of composite type with non-composite type was improved, provided that the latter can be NULL and a query includes temporary tables. The following operations were optimized:
Optimization is feasible, whenever it has no impact on the query results. Optimization can contribute to query plan improvement and reduction of time required to compile a query. | Comparison of composite type with non-composite type, whenever the latter can be NULL and query had temporary tables, resulted in generation of complex queries which eventually can trigger runtime errors and generate non-optimal query plans. | In some scenarios, query performance was improved. |
| Queries. DBMS operations. Server clusters. | If comparison with an empty link returned as a parameter is made in a query, DBMS receives a query, where a parameter is replaced with a constant. Optimization is feasible, if a server cluster supports such DBMS as IBM DB2, Microsoft SQL Server or Oracle Database. | If comparison with an empty link returned as a parameter was made in a query, no replacement of a parameter with a constant was effected. | DBMS can select a more efficient query execution plan, whenever comparison with empty links returned as parameters is made in a query. |
| DBMS operations. | So far as use of infobase in file mode is concerned, execution of a query with several B conditions which use indexes was largely improved. However, in some scenarios insignificantly decelerated execution of such queries is possible. | So far as use of infobase in file mode is concerned, execution of a query with several B conditions which used indexes was non-optimal. | Execution of some queries in infobase file mode was accelerated. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Data composition system. | When reading report, dynamic lists and conditional appearance settings, missing style elements do not cause an error, but are replaced with default values of the corresponding type. | When reading report, dynamic lists and conditional appearance settings, missing style elements caused an error and no application of such settings was possible. | If a style element is used as the appearance parameter value in any report, dynamic list, form conditional appearance settings, the entire settings object will not be lost and the remaining settings will be applied if this element is unavailable for reading as a result of deleting/renaming or applying settings on the previous platform version. Appearance options containing invalid values will also be applied, but using default values. |
| Web client. | Web client reliability is improved. | Web client operation was characterized by lower reliability. | Web client reliability is improved. |
| Development tools. | If halt on error during debugging is enabled, the error text is displayed both in the dialog box and in the message window. This also allows you to go to exception from the message window. | This feature was not provided. An error message was only displayed in a dialog box with error details. | It is now much more easier to use debugger when halt on error is enabled. |
| Development tools. | The following control features were implemented when a report on the configuration repository versions is generated:
DateBegin, DateEnd, DoNotIncludeVersionsWithLabel, IncludeOnlyVersionsWithLabel, IncludeCommentLineWithDoubleSlash, ConfigurationVersion and ReportFormat parameters were implemented for ConfigurationRepositoryReport Designer batch run command. | These features were not provided. | A list of features designed to manage repository reports in Designer batch run mode was expanded. |
| Collaboration system. Linux. | After installing 1C:Enterprise - Notifications and Startup application (in Linux), a shortcut is created on the desktop to launch this application. The shortcut refers to the Finance subcategory of the Office category. | In Linux, you were able to start 1C:Enterprise - Notifications and Startup application from ~/bin/1cecla directory only. | Now, it became easier for Linux users to find and run 1C:Enterprise - Notifications and Startup application. |
| Web client. File operations. | Whenever you use BeginPutFileToServer() and BeginPutFilesToServer() methods on the web client (without a file system extension), PutFilesDialogParameters is used, and in the file opening dialog box you can now select one of the filters defined when you created PutFilesDialogParameters object. When you create PutFilesDialogParameters object, you can now define filter by default to be used when a file selection dialog box is opened. | Whenever you used BeginPutFileToServer() and BeginPutFilesToServer() methods on the web client (without a file system extension), PutFilesDialogParameters was used, and in the file opening dialog box you were unable to select a filter in the file opening dialog box. | If there is now file system extension on the web client, it's easier to select files for further processing by application. |
| Cryptography support. | Values of properties starting from OID prefix which are based on Subject and Publisher properties of CryptoCertificate have the maximum length of 2,048 bytes. | Values of properties starting from OID prefix which were based on Subject and Publisher properties of CryptoCertificate object had the maximum length of 128 bytes. | Eliminated unexpected system behavior .
|
| Global search. | GlobalSearchResultItem object cannot be created on the basis of the following standard global search kinds: GlobalStandardCommands and FunctionsForTechnicalSpecialist. | You were able to create GlobalSearchResultItem object on the basis of the following standard global search kinds: GlobalStandardCommands and FunctionsforTechnicalSpecialist, so that eventually incorrect data upon global search result processing was returned. | Eliminated unexpected system behavior. |
| Dynamic lists. | If the dynamic list settings form contains changed settings, then when attempting to close this form, the user will be warned about the changed settings and will be prompted to save the changed settings. The UserSettingsModified and SettingsModified properties are implemented to expand the client application form for the settings composer. The standard processing of the settings composer form analyzes the flag of settings modification and prompts to save the settings, if necessary. | If the dynamic list settings form contains changed settings, when attempting to close this form, the form was closed without any warnings. | Likelihood of losing work results by changing dynamic list settings was reduced. |
| XML and XDTO support. | When exporting an XDTO package to an XML schema, the default value (or fixed value) for properties with an "Element" presentation option is exported in the same way as it is for properties with an "Attribute" presentation option. This upgrade is ignored in 8.3.13 version compatibility mode. | When exporting an XDTO package to an XML schema, the default value (or fixed value) for properties with an "Element" presentation option was not exported. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | Whenever you convert a spreadsheet document into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format, cells which contain tab characters or text starting with whitespace can now be created easier. | Whenever you converted a spreadsheet document into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format, cells which contained tab characters or text starting with whitespace were created in a way, when the resulting document was visually different from the original one. | Now you have less visual differences between the original spreadsheet document displayed in 1C:Enterprise and that created by way of conversion thereof into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format. |
| Queries. | If the temporary table is generated based on the table of values, a runtime error will be generated if a column with an unspecified type is present in the table of values and this column is included in the temporary table. An error will also occur if a non-typed column is involved in any expression (for example, SELECT or ISNULL). This upgrade is ignored in 8.3.13 version compatibility mode. | If a temporary table is formed based on a table of values where a column with an unspecified type is present and this column is included in a temporary table, no runtime errors were generated, but the query result could be incorrect. | Eliminated unexpected system behavior. |
| Collaboration system. Web client. | Screen translation in the collaboration system running on a web client:
| Screen translation in the collaboration system running on a web client:
| The screen translation tool is improved, so far as the collaboration system runs on the web client. |
| Administration tools. | In Version 8.3.10 and later compatibility mode, GetDataBaseStorageStructure() function returns a table of values where the Indexes column contains short index names. At the same time, the names of indexes are displayed identically for any DBMS. | In the Indexes column of the table of values returned by the GetDataBaseStorageStructure() method, long index names were indicated and the index names differed in different DBMSs. | The names of indexes in the database schema are refined. |
| Configuration extensions. | Tooltips for the check box, which controls the behavior of the object property in the extension, have become more clear and better describing the essence of the check box status. | Tooltips for the check box, which controls the behavior of the object property in the extension were poorly describing the check box status. | Improved tooltips for the check box describing the behavior of an object property in the extension. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Сlient application form. | If no table is displayed in the form or there are no rows in the table or a row which is unavailable in the table is transferred to FormTable object method:
If no table is displayed in the form or no rows are available in the table, as soon as you call FormTable.ChangeRow() and FormTable.CopyRow() methods an exception is generated. If no table is displayed in the form, whenever you call FormTable.AddRow(), FormTable.FinishRowEditing() and FormTable.Update() methods an exception is generated. In 8.3.13 version compatibility mode behavior remained unchanged. | So far as thin and thick client applications are concerned:
Web client:
| Now, the system operates in a similar way both on the thin and thick client. Unexpected system behavior was eliminated. |
| Client application. | To describe OpenID Connect provider in default.vrd file, you can specify the fields to compare users of 1C:Enterprise and OpenID Connect provider infobases. | This feature was not provided. Users were always compared by e-mail and infobase user name. | Now, you can use OpenID Connect with a great number of providers, for instance, Microsoft Azure. |
| Data composition system. | If a data composition system expression in query language contains curly brackets, whenever this query is processed, the said characters cannot be deleted. If there is no "}" character at the end of a data composition system expression in query language before that query is transmitted, an error is displayed. In 8.3.16 version compatibility mode behavior remained unchanged. | If a data composition system expression in query language contained curly brackets, whenever this query was processed, the said characters were deleted from the query. If there was no "}" character at the end of a data composition system expression in query language before that query was transmitted, no error was displayed. | Eliminated unexpected system behavior. |
| DBMS operations. Queries. | When using the file or client-server version (when using the Microsoft SQL Server DBMS), the query language operator IN, which meets all of the following criteria, always returns a Boolean value:
It is recommended to analyze these queries and refactor them, if necessary. This upgrade is ignored in 8.3.13 version compatibility mode. | When using the file or client-server version (when using the Microsoft SQL Server DBMS), the query language operator IN, which meets all of the following criteria, returned a Boolean or NULL value:
| Eliminated unexpected system behavior. |
| Data composition system. | If a query with merges is available in the data composition system query, whenever you use DataCompositionProcessor.Initialize() method with RestrictGettingFieldsByRefByViewRight set to True, View rights are applicable to all merging parts. In 8.3.16 version compatibility mode behavior remained unchanged. | If a query with merges was available in the data composition system query, whenever you used DataCompositionProcessor.Initialize() method with RestrictGettingFieldsByRefByViewRight set to True, View rights were applicable to the initial merging part only. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile client. | Images in SVG format can be displayed in the mobile client. No filters and effects are supported when you use images of this format. ImageFormat.SVG system enumeration property was implemented. | This feature was not provided. | 1C:Enterprise mobile client now supports display of images in SVG format. |
| Add-ins. Mobile platform. Mobile client. | So far as add-ins are concerned which are supported by mobile devices running iOS, you can connect dynamic system libraries to add-ins. The add-in technology documentation is updated. (read more) | This feature was not provided. So far as add-ins running iOS were concerned, you were able to specify required subsystem components only. | Functionality to develop add-ins running iOS was added. |
| Mobile client. | Dynamic add-in setting is no longer supported by mobile client application build (including mobile clients which can run in a standalone mode) running Android. DynamicAddInInstallationSupported() method always returns False value on a mobile device (except mobile versions for developers) | Whenever you were running Android, you were able to use dynamic add-in setting for mobile application application build (including mobile clients capable of running in a standalone mode). | Due to update of security policy by Google, always make sure that add-ins available on a mobile client are included in a mobile application build. |
| Formatted documents. | External appearance of a tool bar for formatted and HTML-documents in a mobile version of 1C:Enterprise was changed. Functionality offered by a tool bar remained unchanged. The formatting tool bar was made similar for mobile phones and tablets. | Previously, external appearance of a tool bar for formatted and HTML-documents in a mobile version of 1C:Enterprise was different. The formatting tool bar was dissimilar for mobile phones and tablets. | The formatting tool bar for formatted and HTML-documents became easier and more user-friendly. |
| Mobile platform. Mobile client. | Application usage statistics services can now be connected to the mobile application being built. The following statistics services are supported:
ApplicationUsageStatistics global context property was implemented. | This feature was not provided. | Now, you can integrate mobile applications for a mobile version of 1C:Enterprise with various mobile application statistics services. |
| Mobile platform. Mobile client. | User interface was enhanced (photos, audio and video recording). Now, you can review the result of action you performed and (if deemed necessary) repeat it. | User interface was different (photos, audio and video recording). You were unable to preview and hear the results of your actions. Moreover, you were unable to repeat any of the actions. | Now, it is much more easier to use tools supported by a mobile version to record audios and videos and make photos in a convenient way. |
| Mobile platform. Development tools. | It has become possible to connect to the web server where the configuration of the mobile application is published using the HTTPS protocol in the developer's mobile platform. Opening the dialog box for configuring an HTTPS connection has been implemented in the infobase adding dialog box. | This feature was not provided. | Connecting a developer's mobile platform to a web server can be more secure (using the HTTPS protocol). |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Error handling. | The HTTP error registration service https://pult.1c.com/pult/platform/errors can be called when the application abnormally terminates. To stop reports sending, disable abnormal terminations report sending in the ErrorProcessing object. | No services were used when the application terminated abnormally. | When the application terminates abnormally, the information about the error is sent to 1C Company automatically. |
| Error handling. | The standard texts of error messages are changed. The standard dialog box for sending an error report is changed. To motivate the user to send a report on a specific error to the error registration service, it is recommended to return an appropriate message from the error registration service. This message will be displayed on the error form. | The standard texts of the error messages were different. The dialog box of sending the error report was different. | Error representation has been improved. |
| Information registers. | When recording an information register record set, the insignificant chars to the right of the last significant chart are deleted in string type dimensions. | When recording an information register record set, the insignificant chars to the right of the last significant chart were not deleted in string type dimensions. | Eliminated unexpected system behavior. |
| A client application form. | If after the form table display update all displayed rows have become invisible, then the InitialListView form table property is used to define the first displayed row. If the current table row have become invisible, the nearest (by key) row of the list becomes the current one. A new display list is formed based on the new current row. It is recommended to review the previous list behavior in the application. This change is not implemented in version 8.3.16 compatibility mode. | If after the form table display update all displayed rows had become invisible, the list display always started from the beginning. | Eliminated unexpected system behavior. |
| Data composition system. | If the filter with the Filled or Is not filled comparison type for the filed which is set as the aggregate function in the query is specified in the settings of the data composition system, then such condition in the resulting query is placed to the HAVING query section. This change is not implemented in version 8.3.16 compatibility mode. | If the filter with the Filled or Is not filled comparison type for the filed which was set as the aggregate function in the query was specified in the settings of the data composition system, then such condition in the resulting query was placed to the WHERE query section. | Eliminated unexpected system behavior. |
| Administration tools. | InfobaseSession.ClientIPAddress property contains IP-address for another sessions only if the user has the Administration right. Otherwise, this property contains an empty string. | InfobaseSession.ClientIPAddress property always contained IP-address for another sessions. | Increased security of the infobase sessions list. |
| Error handling. | For the ErrorCategory system enumeration, the FullTextSearchError, ExternalDataSourceError, and NavigationLinkError values are implemented. Help is disabled in the error form and error report form, because there may be no connection with the server when these forms are displayed. Changed the format of the report.json file, which contains automatically collected error information. Changes are stated in the documentation as well. When adding screenshots in the error report, screenshots of all application windows will be added (even if the application is not active). For the ErrorProcessingSettings object, the IncludeScreenshotsInReport, IncludeDetailedErrorTextInReport, IncludeInfobaseInformationInReport, and AdditionalReportInfo properties are implemented. The appearance of the error report form has been improved. The request file format has been modified for the getInfo method of the error registration web service. It will allow to return localized message texts to the user and specify the dump format for transferring in service (available only when running Windows). | These features were not provided. | The mechanism of runtime errors processing has been improved. |
| Localization. Web client. | Localized web client application interface for Arabic (ar). | This feature was not provided. | 1C:Enterprise web client is now available for Arabic-speaking users. |
| Queries. | Optimized execution of queries using the IN operator with a list of values containing the UNDEFINED value. | Executing queries using the IN operator with a list of values containing the UNDEFINED value was not optimal. | Optimization results in faster query execution, if after the field used in the expression Field IN (Undefined) there are still fields in the index that are used in the filter. |
| DBMS operations. System requirements. | Microsoft SQL Server 2019 DBMS is now supported. | Microsoft SQL Server 2019 DBMS was not supported. | New Microsoft SQL Server version is now supported. |
| Client application. Web client. Error handling. | If an unrecoverable error occurs, the option to automatically terminate the client application without displaying a dialog that requires a user reaction is implemented. The /DisableUnrecoverableErrorMessage client application start line command has been implemented. | This feature was not provided. When an unrecoverable error occurred, a dialog was generated that required a mandatory user reaction. | Simplified the system use in modes when the client application does not require a presence of user (for example, in automatic testing mode). |
| Spreadsheet documents. Data display. | Implemented the feature to save the text writing direction in a spreadsheet document for exporting and printing. This feature is available for thin client, thick client, and web client. The text direction is saved when exporting to all appropriate formats. Text direction is supported for the 1C:Enterprise spreadsheet document and for imported spreadsheet documents of XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) formats. Added the TextDirection spreadsheet document property. This property allows to specify the text direction in a spreadsheet document explicitly: left-to-right or right-to-left. If a cell has automatic horizontal alignment, the numbers are always right-aligned, and other values are aligned according to the interface text direction. | A spreadsheet document was exported and printed with left-to-right text direction. The export and print mode did not depend on the operating system used. | Eliminated unexpected system behavior. |
| Collaboration system. | You can now perform a video call in thick or thin client in remote desktop window. | There was no option to perform a video call in thick or thin client remote desktop window. | Video calls in thin and thick client are more accessible now. |
| Mobile platform. Mobile client. | 1C:Enterprise mobile version now supports the hardware or external keyboard in the client application form fields that display values of Number and Date types. Tab and Shift+Tab shortcuts can now be used to navigate through the form fields. The arrow keys of hardware or external keyboard, joystick, or other cursor control mechanism can now be used to navigate through the form fields. The keyboard shortcuts configured by the developer are now supported for the form items. The standard keyboard shortcuts used in the PC version are not supported. Implemented the Esc and Enter keys support on a hardware or external keyboard. | This feature was not provided. | Improved data input on mobile devices through a hardware or external keyboard. |
| Accumulation registers. | When the maximum period of calculated totals of the accumulation register is set, it is not possible to add register records of this register. | When the maximum period of calculated totals of the accumulation register was set, it was possible to add register records of this register. When the maximum period of calculated totals was changed and register records were added at the same time, register totals could be incorrect. | Eliminated unexpected system behavior. |
| Analytics system. | For the analytics system manager, implemented the GetConnections() method that returns the AnalyticsSystemServerConnection object. Implemented the AnalyticsSystemSchema object. Implemented the options to manage additional sources for the standard data processor of analytics management. The RefreshInterface() global context method changes visibility of the Analytics item in the Service and settings menu (depending on the current analytics system settings). | These features were not provided. | Extended API of interaction with the analytics system. |
| Analytics system. Collaboration system. | If an infobase supports the collaboration system, the analytics system provides the ability to open information on a reference type object in all client applications of this user at once. | This feature was not provided. | Improved the analytics system interface. |
| Full-text search. Common attributes / Data separation. | Reduced use of RAM upon indexing information register records. Faster indexing for separated infobases. Changed the format of temporary full-text search files. Now the format changes automatically upon index update. Upon migration to the previous platform version, the index will be cleared. | Indexing information register records required more RAM. Building a full-text search index for a separated infobase took more time. | Improved building of a full-text search index. |
| Client application form. Mobile platform. Mobile client. | If an input field is used to enter a value of the Number type and the SpecialTextInputMode property is set to Digits, a calculator that contains only digits, a comma, the last character delete button, OK, and Cancel is used for input. | If an input field was used to enter a value of the Number type and the SpecialTextInputMode property was set to Digits, a standard calculator with excessive features was used for input. | Simplified number input in mobile applications. |
| Automated testing. | Improved performance of the following methods of the TestedApplication object and objects of client application windows: FindObject(), FindObjects(), and GetObject(). | Execution of the following methods of the TestedApplication object and objects of client application windows took more time: FindObject(), FindObjects(), and GetObject(). | Improved performance of the automated testing feature for the client application. |
| Mobile application builder. | The mobile application builder can now upload new 1C:Enterprise mobile versions automatically. This feature is supported by the client/server mode of the mobile application builder only. The mobile application builder in the file mode has the following options (and settings) disabled:
| The mobile application builder could upload the new 1C:Enterprise mobile version interactively only. Clearing the obsolete data from the infobase and from the builder cache were available in the file infobase mode. This could potentially cause unexpected system behavior due to the scheduled job feature specifics in the file infobase mode. | Uploading new 1C:Enterprise mobile versions in the mobile application builder is now faster and more convenient. |
| Infobase verification and repair. | Infobase verification and repair feature now includes an option to check the logical integrity of the configuration extension. Some repair options are also available for the extensions. Added the new parameter for the /IBCheckAndRepair command of the Designer batch mode - ConfigurationExtensionsLogIntegrity. This parameter launches the logical integrity check of the configuration extension. | Infobase verification and repair feature had no option to check and repair configuration extensions errors. Some errors might cause the entire infobase to be unavailable. | Improved the reliability of infobases containing extensions. |
| Dumping configurations to files/Restoring configurations from files. | The format version of the configuration export to XML is now 2.11. | The format version of the configuration export to XML was 2.10. | The configuration export to XML now supports new platform features. |
| Error handling. | The network errors info feature was completely reviewed. Improved the error messages text, that now contain information about the error and its possible causes. If there was a network connection error while requesting the 1C:Enterprise server cluster and there is an option to retry the request after the connection was restored, the prompt to retry the request will be replaced by the message that the network connection was restored. The error dialog box does not provide the option to send an error report, if there is no network connection. Application developers should rework the application code using the following recommendations:
| The error messages were harder to understand and more annoying. An option to send the error report was available even if there was no network connection (thus the report could not be sent). | The network errors dialog boxes are now less annoying. |
| Client application. | For all client applications the login button in the authentication dialog box is now called Log in. There is now an option to show the password. Implemented the button to show/hide the password. Improved the authentication form display of OpenID Connect on mobile devices. | For all client applications the login button in the authentication dialog box was called Ok. There was no option to show the password. | The authentication dialog box is now more convenient. |
| Improved performance of initial population of database copy table if this table is included in multiple transactions. | The performance of initial population of database copy table if this table was included in multiple transactions was not optimal. | Improved performance of initial population of database copy table if this table is included in multiple transactions. | |
| System requirements. Mobile platform. Mobile client. | Mobile applications built using mobile version 8.3.17.67 will meet the requirements of Google Play for new applications. The target SDK version is 29. To upload a mobile application to Google Play, build a mobile application using mobile version 8.3.17.67 or later. | Mobile applications built using mobile versions that are older than 8.3.17.67 could not be uploaded to Google Play after August 3, 2020. | 1C:Enterprise mobile version meets the requirements of Google Play. |
| Mobile device-specific features. Mobile platform. Mobile client. | For mobile version tools responsible for audio recording on a mobile device, the following features are now available:
| Audio recording parameters could not be configured on a mobile device. Background audio recording was not supported on a mobile device. | New features for audio recording on a mobile device. |
| Integration service. | Improved sending and receiving of integration service messages. | When using integration services, sending and receiving of messages were not sufficient enough. | Improved sending and receiving of integration service messages. |
| Mobile device-specific features. Mobile platform. Mobile client. Mobile application builder. | AppSee is removed from the list of supported statistics services. | 1C:Enterprise mobile version supported AppSee. | 1C:Enterprise mobile version does not support AppSee. |
| Mobile device-specific features. | The EnableAudioRecording() and MakeAudioRecording() methods prevent the mobile device from idling to sleep to prevent audio recording from stopping. The audio recording stop handler passed to the EnableAudioRecording() method is called to not lock the user interface. The default value for the ButtonLocation parameter of the EnableAudioRecording() method is Undefined. Improved the audio recording interface. | The EnableAudioRecording() and MakeAudioRecording() methods did not prevent the mobile device from idling to sleep. As a result, audio recording could stop. The audio recording stop handler passed to the EnableAudioRecording() method was called in such a way that a long server call from this handler could lock the user interface. The default value for the ButtonLocation parameter of the EnableAudioRecording() method was the value where the platform automatically selected the location of the button to stop recording. | Improved the audio recording interface (both user interface and API) in the mobile application. |
| Mobile client. | The mobile client tries to close the session in the server cluster correctly in case of unexpected shutdown. Abnormal termination can occur, in particular, when the mobile operating system removes the mobile client application from RAM when the device enters sleep. | The mobile client did not try to close the session in the server cluster correctly in case of unexpected shutdown. | Reduced the number of hung mobile client sessions. This reduces the amount of occupied licenses and locks from inactive devices. |
| System requirements. | Updated system requirements for the client application:
| The system requirements for the client application were as follows:
| Updated system requirements for client applications (including Designer). |
| Mobile device-specific features. Mobile platform. Mobile client. | For a mobile application running Android 10 or later to use geolocation in the background, set the Background location permission in Designer, export the configuration, and rebuild the mobile application using Mobile Application Builder. | A mobile application running Android version 10 or later was unable to use geolocation in the background. | The limitations of Android 10 and later are taken into account. |
| Mobile client. | Upgrade: checking the connectivity to the selected infobase in the mobile client is revised. A mobile client signature is verified not only on the mobile client but also on the server. The mobile client can connect to the infobase if the mobile client configuration and the server configuration match at least 80%. Changed setup for generating an infobase configuration signature. Errors that occur while checking the mobile client connectivity to the selected infobase are now more user-understandable. | Mobile client connectivity to the infobase was tested only on the mobile client. The requirement to match mobile client configurations and main infobase configurations was more stringent. | The mobile client can connect to the infobase in more cases. The need to update the mobile client is now less acute. The previously published mobile client can work with the infobase in case of minor modifications to the infobase configuration. |
| Mobile platform. Mobile client. | To restore the ability of the mobile application to access files on a mobile device, do the following:
The target Android version is set back to 10.0 (API 29). | The target Android version was 11 (API 30). As a result of changing the target Android version, the mobile application lost access to files on the mobile device. | Restored access to files on a mobile device. |
| Mobile application builder. | Mobile Application Builder now supports Xcode 12. | Mobile Application Builder did not support building using Xcode 12. | Mobile Application Builder now supports the latest Xcode version. |
| System requirements. Mobile platform. Mobile client. | The mobile version now supports Android 11 and iOS 14. | The mobile version did not support Android 11 and iOS 14. | The mobile version of 1C:Enterprise now supports the latest mobile operating systems. |
| Licensing system. | In file mode, it is checked whether there is a feature testing license. In partictular, using integration services in a file infobase requires a feature testing license. In client/server mode, the upgrade is ignored. | The feature testing license check depended on the infobase mode:
| Eliminated unexpected system behavior. |
| Pictures. | When receiving an SVG image from a temporary storage, an infobase or via a direct link, sections with JavaScript are removed from the image. | When receiving an SVG image from a temporary storage, an infobase or via a direct link, sections with JavaScript were not removed from the image. | Reduced the possibility of destructive actions using JavaScript embedded in an SVG image. |
| Development tools. Mobile client. | The mobile client configuration that was signed in version 8.3.16 (and the signature was not changed in version 8.3.17 and later) is accepted by the mobile client in version 8.3.17 and later. We do not recommend that you change the configuration signature in version 8.3.16 if the configuration is executed on version 8.3.17. | The mobile client configuration that was signed in version 8.3.16 (and the signature was not changed in version 8.3.17 and later) was not accepted by the mobile client in version 8.3.17 and later. Platform version 8.3.17 and later considered such a configuration to be unsigned. | As a result, after updating the platform on the server cluster computer up to version 8.3.17, mobile clients running iOS will remain in operation. |
| Client application. | When using 1C:Enterprise authentication or accessing infobase with thin or web client using HTTP protocol, user password is passed using SHA-256 hash algorythm and AES-256 CBC encoding algorythm.. | Thin and web clients passed the user password not encrypted when using 1C:Enterprise authentication or accessing infobase with thin or web client using HTTP protocol. | Thin and web cliients now use safer authentication when accessing infobase using HTTP protocol. |
| Mobile device-specific features. | PUSH notifications that are sent from the mobile platform for PC through APNS service now use HTTP/2 protocol, port 443. | PUSH notifications that were sent from the mobile platform for PC through APNS service used obsolete binary protocol. | PUSH notifications can now be sent through APNS.service again. |
| Event log. Server clusters. | Limited the number of event log indexing streams. New technological log event: <EVENTLOG>. | Event log indexing could produce heavy system load, especially with a large number of infobases. | Reduced the system load caused by event log indexing when the server cluster hosts a large number of infobases. |
| Web client. System requirements. | The web client is now supported in the following web browsers:
| The web client was not supported in the following web browsers:
| Extended the list of web browsers to run the web client. |
| Event log. | In a file infobase, the event log indexing and the use of an already built index are disabled. | In a file infobase, the event log was indexed and an already built index was used in the event log. | Decreased infrastructure load, especially for a shared file infobase. Improved client application stability. |
| Server clusters. | Eliminated the slowdown in user operations when there is insufficient RAM on computers running cluster working processes. The RAM consumption by cluster working processes might increase. | When there is insufficient RAM on computers running cluster working processes, there was a significant performance decrease. | Eliminated the slowdown in user operations when there is insufficient RAM on computers running cluster working processes. |
| XML and XDTO support. | Reading a large CDATA section for an XML document with UTF-8 encoding is now faster. | Reading a large CDATA section for an XML document with UTF-8 encoding was slow. | Improved XML document performance in some cases. |
| Linux. Server clusters. Administration tools. | Implemented operating system authentication via Kerberos protocol for 1C:Enterprise client applications managed by Linux. | This feature was not provided. | Linux users in a Windows domain network can now use operating system authentication to access infobases that are managed by a Windows server cluster. |
| Standalone server. | New feature: authentication in the infobase is required to perform operations with it via the standalone server administration utility (ibcmd). It is required for the following commands:
| Authentication was not required to perform operations with an infobase via the standalone server administration utility (ibcmd). If connection to DBMS administration utility required a password and it was not specified, the administration utility did not prompt you to enter it. | Operations with the infobase via the standalone server administration utility (ibcmd) are more secure. |
| Web client. System requirements. | Yandex Browser version 22 or later is now supported on Linux, macOS, and Windows. | This feature was not provided. | Extended list of supported web browsers. |
| Client application form. | If visibility is disabled for a form table in the client application, calls of the following methods of this table are ignored: Expand(), Collapse(), AddRow(), ChangeRow(), CopyRow(), EndEditRow(), and Refresh(). This update is applied to tables whose visibility was disabled by the user, tables in a collapsed group, and so on.
<<<<<<< .mine | If visibility was disabled for a form table in the client application, calls of the following methods of this table raised an exception: Expand(), Collapse(), AddRow(), ChangeRow(), CopyRow(), EndEditRow(), and Refresh(). This behavior was relevant for tables whose visibility was disabled by the user, tables in a collapsed group, and so on. | Eliminated unexpected system behavior. |
| Development tools. | You can control remote debugging and debugging features for separated infobases. To do it, you can specify users who can debug the configuration (broken down by infobases). To connect to the debugger, specify username and password. New command for the command line of ragent and dbgs utilities: debugServerUsers. For more information about the user description file format, see the documentation. In the dialog box of Designer parameters, on the Debug tab, the Password input field is removed. New event log events: Debugging. Debug item attachment, Debugging. Debug item detachment, and Debugging. Expression calculation. | This feature was not provided. You could specify one password to debug any database served by a cluster. | Advanced development features for applications running in separated infobases.
|
| Web client. System requirements. | In web client, the minimum supported Google Chrome version is 88. Clipboard operations can be performed in web client without the file system extension in Google Chrome. However, web client must be available over HTTPS or published on a local computer. If these conditions are not met, clipboard operations are unavailable. | In web client, the minimum supported Google Chrome version was 49. The file system extension had to be installed in Google Chrome to perform clipboard operations in web client. | Ended support for legacy Google Chrome versions. |
| Administration tools. | New user password features:
New global-context methods: SetUsersPasswordsMinValidityPeriod(), GetUsersPasswordsMinValidityPeriod(), SetUsersPasswordsMaxValidityPeriod(), GetUsersPasswordsMaxValidityPeriod(), SetUsersPasswordsRepetitionRestrictionAmongRecent(), GetUsersPasswordsRepetitionRestrictionAmongRecent(), SetPeriodOfWarningAboutUsersPasswordsExpiration(), and GetPeriodOfWarningAboutUsersPasswordsExpiration(). New global-context property: UsersPasswordsPolicies. New property: AuthenticationSecondFactorSettingsTemplates.UsersPasswordsPolicies. New properties for the InfobaseUser object: PasswordsPolicyName, PasswordSettingDate, and WrittenPasswordSettingDate. | These features were not provided. Some of the features could be implemented in 1C:Enterprise language, which allowed bypassing of requirements. | Improved user password features, which resulted in overall better system security. |
| Licensing system. | The license owner address is hidden from the About... dialog box when the list of active (or activated) licenses is displayed. For licenses displayed in the Infobase and Configuration sections, addresses are not hidden for the rows obtained by previous 1C:Enterprise versions. | The license owner address was displayed in license information in the About... dialog box. | The license owner address is no longer displayed in license information in the About... dialog box.
|
New parameter values for the -LogIntegrity and -LogAndRefsIntegrity parameters of the /IBCheckAndRepair command:
New command for the command line of ragent and dbgs utilities: debugServerUsers. For more information about the user description file format, see the documentation.
In the dialog box of Designer parameters, on the Debug tab, the Password input field is removed.
New event log events: Debugging. Debug item attachment, Debugging. Debug item detachment, and Debugging. Expression calculation.
You could specify one password to debug any database served by a cluster.
Clipboard operations can be performed in web client without the file system extension in Google Chrome. However, web client must be available over HTTPS or published on a local computer. If these conditions are not met, clipboard operations are unavailable.
The file system extension had to be installed in Google Chrome to perform clipboard operations in web client.
New global-context methods: SetUsersPasswordsMinValidityPeriod(), GetUsersPasswordsMinValidityPeriod(), SetUsersPasswordsMaxValidityPeriod(), GetUsersPasswordsMaxValidityPeriod(), SetUsersPasswordsRepetitionRestrictionAmongRecent(), GetUsersPasswordsRepetitionRestrictionAmongRecent(), SetPeriodOfWarningAboutUsersPasswordsExpiration(), and GetPeriodOfWarningAboutUsersPasswordsExpiration().
New global-context property: UsersPasswordsPolicies.
New property: AuthenticationSecondFactorSettingsTemplates.UsersPasswordsPolicies.
New properties for the InfobaseUser object: PasswordsPolicyName, PasswordSettingDate, and WrittenPasswordSettingDate.
Some of the features could be implemented in 1C:Enterprise language, which allowed bypassing of requirements.
New command for the command line of ragent and dbgs utilities: debugServerUsers. For more information about the user description file format, see the documentation.
In the dialog box of Designer parameters, on the Debug tab, the Password input field is removed.
New event log events: Debugging. Debug item attachment, Debugging. Debug item detachment, and Debugging. Expression calculation.
You could specify one password to debug any database served by a cluster.
Clipboard operations can be performed in web client without the file system extension in Google Chrome. However, web client must be available over HTTPS or published on a local computer. If these conditions are not met, clipboard operations are unavailable.
The file system extension had to be installed in Google Chrome to perform clipboard operations in web client.
New global-context methods: SetUsersPasswordsMinValidityPeriod(), GetUsersPasswordsMinValidityPeriod(), SetUsersPasswordsMaxValidityPeriod(), GetUsersPasswordsMaxValidityPeriod(), SetUsersPasswordsRepetitionRestrictionAmongRecent(), GetUsersPasswordsRepetitionRestrictionAmongRecent(), SetPeriodOfWarningAboutUsersPasswordsExpiration(), and GetPeriodOfWarningAboutUsersPasswordsExpiration().
New global-context property: UsersPasswordsPolicies.
New property: AuthenticationSecondFactorSettingsTemplates.UsersPasswordsPolicies.
New properties for the InfobaseUser object: PasswordsPolicyName, PasswordSettingDate, and WrittenPasswordSettingDate.
Some of the features could be implemented in 1C:Enterprise language, which allowed bypassing of requirements.
Version 8.3.16 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.15 is now implemented. | Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.14 was available. | Configurations developed using 1C:Enterprise platform version 8.3.15 or earlier can now run on version 8.3.16 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.16 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.15 after the migration to version 8.3.16, even if you disable the compatibility mode (simply enable it again). |
| System requirements. | Implemented Programming Training Version running on Linux and macOS. | Programming Training Version ran on Windows only. | Programming Training Version runs on all supported operating systems. |
| System requirements. macOS. | OS X family (version 10.11 or under) is no longer supported. Client application runs on macOS only (version 10.12 or above). | Client application could run on OS X (version 10.8 or above). | Outdated operating systems are no longer supported. |
| Server clusters. Administration tools. | In client/server mode, you can now limit the number of logon attempts with an incorrect password. The following parameters are implemented for the infobase: maximum number of failed authentication attempts before a user is blocked; a time interval during which a user who made a threshold number of authentication attempts cannot attempt authentication again; username suffixes that should be used if it is necessary to authenticate as a blocked user. New global context property: AuthenticationLock. New form to view authentication locks in Designer (Administration – Authentication locks). This command is available only to a user with administrative rights. Implemented the following event log events:
New data of event log events:
In the display form of the list of active users of Designer, you can now view a column with characteristics of user data separation. | This feature was not provided. The platform did not prevent someone from guessing the password by going through the options. | Reduced the likelihood of guessing the infobase user password by going through the options. |
| Queries. | New feature: the query language now supports grouping sets. Upgrade: the query language now supports keywords GROUPING SETS for sentence GROUP BY. New query language function that allows you to determine whether a function parameter can be grouped: GroupedBy(). | This feature was not provided. | Upgrade: grouping by several field sets is faster because grouping is performed per table scan. |
| Charts. Data composition system. | When using charts, you can now save a map between an object (displayed by different charts) and its color. For charts displayed on the form, 1C:Enterprise code is required for this. For the data composition system, this feature is available using settings. A map between an object and its color is saved to the settings system storage. Implemented the Chart.FillSeriesColors() method. For objects DataCompositionOutputParametersValues, DataCompositionGroupOutputParametersValues, DataCompositionChartOutputParametersValues, and DataCompositionAreaChartAppearance, implemented properties ChartType.ColorsSaving and ChartType.ColorsSavingKey. New property: ProcessorOfDataCompositionResultOutputToSpreadsheetDocument.AppearanceForValues. New property: DataCompositionAreaChartGroupTemplate.Presentation. | This feature was not provided. The same object could be displayed by charts with a different color, resulting in bad report readability. | The same object can be displayed by charts with the same color that helps make charts look better and more informative.
|
| Collaboration system. | When using the collaboration system, you can now share your PC screen on a video call. In the web client, screen sharing is available only in Google Chrome and Mozilla Firefox. In the web client, Google Chrome supports sharing of the current web browser tab. | This feature was not provided. | Expanded the collaboration system capabilities. |
| Collaboration system. | On setting the CollaborationSystemMessage.Text property of the FormattedString type from 1C:Enterprise code, appearance is saved (except pictures to be deleted). This message is displayed by the system considering its formatting. A message with appearance cannot be created interactively. Smileys set by emoticons (Unicode characters) are now supported. | This feature was not provided. | New operations with collaboration system messages. |
| Administration tools. Server clusters. | You can now get a server cluster version using program administration interfaces. Getting a server cluster version is only available if a server cluster is running 1C:Enterprise version 8.3.11 or above. Implemented ServerAdministration.GetVersion() method. Implemented the agent version command of the rac utility. | This feature was not provided. | On program administration of the server cluster, you can now determine which features can or cannot be used depending on 1C:Enterprise version the server cluster is running on. |
| Spreadsheet document. Formatted document. Processing PDF documents. | On saving a PDF document, the OpenType font is now available if it is used in appearance of the document to be saved. | This feature was not provided. On saving to the PDF format, only TrueType fonts were embedded. | Improved compatibility of PDF documents generated by 1C:Enterprise with different PDF document display devices. |
| Charts. | You can now interactively change values displayed by charts of the following kinds: a line, a step, and an area (including summarized and normalized series). This feature is not provided in 8.3.15 compatibility mode. Implemented the ValuesEditMode property for Chart and ChartSeries objects. New property: ChartValue.EditMode. New event for the chart form field extension: OnEditValue. The form field extension event for the OnChangeAreaContent spreadsheet document will be called upon interactive editing of a chart and a Gantt chart inserted into the spreadsheet document. The AdditionalParameters parameter is implemented in the handler. This change is not implemented in 8.3.15 compatibility mode. | This feature was not provided. The form field extension event for the OnChangeAreaContent spreadsheet document was not called upon interactive editing of a Gantt chart inserted into the spreadsheet document. | Improved chart interactivity. |
| Web client. | You can now embed the web client in third-party sites and ensure the web client interacts with these sites. New global context property: ExternalSiteWindow. Implemented the ClientApplicationMainWindowMode.EmbeddedWorkplace system enumeration value. Implemented the MainWindowMode command-line command for the client application and web client. Implemented the following access rights, which allow you to start the client application in a main window mode: StandardMainWindowMode, MainWindowModeWorkplace, MainWindowModeEmbeddedWorkplace, MainWindowModeFullScreenWorkplace, and MainWindowModeKiosk. Implemented Embedded WebClient API, which allows a site to interact with the web client. | This feature was not provided. It was impossible to embed the web client in a third-party site. | Advanced web client features. |
| Spreadsheet document. Processing PDF documents. | New feature: you can save a spreadsheet document to PDF/A-2 and PDF/A-3 (versions of the PDF/A format used for long-term storage). New values for the SpreadsheetDocumentFileType system enumeration: PDF_A_2 and PDF_A_3. Implemented two syntax options for the SpreadsheetDocument.Write() method. Implemented the Attachments parameter for the SpreadsheetDocument.BeginWriting() method. New objects: ReadPDF and WritePDF. | It was possible to save a spreadsheet document to PDF/A-1 only. | Expanded spreadsheet document export features. |
| Charts of characteristic types. | Implemented the FullDescription() method for ChartOfCharacteristicTypesRef and ChartOfCharacteristicTypesObject objects. | This feature was not provided. | Unified behavior of the chart of characteristic types and the catalog for getting an item presentation based on hierarchy. |
| Spreadsheet documents. | New feature: you can write a spreadsheet document (using the SpreadsheetDocument.Write() method in an option for writing to a stream) to a stream as XLSX. | It was not possible to write a spreadsheet document (using the SpreadsheetDocument.Write() method in an option for writing to a stream) to a stream as XLSX. | Expanded features of spreadsheet document export to streams. |
| Configuration extensions. | You can now create the following objects in a сonfiguration extension:
You can now extend the following:
| These features were not provided. | Extended configuration extension options. |
| Managed forms. | New feature: you can generate a planner context menu from 1C:Enterprise code and specify an action called upon clicking (depending on the click area). New events for the form field extension for the planner field: GenerateCommandsProcessing, DimensionItemClick, TimeScaleItemClick, and WrappedTimeScaleHeaderClick. New properties for the form field extension for the planner field: TimeScaleItemHyperlink, DimensionItemHyperlink, and WrappedTimeScaleHeaderHyperlink. | These features were not provided. | New planner features. |
| Managed forms. | New feature: you can use a search string for a form table that displays a value table, a value tree, or a value list. Search history is stored in the system settings storage with the following key: Common/TableSearchHistory/<Form name>.<Table name>. This change is not implemented in 8.3.15 compatibility mode. New feature: you can use the Find by current value command in all form tables ignoring сonfiguration compatibility mode. | The search string was available only for form tables that displayed a dynamic list. In other tables, search was done using the standard dialog box, which performed positioning. Search by current value was not available. | Improved search in tables of managed forms, including a pictorial view of searching in the table. |
| Data composition system. Pictures. | New feature: you can use pictures for conditional appearance of reports in the data composition system. New property: DataCompositionAppearance.Picture. New pictures in the picture library: AppearanceGreenUpTriangle, AppearanceYellowHyphen, AppearanceRedDownTriangle, AppearanceGreenUpArrow, AppearanceGreenUpInclineArrow, AppearanceYellowUpInclineArrow, AppearanceYellowRightArrow, AppearanceYellowDownInclineArrow, AppearanceRedDownArrow, AppearanceRedDownInclineArrow, AppearanceGrayUpArrow, AppearanceGrayUpInclineArrow, AppearanceGrayRightArrow, AppearanceGrayDownInclineArrow, AppearanceGrayDownArrow, AppearanceGreenCircle, AppearanceYellowCircle, AppearanceRedCircle, AppearanceBlackCircle, AppearanceCharCheckBox, AppearanceCharExclamationMark, AppearanceCharCross, AppearanceCheckBox, AppearanceExclamationMark, AppearanceCross, AppearanceGreenFlag, AppearanceYellowFlag, AppearanceRedFlag, AppearanceFullStar, AppearanceHalfFullStar, AppearanceEmptyStar, AppearanceFilledCircle, AppearanceThreeQuartersFilledCircle, AppearanceTwoQuartersFilledCircle, AppearanceOneQuarterFilledCircle, AppearanceEmptyCircle, AppearanceFourFilledBoxes, AppearanceThreeFilledBoxes, AppearanceTwoFilledBoxes, AppearanceOneFilledBox, and AppearanceEmptyBoxes. In conditional appearance, you can use only the above pictures from the picture library. If the сonfiguration already has pictures with the same names, a picture from the сonfiguration is added to the collection and a warning is generated upon сonfiguration update. | This feature was not provided. Conditional appearance of the data composition system did not allow you to use pictures for conditional appearance of reports. | Specifying pictures in conditional appearance of reports built using the data composition system is now easier. |
| Pictures. | For common pictures, you can now specify that a common picture is used:
Property CommonPicture.ChoiceAvailability is ignored in 8.3.15 compatibility mode. Property CommonPicture.AppearanceAvailability is ignored in 8.3.15 compatibility mode. | This feature was not provided. | New feature: you can specify which common pictures can be used when working with a spreadsheet document in 1C:Enterprise mode and conditional appearance. As a result, there are less pictures a user can select from in these situations. |
| XML and XDTO support. | New feature: the platform supports XSD schemas containing types, in which attributes are defined via references to global attributes, but overriding such properties as default or fixed ones. | Upon trying to use in the platform XSD schemas containing types, in which attributes were defined via references to global attributes, but overriding such properties as default or fixed ones, errors occurred when checking the XDTO model, and such schemas were not available. | Eliminated unexpected system behavior. |
| Charts. Data composition system. | You can now build combo charts and display a secondary value scale for the following chart types:
Implemented animation upon chart value change. Implemented the SecondaryValuesAxis property for ChartPlotArea and Chart objects. New property: ChartScale.Display. New properties for the ChartSeries object: GraphicalPresentationType, AccumulationType, AccumulationGroup, UsedValuesAxis, ValuesFormatInLabels, PercentageFormatInLabels, and FormatInDataTable. The ChartSeries.Indicator property is deprecated and supported for compatibility purposes. Use the ChartSeries.GraphicalPresentationType property instead. The Chart.ChartType property value is Column by default. The Chart.Outline property value is False by default. New properties for objects DataCompositionAreaChartGroupAppearance and DataCompositionAppearance: GraphicalPresentationTypeInChart, AccumulationTypeInChart, and UsedValuesAxisInChart. New property: DataCompositionAreaChartGroupAppearance.AccumulationGroupInChart. For objects DataCompositionOutputParametersValues, DataCompositionGroupOutputParametersValues, DataCompositionChartOutputParametersValues, and DataCompositionAreaChartAppearance, implemented parameters ChartType.SecondaryValuesScale and ChartType.SecondaryValuesAxis. The ChartType.IndicatorInChart parameter is deprecated and supported for compatibility purposes. Use the ChartType.GraphicalPresentationTypeInChart parameter instead. New parameters for the DataCompositionAreaChartGroupAppearance object: ValuesFormatInChartLabels and FormatInChartDataTable. This change is not implemented in 8.3.15 compatibility mode. | It was impossible to build combo charts and display a secondary value scale. The Chart.ChartType property value is Column3D by default. The Chart.Outline property value is True by default. | New chart features. |
| Server clusters. | You can now start backup working processes. A backup working process is started in advance and server cluster overhead is synchronized for it. This feature allows you to reduce the time spent on switching the client application to a new working process in case of unexpected termination of the working process serving this client application. A flag indicating whether backup is required is set for the infobase. The number of backup working processes is calculated from the Number of infobases per process working server property. New properties: AdministrationInfobase.WorkingProcessesBackup and AdministrationWorkingProcess.Backup. The following Java-based methods are implemented in the administration server interface: IWorkingProcessInfo.isReserve(), IInfobaseInfo.getReserveWorkingProcesses(), and IInfobaseInfo.setReserveWorkingProcesses(). The following items are implemented for the cluster service command-line utility (rac):
| This feature was not provided. A new working process was started only after the current working process was terminated, which could lead to significant time delays upon client application reconnection. From the user's point of view, it looked like the client application interface froze at the time of connection to a new working process. | Reduced time delays resulting from switching the client application to a new working process. Improved application reactivity. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Managed forms. | In the client application form table that displays the value tree (including the All functions dialog box), search using the search string is done considering a parent and by words. In the history form, record date and time are no longer involved in search. | In the client application form table that displays the value tree, search was done ignoring a parent and by substring. In the history form, record date and time were involved in search. | Improved search in client application form tables that display trees (including in the All functions dialog box). |
| Web client. File operations. | Upgrade: security check of access to the file system and clipboard when accessing the web client in Google Chrome and Mozilla Firefox (including web browser extensions and file system extensions) is updated. Once the web browser extension and the file system extension are updated, if it is required to get access to the file system, a user will have to confirm that they trust the site (where the web client is published) to use the file system on their local computer. After that, there are no question until this permission is revoked (using settings of the web browser extension). If the user refuses to trust it, the old mechanism for getting permissions is used (a separate request per action). Clipboard operations are allowed accordingly. Permissions are stored broken down by site addresses where web clients are published. | In the web client, a separate question was displayed to a user upon each file operation, which was not user-friendly. | Simplified file operations in the web client regarding the user permission on operations with the file system and clipboard. |
| Collaboration system. | New feature: the user history now displays whether this user participates in a context conversation regarding an object associated with a form in the history. Optimized user history opening. | The user history did not display whether this user participated in a context conversation regarding an object associated with a form. | In the history, it is now easier for a user to find object forms, in the context conversation of which this user was a message recipient. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. Server clusters. | Improved performance of 1C:Enterprise platform running on Windows 8 or above when the client application and the server cluster are on the same computer. | Performance of 1C:Enterprise platform running on Windows 8 or above when the client application and the server cluster were on the same computer was less optimal. Interprocess interactions took more time. | Improved performance of 1C:Enterprise running on Windows 8 or above. |
| Spreadsheet documents. | Reduced amount of RAM used by a spreadsheet document that contains many text cells. | A spreadsheet document with many text cells needed more space in RAM. | A spreadsheet document now uses smaller amount of RAM. |
| Server clusters. | Improved performance of the server cluster when working with a large amount of session data. Managed form opening, a context server call, and temporary storage operations take less time now. New technological log event: <SDGC>. | The server cluster spent more time on handling a large amount of session data. Managed form opening, a context server call, and temporary storage operations took more time. | Improved server cluster performance. |
| Accumulation registers. | Improved performance of a virtual table of accumulation register balance. | When using a virtual table of accumulation register balance, more time was spent on getting the query result. | Improved performance of a virtual table of accumulation register balance. |
| Queries. | Optimized execution of query in client/server infobase mode, that includes the query language operator IN with a list of values, if the left section of IN operator contains a reference type field that includes several main tables, and the list of values contains references to different tables (from the list of composite type values) but not the Undefined value. This change is not implemented in 8.3.15 compatibility mode. | The query in client/server infobase mode, that includes the query language operator IN with a list of values, if the left section of IN operator contains a reference type field that includes several main tables, and the list of values contains references to different tables (from the list of composite type values) but not the Undefined value, took more time to execute. | Optimized execution of queries containing IN operator with composite type fields. |
| Internet-enabled functionality. | Optimized retrieving of email message headers using the InternetMailMessage.GetHeaderField() method. | Retrieving email message headers using the InternetMailMessage.GetHeaderField() method took a considerable amount of time. | Optimized email message headers retrieving. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Data display. | Upgrade: client applications (except the web client) running on macOS, Linux, and Windows are switched to graphics based on the Cairo library. | Client applications (except the web client) running on macOS, Linux, and Windows used their own graphics based on different technologies and libraries in each operating system. | Unified and optimized user interface display in supported operating systems. |
| Web client, web service, and HTTP service publishing tools. | In the dialog box for publishing the сonfiguration on a web server, labels now comply with the current client applications of the platform. | In the dialog box for publishing the сonfiguration on a web server, labels did not consider the mobile client. | The dialog box for publishing the сonfiguration on a web server considers the mobile client. |
| Full-text search. | New feature: full-text search by hashtag became available (strings of the #Word format, from the # character to the first space). To apply fuzzy search (both in interactive mode and search from 1C:Enterprise code using the FullTextSearchManager object), use the ~ character. This change is not implemented in 8.3.15 compatibility mode. | Search by hashtag was not supported but it was possible to find a hashtag value (the word after the # character) in the usual way or by double quoting a hashtag to search for. The # character was used for fuzzy search. | You can now hashtag objects involved in full-text search. As a result, it became possible to simply find several different types of objects grouped by hasgtag only. |
| Access rights. | If the access rights do not allow saving a spreadsheet document, a text document, a graphic chart, a geographical diagram, a package of displayed documents or an HTML document to the file, but after creating these objects, privileged mode was enabled, then the file can be saved. | If access rights did not allow saving a spreadsheet document, a text document, a graphic chart, a geographic diagram, a package of displayed documents or an HTML document to a file, then enabling privileged mode was ignored and the the files could not be saved. | Eliminated unexpected system behavior. |
| Input by string. | When using input by string for a managed application, all searched words are highlighted in search results if full-text search is not used for input by string or full-text search failed with an error. If full-text search in data is used for input by string, the The method of searching for the specified string during the input by string setting is ignored upon successful application of full-text search, the searched text is always split into words, and search is based on the beginning of the words. This change is not implemented in 8.3.15 compatibility mode. | When using input by string for a managed application, if full-text search was not used for input by string or full-text search failed with an error, two consecutive occurrences of the same string were not highlighted and only the first occurrence of the searched word was highlighted in the first half of results (when searching for one word). | Improved search result highlighting for input by string. |
| Data display. | With the Windows operating system, stability and responsiveness of the client application are improved when working with unavailable printers. | With the Windows operating system, there were some issues when working with unavailable printers, such as unexpected shutdown of the client application and a significant slowdown upon client application start. | With the Windows operating system, stability and responsiveness of the client application are improved when working with unavailable printers. |
| Server clusters. | This change is rolled back. New feature: parallel recalculation of register totals is available upon infobase restructuring, testing, and repair. System background jobs are used for recalculation. ID of such a background job is SystemBackgroundJob.RecalcTotals. Implemented the Number of totals recalculation job parameter for the Infobase parameters dialog box. There are 4 recalculation background jobs by default. New global context methods: GetTotalsRecalculationJobsCount() and SetTotalsRecalculationJobsCount(). | Register totals were recalculated sequentially upon infobase restructuring, testing, and repair for all required infobase registers. | New feature: totals are recalculated faster upon infobase restructuring, testing, and repair. |
| Automated testing. | You can now use form item additions in automated testing. Implemented the FormItemAdditionToTest object. For the FormTableToTest object, the result returned by GetSubobjects(), GetObject(), FindObjects(), and FindObject() methods can include objects of the FormItemAdditionToTest type. For the FormTableToTest.NavigateLevelDown() method, implemented the RowDetails parameter that allows you to specify presentation of a child group to go to. For the FormTableToTest.NavigateLevelUp() method, implemented the RowDetails parameter that allows you to specify presentation of a parent group to go to. For the FormTableToTest.Expanded() method, implemented the RowDetails parameter that allows you to specify presentation of a row of a table, for which it is necessary to check whether this row is collapsed or expanded. For the FormTableToTest.CanExpand() method, implemented the RowDetails parameter that allows you to specify presentation of a table row, for which the expanding feature is being checked. Implemented the FormFieldToTest.GetStateDisplay() function that returns the current state of a spreadsheet document field. Implemented the ApplicationToTest.WaitForState() function intended for waiting within the specified time. Implemented the FormGroupToTest.CurrentOpened() function that returns a group status: collapsed or expanded. Implemented the FormButtonToTest.CurrentCheckBox() function that indicates whether the button is pressed or displays the check box. A reference to the function that will return the notification processing result to the platform can be passed to the ExecuteNotificationProcessing() method now. | These features were not provided. | Extended automated testing capabilities. New features of the Taxi interface are considered in the functionality. |
| Managed forms. Configuration extensions. | The adopted form editor now displays changed and unchanged adopted form items with different colors. The form editor command that allows you to display only changed adopted and own form items in the form item tree is now available. The extension object property panel now displays properties of a сonfiguration object changed in the extension in relation to the extendable сonfiguration with another color. The extension object property panel now has a command that shows only properties that were changed in relation to the extendable сonfiguration. | In the adopted form editor, it was impossible to hide unchanged adopted items in the form item tree. Form items were not distinguished by color. In the property panel, it was not possible to quickly distinguish between changed and unchanged properties of an adopted configuration object. | New feature: easier editing of adopted сonfiguration objects. |
| Dynamic lists. | The dynamic list does not support fields with different expressions for selection and filtering as key fields. This change is not implemented in 8.3.15 compatibility mode. | It was possible to use fields with different expressions for selection and filtering as the key fields of the dynamic list. In this case, the dynamic list operation could cause various hard-to-diagnose errors. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | When opening a spreadsheet document in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format in 1C:Enterprise, conditional formatting is only imported for the area of the source document that contains data. Conditional formatting import now has reduced RAM consumption. When viewing a spreadsheet document obtained after import, there may be situations when the formatting of the resulting document differs from the source document (design of the document area that does not contain data). | When opening a spreadsheet document in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format in 1C:Enterprise, conditional formatting was not imported for the whole document. In this case, a session could abnormally terminate due to lack of RAM. | Improved 1C:Enterprise stability when importing spreadsheet documents in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format, when conditional formatting is set for the whole sheet, and not just for a meaningful area. |
| Data composition system. | The type of data composition system field that results from using the query language aggregate functions SUM() and AVERAGE() will be an unlimited length number. This change is not implemented in 8.3.15 compatibility mode. | The type of data composition system field that resulted from using the query language aggregate functions SUM() and AVERAGE() was the type of field, which was used as parameter for these aggregate functions. | Eliminated unexpected system behavior. |
| DBMS operations. | The data (Purpose field) returned by the GetDBStorageStructureInfo() global context method contains information that describes the tables that are created using the database copy functionality. | The data returned by the GetDBStorageStructureInfo() global context method did not contain information that described the tables that are created using the database copy functionality. The Main value was specified as the table purpose for all the tables after using the database copy functionality. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | When displaying a spreadsheet document containing pictures in cells or pictures of the Picture type:
This change is not implemented in 8.3.15 compatibility mode. | When displaying a spreadsheet document containing pictures in cells or pictures of the Picture type, the system behaved as follows:
| Corrected spreadsheet document pictures display. |
| Client application form. | The addon menu of the Search management form item contains only the appropriate commands, that is: search by current value, advanced search, search history, cancel search). This change is not implemented in 8.3.15 compatibility mode. | The addon menu of the Search management form item contained all the commands of the linked form table (similar to autofilling the table command bar). Visibility was turned off for "excess" commands. | Eliminated unexpected system behavior. |
| Full-text search. Server clusters. | When the UpdateIndex() method of the full-text search manager is called in the client/server infobase mode, preparatory actions are performed using the system background job (its parameters are similar to the system indexing background job). This background job runs on the same working server as the full-text search service. When you click the Refresh Index button of the Full-text search management standard function, the system behavior will be the same. If a single task is configured in the full-text search settings, it will be performed in a separate background job. | When the UpdateIndex() method of the full-text search manager was called in the client/server infobase mode, preparatory actions were performed at the same computer the method was called from. If a single indexing task was configured in the full-text search settings, it was performed in a common server execution thread. | Improved reliability and speed of full-text search indexing. All the indexing actions are performed on the working server, assigned for running the full-text search service. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Queries. | Upon query execution in the infobase file mode, if a number cannot be represented with the required accuracy, an exception is thrown. | Upon query execution in the infobase file mode, if a number cannot be represented with the required accuracy, a number where all digits are 9s is put in the query result. | Eliminated unexpected system behavior. |
| Administration tools. | Implemented Java 9 or later support for the administration server interaction interface from Java. | The administration server interaction interface from Java did not support Java version 9 or later. Only Java version 1.8 was supported. | Implemented support for modern Java versions. |
| Software licensing. | When running commands, the licensing utility sends unattended statistical information to 1C:Remote service by default. You can now deactivate this action when running one command using the --send-statistics parameter. | The licensing utility did not interact with 1C:Remote service. | New feature: you can accumulate statistical information about the licensing utility activity. |
| Functional options. | If a functional option is stored in a catalog, the functional option value is recalculated once a catalog item is deleted. | If a functional option was stored in a catalog, the functional option value was not recalculated once a catalog item was deleted and the code could get the old value of the functional option. | Eliminated unexpected system behavior. |
| Web client. System requirements. | When running on macOS, Google Chrome and Mozilla Firefox can now be used to work in the web client. | When running on macOS, only Safari could be used to work in the web client. | The list of supported web browsers for macOS is expanded. |
| Web client. System requirements. | Ended support of Google Chrome versions 48 and earlier. The web client is supported in Google Chrome versions 49 and later. | Google Chrome versions 48 and earlier were supported. | Ended support for legacy Google Chrome versions. |
| Web client. | On macOS, Google Chrome and Mozilla Firefox now support the file system extension and the add-in extension. Implemented the add-in adapter library for Google Chrome and Mozilla Firefox running on macOS. Changes were made to development technology for add-ins (read more). | On macOS, Google Chrome and Mozilla Firefox did not support the file system extension and the add-in extension. | Advanced file operations on macOS using the web client. |
| File operations. | The following methods are deprecated and supported for compatibility purposes (in all clent applications):
Use asynchronous equivalents of these methods instead. | The following methods could be used to create applied applications:
| Deprecated methods are no longer supported. |
| File operations. | Once the BeginPutFilesToServer() method or the BeginPutFileToServer() method is called, there is no need to wait for the method completion to call these methods again. | Once the BeginPutFilesToServer() method or the BeginPutFileToServer() method was called, it was necessary to wait for completion of a previously executed call to call the methods again. A recall attempt led to an error in the thin client or waiting for completion of the previous call in the web client. | You can now import several files (or file groups) at the same time. |
| Database copies. | You can now choose сonfiguration object properties to be passed to a database copy upon enabled standard replication. You can specify the following objects:
Other attributes (standard attributes, register changes, and common attributes included in separators) are always passed. A query accessing attributes that are outside of the copy is executed on the main database. If a database copy created in version 8.3.16 with restrictions on a composition of objects to copy is used, this copy will be considered deprecated when trying to use it on previous versions and refilled with data upon synchronization. New properties for the DatabaseCopyManager object: TabularSectionsUsage, ValueStoragesUsage, UnlimitedLengthStringsUsage, and OtherFieldsUsage. The following properties of the DatabaseCopyManager object became writable: DBMSType, DatabaseServer, and Database. Parameters of the DatabaseCopyManager.Add() method became optional. New properties for the DatabaseCopyContentItem object: Fields, TabularSectionsUsage, ValueStoragesUsage, UnlimitedLengthStringsUsage, and OtherFieldsUsage. The DatabaseCopyContentItem.Metadata property became writable. The Item parameter of Insert() and Add() methods of the DatabaseCopyContent object is mandatory. This change is not implemented in 8.3.15 compatibility mode. The database copy management standard data processor is changed. | All data of the selected сonfiguration objects was transferred to a database copy upon standard replication usage. It was not possuble to manage properties of data to transfer. The following properties of the DatabaseCopyManager object were read-only: DBMSType, DatabaseServer, and Database. Parameters of the DatabaseCopyManager.Add() method were mandatory. The DatabaseCopyContentItem.Metadata property was read-only. The Item parameter of Insert() and Add() methods of the DatabaseCopyContent object was optional. | When generating data for a database copy, you can now set up content and volume of data stored in the database copy more precisely. |
| External reports and data processors. | The user will only be checked for having the View right for the data processor/report used when calling GetForm() method of the DataProcessorManager and ReportManager objects. The Use right is no longer checked in this case. There are no checks for access rights when calling the GetForm() method of the DataProcessorManager and ReportManager objects. This change is not implemented in 8.3.15 compatibility mode. | When calling the GetForm() method of the DataProcessorManager and ReportManager objects an exception was thrown if the user did not have the Use right for the appropriate data processor or report. | Eliminated unexpected system behavior. |
| Data composition system. | Upgrade: you can apply conditional appearance to header areas of resource and totals fields. Conditional appearance can be managed both from 1C:Enterprise code and the selection form of the conditional appearance application area. Implemented the following properties for the DataCompositionConditionalAppearanceItem object: UseInResourcesFieldsHeader, UseInOverallHeader, and UseInOverallResourcesFieldsHeader. These properties are not available in 8.3.15 compatibility mode. This change is not implemented in 8.3.15 compatibility mode. | It was impossible to apply conditional appearance to headers of resource and totals fields. | Advanced conditional appearance features for reports built using the data composition system. |
| Dynamic lists. | On getting data, the dynamic list checks whether all filter fields are present in available filter fields. When the first field unavailable for filter is found, an error is generated. This change is not implemented in 8.3.15 compatibility mode. | On getting data, the dynamic list did not check whether all filter fields were present in available filter fields. | Eliminated unexpected system behavior. |
| Database operations. | In infobase file mode, unique indexes are created the same way they are created in client/server mode of the infobase. To force generation of indexes, change the compatibility mode and test and repair the infobase with the Restructure infobase tables check box selected.. When the compatibility mode is disabled, while writing data, index keys will be checked for uniqueness for indexes that were rebuilt upon testing and repair. Upon testing and repair (in any compatibility mode), index key uniqueness is not checked. This change is not implemented in 8.3.15 compatibility mode. | In infobase file mode, non-unique indexes of infobase tables were created even when unique indexes were created in other supported DBMSs in the same case. While writing data, 1C:Enterprise did not check index keys for uniqueness, which could cause problems with infobase migration from file mode to client/server mode. | Unified behavior of 1C:Enterprise in both file and client/server modes for operations with unique indexes. Reduced the number of issues that occur when migrating an infobase from file mode to client/server mode. |
| Dynamic lists. | When you press Enter (or double-click a row) in a row of a table linked to a dynamic list or when you call the ChangeRow() form table method, a form table extension will open a form linked to this row whether or not there is the Change command in the table commands. This change is not implemented in 8.3.15 compatibility mode. | When you pressed Enter (or double-click a row) in a row of a table linked to a dynamic list or when you called the ChangeRow() form table method, a form table extension will open a form linked to this row:
| Eliminated unexpected system behavior. |
| Information registers. | If a record set of an independent information register is written to the infobase without replacement, records will be checked for uniqueness in data import mode (the DataExchange.Import property is True). Refined the text of the error that occurs when data is not unique. This change is not implemented in 8.3.15 compatibility mode. | If a record set of an independent information register was written to the infobase without replacement, records were not checked for uniqueness in data import mode (the DataExchange.Import property was True). This behavior could result in data inconsistency. | Eliminated unexpected system behavior. |
| DBMS operations. | The behavior of the IN query language operator with the subquery became the same when using any DBMS. The results of such queries using IBM DB2, PostgreSQL, or Oracle Database might change. It is recommended that you analyze usage locations of the IN operator with the subquery and rewrite these queries if necessary. This change is not implemented in 8.3.15 compatibility mode. | The behavior of the IN query language operator with the subquery depended on the DBMS the query was executed on. | The result of the IN query language operator with the subquery does not depend on the used DBMS anymore. When using PostgreSQL, reduced the time spent on executing queries that contain the IN operator with the subquery. |
| Queries. | Upon addition or subtraction in the query language, if the left operand of the operation could not be NULL but the right operand could be NULL, it is assumed that the operation result can be NULL. | Upon addition or subtraction in the query language, if the left operand of the operation could not be NULL but the right operand could be NULL, it was assumed that the operation result could not be NULL. | Eliminated unexpected system behavior. |
| Server clusters. | In client/server mode, you can now specify roles to apply in a session for a security profile when switching to privileged mode. When privileged mode is enabled, roles specified in the security profile will be used in a session. When privileged mode is disabled, they will return to roles specified by a user. If full access to privileged mode is set in the security profile, a set of roles does not change when privileged mode is enabled. Implemented the Privileged mode roles property for the security profile. New properties for the AdministrationSecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode. New properties for the ISecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode. The following Java-based properties are implemented in the administration server interface for the ISecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode. The following parameters of the profile command are implemented for the cluster service command-line utility (rac): privileged-mode-roles and full–privileged-mode. Properties AdministrationSecurityProfile.PrivilegedModeAllowed and ISecurityProfile.PrivilegedModeInSafeModeAllowed (server cluster administration COM interface and Java-based administration server interface) are deprecated and supported for compatibility purposes only. | This feature was not provided. It was impossible to explicitly specify a list of roles that would be applied in a session when switching to privileged mode. | Expanded features of security profiles in client/server mode. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile client. | The mobile client now supports authentication using OpenID Connect protocol. Authentication uses a system web browser of a mobile device. Authentication using OpenID Connect is supported for iOS 9.0 or higher devices and Android devices that have Google Chrome installed. | This feature was not provided. | The mobile client now supports authentication that was available in thin client and web client. |
| Mobile client. | A сonfiguration synonym is not checked for matches when you start the mobile client. The mobile client will be started if a сonfiguration name has not changed since mobile application build and a сonfiguration signature matches its digest. | Once a сonfiguration synonym changed, it was impossible to use this configuration with the mobile client application that was built with another synonym (for example, which did not have a synonym in any language). | You do not now need to rebuild a mobile application of the mobile client when only a сonfiguration synonym changes. |
| Mobile client. Mobile application builder. | Implemented a mobile client with the operating offline feature. This client application allows you to use it both online (as a mobile client) and offline (as a standalone mobile application). Implemented option to switch from online to offline mode and back. Implemented an offline configuration feature that will be available on the mobile device in offline mode. Offline configuration is a subset of the main configuration. The offline configuration may include all metadata that exists in the platform for a PC. Configuration objects may not be a part of an offline configuration. Configuration extensions cannot be included in an offline configuration. Implemented the MainServer global context property. Implemented the MainServerAvailable() global context method. Implemented the OnMainServerAvailabilityChange() client application module event. The following is implemented for the ClientApplicationForm object:
Implemented the BehaviorWhenMainServerIsUnavailable property for the input field, button, decoration, and table form elements. Implemented the OfflineConfigurationContents, OfflineConfigurationRestrictionRoles properties for the Configuration object. Implemented the BehaviorWhenMainServerIsUnavailable property for the common command and common form. Implemented the form preview in the mobile client mode in offline mode for the client application form editor. Implemented the display of elements and attributes that are not available offline on a mobile device in the client application form editor. Implemented the feature to perform configuration verification in the offline mobile client mode. Implemented the feature to specify in which mode the mobile client will be started in Designer settings. Implemented new debugging items for the debugger. The mobile application builder allows building a mobile client application with the offline mode feature. | This feature was not provided. It was possible to create either a standalone mobile application or a mobile client that worked online. | Expanded the options to build mobile applications using 1C:Enterprise. |
| Mobile platform. Mobile client. Mobile application builder. Mobile device-specific features. | Implemented the feature to automatically manage mobile application data backup using the mobile operating system. Implemented the Backup using OS tools mobile application permission. The backup is performed as follows:
The mobile application builder uses this permission to correctly configure the mobile application being built. | This feature was not provided. | Automatic mobile application data backup (without user interaction) is now possible. |
| Mobile platform. Mobile client. Mobile application builder. Mobile device-specific features. | Implemented the mobile application permission, which allows you to manage the third-party applications installation. This feature is supported by the mobile application builder when building applications for Android. Implemented ApplicationInstallation permission. | This feature was not provided. The third-party applications installation has always been permitted. | If the third-party applications installation is not required for the application, you can reduce the total number of permissions that the mobile application requires when running on Android. |
Information that the message text is displayed as a formatted string has been added to the Guide.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Development tools. | You can now export a configuration which size exceeds 2 GB to a 1Cv8.cf file from Designer. Designer version 8.3.16 and later can only be used to import such configuration. | When attempting to export a configuration which size exceeds 2 GB to a 1Cv8.cf file, the upload was interrupted with a confusing error message. | Exporting very large configurations to a 1Cv8.cf file is now available. |
| Data display. | GetStringDeclensions() and GetStringDeclensionsByNumber() methods return a maximum of 10 declension variants of the passed phrase. This change is not implemented in 8.3.15 compatibility mode. | There was no limit for GetStringDeclensions() and GetStringDeclensionsByNumber() methods of the number of the passed phrase declension variants. | GetStringDeclensions() and GetStringDeclensionsByNumber() methods performance has been improved due to decreasing the number of declension variants. |
| Data composition system. Dynamic lists. | The data composition layout composer adds ordering from the data composition system settings to the top of the ordering list of data composition layout request. This change is not implemented in 8.3.15 compatibility mode. | The data composition layout composer added ordering from the data composition system settings to the bottom of the ordering list of data composition layout request. | Eliminated unexpected system behavior. |
| Client application form. Data display. | When automatically calculating the interface element text color, a more contrasting color relative to the element background color is selected. | When automatically calculating the interface element text color, a less contrasting color relative to the element background color was selected. | Eliminated unexpected system behavior. |
| Data accelerator. | The RAM consumption for storing variable-length fields (variable-length strings and value storage) in the Data Accelerator has been reduced. Execution of some types of queries has been optimized. | Data Accelerator required more RAM to store variable-length fields (variable-length strings and a value storage). Execution of some types of queries was not optimal. | Data Accelerator has been optimized. |
| Processing PDF documents. | New feature: digital signature in PDF documents. Embedding of a digital signature visual representation into a document is also available. Implemented PDFSignatureDescription object. LinkType and ContentType properties are implemented for PDFAttachment object. ContentType and LinkType parameters are implemented for PDFAttachmentCollection.Add() method. ReadPDF object is now available in the thin client and in the web client. File system extension is required to use web client. The following methods are implemented for the ReadPDF object: CheckSignatures(), CheckSignature(), GetSignatureDescription(), StartOpening(), StartRetrievingAttachments(), StartSignaturesCheck(), StartSignatureCheck(), StartRetrievingSignatureDesctiption(), StartClosing(). WritePDF object is now available in the thin client and in the web client. File system extension is required to use web client. WriteSignature(), StartOpening(), StartWritingAttachments(), StartWritingDeletingAttachments(), StartWritingSignature(), StartClosing() methods are implemented for the WritePDF object. | This feature was not provided. Creating a separate digital signature file was available. | Expanded PDF documents management capabilities. The document consistency can now be secured after signing. |
| Client application form. | The OnClose event handler called after the ShutdownSystem (False) method has the Shutdown parameter set to True. This change is not implemented in 8.3.15 compatibility mode. | The OnClose event handler called after the ShutdownSystem (False) method had the Shutdown parameter set to True in the web client and False otherwise. | Eliminated unexpected system behavior. |
| Global search. | If an error occurred while performing the global search, the search result is placed to the GlobalSearchResultElement object, which has the ErrorDetails object placed to the Value property. When displaying the results, the error will be shown using the SpecialTextColor style color. Serialization and XDTO serialization has been implemented for the ErrorDetails object. | Errors that occurred while performing a global search were not displayed to the user. | Eliminated unexpected system behavior. |
| Database copies. | The cases of excessive RAM usage when transferring data to a copy (including the Data Accelerator) have been fixed. | Cases of excessive RAM usage were possible when transferring data to a copy. | Eliminated unexpected system behavior. |
| Common attributes / Data separation. | When using two (or more) separators that are used at the same time (i.e., store their value and conditional separation flag in the same configuration objects), the DeleteInfobaseData() method will deem the configuration object to be included in the current area if it is separated by at least one of the separators from the list of separators using the same configuration objects to store their parameters. It is recommended to analyze using the DeleteInfobaseData() method in the separated configurations and refactor this code, if required. This change is not implemented in 8.3.15 compatibility mode. | When using two (or more) separators that are used at the same time (i.e., store their value and conditional separation flag in the same configuration objects), the DeleteInfobaseData() method deemed the configuration object to have been included in the current area if it was separated by at least one of the separators from the list of separators using the same configuration objects to store their parameters. | The approach to determining the data area using the DeleteInfobaseData() method has been changed. |
| Mobile platform. Mobile client. | Improved execution of certain operations (starting, creating an infobase, etc.) in mobile applications built for Android. The size of mobile applications built for Android has slightly increased. | Execution of certain operations (starting, creating an infobase, etc.) in mobile applications built for Android took more time. | Optimized 1C:Enterprise mobile version, running on Android. |
| Mobile client. | In an offline mobile client, a form that reopens after changing the availability of the main server is reopened with the same set of form parameters as the original form. The documentation contains the recommendation for generation of the offline mobile client home page. The -MobileStandalone parameter has been implemented for the CheckConfig Designer batch run command, which allows to check the configuration for using an offline mode. The -RebuildStandaloneCfg parameter is implemented for the IBCheckAndRepair Designer batch mode run command, which allows to regenerate the offline configuration. | In an offline mobile client, a form that reopens after changing the availability of the main server was reopened with the set of parameters that included the original form key parameters only. | Improved offline mobile client running. |
| macOS. Linux. Common objects. | The UniqueID object creates version 4 universal unique identifiers (a completely random universal unique identifier) when used on PCs running Linux and macOS. | The UniqueID object created version 1 universal unique identifiers (universal unique identifier dependent on time and network adapter MAC) when used on PCs running Linux and macOS. | Enabled using the platform’s built-in features if it was required to pass a version 4 universal unique identifier to an external service during integration and the existing universal unique identifier was not suitable for such transfer. |
| Dynamic lists. Full-text search. | The " " (space) character is used as a separator only when breaking into words, which is performed at input by string and at search in a dynamic list. The ".", ",","-", "/" and "\" characters are no longer considered as separators and are searched for as regular characters. Not only the lines between every two separators, but also the lines from each separator to the end of the line are added to the full-text search index during indexing. | The ".", ",","-", "/" and "\" characters were used as a separators when breaking into words, which is performed at input by string and at search in a dynamic list. | Search as you type and in the dynamic list has become better suited to the user's habits. |
| Mobile client. | It now supports forced use of main server. Use this feature when you start to fill in the infobase of a mobile client with a standalone mode enabled. SetPreferableMainServerUse()/GetPreferableMainServerUse() global context methods are implemented. | This feature was not provided. | Now, you can avoid access to a local infobase of a mobile client , when you begin to populate this database. |
| Mobile platform. Mobile client. | Now you can manage whether a mobile device can enter sleep when the mobile application is running. New global context methods: SetComputerIdlingToSleepProhibition() and GetComputerIdlingToSleepProhibition(). | This feature was not provided. | Now you can block mobile device idling to sleep, which can make it easier to use the mobile application in some usage scenarios. |
| Mobile client. | Remember Me check box is available in the mobile client authentication dialog box. If this check box is selected and standard authentication is used (without biometrics), authentication data is saved in the mobile device secure storage. The following commands of the QR-code designed to add an infobase to a mobile client are now supported:
The following parameters of the /AddInfoBase command of e1c:// schema are supported:
| These features were not provided. | Mobile client start settings are now more detailed. |
| Full-text search. | During infobase data indexing, if the string does not contain any alphanumeric characters, the full-text search index comprises of substrings from each non-alphanumeric character to the end of the line only if the length of the original string is less than 64 characters. | During infobase data indexing, if the string did not contain alphanumeric characters, the full-text search index comprised of substrings from each non-alphanumeric character to the end of the line. As a result, data indexing consumed a big amount of RAM. | Eliminated unexpected system behavior. |
| Mobile client. | When executing a mobile client with the option of standalone mode, the 1C:Enterprise language modules are compiled using the following preprocessor commands:
You can now find out which server is currently used in a client application form and will be called during a server call. The ClientApplicationForm.CurrentFormServer property is implemented. The GetCurrentServer() global context method is implemented. The StandardProcessing parameter that defines whether the dialog box with the suggestion to reopen the form will appear is implemented for the OnMainServerAvailabilityChange event handler of the client application form. The MobileClient value, defining the mode of the mobile client session is implemented for the InfobaseSession.ApplicationName property. The ApplicationPresentation() method now supports the MobileClient parameter value. | When executing a mobile client with the option of standalone mode, the 1C:Enterprise language modules were compiled using the following preprocessor commands:
| Preprocessor commands used to distinguish the client-server interaction methods are now easier to understand when using the mobile client with standalone mode option. It is now easier to determine which server will be used in the form and called during the next server call from the 1C:Enterprise language. |
| Collaboration system. | To deploy your own instance of the collaboration system server, you can purchase a specific software Read more. that doesn't require the CORP license. | CORP license was required to deploy a collaboration system server instance. | To deploy an instance of the collaboration system server, you have to fulfill one of the conditions:
|
| Localization. | Localized client application interface for Armenian (hy). | This feature was not provided. | 1C:Enterprise is now available for Armenian-speaking users. |
| Collaboration system. | When displaying a collaboration system message specified by a formatted string, the navigation links from this formatted string are recognized automatically. If a navigation link has an appearance specified (colour, font, etc.), it will not be recognized. | When displaying a collaboration system message specified by a formatted string, the navigation links from this formatted string were not recognized automatically | Eliminated unexpected system behavior. |
| DBMS operations. | When using PostgreSQL DBMS in the client-server mode, the infobase restructuring causes the database structure to change. These changes are required to support PostgreSQL 12. The change does not affect the application operation. | The database structure did not support PostgreSQL 12 DBMS. | The database structure supports PostgreSQL 12 DBMS. |
| Client application form. | MoveUp and MoveDown commands are now available for the form table linked with data of FormDataCollection or ValueList type with the set row filter. MoveUp and MoveDown commands are available for multiple rows selection in tables linked with data of the ValueList type. | MoveUp and MoveDown commands were unavailable for the form table linked with data of FormDataCollection or ValueList type with the set row filter. MoveUp and MoveDown commands were not supported for multiple rows selection in tables linked with data of the ValueList type. | Eliminated unexpected system behavior. |
| System requirements. Mobile platform. Mobile client. | Implemented support for Apple iPhone 11 device family. Implemented support for iOS version 13. | Apple iPhone 11 device family was not supported. iOS version 13 was not supported. | 1C:Enterprise supports new operating systems and devices. |
| Internet-enabled functionality. | Now the OAuth2 protocol can be used for emails together with the SMTP protocol. The InternetMailProfile.AccessToken property is used for authentication. | The OAuth2 protocol was used for emails for the IMAP protocol only. | Now email servers with the OAuth2 authentication protocol are supported if you use SMTP. |
| Collaboration system. | Now you can take advantage of separate settings of notification sounds for messages and video calls in the dialog box of collaboration system settings. Notification settings from previous versions apply to messages. Video call notifications are enabled by default. Video call notifications allow playing sound notifications upon:
| Separate settings of notification sounds for messages and video calls were not supported in the dialog box of collaboration system settings. | Users can mute or unmute video call notifications and default notifications separately. This will reduce missed video calls. |
| Collaboration system. | Now you can click Add users to video call to add a new user during a video call. The command is now available:
| During a video call, you needed to click Start a video call to add a new user:
| Now the name of the command for adding a new user to a video call is more user-friendly. |
| Client application. | When using thick and thin clients running Windows, changed the view of titles of independent windows (main application window, calendar window, calculator window, system dialog boxes, and other):
| When using thick and thin clients running Windows, independent windows (main application window, calendar window, calculator window, system dialog boxes, and other) were always displayed with the operating system title in remote desktop (RDP) mode or RemoteApp mode. | Improved appearance of the application. When using client applications in terminal mode, the application appearance is now more user-friendly. |
| Collaboration system. | Updated the dialog box of collaboration system settings. Settings specified in the dialog box of collaboration system settings are applied at once without clicking any buttons. Now the button that opens the dialog box is at the top of the Conversations window. Now the dialog box of collaboration system settings has a button that opens the dialog box of device selection where you can:
Now you can open the dialog box of device settings during a video call. In the web client, the dialog box of device settings is displayed in Google Chrome and Mozilla Firefox only if the web client is published using HTTPS protocol (or at localhost). The publication can access the microphone and camera. In the dialog box of device settings, the list of devices and their names can differ from the list of devices and their names in thin and thick client applications (for the same computer). | The button that opened the dialog box of collaboration system settings was at the bottom of the Conversations window. Settings specified in the dialog box of collaboration system settings were applied after clicking OK. Users could not specify the devices used. | Improved collaboration system settings if there are several computer devices that can be used for calls (audio and video calls). |
| Administration tools. Client application. | Upgrade: on computers running Windows, users without administrative rights can install the client application ("for user" installation option). The application is installed to %LOCALAPPDATA%\Programs. With this installation option, 1C:Enterprise server cluster cannot be installed as an operating system service. You can still install client applications in the "for computer" mode (with administrative rights). The "for user" and "for computer" installation options can coexist. Both lists of installed applications will be used upon client application selection. We recommend that you check configurations for explicitly specified directories that store the system. Use the BinDir() global context method instead of explicitly specifying the path. | On computers running Windows, the client application could be installed only if users had administrative rights or it required users to enter an administrator password if they did not have such rights. | Now users without administrative rights can install the client application. |
| Mobile client. Collaboration system. | For the mobile client, implemented collaboration system video calls. The mobile device position (in front of the eyes or close to an ear) is considered upon video calls. | This feature was not provided. | Now you can use collaboration system video calls in the mobile client. |
| Collaboration system. | If the client application is connected to the client application agent, a notification about an incoming video call is shown even if the client application is not running. If a user accepts an incoming call, the client application is launched. A video call to callers starts automatically here. | If the client application was connected to the client application agent, a notification about an incoming video call was not displayed if the client application was not running on a computer. | Users will receive notifications about incoming video calls when the client application is closed. Previously, such video calls were missed. |
| Client application installation. | If Windows XP or Windows Server 2003 have Windows installer v3.1, 1C:Enterprise can be installed only in the per-machine installation context (providing that the user is granted the Administrator rights). If Windows XP or Windows Server 2003 have Windows installer updated to v4.5, 1C:Enterprise can be installed in the per-user installation context (if the user is not granted the Administrator rights). | If Windows XP or Windows Server 2003 had Windows installer v3.1, 1C:Enterprise couldn't be installed raising the error due to the unsupported installer version. | Eliminated unexpected system behavior. |
| Collaboration system. | The header of the client application includes a menu that accommodates all Collaboration System commands. The menu appears only is the infobase in connected to the Collaboration System. Some command items are clickable only if their features are available. For example, the video call button is faded if the user's machine has no camera. | The Collaboration System buttons were scattered over the interface. | Collaboration System user interface is improved. |
| Pictures. Mobile platform. Mobile client. | Upgrade: 1C:Enterprise mobile version now supports multipage TIFF files, just like the personal computer platform. | This feature was not provided. | Upgrade: 1C:Enterprise mobile version now supports multipage TIFF files. |
| Collaboration system. | Improved application stability when using video calls of the collaboration system in thin and web clients. Changes in the dialog box to set up parameters of the used hardware (the Conversations... menu - the Settings menu item - the Settings button) are applied at once without confirming the change. | Application stability was low when using video calls of the collaboration system in thin and web clients. | Improved application stability when using video calls of the collaboration system in thin and web clients. |
| macOS. System requirements. | Updated system requirements for the client application running macOS. The client application is supported only on macOS 10, starting from version 10.12 and later. | The system requirements for the client application running macOS were version 10.12 and later. | Updated system requirements for the client application running macOS. |
| Server clusters. | When a working process fails, switching the session to a backup working process takes less time. | When a working process failed, switching the session to a backup working process took more time. | In the backup cluster, working process emergencies are now less visible to users. |
| Documentation. | The documentation contains a recommendation for using the HTTPs protocol when working with an infobase engaged in commercial operation. | The documentation did not contain a recommendation for using the HTTPs protocol when working with an infobase engaged in commercial operation. | The documentation recommends using safer methods of working over the Internet. |
| Regional settings. | Upgrade: in accordance with the Federal Law of the Russian Federation No. 432-FZ, a new time zone is applied for Volgograd oblast. The update is applied to all 1C:Enterprise system components, except for the web client. The web client sets the time in accordance with the time zone information provided by the operating system and web browser. | 1C:Enterprise ignored the changes introduced by the Federal Law of the Russian Federation No. 432-FZ. | New time zone settings are applied due to the legislation change. |
| Processing PDF documents. Spreadsheet document. | For a PDF document, it is now possible to insert an arbitrary image or a spreadsheet document in a specified PDF document area. New object: DetailsOfPDFObjectToDisplay. New methods for the WritePDF object: WriteObjectToDisplay() and WriteObjectToDisplayAsync(). | This feature was not provided. | Advanced PDF document features. |
| Client application. Client application installation. Web client. | Platform files and extension files for web browsers, and distribution packages used in Windows are signed only with the SHA256 algorithm. With Microsoft Internet Explorer (when running Windows XP, Windows Vista, Windows Server 2003, or Windows Server 2008), enable the option to load and attach unsigned add-ons. We recommend that you use Windows 7 and later (including the web client) to work with 1C:Enterprise. | Platform files and extension files for web browsers, and distribution packages used in Windows were signed with SHA1 and SHA256 algorithms. | The outdated and insecure SHA1 cryptographic hash algorithm is no longer supported. |
| Client application. Administration tools. | Now you can choose an installation mode for 1C:Enterprise: for all users or for the current user. This feature is implemented both in the interactive mode and as command-line parameters/configuration file parameters. New InstallForUsers parameter for 1cestart.cfg configuration file. New ALLUSERS command of the startup command line for the setup.exe utility. | The client application installation mode was selected only by the current user access rights. Even when a user knew the administrator password, the installation for all users could be started only when the setup.exe utility was run under an administrator. | Simplified 1C:Enterprise platform administration. You can select an installation mode for the client application as required by the current administration policies. |
| System requirements. DBMS operations. | The system now supports Postgres Pro DBMS of the following versions (only for x86-64):
| These DBMS versions were not supported.
| Extended list of supported DBMS. |
Version 8.3.15 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.14 is now implemented. | Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.13 was available. | Configurations developed using 1C:Enterprise platform version 8.3.14 or earlier can now run on version 8.3.15 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.15 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.14 after the migration to version 8.3.15, even if you disable the compatibility mode (simply enable it again). |
| 1C:Enterprise script. | If some errors occur, a stack of calls leading up to the error (not related to nested exceptions) is now displayed in detailed error description. In 1C:Enterprise Development Tools, call stack navigation is now available. | If an error message occurred, detailed error description did not include a call stack leading to the line with error (except for nested exceptions). | Improved diagnostics of application errors. |
| Internet-enabled functionality. Administration tools. Event log. | Implemented two-factor authentication. New data for event log events: _$Session$_.Authentication, _$Session$_.AuthenticationError, _$User$_.New, _$User$_.Update. Implemented the following event log events: _$Session$_.AuthenticationFirstFactor, _$InfoBase$_.SecondFactorAuthTemplateNew, _$InfoBase$_.SecondFactorAuthTemplateUpdate, _$InfoBase$_.SecondFactorAuthTemplateDelete | This feature was not provided. | Expanded user authentication options. More secure user authentication is available now. |
| Charts. Data composition system. | New feature: doughnut and 3D doughnut charts. New properties for the ChartType system enumeration: Donut and Donut3D. Implemented the Chart.DonutChartInnerRadius property. Implemented the ChartType.DonutChartInnerRadius parameter for the following objects: DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance. | This feature was not provided. | New chart features. |
| Spreadsheet documents. | Now you can specify a formatted string as a spreadsheet document header or footer. Included the FormattedString type in types of the following properties of the SpreadsheetDocumentHeaderFooter object: LeftText, CenterText, and RightText. With an editor of spreadsheet document headers and footers, you can edit a formatted string. When you start editing the relevant field with the header or footer text, the check box of output of the relevant header or footer to the spreadsheet document is selected automatically. Upon exporting a spreadsheet document, formatting of headers and footers is saved in the following formats: PDF (*.pdf), Microsoft Office OpenXML (*.xlsx and *.docx), Microsoft Excel (*.xls), and Open Document Spreadsheet (*.ods). For more information on how to use a formatted string for displaying headers and footers, see 1C:Enterprise documentation | This feature was not provided. | Expanded spreadsheet document export features. |
| Spreadsheet documents. | New feature: you can save a spreadsheet document to PDF/A-1 (a format for long-term storage). When you save to PDF/A-1 format, remember the following:
Implemented the SpreadsheetDocumentFileType.PDF_A_1 system enumeration value. | This feature was not provided. | Expanded spreadsheet document export features. |
| macOS. Collaboration system. | Client applications running under macOS now support collaboration system video calls. | This feature was not provided. | Implemented collaboration system features under macOS. |
| Data composition system. | New feature: you can save changes upon closing a form for the report settings form and the form for editing a report option. User prompt is generated before saving. The upgrade is valid only if the StandardProcessing parameter of the BeforeClose form event handler is set to True. | This feature was not provided. Upon closing the form, changes in the form were lost. | Reduced risk of losing changes made in the report settings form or the report option form in case of incorrect closing of the editing form. |
| Database copies. Information registers. Accumulation registers. Standard functions. | New feature: you can transfer not all register data but data only for a specific period to a copy for information registers and accumulation registers. This feature is available only for a standard replication. New property: DatabaseCopyContentItem.Filter. New feature for the Database copy management standard data processor. You can set filter by a period for information registers and accumulation registers. New feature: upon defining the query place, you can analyze a period condition in addition to the existing checks. | This feature was not provided. | Extended database copy management features. Improved performance of the database copy management feature by reducing data passed to a copy. |
| Database operations. Common attributes / Data separation. | New feature: you can get the data size that this data occupies in DBMS tables (including a specific data area). Upon calculating the size, the size of data history, extensions, and platform service tables (indexes, etc.) is not considered. New global context method: GetDataBaseDataSize(). | This feature was not provided. | New feature: you can estimate the size of data available in a database area or table. |
| Configuration extensions. | New feature: you can mark a managed extension property so that a mismatch of this property in the extended configuration and in the extension will not block the extension use, but a user will get a message stating that the property value in the extension and the property value in the extended configuration do not match. | This feature was not provided. | New feature: informing of changes of some extended configuration properties is available. Changing such properties does not block extension use, but this change must be processed by the extension developer separately. |
| Configuration extensions. Development tools. | New feature: you can map extended configuration objects and extensions by IDs. Implemented the feature helping to resolve conflicts upon rename conflicts. Mapping objects by IDs can be disabled. New property for the configuration extension: Support mapping to extended configuration objects by internal IDs. New property for adopted extension objects: Extended configuration object. | Extended configuration objects and extensions were mapped only by names. | Simplified diagnostics of renaming an extended configuration object adopted to an extension. Now there is a feature for resolving conflicts upon such rename. |
| Configuration extensions. | Upon creating a new extension, the Compatibility mode extension property is no longer a managed property. | Upon creating a new extension, the Compatibility mode extension property was a managed property. | Simplified development and applicability of extensions. |
| Data display. | New pictures are added to the picture library: Notify, DontNotify, DontDisturb, and SendMessage. | The listed pictures were not available in the picture library. | The picture library is upgraded. |
| Configuration extensions. | New feature: you can adapt extended configuration methods. An extended method is fully copied to an extension where changed code is enclosed by preprocessor directives. During application, it is checked whether the extended method is not changed in relation to the method in the extension. New annotation: ChangeAndValidate. New preprocessor directives: Delete and Insert. You can change one method only in one extension. If two extensions that extend the same method using the ChangeAndValidate annotation are found, only one extension will be applied to the infobase. If a method change in the extended configuration is found, three-way merge using an external application only is available. If an external application for comparing and merging modules is not configured in Designer, merge will be unavailable. | Making changes to the method with control of module source code consistency was unavailable. | Simplified extended configuration method extension if a small method change is required. |
| Web client. | When you start the web client on mobile devices, there is no message prompting that the used web browser version is not supported. New feature: partial support of the web client on mobile devices. Full support of the web client on mobile devices is not implemented. Fixed problems that occur in the web client on mobile devices in main scenarios. | Web client was supported on iPad tablets only. | Web client is partially available on mobile devices. |
| Common objects. | New feature: upon solving a system of linear equations, you can search for connected components of various types for graphs built based on a system of linear equations. Implemented the ComponentsGetMethod parameter of the SolvingLinearEquationsSystems.GetConnectedComponents() method. In 8.3.14 version compatibility mode, this parameter value will be StronglyConnectedComponentsWithoutLinkRequirementWithinComponents. | This feature was not provided. | Advanced features for solving a system of linear equations. |
| Collaboration system. | New link to collaboration system messages. Implemented the CollaborationSystemStandardCommand.GetMessageURL system enumeration value. | This feature was not provided. | Now you can obtain links to specific collaboration system messages. |
| Managed forms. | New feature: a flag field of a client application form can be displayed as an off-on switch. New property of the CheckBoxType.Switch system enumeration. In version 8.3.7 or earlier compatibility mode and in platform version earlier than 8.3.15, the CheckBoxType property value set to the Switch value is the Auto value. | This feature was not provided. | Extended system presentation features. |
| Managed forms. | The client application displays a text document, a spreadsheet document, a graphical schema, and a picture in the client application system form. This is available in the following cases:
A form with a displayed spreadsheet document or graphical schema has a command bar making editing of the relevant document easier. New events for a form field extension for a spreadsheet document, a text document, and a graphical schema: BeforeWrite, AfterWrite and BeforePrint. This change is not implemented in version 8.3.14 compatibility mode. | The client application displayed a text document, a spreadsheet document, a graphical schema, and a picture in special forms. Such forms did not have command bars. | Editing platform documents is now more convenient and intuitive. You can now process saving and printing of a text document, a spreadsheet document, and a graphical schema. |
| Managed forms. | Implemented the option to manage the command home position in the command bar:
New form button property: LocationInCommandBar. The OnlyInAllActions form button property is deprecated and supported for compatibility purposes only. Implemented automatic filling of the LocationInCommandBar property based on the OnlyInAllActions property. Now this mode is available for the client application form button when there is no more than one button linked to one command inside the automatically filled group. New client application button property: CommandUniqueness. New property for the picture field extension and the Picture kind decoration: Scale. This property is ignored in version 8.3.6 or earlier compatibility mode. | For a client application form command, only an indication that a command was located either in the command bar or in the More actions menu was available. | Improved options for creating command interface of the client application form. |
| Data display. | New pictures are added to the picture library: ZoomOut and ZoomIn. | The listed pictures were not available in the picture library. | The picture library is upgraded. |
| Managed forms. | The following features are available for the Planner object:
| These features were not provided. | New planner features. |
| Collaboration system. | New feature: you can define a list of selecting collaboration system users upon creating a context conversation message, a noncontext conversation message, or a video call. You can now create a form of selecting collaboration system users. New event for the ClientApplicationForm object and client application module: CollaborationSystemUserAutoComplete. New event for the ClientApplicationForm object and client application module: CollaborationSystemUserChoiceFormGetProcessing. New сonfiguration property: DefaultCollaborationSystemUserChoiceForm. You can now get a context conversation ID in the client application form (on the client application side). Implemented the BeginGettingConversation() method. | There was no option to override a list of selecting collaboration system users upon selecting a user. Earlier, you could get a context conversation ID on the server side only. | New collaboration system operations for selecting users upon creating messages, conversations, and video calls. |
| Interface. | Updated the Taxi interface. New appearance includes the following main changes:
Implemented the StrFindAndHighlightByAppearance() global context method that allows you to highlight some substrings in the string. The ClientApplicationInterfaceContentSettingsItem object cannot be created for the ToolsPanel panel. The tools panel is ignored in the settings of the main application window panels. New methods for the ClientApplication object: GetOSTitleRepresentation() and SetOSTitleRepresentation(). The Default search form сonfiguration property is deprecated. We recommend that you use global search feature instead. | The Taxi interface had different appearance. | Improved application navigation, increased usability, and developed the interface in accordance with modern trends in interface creation. |
| Spreadsheet documents. | Upon editing spreadsheet document headers and footers, automatic calculation of the page field size is available now if the specified header or footer cannot be placed in the current page field sizes. To calculate the size, click Ok in the headers and footers editing form and page parameter setting form. New feature: you can get the header or footer size. New feature: you can get the page field size. New methods for the SpreadsheetDocument object: CalculateHeaderSize(), CalculateFooterSize(), GetPrinterTopMarginSize(), GetPrinterBottomMarginSize(), GetPrinterLeftMarginSize(), and GetPrinterRightMarginSize(). | This feature was not provided. Earlier, you could pick the size of fields, headers, and footers only manually or iteratively. | New feature: spreadsheet document page fields can be set automatically according to the specified header or footer. |
| Full-text search. | Implemented search by meaningful word parts. In search results, a word is now highlighted if it has a meaningful part. New feature: you can specify meaningful word parts in user dictionaries of full-text search. New item for a description file of a user dictionary of full-text search: <Roots>. To enable search by meaningful word parts, rebuild a full-text search index. It works automatically if the Russian language is selected in regional infobase settings or a user dictionary of full-text search with a list of meaningful word parts is specified for the infobase. New methods for full-text search manager: GetSeparationOfCompositeWordsMode() and SetSeparationOfCompositeWordsMode(). | This feature was not provided. | Improved full-text search usability. |
| Dumping configurations to files/Restoring configurations from files. | If you need to dump configuration information (the DumpConfigToFiles command of Designer batch mode) in a file with objects to dump (the listFiles dump command parameter), specify the Configuration ID. There is no need to specify a configuration name. | If you needed to dump configuration information (the DumpConfigToFiles command of Designer batch mode) in a file with objects to dump (the listFiles dump command parameter), you needed to specify the Configuration ID and a configuration name (dot-separated). | Simplified configuration dump to XML files. |
| Collaboration system. | Now you can block a collaboration system user. A blocked user cannot interact with the collaboration system. Now you can determine a linked infobase user by a collaboration system user. New properties for the CollaborationSystemUser object: IsLocked and InfoBaseUserID. Implemented the GetUsers() method for the collaboration system manager. Standard data processor of collaboration system management supports blocking and unblocking of collaboration system users. | These features were not provided. | New operations with collaboration system users. Now you can disable a user from the collaboration system, for example, if a user is fired. |
| Data display. | New pictures are added to the picture library: ExclamationDialog, QuestionDialog, StopDialog, and InformationDialog. | The listed pictures were not available in the picture library. | The picture library is upgraded. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Dynamic lists. Managed forms. | Typing a text in a form table linked to a dynamic list does not lead to an input focus change and search start if the following conditions are met:
This change is not implemented in version 8.3.14 compatibility mode. | Typing a text in a form table linked to a dynamic list led to an input focus change and search start if the following conditions are met:
| Eliminated unexpected system behavior. |
| Standard functions. | For the Active users standard function, the list update button is moved to the beginning of the list form command bar. | For the Active users standard function, the list update button was located at the end of the list form command bar. | Unified list update command location in various forms of standard functions. |
| Standard functions. Server clusters. | New standard function: Server management. This function is similar to the cluster management console. It requires a server cluster administration server for all servers to be administered. Server operations are carried out using the ServerAdministration object. For a list of functional differences between the standard function and the cluster console, see 1C:Enterprise documentation. The standard function system requirements are the same as the system requirements of the ServerAdministration object. | This feature was not provided. Interactive server cluster administration was available from the cluster management console only. | Interactive server cluster administration is now available not only under Windows. Cluster administration tools are available in the client application using the All functions dialog box. |
| Standard functions. Data history. | Implemented the standard function that allows you to view data history, set an arbitrary filter, and update data history interactively. | Viewing data history of a certain data object only was available in the platform. Custom filter setup to view history was unavailable. | Extended interactive data history operations. |
| Managed forms. Interface. Collaboration system. | Upon form scaling, the scale is shown on a logarithmic scale. 100% value is in the middle of the scale.
New feature: you can click a middle button to:
| Upon form scaling, the scale was shown on a linear scale. 100% value was at the beginning of the scale. You could close search state items (in a dynamic list), remove recipients from context conversations of the collaboration system, and remove attachments from unsent messages of the collaboration system only using the required object control (X in the right part of the item). | Improved application interface usability. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Queries. | New feature: the query language now has optimized calculations of expressions being virtual table parameters. This optimization is similar to optimization of standard query language expressions. This change is not implemented in version 8.3.14 compatibility mode. | The query language did not have optimized calculations of expressions being virtual table parameters. | Eliminated unexpected system behavior. |
| Linux. | Optimized use of RAM on Linux. | RAM was used less effectively on Linux. | Decreased RAM fragmentation and, as a result, decreased the amount of used RAM on Linux. Slightly improved application performance.
|
| Queries. Server clusters. | Optimized execution of a query containing constant values in the selection list. Constant values from the query body are implemented by query parameters. This reduces the amount of plan recompilation in DBMS and, as a result, improves performance of the same queries if only their constant value is different. | This feature was not provided. Constant values were not used by parameters and were used directly in the query body. | Execution time of queries containing constant values is reduced in some cases. In particular, recalculation of register totals can take less time in client/server mode. |
| Managed locks. | Improved performance of the managed lock manager upon transaction completion if there are a lot of transactions that locked the key range of one space. | The managed lock manager spent more time on transaction completion if there were a lot of transactions that locked the key range of one space. | Parallel operation is improved in case of similar load generated by numerous sessions. |
| Configuration comparison and merging. | Optimized comparison/merge of configurations. | Comparison and merge of configurations took more time. | Comparison and merge of configurations is now faster. |
| Queries. | If the query text contains a condition with two constant expressions and each expression is not a string, the condition will be replaced with an expression result before passing the query to DBMS.
This change is not implemented in version 8.3.14 compatibility mode. | Conditions which consisted of constant expressions were not simplified. | In some cases, query performance is improved. |
| Binary data. | Buffers used with objects of the FileStream type are reset only if the FileStream.ResetBuffers() method is executed explicitly. | Buffers used with objects of the FileStream type were reset:
| Decreased load on a disk drive upon intensive operations with the FileStream type objects. |
| Data composition system. | Improved performance of the Value() function of the data composition system expression language. | The Value() function of the data composition system expression language worked more slowly. | Improved performance of the Value() function of the data composition system expression language. |
| DBMS operations. Queries. | Upon query execution, faster creation of a temporary table from a value table passed as a query parameter is available now. | Upon query execution, creation of a temporary table from a value table passed as a query parameter took longer time. | Upgrade: faster creation of a temporary table based on a value table using the query language. |
| Client application installation. System requirements. | Removed Microsoft VC++ Runtime Redistributable Package from thin client distribution package (for Windows). | Microsoft VC++ Runtime Redistributable Package was inside thin client distribution package (for Windows). | Reduced thin client distribution package for Windows. |
| System requirements. | Removed Microsoft Windows Installer 3.0 Package from platform distribution package (for Windows). | Microsoft Windows Installer 3.0 Package was inside platform distribution package (for Windows). | Reduced platform distribution package for Windows. |
| Data composition system. | Composer of data composition system template considers to be used only those fields that are used in the conditional appearance item of data composition only when this conditional appearance item is applied at least to one of the displayed fields (also upon applying conditional appearance to all fields). If conditional appearance item is not applied to any field, used fields are considered to be unused and are not added to the resulting query of the data composition template. Fields, which are not used in conditional appearance, are not added to the data acquisition query. This change is not implemented in version 8.3.14 compatibility mode. | Composer of data composition system template considered to be used all fields in conditional appearance item even if this conditional appearance item was not applied to any field. All fields, which were formally used in conditional appearance, were added to the data acquisition query. | Improved generation of the query of data composition system data acquisition. |
| Queries. | If a query with merges contains a false condition, the part of the merge with the false condition is not passed to DBMS. False conditions are detected only for Number or enumeration data type. Upon merge optimization, the platform can, if necessary, add a requirement for obtaining different records to the resulting query. This change is not implemented in version 8.3.14 compatibility mode. | This feature was not provided. | In some cases, query time will be decreased. |
| Server clusters. | Improved client connection transfer to a new working process upon automatic restart of the working process. | Client connection transfer to a new working process upon automatic restart of the working process took more time. | Transfer of existing sessions to a new working process now takes less time. Decreased (or totally eliminated) client application delay upon transfer. Significantly improved client application operation in interactive mode in this case. |
| Accounting registers. | Improved performance of virtual tables of the accounting register, updated totals upon writing register records, and recalculated accounting register totals. Increased stored data volume and slightly increased record set storage time. To make accounting register performance increase noticeable, disable the compatibility mode. Accounting registers will be restructured. If infobase size exceeds 10 GB, it is recommended that you use optimized tool of database configuration update for restructuring. This change is not implemented in version 8.3.14 compatibility mode. | Operations with virtual tables of accounting register, update of totals upon writing register records, and recalculation of accounting register totals took more time. | Data acquisition from accounting registers is faster now. |
| Accounting registers. Queries. | Improved query to accounting register if the query contains a condition of including the recorder in a list generated under a subquery: Recorder IN (subquery). This change is not implemented in version 8.3.14 compatibility mode. | Query to accounting register if the query contains a condition of including the recorder in a list generated under a subquery: Recorder IN (subquery), poor performance. | Improved data acquisition from the accounting register in some cases. |
| Queries. | If you execute a query in the infobase file mode with data from two tables and these tables are connected with an internal connection and there are indexes of link fields in both tables, then the first iteration is performed for the table with less records. | Number of records in tables was not analyzed upon executing a query in the infobase file mode with data from two tables and these tables were connected with an internal connection and there were indexes of link fields in both tables. | In some cases, improved query performance in the infobase file mode. |
| Data composition system. | Improved generation of data composition system template if a data composition schema query contains a lot of unions (400 or more unions). | Generation of data composition system template took a significant amount of time if a data composition schema query contained a lot of unions (400 or more unions). | Improved performance of the data composition system if there are a lot of unions in a data composition schema query. |
| Server clusters. DBMS operations. | Upgrade for PostgreSQL DBMS: better posting of large documents in the accounting register and improved RecordsWithExtDimensions virtual table. | Posting of large documents in the accounting register and operations with the RecordsWithExtDimensions virtual table took more time if PostgreSQL DBMS was used. | Optimized use of the accounting register if PostgreSQL DBMS is used. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Data composition system. | If a type of one of the operands in a data composition system expression is arbitrary, the resulting expression will also have an arbitrary type. This change is not implemented in version 8.3.14 compatibility mode. | If a value with an arbitrary type was present in a data composition system expression, an arbitrary type was ignored upon calculating the resulting expression time. | Eliminated unexpected system behavior. |
| Interface. | Edited pictures in the client application interface (and in the picture library) for the spreadsheet document commands used for collapsing and expanding all groups. | Pictures in the client application interface (and in the picture library) for the spreadsheet document commands used for collapsing and expanding all groups were different. | Now pictures of the spreadsheet document commands used for collapsing and expanding all groups of the spreadsheet document better correspond to performed actions. |
| Development tools. | In the form editor, the Action property of the adopted form command contains a name of the method, which is a command handler in the extended configuration. Navigation to the command handler is unavailable. | In the form editor, the Action property of the adopted form command contains a name of the method, which is a command handler in the extended configuration. Navigation to the command handler generated an error. | Eliminated unexpected system behavior. |
| Queries. | Query language operation CASE will be considered a constant and replaced with a constant if all operation branches contain only constant expressions. Therefore, operation CASE can be used in constant parameters of virtual tables if all branches of operation CASE contain only constant expressions. If an operand of operation CASE contains NULL in query totals, then the operation result will be a value specified in ELSE or NULL if it is absent. This change is not implemented in version 8.3.14 compatibility mode. | Query language operation CASE was not replaced with a constant and could not be used in constant parameters of virtual tables. Upon calculating operation CASE in query totals, if the operation operand contained NULL, the operation result was NULL. | Eliminated unexpected system behavior. |
| Managed forms. | New feature: you can change properties of client application form items without calling a server:
| This feature was not provided. Accessing the specified properties of client application form items required a server call. | Reduced client/server interaction upon managing a client application form using 1C:Enterprise language. |
| Collaboration system. | Implemented the following features in the collaboration system interface:
Changed the standard user group picture in the drop-down list of user selection. | The collaboration system interface had different behavior:
| Improved collaboration system interface. |
| Data composition system. | Commands Generate, Print, Save, and Compact mode will be added to the report form command bar (with enabled automatic filling) if a property of the report form Report result is set. If a property of the report form Report result is not set, commands Generate, Print, Save, and Compact mode will not be added to the report form command bar, which is filled in automatically. This change is not implemented in version 8.3.14 compatibility mode. | Commands Generate, Print, Save, and Compact mode were always added to the report form command bar with enabled automatic filling. | Eliminated unexpected system behavior. |
| Charts. | If a format is not set explicitly for number presentations in the chart settings, the default format (considering regional infobase settings) will be applied to the numbers. This change is not implemented in version 8.3.14 compatibility mode. | If a format was not specified explicitly for number presentations in the chart settings, no specific formatting was applied to the numbers. | Eliminated unexpected system behavior. |
| Managed forms. | If an input field is in the list selection mode, you can search for the value as follows:
This change is not implemented in version 8.3.14 compatibility mode.
| If the input field was in the list selection mode, search was carried out by the beginning of the line for all types in the specified presentation or if the presentation was not specified, search was carried out in a string value presentation from the selection list. | Now search in input fields, which use a selection list, is more predictable and better meets user expectations. |
| Collaboration system. | New feature: in the collaboration system, you can manage a number of received notifications for context and noncontext conversations. You can disable notifications of a conversation, receive notifications only for the messages to a user, or receive notifications of all messages. This feature can be set up using both user interface and 1C:Enterprise language. Implemented methods GetWatchMode() and SetWatchMode() for noncontext conversations. Implemented the User parameter for the GetWatchMode() and SetWatchMode() methods. Implemented the following methods of the collaboration system manager: SetConversationNotificationRepresentation() and GetConversationNotificationRepresentation(). | Previously, you could only disable all notifications in a collaboration system. The GetWatchMode() and SetWatchMode() methods were used for context conversations only. | Expanded capabilities of the collaboration system interface. |
| Managed locks. Collaboration system. | New feature: now in the client application (thin, thick, and web client), you can unlock object lock set by another user or the same user in another session. An object lock is a lock set interactively upon editing an object in the form or using methods Lock(), LockDataForEdit(), and LockFormDataForEdit(). Now when you find a lock, you can start a conversation with a lock initiator in collaboration system (if the infobase supports the collaboration system). | This feature was not provided. | Simplified operations with infobase data in some cases. |
| Interface. | Implemented the following features for dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox() (in all client applications and Version 8.2 and Taxi interfaces):
| Dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox() had different appearance and did not consider form scale in Taxi interface. | Improved appearance of dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox(). |
| Spreadsheet documents. | Text orientation set for a spreadsheet document cell area is considered upon text output if the Windows system font is selected as a font. This change is not implemented in version 8.3.14 compatibility mode. | If the Windows system font was selected as a font of a spreadsheet document cell area, text orientation set for a spreadsheet document cell area was not considered upon text output. | Eliminated unexpected system behavior. |
| Data composition system. | Now you can apply conditional appearance of a column of a data composition system report table to the entire column if one of the following usage areas is selected for a conditional appearance item: In group, In hierarchical group, or <Everywhere>. This change is not implemented in version 8.3.14 compatibility mode. | If usage area In group, In hierarchical group, or <Everywhere> was selected for a conditional appearance item upon applying appearance of a column of a data composition system report table, appearance could be specified for a table header and column total only. | Eliminated unexpected system behavior. |
| Managed forms. | If a client application form contains one of the following items: a spreadsheet document field, a text document field, a graphical schema field, an HTML document field, a formatted document field, a geographical schema field, or a planner field, a submenu containing Print, Save, and Preview commands is generated in the form title. If there is more than one above-listed item in the form, menu commands are available for the current item of the specified type. Preview command is not displayed in the web client. | This feature was not provided. | Improved form usability. |
| macOS. | Add-ins work correctly in thin client (macOS) and Safari. Add-in revisions are not required. | Add-ins worked incorrectly in Safari but worked correctly in thin client (running under macOS). | Eliminated unexpected system behavior. |
| Queries. | The following query language functions can be used as virtual table parameters that can have constant values only: SUBSTRING(), YEAR(), QUARTER(), MONTH(), DAYOFYEAR(), DAY(), WEEK(), WEEKDAY(), HOUR(), MINUTE(), and SECOND(). You can use them only if all parameters have constant values in the specified functions. In this case, the calculated function value is added as a parameter value. This change is not implemented in version 8.3.14 compatibility mode. | The following query language functions could not be used as virtual table parameters that can have constant values only: SUBSTRING(), YEAR(), QUARTER(), MONTH(), DAYOFYEAR(), DAY(), WEEK(), WEEKDAY(), HOUR(), MINUTE(), and SECOND(). |
Now you can use date/time functions as parameters that can take only constant values, and virtual register tables in the query language. This is possible only if functions have constant values as parameters. |
| Spreadsheet documents. | Now you can edit (both interactively and using 1C:Enterprise language) page parameters of a spreadsheet document converted into compact mode. For a compact spreadsheet document, you can now call the SetHorizontalStretch() method. Upon editing a compact spreadsheet document, both the compact document and the original document are changed. | A compact spreadsheet document did not support setting up page parameters. | Settings of spreadsheet document parameters for print and view are now more convenient. |
| Managed forms. | In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsHorizontalAlign property set to Left, Center, or Auto (which is the same as Left or Center), all last form items or group items, for which the HorizontalAlignInGroup property value is set to Right up to the item, for which the HorizontalAlignInGroup property value is not equal to Right, are aligned right. In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsVerticalAlign property set to Top, Center, or Auto (which is the same as Top or Center), all last form items or group items, for which the VerticalAlignInGroup property value is set to Bottom up to the item, for which the VerticalAlignInGroup property value is not equal to Bottom, are aligned bottom. This upgrade is ignored in 8.3.13 version compatibility mode. | In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsHorizontalAlign property set to Left, Center, or Auto (which is the same as Left or Center), only the last item in a form or a group was aligned right. In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsVerticalAlign property set to Top, Center, or Auto (which is the same as Top or Center), only the last item in a form or a group was aligned bottom. | Eliminated unexpected system behavior. |
| Mobile application builder. | New feature: cleanup of the Mobile application builder cache directory. Artifacts saved to the cache directory more than 30 days ago are deleted. Temporary build directories remaining after unexpected build termination or interruption are also deleted. This does not require setup and is fully automatic. | The Mobile application builder cache could increase in size only. The Mobile application builder did not provide cleanup of unused cached artifacts. | Stopped the uncontrolled growth of the Mobile application builder cache directory. The builder caches only the artifacts used during build for the last 30 days. |
| Full-text search. Server clusters. | The full-text search string cannot contain more than 1,000 words. An error occurs upon excess. Functional words and search operators are not considered when counting the number of words. | The number of words in the full-text search string was not limited. Specifying a very large number of words in the search string could significantly reduce server cluster performance. | Improved application stability. Reduced risk of affecting the application responsiveness as a whole by specifying a very large full-text search string. |
| Database operations. | Enhanced database integrity check upon database configuration update. Several database tables can no longer get the same internal number. In this case, an exception is thrown and the database is not updated. | Upon database configuration update, internal numbers of database tables were not checked for uniqueness. As a result, various unexpected errors could occur when using the information system. | Eliminated unexpected system behavior. |
| File operations. | If thin client connects to the infobase via web server using HTTPS protocol, upon using the GetFile(), GetFiles(), BeginGettingFiles(), BeginGetFileFromServer(), and BeginGetFilesFromServer() methods, reauthentication on the web server is no longer required. | If thin client connected to the infobase via web server using HTTPS protocol, upon using the GetFile(), GetFiles(), BeginGettingFiles(), BeginGetFileFromServer(), and BeginGetFilesFromServer() methods, reauthentication on the web server was required. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Data composition system. | Composer of data composition template does not use the presentation expression specified for the calculated field upon generating an expression of group and total records for calculated fields being resources. Thus, the presentation expression for calculated fields being resources will be displayed in the report in detailed records only. This change is not implemented in version 8.3.14 compatibility mode. | Composer of data composition template used an expression of the calculated field presentation being a resource in detailed, group, and total records. | Behavior of composer of data composition template is the same for calculated fields, data set fields, and calculated resource fields. |
| Queries. Data composition system. | Right joins are not replaced automatically with similar left joins upon processing query text with the query constructor, query scheme, data composition system, and report builder. This change is not implemented in version 8.3.14 compatibility mode. | Right joins were replaced automatically with similar left joins upon processing query text with the query constructor, data composition system, and report builder. If conversion failed to be performed, the connection was removed from the query. | Eliminated system behavior which could lead to an incorrect query. |
| File operations. Web client. | Implemented the BeginGetFileFromServer() and BeginGetFilesFromServer() global context methods. In the interactive mode, methods do not require installing a file system extension on web client. New feature: you can get several files from the server as an archive. The BeginRequestingUserPermission() method allows you to request user permission for new methods. The GetFile(), BeginGettingFiles(), and RequestUserPermission() methods are deprecated and supported for compatibility purposes. It is recommended that you use new methods in the application. | Current methods of receiving files from the server were not logical. Method of receiving several files from the server (BeginGettingFiles()) in the web client required a file system extension. | Getting files from the server is now more transparent and convenient. Now a file system extension is no longer required to use the web client in the interactive mode. |
| File operations. Web client. | Implemented the BeginPutFileToServer() and BeginPutFilesToServer() global context methods. In the interactive mode, the methods do not require installation of a file system extension on web client. New feature: displayed progress of placing a file to the server. New feature: cancel placing a file to the server. New feature: simultaneous transfer of several files from a client computer to the server. Files being transferred are specified using the file search string. The BeginRequestingUserPermission() method allows you to request user permission for new methods. The BeginPutFile(), BeginPuttingFiles(), and RequestUserPermission() methods are deprecated and supported for compatibility purposes. It is recommended that you use new methods in the application. | Existing methods of transferring files to the server (BeginPutFile(), BeginPuttingFiles()) did not allow to cancel placing files during transfer and display the transfer progress. | Putting files to the server is now more transparent and convenient. Now a file system extension is no longer required to use the web client in the interactive mode. |
| Database operations. Common attributes / Data separation. 1C:Enterprise script. | Method FindMarkedForDeletion() will search all available objects of the current data area only if the Undefined value is passed as a value of the first and the second method parameters. This change is not implemented in version 8.3.14 compatibility mode. | Method FindMarkedForDeletion() searched all available objects of the current data area only if the Undefined value was passed as a value of the first method parameter only. | Unified set of parameters and behavior of methods with similar actions. |
| Queries. | Query language behavior changes if: query is a merge of several queries, which are applied to a unified query and each merge query uses the TOP keyword. In this case, each query in the merge turns into a nested query with ordering. If any of the nested query does not have the TOP keyword, subquery is not built by ordering. It is recommended that you analyze when queries that meet these conditions are used. When the compatibility mode is disabled, performance result of such queries can be different from the performance result of this query in compatibility mode. This change is not implemented in version 8.3.14 compatibility mode. | Query language behavior if: query was a merge of several queries, which were applied to a unified query and each merge query used the TOP keyword, depended on the infobase option:
| Implemented similar behavior of a query containing merge, ordering, and the TOP keyword in various infobase mode options. |
| Server clusters. | Upon editing a server cluster resource consumption counter, the counter is reset only if the Group property is changed. Implemented reset of a resource consumption counter instance:
Now you can get a list of resource consumption counter values:
For a resource consumption counter instance, a field containing measurement time is implemented. To get measurement time:
| Upon editing a server cluster resource consumption counter, the counter was reset if any of its properties were changed. Other features were not provided. | Improved administration of server cluster resource consumption. Simplified setting of counters and resource consumption restrictions. Now you can analyze changes of accumulated data. |
| Data composition system. Functional options. | In the data composition system, for the field separated by dot from the temporary table field or nested query, availability check includes checking that the field is not disabled with a functional option. This change is not implemented in version 8.3.14 compatibility mode. | In the data composition system, for the field separated by dot from the temporary table field or nested query, availability check did not include checking that the field is not disabled with a functional option. If a temporary table field or a nested query field was available, it was considered that all fields available via "." (dot) would also be available. | Eliminated unexpected system behavior. |
| Data composition system. Charts of characteristic types. | In the data composition system, a characteristic value type is considered upon getting a characteristic value (for any purpose, for example, sorting or filtering by it). If a value, which does not match the used characteristic value type, is written in the infobase, then NULL will be used instead. It is recommended that you analyze additional characteristics in the data composition system and make sure that the actual characteristic value type matches the type. This change is not implemented in version 8.3.14 compatibility mode. | In the data composition system, a characteristic value type is not considered upon getting a characteristic value (for any purpose, for example, sorting or filtering by it). Even if a value, which does not match the used characteristic value type, is written in the infobase, it will be used. | Improved performance of the data composition system with additional characteristics (charts of characteristic types) by reducing the number of tables used in queries. |
| Server clusters. | Changed rules and settings of 1C:Enterprise server cluster monitoring system. Optimized use of server RAM. In particular, both working process parameters and cluster manager parameters are used when determining the amount of used memory. New feature: server cluster setting, which allows you to specify whether a process dump is to be created when critical memory amount is exceeded. New feature: working server properties that describe a temporarily allowable amount of process memory, a time interval that describes exceeding time of a temporarily allowable amount of process memory, and a critical memory amount. The following settings are removed from the cluster properties:
Settings that describe the amount of working process memory up to which server performance is considered to be sufficient, and the maximum working process memory are removed from the working process properties. However, the removed parameters will be saved in the cluster settings and used in a previous version of 1C:Enterprise. If you create a new cluster, some parameters will have the following default values:
Upon creating a new working server, 256 connections per process will be established by default. If the removed parameters are changed in the cluster settings, it is recommended that you review the cluster settings and adjust them if necessary. Implemented the following objects:
The following Java-based tools are implemented in the administration server interface:
For the cluster service command-line utility (rac):
The following properties are deprecated and supported for compatibility and interaction with previous cluster versions:
| Server cluster monitoring logic was different. Only working process parameters were used when determining the amount of used RAM. Maximum 128 connections per process were offered by default. | Optimized use of RAM by a server cluster. |
| Server clusters. | Upgrade: load balancing upon creating a new connection to the server cluster is updated. Upgrade: the algorithm to assess working process performance is updated. | Load balancing mechanism did not process some situations well enough. In particular, there was non-optimal working process load and load redistribution took a long time. | New connections will use available resources more evenly. Load redistribution among server clusters will be faster. Improved load balancing upon mass connections and disconnections of users to/from the server cluster. |
| Data history. | The version difference form contains information on moved rows in object tabular sections. A row number before and after movement is shown.
After calling the GetVersionDifference() method, the following information will be available for the moved row:
| In the version difference form, the row number after change was adjusted considering actions performed between the first movement and the second movement, and the row number before change contained the row number in the version after change. | Eliminated unexpected system behavior. |
| Data history. | Upon using data history, now you can perform actions once a data version is written. New object manager module event (for objects that support data history): AfterWriteDataHistoryVersionsProcessing. New property available for objects that support data history: WriteDataHistory.AfterWriteDataHistoryProcessing. Use it to manage the need to call the AfterWriteDataHistoryVersionsProcessing event handler. Objects that require processing after writing data history are stored in a special queue. New method available for deleting objects from this queue: DataHistory.DeleteFromAfterWriteVersionsProcessing(). New configuration object property: ExecuteAfterWriteDataHistoryVersionProcessing. Now you can update data history once an object is written. History will be updated by a background job once an object write transaction is complete. New property: WriteDataHistory.UpdateHistoryImmediatelyAfterWrite. New configuration object property: UpdateDataHistoryImmediatelyAfterWrite. New data history manager method: ExecuteAfterWriteVersionsProcessing(). Now you can add new fields and tabular sections to a data history record. Tabular sections can be added only to those objects where metadata has tabular sections. New property: WriteDataHistory.AdditionalData. The GetMetadata() method (by a data version) of the data history manager returns information considering added properties and tabular sections. New methods for the WriteDataHistory object: AddAdditionalData() and AddAdditionalDataFieldPresentation(). Now you can cancel a data history record. New property: WriteDataHistoryParameters.Cancel. Implemented the WriteDataHistory.VersionComment property for a version comment record. The following methods of objects that support data history are deprecated and supported for compatibility purposes only: SetDataHistoryVersionComment() and GetDataHistoryVersionComment(). New parameters available for the UpdateHistory() method (in all syntax options) of the data history manager: ExecuteAfterWriteVersionsProcessing and AutoDeleteFromAfterWriteVersionsProcessing. Implemented manager module for constants. New system background jobs for processing after recording versions and for updating data history after recording. | These features were not provided. | Extended data history features. |
| Queries. Data composition system. | If the LIKE operation is used in the query language (also upon calculating a function in the TOTALS sentence) or the data composition system expression language in the infobase file mode, a special character specified inside the brackets using the ESCAPE keyword, works correctly. This change is not implemented in version 8.3.14 compatibility mode. | If the LIKE operation was used in the query language (also upon calculating a function in the TOTALS sentence) or the data composition system expression language in the infobase file mode, a special character specified using the ESCAPE keyword did not function inside the brackets. | Eliminated unexpected system behavior. |
| File infobase Queries. | In the file infobase, an addition operation and a subtraction operation of the query language are changed. Upon calculating length and precision of an operation type, preference is given to length rather than precision if the total length of 38 characters is exceeded. Therefore, if two numeric fields, the first of which has 20 characters and 0 precision and the second of which has 30 characters and 20 precision, are added together or subtracted, the resulting length will be 38 and the precision will be 18. If the second field contains a number with the last precision digits, the number will be cut by precision digits. Example:
This change is not implemented in version 8.3.14 compatibility mode. | Upon calculating length and precision of an operation type, preference was given to precision rather than length if the total length of 38 characters was exceeded. Therefore, if two numeric fields, the first of which had 20 characters and 0 precision and the second of which had 30 characters and 20 precision, were added together or subtracted, the resulting length would be 38 and the precision would be 20. Because of that, if the first number contained 20 characters in the integral part, a digit overflow error occurred as a result. This would be expressed by a number containing 9 in all parts. Example:
| Eliminated unexpected system behavior. |
| Collaboration system. | New feature: now you can register (and unregister) an infobase in the collaboration system on 1C:Enterprise server. New methods for the collaboration system manager: ExecuteInfoBaseRegistration() and CancelInfoBaseRegistration(). | Earlier, you could register and unregister an infobase in the collaboration system on 1C:Enterprise client only. | Extended administrative actions in the collaboration system. |
| Managed forms. Data composition system. | Upon opening conditional appearance settings (saved in previous platform versions) with disabled compatibility mode, the following conditional appearance parameters of a form or a report will be set to default values:
Changes are applied if values of these conditional appearance parameters are specified as a string and not values of a particular type. We recommend that you analyze where the above mentioned conditional appearance parameters are used and eliminate places where the parameters are set as a string. This change is not implemented in version 8.3.14 compatibility mode. | For some form or report conditional appearance parameters (the DataCompositionAppearance object collection), you could specify values (the DataCompositionParameterValue object) not only as values of particular types but also as a string. These parameters were the following:
You could see the following behavior:
| Eliminated unexpected system behavior. |
| Data composition system. | Upon calculating values of the data composition system fields listed below, the principle is applied: a if value of the resource, from which this field is received, is equal to 0 in the current grouping, the field value is also 0. These fields are the following:
This change is not implemented in version 8.3.14 compatibility mode. | Upon calculating values of the following data composition system fields:
you could see the following behavior: values were always divided by a parent grouping value or grand total, except for cases when the resource value in the grouping was equal to NULL. As a result, an exception could be thrown due to division by 0. | Eliminated unexpected system behavior. |
| Charts. | Upon assigning a new value to the Chart.DataSource property, first, the existing points and series are deleted, and then the new ones are created according to the new data source. After a new value is assigned, the current selection is cleared. We recommend that you remember the current selection before setting new data and restore it if necessary. This change is not implemented in version 8.3.14 compatibility mode. | Upon assigning a new value to the Chart.DataSource property, the existing points and series were not deleted and the selection was not cleared. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile client. Development tools. | In the form editor preview panel, rounded screen corners and displays with a cutout are supported now (for mobile devices on iOS). iPhone models X/XS/XS Max/XR are added to the list of devices for preview in the form editor. | This feature was not provided. | Designing forms for the latest iPhone devices is easier now. |
| Mobile device-specific features. Mobile client. Mobile platform. | Now you can put a stamp on a photo indicating a photo date and time, as well as a custom text. New object: PhotoStamp. Implemented the Stamp parameter of the MultimediaTools.MakePhoto() method. | This feature was not provided. | Expanded photo management capabilities. |
| Mobile device-specific features. Mobile platform. Mobile client. | For mobile applications on Android, the sound is recorded in MPEG4 using AAC codec. For mobile applications on any mobile operating system, the sound is recorded in stereo, the bitrate is 128 kbps, and the sample rate is 44 kHz. The MultimediaTools.MakeAudioRecording() method returns the MultimediaData object where the file extension is set to m4a and the MIME type is set to audio/mp4. | The sound quality and the MultimediaTools.MakeAudioRecording() method result depended on the used operating system:
| Unified audio information recording result on different mobile operating systems. You can listen to a sound recording made in 1C:Enterprise mobile platform using standard tools of operating systems on personal computers. |
| Background and scheduled jobs. Mobile client. | Now you can use the scheduled job dialog on the mobile client. New object available on the mobile client: ScheduledJobDialog. | Editing a schedule for a scheduled job was not available on mobile client. | Now you can edit a schedule for a scheduled job on mobile client. |
| Mobile client. Mobile application builder. | In mobile client, you can add an infobase to the list by scanning a QR code. This feature is available if the mobile client application is permitted to add an infobase with a custom address. This feature is also available in mobile version for developers. In mobile application builder, you can allow users to add infobases using QR codes. In addresses related to schema e1c://, you can use the following commands:
| This feature was not provided. | Advanced features for adding infobases to the list in mobile client or mobile platform. Simplified procedure of adding infobases. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Database copies. | Initial population of a database copy is faster now if source data includes documents generating records in registers and containing a large number of rows in tabular sections. | Initial population of a database copy took more time if source data included documents generating records in registers and containing a large number of rows in tabular sections. | Upgrade: faster initial population of a database copy. |
| Collaboration system. | On overriding the selection list of collaboration system users, on creating a context conversation message, the need to disable a user notification (displayed in the user interface as No notification) is passed as a special value of the ChoiceData parameter of the CollaborationSystemUserAutoComplete data processor. A special value can be created using the constructor of the CollaborationSystemUserID object without specifying a collaboration system user ID. The Undefined value is no longer allowed as a value of the ChoiceData parameter of the CollaborationSystemUserID data processor. | On overriding the list of selecting collaboration system users, on creating a context conversation message, the need to disable a user notification (displayed in the user interface as No notification) was passed as the Undefined value, which prevented distinguishing notification disable and closing the user selection form without any choice. | Eliminated unexpected system behavior. |
| Managed locks. | In client/server mode, a pessimistic object lock will be unconditionally released by the server cluster if the following conditions are met:
| In client/server mode, an attempt to release a pessimistic object lock resulted in the message stating that editing was not possible if the following conditions were met:
| Eliminated unexpected system behavior. |
| Server clusters. | Improved failover cluster reliability. | Failover cluster was unreliable. | Improved failover cluster reliability. |
| Mobile client. Mobile platform. Mobile application builder. | 1C:Enterprise mobile platform running Android now supports 64-bit processors.Mobile application builder creates 4 versions of application that targets Android upon building:
You can now publish 64-bit applications in Google Play. Changed files in the following mobile version distribution archive: mobile.zip. | Mobile platform 1C:Enterprise running Android supported 32-bit processors only. Mobile application builder could not build and publish 64-bit mobile application versions in Google Play. | Expanded list of supported processor architectures for a mobile version running Android. Built mobile applications running Android are larger now. Built mobile applications running Android now perform faster. |
| Mobile platform. Mobile client. Mobile application builder. | Some single mobile application permissions were replaced by multiple permissions in order to meet requirements of application store owners.
The Telephony permission is replaced with: Dialing Read the phone log Call handling Automatically send text messages Get text messages Text message log. The Media permission is replaced with: Camera Microphone Music library Picture and video library Audio and video playback. New permissions are grouped by purpose and functional cohesion. Configurations exported by version 8.3.14 or earlier versions cannot be built using mobile version 8.3.15 or higher. The reverse is also true. | Mobile application permissions had a different composition. | Mobile application permissions include changed requirements of application store owners. |
| Mobile platform. Mobile client. Mobile application builder. | In Designer, you can now edit request bodies of permissions that are required by the mobile application. Request bodies of permissions that have an applied meaning for the user are editable. Mobile application builder allows you to build mobile applications that contain both configurations with the specified permission request bodies and configurations without them (exported in previous 1C:Enterprise platform versions). | Permission request bodies were not editable in Designer. | You can now specify permission request bodies that meet the mobile application requirements as accurately as possible. |
| Mobile platform. Mobile client. Global search. | Upgrade: global search is now available in 1C:Enterprise mobile version. | This feature was not supported in the mobile version. | Upgrade: 1C:Enterprise mobile version now has the features that were implemented earlier in 1C:Enterprise version for a personal computer. |
| Development tools. | Implemented the following changes in Syntax Assistant:
Regardless of the state of the Display deprecated objects setting check box, search using Ctrl+F1 always results in information about a Syntax Assistant object being displayed. Addition version information is filled in for all objects of Syntax Assistant. Deletion version information is filled in for all objects of Syntax Assistant. Objects recommended for replacement are filled in only if the object was declared deprecated in version 8.3.14 and above. Specified changes in Syntax Assistant are valid starting from version 8.3.15 and above. | Syntax Assistant did not have any information about object versions (of addition, depreciation, or change) and objects that are recommended for usage instead of the deprecated ones. Deprecated objects were deleted from Syntax Assistant. It was impossible to access such objects. | Syntax Assistant became more informative and useful for developers. |
| Mobile platform. Mobile client. Mobile device-specific features. | You can now use additional authentication to access mobile application features. Authentication is done by the used mobile operating system and includes authentication using biometrics (a fingerprint, face recognition, or iris recognition) or a password (pattern lock and so on). New global context property: AdditionalUserValidation. Upgrade: safe storage of confidential information on a user mobile device. Information is protected by the mobile operating system. You can now manage the need for additional authentication to access confidential information. New global context property: SecureStore. | These features were not provided. | Added functionality of 1C:Enterprise mobile version for additional user authentication and confidential information storage. |
| Mobile client. | Biometric authentication for simplified login to the application is now available in the mobile client. Use biometrics check box should be enabled on the mobile devices that support biometric authentication, in the mobile client infobase properties, and in the dialog boxes for entering the username and password generated by the mobile client. | This feature was not provided. | Authentication to an application on devices that support biometric authentication can now be simplified. |
| Client application installation. | Windows client application installer now supports Vietnamese language. | The Windows client application installer did not support Vietnamese. | Eliminated unexpected system behavior. |
| Data history. | Implemented the following features for standard Data history processor:
These features are available from the data processor form using the More - Data history management command. | These features were not provided. | The standard data processor supports new features of the data history component previously implemented in the platform. |
| Collaboration system. Client application form. | When calling the BeginGetConversation() form method, a context conversation is created if the resulting context conversation is missing by the time the method is called. | When calling the BeginGetConversation() form method, the context conversation was not created. | When calling the BeginGetConversation() form method, a context conversation is automatically created if it was not created before.. |
| Documentation. | The documents state that 1C:Enterprise can operate with clusters that are created using PostgreSQL DBMS versions listed in the system requirements for the platform. | The list of PostgreSQL DBMS versions using which a cluster is created to operate with 1C:Enterprise was specified incorrectly. | Fixed the error in the documents. |
| Server clusters. | Optimized the final step of load balancing algorithm (in the selection mode with a performance priority) when the workflows selected in the previous steps differ in available performance. | The documents did not contain information on configuring web servers for the correct operation of the background jobs feature in the file infobase. | Optimized load balancing algorithm in a server cluster. |
| Web client, web service, and HTTP service publishing tools. | The documents contain information on configuring web servers for the correct background jobs feature operation in the file infobase. | The documents did not contain information on configuring web servers for the correct operation of the background jobs feature in the file infobase. | Updated platform documents. |
| File operations. | When using the BeginPutFile()/BeginPuttingFiles() methods, the downloaded file(s) are split into parts and the transfer to the server is performed in parts. As a result, the user interface remains operational. Also implemented the option to start putting new files, even if the previously started putting of files is not yet complete. | When using the BeginPutFile()/BeginPuttingFiles() methods, the uploaded file/files were transferred fully. The client application did not respond to user actions during the transfer. It was impossible to start putting a new file until the previously started putting of one or more files was completed. | Eliminated unexpected system behavior. |
| Calculation registers. Applied objects. | Implemented the feature to include sequences and recalculations in the common attributes. This change is not implemented in version 8.3.14 compatibility mode. | This feature was not provided. | Expanded the structure of configuration objects, which may be part of common attributes. |
| Software licensing. | Starting the client application and Designer on PCs running on Linux or macOS when using basic configurations has been accelerated for cases, when the PC has a large number of disk partitions or processor cores. The list of key hardware parameters used when activating the base software license on Linux and macOS is aligned with the list of key parameters in Windows. | Starting the client application and Designer on PCs running Linux and macOS when using basic configurations when the PC had a large number of disk partitions or processor cores took a long time. The list of key hardware parameters used when activating the base software license on Linux and macOS was different from the list of key parameters in Windows. | Starting the client application and Designer when using the basic configuration in Linux and macOS has been accelerated. |
| Mobile client. | The TextDocument object is now available in mobile client. | The TextDocument object was not available in mobile client. | Added new mobile client features. |
| Server clusters. | The Critical amount of process memory, Temporarily allowed amount of process memory, and Period of exceeding the process memory threshold parameters can be changed with a PROF license. However, these parameters only affect the restart of processes. The effect of these parameters on the server calls interruption is only supported for CORP licenses. If the server is running with a PROF license, the limit memory size, after which the client’s server call is interrupted, is defined as 80% of the physical memory of the computer, regardless of the Temporarily allowed amount of process memory parameter value. | The Critical amount of process memory, Temporarily allowed amount of process memory, and Period of exceeding the process memory threshold parameters could only be changed with a CORP license. | Restarting the working processes depending on the amount of RAM used is now possible for a server cluster running PROF license. |
| Client application form. Interface. | Alt+L shortcut is now used for the Search everywhere command of the form elements context menu. | Ctrl+Shift+C shortcut was used for the Search everywhere command of the form elements context menu. | Fixed the conflict between the platform feature keyboard shortcut and the established keyboard shortcuts of typical applications. |
| Interface. | The form menu is added in the Taxi interface. It is called by the three dots button, located in the top right section of the form (except for the dialog boxes generated by the Question(), ShowQuestion(), Warning() and ShowWarning() methods). The home page displays a single form menu. The form menu items depend on the current (active) form element:
The following changes have been made to the Service and Settings menu:
Clipboard commands for numbers (put in the clipboard, add to/subtract from the clipboard) can be displayed in the main application window or in the auxiliary application window title. To enable/disable these commands, use the Show, M, M+, M- command in the Service and Settings menu. Alt+F keyboard shortcut opens the advanced search dialog box in the form table that displays a dynamic list. | There was no form menu. Form menu commands were located in the Service and Settings menu. | Improved navigation in the application. |
| Full-text search. | Fixed the problem of searching for words ending in "*" using full-text search. If the platform can detect that the current full-text search index is incorrect, it will automatically delete it. We recommend to clear and rebuild the full-text search index when upgrading to version 8.3.15. | Searching words ending in "*" using full-text search was not available. | Eliminated unexpected system behavior. |
| Administration tools. | The 1C:Enterprise distribution package now includes files that enable the installer operation on Windows XP (the names of such files have the _xp suffix). The 1C:Enterprise installers now use the UTF-8 encoding on Windows. The 1C:Enterprise installer on Windows XP use the ANSI encoding. The 1C:Enterprise installer on Windows XP does not support Vietnamese language. Provided that Windows XP is not used, we recommend to exclude the files of distribution package for Windows XP when updating the 1C:Enterprise through web server. | The 1C:Enterprise installer could display some national symbols incorrectly on Windows XP. | There is now a separate distribution package for obsolete Windows XP. |
| Spreadsheet documents. | Search control commands are now available in the More menu of the report form and the spreadsheet document form. Commands for working with table and editing commands are no longer available in the More menu of a spreadsheet document. | Search control commands were only available in the report form and spreadsheet document menu. Commands for working with table and editing commands were available in the More menu of a spreadsheet document form. The same commands were available in the form menu. | The distribution of commands between the form menu and the More menu in the report and spreadsheet document forms has become more logical and understandable. |
| Interface. | Save and print settings commands are no longer available in the Service and Settings - File menu. | Save and print settings commands were available in the Service and Settings - File menu. | Removed duplication of commands in various application menus. |
| Interface. | Zoom command was moved to the form menu. | Zoom command was available in Service and Settings menu. | The form context command is now available in the form directly. |
| Administration tools. | The system integrity control utility is implemented by making calculating the hash function of files through the SHA-256 and GOST R 31.11-2012 (512 bit) algorithms possible. In the make utility's operating mode the --method parameter is implemented. Now you can specify the algorithm used in the hash function calculation.
| To calculate the hash function of the files, the system integrity control utility was using the SHA-1 algorithm. | Now you can use stronger algorithms to calculate the hash functions. |
| Data history. | The data history update is now performed faster (with the DataHistory.UpdateHistory() method) in case there is a large number of versions that need to be transferred to the data history. | The data history update (with the DataHistory.UpdateHistory() method) took a very long time in case there is a large number of versions in the system that need to be transferred to the data history. | Data history update is improved. The data history can be updated in the background. |
| Full-text search. | Reduced the time of the full-text search index generation. Reduced disk space requirements of the full-text search index. If you enter a search string consisting of one or two chars and the "*" substitution char (any sequence of chars), an error may occur with the suggestion to refine the search string (if the search result is large). | Full-text search index generation took more time. The index required more disk space. If you entered a search string consisting of one or two chars and the "*" substitution char (any sequence of chars), an error with the suggestion to refine the search string (if the search result is large) did not occurr. | The full-text search index generation is now faster. Reduced disk space requirements of the full-text search index. |
| Database configuration update. | Restructuring of the database table will not be performed if all the following conditions are met:
If all the above-mentioned conditions are met, the optimized restructuring mechanism will only process the actual changes (if possible) without the complete restructuring of the database table. The non-optimized infobase restructuring mechanism performed the complete database restructuring after any changes made in the configuration object metadata. | The database table was restructured if all the following conditions were met simultaneously:
| In some cases the optimized mechanism of restructuring will update the database tables much faster than the previous one. |
| Technological log. | The description of CLSTR event properties was updated in the documentation. | The documentation contained an obsolete CLSTR event properties description. | Documentation was updated. |
| Client application form. Command interface. | Added the following buttons to the client application form header: Save, Print, and Print Preview. These buttons and the File form submenu are displayed if there is at least one visible form field of the following types:
Save and print commands are available if there is at least one form field of one of above-mentioned types that supports these commands. The form menu can now be called by pressing Alt + -. | The Save, Print, and Print Preview commands were displayed in the system command bar and in the main menu. These commands were available if the current form item or a single visible form item supported these commands and was of one of the following types:
| Simplified interaction with the form items that support save and print options. |
| Mobile platform. Mobile client. System requirements. | The iOs 7.x versions are no longer supported. The earliest supported iOS version is 8.0. | The iOS 7.x versions were supported. | Ended support for legacy iOS versions. Apple iPhone 4 is no longer supported. |
| Configuration extensions. | Base configurations can now use extensions. The extension and the base configuration must be signed with the same key. Added the /SignCfg command for Designer batch mode. Added the sign-cfg parameter of the config mode for Designer agent mode. | Extensions were not supported by the base configurations. | Base configurations developers can now release configuration fixes using extensions. |
| Web client, web service, and HTTP service publishing tools. | You cannot publish the web service on Apache web server if the web server bitness does not match the Designer bitness. | During the web service publication there was no check that Apache web server bitness match the Designer bitness. | There are less unexpected errors during the publication caused by the Apache web server bitness and the Designer bitness mismatch. |
| Administration tools. | You can now update your client application through a web server with the PROF license. | CORP license was required to update the client application through a web server. | Simplified the update of client applications through a web server. |
| Server clusters. | Now the cluster monitoring system analyzes both memory usage settings specified in the cluster settings and memory space occupied by every working process:
The cluster mechanisms that use data on available RAM consider changes made to the RAM size while the computer is operating. For example, if you change parameters of the virtual machine where the server cluster runs. | The cluster monitoring system did not analyze memory space occupied by every working process. The cluster mechanisms that used data on available RAM relied on RAM data that was retrieved once upon the cluster start. | Improved server cluster stability if the 32-bit 1C:Enterprise server cluster runs 64-bit operating systems. |
| Spreadsheet documents. | Spreadsheet documents created in 1C:Enterprise v8.3.17 are supported. | Spreadsheet documents created in 1C:Enterprise v8.3.17 were not supported. | Eliminated unexpected system behavior. |
| Pictures. | Multipage TIFF files are supported. New methods: Picture.FramesNumber() and PictureToProcess.GetPictures(). New picture constructor for the PictureToProcess object, which takes an array of pictures as the argument and the resulting picture format as the parameter. New parameters for the PictureToProcess object: Frames and Format. Implemented the CurrentFrameNumber property and the FramesNumber() method for the form field extension of the client application for a picture. | Only the first frame of a multipage TIFF file could be unloaded. | Multipage TIFF files are supported. |
| Client application. Administration tools. | In the dialog box where you enter your username or password, you can now place hyperlinks to navigate to the help page and recover your password. You can recover your password on the website, via email, or using the OpenID provider tools. New feature: each infobase user can recover their password. A configured system does not require human involvement to recover the user password. New properties for the InfobaseUser object: EmailAddress and CannotRecoverPassword. New global context property: AdditionalAuthenticationSettings. Implemented the following event log events: Session. Attempting to recover the password, Session. An error occurred while attempting to recover the password, Infobase. Changing additional authentication settings, Infobase. An error occurred while changing additional authentication settings. | The user password could be recovered with infobase administrator involvement only. | Now it is easier for a user to recover their password. Password recovery no longer requires direct administrator involvement. |
| Dynamic lists. Data composition system. | Eliminated the error restoring data composition system settings and dynamic list settings when the settings were saved in version 8.3.16 or later but configuration compatibility mode was set to Version 8.3.15. | If configuration compatibility mode was set to Version 8.3.15 and data composition system settings or dynamic list settings were saved in platform version 8.3.16 or later, it was not possible to restore the settings. | Eliminated unexpected system behavior. |
| Client application. Client application installation. Administration tools. | You can now distribute the client application via the web server using web server extensions, without configuring the default.vrd file. The client application distribution package will be searched in the distr directory of the version whose web server extension is running on the web server. Implemented new versions of client application distribution packages that can be installed in addition to the full-fledged distribution package of 1C:Enterprise and contain packaged distribution packages of client applications. This option for delivering client applications is supported only for Windows and macOS | This feature was not provided. The client application distribution package could be obtained from the web server only after the default.vrd file was configured correctly. | It is now easier to configure distribution of client application distribution packages when updating the 1C:Enterprise system version. |
Version 8.3.14 includes known bug fixes and functionality modifications.
Improved database configuration update mechanism graduated out of beta.
Windows-based 64-bit client application (thin client, thick client, and Designer) graduated out of beta.
The mobile client has graduated out of beta.
The Windows-compatible mobile platform has graduated out of beta.
Thin client for macOS graduated out of beta. Thick client and Designer for macOS are still in beta testing.
The term "managed application" is replaced with the term "client application." Unless necessary, the term "managed" is no longer used in V8Update file, help files, and documentation. For example, "managed application" is replaced with "client application" and "managed form input field extension" is replaced with "form input field extension." The renaming is applied to related UI texts in client applications and Designer.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.13 is now implemented. | Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.12 was implemented. | Configurations developed using 1C:Enterprise platform version 8.3.13 or earlier can run on version 8.3.14 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.14 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.13 after the migration to version 8.3.14, even if you have disabled the compatibility mode (simply enable it again). |
| Server clusters. | New standalone 1C:Enterprise server. It can handle client applications that operate an infobase over HTTP protocol. The standalone server provides HTTP connection, the web-server is no longer required. The standalone server uses computer resources more efficiently. A single instance of the standalone server provides access to a singe infobase. The standalone server does not support the Designer mode. You can operate the standalone server by the command-line utility. The standalone server supports both file and client/server mode of infobase. It can handle up to 3 client applications in file mode (without sessions of background jobs, web-services etc.) without server license. It requires a server license of any type in other cases. The standalone server has some limited functionality. For more info see documentation. The standalone server provides some inbound administrative tools. This feature is provided solely for beta testing purpose. | This feature was not provided. | The new 1C:Enterprise architecture improves the stability and effectiveness of server operations. |
| Database copies. Server clusters. DBMS operations. | Copies of tables that can intensify the DBMS load when used in reports or queries now can be stored in an external database (external to the 1C:Enterprise database). The feature is supported only in client/server mode. You can define which database will be addressed by a specific report or query. Table copies can be stored in a DBMS of any supported type. The server cluster DBMS type can differ from a database copy DBMS type. The synchronization between the server cluster database and a database copy can be carried out by the means of DBMS or 1C:Enterprise. New global context property: DatabaseCopies. New Query object properties: RequiredDataRelevance and RequiredDataRelevanceTime. New QueryResult object properties: DataIsRelevant, DataRelevanceTime, and DatabaseCopy. New DataCompositionOutputParameterValues object properties: RequiredDataRelevance, RequiredDataRelevanceTime, DataRelevanceOutput, and DatabaseCopyOutput. New functions of the data composition system expression language: DataIsRelevant(), DataRelevanceTime(), and DatabaseCopy(). New system background jobs: Initial population of a database copy and Database copy notification handler. New cluster services: Database copy service and Database copy time service. New standard function: Database copy management. New technological log event: <DBCOPIES>. The database copy feature requires a CORP license. This feature is provided solely for beta testing purpose. | This feature was not provided. | New feature: infobase load can be distributed among a few physical DBMS. For example, the main database can process all document entries, and the database copies can process reports and queries that significantly affect the database performance. |
| Server clusters. System requirements. | New feature: the accelerator of analytical report generation (Data accelerator). It is possible due to a new server cluster service, which acts as a database stored in RAM. Data accelerator is based on the database copy engine. New server cluster service: Data accelerator service. Data accelerator runs only on 64-bit operating systems. It does not support Windows XP and Windows Vista. The database copy feature requires a CORP license. This feature is provided solely for beta testing purpose. The Data accelerator service requires a beta testing license. It is not available without a beta testing license. | This feature was not provided. | The generation time of complicated analytical reports is significantly reduced. |
| Collaboration system. | The collaboration system supports file operations. Collaboration system servers support the following file storages: Amazon S3, Google Cloud and other storages based on Amazon S3 protocol. The following limitations can be set on collaboration system servers:
New property: CollaborationSystemMessage.Attachments. New collaboration system methods: AttachmentsSupported(), AttachCommandsGenerationHandler(), and DetachCommandsGenerationHandler(). | This feature was not provided. | Expanded collaboration system capabilities. |
| Collaboration system. | Upgrade: more than two people can join a video conference. Participants can join and leave a conference at any moment. Upgrade: it is possible to establish video conferences between 1C:Enterprise 8.3.13 and 8.3.14. In this case, only one-on-one video conference is possible. | This feature was not provided. Only video calls (one-on-one video conferences) were possible. | Expanded collaboration system capabilities. |
| Development tools. | New features for Designer agent mode (similar to the features provided by Designer command line):
New features for Designer agent mode (not available in other modes):
New feature: show status of time-consuming operations in agent mode (for some commands). Upgrade: more errors are described by specific code in error-type field. Upgrade: messages returned after a command execution in agent mode contain more details. | These features were not provided. | New features for Designer in agent mode. |
| Server clusters. Administration tools. | New feature: you can administer server clusters using 1C:Enterprise language. The administration is based on ras server, without using COM technology. The cluster supports servers with 1C:Enterprise versions different from the client application version. The administration tools are available from the thin client and from the server. New object: ServerAdministration. | This feature was not provided. Server cluster administration was available from 1C:Enterprise language only over COM connections on a server running on Windows. Server administration required a 1C:Enterprise version identical to the server version. | You can implement cross-platform administration interfaces for 1C:Enterprise server clusters with the client application version different from the server cluster version. You can implement cluster consoles for Linux. It is not necessary to use the cluster console that requires Microsoft Management Console. |
| Data display. | New feature: number-noun agreement. New global context method: GetStringDeclensionsByNumber(). | This feature was not provided. | Generating sentences with numbers (in words or figures) is more convenient. |
| Common objects. | New feature: solving systems of linear equations. New object: SolvingLinearEquationsSystems | This feature was not provided. | Solving large systems of linear equations takes less time. |
| Data display. | New picture added to the picture library: Attach. | The picture was not available in the library. | The picture library is upgraded. |
| Configuration extensions. | New feature: an adopted enumeration value set can be extended. When an extension with an extended enumeration value set is deleted, the infobase object attributes that stored the deleted values take a blank reference to the enumeration as their values. | This feature was not provided. | Enumeration management is upgraded. |
| Configuration extensions. | New property for metadata objects adopted to extensions: Comment. The property is intended solely for developers and ignored when building the final configuration or during extension applicability tests. | This feature was not provided. | Developers can describe the purpose of extension objects using built-in means. |
| Configuration extensions. Common objects. | You can create native session parameters in a configuration extension. They can be included in access restriction text. | This feature was not provided. | Extended configuration extension options. |
| Calculation registers. | New feature: you can get the effective period of a calculation register record set before the set is written. New method for calculation register record sets: GetAdjustedEffectivePeriod(). | The effective period could be calculated only after a calculation register record set was written. | Due to reducing the number of writing operations, parallel register calculations and performance are improved in certain scenarios. |
| Server clusters. | New filters for resource consumption counters: by safe mode and by security profile. New comparison operator for filtering resource consumption counters: inequality. New resource consumption counter filter feature: a number of conditions with the same filter type can be combined using the AND operator. | These features were not provided. | Advanced performance analysis for applications running in client/server mode. |
| Data composition system. | The data composition system can display pictures stored in the infobase. Reports can include both pictures specified as URLs and pictures stored in attributes of ValueStorage type. New properties of DataCompositionAppearance and DataCompositionAreaTemplateTableCellAppearance objects: PictureOutput, PictureSize, TextPositionRelativeToPicture, PictureHorizontalAlign, and PictureVerticalAlign. The default behavior is not changed in Version 8.3.13 compatibility mode. | The data composition system did not provide means for displaying pictures stored in the infobase. | New formatting options for the data composition system. |
| Charts. | New feature: editing sets of chart series and points. New methods for ChartPoints and ChartSeriesCollection objects: Insert(), Move(), Delete(), and Clear(). | This feature was not provided. To edit a point or value, one had to refill all chart data. | New chart features. For example, you can create autoscrolling charts where the first point of a chart is removed and the last one is added with a certain period. |
| Client application. | Batch mode is implemented for the thin and thick clients. The batch mode is available from the start of a client application till the completion of the BeforeStart handler in the application module. Then the batch mode is turned off automatically. The batch mode suppresses all system dialog boxes. The /DisableStartupDialogs command-line option switches a client application to the batch mode. For more information about the batch mode, see 1C:Enterprise documentation. New global context method: ProhibitFormOpening(). You can add the option that enables batch mode to client application startup parameters in Designer. Runtime errors in the RunApp() or BeginRunningApplication() method generate exceptions in batch mode. | This feature was not provided. Only Designer supported the batch mode. Runtime errors in the RunApp() or BeginRunningApplication() method generated dialog boxes with error descriptions on the server. | Client application startup scenarios where you can suppress opening dialog boxes that normally block programmatic handling of startup issues are now possible. |
| System requirements. | New feature: software license for beta testing. The license is complementary to 1C:Enterprise server license. Beta testing license cannot replace a 1C:Enterprise server licence. The number of beta testing licenses must be equal to or greater than the number of server licenses for the server cluster that runs the tests. If a new feature requires a beta testing license, it is mentioned in the feature announcement. To apply for a beta testing license, send your request to betaplatform@1c.ru. Licensing utility now supports feature testing licenses. | Feature beta testing did not require special licenses. | In some cases, feature beta testing requires beta testing licenses. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Web client. | The web client does not support configurations with Version 8.2 interface. The web client does not support switching between Version 8.2 and Taxi interfaces. Command-line options itdi and itaxi are ignored. The options are considered obsolete and not recommended for use. Regardless of the value of the ClientSettings.ClientApplicationInterfaceVariant property, the Taxi interface is used. | The web client supported Version 8.2 interface. | Support of obsolete client application interface type is discontinued. Web client stability is improved. |
| Collaboration system. | Upgrade: a user can separately turn off the camera or microphone during a video call. | When a user turned off the camera during a video call, the microphone turned off automatically. | Eliminated unexpected system behavior. |
| Command interface. | Upgrade: if a section or command interface command has a help topic, its tooltip does not contain the "Help" hyperlink. The help topics are still available from the help window. In the current section functions panel and the functions menu, lists and configuration objects have tooltips with their explanations or extended presentations. | The tooltip behavior was as follows:
| Faster command interface displaying in the thin client. Standardized view of section and command tooltips in different client applications |
| Configuration extensions. Web client. | In the web client, if an infobase contains extensions, browsers cache pictures according to the following rules:
| In the web client, if an infobase contains extensions, browsers cached all configuration pictures for each session. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Charts. | Upgrade: improved performance of charts that contain large data sets. We recommend that you analyze charts in your applications and refactor them as follows:
| Inefficient performance of charts that contained large data sets. | Improved performance of charts that contain large data sets. |
| Administration tools. | Upgrade: the user list in Designer opens faster. The improvement is noticeable if the list contains many users and roles. | In an infobase that contained many users and roles, the user list opened slowly. | The user list opens faster. |
| Accounting registers. Accumulation registers. | Upgrade: faster totals recalculation for accounting registers and accumulation registers in the following cases:
| Totals recalculation for accounting registers and accumulation registers took a significant amount of time. | Totals recalculation for accounting registers and accumulation registers takes less time. |
| Full-text search. | Upgrade: faster search for expressions like "word*" when an application has many instances of "word". Upgrade: exceeding search word threshold is less likely for expressions like "word*". This upgrade is ignored in 8.3.13 version compatibility mode. | Search for expressions like "word*" could fail due to exceeding search word threshold error. | Optimization of full-text search. |
| DBMS operations. | Upgrade: faster restructuring of infobases based on Microsoft SQL Server and IBM Db2. | Restructuring of infobases based on Microsoft SQL Server and IBM Db2 took more time. | Faster restructuring of infobases based on Microsoft SQL Server and IBM Db2. |
| DBMS operations. | Upgrade: simultaneous release of a number of connections with Microsoft SQL Server is less likely, which improves TempDB performance. | There was a possibility of simultaneous release of a number of connections with Microsoft SQL Server, which significantly reduced TempDB performance. | Optimized operation of TempDB on Microsoft SQL Server. |
| Calculation registers. | New feature: clustered index by recorder for calculation registers. An index is rebuilt during calculation register restructuring or during Verify and repair operation. Upon deleting records from an effective period table, if there is no filter by register dimensions, the deletion query does not require establishing connection to the main register table. | Clustered index was not available for calculation registers. Upon deleting records from an effective period table, if there was no filter by register dimensions, the deletion query always established connection to the main register table. | Reduced possibility of table lock upon deleting calculation register effective period records. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client applications. | New feature: the thin client (connected over HTTP/HTTPS) supports all OpenID authentication providers that support OpenID Connect protocol. | This feature was not provided. Only the web client supported such OpenID authentication providers. | New user authentication option for the thin client. |
| Client application. | New feature: user authentication with Unified System for Identification and Authentication (USIA) in the web client or thin client (connected over HTTP/HTTPS). New properties in OpenID Connect provider description in the default.vrd file (the <providers> element): dialect and crypto. In the thin client, authentication with USIA is possible only if the infobase is published on an Apache web server. | This feature was not provided. | New user authentication option. |
| Queries. Data composition system. | New feature: when managing queries with the QuerySchema object, you can use the query language extension for the data composition system. New property: QuerySchema.DataCompositionMode. New properties for the QuerySchemaSelectQuery object: DataCompositionSelectionFields and Characteristics. New property: QuerySchemaSelectOperator.DataCompositionFilterExpression. New property: QuerySchemaTable.DataCompositionParameters. New feature: query wizard in 1C:Enterprise mode supports the query language extension for the data composition system. New property: QueryWizard.DataCompositionMode. | The QuerySchema object did not support the query extension for the data composition system. Query wizard in 1C:Enterprise mode did not support the query language extension for the data composition system. | New features for queries in 1C:Enterprise mode related to the extension for the data composition system. |
| Server clusters. | Upgrade: on cluster manager crash the details of the running and completed background jobs are saved. Scheduled jobs starting and processing is not interrupted. | Cluster manager crash caused the following:
| Improved fault tolerance of server cluster operations related to background and scheduled jobs. Users of applications that run background or scheduled jobs do not notice cluster manager crashes. |
| Dynamic lists. | New feature: you can specify fields that will be used as selection key fields. New properties for the DynamicList object: KeyType and KeyFields. New object: DynamicListRowKey. New feature: dynamic list query settings dialog box allows customization of the fields that form row keys. This feature is ignored in 8.3.7 version compatibility mode. We recommend that you revise all dynamic lists (excluding RecordsWithExtDimensions, TasksByPerformer, filter criterion, and information register slice tables) with no main table specified or where the main table is a virtual table without a key toward using keys of Field value or Row key types. | This feature was not provided. Key fields were defined by the main dynamic list table. | New feature for dynamic lists with no main table. Improved performance of dynamic lists with no main table. For example, now such dynamic lists support groupings. |
| Development tools. | New feature: in Designer agent mode, names of user working directories contain numeric codes. The directory–user mapping is stored in agentbasedir.json file located in the agent working directory (the AgentBaseDir command-line option). | In Designer agent mode, names of user working directories contained the usernames. | Working directory names do not reveal the names of the users that work in Designer agent mode. Shorter paths to user working directories. |
| Configuration extensions. | Upgrade: when a form is adopted by an extension, only form items are adopted. After adoption, you can edit all item properties from an extension using the form editor. By default, other form objects (such as attributes, commands, and parameters) are not adopted, so they are not editable. To edit such objects, you must include them in the extension. When a form is adopted, the parent configuration object of the form is not adopted. The upgrade does not affect the forms adopted to extensions in the previous 1C:Enterprise versions. | When a form was adopted by an extension, the parent configuration object and all the extension objects were adopted. | Managing adopted configuration object forms is more convenient. Adjusting extensions to new configuration versions is more convenient. |
| Charts. Data composition system. | Upgrade: when you print a report, each chart fits one page. Upon printing, the data composition system output processor sets StayWithNext property value to True for the spreadsheet document rows that follow the chart. This upgrade is ignored in 8.3.13 version compatibility mode. | In a printed report, a chart could be ripped by a page break. | Printed reports are more readable. |
| Managed forms. | Upgrade: in the thin, thick, and web clients, a form unlocks objects in one minute after the modification flag is cleared. | In the thin, thick, and web client, a form unlocked objects after the form had been closed. | Parallel operation is improved in some cases. |
| Charts. | The algorithm that calculates the plot area size for a pie chart is revised. It reserves more space for highlighting the sector where the pointer is. This upgrade is ignored in 8.3.13 version compatibility mode. | The plot area of a pie chart occupied all available space. This might cause cropping of the highlighted sector area. | Eliminated unexpected system behavior. |
| Configuration extensions. | Upgrade: when a configuration extension is applied, the number of parameters and Val keyword before event handler parameters are not checked. | When a configuration extension was applied, the number of parameters and Val keyword before event handler parameters were checked. The number of parameters in an extension had to match the number of parameters in an extended configuration. | Extension behavior complies with the platform behavior for the main configuration. Upon an event handler call, the number of parameters is not checked. |
| Data composition system. | Upgrade: upon data composition template generation, a field alias includes the source field alias and the field details (the presentation of the field attribute, the aggregate function, and so on). This upgrade is ignored in 8.3.13 version compatibility mode. | Upon data composition template generation, default query wizard naming rules were applied to create a field alias. | A field content is more transparent by its alias. |
| Pictures. | New feature: support of GIF pictures with "XMP DataXMP" extension. | This feature was not provided. | Extended list of supported picture formats. 1C:Enterprise supports GIF pictures created with Adobe tools. |
| DBMS operations. Technological log. | Upgrade: for PostgreSQL DBMS, the technological log (<plansql> event) keeps query plans for UPDATE, DELETE, and INSERT queries. | For PostgreSQL DBMS, the technological log (<plansql> event) kept query plans only for SELECT queries. | Analyzing applications based on PostgreSQL DBMS is more convenient. |
| Development tools. | Upgrade: upon comparing configuration modules, you can see which methods are unchanged but moved to another preprocessor instruction or region. | Upon comparing configuration modules, methods that were unchanged but moved to another preprocessor instruction or region were displayed as changed, which could be misleading. | Module comparison is more transparent and convenient. |
| Spreadsheet documents. Charts. | When a spreadsheet document is displayed in the edit mode in the thin client, thick client, or Designer, pointing to a chart area opens its properties. | When a spreadsheet document was displayed in the edit mode in the thin client, thick client, or Designer, opening chart area properties required the following steps: first double-click the chart, and then point to the area. | Simplified interaction with charts embedded to spreadsheet documents. |
| Database configuration update. | New feature: critical errors of the optimized database configuration update mechanism are displayed in Designer and in the <EXCP> event of the technological log. | Critical errors of the optimized database configuration update mechanism were not displayed in Designer or in the <EXCP> event of the technological log. | Improved diagnostics of critical errors in the optimized database configuration update mechanism. |
| Spreadsheet documents. | Upgrade: data import from Microsoft Office OpenXML (Microsoft Excel 2007 or later) and ODT (OpenDocument) files is updated. Some bugs related to import from these file types are fixed. | Importing data from Microsoft Office OpenXML (Microsoft Excel 2007 or later) and ODT (OpenDocument) files could cause errors. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | Upgrade: when exporting a spreadsheet document from an XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) file, if a shape or picture text in the source spreadsheet is blank or contains only spaces, a drawing of Text type is not created in the target spreadsheet. This upgrade is ignored in 8.3.13 version compatibility mode. | When importing a spreadsheet document from an XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) file, the following behavior occurred:
| Eliminated unexpected system behavior. |
| Dumping configurations to files/Restoring configurations from files. | When the configuration root is restored from XML partially and there is no external property file with support settings, the restore settings will be cleared. The configuration support will disabled as a result. | When the configuration root was restored from XML partially and there was no external property file with support settings, the restore settings remained intact. The configuration support mode remained intact as well. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | Upgrade: for spreadsheet document drawings that are comments, the DrawingType property value is SpreadsheetDocumentDrawingType.Comment. This upgrade is ignored in 8.3.13 version compatibility mode. | For spreadsheet document drawings that were comments, the DrawingType property value was SpreadsheetDocumentDrawingType.Text. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | Text is displayed correctly in spreadsheet document cells with "Justify" alignment. This upgrade is ignored in 8.3.13 version compatibility mode. | Text in spreadsheet document cells with "Justify" alignment looked as text with "Left" alignment. | Eliminated unexpected system behavior. |
| Data composition system. | The data composition system template generator outputs resource field groupings to templates even if a predefined template describes the output of the parent grouping and resources are not specified in the selected fields of the parent grouping but specified in the fields of the child grouping. This might change the look of some reports. This upgrade is ignored in 8.3.13 version compatibility mode. | The data composition system template generator did not output resource field groupings to templates if a predefined template described the output of the parent grouping and resources were not specified in the selected fields of the parent grouping but were specified in the fields of the child grouping. | Eliminated unexpected system behavior. |
| Technological log. | New technological log properties for DBMS access events (DB2, DBMSSQL, DBPOSTGRS, and DBORACLE) and EXCP and SDBL events: Dbms, Database, and DBCopy. | This feature was not provided. | More convenient DBMS selection diagnostics when managing database copies. |
| Development tools. | Upgrade: when comparing configurations, you can view the detailed differences in help topics. Upgrade: you can compare help topics in selected language, similar to other platform multilingual tools. | When comparing configurations, you could only see if the help topics were different, without any details on the differences. | Comparing help topics in configurations is more convenient. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Administration tools. Software licensing. | New feature: ring command-line utility and its license module are provided as a standalone distribution package (1C:Enterprise licensing utility). The distribution package supports Windows 7 and later, and Linux x86 and x86-64. The distribution archive names comply with the following pattern: 1c-enterprise-license-tools-a.b.c+d-os-arch.zip. The archive is included into 1C:Enterprise distribution package. The distribution packages of the ring utility and its license module are no longer stored to the ExtDst directory. You can find 1C:Enterprise installer documentation on the ITS DVD Read more.. | The ring utility and its license module were a part of 1C:Enterprise distribution package and were stored to the ExtDst directory. The installation of the ring utility was available only after the installation of 1C:Enterprise. | Distribution and update of the ring utility and its license module are more convenient. To install or update the licensing utility, you do not have to install the entire 1C:Enterprise. |
| Software licensing. | New feature: upon activating ("activate" command) a software license and upon creating a response file ("acquire" command) with the ring utility, you can specify an alternative Licensing Center. A Licensing Center can be set in the ExternalResourcesMode parameter of the conf.cfg file. New parameter for the "ring license activate" and "ring license acquire" commands: --conf-location, which is used to specify the directory for the conf.cfg file. | This feature was not provided. Only one Licensing Center was available. | Licensing Center selection is similar to selection of other internet resources required by 1C:Enterprise. The system behavior is more consistent. |
| Internet-enabled functionality. Data display. | New feature: client applications that run on Windows use WebKit library to manage help, Syntax Assistant, HTML document fields, planner, formatted documents, and HTML document editor. In these cases, Microsoft Internet Explorer is no longer applicable. WebKit is included into 1C:Enterprise distribution package and does not require separate installation. The HTMLDocumentField.Document property value type is ExternalObject. The DOM model that can be accessed by this property is changed. We recommend that you review the use of HTMLDocumentField form item in your applications and update applications that use features specific for Microsoft Internet Explorer. | Client applications that ran on Windows used Microsoft Internet Explorer to manage help, Syntax Assistant, HTML document fields, planner, formatted documents, and HTML document editor. | Managing HTML documents is more consistent, regardless of the operating system. |
| Infobase operations. | New feature to ensure the correct identification of two-digit years: the first year of the century. The default first year of the century is changed from 1930 to 1950, meaning 49 is identified as 2049 and 50 as 1950. In a separated infobase, each data area defined by a set of independent separators has its own first year of the century. New global context methods: SetInfobaseBeginningOfCentury(), GetInfobaseBeginningOfCentury(), and SessionBeginningOfCentury(). | The default first year of the century to identify two-digit years was 1930. The year could not be changed. | System behavior related to two-digit years is more transparent. You can customize the first year of the century. |
| Web client. Development tools. | Upgrade: for a file infobase published on a web server, connecting the web client to the infobase in debug mode is only allowed if the infobase was published with the option that allows debugging. Otherwise, debugging is not available. To debug an application using the web client with a file infobase, you have to republish the infobase with debugging allowed. | Debugging applications using the web client with a file infobase was available regardless of the debugging status in the infobase publishing settings. | Eliminated unexpected system behavior. |
| Configuration extensions. Access rights. | New pattern of roles–extensions interaction:
Adopt roles into extensions only when you need to set the extension object rights that do not match the extended configuration's default rights. Upgrade: DefaultRoles property can be expanded. This pattern is ignored in 8.3.13 version compatibility mode. | Old pattern of roles–extensions interaction:
| More convenient roles–extensions interaction pattern. The interaction logic is more transparent. |
| Charts. Data composition system. | New chart tooltip types and view options. New feature: reference lines and tooltips can be displayed at the same time. New properties for the Chart object: ChartValuesTooltipDisplayMode, ValueTooltipFillType, PointsPopUpReferenceLineRepresentation, and ValuesPopUpReferenceLineRepresentation. New feature: chart items can be selected manually or programmatically. A selection can include nonadjacent items. New property for the Chart object: SelectionMode. New event and methods for chart field extensions of field forms. Event: OnActivate. Methods: GetSelectedItems() and SetSelectedItems(). New methods for the SpreadsheetDocumentDrawing object: GetSelectedItems() and SetSelectedItems(). New properties for the DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance objects: ChartType.ValueTooltipDisplayMode, ChartType.ChartValuesTooltipFillType, ChartType.PointsPopUpReferenceLineRepresentation, ChartType.ValuesPopUpReferenceLineRepresentation, and ChartType.SelectionMode. | The following chart features were available:
| Improved chart interactivity. |
| Managed forms. | Upgrade: if a form input field contains a value of reference type, its ChoiceFoldersAndItems property value set to Auto is interpreted as Items. This upgrade is ignored in 8.3.13 version compatibility mode. | If a form input field contained a value of reference type, its ChoiceFoldersAndItems property value set to Auto was interpreted as FoldersAndItems. | Eliminated unexpected system behavior. |
| Data composition system. | Upgrade: upon generation of a data set selection query, the data composition template generator makes an attempt to aggregate the data using the DBMS query language. Query language functions applied to a single field for data aggregation: SUM(), MINIMUM(), and MAXIMUM(). New property that manages aggregate calculation with query language: DataCompositionSchemaDataSetQuery.UseQueryGroupsIfPossible. This upgrade is ignored in 8.3.13 version compatibility mode. | The data composition system did not use grouping to aggregate data in queries, unless it was explicitly specified by the GROUP BY clause. | Improved data acquisition by the data composition system in some cases. |
| Data composition system. | New comparison algorithm for arrays, value tables, and other nonprimitive types in the data composition system:
This upgrade is ignored in 8.3.13 version compatibility mode. | The algorithm output for objects of the same type (including arrays and value tables, excluding objects of primitive type and reference type) was comparison of the object RAM addresses. | Eliminated unexpected system behavior. |
| Server clusters. Administration tools. | New properties for the IClusterInfo object: ErrorsCountThreshold (the number of server errors that is considered critical) and KillProblemProcesses (force closes corrupted processes). | This feature was not provided. | Eliminated unexpected system behavior. |
| Queries. | Upgrade: if a query selection list does not contain tabular section attributes, but the query contains a comparison of tabular section attributes combined with "AND" operator, the conditions are applied together to each tabular section row. This upgrade is ignored in 8.3.13 version compatibility mode. | If a query selection list did not contain tabular section attributes, but the query contained a comparison of tabular section attributes combined with "AND" operator, the conditions were applied separately, which could lead to incorrect comparison results. | Eliminated unexpected system behavior. |
| Pictures. | New feature: you can use 1C:Enterprise language to change picture parameters, such as format, size, DPI, and color depth. New picture management logic:
New methods for the Picture object: Width(), Height(), ColorDepth(), GrayScale(), HorizontalDensity(), VerticalDensity(), and FileSize(). The Picture.Convert() method is deprecated. The PictureProcessor object is deprecated. All PictureProcessor object's methods have matching PictureToProcess object's methods. We recommend that you analyze your applications and replace the deprecated methods and objects with the new ones. | These features were not provided. The only editable picture parameter was picture format. | You can change the parameters of any picture stored in an infobase, for example when you need to send it to a third party having specific requirements to pictures. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile platform. Development tools. | New feature for the mobile platform: report generation based on the data composition system (including data composition system settings dialog boxes). New configuration properties for mobile applications: Default report form, Default report settings form, and Default report option form. Upgrade: data composition system settings forms are adjusted for mobile devices. | This feature was not provided. The mobile platform did not support reports. The data composition system supported only preprogrammed reports without user interaction. | The mobile platform supports reports, including user interaction (users can customize reports). |
| Mobile platform. Mobile client. Mobile application builder. | Upgrade: you can turn off some advertising features when building a mobile application. To turn off the features, clear the Ads check box in the mobile application permissions. | This feature was not provided. | Publishing mobile applications in app stores is more convenient. |
| Mobile platform. Mobile client. | New objects available in the mobile version of 1C:Enterprise: FontChooseDialog and ColorChooseDialog. | These objects were not provided in the mobile version of 1C:Enterprise. | Advanced color and font features in the mobile version of 1C:Enterprise. |
| Mobile platform. Mobile application builder. | Upgrade: faster creation of an infobase at the first start of a mobile application. The upgrade is valid only if the mobile application has been built by exporting (file 1cema.zip) from Designer v. 8.3.14. New format of exporting configurations from Designer. Export to an .xml file is no longer supported. Mobile application builder versions 2.0.8 and earlier do not support configurations exported in the new format. | Creation of an infobase at the first start of a mobile application took more time. | Faster creation of an infobase at the first start of a mobile application. |
| Mobile device-specific features. Mobile platform. | New feature for Windows-based mobile applications: support of in-app purchase service (Windows InAppPurchase). New property: InAppPurchaseService.WindowsInAppPurchase. New feature for the InAppPurchaseReceipt object: a constructor. | Only iOS and Android-based mobile applications supported in-app purchase services. | Windows-based mobile applications support in-app purchase services. |
| Mobile platform. Mobile client. Mobile device-specific features. | New feature: integrate rewarded video ads. New feature: get rewarded video ad status. New methods for the AdRepresentationManager object: GetAdStatus(), SetRewardedVideoID(), GetRewardedVideoID(), ShowRewardedVideo(), StartRewardedVideoDownloading(), StartAdBannerDownloading(), and StartRewardedVideoDownloading(). | This feature was not provided. | Advanced advertising features for mobile applications. |
| Data display. | New mobile platform feature: custom styles and style elements. The feature is available for configurations imported from 1C:Enterprise platform version 8.3.14 and later. Mobile application color scheme ignores the NavigationColor, AuxiliaryNavigationColor, and ImportantColor style properties. | This feature was not provided. | New options for mobile application appearance management. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Queries. | Clarified the error message that appears during an attempt to create a temporary table if the specified temporary table manager has already been closed. The new error text is Cannot use a closed temporary table manager. | The error message that appeared at an attempt to create a temporary table if the specified temporary table manager had already been closed might mislead users. The error text was Temporary table manager is not set. | Eliminated unexpected system behavior. |
| Data composition system. | When the data composition system template generator outputs fields to chart grouping templates, it applies conditional appearance to all of the fields. As a result, in reports based on data composition schemas the conditional appearance applied to resource fields is also applied to charts. This might change the look of reports containing charts with resources that have conditional appearance. | When the data composition system template generator output fields to chart grouping templates, it applied conditional appearance only to nonresource fields. | Eliminated unexpected system behavior. |
| Data composition system. | If a report is displayed in compact mode, reports opened using the Drill down command are also displayed in compact mode. A setting that shows whether the result is displayed in compact mode is available. The name of the setting key is client application-specific. New report form parameter: ResultViewMode. Use it to explicitly specify the report view mode. New method: GetRecommendedCompactWidth(). It returns spreadsheet document cell width. The ConvertToCompactMode() method of spreadsheet document takes its return value as a parameter. | Reports opened using the Drill down command did not inherit the main report mode (compact or normal). | Reports opened in the client application using the Drill down command inherit the main report mode. |
| macOS. Client application. Administration tools. | New feature: distribution packages for the thin client running on macOS. New feature: users can select the version and type of client applications running on macOS. New feature: uninstall wizard for client applications. New directory tree in macOS Applications directory. New directories for some 1C:Enterprise application files. New feature: you can create self-extracting installers (DMG images) for client applications. The archive can contain 1cestart.cfg configuration file that contains setup, runtime, and update settings. The executable files support macOS only. New utility: 1CEClientSetupMake. | Self-extracting installers for macOS were not provided. Users could not select client application version. Users could select client application type only within one version. File tree in Application directory was different. 1CEClientSetupMake utility was not provided. | Administration of client applications on macOS is more convenient. |
| macOS. Client application. Administration tools. | New feature: client applications on macOS can be updated over the network. New field in the dialog window for publishing applications on web server where you can specify the path to the client application distribution package. Fields that contain paths to the client application on Windows renamed according to the bitness. New conf.cfg configuration file parameters: PublishDistributiveLocationMacOS64, PublishDistributiveLocationWindows32, and PublishDistributiveLocationWindows64. The conf.cfg configuration file parameters PublishDistributiveLocation32 and PublishDistributiveLocation64 are obsolete. New attributes for <point> item of default.vrd configuration file: pubdstmac64, pubdstwin32, and pubdstwin64. The attributes for <point> item of default.vrd configuration file pubdst, pubdst32, and pubdst64 are obsolete. New feature: 1C:Enterprise on macOS supports launchers stored on network drives. Upgrade: the web service that receives client application distribution packages supports macOS. | These features were not provided. | Client application update is more convenient. |
| Server clusters. Standalone server. | New parameters for the standalone server configuration file that define path to client application distribution package on Windows and macOS: win32, win64, and mac64. The parameters x86 and x86_64 are obsolete. | The standalone server configuration file supported only Windows operating system. | The standalone server configuration file supports macOS operating system. |
| XML and XDTO support. | Upgrade: the result of a spreadsheet document serialization does not depend on whether the document was transferred between a client and a server. The resulting document always has the same structure. The upgrade does not affect the appearance of spreadsheet documents and usage of 1C:Enterprise language to manage them. This upgrade is ignored in 8.3.13 version compatibility mode. | The result of a spreadsheet document serialization depended on whether the document had been transferred between a client and a server. The resulting documents could have different structures. | Comparison of spreadsheet documents serialized to XML documents is more convenient. |
| Mobile client. Collaboration system. | New feature: the mobile client supports file transfer over the collaboration system. | This feature was not provided. | New collaboration system features for the mobile client. |
| Mobile platform. Mobile application builder. | New configuration export format for the Mobile application builder. The format is supported by the Mobile application builder version 2.0.9 or later. Version 2.0.8 and earlier do not support new format. Upgrade: faster initial start of mobile applications built with Designer version 8.3.14. | These features were not provided. The initial mobile application start took more time. | Faster initial start of mobile applications exported in new format. |
| Mobile application builder. | New feature: you can specify the default application presentation in multiple languages for mobile applications that contain multiple configurations. The default presentation is automatically applied to all new versions of this mobile application. | Each new version of a mobile application that contained multiple configurations was based on the first configuration added to the build. Developers had to change the presentation manually. | Developing mobile applications that contain multiple configurations is more convenient. |
| Spreadsheet documents. Linux. Server clusters. | Upgrade: 1C:Enterprise server clusters running on Linux process spreadsheet documents faster. | 1C:Enterprise server clusters running on Linux took more time to process spreadsheet documents. | Improved performance of 1C:Enterprise server clusters running on Linux in processing spreadsheet documents. |
| DBMS operations. | Upgrade: for PostgreSQL DBMS on Windows, the limitation of 1,200 simultaneously open files per PostgreSQL process is removed (the max_files_per_process DBMS parameter). | For PostgreSQL on Windows, the limitation of 1,200 simultaneously open files per PostgreSQL process was applied. | Improved PostgreSQL DMBS performance with large-size configurations, such as 1C:ERP. |
| Dumping configurations to files/Restoring configurations from files. | Upgrade: when exporting a configuration to files with 1C:Enterprise version 8.3.14 or later (export format 2.8 or later), the name of the spreadsheet document form field extension event that is called upon selection a spreadsheet document area or upon any operation with the chart is OnActivate regardless of the compatibility mode. When exporting a configuration to files in export format 2.8 or earlier, the even name OnActivate is equivalent to the event name OnActivateArea. | The name of the spreadsheet document form field extension event that was called upon selection a spreadsheet document area or upon any operation with the chart depended on the compatibility mode. | The form item event name does not depend on the compatibility mode. |
| Dynamic lists. | Upgrade: in the thin client, users can perform search in a dynamic list composite column by part of the string and by the substring. | In the thin client, users could not perform search in a dynamic list composite column by part of the string and by the substring. | Eliminated unexpected system behavior. |
| Mobile application builder. | Upgrade: the Mobile application builder defines the amount of RAM the Java process requires to build Android mobile applications more precisely. If you use a 32-bit Java version to build an application in a 64-bit environment, a log record that suggests to specify the 64-bit Java in the Mobile application builder settings is created. | In some cases, the Mobile application builder defined incorrect amount of RAM the Java process required to build Android mobile applications. This could lead to build errors due to insufficient memory. If you used a 32-bit Java version to build an application in a 64-bit environment, a log record that suggests to specify the 64-bit Java in the Mobile application builder settings was not created. | Fixed some bugs that caused insufficient memory errors during Android application building. |
| Managed forms. | Upgrade: for the Taxi interface on the thin and thick client, if a form field is in the list selection mode, StartChoice event handler ignores standard processing, and the choice list is empty, the drop-down list is always collapsed. The upgrade is ignored in the web client. This upgrade is ignored in 8.3.13 version compatibility mode. | For the Taxi interface in the thin and thick client, if a form field was in the list selection mode, StartChoice event handler ignored standard processing, and the choice list was empty, the drop-down list was expanded and filled with the choice list values. In the web client, under the same conditions, the list was always collapsed. | Eliminated unexpected system behavior. |
| Configuration extensions. | New configuration extension property: DefaultRoles. With this property, you can specify the roles that define accessibility of extension objects when the user list is empty. New configuration extension property: ForceDefaultRolesForAllUsers. With this property, you can assign all users in an attached extension with the rights defined by the extension default roles. You can edit the property in Designer (extension list) or with the standard extension management function. When you manage user access rights in Designer, the full name of the role added by an extension is displayed. When an extension is created, a special role that grants access rights to all objects of the extension is created automatically. DefaultRoles property value is set to this role. You can edit the role without any limitations. If an extension is attached to a file database in safe mode, access rights to extended configuration objects cannot be granted. This upgrade is ignored in 8.3.13 version compatibility mode. | Developers could not specify default role lists for configuration extensions. When developers managed user access rights in Designer, the full name of the role added by an extension was unavailable. When an extension was created, a special role that granted access rights to all objects of the extension was not created. If an extension was attached to a file database in safe mode, access rights to extended configuration objects could be granted. | Сonfiguration extension access right management is more convenient. |
| Mobile platform. Mobile client. Mobile device-specific features. Mobile application builder. | New push notification service that supports Windows Push Notification Services (WNS) and Firebase Cloud Messaging (FCM). The Mobile application builder supports new push notification options. | This feature was not provided. The notification service supported only Google Cloud Messaging (GCM) and Apple Push Notification Service (APNs). | The notification service is now compliant to the mobile version of 1C:Enterprise. |
| Mobile platform. Mobile client. | New features: the mobile version of 1C:Enterprise supports groups for pop-up forms and forms with United property set to False. | These features were not provided. | Form management in the mobile version of 1C:Enterprise is more flexible. |
| Queries. | Upgrade: the query language ValueType() function applied to an expression that contains the IsFolder field returns the correct value. This upgrade is ignored in 8.3.13 version compatibility mode. | The query language ValueType() function applied to an expression that contained the IsFolder field returned an incorrect value. Result was calculated as if the IsFolder field value contained an inverted value. | Eliminated unexpected system behavior. |
| Queries. | Upgrade: if a parameter expression of the query language ValueType() function contains a virtual field and a primitive type value, the function returns a correct value. This upgrade is ignored in 8.3.13 version compatibility mode. | If a parameter expression of the query language ValueType() function contained a virtual field and a primitive type value, the function returned an incorrect value. | Eliminated unexpected system behavior. |
| Collaboration system. | Upgrade: user search in the collaboration system is performed only by the beginning of words. The search algorithm for headings of noncontext group conversations and participant lists of one-to-on conversations is improved. Conversations in search results are ranked higher if they have:
| User search in the collaboration system used the string-matching algorithm. Search result was ranked in the same order order the conversations had been found in the database. | The search algorithm in the collaboration system is improved. |
| Mobile platform. Mobile client. Mobile application builder. System requirements. | Windows 8.1 and Windows Phone 8.1 operating systems are no longer supported by 1C:Enterprise mobile platform. New: Windows 10 operating system is supported for ARM architecture. Upgrade: components of a distribution package of 1C:Enterprise mobile platform is changed (mobile.zip file). Mobile application builder can no longer build mobile applications for Windows 8.1 and Windows Phone 8.1 using 1C:Enterprise mobile platform 8.3.14 and later. | 1C:Enterprise mobile platform supported Windows 8.1 and Windows Phone 8.1. 1C:Enterprise mobile platform did not support Windows 10 for ARM architecture. | A list of supported Windows versions is updated. |
| Server clusters. | New property AdministrationClusterManager.ClusterManagerID. | This feature was not provided. | Now you can unambiguously identify a cluster manager upon using the ServerAdministration object. |
| Data composition system. | Upon adding a filter to query of composition schema data set that includes unions, the filter is necessarily added to every part of the union if automatic filling of available fields is enabled for the data set or the field, to which the filter is applied, is accessed via the point from the field available for filtering. Besides, if the filter item group contained a field that was not available in one of unions and another field that was available, and if all fields were available in another part of the union, the filter would be applied to the part where it was unavailable, and all unavailable fields would be replaced by NULL. If a query with unions is used in a report or a dynamic list, and it is required that filter for a particular field is included only in certain union parts, it is recommend that you disable automatic filling of available fields for the data set and add the required field only to the union parts you need. This upgrade is ignored in 8.3.13 version compatibility mode. | Whenever a filter was added to a query of composition schema data set that included unions, this filter was necessarily added to every part of the union if it could be included at least in one part of the union. In union parts, in which the filter could not be used as fields used in the filter were missing, these fields were replaced by NULL in conditions being added. Besides, if a filter item group contained a field, which was unavailable in one of the unions, and another field, which was available, and all fields were available in another part of the union, then such filter was applied outside query, on the level of data set of a data composition template. | Now you can create reports, which use queries with unions and in which the filter by some fields can be applied not to all queries inside the union. |
| Data accelerator. Queries. | New feature: now Data accelerator supports queries containing the IN HIERARCHY expression. | Data accelerator did not support queries containing the IN HIERARCHY expression. | Advanced features of Data accelerator. |
| Pictures. | The ColorDepth system enumeration is available in Russian in Version 8.3.14 or later compatibility mode only. In Version 8.3.13 or earlier compatibility mode, this enumeration is available only in the English ColorDepth option. | The ColorDepth system enumeration was available in Russian in any compatibility mode. | Resolved the conflict between platform IDs and names of variables of released applications. |
| Mobile application builder. | Full number of a mobile application built by the Mobile application builder and designed for Windows always has "0" as a last digit in the full application version number. | Full number of a mobile application built by the Mobile application builder and designed for Windows had the current build number, which was unique within one mobile application, as a last digit in the full application version number. | Now the Mobile application builder meets Windows Store requirements for the version number of a mobile application being published. |
| Mobile application builder. Mobile client. | Now you can specify the following upon setting up a mobile client application builder:
You can use the specified features if the address of an infobase or a web service with a shared infobase list starts with the "https://" prefix. Otherwise, certificate operations are not available. | This feature was not provided. | Now you can use the mobile client if accessing an infobase requires secure connection and placing the required certificates on end-user mobile devices is not available. |
| XML and XDTO support. | New feature: the platform supports XSD schemas containing types, in which attributes are defined via references to global attributes, but overriding such properties as default or fixed ones. | Upon trying to use in the platform XSD schemas containing types, in which attributes were defined via references to global attributes, but overriding such properties as default or fixed ones, errors occurred when checking the XDTO model, and such schemas were not available. | Eliminated unexpected system behavior. |
| Data accelerator. Queries. | New feature: now Data accelerator supports queries using tabular sections and the RECORDAUTONUMBER() query language function. | Data accelerator did not support queries using tabular sections and the RECORDAUTONUMBER() query language function. | Advanced features of Data accelerator. |
| Localization. | Localized client application interface for Italian (it). | This feature was not provided. | 1C:Enterprise is available to Italian-speaking users. |
| Interface. | New feature: search bar is available in the All functions dialog box. Search begins when you try to type a search expression in the сonfiguration object tree. The whole list of objects in the dialog box is searched, regardless of whether the branches of the сonfiguration object tree are expanded or not. You can enter several search words in the search bar. In this case, the search will be done using all entered words of the search query. You can also access the search bar by pressing Ctrl+F. To search using the standard dialog box, press Alt+F. Only expanded branches of the сonfiguration object tree are searched. | Search in the All functions dialog box was available only using the standard search dialog box, which searched only expanded branches of the сonfiguration object tree. This dialog box was accessible by pressing Ctrl+F. In the All functions dialog box, search by several words was not available. | The search in the All functions dialog box is much easier now. |
| Software licensing. | Security profiles are not technically blocked in 1C:Enterprise when a PROF license is used. To use security profiles, the user must still have a CORP license. | Security profiles were technically blocked in 1C:Enterprise when a PROF license was used. | Changed functions in CORP licenses, whose availability is checked technically. |
| System requirements. DBMS operations. | PostgreSQL 9.6.6 from AstraLinux Special Edition 1.6 is supported now if the en_US.UTF8 locale is set up in this operating system. | PostgreSQL 9.6.6 from AstraLinux Special Edition 1.6 was not supported. | Extended list of supported DBMS. |
| Mobile client. | Collaboration system push notifications are sent to a mobile device using Firebase Cloud Messaging. | Collaboration system push notifications were sent to a mobile device using Google Cloud Messaging. | Outdated technology of push notification delivery in the collaboration system is no longer used. Upgrade: faster delivery of push notifications from the collaboration system to client mobile devices. |
| Mobile platform. Mobile client. | If case of unexpected shutdown of the mobile application, you will be taken to the application list. | If case of unexpected shutdown of the mobile application, the mobile application itself was shut down. As a result, it was impossible to restore an infobase from a backup (when using a mobile platform) or change connection settings (when using a mobile client). | Improved behavior of the mobile application in case of unexpected shutdown. |
| Mobile platform. Mobile client. Mobile Application Builder. | 1C:Enterprise mobile platform now supports 1244x2208 and 2208x1244 splash screens when running Android OS. Splash screen support of this size is now included in Mobile Application Builder. | 1C:Enterprise mobile platform did not support 1244x2208 and 2208x1244 splash screens when running Android OS. Mobile Application Builder did not support this size for splash screen. | Implemented splash screen support for high-resolution screens when running Android OS. |
| Development tools. Mobile platform. Mobile client. | You can now create a configuration file of the mobile platform in zip format only. You can no longer create an xml configuration file. The change relates to exporting with both the Designer interactive mode and the Designer command line (/MobileAppWriteFile option). | The configuration file of the mobile platform could have zip or xml format. | Configuration export format for the 1C:Enterprise mobile platform has changed. |
| DBMS operations. | PostgreSQL 10.8 is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 10.9 is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 10.10 is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| Administration tools. Software licensing. | The 1C:Enterprise licensing utility distribution package includes the following utilities versions:
| The 1C:Enterprise licensing utility distribution package included the previous versions of utilities. | Minor errors and typos fixed. |
| Mobile platform. Documentation. | The documentation describes the directory structure created when publishing a mobile application on a web server with Designer. It also describes the MIME types that the web server must support to be capable of hosting mobile application configurations and application debugging. | The documentation did not contain information about data located on the web server after publishing the mobile application with Designer. | Updated platform documentation. |
| Collaboration system. | Implemented the CollaborationSystemAttachment.ContentRemoved property to display the fact of deleting the attachment from the 1C:Enterprise file storage. Updated the messages displayed when transferring the file with the collaboration system failed. | There was no way to detect from the 1C:Enterprise language that the attachment was removed from the collaboration system file storage. | You can now detect that the attachment was removed from the collaboration system file storage. |
| Collaboration system. | If the 1C:Dialog service is used to operate the collaboration system, the file transfer has the following limitations: Read more. | Conditions of storing files in the 1C:Dialog service were not defined. | Conditions of storing files in the 1C:Dialog service are now defined. |
| DBMS operations. System requirements. | The server cluster can only interact with Oracle Database DBMS provided that Instant Client 10.2.0.5 is installed on the cluster computer. Oracle Database client libraries were excluded from 1C:Enterprise distribution package. | Oracle Database client libraries were included in 1C:Enterprise distribution package. The server cluster was able to interact with Oracle Database DBMS with no additional software required. | The 1C:Enterprise distribution package content was changed.
|
| System requirements. Mobile platform. Mobile client. | Android version 4.0 is no longer supported. | Android version 4.0 was supported. | Ended support for legacy Android versions. |
| DBMS operations. System requirements. | PostgreSQL DBMS 11.5 (x86-64) is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| Mobile application builder. | The mobile application builder supports Firebase Cloud Messaging push notifications (FCM, for Android) and Windows Push Notification Services (WNS, for Windows) when working through 1C:Enterprise secondary service (https://pushnotifications.1c.com). Google Cloud Messaging service for sending push notifications (GCM, for Android) is disabled when using the 1C:Enterprise secondary service (https://pushnotifications.1c.com) with the mobile application builder. | When using the 1C:Enterprise secondary service (https://pushnotifications.1c.com) with the mobile applications builder, the Apple Push Notification Service (APNs, for iOS) and Google Cloud Messaging (GCM, for Android) were actually available. | When using the 1C:Enterprise secondary service (https://pushnotifications.1c.com) from the mobile applications builder, the builder actually supports the features of the service. |
| Development tools. macOS. | The HASP key driver distribution package has been excluded from the client applications distribution package for macOS. To install the security key driver, you will need to download it from Gemalto website first. | The client applications distribution package for macOS included the HASP key driver distribution package. | Compliance with Apple requirements is now available. Creating the 1C:Enterprise distribution package, which can be installed on macOS version 10.15 and later, is not available without such compliance. |
| DBMS operations. | PostgreSQL 10.12 is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 11,7 is now supported.
| This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| System requirements. Administration. | 1C:Enterprise distribution packages for Windows and macOS include HASP Device Driver 7.92. | 1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 7.63. | 1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver. |
| Interface. | The About... window includes the hyperlink Add-in licenses, which opens the list of the third-party add-ins used in 1C:Enterprise. | The About... window didn't provide the information about the third-party add-ins used in 1C:Enterprise. | Conformity with GNU LGPL v2.1. |
| System requirements. DBMS operations. | Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
| The following Postgres Pro DBMS versions were not supported:
| Extended list of supported DBMS. |
| System requirements. DBMS operations. | Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
| The following Postgres Pro DBMS versions were not supported:
| Extended list of supported DBMS. |
| DBMS operations. | PostgreSQL 10.13 (x86-64) is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 11,8 (x86-64) is now supported.
| This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 12,3 (x86-64) is now supported.
| This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 10.14 (x86-64) is now supported. | This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 11,9 (x86-64) is now supported.
| This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
| DBMS operations. | PostgreSQL 12,4 (x86-64) is now supported.
| This PostgreSQL DBMS version was not supported. | More PostgreSQL DBMS versions are now supported. |
Version 8.3.13 includes known bug fixes and functionality modifications.
Finished the beta testing of the Designer agent mode.
The local collaboration system server feature graduated from beta. Local collaboration servers require COPR-level client and server licenses.Read more.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.12 is now implemented. | Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.11 was implemented. | Configurations developed using 1C:Enterprise platform version 8.3.12 or earlier can run on version 8.3.13 without any changes to configuration or to data structures. This allows for transition to version 8.3.13 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.12 after the transition to version 8.3.13, even if you disabled the compatibility mode (if you did, enable it again). |
| DBMS operations. System requirements. | PostgreSQL version 10 is supported. | PostgreSQL version 10 was not supported. | The list of supported DBMS is extended. |
| Collaboration system. | Implemented 1C:Enterprise. Startup and notifications application. It provides the following features:
The application is available for Windows and Linux, and also for Google Chrome, Mozilla Firefox, and Microsoft Internet Explorer. Implemented the option to display the new messages from the collaboration system and the notification center when starting a client application. Implemented the DisplayUserNotificationList command-line option of the client application startup in the thin, thick, and web clients. | Notifications from a specific application were displayed on a computer only if the application was running on that computer. | The collaboration system notifications from a specific application are available even if the application is not running. |
| Web client. | In the web client an option to specify the OpenID authentication provider (or the list of providers) is implemented. Each specified provider must support the OpenID Connect protocol. The openidconnect parameter is added to the default.vrd file. Implemented the OidcSelectedProvider command-line option in the web client. This feature is not available if the infobase is published from Designer. This feature is available in the web client only. | This feature was not provided. Only the 1C:Enterprise infobase could be used as the OpenID authentication provider in the web client. | Expanded the authentication options list in the web client. |
| Automated testing. | For TestedFormDecoration and TestedFormField objects, implemented the ClickFormattedStringHyperlink() method. The method emulates clicking a hyperlink in a formatted string. | This feature was not provided. | Extended automated testing capabilities. |
| InterfaceConfiguration extensions. Mobile platform. Mobile client. | Implemented the option to create custom styles and style elements. The DefaultStyle configuration property is now available in the managed application. Styles and Style elements are now available in the Common metadata tree branch. Implemented the following system colors:
In version 8.3.12 compatibility mode, style elements of Color and Font type that are included in a style retain their values, provided that the style was not used in the ordinary application and the values of those style elements were not changed. The color of several interface items was slightly changed. In configuration extensions, you can create and adopt styles and style elements. Configuration extensions can override the DefaultStyle property. | This feature was not provided. | New options for client application appearance management. |
| Client application. | The application startup splash can be disabled now. Implemented the DisableSplash command-line option. It is available in the thin, thick and web client. | This feature was not provided. The application startup splash could not be disabled. | Extended capabilities for 1C:Enterprise integration with third-party systems. |
| Configuration extensions. | The following objects can now be created in the configuration extension:
Configuration extension native accumulation registers do not support aggregates. The records of native and adopted configuration extension documents can now include the configuration extension native registers. | This feature was not provided. | Extended configuration extension usage options. |
| Data display. | Implemented the text declension feature. Implemented the GetStringDeclensions() global context method. | This feature was not provided. | 1C:Enterprise is now capable of declining various texts, for example, in reports and documents. |
| Background and scheduled jobs. | Implemented the option to wait for the completion of one or several background jobs within the specified period. For BackgroundJob and BackgroundJobsManager objects, implemented WaitForExecutionCompletion() method. The WaitForCompletion() method is deprecated. We recommend that you review your algorithms that involve background jobs. The message informing about waiting for the completion of a background job that is missing from the lists of running and completed jobs is more accurate. 1C:Enterprise can detect situations where the current user that does not have the Administration access right attempts to wait for the completion of a background job started by another user. | This feature was not provided. Waiting for completion of one or several background jobs was available. If the background job completed abnormally, an exception was thrown. The message informing about waiting for the completion of a background job that did not exist was not clear. | Simplified waiting for background job completion. Simplified other operations performing while waiting for background job completion. |
| Server clusters. | New feature: evaluation of CPU load in the current session. The following time spans are available:
New session properties for the rac utility: cpu-time-current, cpu-time-5min-last, and cpu-time-total. New properties of the ISessionInfo object: cpuTimeCurrent, cpuTimeLast5Min, and cpuTimeAll. New property of the <CALL> event: CpuTime. It stores the duration of a completed server call (in milliseconds). New feature: developers can create custom resource consumption counters with multiple indicators, such as CPU time, memory usage, and disk I/O data volume. The cluster console now supports resource consumption counter management. New rac utility commands:
Implemented the option to run the following session management operations upon reaching the specified resource consumption values:
You can specify resource consumption limits in the cluster console. New rac utility commands:
New feature: developers can manage resource consumption with Java interface for 1C:Enterprise server cluster administration (read more). Resource consumption level feature requires CORP license. | These features were not provided. | You can set the resource load limits on the computer with cluster server. Improved system reliability. |
| Data composition system. | Implemented the DataCompositionUserSettings.GetMainSettingsByUserSettingID() method. This method returns the array of main settings by the user setting ID. It can be used to specify user settings properties that are otherwise read-only. | This feature was not provided. | Simplified access to user settings of the data composition system. |
| Spreadsheet documents. | Implemented the option to optimize the view of spreadsheet documents that do not fit the screen width (mostly on mobile devices). The optimization eliminates the need for horizontal scrolling. For spreadsheet document, implemented GetCompactDocument() method. It returns the compact version of a spreadsheet document. For spreadsheet document, implemented SetAutoWidth() method. It sets the horizontal stretching mode for spreadsheet document columns. For spreadsheet document, implemented ConvertToCompactMode() and RevertToDefaultMode() methods. They respectively create and delete a copy of a spreadsheet document that fits the width of a small screen. When a spreadsheet document is printed or saved, the original non-optimized spreadsheet document is used as a source. Implemented the ResultViewMode property of the report managed form field extension. It allows you to manage the report transformation. Implemented the Compact Mode command of the report managed form field extension. It allows you to edit the ResultViewMode property value. The current report view modes for the mobile client and other client applications are separately stored in the system settings storage. | These features were not provided. The spreadsheet document could not be transformed to fit the width of the small screen. | Improved spreadsheet document appearance on a small screen (for example the mobile device screen). |
| Metadata objects. | The option to analyze metadata, stored in .cf or .cfe file, is implemented. Implemented the ConfigurationMetadataObject constructor. You can now get the configuration name, version, and vendor from the .cf or .cfe file. Implemented the ConfigurationDescription object. You can now get the list of versions, suitable for the update, and the resulting version number from a .cfu file. Implemented the ConfigurationUpdateDescription object. | This feature was not provided. The information about the configuration or the configuration update was not available. | Simplified development of automated configuration updating and distribution packages creating tools. |
| Configuration extensions. | The following configuration properties can now be adopted:
You can now adopt the Picture type objects by replacing the current picture. The following configuration extension properties can now be specified:
| These features were not provided. | Extended configuration extension usage options. |
| Configuration extensions. Data exchange. | The extension native exchange plan can now include adopted objects. You can now adopt the exchange plan data (create exchange plan attributes, tabular sections, and tabular section attributes). | The extension native exchange plan could include the extension native objects only. The exchange plan data could not be adopted. | More configuration extension management options. |
| Data history. | You can now override default data history forms. Added the following properties of the Configuration object:
Implemented DataHistoryVersionFilterDialog and DataHistoryUsersChooseDialog objects. | Default data history forms overriding was not available. | Extended data history options. |
| Internet-enabled functionality. | Implemented the following HTML document options:
| These features were not provided. The only available option was to cycle HTML document DOM model and perform actions with its items. | Simplified and improved the HTML document performance in particular scenarios (for example if you want to delete all <script> tags) |
| Internet-enabled functionality. | Emails can now use OAuth2 protocol together with IMAP protocol. Implemented the following InternetMailProfile object properties: TokenAuthentication and AccessToken. | This feature was not provided. | The email servers with the OAuth2 authentication protocol are now supported. |
| Queries. | A field with consequently increasing unique values can now be added to the temporary table. Implemented the RECORDAUTONUMBER() query language function. It is available for a temporary table only. The RECORDAUTONUMBER() function is not supported in the following cases:
| This feature was not provided. | Simplified adding the unique field with consequently increasing values to a temporary table. |
| Automated testing. | Implemented the following options of the spreadsheet document extension of the TestedFormField object:
| These features were not provided. | Extended automated testing capabilities. |
| Data history. | The option to handle the data version restoration in the object module and in the managed form module is now available. If a form displays one of the older object version, the version number is displayed in the form header. Implemented a dynamic list command that displays the selected object data history (if supported). It is available for users with ViewDataHistory access right. Implemented the VersionNumberSwitchToDataHistoryVersion managed form parameter. Implemented the GenerateFromDataHistoryVersionProcessing() event handler in the following modules:
This handler is called when the object is generated based on the data history version. | The developer could not handle the object version restoration. The object history could be displayed in the object form or the register record form only. | Extended data history options. Improved data history security. |
| Data display. | New pictures were added to the picture library: Conversations, NewConversation, Notifications. | The listed pictures were not available in the picture library. | More content for the picture library. |
| Data history. | Implemented the data history of exchange plans, charts of calculation types, and constants. | This feature was not provided. | Data history is now available for more objects. |
| Applied objects. | Implemented the ConstantValueKey object. Implemented the CreateConstantValueKey() method of the constant manager. | This feature was not provided. | Expanded constant management capabilities. |
| Development tools. | Implemented the option to create a macOS-compatible distribution package. The application distribution package now includes the .zip archive that contains the distribution file and the installer executable files for each supported operating system (Windows, Linux, macOS). The executable files now have the right parameters (Linux, macOS), so you can now unpack the distribution package and install the applicaton. Implemented the CreativeDistributivePackage command-line option of the Designer batch mode. The CreateDistributive command-line option of the Designer batch mode is deprecated. | Creating an application distribution package for Windows and Linux only was allowed. The application could not be installed on macOS. There was no option to create an application distribution package with correct executable files for each supported operating system. You had to specify the correct parameter in the Linux executable file to install the application. | You can now install the application on any supported operating system. The distribution package is now compatible to any supported operating system. |
| System requirements. Configuration repositories. | Implemented the 64-bit configuration repository server on Linux. | There was only the 32-bit configuration repository server available on Linux. | The functionality of configuration repository server is now fully available on 64-bit Linux. |
| Data history. | Implemented the option to force the update of data history of specific infobase object. Imolemented the UpdateHistory() method of the DataHistory object. | This feature was not provided. The data history update was available for all infobase objects at once only. If a specific object data history form was opened, some versions might not be displayed. | The specific object data history form now displays the full history. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Collaboration system. | Converstation participants receive notifications in the conversation form if one of them is typing a message. The following user statuses are now available: offline, away, do not disturb, and online. The Away status is available in thick and thin clients on Windows only. Updated the new message notification. You can now start a conversation with user from the user information form. Updated the collaboration system main window. Updated Collaboration system management standard function. Updated registration and cancelling registration forms. | These features were not provided. | Improved the collaboration system interface. |
| Interface. | Implemented the following changes In the Taxi interface:
| The Taxi interface behaved the following way:
| Improved the spreadsheet document and managed form table appearance in managed form with custom scale. |
| Interface. | All incorrect links are displayed as a link (not link's presentation). When the user favorites settings dialog box is closed, incorrect links remain in the favorites list and can be used or edited. Implemented the URLPresentation.Presentation() method. The GetURLsPresentations() method always returns the array of URLPresentation objects. Each URLPresentation object in this array will have different values depending on the link. This change is not implemented in version 8.3.12 compatibility mode. | Incorrect links had a blank interface presentation and were not available. They were deleted from the user work history after the user favorites settings dialog box was closed. The GetURLsPresentations() method applied to an incorrect link returned Undefined. | Improved links performance. |
| Web client. Spreadsheet documents. | Eliminated spreadsheet document printing faults in the web client if the HTML print method is selected. | A spreadsheet document might be printed with faults in the web client if the HTML print method was selected. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Information registers. | Implemented the cluster index based on dimensions of slice first and slice last physical tables of an information register. Index structure description Read more.. Disabled index uniqueness verification. Optimized performance of queries operating with slice tables. This index can be built the following ways:
| Physical slice first and slice last tables were not indexed. The performance of the queries operating with slice tables was not optimal. | Improved physical slice tables performance in configurations with large number of users. Eliminated deadlocks when updating the physical slice tables. |
| Full-text search. | Reduced the size of temporary files created during the update of full-text search index. This change affects infobases with many separators the most. The new temporary file format is used when the compatibility mode is disabled. This change is not implemented in version 8.3.12 compatibility mode. | Temporary files created during the update of full-text search index were significantly larger. | Reduced the disk space allocated for a full-text search index generating when the infobase contains many separators. |
| DBMS operations. | Improved performance of virtual turnover tables of accumulation and accounting registers when they are grouped by day, month, or year, or when the BeginOfPeriod() query language function is used. This change is available in all supported DBMS, except for Microsoft SQL Server versions earlier than 2012. | Performance of virtual turnover tables of accumulation and accounting registers when they were grouped by day, month, or year, or when the BeginOfPeriod() query language function was used, was suboptimal. | Improved performance of virtual turnover tables of accumulation and accounting registers. |
| Common objects. | Improved performance of the following ValueTreeRowCollection object methods: Remove(), Insert(), Index(), and Move(). | The performance of the following ValueTreeRowCollection object methods was insufficient: Remove(), Insert(), Index(), and Move(). | Improved performance of the value tree rows from 1C:Enterprise script. |
| External reports and data processors. | Improved performance of loading external reports and data processors opened by large number of users. | Loading external reports and data processors opened by large number of users was longer. | Improved performance of loading external reports and data processors opened by large number of users. |
| Background and scheduled jobs. Configuration extensions. | Improved performance of second and further background job startups if they use the same set of configuration extensions. This change is available In file mode. | In file mode second and further background job startups were longer even if they used the same set of configuration extensions. | Improved background job startups in the file mode if they are operating with configuration extensions. |
| Common objects. | Optimized filling and deleting rows of a table of values. | Filling and deleting rows of a table of values were longer. | Improved table of values performance. |
| Web client. | Optimized page titles (tabs) rendering in the web client. | Page titles (tabs) rendering in the web client was slow and suboptimal. | Eliminated unexpected system behavior. |
| Common attributes / Data separation. | Improved opening forms performance in a configuration that uses common attributes. | Forms opened relatively slow if a configuration used common attributes. | Forms in a configuration that uses common attributes now open faster. |
| Data composition system. | Sometimes the data composition system template composer attempts to sort the data set by the DBMS means. The data composition system does not use it's own means in these cases. But the composition result may be incorrect because the row comparison operations are different in various DBMS and 1C:Enterprise platform. This change is not implemented in version 8.3.12 compatibility mode. | Data composition system template composer always sorts the data set by the data composition system means. | Improved the sorting performance during the report building in some scenarios. |
| Data composition system. | Improved the data composition system template generation if the data composition schema is composed of many queries that generate temporary tables with many fields that are not used in the composition process. | The data composition system template generation process was longer if the data composition schema was composed of many queries that generated temporary tables with many fields that were not used in the composition process. | Improved complex reports with many temporary tables building performance. |
| Queries. | If a query contains an IN subquery then a join with table from the IN subquery is used instead. This change is performed only if it does not affect the query result. This change is not implemented in version 8.3.12 compatibility mode. | If a query contained an IN subquery, the DBMS always used this subquery. | Improved the DBMS query plan in some scenarios. |
| Development tools. Server clusters. | Improved the configuration database update performance when it is initiated from a debug session in client/server mode. | The configuration database update was longer when it was initiated from a debug session in client/server mode. | Improved the configuration database update performance when it is initiated from a debug session in client/server mode. |
| Spreadsheet documents. | Improved the CheckPut() method performance if a spreadsheet document contains multiple sheets. | The CheckPut() method performance for a spreadsheet document with many sheets was insufficient. | Improved performance of spreadsheet document display. |
| Spreadsheet documents. | Improved copying to clipboard performance. Improved the GetArea() spreadsheet document method performance when applied to the spreadsheet document area with multiple rows with custom column formatting. | Copying to clipboard performance and the GetArea() spreadsheet document method performance when applied to the spreadsheet document area with multiple rows with custom column formatting were insufficient | Improved performance of obtaining the spreadsheet document area with multiple rows with custom column formatting. |
| Spreadsheet documents. Web client. | Improved performance of spreadsheet document groups collapsing and expanding in the web client. | The collapsing and expanding of spreadsheet document groups in the web client was longer. | Improved spreadsheet document performance in the web client. |
| Background and scheduled jobs. | Improved the background jobs execution and waiting for their completion. | The background jobs execution and waiting for their completion were longer. | The background jobs execution and waiting for their completion are now faster. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Collaboration system. | Implemented the correct data area switching when a collaboration server is used. If the new data area is already registered in the collaboration server, this registration will be used. | This feature was not provided. The reconnection to the collaboration server was not performed if the data area was switched. | Eliminated unexpected system behavior. |
| Managed forms. | Changed the selected row view of the managed form table in the Taxi interface. The current row color now affects the selected row view. | The current row color did not affect the selected row view in the Taxi interface. | Improved the selected row view of the managed form table in the Taxi interface. |
| Development tools. | Modules locked with password are ignored in the Designer batch mode. A diagnostic message is displayed instead. | When modules locked with password were accessed in the Designer batch mode, the password request dialog box might be displayed. | Eliminated all interactive actions in the Designer batch mode, which does not support them. |
| Data display. | If the space is used as a group separator in the format string wizard the resulting format string the will use the nonbreaking space instead. | If the space was used as a group separator in the format string wizard the space was used in the resulting format string too. | Eliminated unexpected system behavior. Decreased number of issues caused by the incorrect group separator. |
| Collaboration system. | Implemented noncontext conversations with two participants (face-to-face). Other users can not take part in such conversations. Implemented the CollaborationSystemConversation.Group and CollaborationSystemConversationsFilter.Group properties. Implemented the capability to combine subscribers applications (infobases or data areas). Implemented the capability to match users of different applications. Implemented the capability to combine context conversations from different applications. Only the subscriber owner can perform the listed above actions. The Collaboration system management standard function can now merge applications, cancel applications merging, match users and context conversations. Implemented the CollaborationSystemUser.MappingKey property. Implemented the following methods of the collaboration system manager:
| These features were not provided. The collaboration might be established only within a single subscriber application. | Expanded the collaboration system capabilities. |
| Development tools. | Error and warnings that are generated by the metadata check, are now displayed as dbstru type messages. Implemented the DBRestuctError value for the error-type message. It describes the infobase restructuring error. Implemented the CommandFormatError value for the error-type message. It describes the invalid command format error. | Error and warnings that were generated by the metadata check, were displayed as log type messages. | Improved the diagnostics of issues that occur in the Designer agent mode. |
| Data composition system. | The composite type child fields are available in user settings if the user has the View right to at least one table of that type and the field itself. The composite type child field can be used in filters, sorting, conditional appearance and other available user settings. Implemented the RestrictGettingFieldsByRefByViewRight property of the DataCompositionProcessor.Initialize() method. This change is not implemented in version 8.3.12 compatibility mode. | If the user did not have the View right to at least one table of the composite type, there were no child fields of the locked type in the user settings. | The user can now obtain the child fields data that he has a View right on. |
| Charts. | The following options are now available in the chart type input field:
Implemented the ChartTypeChooseDialog object. This change is not implemented in version 8.3.12 compatibility mode. | The chart type input field behavior was the following:
| Improved the chart type selection in some scenarios. |
| Collaboration system. | The video call can not be performed if one of the participants do not have the microphone available. The appropriate message is generated. The collaboration system displays the microphone and camera diagnostic icons during the conversation. | The hardware diagnostics was not performed before and during the video call. | Eliminated unexpected system behavior. |
| Development tools. | The attribute or the tabular section can not be named Presentation if it is stored in the database. This change is not implemented in version 8.3.12 compatibility mode. | An attribute or a tabular section could be named Presentation, but this might cause different issues. | Eliminated unexpected system behavior. |
| Managed forms. | Implemented the following changes, when managed form tabs are displayed to the left or right of the Pages item:
| When managed form tabs were displayed to the left or right of the Pages, the tabs headers height was decreased to fit the form height. | Eliminated unexpected system behavior. |
| Managed forms. Mobile client. | The different form Auto values of managed form table HeightControlVariant property can now be used in configurations with version 8.3.7 or earlier compatibility mode. | The different form Auto values of managed form table HeightControlVariant property were used in configurations with version 8.3.10 or earlier compatibility mode. | Options of controlling the height of managed form table are now compliant with the mobile client. |
| Managed forms. Dynamic lists. | If the main table of the dynamic list has both groups and elements, the form conditional appearance is applied to columns that are not linked with the main table, regardless whether the current row displays either an element or a group of the main table. This change is not implemented in version 8.3.12 compatibility mode. | If the main table of the dynamic list had both groups and elements, the form conditional appearance was applied to columns that were not linked with the main table, in the following way:
| Eliminated unexpected system behavior. |
| Accounting registers. | If the Period adjustment property of an accounting register is greater than 0, the PeriodAdjustment standard attribute is displayed in the edit standard attributes form and becomes available in the StandardAttributes collection of the AccountingRegister metadata object (there is no PeriodAdjustment attribute in the StandardAttributes collection in version 8.3.12 compatibility mode). | The PeriodAdjustment standard attribute was not displayed in the edit standard attributes form and was not available in the StandardAttributes collection of the AccountingRegister metadata object. | Eliminated unexpected system behavior. |
| Database configuration update. | If an infobase compatibility mode is Version 8.3.10 or earlier and its database configuration was changed in 1C:Enterprise version 8.3.10 or earlier, the chance of getting a message about incomplete configuration structure conversion when opening the infobase in a client application version 8.3.13 is reduced. | If an infobase compatibility mode was Version 8.3.10 or earlier and its database configuration was changed in 1C:Enterprise version 8.3.10 or earlier, an attempt to open the infobase in a client application version 8.3.11 could not be completed. It returned a message about incomplete configuration structure conversion. The only way to recover the infobase was to open it in Designer version 8.3.11 or later and run infobase restructuring. | Smoother migration from 1C:Enterprise version 8.3.10 to later versions. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Data composition system. Charts. | The processor of data composition result output sets the automatic column width calculation for all cells in the spreadsheet document area that contains a chart. This change is not implemented in version 8.3.12 compatibility mode. | The processor of data composition result output did not set the automatic column width calculation for all cells in the spreadsheet document area that contained a chart. | Eliminated unexpected system behavior. |
| Data composition system. | If the predefined grouping templates are used during the table columns output, then the grand totals template height is automatically calculated to fit all resource headers. The template generator automatically increases the predefined grouping template height If it is less than the grand totals template height. This change is not implemented in version 8.3.12 compatibility mode. | If the predefined grouping templates were used in the table columns output and the grand totals template height was greater than the predefined grouping templates height, some resource headers might not be displayed in the grand totals template. | Eliminated unexpected system behavior. |
| Collaboration system. | Implemented the CollaborationSystemManager.IsEnabled() method. It returns the following flags:
The CollaborationSystemManager.InfoBaseRegistered() method returns whether the infobase is registered in the collaboration service and the registration is active. This change is not implemented in version 8.3.12 compatibility mode. | The CollaborationSystemManager.InfoBaseRegistered() method returned the following flags:
| You can now get the information about the infobase registration and the collaboration system availability separately. |
| Spreadsheet documents. | The spreadsheet document width and height (PageHeight and PageWidth properties) are limited to 5000 mm. This change is not implemented in version 8.3.12 compatibility mode. | The spreadsheet document width and height (PageHeight and PageWidth properties) were unlimited. | Eliminated problems of the spreadsheet document with large pages export to other formats. |
| Data composition system. | If an unavailable property of a data composition system object is accessed, an exception is thrown.
This change is not implemented in version 8.3.12 compatibility mode. | Accessing the listed above properties of the user settings objects was meaningless and did not throw an exception. | Eliminated the incorrect accessing to data composition system object properties. |
| Background and scheduled jobs. | The maximum size of serialized background job parameters is 1 GB. Otherwise an exception is thrown. If the version 8.3.12 compatibility mode is set, an exception is thrown if the size of serialized background job parameters is greater than 2 GB. | If the size of serialized background job parameters was greater than 2 GB the session was abnormally terminated. | Improved background jobs stability. Decreased the background job impact on the system performance if very large parameters were sent. |
| Dynamic lists. | The OnChange event occurs once per deleting dynamic list rows in the thin client. This change is not implemented in version 8.3.12 compatibility mode. | The OnChange event might occur multiple times when dynamic list rows were deleted in the thin client. The number of event calls depended on the deleted rows number:
| Eliminated unexpected system behavior. |
| Common objects. | The Font object constructor returns the Common style text font if the FontName constructor parameter is not specified. This change is not implemented in version 8.3.12 compatibility mode. | The Font object constructor returned Dialog and menu font if the FontName constructor parameter was not specified. | Eliminated unexpected system behavior. |
| System requirements. Linux. | The ImageMagick library from the 1C:Enterprise platform distribution package is used. | The ImageMagick library from the operating system was used. | Reduced the number of issues that might arise due to the incorrect ImageMagic library version in the operating system. |
| Managed forms. | The AddRow(), ChangeRow(), CopyRow() and EndEditRow() methods of the ManagedFormTable object do not perform any actions if their related interactive commands are not available. This change is not implemented in version 8.3.12 compatibility mode. | The behavior of the AddRow(), ChangeRow(), CopyRow() and EndEditRow() methods of the ManagedFormTable object depended on the client application type. In the thin client they performed the related actions. In the web client no actions were performed. | Eliminated unexpected system behavior. |
| Development tools. | The English version of ID, attribute name and metadata object name is now saved in the configuration merge settings file. The following actions are performed when reading the configuration merge settings file: attempt to read IDs in English. If failed, attemt to read IDs in Russian. | The version of ID, attribute name and metadata object name that were saved in the configuration merge settings file, depended on the configuration script variant. | The result of the configuration merge settings loading does not depend on the configuration script variant. |
| Web client. File operations. | Improved web client file operations. Implemented the new file selection dialog box. It supports multiple file choice and dragging. The file system extension is not required for this dialog box. Implemented the limited editing of the file selection dialog box BeginPutFile() and BeginPuttingFiles() methods. The BeginPutFile() method does not require the file system extension installed. Added the option to manage specific parameters of files before transfering them to server. Implemented the BeforeBeginPuttingFilesNotificationDescriprion parameter of the BeginPutFile() and BeginPuttingFiles() methods. Implemented the FullName and FileID properties of the TransferredFileDescription object. The Name property of the TransferredFileDescription contains only the transferred file name. The BeginPutFile() method allows other calls and methods in the thin client. This change is not implemented in version 8.3.12 compatibility mode. You can now drag files on the following form items: managed form field extension for a picture, managed form decoration extension for a picture, and managed form table. Implemented the FileDragMode property of the listed above managed form items. Implemented the FileRef object. The PutFile(), PutFiles(), and GetFiles() methods are deprecated. It is recommended to rework file operations in applications that use the web client. | The file operations in the web client were limited if the file system extension was not installed. In the thin client, while the BeginPutFile() method was being executed, calls of other methods were not allowed. The TransferredFileDescription.Name property contained the full file name. | Expanded the file operations in the web client that do not require the file system extension installed. The web client supports and handles the file dragging. |
| Charts. | If the chart data contains non-numeric values (NULL or Undefined), the chart behavior can be specified. Implemented the NonnumericValueUse and PointsConnectionAcrossSkippedValues properties of the Chart object. Implemented the ChartType.NonnumericValueUse and ChartType.PointsConnectionAcrossSkippedValues properties of the following objects: DataCompositionOutputParameterValues, DataCompositionChartOutputParameterValues, DataCompositionAreaTemplateChartAppearance. If displaying of a series marker is disabled (ChartMarkerType.None is set) and a series value in some point is separated (values in the next and previous points are omitted), then this value is displayed as a circle. The width of the circle line equals to the series line width. Chart lines connections are now rounded. This change is not implemented in version 8.3.12 compatibility mode. | The chart behavior could not be specified if the chart data contained non-numeric values. If displaying of a series marker was disabled (ChartMarkerType.None was set) and a series value in some point was separated (values in the next and previous points were omitted), then this value was not displayed on a chart. The chart lines connection was not rounded. | Expanded operations with charts. |
| Automated testing. | The TestedFormTable.Expand() method can now expand subordinate nodes on the next level of the selected node only. Implemented the WithSubordinates parameter of the TestedFormTable.Expand() method. This change is not implemented in version 8.3.12 compatibility mode. It is recommended to review and rework all code fragments with the TestedFormTable.Expand() method. | The TestedFormTable.Expand() method expanded the selected node and all subordinate nodes. | The automated testing features now correspond the 1C:Enterprise platform capabilities. |
| Data composition system. Dynamic lists. External data sources. | If a dynamic list field in a report may be NULL, the following ordering rule is applied to that field: NULL values come first. If a dynamic list field is based on an external data source table field, and the external data source contains the CASE ... WHEN selection that might return NULL, the following ordering rule is applied to that field: NULL values come first. This change is not implemented in version 8.3.12 compatibility mode. | If a dynamic list was ordered by a field that might be NULL , rows with NULL and with the default field type value were placed together. If a dynamic list was ordered by a field that was based on the external data source table of any type, the final ordering depended on the DBMS type. | Dynamic list ordering by the field that might be NULL rule is now the same as the other objects ordering rule. |
| Managed forms. | When the AutoMarkIncomplete property of a managed form table is set to True, the MarkIncomplete property of that table obtains the correct value after the script execution. This change is not implemented in version 8.3.12 compatibility mode. | The MarkIncomplete property of a managed form table was refreshed only when the table was refreshed or the current table cell was changed. | Eliminated unexpected system behavior. |
| Queries. | The IS NULL function returns FALSE if it is applied to the combination of virtual fields. The IS NULL function returns TRUE if it is applied to the combination of virtual fields and the expression without virtual fields that returns NULL. The IS NULL function returns FALSE if it is applied to the combination of virtual fields and the expression without virtual fields that does not return NULL. This change is not implemented in version 8.3.12 compatibility mode. It is recommended to review all IS NULL functions in existing applications. | The IS NULL function returned FALSE if it was applied to the combination of virtual fields or to the combination of virtual fields and the expression without virtual fields. | Eliminated unexpected system behavior. |
| File operations. Server clusters. | If a security profile that blocks access to the file system is set in the infobase, the TempFilesDir() and GetTempFileName() global context methods return paths with separators, provided by the current operating system. | If a security profile that blocked access to the file system was set in the infobase, the TempFilesDir() and GetTempFileName() global context methods returned paths with separators, provided by the Linux operating system. | Eliminated unexpected system behavior. |
| File operations. | If the parameter of the following File object methods is set to date before the January 1, 1601 in the Windows operating system, these methods throw the File access denied exception:
All errors of File object methods throw the same exception. | If the parameter of the following File object methods was set to date before the January 1, 1601 in the Windows operating system, these methods returned the random date:
| Eliminated unexpected system behavior. |
| Data composition system. | If the CASE operation is used in the data composition system calculated expression, and the resulting field type is unknown (it is a values table field or the field type is not specified) and the ELSE section contains the Undefined value, the result field type in the result values collection will be set to Custom (the type description will be blank). This change is not implemented in version 8.3.12 compatibility mode. | If the CASE operation was used in the data composition system calculated expression, and the resulting field type was unknown (it was a values table field or the field type was not specified) and the ELSE section contained the Undefined value, the result field type in the result values collection would be NULL. | Eliminated unexpected system behavior. |
| Managed forms. | Only methods with the Export keyword are available in expressions containing ThisObject. This change affects from module as well as other modules, where ThisObject is passed. This change is not implemented in version 8.3.12 compatibility mode. | All methods were available in expressions containing ThisObject. | Eliminated unexpected system behavior. |
| Data composition system. | If a filter with the filled/not filled comparison type is used in the data composition system settings and this filter is applied to the calculated field, which type is custom, Characteristics type, or any reference type, then the filter will consider types, included in the Characteristic, custom type or any reference type. This change is not implemented in version 8.3.12 compatibility mode. | If a filter with the filled/not filled comparison type was used in the data composition system settings and this filter was applied to the calculated field, which type was custom, Characteristics type, or any reference type, then the filter ignored types, included in the Characteristic, custom type or any reference type. | Eliminated unexpected system behavior. |
| Queries. | If a temporary table is created by the INTO clause, the temporary table field with NULL value has a compound data type. This compound data type includes the following types:
It is recommended to review all temporary table fields that might have NULL value. This change is not implemented in version 8.3.12 compatibility mode. | If a temporary table was created by the INTO clause, the temporary table field with NULL value had NULL type. | Temporary table fields with NULL values are now available in expressions that do not support NULL value. The CAST() function can be used in such cases. |
| Functional options. | If a functional option value is stored in a periodic information register resource, it is obtained from the slice last. The date from the functional option Period parameter, or the current date (if the functional option Period parameter is not specified) is used as a slice last date. This change is not implemented in version 8.3.12 compatibility mode. | If a functional option value was stored in a periodic information register resource, it was calculated by the logical OR operation across all stored resource values, if only the Period parameter was specified. | Eliminated unexpected system behavior. The system behavior is now compliant to documentation. |
| Managed forms. | Managed form table rows are filtered if there are multiple filter items and the first item filter value is Undefined. This change is not implemented in version 8.3.12 compatibility mode. | Managed form table rows were not filtered if there were multiple filter items and the first item filter value was Undefined. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile device-specific features. | Push notifications on Android use Firebase Cloud Messaging service. It is recommended to transfer push notifications to this platform in current applications. Implemented the DeliverableNotificationSubscriberType.FCM enumeration value. The Google Cloud Messaging service is supported for compatibility purposes and is not recommended for use. The DeliverableNotificationSubscriberType.GCM value is obsolete and supported for compatibility purposes. The GoogleCloudApplicationNumber parameter of the ReceiveNotificationSubscriberID() method is optional on Android. | Push notifications on Android used Google Cloud Messaging service. | The legacy push notifications delivery service is no longer used. Transfered to the latest version of the service. |
| Mobile device-specific features. Mobile platform. Mobile client. | Implemented the capability of managing the camera backlight interactively (on Android and Windows Phone) and from the 1C:Enterprise script (on all mobile operating systems). Implemented the DeviceTools global context property. Implemented the CameraBacklightType parameter of the MultimediaTools.MakePhoto() method. You can now use a camera flash as a flashlight. Implemented the DeviceTools global context property. Implemented the FlashlightSupported() and TurnFlashlightOn() methods of the device tools manager. | Managing the camera backlight from the 1C:Enterprise script was not available. Interactive managing of the camera backlight was available only on iOS. There was no option to use a camera flash as a flashlight. | Extended the mobile device camera operations. |
| Spreadsheet documents. Mobile platform. | A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC. | A PDF type document generated on the mobile platform was less similar to the same PDF type document generated on PC. | A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC. |
| Mobile device-specific features. Mobile client. Mobile platform. | Implemented acquiring purchase receipts feature in 1C:Enterprise mobile version. It is now available to validate the purchase receipt on a mobile device. Implemented the following InAppPurchasesManager object methods:
The InAppPurchasesManager object is now available in the mobile client and in the mobile platform client. Implemented the InAppPurchasesValidationManager.ValidateInAppPurchaseReceiptAtMobileDevice() method on the mobile client and on the mobile platform client. The global context InAppPurchasesValidation property is now available on the mobile client and on the mobile platform client. Acquiring the list of internal purchases is now available in the mobile application builder purchase emulator. | Acquiring purchase receipts feature was not available. The InAppPurchasesValidationManager object and the InAppPurchasesValidation global context property were available only on the server of the PC platform. | Improved the internal purchases feature, provided by the appropriate application store. |
| Mobile platform. | Implemented the following form control properties:
Implemented input hints for multiline input fields. | These features were available in the mobile client only. | Managed forms are now displayed the same way in different 1C:Enterprise mobile versions. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Interface. | In Taxi interface the command check in the menu now displays the same way in different displaying options and different client application types. | The command check in the menu could be different depending on displaying options and client application types. | The command check in the menu now displays the same way. |
| Data composition system. | If a filter is added to a query of composition schema data set that includes union, this filter is added to every part of the union. If a particular union part does not contain a field that is used in the filter, this field is replaced by NULL. This change is not implemented in version 8.3.12 compatibility mode. | If a filter was added to a query of composition schema data set that includes union, this filter was added to parts of the union that contained the field that was used in the filter. | Unified filter operations in data composition system between the union data set and query data set, where the query contained a union. |
| Internet-enabled functionality. | The parameters of the following FTPConnection object methods were renamed in the Syntax Assistant: Get() and Put(). This change is available in the Syntax Assistant only. | The parameters of the following FTPConnection object methods were different in the Syntax Assistant: Get() and Put(). | The names of the FTP methods parameters became more clear. |
| Mobile device-specific features. Mobile platform. Mobile client. | The DeliverableNotification.Title value is now displayed when a notification is shown on iOS version 8.2 and later mobile device. | The DeliverableNotification.Title value was available on Android only. | Improved notifications on iOS. |
| Collaboration system. Mobile platform. Mobile client. | The collaboration system notifications now contain the sender name. The noncontext conversation title is displayed in the notification title. | The collaboration system notifications did not contain the sender name. The noncontext conversation title was displayed both in the notification title and text. | Improved collaboration system notifications. |
| Internet-enabled functionality. | macOS certificate store is now supported. New objects: MacOSCertificationAuthorityCertificates, MacOSCertificateSelectMode, and MacOSClientCertificate. macOS certificate store support is added to object OSCertificationAuthorityCertificates. New -macos parameter for /HttpsCA and /HttpsCert command-line options of the client application. New technological log event: <MACCERT>. | macOS certificate store was not supported. Secured connection was only available if certificates were stored in files. | You can use the system certificate store to establish secured connection on macOS. |
| Collaboration system. | The client application agent supports multiple versions of the collaboration system server's exchange protocol. New 1ceclac application is provided. The client application agent's directory structure is changed. | The client application agent supports a single version of the collaboration system server's exchange protocol. | The client application agent supports the previous versions of the collaboration system server's exchange protocol. |
| Dynamic lists. | The following restrictions apply to search in dynamic lists:
If the search string does not comply with the listed requirements, an exception is generated. For details on splitting the search string into words, see 1C:Enterprise documentation. | There were no restrictions to search in dynamic lists. | Improved application server reliability when searching in dynamic lists. |
| Dynamic lists. Data composition system. | When opening report forms or dynamic list forms, if user settings are not available in the storage, the system performs the following actions:
New UseDefaultSettings parameter for BeforeLoadUserSettingsAtServer and OnLoadUserSettingsAtServer event handlers. The Set default settings command of report and dynamic list forms performs the following actions:
Method DataCompositionSettingsComposer.Refresh() with parameter DataCompositionSettingsRefreshMethod.Full performs the following actions: sets the Use flag to False for main settings items that lost their linking to available fields, and deletes items of main settings and user settings that are marked as user settings but contain fields absent from the collection of available fields or not available for the current functional options and rights. This change is not implemented in version 8.3.12 compatibility mode. | When opening report forms or dynamic list forms, if user settings were not available in the storage, the system performed the following actions:
The Set default settings command of report and dynamic list forms had the following behavior:
Method DataCompositionSettingsComposer.Refresh() with parameter DataCompositionSettingsRefreshMethod.Full set the Use flag to False for main settings items that lost their linking to available fields. | Unavailable fields cannot be added to the default user settings of reports or dynamic lists. |
| Data analysis. | If a data set contains an even number of elements, its median is calculated as the arithmetic mean of the two middle elements of the ordered set. In particular, this rule applies to data sets that contain two elements. This change is not implemented in version 8.3.12 compatibility mode. | If a data set contained an even number of elements, its median was calculated as follows:
| Eliminated unexpected system behavior. |
| Internet-enabled functionality. | For SMTP operations, added support of NOTIFY parameter of RCPT command and RET parameter of MAIL command. This provides support for mail delivery receipts described in RFC 1891. InternetMailMessage.DeliveryReceiptAddresses property is deprecated. This property is only available in Version 8.3.12 compatibility mode. Note that some SMTP server implementations or some of their settings can prevent receiving mail delivery receipts. It is recommended that you do not use DeliveryReceiptAddresses property of InternetMailMessage object. Use the following properties instead:
| Instead of delivery receipts, read receipts were generated. | Eliminated unexpected system behavior. Both delivery and read receipts are now available. |
| Internet-enabled functionality. | If a mailbox does not contain any messages matching the IDs specified in the parameter of InternetMail.GetMessagesFlags() method, the method returns a blank map. This change is not implemented in version 8.3.12 compatibility mode. | If a mailbox did not contain any messages matching the IDs specified in the parameter of InternetMail.GetMessagesFlags() method, the method generated an exception. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | An attempt to save a spreadsheet document with pictures in 1C:Enterprise 7.7 format on a server or in an external connection generates an exception. Only spreadsheet documents without pictures can be saved in this format. | An attempt to save a spreadsheet document with pictures in 1C:Enterprise 7.7 format on a server or in an external connection resulted in generation of a corrupted document that could not be opened. | Eliminated unexpected system behavior. |
| Managed forms. | If the Width property of a form field is not 0 and horizontal stretching is not applied, this property defines the field width without the input field buttons (Select, Clear, and others). The resulting field width is equal to the sum of the Width value and all button widths. This change is not implemented in version 8.3.12 compatibility mode. | If the Width property of a form field was not 0 and horizontal stretching was not applied, this property defined the field width as follows:
Thus, adding or removing input field buttons could change the field width. | Eliminated unexpected system behavior. |
| Collaboration system. | If several applications share a collaboration server, the message counter of the client application agent is incremented once per message. | If several applications shared a collaboration server, the message counter of the client application agent was incremented several times (once per application). | Eliminated unexpected system behavior. |
| Add-ins. macOS. | Client applications running on macOS now support add-ins based on Native API. The add-in technology documentation and examples are updated accordingly (read more). | Client applications running on macOS did not support add-ins based on Native API. | Client applications running on macOS now support add-ins. |
| Add-ins. Mobile platform. Mobile client. | For add-ins intended to run on iOS, you can specify a set of properties to be included in the application properties (file info.plist). The properties required by the add-in are added by the Mobile application builder. The add-in technology documentation is updated. (read more) | This feature was not provided. Add-ins could not add properties to the info.plist file. | Development of add-ins intended to run on iOS is more convenient. |
| Collaboration system. Client application. | When a collaboration system notification is deleted from the notification center, the conversation is marked as read. Deleting a notification here means either deleting a single notification or clearing the notification list. | When a collaboration system notification was deleted from the notification center, the conversation was not marked as read. Deleting a notification here means either deleting a single notification or clearing the notification list. | The collaboration system behavior is more logical and predictable. |
| Data composition system. XML and XDTO support. | When XDTO deserialization is applied to data composition parameters, only parameters that are included in the list of the available parameters of the current platform version are deserialized. No deserialization attempts are performed for parameters that are not included in the list of available ones. This ensures successful restoration of parameters. | When XDTO deserialization was applied to data composition parameters, the platform attempted to deserialize all of the serialized parameters. Attempts to restore data composition settings using an earlier platform version where the list included parameters unavailable in the current version generate errors. | You can use an earlier platform version to restore data composition schemas and data composition settings saved in a later platform version. At that, data composition parameters available only in the later version are ignored. |
| Mobile client. Server clusters. Data history. | If mobile client version 8.3.12 is connected to a 1C:Enterprise server 8.3.13:
If mobile client version 8.3.13 is connected to a 1C:Enterprise server 8.3.12, an attempt to view the change history always opens the default change history form. | If mobile client version 8.3.12 was connected to a 1C:Enterprise server 8.3.13, the change history was unavailable. | Eliminated unexpected system behavior. |
| DBMS operations. System requirements. | PostgreSQL version 10.3 is supported. | PostgreSQL version 10.3 was not supported. | Extended list of supported DBMS. |
| Managed forms. Client application. | If a form table does not have a current row (for example, it is blank) and a column group is hidden from the table header, its parent column group is also hidden from the header. If a form table has a current row and a column group is shown in the header, its nested column group is shown in the header only if the current row contains cells that belong to the nested group. This change is not implemented in version 8.3.12 compatibility mode. | If a form table did not have a current row (for example, it was blank) and a column group was hidden from the table header, its parent column group was shown in the header as a blank column. If a form table had a current row and a column group was shown in the header, its nested column groups were always shown in the header. | Eliminated unexpected system behavior. |
| Data composition system. | Predefined resource templates that describe intersections of table row groupings (template type: Title or Footer) with table column groupings (template type: Grand Total Title or Grand Total Footer) are displayed in a report even if the resource fields are not displayed in the table columns. This change is not implemented in version 8.3.12 compatibility mode. | In data composition system tables, if resource fields were not displayed in table columns, predefined resource templates were not displayed for row totals. | Eliminated unexpected system behavior. |
| Data history. | In a data structure that is generated by the DataHistoryManager.GetVersionDiff() method and describes moving a table row:
This change is also applied to the standard version difference report. | In a data structure that was generated by the DataHistoryManager.GetVersionDiff() method and described moving a table row:
| Eliminated unexpected system behavior. The row numbering is now more intuitive. |
| Cryptography support. | An interactive mode of password-related operations is implemented for the cryptography manager. If the cryptography manager is initialized in the interactive mode, the password to access the private key that is defined in the object is ignored, and the user is asked to enter the password. The option to remember the password is implemented. The interactive mode of the cryptography manager is supported only on the client. An attempt to use the interactive mode on the server generates an error. InteractiveModeUse parameter is implemented for CryptoManager constructor and CryptoManager.BeginInitialization() method. We recommend that you analyse the cases where the cryptography manager is used and implement interactive mode on the client to improve the user experience. | The only way to specify the password to access a private key was through the cryptography manager property. Users could not set the password themselves. | More secure and user-friendly mode of managing private key passwords is implemented. |
| Managed forms. | If a form input field contains modified data and it is not the current form item, an attempt to set its Visible, Enabled, or EditText property to False or set its ReadOnly property to True results in the following:
If a form input field contains unmodified data and it is not the current form item, an attempt to set its Visible, Enabled, or EditText property to False or set its ReadOnly property value to True results in closing the drop-down list (if the list was open). This change is not implemented in version 8.3.13 compatibility mode.
| Setting the Visible property of an input field to False results in the following:
| Eliminated unexpected system behavior. |
| Mobile client. Internet-enabled functionality. | Mobile clients can connect to infobases over HTTPS. The infobase access parameters of the mobile client now include the client certificate source and the server certificate verification options. The client certificate source can be an application certificate store or a file (for iOS and Android). The source of root certificates for server certificate verification can be a system certificate store, application certificate store, or file (for iOS and Android). | This feature was not provided. | Added new mobile client features. |
| Mobile client. Managed forms. | In the mobile client, customization of form command bars is implemented. A new form property: MobileDeviceFormCommandBarContent. In the mobile client, the property content (unless it is blank) is displayed in the form command bar, replacing the default command bar. Including a form command bar into the MobileDeviceFormCommandBarContent property content is not supported. If a form group title is defined but not displayed, the title is considered when generating the title of an automatically collapsed group on the mobile client. | In the mobile client, form command bar customization was not supported. If a form group title was defined but not displayed, the title was not considered when generating the title of an automatically collapsed group on the mobile client. | Form customization on the mobile client is upgraded. |
| DBMS operations. System requirements. | PostgreSQL version 10.5 (for 32-bit and 64-bit operating systems) is supported. | PostgreSQL version 10.5 was not supported. | Extended list of supported DBMS. |
| Mobile client. Collaboration system. | New features for the mobile client:
New objects supported by the mobile client:
The version of the collaboration system on the mobile client is defined by the collaboration system version on the 1C:Enterprise server. Mobile client collaboration system features are defined by the collaboration system version on the 1C:Enterprise server and do not depend on the server version. | These features were not provided. | The collaboration system features on the mobile client match the features on the thin client. |
| System requirements. Mobile platform. Mobile client. | The mobile version of 1C:Enterprise supports Android 9, iOS 12, and the following Apple devices: iPhone Xs, Xs Max, and Xr. | The mobile version of 1C:Enterprise did not support Android 9 and iOS 12. The mobile version of 1C:Enterprise did not support iPhone Xs, Xs Max, and Xr. | 1C:Enterprise supports new operating systems and devices. |
| Mobile application builder. | New: now you can manage permissions of mobile applications running under Android OS even more accurately if it is required to grant Telephony permission in the application. If the permission is required, then the builder prompts you to define which permission out of 6 ones is required by the mobile application. | If the application required the Telephony permission, the mobile application builder provided the mobile application with 6 permissions at once. | Requirements for permissions that appeared in a new edition of Google Play developer rules are considered. Now you can define only the permissions required by the mobile application. |
| System requirements. DBMS operations. | Support of the following Postgres Pro DBMS versions is implemented:
| The following Postgres Pro DBMS versions were not supported:
| Extended list of supported DBMS. |
| Localization. | Localized client application interface for Spanish (es). | This feature was not provided. | 1C:Enterprise is available to Spanish-speaking users. |
| Localization. | Localized client application interface for Greek (el). | This feature was not provided. | 1C:Enterprise is available to Greek-speaking users. |
| HTML support. | Upon reading an HTML document using the HTMLReader object (using the OpenFile(), OpenStream(), and SetString() methods), document parsing will be stopped when the nesting reaches 1,024 tags. The user will get access to a part of the document only. | Upon reading an HTML document using the HTMLReader object, there were no restrictions on the number of nested tags, which might lead to abnormal shutdown. | Upgrade: better system reliability upon parsing HTML documents with high tag nesting. |
| DBMS operations. | The following DBMS are now supported (64-bit versions only):
| These PostgresPro DBMS versions were not supported. | More PostgresPro DBMS versions are now supported. |
| System requirements. DBMS operations. | Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
| The following Postgres Pro DBMS versions were not supported:
| Extended list of supported DBMS. |
| Mobile platform. | When creating a secure OpenSSL connection, server certificate validation is performed using the certificates installed on the mobile device if the value of the CertificationAuthorityCertificates parameter of the OpenSSLSecureConnection constructor is Undefined or is of the OSCertificationAuthorityCertificates type. | When creating a secure OpenSSL connection, server certificate validation was not performed if the value of the CertificationAuthorityCertificates parameter of the OpenSSLSecureConnection constructor was Undefined or was of the OSCertificationAuthorityCertificates type. | Eliminated unexpected system behavior. |
| System requirements. DBMS operations. | Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
| The following Postgres Pro DBMS versions were not supported:
| Extended list of supported DBMS. |
Version 8.3.12 includes known bug fixes and functionality modifications.
Before adapting an application to the mobile client, we recommend that you read the ITS article Read more..
Finished the beta testing of the application debug by HTTP protocol option.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.11 is now implemented. | Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.10 was implemented. | Configurations developed using 1C:Enterprise platform version 8.3.11 or earlier can run on version 8.3.12 without any changes to configuration or to data structures. This allows for transition to version 8.3.12 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.11 after the transition to version 8.3.12, even if you disabled the compatibility mode (if you did, enable it again). |
| Client application. | On 64-bit Windows, you can set the bitness of a client application at application startup. In the Startup window settings dialog box, the option to specify the application bitness is implemented. This value is stored to the DefalutVersion parameter of 1CEStart.cfg file. In the infobase properties, the option to specify the bitness of the client application used with this infobase is implemented. This value is stored to the AppArch parameter of ibases.v8i file. The command-line option /AppArch is implemented for the thin and thick client applications. | This feature was not provided. On 64-bit Windows, users could not select the bitness of client applications. | On 64-bit Windows, the option to select the bitness of a client application is implemented. You can explicitly specify a 32-bit application in scenarios where a 64-bit application cannot work properly (for example, in a scenario where 64-bit add-ins are not available). |
| Configuration extensions. | The option to select the application area of configuration extensions, as well as activate or deactivate them, is implemented. The following application areas are available: the current data area and the entire infobase. When an extension is deactivated, it is not deleted from an infobase. For ConfigurationExtension object, implemented Scope and Active properties. The extension activation order is changed. Extensions that are applied to the entire infobase are activated first. | These features were not provided. Extensions were always attached to specific data areas. Disabling extensions without deleting them was not available. | More configuration extension management options. You can add configuration extensions to all of the infibase data areas at once. You can use this feature to apply hotfixes. |
| Collaboration system. | Automatic conversion of character sequences to pictures ("smileys") is implemented. Sound alerts for the following events are implemented: new message, incoming call, waiting for reply to a video call, and end of video call. Links to conversations, getting links to conversations, and opening links to conversations (both interactively and using GotoURL() method) are implemented. The option to add such links to Favorites is implemented. The option to get presentations of such links using GetURLsPresentations() method is implemented. In conversation messages, links to conversations are displayed as hyperlinks. In the thin and thick clients for Windows, taskbar blinking upon receiving a notification is implemented. In the main collaboration system form, a context menu is implemented for the conversation list. A context menu is implemented for collaboration system messages. For noncontext conversations, service collaboration system messages are implemented for the following events: conversation topic changed, a user joined/left a conversation. The search ignores service messages. The conversation participant list view is changed. Special marking for unsent outgoing messages is implemented. The collaboration system settings dialog box is implemented. The user picture (avatar) editor is implemented. The message list view is changed. | These features were not provided. | Improved collaboration system usability. |
| Data history. | Support of data history for charts of accounts and charts of characteristic types is implemented. For ChartOfAccountsObject and ChartOfCharacteristicTypesObject objects, methods SetDataHistoryVersionComment() and GetDataHistoryVersionComment() are implemented. | This feature was not provided. | Data history is now available for more objects. |
| Configuration extensions. | For native and adopted extension objects, the option to generate records in all adopted registers is implemented, except for turnover accumulation registers with aggregates. | This feature was not provided. Extension documents could generate records only in native information registers available in the extension. | Extended configuration extension capabilities. |
| Configuration extensions. Development tools. Settings storage. | The option to store configuration extensions in configuration repositories is implemented. All of the Designer batch mode command-line options that are related to configuration repositories support configuration extensions. For Designer batch mode, the following changes are implemented:
| This feature was not provided. Configuration extensions could not be stored in configuration repositories, making development unnecessarily complicated. | Simplified group development and versioning of configuration extensions. |
| Configuration extensions. | Creation of enumerations in configuration extensions is now supported. | This feature was not provided. | Extended configuration extension capabilities. |
| Internet-enabled functionality. | Moving email messages between IMAP mailboxes is now supported. Method InternetMail.MoveToMailbox() is implemented. Getting and setting flags of IMAP email messages is implemented. For InternetMail object, methods GetMessageFlags() and SetMessageFlags() are implemented. | These features were not provided. | Extended support of IMAP email operations. |
| Charts. Data composition system. | Highlighting specific chart intervals and values is implemented. This feature is available for the following chart types: stock, open-high-low-close, all types of column charts, all types of bar charts (except for bar graph), line, step, stacked line, area (all types), scatter, bubble, radar (all types), and gauge.
For Chart object, the following properties are implemented: ColorPaletteDescription, DataIntervalsColorPaletteDescription, ValueDataLines, PointDataLines, ValueDataIntervals, and PointDataIntervals. For ChartLabelArea, the following properties are implemented: Orientation and Angle. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, the following parameters are implemented: ChartType.ColorPaletteDescription, ChartType.DataIntervalsColorPaletteDescription, ChartType.ValueDataLines, ChartType.PointDataLines, ChartType.ValueDataIntervals, and ChartType.PointDataIntervals. The following properties and methods of Chart object are obsolete and not recommended for use: ColorPalette, GradientPaletteStartColor, GradientPaletteEndColor, GradientPaletteMaxColors, GetPalette(), and SetPalette(). | This feature was not provided. | Additional chart layout features are introduced. |
| Spreadsheet documents. | Implemented representable document batch export to the following formats: XLS (Microsoft Excel 97-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later), and ODT (OpenDocument). You can export each spreadsheet document of the batch to a separate sheet of the resulting document. Implemented RepresentableDocumentBatchItem.Title property. Use it to specify the sheet name. Implemented Write() and BeginWriting() methods of RepresentableDocumentBatch object. | This feature was not provided. | You can save several 1C:Enterprise spreadsheet documents to the resulting XLS, XLSX, or ODT document. |
| Full-text search. Server clusters. Technological log. | In client/server mode, the option to set the number of background jobs that update the full-text search index is implemented. You can use requirements of functionality purpose to set the number of background jobs that update the full-text search index. For FullTextSearchManager object, the following methods are implemented: SetIndexingJobsCount() and GetIndexingJobsCount(). For FTEXTUpd technological log event, the following properties are implemented: MinDataId, MemoryUsed, BackgroundJobCreated, JobCanceledByLoadLimit, TotalJobsCount, and FailedJobsCount. | This feature was not provided. The update of the full-text search index was always performed as a single background job. | Improved performance of full-text search index updates (especially in scenarios with full index rebuilding). |
| Configuration extensions. Distributed infobases. | Support of configuration extensions in distributed infobases is implemented. For exchange plans, IncludeConfigurationExtensions property is implemented. For configuration extrensions, UseInDistributedInfobase and MasterNode properties are implemented. | This feature was not provided. | Extended configuration extension usage options. You can manage the replication of configuration extensions in distributed infobases. |
| Charts. | In charts, the option to manage automatic calculation of header, legend, and plot area sizes and positions is implemented. For ChartLegendArea, GanttChartLegendArea, PivotChartLegendArea, ChartPlotArea, GanttChartPlotArea, PivotChartPlotArea, ChartTitleArea, GanttChartTitleArea, and PivotChartTitleArea objects, property Placement is implemented. Property ShowLegend of Chart, GanttChart, and PivotChart objects is deprecated. Property ShowTitle of Chart, GanttChart, and PivotChart objects is deprecated. | Charts only provided the option to manage header and legend view. | Improved chart customization options. |
| Queries. | In the query language, extended support of UUID and ValueStorage types. The option to create temporary tables based on value tables that contain columns of these types is implemented. The option to use fields and expressions of UUID type in queries where IN is applied to a selection of multiple fields is implemented. | This feature was not provided. | Extended query language capabilities. |
| Data composition system. | In data composition settings, the option to use a period addition in scenarios where the reporting period does not match a regular calendar period is implemented. You can specify month size, either a calendar month or "4-5-5". In the latter case, a year is divided into 4 quarters. Each quarter has two 4-week months and the third 5-week month.
For system enumeration DataCompositionPeriodAdditionType, the following values are implemented:
| The data composition system always used period additions based on calendar beginning of quarter or year. | Simplified reporting in scenarios where the reporting period does not match a regular calendar period. |
| Managed forms. | For managed forms, collapsible pop-up groups are implemented. When a pop-up group is collapsed, a form displays its title; clicking the title opens a pop-up window, which contains all of the group items. In a form, you can view the content of a single pop-up group at a time. The option to toggle the state of collapsible and pop-up groups from 1C:Enterprise script is implemented. The following system enumeration value is implemented: UsualGroupBehavior.PopUp. For managed form group extensions for usual groups, the following methods are implemented: IsHidden(), Show(), and Hide(). For managed form group extensions, HiddenViewTitleBackgroundColor property is implemented. | These features were not provided. | New options for grouping managed form items. |
| Database configuration update. | In the optimized restructuring mechanism (version 2), added the support of restructuring configuration objects having at least one extension (that extends data) attached in any of the data areas. This is only applicable to restructuring main database configurations. Restructuring that is performed during extension updates does not use the optimized restructuring mechanism (version 2). | This feature was not provided. For main database configurations, if any of the areas had an extension (that extended data) attached, the regular restructuring mechanism (version 1) was used. | Improved interaction between platform mechanisms. |
| Automated testing. | For TestedFormField objects that represent form items of radio button, input field, and label (with hyperlink flag set) types, method GetDisplayedText() is implemented. It gets the text displayed on the item. For TestedFormField objects that represent form items of radio button and input field types, method GetChoiceListPresentation() is implemented. It gets a fixed array that contains presentations of the form item choice list. | This feature was not provided. | Extended automated testing capabilities. |
| Mobile client. | Implemented the mobile client, which is equivalent to the thin client running on a mobile device. Its interface is similar to mobile platform interface. The mobile client supports only HTTP connections to infobases. It does not support TCP connections. The exact match between the mobile client version and the server (or the web server extension) version is not required. The mobile client provides online access to the majority of the features available in the thin client and in the web client. The mobile client supports all mobile device-specific features, such as camera, location, and notifications. The collaboration system uses push notifications to deliver messages. Messages are delivered even if applications that generated them are not running or inactive. Mobile client applications are always built to run with a specific list of configurations. Changing the assortment of configuration objects in an infobase connected to a mobile client application is not supported. You can modify a configuration without modifying the assortment of its objects. If the assortment of objects changes, you have to republish the mobile application. A mobile client application cannot run with configurations that are not in the list because of application store requirements. The mobile client uses digital configuration signatures to check whether a configuration is in the list. Implemented automatic adjustment of configuration forms to mobile device screens. You can use new form item properties to modify the adjustment rules. In the managed form editor, implemented the form preview for mobile client mode. In the mobile client, the list of home page forms is identical to that of the thin and web clients (but different from the list of home page forms of the mobile platform). When you start an application, it displays the first form in the list, while the other forms are available through a menu. The mobile client supports add-ins. The mobile client does not support interactive opening of external reports and data processors. The mobile client can run configurations with compatibility mode Version 8.3.7 or later. In Designer, implemented commands for interactive start of the mobile client on a mobile device. The mobile application builder can now build mobile client applications. You can select the type of application to build: a mobile client application or a mobile platform application. Implemented MobileClient access right. Implemented MobileClient preprocessor command. In the Syntax Assistant, implemented a new availability option for objects, properties, and methods. For managed forms, implemented CollapseItemsByImportance property. For managed form items, implemented DisplayImportance property. It affects the adjustments of the form layout. For managed form tables, implemented CurrentRowUse and BehaviorOnHorizontalCompression properties. For form groups, implemented CurrentRowUse and AssociatedTable properties. For Designer batch mode, implemented the following command-line options and parameters: MobileClientWriteFile and MobileClientDigiSign options -MobileClient parameter for CheckModules and CheckConfig options -MobileClientDigiSign parameter for CheckConfig option Changed the content of the mobile platform distribution package (mobile.zip). Now it contains the mobile client files required to develop and build mobile applications, as well as distribute them through application stores. This feature is included for beta testing purpose only. | This feature was not provided. The mobile platform was capable of running specialized offline applications. | Mobile devices can be used in the new way now. You can now work online with all application features that were available on the thin client and on the web client without the significant configuration refactoring. |
| Administration tools. | In Designer batch mode, for command-line options CreateDistributionFiles and CreateDistributive, implemented parameter WarningAsError. | This feature was not provided. | You can apply stricter validation rules (treat all warnings as errors) to generation of application distribution kits. |
| Server clusters. | Implemented new values for session and connection attributes. They indicate the duration of cluster service calls initiated by a session or a connection. They are available in all administrative tools: the cluster console, COM connection, Java administrative API, and the administration server. Implemented the following IInfoBaseConnectionInfo object and ISessionInfo object properties:
Added the same attributes to the session list, connection list, and the connection properties dialog box in the cluster console. Added the following parameters of connection list commands and session list commands for the cluster service command-line utility (rac): duration-current-service, current-service-name, duration-last-5min-service, and duration-all-service. | This feature was not provided. | The duration of cluster service calls initiated by a specific connection or a specific session is now available. |
| System requirements. Client application. | The client application for Linux needs the 1.4.3 version or higher of the webkitgtk-3.0 library installed. | The client application for Linux needed the 1.4.3 version or higher of the webkitgtk-1.0 library installed. | Unified the Linux and MacOs client applications operation. |
| Add-ins. | Implemented the new global context method DynamicAddInInstallationSupported(). It shows whether the add-in loading is available from the current infobase. The dynamic add-in loading is available only on Android mobile devices. Otherwise add-ins should be included in the mobile application and are available only from the Add-in type configuration templates. The dynamic add-in loading is available in the thick client, in the thin client, and in the web client (this behavior did not change). | Add-ins were available only from the mobile application and you could not load them from the infobase. You could not define the availability of dynamic add-in loading feature. | Now you can get the availability of dynamic add-in loading feature. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Managed forms. | Keyboard navigation is now available for managed form decorations and fields, provided that they do not have the Hyperlink flag set and they display FormattedString values. Keyboard navigation provides the option to move between hyperlinks available in a formatted string. | This feature was not provided. | Improved managed form usability. |
| Web client. Spreadsheet documents. | In the web client, implemented all of the interactive spreadsheet document editing features that are available in other clients. Implemented the following spreadsheet document commands: AlignPictureLeft, AlignPictureCenter, AlignPictureRight, AlignPictureTop, AlignPictureMiddle, AlignPictureBottom, PicturesEqualWidth, PicturesEqualHeight, PicturesEqualSize, DistributePicturesVertically, DistributePicturesHorizontally, BringPictureForward, SendPictureBack, PringPictureToFront, and SendPictureToBack. | The options for interactive editing of spreadsheet documents were limited. The availability of interactive commands that affected spreadsheet document view was limited. Displaying row and column headers and grid lines was not supported. | Extended interactive spreadsheet document operations in the web client. |
| Spreadsheet documents. | In the thin client, in the paste special dialog box for spreadsheet documents, the option to include or exclude the following items is implemented:
In this dialog box, the All check box is replaced with buttons that select and clear all of the check boxes available in the dialog box. | In the thin client, the paste special dialog box for spreadsheet documents did not provide the option to include or exclude the following items:
In this dialog box, the All check box was available. | Extended paste special options for spreadsheet documents. |
| Interface. | In actions panel and navigation panel customization forms, the correct picture is set for Move to group command. | In actions panel and navigation panel customization forms, the picture of Move to group command was incorrect. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. | The client application interface rendering is now faster. The client application load on the operating system is reduced. | The client application interface rendering was slower and used more operating system resources. | Improved client application usability. |
| Background and scheduled jobs. | Background jobs now start faster. | Background job startup took more time. | Background jobs now start faster. |
| Binary data. | Optimized performance and memory usage of the following 1C:Enterprise script function:
| The performance and memory usage of the following 1C:Enterprise script functions were insufficient:
| Improved performance and stability of several functions that process binary data. |
| Configuration extensions. | Reduced database configuration update time for configuration extensions that do not affect the database structure. | The database configuration update time was longer if the configuration extension did not affect the database structure. | Reduced database configuration update time if the update includes applying changes to the configuration extensions that do not affect the database structure. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Charts. | The option to display Gantt chart intervals that would occupy less than 2 pixels in the current chart scale is implemented. They are displayed as 2-pixel intervals. | In some cases, Gantt chart intervals that would occupy less than 2 pixels in the current chart scale were not displayed. | Eliminated unexpected system behavior. |
| Data composition system. | The value of ResourcesAutoPosition data composition system parameter does not affect how column totals are displayed in data composition system reports. This change is not implemented in 8.3.11 compatibility mode. | In data composition system report spreadsheets, column totals were not displayed if ResourcesAutoPosition data composition system parameter was set to DontUse. | Eliminated unexpected system behavior. |
| Development tools. | In configuration comparison reports, the description of differences in XDTOPackages properties of Web service object is more detailed. The report includes the list of added and removed packages (with package names included) and their namespace data. | In configuration comparison reports, the description of differences in XDTOPackages properties of Web service object was less detailed. | Eliminated unexpected system behavior. |
| Charts. Spreadsheet documents. | In black-and-white view mode:
In black-and-white printing mode:
This change is not implemented in 8.3.11 compatibility mode. | In black-and-white view mode:
In black-and-white printing mode:
| For spreadsheet document objects, eliminated differences between black-and-white view and black-and-white printing. |
| Charts. | The background patterns used in black-and-white chart printing are based on original chart colors. If a pattern based on an original color is already in use, the next available pattern is used instead. The total number of available patterns in increased to 27. This change is not implemented in 8.3.11 compatibility mode. | The background patterns used in black-and-white chart printing were based on original chart colors (no check for duplicate patterns). The total number of available patterns was 12. | Improved chart view for black-and-white printing. |
| External data sources. | During a configuration update, the platform checks whether the Group property of external data source cube commands and external data source dimension table commands is filled. If the property is not filled, the update is canceled. This change is not implemented in 8.3.11 compatibility mode. | During a configuration update, the platform did not check whether the Group property of external data source cube commands and external data source dimension table commands was filled. | Eliminated unexpected system behavior. |
| Data history. Configuration extensions. | Support of data history is added to native and adopted extension objects. | Native and adopted extension objects did not support data history. | Data history is available for configuration extensions. |
| Spreadsheet documents. | In spreadsheet document headers and footers, the option to specify the first page number is implemented. The following property is implemented: SpreadsheetDocument.FirstPageNumber. In the spreadsheet document headers and footers dialog box, the option to specify the first page number is implemented. When a spreadsheet document is exported to OpenXML or OpenDocument format, the first page number is exported to the respective document property. | This feature was not provided. The number of the first page was always 1. | You can generate spreadsheet documents that match the requirements of regulatory authorities. |
| Internet-enabled functionality. | The platform no longer uses the imaplib library. The behavior of InternetMail object is not changed. The functionality previously provided by the library is now provided by the platform. | 1C:Enterprise used the imaplib library, which provided a part of InternetMail object functionality in compatibility modes Version 8.3.5 and earlier. | Improved platform stability and security. |
| Full-text search. Interface. | The standard full-text search form is updated. The History picture is added to the picture library. | The standard full-text search form looked differently. | Improved usability of the standard full-text search form. |
| Development tools. | The following features are added to the managed form editor:
| These features were not provided. | Improved form editor usability. |
| Data composition system. | If a query parameter belongs to a query language expression that has a name, or the parameter is an independent expression, it is available for use in data composition system data parameteres (however, it is not visible to end users). This change is not implemented in 8.3.11 compatibility mode. | If a query parameter belonged to a query language expression that had a name, or the parameter was an independent expression, it was not included in the list of available data parameters of the data composition system. | Eliminated unexpected system behavior. |
| Dynamic lists. | If a column of a table linked to a dynamic list belongs to a column group with In cell grouping, in a document generated using the Output list command, the column header is taken from the managed form table column header. This change is not implemented in 8.3.11 compatibility mode. | If a column of a table linked to a dynamic list belonged to a column group with In cell grouping, in a document generated using the Output list command, the column header was:
| Eliminated unexpected system behavior. |
| Automated testing. | The option to set and get timeouts for automated testing operations is implemented. For TestedApplication object, methods SetActionTimeout() and GetActionTimeout() are implemented. Clarified wordings of error messages related to attempts to connect to and/or operate applications being tested. | The option to set and get timeouts for automated testing operations was not available. Wordings of error messages related to attempts to connect to and/or operate applications being tested were less detailed and less accurate. | You can set timeouts for automated testing operations. Improved diagnostics for automated testing errors. |
| Spreadsheet documents. | If a spreadsheet document has docked rows or columns, the lines that outline the docked areas are only displayed after the document has been scrolled vertically (for rows) or horizontally (for columns). This change is not implemented in 8.3.11 compatibility mode. | If a spreadsheet document had docked rows or columns, the lines that outlined the docked areas were always displayed. | Improved report view. |
| Managed forms. | If the width specified for a managed form group is less than the total width of its subordinate items (at their minimum possible sizes), the specified width value is ignored. Instead, the width is calculated as follows:
This change is not implemented in 8.3.11 compatibility mode. | If the width specified for a managed form group was too small and some of the subordinate items could not fit even at their minimum possible sizes, the group still had the specified width. | Eliminated unexpected system behavior. |
| Queries. | An attempt to execute a query that contains a nested query with AUTOORDER keyword generates the following error: Nested queries cannot contain AUTOORDER operation. | An attempt to execute a query that contained a nested query with AUTOORDER keyword generated the following error: Nested queries cannot contain ORDER BY operation without TOP construction. | The error message is more accurate. |
| Configuration extensions. | Notifications related to applying configuration extensions have Important status. Therefore, they are available in the notification center and users who miss them can read them later. | Notifications related to applying configuration extensions had Information status. Therefore, they were not available in the notification center and, if errors occurred when applying configuration extensions, users who missed the notifications at the time they were generated missed them completely. | Better diagnostics of errors related to applying configuration extensions. |
| Data composition system. Dynamic lists. | When a new parameter that is a part of IN clause is added to a data set query, the data composition schema wizard automatically sets the option to use a value list as the parameter value. If a description of a query parameter that is a part of IN clause is missing from a data composition schema, the option to use a value list as the parameter value is automatically added to the available parameter of the source of available data composition settings. If a parameter of a dynamic list query is a part of IN clause, you can assign a value of value list type to this parameter in the dynamic list composition settings, and the dynamic list will pass the correct value list to the query. This change is not implemented in 8.3.11 compatibility mode. | The data composition schema wizard did not automatically set the option to use a value list as the value of a data composition schema parameter. If a parameter description was missing from a data composition schema, only a single value could be used as the parameter value. Dynamic lists processed query parameters of value list type incorrectly. | Eliminated unexpected system behavior. Improved data composition system behavior in scenarios where queries use value lists to set filters. |
| Data composition system. | In the data composition system, header templates (available for reports, tables, groupings, and charts) are not followed by blank line templates. As a result, a table or a chart header is always followed by a single blank line. This change is not implemented in 8.3.11 compatibility mode. | In the data composition system, header templates (available for reports, tables, groupings, and charts) were followed by blank line templates. As a result, a table or a chart header was always followed by two blank lines. | Eliminated unexpected system behavior. A table or a chart header is now followed by a single blank line instead of two blank lines. |
| Standard functions. | In the standard full-text search management function, the option to set the maximum size of objects to be indexed and the option to set the number of background jobs used for indexing are implemented. To set these parameters, use the dialog box that is opened using the Additional parameters button of the standard full-text search management function form. | This feature was not provided. | You can specify additional parameters for full-text search indexing. |
| Spreadsheet documents. | In the thin client, when a spreadsheet document is saved to a PDF file, if the spreadsheet page size is not specified, the page size setting of the current printer is used instead. This change is not implemented in 8.3.11 compatibility mode. | In the thin client, when a spreadsheet document was saved to a PDF file, if the spreadsheet page size was not specified, size A4 was used instead. | Eliminated unexpected system behavior. |
| Data display. | In Designer, thin client, and thick client, in the font selection dialog box, when you select a font by name (for example, "Arial"), the Scale value is applied to the resulting font. This change is not implemented in 8.3.11 compatibility mode. | In Designer, thin client, and thick client, in the font selection dialog box, when font was selected by name (for example, "Arial"), the Scale value was not applied to the resulting font. | Eliminated unexpected system behavior. |
| Data composition system. | In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag does not set that flag to its parent parameter. This change is not implemented in 8.3.11 compatibility mode. | In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag also set that flag to its parent parameter. | Eliminated unexpected system behavior. |
| Managed forms. | In the property palette, the field linked to the font property displays the font name, style, appearance (bold, italic, or strikethrough), and scale. | In the property palette, the field linked to the font property displays the font name and style. | You can view the current font parameters in the property palette, without opening the font dialog box. |
| Managed forms. | Implemented the new AlwaysHorizontal value of the ChildFormItemsGroup system enum. The Horizontal value of the ChildFormItemsGroup system enum is deprecated If the Horizontal value is used in the application, the PC platform wil use the AlwaysHorizontal value, and the mobile platform – the HorizontalIfPossible value instead. We recommend to replace the Horizontal by the HorizontalIfPossible value in applications in most cases. The AlwaysHorizontal value should be used only if a group must be horizontal on any screen, including mobile device screens. For example, if there is a group with an input field and a button with a picture and without text, linked to this field. | The following options of horizontal alignment of forms and form groups were available: Horizontal and HorizontalIfPossible. | The smooth conversion of previously created form to the mobile client usage is available. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Settings storage. | If a report form is opened with UserSettingsKey parameter specified and UserSettings parameter missing:
This change is not implemented in 8.3.11 compatibility mode. | If a report form was opened with UserSettingsKey parameter specified and UserSettings parameter missing:
| Eliminated unexpected system behavior. |
| Client application installation. | 1C:Enterprise launcher searches for distribution packages of new 1C:Enterprise versions in the following directories: Setup (32-bit platform) and Setup64full (64-bit platform). | 1C:Enterprise launcher searched for distribution packages of new 1C:Enterprise versions only in directories that contained specific versions (ignoring subdirectories). | Automatic client application updates support scenarios where client applications are both 32-bit and 64-bit. |
| Charts. | When OnIntervalEditEnd handler of a form item that displays a Gantt charts is executed:
This change is not implemented in 8.3.11 compatibility mode. | When OnIntervalEditEnd handler of a form item that displays a Gantt charts was executed:
| The behavior of OnIntervalEditEnd handler of form items that display Gantt charts is more logical. |
| Event log. | Interactive editing of event log format is implemented. The new event log event _$InfoBase$_.EventLogSettingsUpdate indicates the format change. In file infobases, changing event log format requires exclusive infobase access. Global context method ClearEventLog() is deprecated and only applicable to logs that have SQLite format. It is recommended that you do not use this method. If selection from event log records takes a long time, you can abort it by deleting the session that initiated the selection. The following limitations are applied to time-consuming selections from the event log:
The default event log format (the one that is selected in newly created infobases) is sequential format. | Interactive editing of event log format was not available. The default event log format (the one that was selected in newly created infobases) was SQLite format. | Interactive selection of event log format is now available. Applications no longer stop responding when performing time-consuming selections from the event log. |
| Temporary storages. | If the Address parameter of PutToTempStorage() method contains a value that was previously used in DeleteFromTempStorage() method, an exception is generated. This change is not implemented in 8.3.11 compatibility mode. | If an Address parameter value was previously used in PutToTempStorage() method and then in DeleteFromTempStorage() method, an attempt to use the value in PutToTempStorage() method again was only successful if it was a UUID of a form that was open at that time. | Eliminated unexpected system behavior. |
| Charts. | The algorithm of displaying stacked charts that have negative values is changed:
This change is not implemented in 8.3.11 compatibility mode. | In stacked charts, each point had a single column that represented the sum of all values (calculated with appropriate signs). | Eliminated unexpected system behavior. |
| Data composition system. | In data composition settings composer, when the source of user-defined settings is specified, if a data parameter value contains an array and the option to use a value list in this parameter is enabled, the parameter value is set to a value list containing all of the values from the source array. This change is not implemented in 8.3.11 compatibility mode. | In data composition settings composer, when the source of user-defined settings was specified, if a data parameter value contained an array and the option to use a value list in this parameter was enabled, the parameter value was set to a value list containing a single value (the default value for the parameter value type). | Eliminated unexpected system behavior. |
| Managed forms. | When form item properties DataPath, FooterDataPath, HeaderDataPath, TitleDataPath, and RowPictureDataPath are set from 1C:Enterprise script or a configuration with these properties is loaded from a file, if any of these properties contains a path that refers to a form item that has a row index, an error is generated. This change is not implemented in 8.3.11 compatibility mode.
| When form item properties DataPath, FooterDataPath, HeaderDataPath, TitleDataPath, and RowPictureDataPath were set from 1C:Enterprise script or a configuration with these properties was loaded from a file, if any of these properties contained a path that referred to a form item that had a row index, no errors were generated. Such property values were set but they were actually ignored. | Eliminated unexpected system behavior. |
| Dynamic lists. | In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as Ref.Products.Product.[State of origin]) are not available for filtering, sorting, or grouping. This change is not implemented in 8.3.11 compatibility mode. | In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as Ref.Products.Product.[State of origin]) were available for filtering, sorting, or grouping. However, an attempt to set a filter by a value of such field returned an error. | Eliminated unexpected system behavior. |
| Data composition system. | If an expression of a calculated data composition system field is empty, NULL is substituted for the field value in detailed records. This change is not implemented in 8.3.11 compatibility mode. | If an expression of a calculated data composition system field was empty, an attempt to use the field in detailed records generated a "field not found" error. | Eliminated unexpected system behavior. The system behavior is improved in scenarios where a user selects a custom field with no expression specified. |
| Data composition system. | If calculation of EvalExpression() function result includes division by 0, the result of the expression calculated with this function is Division by zero. This change is not implemented in 8.3.11 compatibility mode. | If calculation of EvalExpression() function result included division by 0, the expression calculated with this function was fully calculated (Division by zero was used as the function result). | Eliminated unexpected system behavior. |
| Settings storage. | Each operation with the standard settings storage includes a check for SaveUserData access right. Calls of StandardSettingsStorageManager.SetDescription() method include a check for SaveUserData access right. | Operations with the standard settings storage included checks for SaveUserData access right only if they were performed from 1C:Enterprise script. Calls of StandardSettingsStorageManager.SetDescription() method did not include a check for SaveUserData access right. | Eliminated unexpected system behavior. In particular, commands related to dynamic list settings are no longer available to users that do not have SaveUserData access right. |
| Data composition system. | Items of conditional appearance of data composition system are applied using the following rules:
This change is not implemented in version 8.3.11 compatibility mode. | Items of conditional appearance of data composition system were applied using the following rules:
| Eliminated unexpected system behavior. |
| Data composition system. | In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field affects the filter presentation. This change is not implemented in version 8.3.11 compatibility mode. | In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field did not affect the filter presentation. | Improved filter presentations in dynamic lists and data composition system-based reports. |
| Infobase operations. | When administrative infobase parameters are set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior is different from that of the previous versions. For details, see 1C:Enterprise documentation. | When administrative infobase parameters were set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior was different. This behavior was not documented. | Setting administrative infobase parameters is more intuitive and predictable. |
| Interface. | In managed applications, calls of SwitchInterface() global context method are ignored in all client modes. We recommend that you do not use ordinary forms in managed client application mode. This change is not implemented in version 8.3.11 compatibility mode. | In managed applications, calls of SwitchInterface() global context method displayed command bars. | Eliminated unexpected system behavior. |
| 1C:Enterprise script. | When CurrentLanguage() global context function is called on the server, in the thick client, or in an external connection, it returns the interface language of the current user. If the current user is not specified, or the interface language is not specified, or the specified interface language is not included in the configuration, the function returns the default configuration language. The CurrentLanguage() function behavior is now uniform across all modes. This change is not implemented in version 8.3.11 compatibility mode. | When CurrentLanguage() global context function was called on the server, in the thick client, or in an external connection, if the interface language specified for the current user was not included in the configuration, the function returned Undefined. The CurrentLanguage() function behavior on the client and on the server was not uniform. | Eliminated unexpected system behavior. |
| Data composition system. | In a nested query included in the right part of a left join, its WHERE section does not include an explicitly specified field, and the parent query includes a different field with the same data composition name, the template composer does not include the filter to the nested query. To preserve the previous query behavior, explicitly specify a field in the WHERE section. This change is not implemented in version 8.3.11 compatibility mode. | When filling available data set fields, the template composer always included the filter in the nested query. | The result of automatic filling of available data set fields is more predictable. |
| Internet-enabled functionality. | In InternetMail.Logon() method, implemented authentication request with the user name and password if APOP authentication fails. | The InternetMail.Logon() method generated an exception if APOP authentication failed. The authentication attempt with the user name and password was not performed. | The user authentication on the mail server better complies with RFC 1939 standard. |
| Managed forms. | In OpenForm() method, changed the algorithm of searching for an open form instance.
This change is not implemented in version 8.3.11 compatibility mode. | The following algorithm of searching for an open form instance was used.
| Eliminated unexpected system behavior. Unified the algorithm that searches for an open form in different client application modes. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Managed forms. | On Android, context menus are displayed next to the items where they belong. Opening a context menu does not change the form layout. | The context menu was displayed at the top of a form. Opening a context menu changed the form layout and repositioned form items. | On Android, improved usability of accessing context menus of form items. |
| Mobile device-specific features. | Optimized MultimediaData object generation algorithm used during device camera operations. | The MultimediaData object generation algorithm used during device camera operations was not optimal. | Improved performance of device camera operations in mobile applications. |
| Interface. | Changed the calendar view on mobile devices:
| The calendar view on the mobile device was different:
| Improved calendar usability on mobile devices. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Web client. | Implemented the following features for file system extensions for Google Chrome and Mozilla Firefox:
| File system extensions for Google Chrome and Mozilla Firefox did not support the following:
| Improved secure connection support. Improved web client security. |
| Web client. | In the web client, dragging spreadsheet document cells and pictures is implemented. If Ctrl is held down, they are copied, otherwise they are moved. The web client behavior is now identical to the thin client behavior. This change is not implemented in version 8.3.11 compatibility mode. | In the web client, dragging spreadsheet document cells and pictures was not supported. | New interactive spreadsheet document operations in the web client. |
| Automated testing. | If TestedFormField or a similar object is retrieved using FindObject() or FindObjects() method, its TitleText property always stores the title value set in Designer. This change is not implemented in version 8.3.11 compatibility mode. | If TestedFormField or a similar object was retrieved using FindObject() or FindObjects() method, if its title was explicitly specified in the form editor, a colon might be missing from the title. | Eliminated unexpected system behavior. |
| Managed forms. | Changing the Enabled property of managed form item groups and form items in managed form tables does not require server calls. Setting the Visible property of an input field to False results in the following:
This change is not implemented in 8.3.11 version compatibility mode. | Changing the Enabled property of managed form item groups and form items in managed form tables required a server call. Setting the Visible property of an input field to False resulted in the following:
| Changing the visibility of some managed form items is optimized. |
| Mobile platform. Mobile client. | Implemented the following features of the applications list in the mobile client and mobile application main menu:
Command-line parameters can be specified for each application in the applications list. The following command-line parameters are available in the mobile application and mobile client: N, P, ClearCache, C, WSA, OIDA, Autooff, DisableStartupMessahes, Z, UsePrivilegedMode, HttpsForceSSLv3, HttpsForceTLS1_0, O, L, VL, WSN, WSP, and URL. Implemented the application startup according with the set of supported command-line parameters. | These features were not provided. | New application list management operations. You can now specify command-line options to fine tune the application behavior at startup. |
| Managed forms. | In the mobile platform and in all client applications, if a form control that has minimum width does not fit the form, the control width is reduced below the minimum. This change is not implemented in version 8.3.11 compatibility mode. | If a form control that had minimum width did not fit the form, the control width was not reduced below the minimum. | Eliminated unexpected system behavior. |
| Data composition system. | Rows and columns can be docked when generating a grouping header template based on a predefined template. Columns are docked (FixLeft property of a data composition template area cell is set) if the FixLeft report setting is not set or is set to Auto. Rows are docked (FixTop property is set) if the FixTop report setting is not set or is set to Auto. This change is not implemented in version 8.3.11 compatibility mode. | Rows and columns were never docked when generating a grouping header template based on a predefined template. | Eliminated unexpected system behavior. |
| Queries. | If a query contains a UNION expression without the ALL keyword, a CAST AS Reference operation will return a single string with NULL value. ISNULL() function applied to a CAST AS Reference expression returns the correct result. This change is not implemented in version 8.3.11 compatibility mode | If a query contained a UNION expression without the ALL keyword, a CAST AS Reference operation might return multiple strings with NULL value. ISNULL() function applied to a CAST AS Reference expression might return an incorrect result. | Eliminated unexpected system behavior. |
| Collaboration system. | Clarified some of the collaboration system error messages. | Some of the collaboration system error messages were less clear. | The collaboration system error messages are more clear now. |
| Data composition system. | In the settings composer of the data composition system, when the source of available settings is specified, if a parameter value is a fixed array and the parameter can store a value list, the value list that includes all the values from the initial fixed array is stored to the parameter. This change is not implemented in version 8.3.11 compatibility mode | In the settings composer of the data composition system, when the source of available settings was specified, if a parameter value was a fixed array and the parameter could store a value list, a value list containing a single element with the default value of the parameter type was stored to the parameter. | Eliminated unexpected system behavior. |
| Managed forms. | Unified and improved appearance of managed form control tooltips that have ToolTipRepresentation property set to Button. This change is implemented for various types of managed form controls. | The appearance of managed form control tooltips that had ToolTipRepresentation property set to Button was not unified across different control types. | Unified tooltip appearance for various types of form controls. |
| Mobile platform. Mobile client. Managed forms. Internet-enabled functionality. | In mobile applications, for managed form field extension for an HTML document field, the Document property is now available. In mobile applications, for EventData parameter of OnClick event handler of managed form field extension for an HTML document field, Document and Href parameters are now available. Mobile platform notifications about calls of methods and properties that do not exist may be different from PC platform notifications. | These features were not provided. On mobile devices, HTML documents displayed in forms were inaccessible. | Extended HTML document capabilities for the mobile platform. |
| DBMS operations. System requirements. | Support of Microsoft SQL Server 2017 is implemented. | Microsoft SQL Server 2017 was not supported. | Support of Microsoft SQL Server 2017 is implemented. |
| Development tools. | For TextColor and BackColor properties of managed form buttons, both the property palette and the color selection dialog box now display the actual color values (if these properties are set to Auto or to any of the system style items). | For TextColor and BackColor properties of managed form buttons, both the property palette and the color selection dialog box displayed the color of the system style item (if these properties were set to Auto or to any of the system style items). | The property palette now displays property values more accurately. |
| Localization. | The French localization of the client applications is available. | This feature was not provided. | 1C:Enterprise is available to French-speaking users. |
| Mobile client. | The information in the About dialog box in the mobile client was expanded. | There was less information in the About dialog box in the mobile client. | The About dialog box in the mobile client is now closer to the About dialog box in the thin client. |
| Mobile platform. Mobile client. Collaboration system. | Implemented the feature of receiving and processing push notifications from the collaboration system. The mobile device application should be built with push notifications extension enabled. Notifications are generated by the pushnotifications.1c.com service from 1C company. The registration in service is performed automatically. | The collaboration system did not generate mobile push notifications. | Reduced risk of missing the collaboration system notification when the application is not running, or is hidden, or when the user is operating in another infobase within a single application. |
| Internet-enabled functionality. | Implemented the feature of including external providers in the OpenID authentication process. For the specifics of external providers usage, refer to the documentation. | This feature was not provided. | Improved the OpenID authentication support. |
| Mobile platform. Mobile client. | The iPhone X screen is now supported in the 1C:Enterprise mobile version. | This feature was not provided. | The 1C:Enterprise mobile version interface is adapted to iPhone X. |
| Internet-enabled functionality. | 1C:Enterprise 8 now supports cryptographic algorithms that meet the GOST R 34.10-2012 and 34.11-2012 requirements. | This feature was not provided. | Internet resources that demand the GOST R 34.10-2012 and 34.11-2012 compliance are now available in 1C:Enterprise 8. |
| Mobile platform. Mobile client. Mobile device-specific features. | 1C:Enterprise platform does not support barcode scanning, making photos and videos on Windows Desktop. The following methods of the MultimediaTools object return False on Windows Desktop: BarcodeScanningSupported(), PhotoSupported(), VideoRecordingSupported(). | The following methods of the MultimediaTools object returned True on Windows Desktop: BarcodeScanningSupported(), PhotoSupported(), VideoRecordingSupported(). | Eliminated unexpected system behavior. |
| Pictures. | If the name of the picture from a picture library equals to the name of the configuration common picture, a warning will be generated during the database update. The database update process will not be interrupted. When accessing the picture by name, the configuration picture returns. When this warning appears, it is recommended to review picture names in the configuration. | If the name of a picture from a picture library was equal to the name of a configuration common picture, the database update could not be performed. | The database update is now available if the name of a picture from a picture library is equal to the name of a configuration common picture. |
| Mobile platform. Mobile client. Administration tools. | The 1C:Enterprise 8 mobile platform now supports OS authentication. The HTTPConnection object constructor supports the UseOSAuthentication parameter. | This feature was not provided. | The 1C:Enterprise 8 mobile platform is now sufficient when the OS authentication is required. |
| Data display. Mobile client. | The 1C:Enterprise mobile platform now displays messages of the same style as other mobile messages. Messages are generated by the ShowUserNotification() method with the UserNotificationStatus parameter set to UserNotificationStatus.Information. | If a message was generated by the ShowUserNotification() method with the UserNotificationStatus parameter set to UserNotificationStatus.Information, this message was not displayed. | Extended capabilities of the ShowUserNotification() method in the mobile client. |
| Mobile platform. Mobile client. Managed forms. | The command set and the appearance of the context menu of a managed form table row was changed in the 1C:Enterprise mobile version. | The command set and the appearance of the context menu of a managed form table row in the 1C:Enterprise mobile version were different. | Improved the 1C:Enterprise mobile interface. |
| Internet-enabled functionality. | Improved the analysis of the root certificate revocation. Implemented the option to specify the behavior of the platform when the root certificate revocation can not be verified unambiguously. Implemented the IgnoreServerCertificatesChainRevocationSoftFail parameter of the conf.cfg file. These changes are available in all Internet-enabled features of 1C:Enterprise platform. | The analysis of the root certificate revocation was the same regardless of the reason why the remote node was not validated. There was no option to specify the platform behavior when the root certificate revocation could not be verified unambiguously. | Improved diagnostics of Internet-enabled functionality. In some cases the option to specify the platform behavior is now available. |
| Mobile platform. | Implemented the database file validation in the verify and repair feature of the mobile platform. This feature checks whether the database file is corrupted and prompts several solutions. | These features were not provided. The verify and repair feature could not validate the database file. If the database file was corrupted the session was abnormally terminated. | Improved the database file diagnostics capabilities. |
| Configuration extensions. | If the active extension changes the database structure it can not be deleted. If you want to delete the extension you shoud deactivate it first. You will be prompted to confirm the deletion of the inactive extension that changes the database structure. Implemented the ConfigurationExtension.ModifiesDataStructure() method, which shows whether the configuration extension changes the database structure. | When the extension that changed the database structure was deleted no actions preventing the extension data loss were performed. | Reduced risk of configuration extension data loss. |
| Mobile client. Mobile application builder. | A web page where user can register in the infobase (or service) can now be specified in the mobile client. This page can be reached either automatically (if there are no registered infobases in the mobile client) or manually. You can now specify an URL with the personal account of services that contain infobases for the mobile client. The mobile client can now retrieve shared infobase lists from the server through special web services. You can specify multiple addresses of the same server, as well as addresses of multiple servers. The following options are now available when building a mobile application:
The e1c:// type hyperlinks are now supported as a starting page and an infobase list element in the mobile client. Implemented the AddToStartCfg command-line option for the mobile client. It adds an infobase in the mobile client infobase list. It can be placed in web pages, specified during the mobile application customization. OpenID authentication is not supported for accessing web-servers with shared infobase lists. | These features were not provided. | The registration of an infobase or a web service in the mobile client became more clear and simple. |
| Event log. | Implemented the following events:
Extended the list of data types that are handled by the following events: _$Access$_.AccessDenied, _$InfoBase$_.EventLogSettingsUpdate. New events require the DataAdministration access right to view, except managing users events and the following ones: $InfoBase$_.DBConfigUpdateError, and _$InfoBase$_.DBConfigExtensionUpdateError. | There were less registered events and less handled data types. | Improved logging events. |
| Data composition system. Charts. | Some of the output parameters of the data composition system are only saved if their Use flag is set (the exact list of parameters depends on the configuration compatibility mode).
| All of the changes in the output parameters of the data composition system were saved. This could cause issues at opening data composition settings in the earlier versions of 1C:Enterprise. | Data composition settings related to charts are now usable in the earlier platform versions. |
| Web client. | The Mozilla Firefox add-on that provides access to 1C:Enterprise extensions and 1C:Enterprise add-ins is available in the add-on store https://addons.mozilla.org. The add-on is automatically updated to newer versions as they appear in the store. | The Mozilla Firefox add-on that provides access to 1C:Enterprise extensions and 1C:Enterprise add-ins was not available in the add-on store https://addons.mozilla.org. The add-on updates were delivered and installed with new 1C:Enterprise versions. | Updates of the Mozilla Firefox add-on are now transparent to users. |
| Mobile client. Mobile platform. Managed forms. | In the mobile version of 1C:Enterprise, in HTML document fields, full-featured editing of HTML page input fields is now available (if their contentEditable property allows editing). At that, all formatted document functionality is supported. | In the mobile version of 1C:Enterprise, in HTML document fields, full-featured editing of HTML page input fields was not available (if their contentEditable property allowed editing). | Extended HTML document functionality in the mobile version of 1C:Enterprise. |
| Software licensing. | Software licenses can be associated with dongles. Human-readable information about the license is added to the bottom of activated software license files. Such files are compatible with the earlier 1C:Enterprise versions. | Software licenses could not be associated with dongles. Activated software license files did not contain human-readable information about the license. | The software licensing features are upgraded. |
| Software licensing. | New license type: 1C:Enterprise server CORP license. Implemeted a check for the CORP license if a feature requires it. The following features are available for CORP licenses:
The following CORP license types are available:
Licensing utility now supports CORP licenses. New command: ring license update. The command updates all licenses located in the storage. | Having a CORP license was a legal requirement, not a technical requirement. | A new license type: CORP. |
| Internet-enabled functionality. Add-ins. Cryptography support. File operations. | Distribution packages of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer are converted into .exe files. Distribution packages in .cab format are considered obsolete, although supported. The add-in technology documentation is updated. (read more) | Distribution packages of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer were provided in .cab files. | Installation of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer is more convenient. |
| System requirements. Linux. | The following Linux distribution packages are supported:
Both 32-bit and 64-bit distribution packages are supported. 1C:Enterprise server clusters and client applications are supported. | The distribution packages were not supported. | Extended list of supported Linux distribution packages. |
| Internet-enabled functionality. | Upgrade: the credentials used as a basis for WS-reference and WSDefinition objects are only sent to the primary resource that provides a WSDL definition. If the downloaded schema requires schemas from other secondary resources, they are accessed anonymously. | The credentials that had been used as a basis for WS-reference and WSDefinition objects were used to access all resources that provided WSDL definitions. | To download a web service definition, if a web server requires authorization, the credentials are sent only to the primary resource selected to download the schema. |
| Command interface. | Upgrade: for the "All functions" dialog box in the thick and thin client applications, the search by the first characters is disabled. To open the search box, press Ctrl+F. To move to the next search result, press F3. To move to the previous search result, press Ctrl+F3. | In the "All functions" dialog box, there were two ways to start a search:
| Eliminated unexpected system behavior. |
| Regional settings. | Upgrade: in accordance with the Federal Law of the Russian Federation No. 368-FZ, a new time zone is applied for Volgograd oblast. The update is applied to all 1C:Enterprise system components, except for the web client. The web client sets the time in accordance with the time zone information provided by the operating system and web browser. | 1C:Enterprise ignored the changes introduced by the Federal Law of the Russian Federation No. 368-FZ. | New time zone settings are applied due to the legislation change. |
| Configuration comparison and merging. | New feature: on comparing two configurations, the command order changes are displayed for the commands stored in standard command groups. | On comparing two configurations, the command order changes were not displayed for the commands stored in standard command groups. Therefore, the changes were not applied to the resulting configuration. | Eliminated unexpected system behavior. |
| Mobile application builder. | Upgrade: Mobile application builder successfully builds applications when an add-in is missing for some mobile operating systems supported by the mobile application. It records warnings about missing add-ins to the mobile application building log. When a mobile application attempts to access a missing add-in, an exception is generated. | Mobile application builder did not allow building applications when an add-in was missing for a mobile operating system supported by the mobile application. | You can build a mobile application if there is an add-in that is not required on some operating systems supported by the mobile application. |
| Mobile client. Data history. | Upgrade: the Change history command is hidden from context menus of dynamic lists in the mobile client version 8.3.12 connected to 1C:Enterprise server version 8.3.13 or later. | Two Change history commands were displayed in the context menus of dynamic lists in the mobile client version 8.3.12 connected to 1C:Enterprise server version 8.3.13 or later. Both commands were unavailable. | Eliminated unexpected system behavior. |
| Client application. | Upgrade: client applications require less RAM to handle pictures. | Client applications required more RAM to handle pictures. | RAM consumption by client applications when handling pictures is optimized. |
| Server clusters. | Upgrade: occasional performance degradation of loaded server clusters is fixed. | Occasionally, performance degradation of loaded server clusters occurred. | Server cluster performance is more stable. |
| System requirements. Linux. | Upgrade: new approach to Linux OS distribution support. 1C:Enterprise supports only distributions listed in the system requirements. In general, the client-supported distribution list matches the server-supported distribution list, but there might be some exceptions. The list of supported Linux distributions is up-to-date. | The list of supported Linux distributions was not up-to-date. | The list of supported Linux distributions is brought up-to-date. |
| Mobile client. | Upgrade: when you use iOS mobile application home page to add an application, the compatibility check is based on the digital signatures of all configurations included in the mobile application build. | When developers used iOS mobile application home page to add a new application, the application failed. | You can use iOS mobile application home page to add new applications based on the configurations included in the mobile client application. |
| Mobile client. | New feature: the favorites setting form contains hint text on how to use this form. Upgrade: If a mobile client form has a link, the More actions menu always contains the commands Add to favorites and Get link. New command in the Get link dialog box that adds a link to the favorites. | The favorites setting form did not contain hint text on how to use this form. If a mobile client form had a link, then:
Command of adding a link to the favorites was not available in the dialog box of the Add to favorites command. | Mobile client interface is improved. |
| Mobile client. | Upgrade: the table row rearrangement command is automatically added to the table context menu instead of commands of moving rows up and down (even if command bar autofill is disabled). Upgrade: if the multiple choice is set for a table (even if command bar autofill is disabled), the command of selecting several table rows is automatically added to the table context menu and table command bar. | The table row rearrangement command was added to the table context menu only if the context menu had been filled automatically or manually. Command of selecting several table rows was added to the table context menu and the table command bar only if the table context menu and the table command bar had been filled automatically or manually. | Mobile client interface is improved. |
Version 8.3.11 includes known bug fixes and functionality modifications.
Performance optimization for user work history is included in the list of changes implemented in 1C:Enterprise version 8.3.8.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.10 is now implemented. | Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.9 was implemented. | Configurations developed using 1C:Enterprise platform version 8.3.10 or earlier can run on version 8.3.11 without any changes to configuration or to data structures. This allows for transition to version 8.3.11 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.10 after the transition to version 8.3.11, even if you disabled the compatibility mode (if you did, enable it again). |
| Configuration comparison and merging. | Merging composite types and the contents of exchange plans, subsystems, and functional options is implemented. Viewing the differences in these objects is available both in interactive mode (in a dialog box) and in a configuration comparison report. Automatic merging of composite types and the contents of exchange plans, subsystems, and functional options is implemented, with the option to specify the configuration that has priority. The format of the file that stores configuration comparison and merging settings is changed. | Merging composite types and the contents of exchange plans, subsystems, and functional options was not available. Available options included taking the entire object from the configuration being loaded or keeping the existing objects without changing them. | Simplified configuration comparison and merging. |
| Data history. | The history of database object changes is implemented. The Data history property is implemented for the following configuration objects: catalogs, documents, business processes, tasks, and information registers. The option to keep the history of attributes of these objects (including standard attributes and tabular sections), common attributes (except for data separators), and information register resources is implemented. The options to view and edit data change history, add comments to data history records, and revert to a specific data version are implemented. Native objects of configuration extensions do not support data history. The following access rights are implemented: ReadDataHistory, ReadDataHistoryOfMissingData, UpdateDataHistory, UpdateDataHistoryOfMissingData, UpdateSettingsDataHistory, UpdateDataHistoryVersionComment, ViewDataHistory, EditDataHistoryVersionComment, and SwitchToDataHistoryVersion. The global context property DataHistory is implemented. It provides access to the data history from 1C:Enterprise script. The user interface that provides access to data history is implemented. | This feature was not provided. Implementation of a change history based on built-in 1C:Enterprise tools was possible. | The data history is now available as a platform-level feature. This simplifies application development and support. |
| Development tools. | In the managed form editor, the option to preview a form as it would look on a mobile application is implemented. This option is available in configuration compatibility mode Version 8.3.7 or later. | In the managed form editor, the option to preview a form as it would look on a mobile application was not available. The preview always displayed a form as it would look on a PC. | Improved form development tools for configurations that run on mobile devices. |
| Binary data. | A set of functions that perform bitwise operations on integer numbers is implemented. They treat numbers as unsigned 32-bit numbers. The following global context methods are implemented: CheckBit(), CheckByBitMask(), SetBit(), BitwiseAnd(), BitwiseOr(), BitwiseNot(), BitwiseAndNot(), BitwiseXor(), BitwiseShiftRight(), and BitwiseShiftLeft(). This change is not implemented in 8.3.10 compatibility mode. | 1C:Enterprise only provided methods for logical operations with data stored in binary data buffers. | Simplified usage of bitwise operations with numerical operands. |
| Database configuration update. Server clusters. | New infobase restructuring algorithm is implemented. It features the following major differences from the previous algorithm:
This feature has beta status. The new restructuring algorithm is only used in client/server mode with Microsoft SQL Server or PostgreSQL DBMS. The new restructuring algorithm requires Java 1.8 to be installed on the computer that runs 1C:Enterprise server. For the conf.cfg file, new parameters JavaHome, JavaOpts, and UpdateDBCfg are implemented. | This feature was not provided. | The new algorithm significantly improves the performance of infobase restructuring. This reduces the maintenance downtime during application updates on production servers. |
| Data display. Dynamic lists. | For the format string parameter of Format() function, the option to include a number format template is implemented. The new NF format string parameter is implemented for this purpose. The template specifies the position of a number in a string. The search in dynamic lists is based on the format specified for list columns. The search results are highlighted even in cells that contain string constants before and/or after the number. This change is not implemented in 8.3.10 compatibility mode. | These features were not provided. | You can display formatted values with measurement units in charts and in other interface items that support format strings. |
| Development tools. | In batch Designer mode, the configuration check includes the option to check configuration modules for synchronous method calls. For /CheckConfig command-line option, the -CheckUseSynchronousCalls parameter is implemented. If you specify this parameter, you also have to specify the -ExtendedModulesCheck parameter for this command-line option. | The option to check configuration modules for synchronous method calls during a configuration check initiated from batch Designer mode was not available. This option was only available if Designer was running in interactive mode. | Eliminated unexpected system behavior. |
| Web services and HTTP services. Configuration extensions. | For native configuration extension objects of web service and HTTP service types, support of configurable session reuse is implemented. | For native configuration extension objects of web service and HTTP service types, configurable session reuse was not available. | Unified platform behavior for accessing similar mechanisms from a configuration and from an extension. |
| Collaboration system. | Sending messages from a 1C:Enterprise server to a client application is implemented. A configured collaboration system operates as transport for message exchange purposes. Client applications can get messages both synchronously and asynchronously, depending on the server call type: a regular call or a background job. For collaboration system manager, the following methods are implemented: CreateUser(), DeleteMessage(), BeginAttachNewMessagesHandler(), BeginDetachNewMessagesHandler(), and a new variant of GetConversation() method. For CollaborationSystemConversation object, Key and Visible properties are implemented. For CollaborationSystemConversationsFilter object, Key and Displayed properties are implemented. The CollaborationSystemMessage object and some of its properties (Author, Date, ID, Recipients, and Text) are now available on the client. For CollaborationSystemMessage object, Data and Conversation properties are implemented. Objects CollaborationSystemConversationID and CollaborationSystemMessageID are are now available on the client. Objects CollaborationSystemUserID and CollaborationSystemUserIDCollection, their properties, and their methods are now available on the client. | This feature was not provided. The CollaborationSystemMessage object and some of its properties (Author, Date, ID, Recipients, and Text) were only available on 1C:Enterprise server. Objects CollaborationSystemConversationID and CollaborationSystemMessageID were only available on 1C:Enterprise server. Objects CollaborationSystemUserID and CollaborationSystemUserIDCollection, their properties, and their methods were only available on 1C:Enterprise server. | You can implement client notifications for events that occur on 1C:Enterprise server. |
| Collaboration system. | The option to attach a handler that is executed after sending a collaboration system message is implemented. A message can now include hyperlinks; clicking a hyperlink executes the handler or a standard action assigned to the hyperlink . For CollaborationSystemManager object, the following methods are implemented: AttachAfterMessageSendHandler(), DetachAfterMessageSendHandler(), AttachMessageActionHandler(), and DetachMessageActionHandler(). The CollaborationSystemMessage.Actions property is implemented. CollaborationSystemConversation and CollaborationSystemConversationContext objects are now available in client applications. | These features were not provided. CollaborationSystemConversation and CollaborationSystemConversationContext objects were only available on 1C:Enterprise server.
| Expanded collaboration system capabilities. You can implement automatic replies to incoming messages. |
| Queries. | For QuerySchemaQueryBatch, QuerySchemaOperators, QuerySchemaColumns, QuerySchemaIndexExpression, QuerySchemaOrderExpression, and QuerySchemaTotalCalculationFields objects, the MoveTo() method is implemented. It moves a collection element to the specified position. | This feature was not provided. | Expanded development tools for some collections related to query schemas. |
| Configuration extensions. Applied objects. | In configuration extensions, support of native catalogs, documents, exchange plans, and information registers is implemented. For adopted catalogs and documents, the option to add attributes and tabular setions in extensions is implemented. A native exchange plan can only include native extension objects. A native exchange plan cannot be used in a distributed infobase. The option to add native extension objects to adopted exchange plans is implemented. The full list of limitations is provided in the documentation. Deleting an extension deletes all data that was added to native extension objects from the infobase. | These features were not provided. | Expanded configuration extension capabilities. An extension attached to an infobase can store its data in the infobase. |
| Information registers. | For InformationRegisterRecordKey object, the option to get the related metadata object is implemented. The method InformationRegisterRecordKey.Metadata() is implemented. This change is not implemented in 8.3.10 compatibility mode. | Getting the related metadata object directly from the InformationRegisterRecordKey object was not available. | Getting metadata related to information register record keys is now similar to getting metadata from other configuration objects. |
| Charts. | For stock charts, support of the following properties of ValuesAxis object is implemented: MinValueDetectionMethod, MinValue, MaxValueDetectionMethod, and MaxValue. This change is not implemented in 8.3.10 compatibility mode. | For stock charts, values of the following properties of ValuesAxis object did not affect the chart view: MinValueDetectionMethod, MinValue, MaxValueDetectionMethod, and MaxValue. | Improved stock chart display options. |
| Standard functions. Event log. | In the event log, for Users.Add and Users.Modify events, OpenIDAuthentication and UnsafeOperationProtection properties are implemented (in the Data field of the log record). For Users.Add and Users.Modify events, the log viewer now displays OpenID authentication and Unsafe operation protection properties. This change is not implemented in 8.3.10 compatibility mode. | For events that described adding or modifying a user, the OpenID authentication flag and unsafe operation protection flag were recorded to the event log but were not available for viewing. | Eliminated unexpected system behavior. You can access data that was previously unavailable. |
| Software licensing. | In the license acquisition wizard, selecting a country from a list is implemented. | In the license acquisition wizard, one could enter any word as a country name. | Eliminated issues that occurred due to entering incorrect country name during software license acquisition. |
| DBMS operations. System requirements. | Support of Oracle Database version 11.2.0.4 (Linux) is implemented. It is only supported with patch 20954292. Oracle Database version 11.2.0.4 (Windows) is only supported with patches 24591646 and 24591637. | Oracle Database version 11.2.0.4 (Linux) was not supported. Oracle Database version 11.2.0.4 (Windows) was supported without the requirement to install any patches. | Extended list of supported Oracle Database versions. |
| Technological log. | <WINCERT> technological log event is implemented. It is intended for investigating errors related to certificate validation using Windows API methods. This event can only be generated on Windows. | This feature was not provided. | Simplified investigation of errors related to certificate validation on Windows. |
| Collaboration system. | Local collaboration system server is now available. The server is provided as a standalone distribution package, it requires separate installation. This feature is currently in beta status. | This feature was not provided. The collaboration system only worked over 1cDialog.com service. | You can install and use a local collaboration system server. |
| Software licensing. System requirements. | If one of the key computer parameters was changed, a license activated on 1C:Enterpirse 8.2.15 or later is considered valid when verified with ring license command with validate option. Using --validate parameter with activate or prepare-request option returns an error if a run-time error occurs when attempting to retrieve any of the key parameters. The behavior of these options when they are used without this parameter is not changed. The license command requires ring utility version 0.8. | If one of the key computer parameters was changed, a license activated on 1C:Enterpirse 8.2.15 or later was considered invalid when verified with ring license command with validate option. If a run-time error occured when attempting to retrieve any of the key parameters, the license was activated successfully and the corresponding license fields were filled with blank values, making the license impossible to use. The license command required ring utility version 0.6. | Eliminated unexpected system behavior. |
| DBMS operations. System requirements. | Support of PostgreSQL version 9.4.5 from AstraLinux Special Edition 1.5 is implemented, starting with 1C:Enterprise version 8.3.11.3034. | PostgreSQL version 9.4.5 from AstraLinux Special Edition 1.5 was not supported. | Extended list of supported DBMS. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Managed forms. | Improved usability of line selection in managed form tables. You can use Ctrl and Shift keys, as well as mouse buttons, to select table lines. This change is not implemented in 8.3.10 compatibility mode. | The only way to select multiple lines in a managed form table was clicking each line while holding down Ctrl. | Improved usability of line selection in managed form tables. |
| Web client. | A single application can be accessed from multiple web browser tabs. | An attempt to run a second application instance in a second web browser tab generated an error. | The platform supports running multiple web client sessions in a single web browser. |
| Client application installation. | Implemented a unified name "access application" for all client application types in messages displayed during client application update over HTTP. | In messages displayed during client application update over HTTP, two terms were alternately used for client application: "data viewer" and "access program". | Unified terminology in messages related to access application update over HTTP. |
| Managed forms. Data display. | When a managed form table is exported using the Output list command:
This change is not implemented in 8.3.10 compatibility mode. | When a managed form table was exported using the Output list command:
| Eliminated unexpected system behavior. |
| Managed forms. Data display. | When a managed form table with multiple lines selected is exported using the Output list command (with the Selected items only check box selected):
The performance of the Output list command (with the Selected items only check box selected) is improved in the following scenario: the table displays a dynamic list, a large number of lines is selected, and the dynamic list query is not efficient. This change is not implemented in 8.3.10 compatibility mode. | When a managed form table with multiple lines selected was exported using the Output list command (with the Selected items only check box selected):
The performance of the Output list command (with the Selected items only check box selected) was insufficient in the following scenario: the table displayed a dynamic list, a large number of lines was selected, and the dynamic list query was not efficient. | Improved alrogithm of exporting a managed form table to a spreadsheet or text document. |
| Collaboration system. | The recipient selection procedure in context conversation messages is modified. If the sender does not want to notify any of the users who can see the message (i.e. users having the right to access the object that provides the context), they must explicitly select No notification. Sending a message to an empty list of recipients is not allowed. | Sending a context message with an empty list of recipients was possible. | Improved notification usability. |
| Spreadsheet documents. | The commands that perform the following operations are added to the Table section of the main application menu:
| These commands were not available in managed client applications. | Added support of interactive operations with pictures to managed applications. |
| Collaboration system. | During video calls in the thin and web clients, 1C:Enterprise performs the diagnostics of Internet connection quality. If the quality is insufficient, 1C:Enterprise displays the diagnostics report over the video feed. | During video calls, if the Internet connection quality was insufficient, 1C:Enterprise did not display any diagnostics data. In some cases the picture might freeze without any explanations. | Diagnostics of Internet connection quality during collaboration system video calls are implemented. |
| Standard functions. | If an application does not contain any objects that can be involved in totals management, when you attempt open the totals management dialog box in ordinary application mode (Main menu – Operations – Totals management), 1C:Enterprise displays a diagnostics message instead of the dialog box. | If an application did not contain any objects that could be involved in totals management, an attempt open the totals management dialog box in ordinary application mode (Main menu – Operations – Totals management) did not open the dialog box and no diagnostics messages were displayed. | Improved 1C:Enterprise usability. |
| Managed forms. | The tab order of managed form groups does not depend on the United property value of subordinate groups. It depends on group settings (horizontal or vertical). This change is not implemented in 8.3.10 compatibility mode.
| The tab order of managed form groups depended on the United property value of subordinate groups. Groups where United was set to False were ignored, their settings did not affect the tab order. | Eliminated unexpected system behavior. |
| Client application. | Pressing F1 or using Help menu command always opens identical help pages regardless of client application or interface mode. | Pressing F1 or using Help menu command might open different help pages depending on client application, interface mode, or help opening method. | Eliminated unexpected system behavior. |
| Collaboration system. | If forced switching to the recipients field of a context collaboration system conversation is performed (after an attempt to send a message without any recipients specified), once a user selects a recipient, the focus is set to the message text field. | If forced switching to the recipients field of a context collaboration system conversation was performed (after an attempt to send a message without any recipients specified), once a user selected a recipient (i.e. selected any option except for No notification), the focus stayed in the recipients field. | Improved interface for sending messages in context collaboration system conversations. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| DBMS operations. Queries. | In applications that use PostgreSQL DBMS, the conversion of LIKE `TEXT%` query language operation to an SQL query operation is optimized. This change is not implemented in 8.3.10 compatibility mode. | In applications that used PostgreSQL DBMS, the conversion of LIKE `TEXT%` query language operation to an SQL query operation was not optimal. | In applications that use PostgreSQL DBMS, improved performance of search by beginning of a string in the query language. |
| Full-text search. | The access rights verification for full-text search results is optimized in scenarios where the search returns over 100 results. This change is not implemented in 8.3.10 compatibility mode. | The performance of access rights verification for full-text search results in scenarios where the search returned over 100 results was insufficient. | Reduced time of getting full-text search results for users with access right restrictions in scenarios where the search returns over 100 results. |
| Spreadsheet documents. | The performance of CheckPut() method of spreadsheet document is improved. | The performance of CheckPut() method of spreadsheet document was insufficient. | Faster data output to a spreadsheet document in scenarios that include the check whether the output area fits a single page. |
| External reports and data processors. Server clusters. Client application. | Improved performance of loading external reports and data processors in client applications and on 1C:Enterprise server. Intensive work with external reports and data processors does not cause lags. | The performance of loading external reports and data processors in client applications and on 1C:Enterprise server was insufficient. Intensive work with external reports and data processors caused lags. | Eliminated 1C:Enterprise server lags in scenarios that involve inrtensive work with external reports and data processors. |
| Internet-enabled functionality. | Improved 1C:Enterprise performance and scalability in scenarios that involve using HTTPConnection and FTPConnection objects on 1C:Enterprise server (if these connections belong to different sessions).
| 1C:Enterprise performance was significantly reduced in scenarios that involved using HTTPConnection and FTPConnection objects on 1C:Enterprise server (if these connections belonged to different sessions). | Improved 1C:Enterprise server performance in scenarios that involve multiple HTTP or FTP connections from different sessions. |
| DBMS operations. | Improved performance of operations with temporary tables in scenarios that involve the following Microsoft SQL Server versions:
| The performance of operations with temporary tables in scenarios that involved some Microsoft SQL Server versions was insufficient. | Improved performance of operations with temporary tables in scenarios that involve some Microsoft SQL Server versions. |
| Cryptography support. Internet-enabled functionality. | On Windows, improved the performance of cryptography operations and operations over SSL and TLS protocols in scenarios where these operations are running simultaneously in a large number of sessions. | On Windows, the performance of cryptography operations and operations over SSL and TLS protocols was insufficient in scenarios where these operations were running simultaneously in a large number of sessions. | On Windows, improved the performance of cryptography operations and operations over SSL and TLS protocols in scenarios where these operations are running simultaneously in a large number of sessions. |
| Background and scheduled jobs. Configuration extensions. | The performance of starting background jobs is improved in infobases that run in file mode and use extensions. | The performance of starting background jobs in infobases that ran in file mode and used extensions was insufficient. | Eliminated unexpected system behavior. |
| Development tools. | The performance of the following Designer operations is improved:
| The performance of the following Designer operations was insufficient:
| Improved perfromance of frequently used development tools. |
| System requirements. | The size of executable files of 1C:Enterprise is reduced. | Executable files of 1C:Enterprise required more disk space. | Reduced 1C:Enterprise requirements to available disk space. |
| Development tools. | In 1C:Enterprise script editor, the performance of the following operations is improved:
| For large modules, the performance of 1C:Enterprise script editor was insufficient. | Improved usability for application developers. |
| Infobase operations. | Improved the performance of loading infobases from .dt files in systems that use IBM DB2. | Loading infobases from .dt files in systems that used IBM DB2 took more time. | Reduced time of moving infobases in systems that use IBM DB2. |
| Managed locks. Server clusters. | The 1C:Enterprise server performance in scenarios with simultaneous posting of large documents (dozens of thousands of lines) is improved. | Simultaneous posting of large documents (dozens of thousands of lines) could hang the server cluster. | Improved performance of 1C:Enterprise server under heavy load. |
| Spreadsheet documents. | The performance of drawing spreadsheet documents with a lot of pictures in hidden rows is improved. | Drawing spreadsheet documents with a lot of pictures in hidden rows took more time. | Improved performance of operations with spreadsheet documents that contain a lot of pictures in hidden rows. |
| DBMS operations. | Optimized operations with large temporary tables in PostgreSQL. | The performance of operations with large temporary tables in PostgreSQL was insufficient. | Improved performance of operations with large temporary tables in PostgreSQL. |
| DBMS operations. | Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized.
| The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient. | Improved performance of temporary table operations. |
| Infobase operations. | In file infobases that contain large amounts of metadata, improved performance of metadata restructuring. The performance of restructuring data tables has not changed. | In file infobases that contained large amounts of metadata, metadata resturcturing took more time. | If a configuration contains a large amount of metadata and its metadata structure has changed, the performance of restructuring file infobases based on this configuration is improved. |
| Managed forms. | Improved performance of adding lines to form attributes of FormDataTree type in the thick and thin clients. The peformance improvement is most noticeable in trees that contain large numbers of lines. | Adding lines to form attributes of FormDataTree type took more time in trees that contained large numbers of lines. | Improved performance of operations with form data. |
| Dynamic lists. | Improved performance of opening forms that contain dynamic lists. | Opening forms that contained dynamic lists took more time. | Improved performance of opening forms that contain dynamic lists. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. | When 1C:Enterprise opens an infobase that is not registered in its infobase list, it creates a directory for storing the service data of the infobase. It creates an individual directory with a unique name for each infobase connection string and each infobase user. The maximum number of directories is 20. | When 1C:Enterprise opened an infobase that was not registered in its infobase list, it used a directory with a predefined name for storing the service data of all such infobases: 00000000-0000-0000-0000-00000000000. | The service data of infobases that are not registered in the infobase list is stored in dedicated directories. This facilitates disk space management and prevents the growth of a single directory. |
| Development tools. | When a custom command of a metadata object is renamed, the platform checks whether the new name exactly matches the name of any standard command of that metadata object. The platform also performs this check during the configuration logical integrity check. | This feature was not provided. Names of custom commands of a metadata object could exactly match the names of its standard commands. | Eliminated unexpected system behavior. |
| Charts. | The chart scale view settings are expanded, they now include scale view, color, and position, scale label angle, grid line visibility and color, and more. For ChartScale object, the following properties are implemented: GridLinesShowMode, GridLine, GridLineColor, LabelFont, LabelColor, LabelOrientation, MaxLabelRows, LabelAngle, LabelFormat, ScaleLocation, ScaleLine, ScaleLineColor, ScaleStep, ScaleMarkLocation, and ScaleLabelLocation. The following properties of ChartPlotArea object are deprecated, they are supported solely for compatibility purposes:
In version 8.3.10 compatibility mode, the following properties are hidden from the property palette and do not affect the chart view:
| These features were not provided. The chart scale view settings were simpler. | Expanded chart view options. |
| Full-text search. | The following full-text search features are implemented:
To apply these changes, disable the compatibility mode and rebuild the full-text search index. Previous 1C:Enterprise versions cannot work with indexes built in version 8.3.11 with compatibility mode disabled. This change is not implemented in 8.3.10 compatibility mode. | Full-text search worked as follows:
| Optimized full-text search. |
| Data composition system. Spreadsheet documents. | In the data compostion system, nested charts and tables of the resulting spreadsheet document are located in spreadsheet document groupings. The data composition system template composer creates blank templates with VerticalLevel property set. These templates follow the templates of charts and tables located in groupings. This change is not implemented in 8.3.10 compatibility mode. | In the data compostion system, the resulting spreadsheet document did not contain groupings for charts and nested tables that did not have row groupings. The template composer did not create blank templates with VerticalLevel property set that followed the chart templates. For tables located in groupings, the composer created blank templates with VerticalLevel set to 0. | Eliminated unexpected system behavior. |
| XML and XDTO support. | The option to download XSD documents that import schemas that require HTTP requests to external servers (with redirects) is implemented. This change is not implemented in 8.3.10 compatibility mode. | The option to download XSD documents that imported schemas that required HTTP requests to external servers (with redirects) was not available. | Eliminated unexpected system behavior. |
| Development tools. Client application. | In the search and replace dialog box of the text editor, the following behavior of the Replace button is implemented:
| In the search and replace dialog box of the text editor, clicking the Replace button searched for the next occurrence of the search string. Clicking Replace again replaced it. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | In the dialog box for setting a spreadsheet document area name, the default name is generated in the language that matches the current 1C:Enterprise script variant. This change is not implemented in 8.3.10 compatibility mode. | In the dialog box for setting a spreadsheet document area name, the default name was generated in the language that matched the client application interface language. | Eliminated unexpected system behavior. |
| Development tools. | During the creation of a configuration update file, the message stating that the configuration update requires 1C:Enterprise version 8.3.9.2033 or later is no longer displayed. | During the creation of a configuration update file, the message stating that the configuration update required 1C:Enterprise version 8.3.9.2033 or later was displayed. | Removed a message that is no longer relevant. |
| XML and XDTO support. | When an XSD schema is imported to an XDTO package, for references to global elements and attributes, the default and fixed properties are imported to DefaultValue and Fixed properties, regardless of the element or attribute declaration type. | When an XSD schema was imported to an XDTO package, for references to global elements and attributes, the default and fixed properties that were specified locally were not imported. | Eliminated unexpected system behavior. |
| Dynamic lists. | If a dynamic list contains PredefinedDataName and DataVersion fields, the following rules apply to these fields:
| If a dynamic list contained PredefinedDataName and DataVersion fields, the following rules applied to these fields:
| Eliminated unexpected system behavior. |
| 1C:Enterprise script. | The option to omit a notification description handler is implemented. Use this option in scenarios where you would create an empty handler (because the result of the execution of an asynchronous method is not important and only the handler for the method errors is important). Now you can omit any parameter of the NotifyDescription constructor. | A handler for asynchronous method errors could only be created together with an empty handler for the method execution result. | Simplified handling of asynchronous method errors. |
| ZIP archive operations. | When 1C:Enterprise accesses a file name using the properties of ZipFileEntry object (this includes the scenario when a file is being written to the disk), it replaces invalid characters with underscores (_). The list of invalid characters includes all characters that are not allowed in Windows file names. 1C:Enterprise makes the replacement on all operating systems.This change is not implemented in 8.3.10 compatibility mode. To provide access to the original file names (before the character replacement), the following properties are implemented for ZipFileEntry object: OriginalFullName, OriginalName, OriginalPath, OriginalExtension, and OriginalBaseName. | If a name of a file stored in a ZIP archive contained invalid characters, the name was truncated, leaving only the part before the first invalid character. The list of invalid characters included all characters that were not allowed in Windows file names. This might cause issues when extracting files whose names contained invalid characters. | Any file can be successfully extracted from a ZIP archive on any operating system. The names of the extracted files might change, |
| Data display. Spreadsheet documents. | The look of a spreadsheet document containing SVG pictures in the thin client exactly matches the look of that document in the following cases:
| The look of a spreadsheet document containing SVG pictures in the thin client could differ from the look of that document in the following cases:
| Unified look of spreadsheet documents in various client applications and export formats. |
| Infobase operations. Server clusters. | In client/server mode, the reliability of the following operations is improved:
| In client/server mode, the following operations might cause issues:
| Improved reliability of some operations in client/server mode. |
| Spreadsheet documents. Web client. | When a spreadsheet document is exported to PDF format, the resulting document includes the page size and orientation (PickTrayByPDFSize property of a PDF document). If you need to print the resulting document on custom-size paper from a web browser, it is recommended that you set the PrintAccuracy property of the spreadsheet document to Accurate. In Microsoft Internet Explorer, you do not need to use this property. | When a spreadsheet document was exported to PDF format, the resulting document did not include the page size and orientation. Printing the resulting document required a manual check of paper size and orientation in the PDF viewer. | Eliminated unexpected system behavior. |
| Common objects. Configuration properties. | If you access the UsePurpose property of the entire configuration or a managed form from 1C:Enterprise script, it has Undefined value. | When the UsePurpose property of the entire configuration or a managed form was accessed from 1C:Enterprise script, it had FixedArray type, with the selected values as array elements. | Eliminated unexpected system behavior. The behavior of this property is now similar to the behavior of other properties that do not affect application functionality in 1C:Enterprise mode. |
| Web client. | In the web client, the performance of opening system dialog boxes, as well as dialog boxes opened using ShowQueryBox() and ShowMessageBox() methods, is improved. | In the web client, opening system dialog boxes, as well as dialog boxes opened using ShowQueryBox() and ShowMessageBox() methods, took more time. | Improved performance and reliability of the window subsystem of the web client. |
| Spreadsheet documents. | In spreadsheet documents, there is no spacing between pictures and their borders. This change is not implemented in 8.3.10 compatibility mode. | In spreadsheet documents, unexprected spacing might appear between pictures and their borders. | Eliminated unexpected system behavior. |
| Full-text search. | Morphological full-text search by attribute name is now supported. It is recommended that you rebuild the full-text search index in order to use this feature. This change is not implemented in 8.3.10 compatibility mode. | Morphological full-text search by attribute name was not supported. | Full-text search by attribute name is more user-friendly. |
| Data exchange. | ThisNode() method of ExchangePlan object always returns a reference to the exchange plan item with ThisNode property set to True. This change is not implemented in 8.3.10 compatibility mode. | ThisNode() method of ExchangePlan object did not always return a reference to the exchange plan item with ThisNode property set to True. | Eliminated unexpected system behavior. |
| Queries. | In the query language, if a CASE operation includes a nested CASE operation or ISNULL() function, which uses both a virtual field and a nonvirtual field, the CASE calculation result is correct. | In the query language, if a CASE operation included a nested CASE operation or ISNULL() function, which used both a virtual field and a nonvirtual field, the CASE calculation result was incorrect and this might cause an unexpected shutdown. | Eliminated unexpected system behavior. |
| Charts. | The chart view in the thin client and web client is unified:
This change is not implemented in 8.3.10 compatibility mode. | The chart views in the thin client and web client were different:
| Eliminated unexpected system behavior. The chart view is more predictable. |
| Development tools. | During application debug, you can access variable properties (provided that it has properties) even if the variable presentation is not available. | During application debug, if a variable presentation was not available, the variable properties were also not available. | Eliminated unexpected system behavior. |
| Dumping configurations to files/Restoring configurations from files. | Intertactive export of configurations to files is always performed in hierarchical format. The flat format is only supported in batch Designer mode. It is recommended that you always use the hierarchical format. | The interactive export of configurations to files offered a choice between flat and hierarchical formats. | The option to export configuration files in flat format is disabled due to possible issues. For example, transferring exported files between different file systems might be difficult. |
| Development tools. | During debugging over TCP, debugger no longer stops responding while calculating an expression or editing a variable value. | During debugging over TCP, debugger might stop responding while calculating an expression or editing a variable value. | Application debugging over TCP is more predictable and reliable. |
| Client application. | In the Start menu, a single shortcut combines 32-bit and 64-bit versions of 1C:Enterprise. 1C:Enterprise installation on a computer with any operation system of Windows family adds all of the available 1C:Enterprise shortcuts to the Start menu. Pinning a running 1C:Enterprise application to the taskbar actually pins a shortcut to file 1cestart.exe. If multiple 1C:Enterprise applications are running, they are combined into a single taskbar shortcut. The jump list is only available if the shortcut to 1cestart.exe is pinned to the taskbar. | The Start menu included two 1C:Enterprise shortcuts: one for the 32-bit version and the other one for the 64-bit version. 1C:Enterprise installation on Windows 8 or later did not add all of the available 1C:Enterprise shortcuts to the Start menu. Pinning a running 1C:Enterprise application to the taskbar pinned exactly that application. If multiple 1C:Enterprise applications were running, they were combined in this shortcut. The jump list was available for any 1C:Enterprise-related shortcut. | All of the 1C:Enterprise components are available on the Start menu. The jump list behaviour is more predictable. |
| Data composition system. | The parsing algorithm of data composition system queries validates comparison operations that include String parameters of unlimited length. The parsing is performed when the data composition system wizard is opened and when a schema-based source of available settings is initialized (opening reports also includes this operation). | The parsing algorithm of data composition system queries that included String parameters of unlimited length generated errors stating that using strings of unlimited length in queries was not allowed. | Eliminated unexpected system behavior. |
| Collaboration system. | In the collaboration system, video calls use peer-to-peer connections instead of using a central server. The central server is only required to establish connections between the conversation participants. | In the collaboration system, video calls always used the central server and did not use peer-to-peer connections. | Reduced load on the central server of the collaboration system. If conversation participants belong to a local network, the video call traffic is limited to local network. |
| Collaboration system. | If 1C:Enterprise connects to the collaboration server through a proxy server, it gets the proxy server settings from the operating system settings or from inetcfg.xml configuration file. NTLM authentication at proxy servers is not supported. | Connection to the collaboration server through a proxy server was not supported. | Simplified collaboration system setup in scenarios that include a proxy server. |
| Information registers. | When an information register record set is written using InformationRegisterRecordSet.Write(), Undefined value is not ignored when setting a managed lock. This change is not implemented in 8.3.10 compatibility mode. | When an information register record set was written using InformationRegisterRecordSet.Write(), Undefined value was ignored when setting a managed lock. This resulted in locking excessive data. | Improved parallel writing of information register record sets when multiple users write dimensions of composite types where dimension values can be blank. |
| Localization. | Support of Kazakh user interface (kk language code) is restored. | Support of Kazakh user interface was not available. | 1C:Enterprise now provides the option to use Kazakh user interface. |
| Localization. | The French interface language (language code: fr) is not supported. | The French interface language (language code: fr) was supported. | The French interface language is not supported. |
| Server clusters. | On Linux, the working process parameter Memory occupied is calculated based on VmRSS (resident set size) value. The value of Memory occupied parameter in absolute terms is reduced and it is more accurate. It is recommended that you revise the working process restart options in the working server properties. | On Linux, the working process parameter Memory occupied was calculated based on VmSize (virtual memory usage) value.
| On Linux, the cluster monitoring system uses a parameter that provides more accurate data. |
| Localization. | Entering Russian Ruble symbol (₽, ISO 4217 643) from the keyboard is supported. | This feature was not provided. | Eliminated unexpected system behavior. |
| Applied objects. | When floating point numbers are converted between 1C:Enterprise format and external formats, the accuracy of their presentations is never lost. In scenarios where previously accuracy losses were possible, the conversion algorithm does not depend on the operating system. | When floating point numbers were converted between 1C:Enterprise format and external formats, accuracy losses were possible. In scenarios where accuracy losses were possible, the conversion algorithm depended on the operation system. | Reduced number of scenarios where conversion of floating point numbers with significant digits in their fractional parts between 1C:Enterprise format and external formats (such as XSL file format) introduces accuracy losses. |
| Linux. | Improved reliability of the Linux version of 1C:Enterprise in some scenarios. | In some scenarios, reliability of the Linux version of 1C:Enterprise was insufficient. | Improved stability of the Linux version of 1C:Enterprise. |
| Technological log. | Updated the <ADMIN> event content and description in the documentation and in the technological log configuration file editor. (read more) | The <ADMIN> event content and description in the documentation and in the technological log configuration file editor were incorrect. | The technological log configuration file editor is now up-to-date. |
| Database configuration update. | The Cannot reference table... error never occurs after clicking the Accept button in the Restructure data window. Previously this prevented database configuration update. This error message appears before you have the option to click the Accept button. To eliminate the issue that causes the error message, run infobase verification and repair. | The Cannot reference table... error might occur after clicking the Accept button in the Restructure data window. This prevented database configuration update. | Eliminated unexpected system behavior. |
| Dynamic lists. | When you press Enter (or double-click) in a row of a table linked to a dynamic list or when you call the ChangeRow() form table method, a form table extension will open a form linked to this row only if there is the Change command in the commands. This change is not implemented in 8.3.10 compatibility mode. | When you pressed Enter (or double-clicked) in a row of a table linked to a dynamic list or when you called the ChangeRow() form table method, a form table extension opened a form linked to this row in any case. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Internet-enabled functionality. Web client. System requirements. | The web client no longer supports Microsoft Internet Explorer versions 8 and 9. | The web client supported Microsoft Internet Explorer versions 8 and 9. | Legacy versions of Microsoft web browser are no longer supported. |
| 1C:Enterprise script. Development tools. | In the thin and web clients, detection of attempts to assign a value to a nondeclared variable whose name matches a common module name is implemented. As a result, in this scenario the value is not assigned and an error message is generated. This change is not implemented in 8.3.10 compatibility mode. | In the thin and web clients, attempts to assign a value to a nondeclared variable whose name matched a common module name were not detected. In the web client, this caused an unexpected shutdown of the client application. | Eliminated unexpected system behavior. |
| Queries. | The Move() method of QuerySchemaQueryBatch, QuerySchemaOperators, QuerySchemaColumns, QuerySchemaIndexExpressions, QuerySchemaOrderExpressions, and QuerySchemaTotalCalculationFields objects shifts the specified collection element by the specified number of positions. This change is not implemented in 8.3.10 compatibility mode. | The behavior of the Move() method was different from the standard one:
| The behavior of the Move() methods is unified with the behavior of Move() methods in other collections. |
| Managed forms. Dynamic lists. Access rights. | Upgrade: if the current user does not have enough rights to access form items related to commands of table or form extensions for dynamic lists, the items are hidden, regardless of the method used to add them (explicitly by application developers or automatically by the extensions). Upgrade: the following commands are removed from the managed form table context menu: OutputList, ListSettings, LoadDynamicListSettings, SaveDynamicListSettings, DynamicListStandardSettings, List, HierarchicalList, and Tree. Upgrade: the submenu Generate is always added as the last menu item regardless of the hierarchy. Upgrade: advanced search commands and list settings commands are added to tables that contain a dynamic list with the main table, filter criterion, or enumeration. Upgrade: upon a form creation, if a table is removed, all commands related to the table are also removed. It happens, for example, when the user does not have the right to view the main table of the dynamic list related to the form table. This change is not implemented in 8.3.10 compatibility mode. | If the current user did not have enough rights to access form items related to commands of table or form extensions for dynamic lists, the items were hidden only if they were added automatically by the extensions. If they were added explicitly by application developers, they were still visible (but unavailable to the user). If the managed form table displayed a dynamic list without the main table, the following commands were added to the context menu: OutputList, ListSettings, LoadDynamicListSettings, SaveDynamicListSettings, and DynamicListStandardSettings. If the managed form table displayed a dynamic list with the main table that supported hierarchy, the following commands were added to the context menu: List, HierarchicalList, and Tree. The submenu Generate was added to different parts of the context menu depending on the displayed table. Advanced search commands and list settings commands were not added to tables that contained a dynamic list with the main table, filter criterion, or enumeration. Upon a form creation, if a table is removed, most of commands related to the table were also removed. However, one command (usually, Update) was never removed. | Eliminated unexpected system behavior. |
| Dynamic lists. | You can hide folder pictures in hierarchical dynamic lists. To hide the pictures, clear the RowPictureDataPath property of the table that displays the hierarchical dynamic list. This change is not implemented in 8.3.10 compatibility mode. | Hiding folder pictures in hierarchical dynamic lists was not available. Clearing the RowPictureDataPath property of the table that displayed the hierarchical dynamic list did not hide the pictures. | Eliminated unexpected system behavior. |
| Client application installation. | The timeout for downloading a client application distribution kit over HTTP is removed. You can cancel downloading by clicking Cancel in the dialog box that displays the progress. | Downloading a client application distribution kit over HTTP was terminated if it took more than 600 seconds. | Downloading a client application distribution kit using a slow connection channel is now possible. |
| Common objects. | In the TextReader object constructor, if LineSplitter parameter is omitted, this is treated as setting it to Chars.LF. If ConvertibleSplitterOfLines parameter is omitted, this is treated as setting it to Chars.LF + Chars.CR. This change is not implemented in 8.3.10 compatibility mode. | In the TextReader object constructor, if LineSplitter or ConvertibleSplitterOfLines parameter was omitted, this was treated as setting it to a blank string. | Eliminated unexpected system behavior. The values of omitted parameters now match the Syntax Assistant descriptions. |
| Infobase operations. | A composite index that includes attributes with Index property set to Index with additional ordering no longer depends on the attribute order. The order of the atttributes in the index is fixed. The index is rebuilt during the first object restructuring after disabling compatibility mode. This change is not implemented in 8.3.10 compatibility mode. | A composite index that included attributes with Index property set to Index with additional ordering depended on the attribute order. If the order was changed, the platform rebuilt the index. | The effect of the attribute order on the database index structure is reduced. |
| Queries. | The attempt to execute a query that contains MIN() or MAX() aggregate function with the following parameter types generates an error:
This change is not implemented in 8.3.10 compatibility mode. | The attempt to execute a query that contained MIN() or MAX() aggregate function with the following parameter types did not generate an error:
Such a query might return an incorrect result or cause an unexpected shutdown. | Eliminated unexpected system behavior. |
| Queries. | A query that contains ISNULL() or CASE() operation that applies to result of MAX() or MIN() function (provided that parameters of these functions include values of UUID type or system enumerations, and provided that the other operand of ISNULL() or CASE() is a value of primitive type or another system enumeration) returns the correct result. This change is not implemented in 8.3.10 compatibility mode. | A query that contained ISNULL() or CASE() operation that applied to result of MAX() or MIN() function (provided that parameters of these functions included values of UUID type or system enumerations, and provided that the other operand of ISNULL() or CASE() was a value of primitive type or another system enumeration) returned UNDEFINED. | Eliminated unexpected system behavior. |
| Charts. | In charts that use the default palette, the default colors of chart scales and series are changed. New system enumeration value is implemented: ChartColorPalette.SoftAdaptive. This change is not implemented in 8.3.10 compatibility mode. | In charts that used the default palette, the default colors of chart scales and series were different. | Imoroved view of charts with default settings. |
| Managed forms. | In the standard processing of a ChoiceDataGetProcessing event handler of configuration object managers, correct handling of Undefined value of Parameters.SearchString parameter is implemented. If this value is set to Undefined, the system behavior is similar to quick choice, it returns the list of all database items for this configuration object. This change is not implemented in 8.3.10 compatibility mode. | In the standard processing of a ChoiceDataGetProcessing event handler of configuration object managers, if Parameters.SearchString parameter was set to Undefined, it was treated as an empty search string. | Eliminated unexpected system behavior. |
| Queries. | In the Parameters collection of the Query object, the parameter type used in a comparison operation (>, >=, <, <=, =, <>) applies to both operation parameters, however, their type qualifiers do not have to be identical. For example, if the first parameter is a string, you can specify a string of unlimited length as a second parameter. This change is not implemented in 8.3.10 compatibility mode. | In the Parameters collection of the Query object, the parameter type used in a comparison operation (>, >=, <, <=, =, <>) and its type qualifier were applied to both operation parameters. | Eliminated unexpected system behavior. |
| Data composition system. | When you add a condition with Empty comparison type to a query, the data composition system adds the condition to a nested query in the right part of a left join only if it cannot add the condition to the parent query. Otherwise, it never adds such conditions to nested queries. This change is not implemented in 8.3.10 compatibility mode. | When a condition was added to a query, the data composition system always attempted to add the condition to a nested query. If the nested query was located in the right part of a left join, the condition was duplicated in the parent query. | When a query includes a nested query located in the right part of a left join, the data composition system provides a more predictable result. |
| File operations. | The CreateDirectory() and BeginCreatingDirectory() methods generate exceptions if the directory name contains invalid characters. This change is not implemented in 8.3.10 compatibility mode. | The CreateDirectory() and BeginCreatingDirectory() methods did not analyze the directory name. If the directory name contained invalid characters, the directory was not created and no error messages were generated. | 1C:Enterprise checks whether the names of directories to be created are valid. |
| Managed forms. | A managed form group with HorizontalAlignInGroup property set to Center is centered relative to the parent group. This change is not implemented in 8.3.10 compatibility mode. | A managed form group with HorizontalAlignInGroup property set to Center was aligned left relative to the parent group. | Eliminated unexpected system behavior. |
| Managed forms. | If ShapeRepresentation property of a managed form button is set to None and its BackColor property is set to any value except Auto, the button has transparent background. This change is not implemented in 8.3.10 compatibility mode. | If ShapeRepresentation property of a managed form button was set to None and its BackColor property was set to any value except Auto, the button background color was taken from the BackColor property. | Eliminated unexpected system behavior. |
| Web client, web service, and HTTP service publishing tools. | If an application is published to a web server using webinst utility with -descriptor option, the pubdst, pubdst32, and pubdst64 attributes of the root point element are copied from the publication template to the resulting default.vrd file. | If an application was published to a web server using webinst utility with -descriptor option, the pubdst, pubdst32, and pubdst64 attributes of the root point element were not copied from the publication template to the resulting default.vrd file. | Eliminated unexpected system behavior. |
| Documentation. | The description of SessionParameters.Clear() method in Syntax Assistant now states that calling this method requires the right to change all session parameters that are used in the method (possibly all parameters available in the session). | The description of SessionParameters.Clear() method in Syntax Assistant was incorrect. | The Syntax Assistant topic is now up-to-date. |
| Managed forms. | If a managed form attribute is created using 1C:Enterprise script, it can be accessed only with ThisObject. prefix. This change is not implemented in 8.3.10 compatibility mode. | In some scenarios, managed form attributes created using 1C:Enterprise script could be accessed without ThisObject. prefix. | Eliminated unexpected system behavior. |
| Administration tools. | New version of Java-based 1C:Enterprise Administrative Service API, which is compatible with 1C:Enterprise 8.3.11, is available (read more). | The previous version of Java-based 1C:Enterprise Administrative Service API was compatible with 1C:Enterprise versions 8.3.10 and earlier. | You can select Java-based 1C:Enterprise Administrative Service API version that is compatible with your 1C:Enterprise version. |
| System requirements. | The minimum system requirements for some operating systems of Windows family have changed:
The system requirements for other Windows versions have not changed. If an operating system does not match the requirements, 1C:Enterprise generates a warning with a recommendation to install the required update. If you choose the installation option that does not have user interface and the operating system does not match the requirements, the cluster console and the COM connection module are not registered. 1C:Enterprise distribution package for Windows includes Visual C++ Redistributable for Visual Studio 2015. 1CEClientMakeSetup utility requires Visual C++ Redistributable to generate distribution packages for platform versions 8.3.11 and later. | The minimum system requirements for some operating systems of Windows family were:
| The platform installer installs the required redistributables and displays warnings about unsupported operating systems. |
| Server clusters. Administration tools. | You can use server cluster administration tools (both Java-based and administration server-based) for administering any 1C:Enterprise server cluster version, starting with 8.3.9. You can even use features that are not available in some administration server (ras) versions and server cluster versions. | Server cluster administration tools (both Java-based and administration server-based) were compatible only with 1C:Enterprise server clusters that had the same version. In most cases, exact version matches were required. | Simplified server cluster administration. Reduced cost of adapting the administrative infrastructure to new 1C:Enterprise server cluster versions. |
| Collaboration system. |
Creating a displayed context conversation with a specific list of participants from 1C:Enterprise script is not supported. In this scenario, the CollaborationSystemConversation.Write() method throws an exception. | Creating a displayed context conversation with a specific list of participants was allowed. | Eliminated unexpected system behavior. |
| Internet-enabled functionality. | Security profile restrictions do not impact the following objects:
| If a security profile was applied, the following objects were not available:
| Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile device-specific features. | The following permissions are implemented for iOS mobile applications:
| These features were not provided. | Expanded settings for iOS mobile applications. |
| Managed forms. | In the mobile platform, the object that visualizes planner data (the planner) is now available. For the object usage specifics, see the documentation. | The planner was only available on the platform for personal computer. | Expanded data presentation options on mobile devices. |
| Mobile device-specific features. | Support of local and push notifications is added to the mobile platform for Windows. 1C:Enterprise uses Windows Notification Services for this purpose. The notification sending service provided by 1C Company does not support Windows Notification Services. The system enumeration value DeliverableNotificationSubscriberType.WNS is implemented.The DeliverableNotificationSendManager.GetAccessToken() method is implemented. Notification sending errors are returned in the return value of DeliverableNotificationSendManager.Send() method.This change is not implemented in 8.3.10 compatibility mode. The system enumeration DeliverableNotificationSendErrorType is implemented. The DeliverableNotificationSendIssueInformation object is implemented. For DeliverableNotificationSendManager.Send() method, the DeliverableNotificationSendIssuesInformation parameter is implemented. The option to get a local notification when a device is crossing a geofence border is implemented. | Support of local and push notifications was only available for iOS and Android devices. Notification sending errors generated exceptions. | Standard user notifications are now available on mobile Windows devices. Both mobile applications and desktop applications can generate notifications (local and push notifications, respectively). |
| System requirements. | Support for Android versions earlier than 4.0 is ended. The earliest supported API version is API 14 (Androuid 4.0). | Android versions with API 9 (Android 2.3) or later were supported. | Ended support for legacy Android versions. |
| Print tools. Spreadsheet documents. | In the mobile platform, support of batch printing is implemented. | This feature was not provided. | Batch printing is now available in the mobile platform. |
| File operations. | On the mobile platform, the file selection dialog box now supports multiple file masks. The search by mask in the file selection dialog box and the search by mask with FindFiles() method are now case-insensitive. The file selection dialog box and FindFiles() method now support iOS and Android wildcards. | The file selection dialog box did not support multiple file masks. The search by mask in the file selection dialog box and the search by mask with FindFiles() method were case-sensitive. The file selection dialog box and FindFiles() method did not support iOS and Android wildcards. | Expanded file operation tools in the mobile platform. These tools are unified with file operation tools available in the desktop platform. |
| Formatted documents. | The mobile platform now supports FormattedDocument object (and can display formatted documents in managed forms). | This feature was not provided. | Expanded support of formatted text in mobile applications. |
| Mobile device-specific features. | On the mobile platform for Windows (except Windows 8.1), support of map operations is implemented. The following methods are now available: ShowOnMap(), GetAddressByLocation(), and GetLocationByAddress(). Global context method MapRepresentationSupported() is implemented. | Map operations were not supported on Windows mobile devices. | Extended mobile platform capabilities on Windows. Determining whether map operations are available is standardized with other operations that might be unavailable on some devices or operating systems. |
| Mobile applications. | When a configuration that was saved using an earlier 1C:Enterprise version for personal computer is loaded to a mobile application, the mobile device displays a warning and provides the option to cancel the operation. | When a configuration was loaded on a mobile device, 1C:Enterprise did not check whether the configuration was saved using an earlier 1C:Enterprise version for personal computer. | Implemented diagnostics of potential compatibility issues between the mobile platform and the configuration to be loaded (in scenarios where the configuration was saved using an earlier 1C:Enterprise version for personal computer). |
| Mobile device-specific features. | On Android devices, the following operations with SMS messages are implemented:
On Android devices, in method SMSLog.FindRecords(), ungrouped filter items are combined using AND operator. | On Android devices, access to SMS message log was not provided. On Android devices, in method SMSLog.FindRecords(), ungrouped filter items were combined using OR operator. | Introduced advanced SMS management tools on Android devices. The behavior of the filter used in a search in the SMS message log is unified with other filters. |
| Database configuration update. | In built mobile applications, the message stating that unused data will be deleted is no longer displayed after configuration updates. The mobile platform for developers displays a message stating that the update changes metadata structure (only when it actually changes it). The developers are now responsible for preventing data losses caused by configuration updates. | If a configuration update changed metadata structure, a message stating that unused data will be deleted was displayed after the update. The message was displayed both in built mobile applications and in the mobile platform for developers. | Configuration updates are now less distressing to end users. In patricular, end users do not get a message that their data will be lost (which was not always true). At the same time, developers must be more cautious when implementing configuration changes that might cause losses or user data. |
| Mobile device-specific features. | Universal date type values are now used in the following properties: CallLogRecord.Date, CalendarEventData.Start, and CalendarEventData.End. This change is not implemented in version 8.3.10 compatibility mode. | Local date type values were used in the following properties: CallLogRecord.Date, CalendarEventData.Start, and CalendarEventData.End. | Date presentation now meets the general requirements of 1C:Enterprise platform. |
| Mobile device-specific features. | The split screen implemented in Android 7 is no longer supported in the mobile platform. | The split screen implemented in Android 7 was supported incorrectly. | Eliminated unexpected system behavior. |
| Mobile device-specific features. | The mobile application now contains a set of predefined messages that describe mobile application demands on different permissions. They are displayed when a specific permission is required. Developers cannot modify these messages. | If a specific permission was required for a mobile application, a user prompt contained only the name of the permission and response variants.There was no reason of permission demand stated in the prompt. | The mobile application permission prompts now meet the requirements of application stores and provide more information about the required permission. |
Version 8.3.10 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.9 is now implemented. | Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.8 was implemented. | Configurations developed in version 8.3.9 or earlier now run in version 8.3.10 without requiring any changes to configuration or to data structures. This allows for transition to version 8.3.10 in two stages: first, version update is applied (without any changes to configuration); then, any needed changes are applied and compatibility mode is disabled. This also allows using version 8.3.9 for infobase operations, if necessary, after transition to version 8.3.10. Compatibility mode must be enabled to use version 8.3.9. If you disabled it, enable it again. |
| Web client, web service, and HTTP service publishing tools. | In the "publish to web server" dialog box, parameters related to OpenID authentication are now on a separate tab. In the "publish to web server" dialog box, also implemented entering a list of URLs that can be used for user redirection after OpenID authentication. | The only method of specifying a list of URLs that can be used for user redirection after OpenID authentication was to edit default.vrd file manually. | When publishing to web servers, you can interactlvely specify all of the parameters defined in default.vrd file. |
| Client application installation. | Rules for detecting computers with Ukrainian language pack are improved. When a 1C:Enterprise client application is being installed on Windows, the installer language and the default platform language are set to Ukrainian if at least two of the following conditions are met:
| When a 1C:Enterprise client application was being installed on Windows, the default platform language was set to Ukrainian only if the primary operating system language was Ukrainian. The only way to run the installer in Urkainian was using the /luk command-line option. | Improved 1C:Enterprise installer usability for Ukrainian speakers. |
| 1C:Enterprise script. Administration tools. | Implemented functionality for collecting information on circular references during 1C:Enterprise script execution. Using this feature may result in reduced application performance. It is recommended that you use this feature for testing purposes only. Implemented global context method CheckScriptCircularRefs(). For technological log settings file (logcfg.xml), implemented item <SCRIPTCIRCREFS>. Implemented technological log event <SCRIPTCIRCREFS>. Implemented command-line option for the thin client and thick client startup: /EnableCheckScriptCircularRefs. Implemented command-line parameter for 1C:Enterprise server startup: -EnableCheckScriptCircularRefs. In the dialog box used to specify client application startup parameters from Designer, implemented parameter Detect 1C:Enterprise script circular references. Implemented parameter EnableCheckScriptCircularRefs in file conf.cfg. If 1C:Enterprise is started with option/parameter EnableCheckScriptCircularRefs, discovery of any circular reference will result in unrecoverable error containing information on the discovered circular reference. | This feature was not provided. | Diagnostics of circular reference usage in 1C:Enterprise script is now more intuitive. |
| Configuration extensions. | In module editor, implemented functionality for adding a specific method to extension (when working with a configuration being extended). In module editor, implemented navigation from annotation of extending method to method being extended (when working with an extension). Implemented keyboard shortcut Alt+Shift+F2 for command Add to extension. Keyboard shortcut Alt+F2 for this command is now disabled. | User-friendly functionality for adding methods to extensions was not available. Navigation from annotation of extending method to method being extended was not available. Keyboard shortcut Alt+F2 was used for command Add to extension. | Creating 1C:Enterprise script-based module extensions is now more ergonomic. |
| Dynamic lists. | Implemented additional processing for data received by a dynamic list before the data is displayed. Implemented event OnGetDataAtServer. In version 8.3.7 compatibility mode, behavior remained unchanged. | This feature was not provided. | It is now easier to use dynamic lists to output linked data that was previously extremely difficult or impossible to obtain through dynamic list query. |
| Managed forms. | Implemented arbitrary scaling of managed forms in Taxi interface. If compact display mode is set at application level, interactive scaling is disabled. Form size settings are saved per DPI value and per form scale value. Implemented managed form property Scale, command Change scale in client application menu View, and system command bar button used to open the scale change dialog box. This change is not implemented in 8.3.6 compatibility mode. Implemented support for picture variant sets in client applications for PC (thick client, thin client, and web client). Added variants of system pictures used for client applications. Implemented new resolutions for picture variants: bldpi (85% scale), aldpi (125% scale), amdpi (175% scale), and udpi (400% scale). In picture variant set manifest, implemented choice of target interface for each variant. To define size of picture variants more precisely, implemented parameters for height and width of each variant in picture variant set manifest. For system enumeration PictureSize, implemented values RealSizeIgnoreScale and AutoSizeIgnoreScale. | This feature was not provided. Compact viewing mode was available at form level and at application level (through 1C:Enterprise script). Picture variant sets were supported in mobile application only. | Interface customization is now more user-friendly. |
| 1C:Enterprise script. | Implemented generation of text strings whose content depends on a number specified in a string. Examples: 1st week of the month, 2nd week of the month. Implemented the StringWithNumber() function. The following langauges are supported: Azerbaijanian, Belarusian, Chinese, Bulgarian, English, Estonian, Finnish, French, Georgian, German, Hungarian, Kazakh, Kyrgyz, Latvian, Lithuanian, Polish, Romanian, Russian, Turkish, Turkmenian, Ukrainian, and Vietnamese, | This feature was not provided. | Generation of text strings whose content depends on a number specified in a string is now streamlined. |
| Spreadsheet documents. | Implemented getting data area size value during import from third-party spreadsheet formats: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument). For object SpreadsheetDocument, implemented methods GetDataAreaHorizontalSize() and GetDataAreaVerticalSize(). | This feature was not provided. | It is now easier to import documents in third-party spreadsheet formats without clearly defined boundaries of imported data area. |
| Development tools. OData interface. | Implemented server debug item Standard OData interface intended for debugging 1C:Enterprise script running during queries to standard OData interface. Changed debug item sorting rules that apply to debug item lists (for HTTP debug protocol). Changed auto attachment dialog box (for TCP debug protocol). | Debugging of 1C:Enterprise script running at the server side during infobase calls through standard OData interface was not supported. Debug item sorting rules that apply to debug item lists (for HTTP debug protocol) were different. Auto attachment dialog box for TCP debug protocol displayed debug items in a different order. | It is now easier to debug 1C:Enterprise scripts using standard OData interface. |
| Managed forms. | The option to manage height for managed form tables that display data other than dynamic lists is implemented. This includes the option to have table height resized automatically based on the amount of data displayed. The HeightControlVariant managed form table property is implemented. This change is not implemented in 8.3.9 compatibility mode. | This option was not provided on the desktop platform. It was only available on the mobile platform. The HeightControlVariant managed form table property was ignored on the desktop platform. | The option to add a form table that does not display dynamic list data and still is automatically resized based on the number of rows is implemented. This reduces the number of scroll bars and saves form space. |
| Software licensing. Technological log. | For technological log, implemented registration of events associated with:
Implemented technological log event <LIC>. The <HASP> technological log event allows to analyze technological aspects of HASP management only (HASP interface calls); it does not allow to monitor granted or released licenses with HASP keys. | This feature was not provided. Only the option to check HASP key operations using the <HASP> event was provided. | Easier investigation of license-related issues. |
| Data composition system. | Values of type DataComposionSchemaNestedDataSet can now be added to collection DataComposionSchemaDataSetFields. Implemented values of type DataComposionSchemaDataSetFields to be used in methods Add() and Insert() of object DataComposionSchemaDataSetFields. | Values of type DataComposionSchemaNestedDataSet could not be added to collection DataComposionSchemaDataSetFields. | Now it is possible to create a data composition schema with nested data sets using 1C:Enterprise script. |
| Managed forms. | Implemented control of planner interval background color in accordance with values of measurements associated with this interval. Implemented property PlannerBackgroundInterval.DimensionValues. | Planner interval background color management based on the values of dimensions associated with this interval was not available. Planner interval background color could only be changed for date intervals. | Visual customization of planner is enriched. |
| Development tools. | Implemented option for running Designer in agent mode. This is a variation of batch mode where Designer operates as an SSH or SFTP server and accepts commands sent through these protocols. While in agent mode, Designer can only work with a single infobase at a time. If access to multiple infobases is required, it is recommended that you run several instances of Designer in agent mode. Implemented command-line options for batch mode: /AgentMode, /AgentPort, /AgentListenAddress, /AgentSSHHostKey, /AgentSSHHostKeyAuto, and /AgentBaseDir. Changed behavior of command-line options /Visible and /LoadConfigFromFiles when used in agent mode. If you need a client application to connect to SSH or SFTP servers, you can now use any application with SSH/SFTP functionality that supports text command exchange with SSH and SFTP servers (examples: putty, winscp, MobaXTerm). This functionality is currently available in beta status. | This feature was not provided. | Designer connectivity automation capabilities are now expanded. Response time of Designer is improved because a separate instance of Designer is no longer started on each call. |
| Formatted documents. | Implemented saving formatted documents in PDF format (both in interactive mode and by using method FormattedDocument.Write()) . Implemented value FormattedDocumentFileType.PDF. | This feature was not provided. Formatted documents could be only saved in HTML format or as plain text without formatting. | Formatted document management capabilities are now expanded. |
| Spreadsheet documents. | Implemented 1C:Enterprise script-based management of how row, column, and cell names are displayed in spreadsheet documents. For object SpreadsheetDocument, implemented properties ShowRowAndColumnNames and ShowCellNames. In spreadsheet document editor menu (in 1C:Enterprise mode), implemented commands for defining view of named areas and for assigning area names. | 1C:Enterprise script-based management of how row, column, and cell names are displayed in spreadsheet documents was unavailable. | It is now easier to organize editing of spreadsheet documents containing named areas. |
| Technological log. | Implemented logging of events that occur upon initial connection of 1C:Enterprise server to Microsoft SQL Server database. The events are saved in the technological log. The logging is based on event <DBMSSQLCONN>. | This feature was not provided. | It is now easier to investigate incidents associated with loss of connection between 1C:Enterprise server and Microsoft SQL Server database. |
| Configuration extensions. | The help available in a configuration being extended includes reference information on extension objects. The reference information on the extension is included in the help search results. | This feature was not provided. Reference information implemented in a configuration extension was missing from the help tree and could not be accessed through searching. | Eliminated unexpected system behavior. Reference information from an extension is included in the help available in the configuration being extended, making it easier to use the resulting configuration. |
| Spreadsheet documents. | When importing spreadsheet documents from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files, areas of the resulting document that match sheets of the original document are marked up as named row ranges. Names of sheets of the original document are converted into range names so as to satisfy rules of 1C:Enterprise script ID generation. When importing spreadsheet documents from Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) files, sheets with no names provided are imported normally and areas defining these sheets are given automatically generated names. This change is not implemented in 8.3.9 compatibility mode. | When importing spreadsheet documents from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files, areas of the resulting document that matched sheets of the original document were not marked up. When importing spreadsheet documents from Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) files, sheets with no names provided were not imported.
| It is now easier to process spreadsheet documents created by importing multipage XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files. It is now easier to recognize pages of the imported documents. |
| Configuration extensions. | For configuration extensions, implemented configuration extension purposes: Patch, Customization, and AddOn. Extensions are applied in the following order:
Multiple extensions with the same purpose are applied in no specific order. Purpose of extensions that are already loaded to the infobase is automatically set to Customization. Implemented property ConfigurationExtension.Purpose. | This feature was not provided.
All extensions were applied with the same priority.
| It is now possible to sort extensions by function. It is now easier to understand the purpose of any extension. |
| Configuration extensions. Spreadsheet documents. | Implemented extensions for spreadsheet documents. Implemented merging of spreadsheet documents during configuration update that uses a file in .cf or .cfu format. | The spreadsheet document extension feature was not provided. The feature allowing spreadsheet document merging during configuration update was not provided. | Configuration extension offers more features now. Additional spreadsheet document management features are now provided for supported configurations. |
| Pictures. | Implemented getting a specific picture from a picture variant collection based on DPI, display scale factor, and template picture flag. For methods Convert(), Write(), GetBinaryData(), and FileNameFilter() of Picture object , implemented parameters AllVariants and SelectVariant. | Platform behavior upon attempt to get a specific picture from a picture variant collection was not defined. This activity could result in system failure. | Eliminated unexpected system behavior. Getting a specific picture (best matching the current display mode) from a picture variant collection is now supported. |
| Charts. | Now fractional values can be used to define boundaries of gauge chart bands. This change is not implemented in 8.3.9 compatibility mode. | Fractional values could not be used to define boundaries of gauge chart bands. | An additional chart appearance control feature is now implemented. |
| Charts. Data composition system. | Implemented the following chart display options (also available in data composition system):
Implemented system enumerations ChartTrendlineApproximationType, ChartTrendlineFactor, StockChartUsedPointValue, ShowInChart, and ShowInChartLegend. For system enumeration ChartLabelLocation, implemented values: Auto, TopLeft, BottomLeft, TopRight, BottomRight, TopAndLeftSpecified, and EmptySpace. For system enumeration ChartMarkerType, implemented values Alternation and Auto. Implemented objects ChartLabelArea and ChartTrendline. For object ChartSeries, implemented properties Trendlines, ShowGraphicalDataRepresentationInChart, and ShowGraphicalDataRepresentationInChartLegend. For property ChartSeries.Marker, the default value is set to Auto. This change is not implemented in 8.3.9 compatibility mode. For objects DataCompositionAreaTemplateChartGroupAppearance and DataCompositionAppearance, implemented parameters ChartTrendline, ShowGraphicalDataRepresentationInChart, and ShowGraphicalDataRepresentationInChartLegend. | These features were not provided. Value of property ChartSeries.Marker was set to Rect, Circle, or Rhomb, based on series number. | Additional chart features, related to appearance control and analytics, are now implemented. |
| Charts. Data composition system. | Implemented new chart types: scatter chart and bubble chart. For Chart object, implemented properties BubbleSizeCommonSeries, BubbleSizeValueSource, DefaultBubbleSize, MinBubbleSize, MaxBubbleSize, ChartBubbleSizing, and BubbleChartNegativeValuesShowMode. Implemented the following chart management features:
Expanded set of values that can be used in chart labels. For ChartLabelType system enumeration, implemented values ValueSize, SeriesSize, SeriesValueSize, SeriesPointSize, SeriesPointValueSize, PointSize, and PointValueSize. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.ValuesAxis, ChartType.PointsAxis, ChartType.PointsAxisValuesSource, ChartType.PointsAxisSeries, ChartType.BubbleSizeValueSource, ChartType.BubbleSizeCommonSeries, ChartType.DefaultBubbleSize, ChartType.MinBubbleSize, ChartType.MaxBubbleSize, ChartType.ChartBubbleSizing, ChartType.BubbleChartNegativeValuesShowMode, and ChartType.PointsConnection. For data composition system object DataCompositionAreaTemplateChartGroupAppearance, implemented properties PutOnPointsAxis and UseAsCommonBubbleSizeSeries. Properties AutoMaxValue and AutoMinValue are now deprecated and supported for compatibility purposes only. | These features were not provided. Scatter charts and bubble charts were not implemented. Fractional values could not be used for properties MinValue and MaxValue of Chart object. Properties AutoMinValue and AutoMaxValue were used for calculating minimum and maximum chart values. | Additional chart features are now implemented. |
| Charts. Data composition system. | Implemented custom labels for chart scales. For ChartPlotArea object, implemented properties PointsScale, ValuesScale, and SeriesScale. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.PointsScale, ChartType.ValuesScale, and ChartType.SeriesScale. | These features were not provided. | Additional chart appearance control features are now implemented. |
| Charts. Data composition system. | Implemented custom point display order for bar charts. For Charts object, implemented property BarChartPointsOrder. This change is not implemented in 8.3.9 compatibility mode. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameter ChartType.BarChartPointsOrder. | These features were not provided. Points in bar charts were always displayed in bottom-to-top order (the first point at the bottom of the chart). | Additional chart appearance control features are now implemented. |
| Data composition system. Charts. | Implemented customization of scale lines, scale color, series markers, series indicators, and series line types when displaying charts. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.ScaleLines and ChartType.ScaleColor. For data composition system objects DataCompositionAreaTemplateChartGroupAppearance and DataCompositionAppearance, implemented properties LineInChart, MarkerInChart, and IndicatorInChart. | These features were not provided. | Additional features of chart appearance control through data composition system are now implemented. |
| Collaboration system. | Implemented the "collaboration system" feature that supports interaction between the server, client applications, and users of a single infobase. The collaboration system simplifies automation of enterprise business processes and provides an easy way to establish work-related communication. 1C:Enterprise application uses can exchange text messages and call each other (audio calls with optional video feed). Text conversations can be related to specific infobase objects (context conversations) or not related to any object (noncontext conversations). Access to conversations is allowed or denied based on the object access rights. Implemented Collaboration system management standard function. Implemented notifications about new messages. Implemented conversation management using 1C:Enterprise script tools. Implemented CollaborationSystem global context property. For ManagedForm object, implemented ConversationsRepresentation property. This property is not available in 8.3.9 compatibility mode. Implemented CollaborationSystemInfoBaseRegistration access right. The web client supports the collaboration system if it runs in one of the following browsers: Google Chrome, Mozilla Firefox, Safari, Microsoft Edge, or Microsoft Internet Eхplorer version 10.0 or later. All of the messages are stored on the collaboration system server. To start using the collaboration system, you have to register your infobase on the collaboration system server. Initially the server is available as the 1cDialog.com service hosted by 1C Company. Note that in order to use the collaboration system you have to open Internet access to wss://1cdialog.com. A distribution kit for a local collaboration system server will be available in a future release. Therefore, you will have a choice between using 1cDialog.com service and running a local server. Using calls is limited during the beta testing period. Call usage instructions will be available separately. This feature currently has beta status. The service access terms will be available separately. The email message with the registration code sent from 1cDialog.com when you request registration in the service will include instructions for enabling video calls. | This feature was not provided. | The new feature provides 1C:Enterprise application users with communication options that are tightly integrated into the application interface and business logic. |
| Dumping configurations to files/Restoring configurations from files. | Implemented partial dump of the configuration being edited to XML files. During partial dump, only objects that were modified since the previous dump are dumped. The file ConfigDumpInfo.xml containing information about all dumped configuration objects is created. This file also contains internal versions of all dumped objects. An object is not dumped during a partial dump if its version numbers in Designer and in file ConfigDumpInfo.xml are identical. Moreover, a file containing information about the differences between the current and the previous dump can be generated. When restoring data from XML files, users can specify that the file containing information about dumped configuration objects must be updated. In this case, information matching the configuration state after it is restored is saved to this file. For Designer batch mode command-line option /DumpConfigToFiles, implemented parameters update, force, getChanges, configDumpInfoForChanges, and listFile. For Designer batch mode command-line option /LoadConfigFromFiles, implemented parameter updateConfigDumpInfo. | Partial dump of configurations to XML files was not supported. Only full configuration dump was implemented. | Dumping configurations to XML files is now faster. especially dumping very large configurations with minor changes. |
| Dynamic lists. | Implemented management of availability of dynamic list fields (including subordinate fields) for use in groupings, filters, and order settings. Implemented methods SetRestrictionsForUseInGroup(), SetRestrictionsForUseInOrder(), SetRestrictionsForUseInFilter(), GetRestrictionsForUseInGroup(), GetRestrictionsForUseInOrder(), and GetRestrictionsForUseInFilter(). | These features were not provided. | Now developers can explicitly prohibit groupings, ordering, and filtering for fields not intended for these operations. |
| Window-based interface. Dumping configurations to files/Restoring configurations from files. | Implemented visibility management for managed form title. Implemented property ManagedForm.ShowTitle.
Implemented visibility management for form closing button. Implemented property ManagedForm.ShowCloseButton.
Implemented selection of main application window display mode.
Implemented global context property ClientApplication that provides access to client application settings (such as getting and changing the client application window title). For metadata object that describes the configuration, implemented property MainClientApplicationWindowMode. Changed version number of format used for dumping configurations to files. The following global context methods are now deprecated. It is recommended that you do not use any of these: SetShortApplicationCaption(), GetShortApplicationCaption(), SetClientApplicationCaption(), GetClientApplicationCaption(), ClientApplicationBaseFontCurrentVariant(), and ClientApplicationInterfaceCurrentVariant(). The above features are available in Taxi interface. | These features were not provided. | Expanded capabilities of client application appearance management. Now a specific interface can be enabled (cashier's interface, self-service kiosk, and more). |
| Configuration extensions. Common attributes / Data separation. | Implemented a flag specifying whether a common attribute used as a separator can separate configuration extensions. For CommonAttribute configuration object, implemented property ConfigurationExtensionsSeparation. It is recommended that you disable extension separation for separators in Independent and shared mode. | Any configuration separators could be used to separate configuration extensions. Disabling extension separation was not possible if data separation was enabled at infobase level. | Now developers have control over separation of configuration extensions to be used in the infobase. For example, a configuration developer can specify that none of the separators available in the application can be used to separate configuration extensions. |
| Client application. | For the thin and thick client applications that directly connect to a 1C:Enterprise server, the disconnection monitoring mechanism is implemented. If a server connection issue is detected, the client application automatically attempts to reestablish the connection and repeat the server call. If the connection cannot be established, the application is shut down. The following timeouts are applied:
The timeout values cannot be changed. | If any server connection issues occurred in the thin or thick client application that was directly connected to a 1C:Enterprise server, the client application might stop responding for a long period (several minutes). That period was defined by TCP stack settings in the operating system. | Improved reliability of client applications that directly connect to a 1C:Enterprise server. Reduced chance of situations when an application stops responding. |
| DBMS operations. System requirements. | Support of PostgreSQL version 9.6 is implemented. | This PostgreSQL version was not supported. | Extended list of supported PostgreSQL versions. |
| DBMS operations. System requirements. | Support of Postgres Pro Enterprise version 9.6 is implemented (only in managed lock management mode). | Postgres Pro Enterprise was not supported. | Extended list of supported DBMS versions. |
| System requirements. Web client. | Ended support of Mozilla Firefox versions 51 and earlier. | Mozilla Firefox versions 51 and earlier were supported. | Ended support for legacy Mozilla Firefox versions. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Web client. Spreadsheet documents. | Implemented automated marking of blank fields when entering data into spreadsheet documents in the web client. | Automated marking of blank fields was not performed when entering data into spreadsheet documents in the web client. | Eliminated unexpected system behavior. |
| Managed forms. | Implemented changes to calculation of page tab size and the appearance of page tabs in vertical mode.
Implemented scaling of pictures in page tabs when changing DPI (both for thin client and thick client). This change is not implemented in 8.3.9 compatibility mode. Implemented slight size and position changes for several types of managed form items. Changed appearance of slider (both in Taxi interface and in the web client with Version 8.2 interface). The slider appearance in the web client differs from its appearance in the thick and thin clients. The size of the colored picture used for input fields that display data of Color type differs between the web client and the thick/thin clients. Changed appearance of system forms (in Taxi interface for both thick and thin clients) for better conformity with general visual interface style. Increased hit boxes for icons that collapse and expand tree nodes in tables (in Taxi interface). Improved appearance of controls for non-standard DPI values. Modified size calculation for slider fields in forms. | The interface appearance was different. Pictures in page tabs were not resized when changing DPI (both for thin client and thick client). | Improved appearance of client applications. |
| Managed forms. | Changed appearance of form navigation panel in Taxi interface. In Russian localization, the name of panel item Main is now slightly changed. All commands are displayed in the form navigation panel. Full names are displayed for all of the panel commands. If a command does not fit the form actions panel, the command is displayed in the More menu. | Appearance of form navigation panel was different. In Russian localization, the name of panel item Main was slightly different. The following rule was in force when displaying commands: if the Important group contained more than two commands, only two commands were displayed on the navigation panel. Commands that did not fit the form navigation panel were available through the More menu. Long names were shortened and marked with ellipses (...) both in the thick and thin clients. | Application UI was improved. |
| Interface. | The opened items panel was redesigned in Taxi interface:
| Appearance and functionality of the opened items panel (in Taxi interface) were different:
| It is now easier to use the opened items panel in Taxi interface. |
| Spreadsheet documents. Web client. | All border types are now displayed in spreadsheet documents opened in the web client. Appearance of border lines of spreadsheet documents opened in the web client depends on the browser and may differ from appearance of border lines of spreadsheet documents opened in the thick or thin client. | Only border lines of these types were displayed for spreadsheet document cells: Solid, Dotted, and None. All other line types were replaced by the above types as follows:
| Eliminated unexpected system behavior. Border lines of spreadsheet documents opened in the web client now more closely conform to border lines of spreadsheet documents opened in the thick or thin client. |
| Managed forms. | If the freeze area of a managed form table exceeds the visible area of the table, column freeze is canceled automatically. This change is not implemented in 8.3.9 compatibility mode. | If the freeze area exceeded the size of the whole table, the table could not be scrolled horizontally. | It is now easier to work with tables in small forms. |
| Data composition system. | In the "Main" data composition appearance template used in Taxi interface, text color is set to Auto for all template areas except the report header. This change is not implemented in 8.3.9 compatibility mode | In the "Main" data composition appearance template used in Taxi interface, gray text color was used for some of the template areas (except the report header). | Now optimal text color is chosen whenever a report is displayed or printed, improving readability. |
| Dynamic lists. | Implemented sorting for dynamic lists by clicking any column header in the table displaying dynamic list data, provided that the query text contains aggregate functions and GROUP BY expressions. This change is not implemented in 8.3.7 compatibility mode. | Dynamic list sorting by clicking any column header in the table displaying dynamic list data was not supported, regardless of whether the query text contained aggregate functions or GROUP BY expressions. | Behavior of tables displaying dynamic list data is now more intuitive and predictable. |
| Managed forms. | In the thin and thick clients, the wheel button scrolls a form item where mouse cursor is currently located (provided that such form item is scrollable). The form item is scrolled regardless of whether it has received input focus. After the form item is fully scrolled, the parent form item starts scrolling (provided that it is scrollable). | In the thin and thick clients, the wheel button only scrolled active form items. In the web client, the wheel button scrolled both active and nonactive form items. | Managed form navigation is now more user-friendly. Unified scrolling behavior between the web client, the thin client, and the thick client. |
| Client application. Data display. | All standard pictures used by client applications are implemented as sets of pictures optimized for a variety of DPI and display scale values. Standard pictures are redesigned. | Standard pictures used by client applications were not optimized for current DPI and display scale values. Therefore, applying non-standard DPI could result in blurry standard pictures. | Optimized appearance of client interface for non-standard DPI and display scale values. |
| Client application installation. | If any issue occurs during the thin client update over HTTP, you have the option to get the name of the file that cannot be updated. This option is provided in the following scenarios:
| If any issue occurred during the thin client update over HTTP, the option to get the name of the file that cannot be updated was not available. In particular, there was no way to get the file name of a corrupted archive of the name of the file that had invalid digital signature.
| Improved issue diagnostics during the thin client update over HTTP. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Server clusters. | Improved server cluster scalability for the following cases:
Reduced amount of RAM used by 1C:Enterprise server to run applications that utilize batch queries. | Poor server cluster scalability was observed in the following cases:
1C:Enterprise server used a significant amount of RAM to run applications that utilized batch queries. | Improved 1C:Enterprise server cluster scalability. |
| Встроенный язык. | Faster 1C:Enterprise script execution by 1C:Enterprise server. | The performance of 1C:Enterprise script execution by 1C:Enterprise server was insufficient. | Optimized 1C:Enterprise script execution by 1C:Enterprise server. |
| Data composition system. | Faster initialization of data composition settings composer by source of available data composition settings when using schemas with a large number of calculated fields. | The performance of initialization of data composition settings composer by source of available data composition settings when using schemas with a large number of calculated fields was insufficient. | Improved performance of data composition system initialization in several scenarios. |
| Server clusters. | Reduced amount of RAM used by 1C:Enterprise server to run applications that utilize batch queries. | Significant amount of RAM was used by 1C:Enterprise server to run applications that utilize batch queries. | Optimized amount of RAM used by 1C:Enterprise server to run batch queries. |
| Configuration repositories. | Optimized updating of local cache of configuration storage when putting objects into storage and getting objects from storage. | The performance of putting objects into configuration storage and getting objects from storage was insufficient. | Putting objects into configuration storage and getting objects from storage is now faster. |
| Development tools. | Implemented retention of module search index between Designer sessions. Reduced time required for initial generation of module search index. Significantly reduced time required for module search index generation during all subsequent Designer sessions. Running Designer with command-line option /ClearCache clears the module search index. | Module search index was not retained between Designer sessions. Index generation required significant time. | It is now easier to work with large configurations. |
| 1C:Enterprise script. | When searching for strings in a value table using the FindRows() method, the index is only analyzed for column content matches between the search parameters and the index. The relative order of columns in the search parameters or in the index is ignored during the search. | When searching for strings in a value table using the FindRows() method, the index was only used if the relative order of columns in the search parameters matched the index column order. | Using the index to search value tables by multiple columns is now faster. |
| Full-text search. | Optimized full-text search index generation and update. | The performance of initial generation and updates of full-text search index was insufficient. | Updating the full-text search index is now faster. |
| DBMS operations. Queries. | Improved processing speed of queries containing keyword DISTINCT that get a large number of records (in file infobases). | Processing speed of queries containing keyword DISTINCT that get a large number of records (in file infobases) was insufficient. | Getting large lists of unique records from file infobases is now faster. |
| DBMS operations. Queries. | Faster deletion of large record sets from file infobases. Faster recalculation of totals for tables with a large number of records in file infobases. | The following operations in file infobases were insufficiently fast:
| File infobases now work faster in some scenarios. |
| Dynamic lists. | Improved performance when getting data displayed as dynamic list with conditional formatting.
| The performance of getting data displayed as dynamic list with conditional formatting was insufficientl. | The performance of dynamic lists with conditional formatting is now improved. |
| Dynamic lists. | Faster opening of forms containing dynamic lists with complex queries. | The performance of opening forms containing dynamic lists with complex queries was insufficient. | Forms containing dynamic lists with complex queries now open faster. |
| Dynamic lists. | For dynamic lists, implemented the option to enable or disable getting presentations for values of reference types that are not displayed in the form or are associated with invisible form items. Presentations of key field values for dynamic lists in selection mode are obtained regardless.
Implemented dynamic list property GetInvisibleFieldPresentations. This change is not implemented in 8.3.7 compatibility mode. | In dynamic lists, presentations were obtained for all reference type values to be sent to client side. | Dynamic lists can now be displayed faster in some cases. |
| Data composition system. | Optimized RAM usage when composing data composition templates with large queries in data composition schema. | RAM usage when composing data composition templates with large queries in data composition schema was sub-optimal. | Composing data composition templates with large queries in data composition schema now requires less RAM. |
| Infobase operations. | Slightly improved thin client startup time in file infobases when working with large configurations. | Startup time of the thin client in file infobases when working with large configurations was insufficient. | Startup time of the thin client in file infobases when working with large configurations is now improved. |
| Configuration repositories. | Optimized object lock and release operations in configuration repositories. Changed internal format of locked object data storage for infobases connected to repositories. The data storage format is changed after the data storage optimization operation is completed using the Local repository data usage settings dialog box. This optimization is only available if the configuration was bound to a configuration repository in an earlier platform version. To use the optimized infobase in an earlier platform version, rebind the infobase to the configuration repository in an earlier platform version. | The performance of object lock and release operations in configuration repositories was insufficient. | Working with configuration repositories that store large configurations is now faster. |
| Client application. | Improved startup time of client applications after dynamic update. | Client applications required longer time to start after dynamic update. | Improved startup time of client applications after dynamic update. |
| Web services and HTTP services. | Every time a method of a web or HTTP service is called, the compiled service module is cashed. | Every time a method of a web or HTTP service was called, the service module was compiled. | Improved system performace in scenarios that include a large number of web or HTTP services calls. |
| Accounting registers. DBMS operations. | Improved performance of the following accounting register record set operations for infobases running in file mode or in client/server mode with PostgreSQL:
| The performance of the following accounting register record set operations was insufficient in infobases running in file mode or in client/server mode with PostgreSQL:
| Optimized accounting register operations for some DBMS. |
| DBMS operations. | Optimized query plan generation for PostgreSQL version 9.6.3. This improves the performance of complex queries that use data access restriction templates. Optimization is available for PostgreSQL versions 9.6.3-2.1C and later. | In PostgreSQL, performance of complex queries that used data access restriction templates was insufficient, in some cases applications might stop responding during query execution. | Improved performance of PostgreSQL operations initiated from 1C:Enterprise. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Background and scheduled jobs. Server clusters. | Changed approach to storing background and scheduled job execution history. In client/server mode, the stored history data was broken down by infobase. The following history data is stored for each infobase:
For each job (background, scheduled, or system background), information about at least 3 latest job executions is saved, if possible. The three executions limit can be reduced if over 1 000 records are created for any given job type. | In file mode, the stored job history data was broken down by infobase. In client/server mode, the stored job history data was broken down by server cluster. In both cases, data was stored on the total of 1 000 jobs, regardless of job type (background, scheduled, or system background). | Improved diagnostics of background and scheduled job execution when a large amount of jobs is present in the system. Reduced risk of information about rarely used 1C:Enterprise script-based background jobs being superseded by information about a large amount of scheduled jobs or system background jobs. |
| Data display. Charts. | For objects Chart, GanttChart, PivotChart, and Dendrogram, the default value of Font property of subordinate objects describing specific chart areas is set to Auto, meaning Normal text font. When the web client is running on Windows, the procedures of displaying charts in the web client, exporting spreadsheet documents containing charts to HTML5 format, and exporting charts to SVG format include checks for OS-based substitutions of chart fonts. If the OS substitutes chart fonts, the resulting files include the names of the fonts that are actually used. When exporting spreadsheet documents to HTML format and displaying spreadsheet documents in the web client, system fonts are not substituted by Arial; instead, the names of the fonts that are actually used are determined. | For objects Chart, GanttChart, PivotChart, and Dendrogram, the default value of Font property of subordinate objects describing specific chart areas was set to Text font. When the web client was running on Windows, the procedures of displaying charts in the web client, exporting spreadsheet documents containing charts to HTML5 format, and exporting charts to SVG format included exporting fonts "as is", without attempting to determine which fonts were actually used. When exporting spreadsheet documents to HTML format and displaying spreadsheet documents in the web client, system fonts were substituted by Arial. | Unified fonts used to display charts across client applications, including the web client running in a variety of web browsers. Unified fonts used to display spreadsheet documents across client applications. When exporting spreadsheet documents containing charts, original fonts used to display the charts are retained. |
| Binary data. | Binary data management capabilities are now expanded. Implemented bilateral conversion between binary data and the following data types: binary data array, string, binary data buffer, Base64 string, hexadecimal string, and binary data as string. Implemented binary data usage in methods and constructors that previously supported files only. Implemented bitwise operations (AND, OR, NOT, XOR, NAND, and inversion) for binary data stored in a binary data buffer. Implemented binary data exchange with add-ins for add-in developers (also available in the web client). Implemented getting bulk permissions when working with binary data in the web client. Implemented direct copying of binary data from DataReader object to DataWriter object. Implemented global context methods ConcatBinaryData(), SplitBinaryData(), GetBinaryDataFromString(), GetBinaryDataBufferFromString(), GetStringFromBinaryData(), GetStringFromBinaryDataBuffer(), GetBinaryDataFromBase64String(), GetBinaryDataBufferFromBase64String(), GetBase64StringFromBinaryData(), GetBase64BinaryDataFromBinaryData(), GetBinaryDataFromBase64BinaryData(), GetBase64BinaryDataBufferFromBinaryDataBuffer(), GetBinaryDataBufferFromBase64BinaryDataBuffer(), GetBinaryDataFromHexString(), GetBinaryDataBufferFromHexString(), GetHexStringFromBinaryData(), GetHexStringFromBinaryDataBuffer(), GetHexBinaryDataFromBinaryData(), GetBinaryDataFromHexBinaryData(), GetHexBinaryDataBufferFromBinaryDataBuffer(), GetBinaryDataBufferFromHexBinaryDataBuffer(), GetBinaryDataFromBinaryDataBuffer(), GetBinaryDataBufferFromBinaryData(), NumberFromHexString(), and NumberFromBinaryString(). Implemented the option to use binary data streams:
Implemented OpenStream() method for objects HTMLReader, HTMLWriter, JSONReader, JSONWriter, FastInfosetReader, FastInfosetWriter, XMLReader, and XMLWriter. Implemented GetBodyAsStream() method for objects HTTPRequest, HTTPResponse, HTTPServiceRequest, and HTTPServiceResponse. Implemented method ConversionToCanonicalXML.CanonicalizeToStream(). For XSLTransform object, implemented methods LoadXSLStyleSheet() and Transform(). Implemented method ZipFileWriter.GetBinaryData(). For BinaryDataBuffer object, implemented methods WriteBitwiseAnd(), WriteBitwiseOr(), WriteBitwiseXor(), WriteBitwiseAndNot(), and Invert(). For DataReader object, implemented methods CopyTo() and BeginCopyTo(). For methods CopyTo() and BeginCopyTo() of Stream object, changed the purpose of the second method parameter and the return value: the number of bytes to be copied is passed as the second parameter, and the return value is the actual number of copied bytes. The buffer size is defined automatically. The method descriptions are now uniform with the similar methods of DataReader object. This change is not implemented in 8.3.9 compatibility mode. | For methods CopyTo() and BeginCopyingTo() of Stream object, the size of buffer used for copying was passed as the second parameter, and return values were not available. | It is now easier to use binary data for a range of applied tasks. |
| Event log. | In the event log (opened from a file or otherwise), each data presentation string recorded to the log when an event was registered is only displayed to users that have the right to view this data or Administration right. If a user does not have Administration right and the data presentation is probably unavailable to them, the saved data presentation is hidden from this user. If the Data field of an event log record contains a reference and a user probably has no rights to view the related data object, the Data presentation field is blank. | Access rights of the current user were not checked when displaying presentation of event log data. | Users with restricted rights no longer can access data objects that are unavailable to them by accessing presentations of unavailable objects that were saved earlier. |
| Development tools. | In the call stack window of the debugger, implemented correct display of method parameters containing extremely long text strings or multiline strings. In this case, the presentation is based on the initial 20 characters of the parameter string appended with ellipsis (...), continued with other parameters and the closing bracket of the method. | In the call stack window of the debugger, method parameters containing extremely long text strings or multiline strings were displayed incorrectly: text presentations of the following parameters (if any) and the closing bracket of the method were missing. | The accuracy of data in the call stack window is improved. |
| Spreadsheet documents. | When exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats, only right-aligned cell text is converted into numeric format. The content of cells without right alignment is saved as text. This change is not implemented in 8.3.9 compatibility mode. | When exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats, cell text was converted into numeric format regardless of text alignment. | Exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats is improved. |
| Print tools. | Implemented settings for default page size during printing (including printing to PDF file). This feature is available both for the web client and for documents generated by scheduled jobs. Implemented the PrintSettings object. In the web client parameters dialog box, implemented Default page size settings item. This change is not implemented in 8.3.9 compatibility mode. | A4 format was used as the default paper size. In the web client parameters dialog box, Default page size settings item was not available. | When printing a document (or saving it to a PDF file) in the web client, the paper size set for the current client application is used for pagination purposes. Thus, the resulting document better satisfies user expectations. This functionality is now also available for the documents generated by scheduled jobs. |
| Data composition system. | When loading data composition schema and data composition settings in interactive mode, style colors and fonts not available in the current configuration are automatically removed from the schema and settings. | When loading data composition schema and data composition settings in interactive mode, style colors and fonts not available in the current configuration caused XDTO data conversion errors.
| Now data composition schema and data composition settings containing style colors and fonts not available in the current configuration can be used. |
| Dynamic lists. | Content of System fields folder cannot be used as selection fields in dynamic lists.
If a dynamic list has no main table specified or the specified main table is missing a dynamic list key field, grouping fields cannot be set up for this dynamic list. This change is not implemented in 8.3.9 compatibility mode. | Content of System fields folder could be used as selection fields in dynamic lists. If a dynamic list had no main table specified or the specified main table was missing a dynamic list key field, grouping fields could be set up for this dynamic list, resulting in data retrieval error. | Eliminated unexpected system behavior. Dynamic lists are more reliable now. |
| Dynamic lists. | The following properties of DynamicList object are unavailable in the thick client: DynamicDataRead, MainTable, CustomQuery, and QueryText. Assigning values to managed form attributes of DynamicList type is not allowed. Passing attributes of DynamicList type as method parameters or return values in client/server interactions is not allowed. This change is not implemented in 8.3.9 compatibility mode. | The following properties of DynamicList object were available in the thick client: DynamicDataRead, MainTable, CustomQuery, and QueryText. However, changing their values did not affect the dynamic lists in any way. Assigning values to managed form attributes of DynamicList type was allowed. However, further behavior was not defined. Passing attributes of DynamicList type as method parameters or return values in client/server interactions was allowed. However, further behavior was not defined. | Dynamic lists are more reliable now. The listed cases of dynamic list misuse are no longer supported. |
| Charts. | Series data (marker) in a chart legend depends on the appearance of the series in the chart (line color, line style, and marker). This change is not implemented in 8.3.9 compatibility mode. | Series data in chart legend was always represented by a square marker of color matching color of the series in the chart. | Chart readability is now improved (best results for charts printed in black and white). |
| Data composition system. | Templates of resources created at intersection with matching predefined templates of grouping titles are initially blank. This change is not implemented in 8.3.9 compatibility mode. | Resources were displayed in templates of resources created at intersection with matching predefined templates of grouping titles. | Eliminated unexpected system behavior. |
| Cryptography support. | If a serial number of a certificate starts with a set high bit, a leading zero byte is appended to the serial number. This change is not implemented in 8.3.8 compatibility mode. | A leading zero byte was not appended to serial numbers of certificates. | Defects in encryption management logic are corrected. |
| Dynamic lists. | Implemented disabling auto filling of available fields in dynamic lists. This option is only available for dynamic lists generated using custom queries. The system behavior is identical to the similar data composition schema option. Implemented dynamic list property AutoFillAvailableFields. This change is not implemented in 8.3.7 compatibility mode. | Auto filling of all available fields was enabled for all dynamic list queries. | Availability of the list fields can now be changed by the extension of the query language for data composition schema. |
| Charts. Data composition system. | Implemented management of series display order in chart legends (also available in the data composition system). Implemented property Chart.SeriesOrderInLegend. For ChartType appearance item of DataCompositionAreaTemplateChartAppearance, DataCompositionChartOutputParameterValues, DataCompositionOutputParameterValues, and DataCompositionGroupOutputParameterValues objects, implemented parameter SeriesOrderInLegend. This change is not implemented in 8.3.9 compatibility mode. | Series display order in chart legends could not be changed. | Additional chart display features are now implemented. |
| Development tools. | The user is asked if they want to save their work whenever they attempt to close the query expression editor dialog box (in the query wizard) by pressing Esc or clicking the Close button (X) after making changes to the expression in the editor. | The user was not asked if they want to save their work whenever they attempted to close the query expression editor dialog box (in the query wizard) by pressing Esc or clicking the Close button (X) after making changes to the expression in the editor. This behavior resulted in loss of user work. | Eliminated unexpected system behavior. Reduced risk of loss of user work when editing query expressions. |
| Development tools. | Improved diagnostics and system behavior when an invalid or missing manifest is discovered in a picture archive:
| The system behavior was different when an invalid or missing manifest was discovered in the picture archive:
| Improved diagnostics and system reliability when accessing picture archives with invalid or missing manifests. |
| Dumping configurations to files/Restoring configurations from files. | During full restoration of a configuration from files, the following rules apply:
During partial restoration of a configuration from files, the following rules apply:
| Dumping and restoring configurations from files were executed regardless of whether a configuration is covered by support or connected to a configuration repository. | Eliminated issues that occurred when attempting to restore a configuration that is covered by support or connected to the configuration repository from files. |
| Dynamic lists. | Improved algorithm for searching through search boxes of dynamic lists:
This change is not implemented in 8.3.9 compatibility mode. | Searching through search boxes of dynamic lists was implemented as follows:
| Improved searching using search boxes of dynamic lists. |
| Dynamic lists. | Fields that cannot be used in filters are not available in the advanced search dialog box of dynamic lists (i.e. not displayed in the Search in field list). If the current column of the table associated with the dynamic list displays a field that cannot be used in filters, the command that starts the search by current value is not available. | Fields that could be used in filters were available in the advanced search dialog box of dynamic lists (i.e. displayed in the Search in field list). Availability of the command that starts the search by current value was not affected by whether the field displayed in the current column of dynamic list can be used in filters. | Eliminated unexpected system behavior. |
| Administration tools. | During the verification and repair of a file infobase, infobase table records are deleted if their keys become non-unique after the records are modified. At that, a diagnostic message is displayed in the message window.
| During the verification and repair of a file infobase, keys of infobase table records were not checked for uniqueness after the records were modified. This could result in records with non-unique keys occurring in the infobase. To remedy this, it was necessary to run the infobase verification and repair procedure once more. | Unified behavior of infobase verification and repair procedure between file and client/server infobase modes. |
| 1C:Enterprise script. | Enumerations are present in type selection dialog boxes and type description dialog boxes for all client applications running in managed application mode. This change is not implemented in 8.3.9 compatibility mode. | Enumerations were not present in type selection dialog boxes and type description dialog boxes for thick client and thin client applications running in managed application mode. However, enumerations were present in these dialog boxes for the web client. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | When exporting spreadsheet documents to Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) format, the name of XML component of shared strings starts with a lowercase letter: sharedStrings.xml. This change is not implemented in 8.3.9 compatibility mode. | When exporting spreadsheet documents to Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) format, the name of XML component of shared strings started with an uppercase letter: SharedStrings.xml. | The platform behavior now conforms to OpenXML standard. Improved compatibility with case-sensitive systems parsing OpenXML files. |
| Managed forms. Dynamic lists. | Implemented the Main attribute flag for managed form attribute of DataCompositionSettingsComposer type. In this case, Managed form extension for settings composer serves as form extension. The User-defined settings group form property and OnUpdateUserSettingSetAtServer event handler are now available for the form. | Managed form property Main attribute was only set for automatically generated forms of dynamic list settings. Developers were not allowed to create these forms. | Developers can now create all-purpose data composition settings editing forms. |
| Development tools. | When comparing and merging modules (without using third-party tools), placement of methods in areas defined by preprocessor instructions (#Region, #If) is taken into account. Areas defined by preprocessor instructions are isolated as separate entities (together with procedures and functions). For these areas, implemented specifying the merging parameters. | This feature was not provided. The preprocessor instructions were processed as comments linked to the procedures they preceded. Module merging could result in corrupted structure of blocks defined by preprocessor instructions. | Module merging performed by native Designer tools is now more reliable and user-friendly. |
| Managed forms. | The navigation panel of the item form of an hierarchical catalog or chart of characteristic types contains:
The navigation panel of the group form of an hierarchical catalog or chart of characteristic types contains:
This change is not implemented in 8.3.9 compatibility mode. | All commands used to access subordinate catalogs were located in the navigation panel of the item form of an hierarchical catalog or chart of characteristic types. The navigation panels of group forms of these configuration objects did not contain any of the commands used to access subordinate catalogs. All commands used to access information registers were located in the navigation panel of the item form of an hierarchical catalog or chart of characteristic types. The navigation panels of group forms of these configuration objects did not contain any of the commands used to access information registers. | Eliminated unexpected system behavior. |
| Development tools. Dumping configurations to files/Restoring configurations from files. | In the "dump configuration to files" feature, changed the dump format of information about dynamic lists located in managed forms. It is recommended that you dump all forms containing dynamic lists once more. | In the "dump configuration to files" feature, the dump format of information about dynamic lists located in managed forms was different. | In the "dump configuration to files" feature, the format of resulting XML files is improved. |
| Database configuration update. | Messages about creation and deletion of options tables for charts of characteristic types, charts of accounts, charts of calculation types, and catalogs are not displayed when updating database configuration. | Messages about creation and deletion of options tables for charts of characteristic types, charts of accounts, charts of calculation types, and catalogs were displayed when updating database configuration. | Messages that contain no useful information for the user are no longer displayed when updating database configuration. |
| Charts. |
Expanded set of palettes that can be used to customize chart colors. The palettes can contain either fixed color sets or color sets that vary depending on the quantity of series. Implemented creation of custom color sets for charts. For ChartColorPalette system enumeration, implemented values Auto, Custom, Gradient, Blue, Orange, Green, Yellow, Gray, Warm, Cold, Bright, Soft, and Pastel. For Chart object, implemented the following:
For ChartType appearance item of data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ColorPalette, GradientPaletteStartColor, GradientPaletteEndColor, and GradientPaletteMaxColors | Only two palettes (with 8 and 32 colors respectively) were available for picking chart colors. Creation of custom chart color palettes was not supported. | Additional chart appearance features are now implemented. |
| Data composition system. | When data composition output processor outputs merged cells to a spreadsheet document, width of the columns containing merged cells is adjusted in order to minimize height of the content of these cells. This change is not implemented in 8.3.9 compatibility mode. | When data composition processor outputted merged cells to a spreadsheet document, width of the columns containing merged cells was not adjusted in some cases. This could result in inappropriately narrow columns. | Calculation of width of spreadsheet document columns containing merged cells performed by data composition output processor is improved in some cases. |
| Accounting registers. | The PointInTimeWithPeriodAdjustment type is available in the thin and web clients. | The PointInTimeWithPeriodAdjustment type was available only in the thick client and only on the server. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | For spreadsheet documents, the option to paste data that has XLS (Microsoft Excel 97-2003) or ODS (OpenDocument Spreadsheet) format is added to the Paste special operation. | For spreadsheet documents, the option to paste data that has XLS (Microsoft Excel 97-2003) or ODS (OpenDocument Spreadsheet) format was not available. | The Paste special operation now supports selection from all spreadsheet formats that support pasting. |
| Spreadsheet documents. Data composition system. | For spreadsheet documents, the option to automatically adapt column width to the display area is implemented (both for viewing and printing). For SpreadsheetDocumentRange and DataCompositionAreaTemplateTableCellAppearance objects, implemented properties HorizontalStretch and WidthWeightFactor. For DataCompositionAppearance object, implemented appearance parameters HorizontalStretch and WidthWeightFactor. When the data composition system displays a chart in a spreadsheet document, it automatically sizes the chart to fit the display area width. This change is not implemented in 8.3.9 compatibility mode. | Spreadsheet document column width could not be adapted to the display area width. When the data composition system displayed a chart in a spreadsheet document, the chart had fixed width. | Improved options for adapting spreadsheed documents to the display area. |
| Spreadsheet documents. | For form field extension for a spreadsheet document field, the following improvements are implemented:
| The following options were available for form field extension for a spreadsheet document field:
| Extended display options for spreadsheet documents embedded in managed forms. |
| Managed forms. | In managed form tables, improved algorithm for automatic column width calculation based on the font settings. This change is not implemented in 8.3.9 compatibility mode. | The algorithm for automatic column width calculation based on the font settings sometimes generated poor results. | Improved view of managed form tables. |
| Dumping configurations to files/Restoring configurations from files. | When restoring help topics from XML files, 1C:Enterprise does not check whether the language of the help topics (Language configuration object) is available in the configuration. | When restoring help topics from XML files, 1C:Enterprise did not restore the help topics whose language (Language configuration object) was not available in the configuration. | Simplified dumping and restoration of configurations, external reports, and external data processors to or from XML files. |
| Development tools. Configuration extensions. | Configuration extension bookmarks, breakpoints, and performance measurements are stored with extension names. | Configuration extension bookmarks, breakpoints, and performance measurements were stored with internal extension IDs. | Support for future integration of extension debugging with 1C:Enterprise Development Tools. |
| macOS. Spreadsheet documents. | Implemented export of spreadsheet documents to PDF format on macOS. | An attempt to export a spreadsheet document to PDF format on macOS generated an error. | Eliminated unexpected system behavior. |
| Operating system. | The time zone detection algorithm on Windows is modified. Now the time zone is determined as follows:
| The platform used the following time zone detection algorithm on Windows:
| The session time zone is determined correctly on Windows terminal servers. |
| DBMS operations. | If 1C:Enterprise is running in managed lock mode (in client/server mode) with PostgreSQL version 9.3 or later, it supports setting lock waiting time. The waiting time is retrieved from the infobase parameters, just like in configurations that use other DBMS types. | If 1C:Enterprise was running in managed lock mode (in client/server mode) with PostgreSQL version 9.3 or later, it did not support setting lock waiting time. In configurations that used PostgreSQL, setting lock waiting time was only supported in automatic lock mode. | In configurations that used PostgreSQL, operations with lock waiting time in managed mode are identical to operations with lock waiting time in configurations that use other DBMS. |
| Charts. Spreadsheet documents. | When a spreadsheet document that contains a chart is saved to a file, automatically assigned point colors, series colors, and series markers are stored in the format supported by earlier 1C:Enterprise versions. This ensures that the colors and markers are displayed correctly in earlier 1C:Enterprise versions. | When a spreadsheet document that contained a chart was saved to a file, automatically assigned colors and markers were stored in the format that was not supported by earlier 1C:Enterprise versions. This might significantly alter the chart look in earlier 1C:Enterprise versions. | The look of spreadsheet documents with charts in earlier 1C:Enterprise versions is very similar to their look in 1C:Enterprise version 8.3.10 or later. |
| Internet-enabled functionality. | The DigiCert certifying center root certificate was added to the cacert.pem file (root certificates file), included in the platform. | The DigiCert certifying center root certificate was not included in the cacert.pem file (root certificates file).
| 1C:Enterprise applications can now connect to 1C company services. Service infrastructure update is needed. |
| External reports and data processors. | The option to disable the warning of the unsafe operation protection system when you create an external report or data processor object is implemented (use it when you are sure that the file specified in the method parameter contains trusted script). For the Create() method of ExternalReportsManager and ExternalDataProcessorsManager objects, the UnsafeOperationProtection parameter is implemented. | This feature was not provided. | When adding an external report or an external data processor from a file, you can specify that the file contains trusted script and therefore does not require displaying the unsafe operation protection system warning. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Managed forms. | When collapsing a node of a value tree with subordinate items that is displayed in a managed form, event BeforeCollapse is generated for each node being collapsed throughout the hierarchy. This change is not implemented in 8.3.9 compatibility mode. | When collapsing a node of a value tree with subordinate items that is displayed in a managed form, event BeforeCollapse was only generated for top-level tree items. | Eliminated unexpected system behavior. Value tree items to be collapsed are now defined more precisely in interactive mode. |
| Access rights. | Calling the AccessRight() method generates an exception if the access right being checked cannot be applied to a metadata object. This change is not implemented in 8.3.9 compatibility mode. | Calling the AccessRight() method always returned True if the access right being checked could not be applied to a metadata object. | Eliminated unexpected system behavior. |
| Data composition system. | Data composition schema parameters whose types contain only types disabled by functional options are added to the list of available data composition schema parameters with disabled visibility. Therefore, these parameters cannot be edited by users but can still be accessed from 1C:Enterprise script. Moreover, these parameters are not added to the list of available parameter fields. When a report option is loaded, the usage flag is cleared for the data parameters disabled by functional options. The DataCompositionSettingsComposer.Refresh() method disables the Use property of data parameters disabled by functional options. This change is not implemented in 8.3.9 compatibility mode. | Functional options did not affect the visibility of data composition parameters. When a report option was loaded, the usage flag was not cleared for the data parameters disabled by functional options. The DataCompositionSettingsComposer.Refresh() method did not modify the Use property of data parameters disabled by functional options. | Management of report parameters of types disabled by functional options is now more user-friendly. |
| HTML support. | For HTMLDocumentShell object, implemented property TemplateLanguageCode. If this property is set, the following methods of this object return a result for the specified language: GetCOMObject(), GetHTMLDocument(), and GetText(). | Selection of language to be used in return values of HTMLDocumentShell object methods was not available for HTML templates. | Now HTML templates can be used for languages that do not match the language of the current session. |
| System requirements. | Changed presentation of Microsoft Windows version, starting from Windows Vista, in SystemInfo.OSVersion property. The property text contains the user presentation of the operating system name, as well as technical information (version, build number, and so on). This change is not implemented in 8.3.9 compatibility mode. | Presentation of Microsoft Windows version, starting from Windows Vista, in SystemInfo.OSVersion property did not contain the user presentation of operating system name. | Information about Microsoft Windows version stored in SystemInfo.OSVersion property (for systems running on Microsoft Windows) now offers better readability. |
| Web services and HTTP services. Internet-enabled functionality. | When method HTTPConnection.CallHTTPMethod() is called, its parameter HTTPMethod must comply with RFC 7230 Read more.. If this requirement is not met, an exception is raised. This change is not implemented in 8.3.9 compatibility mode. | When method HTTPConnection.CallHTTPMethod() was called, its parameter HTTPMethod could take up any value. | The behavior of 1C:Enterprise better complies with RFC standards now. |
| DBMS operations. | When a 1C:Enterprise application runs in client/server mode using a Microsoft SQL Server database, a query containing expression CAST(... AS STRING(...)) adds trailing space characters to the operation result until it reaches the required length. This change is not implemented in 8.3.9 compatibility mode. | When a 1C:Enterprise application ran in client/server mode using a Microsoft SQL Server database, a query containing expression CAST(... AS STRING(...)) did not add trailing space characters to the operation result until it reached the required length. | 1C:Enterprise behavior is now uniform across all supported databases. |
| XML and XDTO support. | Serialization of a ValueList object using the XDTOFactory.WriteXML() method creates an XML document based on the schema used for serialization of this object with XDTOSerializer.WriteXML() method. Due to this change:
| Serialization of a ValueList object using the XDTOFactory.WriteXML() method created an XML document that did not match the schema used for serialization of this object with XDTOSerializer.WriteXML() method. | Eliminated unexpected system behavior. |
| Managed forms. | If a hyperlink is displayed in a managed form table cell and Read only mode is set for this table cell, double-clicking this cell results in raising the Selection table event once. This change is not implemented in 8.3.9 compatibility mode. | If a hyperlink was displayed in a managed form table cell and Read only mode was set for this table cell, double-clicking this cell resulted in raising two Selection table events. | Eliminated unexpected system behavior. |
| Development tools. | For event subscriptions, implemented the match check for events and source types. The check is performed prior to saving the configuration. If the event does not match the source type, an error is generated and the configuration is not saved. This change is not implemented in 8.3.9 compatibility mode | For event subscriptions, the match check for events and source types was not performed. | Eliminated unexpected system behavior. |
| Queries. | An error is generated during query analysis if the expression following the temporary table name does not contain the field name. This change is not implemented in 8.3.9 compatibility mode. | During query analysis, if the expression following the temporary table name did not contain the field name, the name of the first field of the temporary table was used instead. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | When displaying spreadsheet documents in Taxi interface, the Auto text color is selected as follows:
This change is not implemented in 8.3.9 compatibility mode. | When displaying spreadsheet documents in Taxi interface, black was always used as the Auto text color. | Eliminated unexpected system behavior. |
| Managed forms. | For attributes of String or Number type displayed in a managed form input field with list selection mode enabled:
This change is not implemented in 8.3.9 compatibility mode. | When editing values of Number type in a managed form input field with list selection mode enabled, number qualifiers configured for the attribute were affecting format of the text being edited. | Improved usability of text input fields. |
| Spreadsheet documents. | When processing a template in a spreadsheet document cell, content located between the final section [] and an escaped character [ is not removed from the result. This change is not implemented in 8.3.9 compatibility mode. | When processing a template in a spreadsheet document cell, content located between the final section [] and an escaped character [ was removed from the result. | Eliminated unexpected system behavior. |
| Internet-enabled functionality. | When 1C:Enterprise is running on Microsoft Windows, web server certificate checks are performed for all chains of trusted certificates registered in the Windows trusted certificate store. | When 1C:Enterprise was running on Microsoft Windows, web server certificate checks could fail if a trusted parent certificate of the certificate being checked was not registered in the trusted certificate store. | Eliminated situations that could occur on Microsoft Windows when 1C:Enterprise failed to check a web server certificate via HTTPS/FTPS if the server certificate publisher was not included in the list of trusted root certificates. |
| Full-text search. | If a full-text search query generates multiple intermediate results and the search result contains under 1 mln records, the user gets the search result. This change is not implemented in 8.3.9 compatibility mode. To enable this feature, set the configuration compatibility mode to None and update the full-text search index. The later a data item was modified, the higher in the full-text search results it is displayed (within a single configuration object, such as a document type). | If a full-text search query generated multiple intermediate results, the error stating that there are too many search results was displayed to the user. | Full-text search now returns results when searching for several words that commonly occur separately but rarely occur together. |
| Client application installation. | Searching the distribution kit directories for new 1C:Enterprise versions when opening the infobase list window is now faster. The search is performed for the names of distribution kit directories.
Distribution kit type and bitness are determined based on the name of .msi file:
| Searching the distribution kit directories for new 1C:Enterprise versions was insufficiently fast because it relied on data stored in properties of .msi files. | The infobase list dialog box now opens faster if the Install new application versions automatically check box is selected in the dialog box settings. |
| Managed forms. | When attempting to create a managed form group with an invalid value of Type property using 1C:Enterprise script, an exception is raised. This change is not implemented in 8.3.9 compatibility mode. | When attempting to create a managed form group with an invalid value of Type property using 1C:Enterprise script, the system behavior was not defined and could result in abnormal termination. | Eliminated unexpected system behavior. |
| Data composition system. | Implemented setting expressions simultaneously both for detailed records and totals records of user-defined fields of the data composition system. Implemented the same for user-defined field presentations in detailed records and totals records of the data composition system. For DataCompositionUserFieldExpression object, implemented methods SetExpressions() and SetExpressionsPresentation(). Methods SetDetailRecordExpression(), SetTotalRecordExpression(), SetDetailRecordExpressionPresentation(), and SetTotalRecordExpressionPresentation() are now deprecated and supported for compatibility purposes only. It is recommended that you do not use any of these. | Expressions of user-defined fields of the data composition system for detailed records and totals records were set by different methods. Presentations of user-defined fields of the data composition system for detailed records and totals records were also set by different methods. | Eliminated unexpected system behavior. User-defined fields of the data composition system that contain deleted or renamed query fields in both expressions are now editable. |
| Data composition system. | When automatically filling available fields of query data set for virtual tables of information registers, dimension fields become available for filtering based on virtual table parameters. This change is not implemented in 8.3.9 compatibility mode. | When automatically filling available fields of query data set for virtual tables of information registers, dimension fields did not become available for filtering based on virtual table parameters. | Getting data from information registers through the data composition system is now more efficient when virtual tables of information registers are used. |
| Queries. | When adding filter expressions to a query by using QuerySchemaExpression object constructor, the filter expressions are added without conversion. This change is not implemented in 8.3.9 compatibility mode. | When adding filter expressions to a query by using QuerySchemaExpression object constructor, the filter expressions were corrupted due to conversion. | Eliminated unexpected system behavior. |
| Configuration repositories. | New configuration repositories are created in version 8.3.8 format, with page size 8192 bytes. You can use the cnvdbfl utility to change configuration repository format from version 8.2.14 to version 8.3.8 and vice versa. | The configuration repository database was created in version 8.2.14 format. | You can set the configuration repository format to version 8.3.8. Repositories that have this format can store larger reporitory history. |
| Accounting registers. | If an accounting register resource value is associated with the accounting flag for a chart of accounts, values of this resource in Balance, Turnovers, BalanceAndTurnovers, and DrCrTurnovers virtual tables depend on the status of this accounting flag for each account. If the accounting flag is set, the resource value has Number type. If the accounting flag is cleared, the resource has value is NULL. This change is not implemented in 8.3.9 compatibility mode. | Virtual tables of accounting registers (Balance, Turnovers, BalanceAndTurnovers, and DrCrTurnovers) could return non-NULL values of accounting register resources associated with accounting flags for accounts where these accounting flags were disabled. | Eliminated unexpected system behavior. |
| Web client. Client application. Interface. Managed forms. Applied objects. | Ended support of modal windows in the web client, regardless of web browser used. Any modal method call performed by an application now raises an exception. For the thin client and web client, ended support of document posting performed in the mode interactively specified by the user. Accessing a document with such posting mode now raises an exception. The system enumeration value PostingModeUse.Ask is no longer supported by the thin client and web client. The window opening option (Window parameter) is now ignored when used in methods OpenForm() and GetForm(), and when used as a structure property value CommandExecuteParameters.Window (with type defined by system enumeration WindowOpenVariant). In the thin client, the Window parameter is ignored when the compatibility mode is disabled. The system enumeration WindowOpenVariant is excluded from the Syntax Assistant. In the thin client and web client, forms can no longer be opened in separate windows when Forms in tabs interface mode is enabled. In the web client, ended support of interface mode Forms in separate windows. In the thin client, interface mode Forms in separate windows cannot be enabled through the client application parameters dialog box. In the web client, ended support of the web client command-line parameter isdi. The check whether popup windows are blocked is not performed when starting the web client. | Windows that locked other windows were supported in the web client. Document posting mode could be specified by the user interactively, as a part of the posting procedure. In the thin client and web client, forms could be opened in separate windows when interface mode Forms in tabs was enabled. In the web client, interface mode Forms in separate windows was supported. | Ended support of interface mode not supported by the current web browsers. |
| Interface. Data display. | For global context method ShowUserNotification(), implemented parameters UserNotificationStatus and UniquenessKey. The parameter of URL method is renamed to ActionOnClick. The look of notifications with Information status is slightly changed. In Taxi interface, notifications with Important status are redesigned, including the following changes:
Implemented notification management through the notification center. Dragging the notification window is not supported. For the specifics of notification behavior depending on the operating system and the client application, refer to the documentation. | These features were not provided. Capabilities of global context method ShowUserNotification() were limited. | Notifications with Important status are implemented. They are displayed even if the application window is inactive. |
| Charts. Spreadsheet documents. | Implemented the availability to open details for Gannt charts displayed in spreadsheet documents. The procedure is identical to opening details for Gannt charts displayed in managed forms. For spreadsheet document event handlers DetailProcessing and AdditionalDetailProcessing, implemented parameter AdditionalParameters. This parameter stores the date that is used as an input parameter for retrieving the details. This change is not implemented in 8.3.9 compatibility mode. The context menu of Gantt charts in spreadsheet documents now opens on releasing the right mouse button. This change is not implemented in 8.3.9 compatibility mode. | Any attempt to access details for a Gantt chart in a spreadsheet document resulted in opening a window containing a noninteractive list of details. Spreadsheet document event handlers DetailProcessing and AdditionalDetailProcessing had only two parameters (and did not have the AdditionalParameters parameter). The context menu of Gantt charts embedded in spreadsheet documents opened on clicking the right mouse button. | Eliminated unexpected system behavior. The behavior of Gantt chart details in spreadsheet document is now standardized. |
| Charts. Web client. | If chart properties Adjust series and Adjust points are set to False, series colors or point colors now use the custom color palette in the thin client. This change is not implemented in the web client .
This change is not implemented in 8.3.9 compatibility mode.
| If chart properties Adjust series and Adjust points were set to False, series colors or point colors used the default color palette in the thin client, and the custom color palette in the web client. | Eliminated inconsistencies in chart appearance between the web client and thin client. |
| Charts. | During chart deserialization, if Adjust series or Adjust points property is set to False, series colors or point colors use the custom color palette (they are set once the palette is loaded). This change is not implemented in 8.3.9 compatibility mode. | During chart deserialization, if Adjust series or Adjust points property is set to False, series colors or point colors used the default color palette. | Eliminated unexpected system behavior. |
| Charts. | During interactive chart editing, if Adjust series or Adjust points property is set to False, the following operations are performed:
This change is not implemented in 8.3.9 compatibility mode. | During interactive chart editing, parameters controlling appearance of series or points were not set to default values if Adjust series or Adjust points property was set to False. | Eliminated unexpected system behavior. |
| Charts. | If Adjust series or Adjust points chart property is set to False, any attempt to change series properties or point properties for this chart by using 1C:Enterprise script raises an exception. This change is not implemented in 8.3.9 compatibility mode. | Attempts to change a series or point property for a chart by using 1C:Enterprise script did not raise an exception if Adjust series or Adjust points chart property was set to False. The property was set for series or point instead. | Invalid chart use is not allowed now |
| Common objects. | In a value table generated using the Unload() method of a tabular section of any object, names of predefined columns are generated in 1C:Enterprise script language variant specified in the Script variant configuration property. This change is not implemented in 8.3.9 compatibility mode. | In a value table generated using the Unload() method of a tabular section of any object, predefined column names could be accessed in the following 1C:Enterprise script language variants:
| Eliminated unexpected system behavior. |
| Background and scheduled jobs. Common attributes / Data separation. | When a background job is started with a uniqueness key specified, the key uniqueness is verified within the area described by the current set of separators. For each unique set of separators, you can run a single background job with a uniqueness key specified. This change is not implemented in 8.3.9 compatibility mode. | When a background job was started with a uniqueness key specified, the key uniqueness was verified within the entire infobase, regardless of the separator values. | You can run a background job in each unique data area. For example, you can run long calculations in different areas of a separated infobase and avoid conflicts related to duplicate uniqueness keys. |
| Managed forms. | If the Cancel parameter of OnOpen managed form handler is set to True, once the handler execution is completed, the memory occupied by the form is cleared, all related resources (temporary storage, locks, and so on) are released, and idle handlers are disabled. This change is not implemented in 8.3.9 compatibility mode. | If the Cancel parameter of OnOpen managed form handler was set to True, once the handler execution was completed, in some scenarios the memory occupied by the form was not cleared. Consequently, all related resources (temporary storage, locks, and so on) were not released, and idle handlers were not disabled. | Eliminated unexpected system behavior. |
| Managed forms. | Implemented the option to apply through alignment (Through alignment property) to managed form groups with United property set to False. This change is not implemented in 8.3.9 compatibility mode. | For managed form groups with United property set to False, the value of the Through alignment property was ignored. | Eliminated unexpected system behavior. |
| Linux. System requirements. | 1C:Enterprise system requirements for Linux computers are modified. The freetype library is now included in 1C:Enterprise distribution kit and excluded from the list of libraries whose availability is verified at 1C:Enterprise startup. | The freetype library was not included in 1C:Enterprise distribution kit. Its availability was verified at 1C:Enterprise startup. | The system requirements for Linux computers are simplified. |
| Managed forms. | If FixingInTable property of a managed form table column group is set to Left or Right, all of the columns belonging to the group are fixed, as well as all other columns with this property set to Left or Right. This change is not implemented in 8.3.9 compatibility mode. | If FixingInTable property of a managed form table column group was set to Left or Right, only columns to the left or to the right of the group, respectively, were fixed. The columns included in the group were not fixed. | Eliminated unexpected system behavior. |
| Managed forms. | If a managed group form of "command bar" type has GroupVerticalAlign property set to Auto and it belongs to a group or form with ChildItemsVerticalAlign property set to Auto, the command bar is displayed at the top of the parent group (just below the last item). This change is not implemented in 8.3.9 compatibility mode. | If a managed group form of "command bar" type had GroupVerticalAlign property set to Auto and it belonged to a group or form with ChildItemsVerticalAlign property set to Auto, the command bar was displayed at the bottom of the parent group. | Eliminated unexpected system behavior. |
| Dynamic lists. | In dynamic list search field, values that can be interpreted as numbers in exponential notation are treated as strings (the platform searches for the specified string). This change is not implemented in 8.3.9 compatibility mode. | In dynamic list search field, values that could be interpreted as numbers in exponential notation were treated as numbers (the platform searched for the number). | Eliminated unexpected system behavior. |
| Data composition system. | The Use property of data parameters that can be edited by users but are disabled by functional options is disabled in the following scenarios:
This change is not implemented in 8.3.9 compatibility mode. | The Use property of data parameters that were disabled by functional options was disabled in the following scenarios:
| Improved compatibility with data composition system queries created using previous 1C:Enterprise versions. |
| 1C:Enterprise script. Web client. | In the web client, Title() function only converts strings that contain only Latin characters (A-Z, a-z), numbers, and special characters. In other client applications and on the server, Title() function behavior remains unchanged: the conversion rules are defined in the Unicode standard. | In the web client, Title() function always returned the source string. | Corrected the behavior of Title() function. |
| System requirements. Administration. | 1C:Enterprise distribution packages for Windows and macOS include HASP Device Driver 7.63. | 1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 6.60 or 7.60. | 1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver. |
| Applied objects. | After restructuring a chart of calculation types, the order of lines in tabular sections of predefined calculation types changes. | The order of lines in tabular sections of predefined calculation types was different. | Changed line order in tabular sections of predefined charts of calculations types. If your application algorithms depend on the line order, we recommend that you eliminate the dependencies. |
| Add-ins. System requirements. | The add-in development technology now supports Web Extensions API for Mozilla Firefox. It is recommended that you rebuild add-in distribution packages for Mozilla Firefox with new template projects. The resulting add-ins will be compatible with the same 1C:Enterprise 8 versions as before. Updated the template project included in the add-in development technology (read more) | The add-in development technology did not support Web Extensions API for Mozilla Firefox. | The add-in development technology is adapted to new Mozilla Firefox requirements. Mozilla Firefox versions 57 and later do not support add-ins that use other interfaces rather then Web Extensions API. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile device-specific features. | Implemented the following location features:
Implemented the Geofence object. Implemented LocationRelativeToGeofence system enumeration. Implemented LocationProviderInformation.Available property. Implemented AvailableOnly parameter for the following methods of LocationTools object: GetProviders(), GetProvider(), GetMostAccurateProvider(), and GetMostPowerSavingProvider(). For LocationTools object , implemented methods: LocationDataUseEnabled(), AttachProvidersAvailabilityChangeHandler(), DetachProvidersAvailabilityChangeHandler(), EnableGeofencesMonitoring(), GetMonitoredGeofences(), GetMonitoredGeofence(), DisableGeofencesMonitoring(), DisableAllGeofencesMonitoring(), and AttachMonitoredGeofencesBordersCrossingDetectionHandler(). | These features were not provided. | Location management capabilities are now expanded. For example, predefined actions can be performed when a mobile device reaches a specific location. |
| Binary data. | Implemented binary data management capabilities for the mobile platform. | This feature was not provided. Binary data management capabilities were only available for the PC platform. | Binary data management capabilities are now implemented for the mobile platform. |
| Internet-enabled functionality. | Implemented check whether a mobile device is in roaming mode. The Internet connection change handler is called when the roaming mode status is changed. Implemented method InternetConnectionInformation.GetRoamingUsage(). | Check whether a mobile device is in roaming mode was not implemented. | A variety of actions can be performed when roaming mode is enabled on a mobile device. For example, access to mobile Internet can be restricted or prohibited due to high Internet charges in roaming. |
| Internet-enabled functionality. | For mobile platforms running on Windows, implemented secured connection management capabilities. | Secured connection management capabilities were not available for mobile platforms running on Windows. | Mobile platforms running on Windows can now access resources that require secured connection. |
| Cryptography support. | Implemented encryption operations for the mobile platform. The mobile platform behavior is identical to that of the thin client. Details of the encryption operations are described in the documentation. Implemented CryptoManager.ShowCertificateList() method. Implemented CryptoKeysContainer object. Changed behavior of the following methods of CryptoCertificateStore object on the mobile platform: Add(), Delete(), BeginAdding(), and BeginDeleting(). | Encryption operations were not implemented for the mobile platform. | On the mobile platform, you can implement a check whether a document stored locally was modified. Sensitive data and documents can now be securely sent through open channels thanks to encryption capabilities. |
| Mobile device-specific features. | For the mobile platform, implemented a check whether contacts and calendars can be added or edited. For ContactManager object, implemented methods ContactEditingSupported() and ContactsAddingSupported(). For CalendarsManager object, implemented methods CalendarEditingSupported() and CalendarsAddingSupported(). The CalendarManager.CalendarEditingSupported property is now deprecated and supported for compatibility purposes only. For 1C:Enterprise applications running on Windows, the CalendarManager.EventEditingSupported() method always returns False. | The check whether contacts can be added or edited was not implemented. The check whether calendars can be added or edited was implemented in a different way. | Unified contacts and calendar management as related to adding and editing objects. |
| Mobile device-specific features. | Implemented new configuration permission: Ads. This permission is only used by the mobile application builder when selecting a mobile platform version for iOS to be used in the builds. If the Ads permission is used in the configuration export file, The app uses ads check box is unavailable in the mobile configuration form of the mobile application builder. | The permission specifying that ads are allowed for a mobile application was not implemented in the configuration. Instead, The app uses ads check box in the mobile application builder was used for this purpose. | Now the mobile application builder can be forced to use an advertisement-enabled mobile platform version for iOS in the builds. |
| File operations. | For the mobile platform, implemented getting thumbnails for pictures and video files stored in the corresponding libraries of the mobile device. This feature requires the file path to start with content: schema. For File object , implemented methods GetMobileDeviceLibraryFileThumbnail() and BeginGetMobileDeviceLibraryFileThumbnail(). | This feature was not provided. It was possible to fully load a picture or video file into memory when a thumbnail could be used instead | Optimized mobile device memory use when loading pictures or video files from the corresponding libraries of the mobile device. Reduced risk of insufficient memory error for mobile applications that load a large number of pictures or video files from the corresponding libraries of the mobile device. |
| Managed locks. | Implemented data lock management for mobile platforms. Implemented global context methods LockDataForEdit(), UnlockDataForEdit(), SetLockWaitTime(), and GetLockWaitTime(). Implemented methods IsLocked(), Lock(), and Unlock() for objects CatalogObject, DocumentObject, and ExchangePlanObject. Implemented method AccumulationRegisterRecordSet.LockForUpdate(). Implemented method ManagedForm.LockFormDataForEdit(). Implemented DataLock and DataLockItem objects. For Document, Catalog, and ExchangePlan configuration objects, implemented the DataLockFields property. For Configuration, Document, Catalog, ExchangePlan, Constant, Sequence, AccumulationRegister, and InformationRegister configuration objects, implemented DataLockControlMode property. | Managed lock support was not provided on the mobile platform. | Object lock management during background job execution on the mobile platform is now available. |
| File operations. | Implemented getting a file mask that describes all files, as well as getting a file path separator character, regardless of the mobile operating system where 1C:Enterprise is running. Implemented methods GetAllFilesMask(), GetClientAllFilesMask(), GetServerAllFilesMask(), GetPathSeparator(), GetClientPathSeparator(), and GetServerPathSeparator(). Implemented method BeginGettingMobileDeviceLibraryDir(). | Getting a file mask that describes all files and getting a file path separator character regardless of the mobile operating system used was not supported. | File operations in mobile applications are nearly operating system-agnostic now. |
| System requirements. | Implemented Android 7.0 support. Implemented multiwindow mode for Android 7.0.
For Android versions 6.0 or earlier:
| Multiwindow mode was not supported for Android 7.0. Dynamic resolutions were not supported for Android versions 6.0 or earlier. Dynamic resolution management was not supported for Android versions 6.0 or earlier. | Improved support of Android versions 6.0 and earlier. |
| Mobile device-specific features. | Implemented barcode scanning capability for mobile devices running Windows 10. Barcode scanning is not supported for mobile devices running Windows 8.1 or earlier. For devices running Windows 10, implemented availability of MultimediaTools.ShowBarcodeScanning() method, while MultimediaTools.BarcodeScanningSupported() method returns a value specifying whether barcode scanning functionality is available. For successful barcode scanning, continuous auto focus mode must be supported for the primary device camera. | Barcode scanning was not supported for mobile devices running Windows. | Expanded mobile platform capabilities for devices running Windows 10. |
| Managed forms. | For the mobile platform, implemented form field extension for the calendar field. The form field extension for the calendar field does not support dragging. | This feature was not provided. | Expanded Data type data management capabilities for mobile platform forms. |
| Print tools. | Printing is now supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64). | Printing was not supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64). | Extended mobile application capabilities on Windows. |
| Mobile applications. | Hardware rendering support is implemented for user interface on Android devices. | This feature was not provided. | Improved performance of user interface generation on Android devices. |
| Mobile application builder. | In the mobile application builder, automatic deletion of obsolete data is implemented. Obsolete data is defined as mobile application builds and mobile platforms that were last changed (or imported) before a specific date. This date is calculated as follows: current date minus the specified number of days (the gap size). You can specify custom gaps for mobile application builds and mobile platforms. Default values:
If you set the gap size to 0, obsolete objects are never deleted. When you attempt to use an obsolete object, the mobile application builder prompts you to rebuild the mobile application or reimport the mobile platform.
| The mobile application builder did not provide tools for automatic deletion of obsolete objects. | You have the option to keep the size of the mobile application builder infobase within reasonable limits, avoiding significant growth of the disk space occupied by this infobase. |
| Mobile application builder. | The requirements to Android SDK components used to build mobile applications are defined by the requirements of the mobile platform version used to build the applications. The builder uses the latest Android API Level available on the computer, provided that the API Level meets the mobile platform requirements. The requirements to other Android SDK components are defined by Android API Level requirements. If the mobile platform was loaded in a previous builder version, the builder requires Android API Level version 24 or later. | The following Android SDK components were required to build mobile applications for Android:
These requirements were applied regardless of the mobile platform versions used to build mobile applications. They were hardcoded in the mobile application builder. | The requirements to mobile application build infrastructure for Android are defined by the mobile platform version, instead of the requirements hardcoded in the mobile application builder. |
| Mobile application builder. | In mobile application builder, Gradle tool now can be used to build mobile applications. On Android SDK version 26 or later, you can build mobile applications using no other tools besides Gradle. You can specify two Android SDK paths in the builder settings: one for version 25 or ealier and the other one for version 26 or later. Therefore, you can build mobile applications that require any specific Android SDK version. Building with Gradle requires Java 8 on the computer that runs mobile application builder. It does not require Apache Ant. | Mobile application builder did not support building mobile applications with Gradle tool. | Building mobile applications that use new Android SDK versions is now available. |
| Mobile applications. | Since mobile platform version 8.3.10.71, only building mobile applications with Gradle tool is supported. Use mobile application builder provided as a part of the mobile platform distribution package to build mobile applications. Since mobile platform version 8.3.10.71, Apache Ant is not required for building mobile applications. | Mobile platform versions earlier that 8.3.10.71 did not support Gradle. Building the mobile platform required Apache Ant. | The mobile application building procedure is modified to comply with the changes in the recommended application building procedure for Android. |
| System requirements. Mobile application builder. | In the mobile platform, implemented iOS 11 support. Extended graphical asset collection for mobile applications that run on iOS 11. The mobile application builder supports the new graphical asset collection and building applications for iOS 11. | The mobile platform did not support iOS 11. | Implemented support of the latest operation system for Apple devices. |
| Error handling. | In the event of unexpected shutdown of a mobile application on Android, 1C:Enterprise displays a dialog box with a detailed error description, with the option to copy the error description to the clipboard. | In the event of unexpected shutdown of a mobile application on Android, no error details were displayed. | Simplified diagnostics of unexpected shutdown causes. Applications users can send error details to mobile application developers. |
| Interface. Mobile platform. | A spreadsheet document now supports the Output right on a mobile device. If the Output right is disabled, the following functions are not available: copying to clipboard, printing and saving the displayed data. | A spreadsheet document did not support the Output right on a mobile device. The following functions were always available: copying to clipboard, printing and saving the displayed data. | Eliminated unexpected system behavior. |
To enable this feature, set the configuration compatibility mode to None and update the full-text search index.
Version 8.3.9 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.8 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, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, 8.3.6, and 8.3.7. | In version 8.3.9 you can run configurations created in version 8.3.8 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.9 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also gives you the option to use version 8.3.8 for working with the infobase even after the transition to version 8.3.9. You can use this option both before and after removing the compatibility mode (in the latter case you have to turn the compatibility mode back on). |
| Configuration extensions. 1C:Enterprise script. | In configuration extensions, the option to adopt the following objects is implemented:
The option to adopt ordinary form modules and ordinary application modules is not available.Therefore, you can adopt any module except for modules that are used solely in ordinary applications. The following operations are now available:
Export methods and variables of the extended module form the uniform context of the extended module. Adopted form modules are now handled differently. You have the option to allow or deny extending all modules of abovementioned types (the all module extensions security profile property). You have the option to provide a list of modules where extension is allowed (the Modules available for extension property) or where extension is denied (the Modules not available for extension property). You have the option to create common modules in configuration extensions. For ISecurityProfile object, the following properties are implemented: AllModulesExtension, ModulesAvailableForExtension, and ModulesNotAvailableForExtension (software administration of server clusters based on COM objects). For ISecurityProfile interface, the following methods are implemented: getAllModulesExtension(), setAllModulesExtension(), getModulesAvailableForExtension(), setModulesAvailableForExtension(), getModulesNotAvailableForExtension(), and setModulesNotAvailableForExtension() (Java interface for server administration). In the server cluster command-line utility (rac), for the profile command, the following parameters are implemented: all-modules-extension, modules-available-for-extension, and modules-not-available-for-extension. | The option to adopt modules was not available, except for form modules. The option to create common modules in configuration extensions was not available. Adopted form modules were handled differently. The option to specify which modules can be extended was not available. | The configuration extensions feature now provides the option to extend all 1C:Enterprise script modules, except for those used solely in ordinary applications. New security profile options related to configuration extensions. |
| Web services and HTTP services. OData interface. Configuration extensions. Server clusters. | The option to manage session lifetime when using Internet services and the standard OData interface is implemented:
For web services and HTTP services, the ReuseSessions and SessionMaxAge properties are implemented. If a web service or HTTP service is a native configuration extension object, these properties are read-only. The following additions to the default.vrd file are implemented:
The enableStandardOData attribute of the <point> element is deprecated. If a web service or an HTTP service is a native configuration extension object and it is either not published in the default.vrd file or published without the session reuse option, session reuses are not available for that service. A server cluster service that manages the automatic pool of reused sessions is implemented. The service name is SessionReuseService (Session reuse service). | This feature was not provided. A new session was created for each Internet service call and each standard OData interface query. | Improved performance of Internet services and the standard OData interface. |
| Formatted documents. | The behavior of the Tab key is changed:
The FormattedDocumentBookmark object is linked to a character within a paragraph, not to a character position. If a text is changed, the bookmark position better matches its original position. | Pressing Tab always increased the indent. The FormattedDocumentBookmark object was linked to a character position within a paragraph. | Formatted document behavior better meets user expectations. |
| Binary data. | Tools for operations with binary data are implemented. They provide the following options:
The following objects are implemented: BinaryDataBuffer, Stream, FileStream, MemoryStream, DataReader, DataWriter, ReadDataResult, FileStreamsManager. The BinaryData.Size() method is now available in the web client. For the BinaryData.Write() method, the option to write data to a stream is implemented. The OpenStreamForRead() method is implemented, it opens a stream for reading binary data specified in the BinaryData object. | These options were not provided. The only available options were reading files from disk and writing files to disk without any means to perform any other operations with those files. | Extented capabilities for operations with binary data. |
| Pictures. | Support of vector images in SVG format is implemented. The PictureFormat.SVG system enumeration value is implemented. The picture editor in Designer does not support editing pictures that have SVG format. The specifics of SVG format support are described in the documentation. | This feature was not provided. | Extended list of supported picture formats. You have the option to use scalable pictures that can be displayed in areas of any size. |
| Administration tools. | For the /regserver client application command-line option (registration of COM objects), the following optional parameters are implemented:
The behavior of the /regserver option without parameters is not changed. | When a client application was started with the /regserver command-line option (registration of COM objects), it attempted to perform the registration for all users. If the current user did not have the rights for this, they were prompted to confirm the registration for the current user. | Simpler usage of the /regserver command-line option in 1C:Enterprise batch startup mode. |
| XML and XDTO support. | Support of Canonical XML 1.1 specification is implemented. The ConversionToCanonicalXML object is implemented. For the XMLCanonicalizationType system enumeration, the following values are implemented: XMLCanonicalization1_1 and XMLCanonicalization1_1WithComments. The XMLCanonicalizingWriter and DOMCanonicalization objects are deprecated. These objects do not support Canonical XML 1.1 specification. | Only Canonical XML 1.0 specification was supported. | Extended capabilities for integration with third-party systems. |
| DBMS operations. Administration tools. | The option to attempt the restoration of database structure from Designer batch mode command line is implemented. The /IBRestoreIntegrity Designer command-line option is implemented. Running Designer with the /IBRestoreIntegrity parameter is recommended if a previous database configuration update (performed either interactively or in batch mode) have not been completed successfully because of unexpected Designer shutdown or power outage. | This feature was not provided. | Improved infobase fault tolerance in scenarios that include database configuration update. |
| Predefined data. Event log. | Recording events related to predefined data restructuring to the event log is implemented. This includes the following events:
| This feature was not provided. | Simplified diagnostics of predefined data issues. |
| Spreadsheet documents. | The export of spreadsheet documents to Microsoft Office OpenXML (Microsoft Word 2007- 2010) format includes the export of pictures stored in spreadsheet document cells. This change is not implemented in 8.3.8 compatibility mode. | The export of spreadsheet documents to Microsoft Office OpenXML (Microsoft Word 2007- 2010) format did not include the export of pictures stored in spreadsheet document cells. | Spreadsheet documents exported to Microsoft Word better match the original spreadsheet documents. |
| Internet-enabled functionality. | The following algorithms can be used together with TLS protocol: GOST R 34.10-2001, GOST R 34.10-94, GOST R 34.11-94, and GOST 28147-89. GOST R 34.10-2012 and GOST R 34.11-2012 algorithms are not supported. | This feature was not provided. | Internet services that use the listed GOST algorithms together with TLS protocol are now supported. |
| OData interface. | For the standard OData interface, the option to get the following data is implemented:
| These features were not provided. | Extended capabilities of the standard OData interface. |
| OData interface. | For queries to the standard OData interface, support of the $expand operator is implemented. This gives you the option to include referenced entities in the response body. | This feature was not provided. | The option to get values of referenced entities together with the main query result is implemented, which eliminates the need to use a separate query for each referenced entity. |
| Dynamic lists. | The following changes are made in the dynamic list query builder:
This change is not implemented in 8.3.8 compatibility mode. | The dynamic list query builder did not provide the option to edit batch queries. The option to specify the number of selected records was available but this number was never used. | The option to edit query batches using the dynamic list query builder is implemented. Better error diagnostics for dynamic list queries. |
| Configuration extensions. | The option to change access rights (including data access restrictions) in adopted roles is implemented. The option to add roles to configuration extensions is implemented, this requires the use of 1C:Enterprise script. In Designer, the only operation available for such roles is deletion. The option to apply data access restirictions added in a configuration extension to the resulting configuration is implemented through the use of security profiles (the access rights extension property). For the ISecurityProfile object, the RightExtension and RightExtensionDefinitionRoles properties are implemented (for the technology of programmatic cluster administration based on COM objects). For the ISecurityProfile object, the RightExtension and RightExtensionDefinitionRoles properties are implemented (for the Java administration server interface). For the server cluster command-line utility (rac), the right-extension and right-extension-definition-roles parameters of the profile command are implemented. | In configuration extensions, only the option to set access rights for native extension objects in adopted roles was available. The option to change rights in adopted roles was not available. | Significant improvements for access right management in configuration extensions. |
| Configuration extensions. Development tools. | The following options to check the applicability of a configuration extension without running an applied solution with this extension are implemented:
When a client application is started, extension compatibility issues are no longer displayed in the message window. Instead, they are added to the information for technical support (which is available from the About 1C:Enterprise window). If any compatibility issues are encountered, a warning dialog box is also displayed, with a link to the full list of issues. For the ConfigurationExtensions object, the CheckCanApplyAll() and GetSessionApplicationIssuesInformation() methods are implemented. For the ConfigurationExtension object, the CheckCanApply() method is implemented. For Designer batch mode, the /CheckCanApplyConfigurationExtensions command-line option is implemented. For the Configuration extension management standard function, the Check applicability when adding and loading extensions check box is implemented. | These features were not provided. When an extension was attached, the diagnostics messages were displayed in the message window. | Improved diagnostics for configuration extension attachment issues. The option to automate the diagnostics by running them in the batch mode is implemented. |
| Event log. | When the event log is exported to an XML file, the state of predefined data update is exported as the value of the Data field. The PredefinedDataUpdate system enumeration is now available in the thin and web clients. | This feature was not provided. | The event log export to an XML file is adjusted to reflect the new events. |
| Localization. | The French localization of the client applications is available. | This feature was not provided. | 1C:Enterprise is available to French-speaking users. |
| Localization. | The Hungarian localization of the client applications is available. | This feature was not provided. | The Hungarian platform interface is available. 1C:Enterprise is available to Hungarian-speaking users. |
| Configuration extensions. Development tools. | The ConfigurationExtensionsManager.ExecuteBackgroundJobWithoutExtensions() method is implemented. It runs a background job without extensions (configuration extensions available in the database are not applied in the background job session). For all metadata objects, the ChangedByConfigurationExtensions() method is implemented. It defines whether a configuration object is available in the current session. | This feature was not provided. | Simplified 1C:Enterprise script-based operations with configuration extensions. |
| DBMS operations. System requirements. | Microsoft SQL Server 2016 DBMS is now supported (including its Linux version). | Microsoft SQL Server 2016 DBMS was not supported. | Microsoft SQL Server 2016 DBMS is now supported. |
| Client application. System requirements. | A 64-bit client application for Windows is implemented. It includes the thin client (also available as a standalone distribution kit), the thick client, and Designer. The current client application status is beta. When you start a client application, the 32-bit version has priority because most of the add-ins are not yet available for the 64-bit version of 1C:Enteprise platform. Automatic client application updates also install 32-bit versions (provided that the 32-bit versions are available in the distribution kit directories). The 64-bit client installer is similar to the 32-bit client installer. We recommend that you do not install both 64-bit 1C:Enterprise server and applications from the full 64-bit 1C:Enterprise distribution kit on a single computer. | Only 32-bit versions of Windows client applications (including Designer) were available. 1C:Enterprise server was the only 1C:Enterprise component that had a 64-bit version. | Support of 64-bit Windows versions is implemented. Issues caused by insufficient memory for operations with large configurations (such as comparing and merging configurations) are eliminated. |
| Accounting registers. Database operations. | Before you start infobase verification and repair in the interactive mode, 1C:Enterprise displays a recommendation to create an infobase backup. Infobase restructuring and infobase verification and repair now include a check for the following: the table of accounting register extra dimension values contains records that do not have matching records in the main accounting register table (lost extra dimensions). During the repair, lost extra dimensions are deleted from the table of accounting register extra dimension values if the following conditions are met:
During the restructuring, the check is performed if any of the following entities change:
If lost extra dimensions are found during the restructuring, the restructuring is stopped and 1C:Enterprise displays a recommendation to perform infobase verification and repair. The check for lost extra dimensions during the infobase verification and repair is implemented. If extra dimensions are lost, it is recommended that you restore the infobase from a backup. The check is performed if the following conditions are met:
| The diagnostics of extra dimension inconsistencies was insufficient. | Diagnostics and repair of accounting register logical integrity issues that can result in data losses is implemented. |
| Administration tools. | The rules for generation of application and shortcut names displayed in the Windows Start menu are modified. The new name template is Application name (full version number). In Windows version 8 or later, the 1C:Enterprise 8 folder contains all installed applications (and shortcuts) with their version numbers. In Windows version 7 or earlier, the 1C:Enterprise 8 folder contains folders for each version number. Each of these folders contains all installed applications (and shortcuts) for a specific version, with their names generated according to the abovementioned rule. | The names of installed applications (and shortcuts) did not include the full system version number. | Simplified navigation in the Start menu on Windows version 8 and later. Application names now contain full version numbers. |
| Accounting registers. Dumping configurations to files/Restoring configurations from files. | The option to create an accounting register record that only affects the opening balance of a single period and does not affect the closing balance of the previous period is implemented. The implementation is based on the new "period adjustment" concept. A period adjustment is a number that represents the number of time intervals within a single second. The maximum number of intervals is 1000. If a record belongs to any period adjustment interval, the record does not affect the closing balance of a period but affects the opening balance of the next period and does not affect the turnovers of both periods. A register record that belongs to a period adjustment interval only affects turnovers if the turnover period includes the entire point in time of that register record. Now the point in time can inlcude not only the date, time, and recorder, but also a period adjustment. For the accounting register configuration object, the Period adjustment length property is implemented. If this property is set to 0, the register does not use period adjustments. The PeriodAdjustment property is implemented for AccountingRegisterRecord and AccountingRegisterSelection objects. This property is also available in the main accounting register table, the extra dimensions table, and the virtual table of register records with extra dimensions. The PeriodAdjustment value is implemented for the Periodicity parameter of the following virtual tables of accounting registers: Turnovers, DrCrTurnovers, and BalanceAndTurnovers. The PointInTimeWithPeriodAdjustment object is implemented. The XML dump format version is changed. If a configuration contains at least one accounting register with period adjustment enabled (the value of the Period adjustment length property is not 0), this makes the infobase incompatible with the earlier 1C:Enterprise versions, including earlier builds of 1C:Enterprise 8.3.9. When you attempt to open such an infobase with 1C:Enterprise version 8.3.9.2015 or earlier, 1C:Enterprise displays the message Configuration structure is incompatible with the current program version and shuts down. To restore the compatibility, you have to delete all of the accounting registers with period adjustment, or set their Period adjustment length to 0. | This feature was not provided. The option to create an accounting register record that only affected the opening balance of a single period and did not affect the closing balance of the previous period was not available. | You can implement certain operations related to opening balance corrections at period boundaries. |
| DBMS operations. System requirements. | Support of Oracle Database version 11.2.0.4 (Windows) is implemented. | This Oracle Database version was not supported. | Extended list of supported Oracle Database versions. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. | All of the common report forms use the following help topic priorities:
This change is not implemented in 8.3.8 compatibility mode. | Common report froms used the following help topic priorities:
| Help topics are displayed in more logical order. |
| Interface. Client application. | For thin client running on Windows operating system, touch screen support is implemented. Support of scrolling with 2-finger gestures in all directions is implemented for all controls that have scroll bars. The effect of 1-finger gestures depends on control type:
The tap detection area is expanded for the following controls:
For graphical schemas, support of scaling using the scaling gesture is implemented. For tapping form buttons and command bar buttons, a visual effect is implemented. | The touch screen support was limited. | Improved 1C:Enterprise usability for touch monitors. |
| Spreadsheet documents. | In spreadsheet documents, if a search string can be converted to a number, 1C:Enterprise determines the number of digits in that number. Then it searches exactly for the specified number, without further simplifications or conversions. The search does not ignore strings with leading zeros. This change is not implemented in 8.3.8 compatibility mode. | In spreadsheet documents, for searches by number, 1C:Enterprise did not determine the number of digits in that number. Strings with leading zeros were not converted to numbers. | Better algorithm for searching spreadsheet documents for numeric values. |
| Web client. | File system extension and cryptography extension are compatible with Mozilla Firefox version 51 and later. The extensions are automatically updated first time they are accessed (after the platform update). | File system extension and cryptography extension were not compatible with Mozilla Firefox version 51 and later. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Development tools. | The performance of the following Designer operations is improved:
| The performance of module and configuration checks was insufficient. | Improved usability for developers of large applied solutions. |
| 1C:Enterprise script. | The performance of 1C:Enterprise script execution is slightly improved in the thin and thick client applications. | The performance of 1C:Enterprise script execution in client applications was insufficient. | Improved performance of 1C:Enterprise script execution in the thin and thick client applications. |
| Common objects. | The performance of updating value table column cells in columns that are not a part of any value table index is improved. | Redundant rebuilding of value table indexes was performed in the event of updating a cell in a column that was not a part of any value table index. | Improved performance for bulk value changes in columns that are not part of any value table index. |
| Data exchange. Server clusters. | The following operations that are performed during the creation of an initial infobase image in client/server mode are optimized: reading accumulation register and information register record sets, and reading calculation register record sets that do not feature action period. The time required to create an initial image of a client/server infobase is significantly reduced. | The performance of creation of an initial image in a client/server infobase was insufficient. | Improved performance of infobase preparation for new distributed infobase nodes. |
| Command interface. Development tools. | Improved performance of opening the configuration command interface editor form. | The performance of opening the configuration command interface editor form was insufficient. | Better usability of editing the configuration command inerface. |
| DBMS operations. Server clusters. | The algorithm of 1C:Enteprise server cluster operations with PostgreSQL DBMS is modified. This reduces PostgreSQL memory usage. If a 1C:Enterprise server cluster connection to PostgreSQL DBMS is idle for 30 minutes, it is released. | The algorithm of 1C:Enteprise server cluster operations with PostgreSQL DBMS caused increased PostgreSQL memory usage. 1C:Enterprise server cluster did not release idle connections to PostgreSQL DBMS.
| Reduced PostgreSQL memory usage for operations with 1C:Enterprise server cluster. |
| Development tools. | Infobase configuration update is optimized. Configuration comparison in scenarios where objects are mapped by their names is optimized. | The performance of infobase configuration update was insufficient. | Improved performance of configuration updates. |
| DBMS operations. | Temporary table operations are optimized in scenarios that use PostgreSQL DBMS. | The performance of temporary table operations in scenarios that used PostgreSQL DBMS was insufficient. | Improved performance in multiuser mode in scenarios that use PostgreSQL. |
| Web services and HTTP services. | Sending large files (tens and hundreds of megabytes) over HTTP services is optimized. | The performance of sending large files (tens and hundreds of megabytes) over HTTP services was insufficient. | Improved performance of sending large files over HTTP services. |
| DBMS operations. | Optimized temporary table operations in scenarios that use Microsoft SQL Server and include high load on 1C:Enterprise and active usage of temporary tables. Pauses during the closing of DBMS connections are eliminated. | The performance of temporary table operations in scenarios that used Microsoft SQL Server and included high load on 1C:Enterprise and active usage of temporary tables was insufficient. | Improved performance in multiuser mode in scenarios that use Microsoft SQL Server.
|
| DBMS operations. | In the file mode, queries are optimized for scenarios where an applied solution has separators but actually contains a single data area. To apply this optimization to an existing infobase, perform infobase verification and repair with the Reindex infobase tables check box selected. Once the restructuring is completed, the optimization is applied to all restructured objects. | In the file mode, in scenarios where an applied solution had separators but actually contained a single data area, the performance of queries was insufficient. | Improved file infobase performance in scenarios where an applied solution has separators but actually contains a single data area. |
| Development tools. Command interface. | Reduced time of displaying changes in configuration objects that affect the configuration command interface. Such changes cause the immediate update of the active form editor, while other form editors are updated when they are activated. | Changes in configuration objects that affected the configuration command interface caused the update of all open form editors. | Improved Designer performance during the update of properties of configuration objects that affect the command interface. |
| Formatted documents. | The performance of formatted documents is improved. | The performance of formatted documents was insufficient. | Improved performance of operations with large texts. |
| Managed locks. | Absorption of managed locks is implemented (when two managed locks are applied at the same time, only one will take effect). A lock that does not have all lock areas specified absorbs a lock that has more lock areas specified, provided that the values in their common areas match. If lock escalation causes a conflict with other locks, the escalation is not performed and an attempt to set the requested lock is made instead. This can lead to a total of more than 100 000 locks in a single area. In scenarios where a single transaction uses a large number of managed locks with slight differences (for example, a single dimension varies), it is recommended that you set a single managed lock where the value of that dimension is not set. | Lock absorption was not performed. If lock escalation caused a conflict with other locks, the transaction that attempted to escalate the lock was canceled. | Reduced number of locks and reduced amount of memory used by the cluster manager. Improved system reliability in scenarios with large numbers of simultaneous locks. |
| DBMS operations. Calculation registers. | When deleting records belonging to the actual action period, recording of register sets of calculation registers that support actual action period is performed within several queries, which reduces the chance of escalating the lock to the table level. This does not increase the record set execution time. | When deleting records belonging to the actual action period, recording of register sets of calculation registers that supported actual action period was performed within a single query, which could cause lock escalation to the table level. | Reduced chance of table lock, which gives more options for performing parallel operations. |
| Calculation registers. | The index of the actual action period table of a calculation register is complemented by the start date and end date fields, and the index is now clustered. This reduces the chance of lock escalation to the table level when writing record sets of calculation registers that support action period. For the chart of calculation types table that stores serial numbers of calculation type displacements, a nonunique index by displacement number is implemented. As a result, simultaneous editing of a single chart of calculation types in different data areas of a separated infobase never requires waiting for lock releases. To apply this optimization to existing infobases, perform the infobase verification and repair operation with the Restructure infobase tables option selected.
| The index of the actual action period table of a calculation register did not include the start date and end date fields, and the index was not clustered. For the chart of calculation types table that stored serial numbers of calculation type displacements, a nonunique index by displacement number was not available. | Improved calculation register performance in large and separated databases. In large databases and especially separated databases, reduced number of table-level locks for the following tables: actual action period table of a calculation register and table that stores serial numbers of calculation type displacements. |
| Managed forms. Development tools. | The first opening of managed form editor in Designer is faster. | The first opening of managed form editor in Designer took significant time. | Reduced waiting time in managed form development. |
| Information registers. | Faster writing of information register record sets that have slice first or slice last options enabled. Faster execution of SliceFirst() and SliceLast() information register manager methods. | The performance of writing information register record sets that had slice first or slice last options enabled and the performance of SliceFirst() and SliceLast() information register manager methods was insufficient. | Improved performance of information registers with slice first or slice last options enabled. |
| Interface. Managed forms. Functional options. | The performance of RefreshInterface(), SetInterfaceFunctionalOptionParameters(), and SetFormFunctionalOptionParameters() methods is improved. Delays introduced by these methods in applications with multiple simultaneous user connections are eliminated. | The performance of RefreshInterface(), SetInterfaceFunctionalOptionParameters(), and SetFormFunctionalOptionParameters() methods was insufficient. The performance was reduced in applications that called these methods in scenarios with multiple simultaneous user connections. | Streamlined operations in applications that use functional options. |
| Managed forms. Mobile applications. | In the mobile platform, the performance of operations with large spreadsheet documents is improved. | In the mobile platform, the performance of operations with large spreadsheet documents was insufficient. | Improved performance of operations with large spreadsheet documents on mobile devices. |
| DBMS operations. | The performance degradation of Microsoft SQL Server 2014 caused by interaction between 1C:Enterprise server and Microsoft SQL Server 2014 is eliminated. 1C:Enterprise server now forces setting TRACE FLAG 4199 for each Microsoft SQL Server 2014 connection. To be able to set the flag, the account that the 1C:Enterprise server uses to connect to the DMBS must have administrator rights. If TRACE FLAG 4199 is set for the entire database, 1C:Enterprise server does not set it for each connection. | In some scenarions interaction between 1C:Enterprise server and Microsoft SQL Server 2014 reduced Microsoft SQL Server 2014 performance. 1C:Enteprise server did not force setting TRACE FLAG 4199 and did not check whether this flag was set for the entire database. | In some scenarions the performance of operations involving Microsoft SQL Server 2014 is improved. |
| DBMS operations. | For PostgreSQL, reduced the overhead expenses for processing temporary tables. | For PostgreSQL, processing temporary tables took a lot of time. | For PostgreSQL, improved the performance of transactions that actively use temporary tables. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Internet-enabled functionality. | The option to choose FTPES for communication with FTP servers is implemented. For the constructor of the FTPConnection object, the SecureConnectionLevel property is implemented. This property defines the secure connection requirements to the FTP server. If the parameters of the FTPConnection constructor do not have the required types, an exception is thrown. This change is not implemented in 8.3.8 compatibility mode. | All FTP server operations were performed over FTPS. If the parameters of the FTPConnection constructor did not have the required types, an attempt to convert them to the required types was performed. | Extended secure connection management capabilities for FTP server operations. |
| Managed forms. | Clicking a managed form table cell that displays a picture with a hyperlink (the CellHyperlink property is set to True) calls the Selection event of the form table. This change is not implemented in 8.3.8 compatibility mode. | Clicking a managed form table cell that displayed a picture with a hyperlink (the CellHyperlink property was set to True) did not call the Selection event of the form table. | Eliminated unexpected system behavior. Unified system behavior for different object types that can be displayed in a form table. |
| Print tools. | The option to use duplex printing settings of the printer is implemented. The system enumeration value DuplexPrintingType.UsePrinterSettings is implemented. The DuplexPrinting property of spreadsheet documents, graphical schemas, representable document batches, and text documents has the following default value:
Printing spreadsheet documents and representable document batches from the web client to a PDF document and saving a spreadsheet document to a PDF document transfers the DuplexPrinting and PagePlacementAlternation property values to the corresponding PDF document properties. If the PDF viewer software supports these properties, they are applied when the document is printed. If the PDF viewer software does not support these properties, use the print software settings or printer settings for duplex printing. | Duplex printing settings of the printer were ignored during the printing of spreadsheet documents, graphical schemas, representable document batches, and text documents. | Improved document printing options. |
| Data composition system. | When the data composition schema wizard is opened, data set fields with duplicate names are deleted, leaving only the first one. | When the data composition schema wizard was opened, duplicate data set fields were not deleted. | Eliminated unexpected system behavior. |
| Technological log. | Debugger exceptions that are thrown during the startup of the debug server (dbgs) are now saved to the technological log. The <EXCP> event is used for that logging. | Debugger exceptions that are thrown during the startup of the debug server (dbgs) were not logged. | Better error diagnostics for the startup of the debug server (dbgs). |
| Predefined data. Development tools. | If the result of merging configurations would include predefined data items with duplicate names, a numeric suffix is added to the item taken from the source with lesser priority. | The result of merging configurations could include predefined data items with duplicate names. | Eliminated unexpected system behavior. |
| 1C:Enterprise script. | For the StrTemplate() method, the syntax option with a substitution token %(N) is implemented. You can specify a substitution number in parentheses after the percent. With this syntax you can specify a number right after the substitution token in a template string. | Eliminated unexpected system behavior. | You can create template strings where the substitution token is followed by a numeric character. |
| Development tools. | During the configuration check and refactoring, the search for calls of deprecated synchronous methods does not check the modules that cannot be executed at the client application side. In other modules the search ignores client script parts marked with preprocessor insrtructions and compilation directives. | During the configuration check and refactoring, the search for calls of deprecated synchronous methods ignored the execution context of modules and methods. | Reduced number of false warnings while searching for calls of deprecated synchronous methods during the configuration check and refactoring. |
| Web client, web service, and HTTP service publishing tools. | If an attempt of publishing to a web server using an account that does not have administrative rights is made:
| If an attempt of publishing to a web server using an account that does not have administrative rights was made, no diagnostics was performed. | Better diagnostics for publishing to the web sever. |
| XML and XDTO support. | When an XDTO package is deleted, 1C:Enterprise checks whether the package is used in web services. If web services that use the package are found, a warning with a web service list is displayed. | When an XDTO package was deleted, 1C:Enterprise did not check whether the package was used in web services, | Eliminated situations where a web service stopped working due to deletion of an XDTO package. |
| Managed forms. | The option to set the focus to command bars that do not contain form item commands of contain commands from multiple sources using Tab or Shift+Tab is implemented. In the calendar used to enter a date in a text box, selection of the current date by clicking the Today hyperlink is implemented. In the thin and thick clients, in the calendar used to enter a date in a text box, selecting a date that does not belong to the current month adds this date to the text box. | The option to set the focus to command bars that did not contain form item commands of contained commands from multiple sources using Tab or Shift+Tab was not available. In the calendar used to enter a date in a text box, clicking the Today hyperlink set the focus to the current day of the month in the month currently selected in the calendar. In the thin and thick clients, selecting a date that did not belong to the current month activated the selected month in the calendar field. In the web client, this added the selected date to the text box. | Eliminated unexpected user interface behavior in some scenarios. Unified system behavior in different client applications. |
| Configuration repositories. | When you store an object to a configuration repository, the repository server checks the integrity of object data. In the event of integrity violation an exception is generated and the object is not stored. | The configuration repository server did not check the integrity of stored object data. | Reduced chance of storing corrupted configuration object data to a repository. |
| Database configuration update. | During a dynamic update, deletion of configuration objects that do not prevent the update and are absent from the new configuration is handled correctly. These objects are only deleted during the exclusive update. This change is not implemented in 8.3.8 compatibility mode. | Deletion of configuration objects that did not prevent the update and were absent from the new configuration was performed immediately, during a dynamic update. | Reduced number of issues that might arise during a dynamic update if some objects were deleted from the new configuration. |
| Web services and HTTP services. Internet-enabled functionality. | This change is rolled back. The URI string encoding (either with the EncodeString() function or with internal platform algorithms) replaces the percent sign (%) with %25. This change is not implemented in 8.3.8 compatibility mode. | The URI string encoding (either with the EncodeString() function or with internal platform algorithms) did not replace the percent sign (%) with %25. It was left "as is." | RFC 3986 recommendations for URI string encoding are implemented. |
| Localization. | In the number-to-words conversion algorithm for Azerbaijani language, a typo is corrected. This affects the numbers beginning with "two" and "twenty." | The number-to-words conversion algorithm for Azerbaijani language had a typo. This affected the numbers beginning with "two" and "twenty." | Eliminated unexpected system behavior. |
| Development tools. | In the debugger, when a collection (for example, a value table) is being viewed in a new window, its columns are no longer sorted in alphabetical order. | In the debugger, when a collection (for example, a value table) was being viewed in a new window, its columns were sorted in alphabetical order. This behavior occurred in 1C:Enterprise versions 8.3.7 and 8.3.8. | Eliminated unexpected system behavior. |
| Common attributes / Data separation. Configuration extensions. | The data deleted by EraseInfoBaseData() method now includes configuration extensions for the entire infobase or for a specific area, depending on the call parameters. | The EraseInfoBaseData() method did not delete configuration extensions. | The EraseInfoBaseData() method clears more data. |
| Dynamic lists. Server clusters. | In a dynamic list search box, if you enter a value that can be interpreted as a date with year specified as a 1-digit or 2-digit number, the year is converted to this century year. This prevents the error that occurs when you use Microsoft SQL Server with a zero date offset. | In a dynamic list search box, if you entered a value that could be interpreted as a date with year specified as a 1-digit or 2-digit number, the year was not converted to this century year. In 1C:Enterprise that used Microsoft SQL Server with a zero date offset, this search scenario returned an error. | The dynamic list error that occurred if a date was entered in a search box in 1C:Enterprise that used Microsoft SQL Server with a zero date offset is eliminated. |
| Spreadsheet documents. | When a spreadsheet document is exported to Microsoft Excel 97 or later format, if it contains cells with multiline text that is aligned centrally and does not fit a cell, the cell is merged. It is horizontal merging that spreads equally to both sides of the cell so that the entire text fits the new merged cell. The columns overlapped by the left and right borders of the merged cell are split into two columns. The resulting document in Microsoft Excel format better matches the original document. This change is not implemented in 8.3.8 compatibility mode. | When a spreadsheet document was exported to Microsoft Excel 97 or later format, if it contained cells with multiline text that were aligned centrally and did not fit the cell, such cells were not merged. | When a spreadsheet document is exported to Microsoft Excel format, the resulting document better matches the original document. |
| Development tools. | If programmatic access to Microsoft Internet Explorer browser clipboard is disabled by the Allow Programmatic clipboard access security option, an attempt to use the Copy command of the Syntax Assistant context menu results in a notification that the clipboard is not available, which includes a workaround recommendation (use a keyboard shortcut). | If the Allow Programmatic clipboard access security option in Microsoft Internet Explorer was disabled, the Copy command of the Syntax Assistant context menu did not work. | Better diagnostics of unexpected system behavior. |
| Managed forms. | For groups with titles that display data, the support of Format property in both interface modes (Taxi and Version 8.2) is implemented. This change is not implemented in 8.3.8 compatibility mode. | For groups with titles that display data, the Format property was not supported in some interface modes. This property had some implementation differences between the thin and web clients. | Uniform behavior of the thin and web clients. Eliminated unexpected system behavior. |
| Development tools. | The option to update configurations that include constant forms using update (.cfu) files is restored. The option to update configurations using update (.cfu) files is implemented for scenarios where only the Use always flag in constant forms was changed. | In some scenarios, if the Use always flag in a constant form was changed in a new configuration, this caused configuration update issues. | Eliminated the issues that appeared during the update of configurations that included constant forms with update (.cfu) files. |
| Development tools. |
If the size of the file that stores new and changed objects, which is created during the generation of a .cfu update file, exceeds 2 GB, the update file is generated in the new format. If you are creating the update file manually, you get a notification about the new format in a dialog box. If you are creating the update file in batch mode, the notificaton is added to the service message file (/out comand-line option). Update files that have new format can only be used in 1C:Enterprise versions 8.3.9.2033 and later. If you attempt to use an update file in an earlier 1C:Enterprise version, you get a message about incorrect data storage format. You can use 1C:Enterprise versions 8.3.9.2033 and later to apply any updates, regardless of their file format. | If the size of the file that stored new and changed objects, which was created during the generation of a .cfu update file, exceeded 2 GB, the update file could not be generated. | 1C:Enteprise supports very large update files (.cfu). |
| Print tools. | The RepresentableDocumentBatch.Print() method splits batches into multiple jobs (in all application types except for the web client). It uses the document batch properties, such as the printer, page orientation, or duplex printing, to generate the jobs (and split document batches). | The RepresentableDocumentBatch.Print() method printed the entire document batch as a single job (in all application types except for the web client). This might cause issues when the documents were to be printed on different printers or with different print settings because jobs always apply the same settings to all its documents. | Eliminated document batch printing issues caused by differences of document print settings (such as the printer, page orientation, or duplex printing). |
| Operating system. | 1C:Enterprise behavior changed in scenarios that involve switching the computer to sleep mode. 1C:Enterprise prevents switching to the sleep mode if:
| 1C:Enterprise prevented switching to sleep mode if:
| Power saving schemes applied when 1C:Enterprise runs are changed. |
| Infobase operations. | Dumping an infobase to a .dt file is not interrupted if any issues related to the internal infobase structure are encountered. | Dumping an infobase to a .dt file was interrupted if any issues related to the internal infobase structure were encountered. | Minor infobase data structure issues, which do not impact 1C:Enterprise functionality, no longer block dumping infobases to files.
|
| JSON support. | Improved reliability of JSON operations. | JSON operations might cause unexpected shutdown. | Eliminated unexpected system behavior. |
| Server clusters. | When the Secure connection cluster property value is changed, this takes effect after restarting the cluster processes. It is recommended that you restart the cluster after changing the Secure connection property value. | An attempt to change the Secure connection cluster property value generated an error and the value was not changed. | Eliminated unexpected system behavior. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| 1C:Enterprise script. | During the compilation of 1C:Enteprise script texts, unknown compilation directives cause errors. This change is not implemented in 8.3.8 compatibility mode. | Unknown compilation directives did not cause compilation errors. | Better control of source texts. Reduced number of issues that are hard to detect (typos in compilation directives). |
| Queries. | When a transaction is rolled back from the temporary table manager, all temporary tables created within the transaction are deleted. In file databases, temporary tables created within a query transaction are not available in that query after rolling the transaction back (this behavior is now uniform with scenarios that use other DMBS). This change is not implemented in 8.3.8 compatibility mode. | When a transaction was rolled back from the temporary table manager, temporary tables created within the transaction were not deleted. In file databases, the option to use temporary tables created in a transaction that was rolled back was available. In scenarios that used other DBMS, this option was not available. | Uniform 1C:Enterprise behavior in scenarios that use different DBMS. |
| Navigation links. | An attempt to execute the GetURL() method for a value that cannot provide an URL generates an exception. This change is not implemented in 8.3.8 compatibility mode. | An attempt to execute the GetURL() method for a value that cannot provide an URL had the following result:
| Unified system behavior in different client applications. |
| Window-based interface. Error handling. | If the Timeout parameter of the DoQueryBox(), ShowQueryBox(), DoMessageBox(), or ShowMessageBox() method has a negative value, an exception is generated. This change is not implemented in 8.3.8 compatibility mode. | If the Timeout parameter of the DoQueryBox(), ShowQueryBox(), DoMessageBox(), or ShowMessageBox() method had a negative value:
| Eliminated unexpected system behavior. Unified system behavior in different client applications. |
| Managed forms. | The option to monitor the usage of context server calls (including implicit calls) in form event handlers where such calls are prohibited at run time is implemented.
If you enable this option, diagnostics messages are added to the message window. To enable or disable this option, use the /EnableCheckServerCalls command-line option of the client application. The option to run the client application from Designer is implemented, with this command-line option available. | A tool for monitoring the usage of context server calls in form event handlers where such calls were prohibited was not available. | Improved diagnostics of incorrect usage of 1C:Enterprise programming interfaces. |
| DBMS operations. | If a parameter of the In operation of the query language is a value table with a column of String type longer that 1024 characters or BinaryData type longer that 2048 bytes, an exception is generated during the query execution. | If a parameter of the In operation of the query language was a value table with a column of String type longer that 1024 characters or BinaryData type longer that 2048 bytes, the query might or might not be executed, depending on the DBMS. | More predictable query results on different DBMS. Improved system reliability. |
| Client application. Managed forms. | At the thick client startup, the Synchronous call usage mode for platform extensions and add-ins configuration property is ignored and all synchronous methods are executed without any warnings or exceptions. When the thick client is started from Designer, the /EnableCheckExtensionsAndAddInsSyncCalls option is not passed to the client. The behavior of the thin client and the web client in this scenario is not changed. The behaviour of configuration verification and refactoring is not changed: they display warnings for all synchronous methods calls and recommend conversion to asynchronous methods. | At the thick client startup, the Synchronous call usage mode for platform extensions and add-ins configuration property was not ignored. When the thick client was started from Designer, the /EnableCheckExtensionsAndAddInsSyncCalls option was passed to the client. | Removed checks for synchronous method calls in applied solutions intended to run in thick client only. |
| Queries. | During the query generation, the query builder (in Designer and in the thick client) and the QuerySchema object (in the thick client) generate aliases for all fields of the first query (in a set of unions) for each query in a batch. This change is not implemented in 8.Х.Х repository compatibility mode. | During the query generation, the query builder (in Designer and in the thick client) and the QuerySchema object (in the thick client) generated aliases only for expression fields and for fields used for ordering and totals calculation. | Unified behavior of query builder and the QuerySchema object in different client applications. |
| Managed forms. | The following object keys are used for storing desktop separator positions:
Once you turn the compatibility mode off, the keys are renamed. If you set the compatibility mode to Version 8.3.8, the initial names are applied again. When you export a configuration to a set of XML files, the file that stores the HomePageWorkingArea property (former StartPageWorkingArea property) has a different name. This change is not implemented in 8.3.8 compatibility mode. | The following object keys were used for storing desktop separator positions:
| The object key names better reflect their purpose. |
| Spreadsheet documents. | If auto grouping or rows is enabled, new groupings inherit the name and visibility from the area that is displayed in the grouping header area. This change is not implemented in 8.3.8 compatibility mode. | If auto grouping or rows was enabled, new groupings inherited the name and visibility from the area that was displayed inside the grouping. | Eliminated unexpected system behavior. |
| Common objects. | If the DBMSNames parameter of the GetDBStorageStructureInfo() method has a value of non-Boolean type, an exception is generated. This change is not implemented in 8.3.7 compatibility mode. | A value of any type could be passed to the DBMSNames parameter of the GetDBStorageStructureInfo() method. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | In spreadsheet documents, when a text is displayed with nonhorizontal orientation, it has the same font size as regular text. This change is not implemented in 8.3.8 compatibility mode. | In spreadsheet documents, when a text was displayed with nonhorizontal orientation, it had bigger font size than regular text. | Eliminated unexpected system behavior. |
| DBMS operations. | Changing the data lock timeout in the Infobase options dialog box in Designer requires administrative rights in a nonseparated session and sets exclusive infobase access mode. If an exclusive lock cannot be set, a message with a list of sessions preventing the lock is displayed, it includes the retry option. The SetLockWaitTime() method requires administrative rights in a nonseparated session, sets an exclusive database lock (if it was not set earlier), and throws an exception if the exclusive lock cannot be set. The change of the data lock timeout is applied immediately to all DBMS except IBM DB2. Changing the lock timeout in IDB DB2 requires a database restart. | Changing the data lock timeout in the Infobase options dialog box or using the SetLockWaitTime() 1C:Enterprise script method was allowed in infobases running in shared mode. | Eliminated the issues related to database operations that appeared in some scenarios. |
| XML and XDTO support. | For the XMLWriter.OpenFile() method, the AddBOM parameter is implemented. It shows whether the resulting file includes a BOM. | This feature was not provided. | Integration with systems that do not expect BOMs in their input XML files is now available. |
| Administration tools. System requirements. | In the file infobase, the check for client application versions is implemented. Access to the infobase is only allowed if the versions of all client applications match. If the versions do not match, an error is displayed. | An attempt to access an infobase using multiple versions from the following list generated an exception: 8.2.19 to 8.3.4, 8.3.6, and 8.3.7. In some cases simultaneous access to a single infobase with different platform versions was allowed, where one version was 8.2.18 or earlier and the other one was in range 8.3.1-8.3.3. | Increased reliability of file infobases. Simultaneous access to a single infobase using different 1C:Enterprise versions is not allowed. |
| ZIP archive operations. | The path separator of the ZipFileEntry object depends on the operating system. This change is not implemented in 8.3.8 compatibility mode. | The path separator of the ZipFileEntry object was always a slash mark (/) and did not depend on the operating system. | ZIP file operations use the same file path separators as other file operations. |
| Data composition system. | When data composition template composer generates parameter names, it does not assign parameter names that are already used in the data composition schema. This change is not implemented in 8.3.8 compatibility mode. | When data composition template composer generated parameter names, it could assign parameter names that were already used in the data composition schema. | Eliminated unexpected system behavior. |
| Administration tools. | When 1C:Enterprise establishes a secure connection (HTTPS) to the Licensing Center, it automatically selects the root certificate store of the operating system. If the Internet connection uses a proxy server that decrypts secure connection (HTTPS) traffic, the system administrator must add the certificates that sign the proxy server certificate to the trusted root certificate store of the operating system. | When 1C:Enterprise established a secure connection (HTTPS) to the Licensing Center, it searched the file cacert.pem for a secure connection certificate. | Reduced number of issues related to interaction with the Licensing Center. |
| Configuration extensions. | For the execution of some configuration object handlers and subscriptions, disabling the safe mode is implemented. Once a handler or subscription is executed, the safe mode and the security profile are restored. You can disable the safe mode manually using the SetSafeModeDisabled() and GetSafeModeDisabled() global context methods. These methods are not available in configuration extensions. The list of handlers where the safe mode is automaticly disabled is provided in the documentation. | The option to disable the safe mode using 1C:Enterprise script tools was not provided. | You have the option to access objects that have events that require privileged mode in their object modules from configuration extensions and external data processors executed in safe mode. |
| Internet-enabled functionality. | TLS 1.2 protocol is used to establish secure connection because it provides additional security. You can force the use of TLS 1.0 protocol when establishing thin client connection to a web server using the command-line option /HttpsForceTLS1_0. HTTPConnection, FTPConnection, and WSProxy objects automatically select TLS 1.2 protocol, regardless of the specified client certificate source. For the conf.cfg configuration file, the ForceTLS1_0 parameter is implemented. Simultaneous use of /HttpsForceTLS1_0 and /HttpsForceSSLv3 command-line options in the thin client is not supported. | TLS 1.0 protocol was used to establish secure connections. | Increased security of thin client Internet connections. |
| Internet-enabled functionality. | If an SMTP server cannot send an email message to one or several recipients, the InternetMail.Send() method returns a map where recipients are keys and SMTP server diagnostic messages are values. This change is not implemented in 8.3.8 compatibility mode. | If an SMTP server could not send an email message to one or several recipients, the InternetMail.Send() method generated an exception. | You can determine which recipients cannot be reached by email and view the reasons provided by the SMTP server. |
| Development tools. Configuration properties. Dumping configurations to files/Restoring configurations from files. | When a configuration is exported to files, the format of Compatibility mode configuration property in the resulting file is different. The new format eliminates possible loss of compatibility mode data during the import. | When a configuration with Compatibility mode property set to Do not use was exported to files, the property value was exported as Do not use. Then, if that configuration was imported using a later 1C:Enterprise version, the imported compatibility mode value was incorrect. | Eliminated the chance to lose compatibility mode data after exporting and importing a configuration. Eliminated unexpected system behavior. |
| Spreadsheet documents. | The FillPropertyValues() method applied to a spreadsheet document copies the Template property of the spreadsheet document. This change is not implemented in 8.3.8 compatibility mode. | The FillPropertyValues() method applied to a spreadsheet document did not copy the Template property of the spreadsheet document. | The behavior implemented earlier to streamline migration to the previous version is no longer supported. |
| Administration tools. Database operations. | In the file mode, the default format of new databases is 8.3.8. | In the file mode, the default format of new databases was 8.2.14. | The optimized file database format implemented in platform version 8.3.8 becomes the default one. |
| Internet-enabled functionality. | The Port property of FTPConnection object and the Port parameter of its constructor have the Number type. This change is not implemented in 8.3.8 compatibility mode. | The Port property of FTPConnection object and the Port property of its constructor had String type. The constructor parameter accepted any data that could be converted to Number type. | Eliminated unexpected system behavior. |
| Database operations. | After calling the GetDBStorageStructureInfo() method, tables that do not have presentations in the query language have empty strings for their names (TableName property) and their field names (FieldName property). This change is not implemented in 8.3.8 compatibility mode. | After calling the GetDBStorageStructureInfo() method, tables that did not have presentations in the query language had their table name (TableName property) and field name (FieldName property) values equal to virtual table presentations. | Eliminated unexpected system behavior. |
| HTML support. | Reading and writing XML documents containing <?xml does not generate an error message. This change is not implemented in 8.3.8 compatibility mode. | Reading and writing XML documents containing <?xml generated an error message. | Eliminated unexpected system behavior. |
| ZIP archive operations. | File names in ZIP archives are written in UTF8 encoding. For the ZipFileWriter object constructor and the Open() method of the ZipFileWriter object, parameters that define file name encoding in ZIP archives are implemented. These parameters override the FileNamesEncodingInZipFile parameter in the conf.cfg file. The default value of the FileNamesEncodingInZipFile parameter in the conf.cfg file is UTF8. This change is not implemented in 8.3.8 compatibility mode. | File names in ZIP archives were written in UTF8 encoding and the current operating system encoding. 1C:Enterprise script did not provide methods to specify encoding of file names in ZIP archives. The default value of the FileNamesEncodingInZipFile parameter in the conf.cfg file was OSEncodingWithUTF8. | 1C:Enterprise script provides methods to specify the encoding of file names in 1C:Enterprise-generated ZIP archives. |
| Dynamic lists. | Dynamic list fields included in conditional form appearance item filters are always passed to the client, regardless of the value of the Use always field property or the availability of a visible linked column. This change is not implemented in 8.3.7 compatibility mode. | Dynamic list fields included in conditional form appearance item filters were not automatically passed to the client. To ensure correct functioning of conditional appearance items, developers had to set the Use always property for such fields. | Better usability for 1C:Enterprise developers. |
| Dynamic lists. | The recommendation to avoid using conditional form appearance for customizing dynamic list appearance if the desired effect can be achieved by using conditional dynamic list appearance is added to the documentation. | The recommendation to avoid using conditional form appearance for customizing dynamic list appearance if the desired effect can be achieved by using conditional dynamic list appearance was not available in the documentation. | 1C:Enterprise documentation is improved. |
| Data composition system. | In the composition of a data composition system template, the following operations are performed using additional data sets that are automatically generated by a template composer:
This change is not implemented in 8.3.8 compatibility mode. | In the composition of a data composition system template, the following operations were performed within a query:
This might generate incorrect results or errors. | Eliminated unexpected system behavior. |
| Data composition system. | In data composition schema templates, when parameters that can have both English and Russian names are generated, their names are generated in the language of the current 1C:Enterprise script variant. This change is not implemented in 8.3.8 compatibility mode. | In data composition schema templates, when parameters that could have both English and Russian names were generated, their names were always generated in English. | You can use Russian names of data composition schema parameters, which match the parameter names that are automatically retrieved from virtual tables. |
| Managed forms. | 1C:Enterprise behavior in the following scenario is changed: a user types something in a text box and then clicks a decoration hyperlink without exiting the text box, which initiates a context server call. The new behavior consists of the following steps:
This change is not implemented in 8.3.8 compatibility mode.
| 1C:Enterprise behavior in the following scenario was different: a user types something in a text box and then clicks a decoration hyperlink without exiting the text box, which initiates a context server call. The previous behavior consisted of the following steps:
| Eliminated unexpected system behavior. Unified behavior of client applications. |
| Client application. Client application installation. Add-ins. | Since Windows versions 2008 R2 and later stop trusting SHA-1 certificates in January 2017, the following changes are implemented:
| On Windows, the file system extension and cryptography extension installers for Google Chrome and Mozilla Firefox were delivered as .msi files signed with SHA-1. | The platform executable files are verified on all supported operating systems of Windows family. |
| Automated testing. | The TestedFormButton.Click() method generates an error if the button specified in this method is not visible. This change is not implemented in 8.3.8 compatibility mode. | The TestedFormButton.Click() method did not generate an error if the button specified in this method was not visible. | Eliminated unexpected system behavior. The automated testing only performs the actions that are available to users in interactive mode. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| File operations. Multimedia support. | On the mobile platform, the FileDialog object is available. For the dialog limitations on specific mobile operating systems, see the Syntax Assistant. For mobile devices, the option to select files interactively is implemented for the following methods: GetFile(), GetFiles(), PutFile(), and PutFiles(). The File.GetMobileDeviceLibraryFilePresentation() method is implemented. It returns the file presentation for displaying on the mobile device. You can use mobile device library file names (with the content: schema) in constructors of the following objects: File, BinaryData, Picture, and MobileDeviceApplicationRun. You can use them as parameters for the following global context methods: RunApp(), GotoURL(), FileCopy(), MoveFile(), DeleteFiles(), and FindFiles(). On iOS and Android, you can also use them as parameters for the following methods of the MultimediaTools object: PlayAudio() and GetAudioDuration(). The MobileDeviceLibraryDir() global context method is implemented. It returns a path to a mobile device library (a picture, audio, or video library). | The FileDialog object was not available on the mobile platform. | Interactive file operations are implemented for the mobile platform. |
| Mobile device-specific features. | For Android operating system, the option to process incoming call data using 1C:Enterprise script tools is implemented. For the TelephonyTools object, the CallsHandlingSupported(), AttachCallsHandler(), and DetachCallsHandler() methods are implemented. The TelephonyTools.CallsHandlingSupported() method returns True on Android only. | This feature was not provided on the mobile platform. | The option to process incoming call data in mobile applications using 1C:Enterprise script tools is now available on Android operating system. |
| Mobile device-specific features. | Extended multimedia options for the mobile platform:
| These features were not provided on the mobile platform. | Extended multimedia support. |
| Data composition system. | On the mobile platform, the support of data composition system is implemented, except for the objects that allow user interaction. Therefore, all data composition system operations are performed using 1C:Enterprise script tools. In Designer, the option to create data composition schemas for reports that run in mobile applications is implemented. | This feature was not provided on the mobile platform. | Extended report development capabilities on the mobile platform. |
| Add-ins. | On the mobile platform, add-in support is implemented. It uses the NativeAPI technology. You can export a mobile configuration from Designer to 1cema.zip format, which includes the add-ins used in the configuration. When you connect a mobile device using Android Debug Bridge (ADB), add-ins are copied to the device. In the mobile application builder, the option to build applications with add-ins is implemented. Add-in development technology documentation and examples are updated (read more). | The mobile platform did not support this feature. | You have the option to expand mobile platform functionality when its standard features do not cover your needs. |
| Managed forms. | The following features are implemented for the mobile platform:
Support of BorderColor, BackColor, TitleTextColor, and TitleFont properties is implemented for buttons of CommandBarButton and CommandBarHyperlink type and for form group extensions for popups. | This feature was not provided on the mobile platform. | The set of features available on the mobile platform is closer to the set of features available on the desktop platform. |
| Internet-enabled functionality. | The option to check the availability of data transfer network in mobile applications is implemented. The InternetConnectionInformation global context property is implemented. | This feature was not provided on the mobile platform. | The option to analyze available data transfer methods and choose the optimal strategy for operations with external data is implemented. |
| JSON support. | The mobile platform now supports JSON operations. Serialization of XDTO documents to JSON objects is not supported. | This feature was not provided on the mobile platform. | Simplified integration with applications (including web applications) that use JSON data format. The option to store data in JSON format (for example, instead of XML format) is implemented. |
| Internet-enabled functionality. | The behavior of the OpenSSLSecureConnection object is unified with that of the PC platform.
The OSCertificationAuthorityCertificates object is now available on the mobile platform. This change is not implemented in 8.3.8 compatibility mode. | The certificate check always used the root certificates installed on the mobile device. The CertificationAuthorityCertificates parameter of the OpenSSLSecureConnection object constructor was ignored. | Unified behavior of the mobile platform and the PC platform. Eliminated unexpected system behavior. |
| Mobile device-specific features. | The option to check the availability of operations with global contact keys, calendars, and calendar events on different mobile operating systems is implemented. For the ContactManager object, the GlobalContactsKeySupported() method is implemented. For the CalendarsManager object, the GlobalCalendarsKeysSupported() and GlobalEventsKeysSupported() methods are implemented. The GlobalContactKey parameter of the AccountContactData object constructor is no longer supported. The values of properties that describe global contact keys, calendars, and calendar events depend on the result of the function that checks the availability of global key operations. If global key operations are not supported, requests to these values return blank strings. Availability of LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects on the mobile application server is implemented. | The availability of global contact keys, events, and calendar events depended on the platform where a mobile application was running. Developers had no means to check whether operations with global keys from 1C:Enterprise script were supported. The LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects were not available on the mobile application server. | The mobile platform behavior is unified with the general behavior of applications that have features that are not available on some mobile devices or operating systems. |
| Predefined data. | In the mobile platform, support of the following global context methods is implemented: InitializePredefinedData(), SetInfoBasePredefinedDataUpdate(), and GetInfoBasePredefinedData(). | This feature was not provided on the mobile platform. | Unified desktop and mobile platform features related to predefined data. |
| Managed forms. | New managed form interface features in the mobile platform. Now you can:
Command bar commands are no longer included in the More menu. Table row context menu commands can be moved to the More menu if they do not fit the screen. Fixed spreadsheet document areas are displayed in a new way. | These features were not provided.
| The mobile platform interface is closer to the modern interface development standards. |
| Mobile device-specific features. | The implementation of the Beep() method is now uniform with the implementation of the MultimediaTools.PlaySoundAlert(SoundAlert.Default). | The Beep() method did not perform any actions. | You can use the Beep() method to play the default sound alert of a mobile device. |
| Administration tools. | For mobile applications, the following features are implemented:
The backups are stored to the mobile device storage. These options are available in the application settings dialog box (the Administration button in this dialog box). | This feature was not provided. | Additional options for mobile application administrators. |
| Mobile device-specific features. | The 1C:Enterprise mobile platform does not support Apple iAd any more as the service is officially shut down. Google AdMob advertisement service is supported for both iOS and Android devices. In Mobile application builder, you can specify that your application uses ads, and the builder picks the appropriate mobile platform for building the application based on the option that you select. You do not have to modify your iOS applications that support both services but the applications that support only Apple iAd require modification. | The 1C:Enterprise mobile platform supported Apple iAd and Google AdMob. | The Apple iAd service, which is now obsolete, is not supported. |
| Mobile application builder. | Mobile application builder can create application builds for OS emulators. | Mobile application builder could not create application builds for OS emulators. | More options for iOS application developers. |
To apply this optimization to an existing infobase, perform infobase verification and repair with the Reindex infobase tables check box selected.
Once the restructuring is completed, the optimization is applied to all restructured objects.
For the chart of calculation types table that stores serial numbers of calculation type displacements, a nonunique index by displacement number is implemented. As a result, simultaneous editing of a single chart of calculation types in different data areas of a separated infobase never requires waiting for lock releases.
To apply this optimization to existing infobases, perform the infobase verification and repair operation with the Restructure infobase tables option selected.
Version 8.3.8 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.7 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, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, and 8.3.6. | In version 8.3.8 you can run configurations created in version 8.3.7 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.8 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.7 for working with the infobase even after the transition to version 8.3.7. 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). |
| Internet-enabled functionality. | Support of Linux trusted certificate directories (/etc/ssl/certs and /etc/pki/tls/certs) is implemented. The OSCertificationAuthorityCertificates object enabling cross-OS certificate operations is implemented. The LinuxCertificationAuthorityCertificates object caching certificate data on Linux operating system is implemented. It is recommended that you use the OSCertificationAuthorityCertificates object. The CertificationAuthorityCertificates parameter of OpenSSLSecureConnection object constructor accepts objects of OSCertificationAuthorityCertificates and LinuxCertificationAuthorityCertificates types. NSS certificates are no longer supported. | On Linux operating system, the platform used NSS certificate store. | On Linux operating system, in the thin client, the option to access infobases published on resources that require clent certificates is implemented. |
| Web client, web service, and HTTP service publishing tools. System requirements. | Support of Apache 2.4 is implemented for Windows and Linux. For the webinst utility, the -apache24 key is implemented. | This feature was not provided. Apache versions 2.0 and 2.2 were supported. | Extended list of supported web servers. |
| Automated testing. | The About 1C:Enterprise window and the title of the client application window indicate whether the client application is a test manager or a test client. The TestedApplication.SetFileDialogResult() method is implemented, it provides the result of an operation performed in the file selection dialog box. The resulting collection of the TestedApplication.GetChildObjects() method now inlcudes windows that contain text or spreadsheet documents. The TestedForm.ExecuteChoiceFromList() method is implemented, it selects a value from the list opened using the ManagedForm.ChooseFromList() method. The TestedForm.ExecuteChoiceFromMenu() method is implemented, it selects a value from the menu opened using the ManagedForm.ChooseFromMenu() method. For the TestedFormField object, the support of form field extension for a text document is implemented. For the TestedFormField object, the support of form field extension for a formatted document is implemented. For the TestedFormField object, the following methods are implemented: GetHTML() (returns the formatted document content) and InputHTML() (emulates entering text to the formatted document). The TestedFormField.WriteContentToFile() method is implemented, it writes the document file to the hard disk (same as the Save command). The method is available for spreadsheet document, text document, and formatted document extensions. | These features were not provided. | Extended automated testing capabilities. |
| Development tools. | The option to save and restore the settings in the configuration comparison and merging window is implemented. A check box that manages automatic automatic saving of the form settings is implemented. The module comparison and merging form is refactored. Now it includes a command bar with the editor commands. The filter settings now include the Show only properties that were changed twice option. | These features were not provided. | Improved usability for applied solution developers who often perform comparison and merging of configurations with custom settings. |
| Development tools. | The following operations are now available as command-line options for batch Designer startup mode:
The following parameters are implemented for /UpdateCfg command-line option of batch Designer startup:
For /ConfigurationRepositoryUpdateCfg command-line option of batch Designer startup, the -objects parameter is implemented. This parameter specifies that the operation is performed for a specific set of configuration objects. | These features were not provided. The /ConfigurationRepositoryUpdateCfg command-line option of batch Designer startup was only applicable to the entire configuration. | Simplified automatic update of applied solutions. |
| Queries. | For the query debug, the following operations are inplemented: viewing the list of temporary tables, the structure of temporary tables, and the contents of temporary tables. The Query.ExecuteBatchWithIntermediateData() method is implemented. The TempTablesManager.Tables property is implemented. | This feature was not provided. | Extended applied solution debug capabilities, especially when debugging complex batch queries. |
| External data sources. | The ExternalDataSourceManager.TransactionActive() method is implemented. It determines whether an external data source has a transaction in progress. | This feature was not provided. | The option to determine whether an external data source has a transaction is progress is now available. |
| Web services and HTTP services. | Support of web services that support MTOM standard is implemented (read more). | This feature was not provided. Web services that supported MTOM standard were not supported. | Extended capabilities for 1C:Enterprise integration with third-party systems. Integration with web services that support optimized transfer of binary data is available, which reduces the network traffic and RAM usage. |
| OData interface. | The following improvements to the standard OData interface are implemented:
| The standard OData interface provided more limited functionality | 1C:Enterprise object presentations better conform to the OData standard requirements. |
| Configuration extensions. Development tools. | The ConfigurationExtension() method is implemented for configuration objects. It is used to determine the configuration extension where the object belongs. For ConfigurationExtensionsManager.Get() method, the ConfigExtensionSource parameter is implemented. If specifies which list of extensions is retrieved (database extensions only; extensions available in the current session; or extensions that were disabled or did not pass the check at the attachment stage). | This feature was not provided. | Simplified configuration extension operations in 1C:Enterprise script. |
| Configuration extensions. | The ConfigurationExtensionCompatibilityMode property of configuration extensions is implemented. This property is used to limit the extension functionality to ensure its compatibility with a specific version of 1C:Enterprise platform, while leaving the option to edit the extension using a later 1C:Enterprise platform version, which provides more features for configuration extensions.The option to create the following objects in configuration extensions is implemented:
In configuration extensions, the option to change the properties of adopted configuration objects, which describe both main and auxiliary forms, is implemented. For adopted reports, the option to change the Main data composition schema property is implemented. In configuration extensions, changing the Picture property of subsystems, command groups, commands, and common commands is available. In the module editor, the context help is only displayed for objects included in the current extension. | These features were not provided. In the module editor, the context help was displayed for both the original configuration and the extension. | Extended configuration extension capabilities. |
| Development tools. Dumping/loading configurations to files. | The option to export external reports and data processors to XML files is implemented. In Designer, the following File menu commands provide this option: Save, Save as, and Save copy. After the export, changing the object type (external report to external data processor or vice versa) is not available. The import is available using the Open command of the File menu. In the external report or data processor editor dialog box, the options to export the report or data processor to files and import it from files are implemented. The export and import commands are available on the Actions menu of the dialog box. The option to compare an external report or data processor with an external report or data processor stored in XML files is implemented. In the external report or data processor editor dialog box, the following Actions menu command provides this option: Compare and merge with external report or data processor. The option to export and import external reports or data processors to or from XML files using the command-line options of Designer batch mode is implemented. The /DumpExternalDataProcessorOrReportsToFiles and /LoadExternalDataProcessorOrReportsFromFiles keys are implemented. Export to both flat and hierarchical file structures is supported. The export is only available in export format version 2.0. The import format is determined automatically during the import. | These features were not provided. External reports and data processors could only be saved in binary format. | Extended capabilities for external report and data processor operations in scenarios that use external version control systems. The option to use external tools for creating and editing external reports and data processors is implemented. |
| Dynamic lists. | For dynamic lists, support of batch queries is implemented. The dynamic list query builder does not support editing batch queries. This change is not implemented in 8.3.7 repository compatibility mode. | Dynamic lists did not support batch queries. | Extended dynamic list capabilities. |
| Development tools. | In the Syntax Assistant, more information is added to the description of the HTTP service request handler method. This includes the parameter type and the return value type. | In the Syntax Assistant, some information was missing from the description of the HTTP service request handler method. It did not provide the parameter type and the return value type. | Easier developer access to critical information. |
| Data display. Managed forms. | For the StyleColors system enumeration, the following values are implemented:
| The following values of the StyleColors system enumeration were used to format form items:
| Extended style item usage options. |
| Data display. Managed forms. | The sizes of form buttons and command bar buttons are changed. This change is not implemented in 8.3.7 compatibility mode. | Form buttons and command bar buttons had different sizes. | Improved button layout. |
| Technological log. | For the <CALL> technological log event, the Usr property is implemented. It stores the name of the authenticated infobase user. | The Usr property of the <CALL> technological log event was not available, | The <CALL> technological log event is more informative now. |
| ZIP archive operations. |
For the conf.cfg configuration file, the FileNamesEncodingInZipFile parameter is implemented. It specifies the file name encoding in 1C:Enterprise-generated ZIP archives. It can have one of the following values: UTF8 (UTF8 only) and OSEncodingWithUTF8 (both UTF8 and the operating system encoding). If the parameter value is UTF8, the ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, display file names with non-English characters inside the archives incorrectly. The built-in decompression program from OS X displays such file names correctly. If the parameter value is OSEncodingWithUTF8, the built-in decompression program from OS X displays file names with non-English characters incorrectly but other decompression programs display them correctly. | File names in 1C:Enterprise-generated ZIP archives were always stored in both UTF8 encoding and operating system encoding. | The option to specify encoding for the file names in 1C:Enterprise-generated ZIP archives is implemented. |
| DBMS operations. System requirements. | IBM DB2 11.1 DBMS is now supported. | IBM DB2 11.1 DBMS was not supported. | IBM DB2 11.1 DBMS is now supported. |
| Administration tools. | The administration console utility (1cv8a) is available. It includes some of verification and repair features that are available in Designer. You can use the utility to speed up certain operations:
The utility is available for the following operating systems:
| This feature was not provided. Some of the utility features were available as part of the Verify and repair feature in Designer but they took much more time. | Now you do not have to start Designer to fix some of the infobase issues. This can save valuable time because the utility only processes objects with issues detected and performs a limited set of repair operations. |
| 1C:Enterprise script. Configuration extensions. Administration tools. | Unsafe operation protection is implemented. When a potentially unsafe operation is attempted, 1C:Enterprise displays a warning that contains its description and why it might be unsafe. Potentially unsafe operations include:
You have the option to allow or deny a potentially unsafe operation. In some scenarios you have to retry the operation after allowing it. When you load or update a configuration from a .cfu file, 1C:Enterprise adds the warning to existing Designer dialog boxes. The InfoBaseUser.UnsafeActionProtection property is implemented. The ConfigurationExtension.UnsafeActionProtection property is implemented. For the Connect() method of ExternalReports and ExternalDataProcessors objects, the UnsafeActionProtection parameter is implemented. In the configuration extension management dialog boxes (both in Designer and in the standard functions), the Unsafe operation protection check box is implemented. You can define the list of infobases where unsafe operation protection is disabled. For the conf.cfg file, the DisableUnsafeActionProtection parameter is implemented. | Unsafe operation protection was not available. Administrators could prohibit running external reports or data processors using security profiles. | Increased security when running potentially unsafe script. |
| 1C:Enterprise script. Configuration extensions,. External reports and data processors. Administration tools. | In the thin and thick client applications, if unsafe operation protection triggers, once the unsafe operation is completed, the application execution continues as if it was not paused. If the user prohibits the unsafe operation, the platform generates an exception that can be caught using 1C:Enterprise script. The web client and server behavior is not changed. | In the thin and thick client applications, if unsafe operation protection triggered during the execution of the client script, the platform paused the script execution and prompted the user to allow or prohibit the operation. Regardless of the user choice, the script execution was not resumed and the user had to restart the operation. | Simplified application behavior in scenarios where unsafe operation protection triggers in a thin or thick client application. |
| System requirements. | 1C:Enterprise now supports Microsoft Windows Server 2016 (x86-64). | 1C:Enterprise did not support Microsoft Windows Server 2016 (x86-64). | The list of supported operating systems is extended. |
| System requirements. | Astra Linux Special Edition 1.5 is supported. | This release was not supported. | New Linux release is supported. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Interface. | In the Taxi interface, the appearance of scroll bars is changed. | In the Taxi interface, scroll bars had a different appearance. | Better visibility of scroll bars in managed forms. |
| Interface. | In the search dialog box that can be opened from a managed form table linked to a FormDataCollection attribute, the order of fields is changed: the Search in field comes before the Find field. | In the search dialog box that could be opened from a managed form table linked to a FormDataCollection attribute, the Find field came before the Search in field. | Unified look and feel of search dialog boxes in managed form fields linked to various data types. |
| Managed forms. | In the Taxi interface, the following keyboard shortcuts are implemented for the managed form navigation panel:
| In the Taxi interface, keyboard shortcuts for moving through navigation panel items were not available.
| Improved usability of 1C:Enterprise client applications that use the Taxi interface. |
| Interface. | In the Taxi interface, in dynamic lists, the vertical scrollbar is replaced with a set of buttons (go to beginning, go to end, page up, and page down) located at the right bottom part of the table linked to a dynamic list. | Tables linked to dynamic lists had vertical scroll bars that did not provide comfortable navigation. | Improved navigation in dynamic lists. |
| Interface. Dynamic lists. | The following commands are added to the context menu of a table linked to a dynamic list whose main table is a document list or a document journal: Post and Clear posting. | For a table linked to a dynamic list whose main table was a document list or a document journal, the Post and Clear posting commands were only available on the More menu.
| Simplified posting and clearing posting in dynamic lists. |
| Interface. Dynamic lists. | The context menu of a managed form table that is linked to the main attribute of a managed list form having the Generate command now includes a Generate submenu. | The generation commands were only available in the command bar of a managed form table linked to the main attribute of a managed list form. | Simplified document generation based on dynamic lists.
|
| Interface. | In the thick and thin clients, in the managed mode, the option to add a search string to the system command area is removed from all interface modes. | The option to add a search string to a system command area was available. | Removed a feature that was no longer in use. |
| Interface. | The system command area displays the current user name. It is a hyperlink that opens a dialog box with the user info. The dialog box includes the option to log out of the client application. If the user is authenticated using OpenID, this also cancels OpenID authentication (so that a single command both exits the application and cancels OpenID authentication). If the infobase does not have users, the user name is not displayed. The option to specify the URL that is opened after the exit from the web client in the .vrd file is implemented (you can also specify the URL in the publishing settings dialog box in Designer, and then the platform writes it to the .vrd file). The <exitURL> element of the <point> element of default.vrd file is implemented. This change is not implemented in 8.3.7 compatibility mode. | The exit command and the cancel OpenID authentication command were available on the File menu. | Client application behavior is closer to the standard behavior of web applications. |
| Web client. Managed forms. | In the web client, streamlined the undo operation in text document fields and input fields. In Safari web browser for Apple iPad, the undo operation is applied to an entire word (and not to each of its characters), just like it is implemented in other web browsers. | In the web client, the undo and redo operations were not optimal. | Improved usability of text operations in the web client. |
| Client application. | On Windows 7 and later and on Linux with Unity desktop shell, support of jump lists is implemented. The last used infobases are automatically added to a jump list, so that a user can open these infobases without opening the 1C:Enterprise start dialog box. On Windows 7 and later, the option to define buttons that are displayed in the application preview taskbar window (using 1C:Enterprise script) is implemented. This is similar to Windows Media Player buttons in its preview window. On Windows 7 and later and on Linux with Unity desktop shell, the option to define a picture or a number to be displayed at the bottom right corner of the application taskbar icon (using 1C:Enterprise script) is implemented. On Windows XP and later and on Linux with Unity desktop shell, the option to enable blinking of a taskbar application icon (using 1C:Enterprise script) is implemented. The OSTaskbarManager object is implemented. | This feature was not provided. | Inproved usability of 1C:Enterprise applications on some operating systems. |
| Client application. Interface. | 1C:Enterprise user interface now has screen reader support, which provides accessibility for blind and visually impaired people. This option is available on Windows XP or later. It uses the NVDA screen reader software (read more). Screen reader support is only available for managed forms, in the thick and thin clients that use the Taxi interface. | This feature was not provided. | Improved 1C:Enterprise usability for blind and visually impaired people due to screen reader support. |
| Dynamic lists. | In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the Change form command on the More menu) is implemented. Adding subordinate fields is available for fields whose type includes at least one reference type. | In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the Change form command on the More menu) was not available. | Improved data display capabilities in dynamic lists. |
| Web client. File operations. | In the web client, a CreateDirectory() or BeginCreatingDirectory() method call includes the question to the user: Do you want to create the DirectoryName directory? In the RequestUserPermission() and BeginRequestingUserPermission() method calls, this confirmation is included in the final question to the user (provided that the confirmation is needed). | In the web client, directories were created without user confirmation. | The platform behavior conforms to the general security recommendations for file operations in the web client. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Server clusters. | Optimized operations with session data. The lags experienced by end users during the periods of high load on the session data storage in client/server mode are eliminated. | Operations with session data required optimization. End users experienced lags during the periods of high load on the session data storage in client/server mode. | Improved 1C:Enterprise usability. |
| Interface. | The impact on the total number of opened forms to the opening of new forms is reduced. | The impact on the total number of opened forms to the opening of new forms was significant. | Streamlined form opening when many other forms are open. |
| Queries. | In the query language, <EXPRESSION> OR TRUE expressions are optimized. This change is not implemented in 8.3.7 compatibility mode. | The query language did not feature additional optimization of query texts. | In some scenarios, the optimization increases the performance of dynamic lists and access restriction queries because the DMBS generates a simpler query plan. |
| Development tools. | The dump configuration to files and restore configuration from files operations are optimized for scenarios where the configuration includes a large number of managed forms. | The performance of dump configuration to files and restore configuration from files operations was insufficient. | In scenarios where the configuration is stored in an external system, improved performance of data exchange between the infobase and that system. |
| Database operations. | File infobase operations are optimized in the scenario where all of the following conditions are met:
| In the specified scenario, the file infobase performance was insufficient. | Improved performance of database configuration updates for file infobases in the scenario where Designer and the database are located on different computers. |
| Data exchange. | The performance of initial infobase image creation is improved. The performance or reading records from independent nonperiodic information registers during the initial image creation is improved. | The performance of initial infobase image creation was insufficient. | Faster creation of subordinate node infobases in distributed infobases. |
| DBMS operations. | Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized. | The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient. | Improved performance of temporary table operations. |
| DBMS operations. | In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) have a different execution algorithm when applied to lists containing more than 100 records. This change is not implemented in 8.3.7 compatibility mode.
| In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) had a different execution algorithm when applied to lists containing more than 1000 records. | Improved performance for some scenarios that include access to Oracle Database DBMS. |
| Administration tools. Technological log. Server clusters. DBMS operations. | Getting DBMS lock data is optimized. The time required for getting the data does not depend on the number of infobases in the cluster. The server cluster service that collects DBMS lock data is implemented. It is named AuxiliaryService (Utility cluster service). The option to manage the collection of DBMS lock data is implemented in the technological log (<DBMSLOCKS> element). Enabling the data collection increases the DBMS load. | The time required for getting DBMS lock data depended on the number of infobases in the cluster. The option to manage the collection of DBMS lock data using the technological log was not available.
| Extended database diagnostics. |
| Administration tools. Database operations. | In the file mode, infobase operations are optimized. To support the optimization, the file database data storage format is updated to new version 8.3.8 format. The option to change the page size of the infobase file (1Cv8.1CD) is implemented. The page size can have one of the following values: 4096, 8192, 16384, 32768, or 65536 bytes. If you set the page size for a database having version 8.3.8 format to 8192 bytes or more, the internal database file size cannot exceed 6 GB. 1C:Enterprise version 8.3.8 can open infobases created in the earlier 1C:Enteprise versions (and having version 8.2.14 database format) without changing their compatibility modes. By default, new infobases have version 8.2.14 format. For the conf.cfg file, the DBFormatVersion parameter is implemented. It defines the format of newly created file-mode infobases. For the infobase connection string, the DBFormat and DBPageSize parameters are implemented. They define the format and page size for new infobases. To migrate data between infobase formats, you can use a .dt file (provided that the target infobase has the required format) or convert the infobase file using cnvdbfl utility. The cnvdbfl utility can change the infobase file page size during the conversion. | All infobases had the same format (version 8.2.14). Pages of the infobase file had fixed size: 4096 bytes. The option to change the size was not available. The internal database file size could not exceed 4 GB. | For infobases with large page sizes, the infobase opening time is reduced and the performance of some queries is improved. |
| Server clusters. | Reduced size of session data on the hard disk. Session data is stored in the server cluster in compressed form. | Session data was stored in the server cluster in uncompressed form. | The space occupied by internal cluster data is reduced. Some of the internal cluster operations are streamlined. |
| Client application. | Faster thin client startup in the file mode. | The performance of the thin client startup in the file mode was insufficient. | Faster thin client startup in the file mode. |
| Database operations. | Restructuring of separated hierarchical catalogs is optimized. | The performance of restructuring separated hierarchical catalogs was insufficient. | The performance of restructuring separated hierarchical catalogs is improved. |
| Database operations. | The RAM usage is reduced for restructuring a database that contains large amounts of binary data in file mode. | Restructuring a database that contained large amounts of binary data in file mode might result in an unexpected shutdown due to insufficient RAM. | Improved system stability for database restructuring in file mode. |
| Interface. Server clusters. | For 1C:Enterprise installations that use Microsoft SQL Server, improved performance of opening user work history. The performance improvement will take effect after you perform the following steps:
| For 1C:Enterprise installations that used Microsoft SQL Server, opening user work history was slower. | Improved performance of opening user work history. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Software licensing. Administration tools. | The command-line utility for software license management (which includes license activation, getting license data, getting the list of licenses, and more) is implemented. The utility is delivered in two distribution packages, which are located in the ExtDst subdirectory of the platform version directory (provided that the thick client or 1C:Enterprise server is installed for this platform version). The utility is not installed automatically. In order to use it, you have to install it first. The utility is available for Windows operating system (both architectures) and for Linux operating system (both architectures, as .deb- and .rpm packages). To access the utility, use the ring license command. The utility requires Java version 8. The detailed utility description is available in 1C:Enterprise documentation. | Software license activation was only available in the interactive mode. No other software management options were available. | Simplified software license management on the end-user computer. |
| Managed forms. | During the automatic generation of managed form items, the names of items that match the CreateByParameter and ShowInList commands are generated according to the following template: <Form><CommandName><ConfigurationObjectName>. This change is not implemented in 8.3.7 compatibility mode. | During the automatic generation of managed form items, the names of items that matched the CreateByParameter and ShowInList commands were generated according to the following template: <Form><CommandName><SequentialNumber>.
| Better usability for applied solution developers. |
| Managed forms. | In a managed form, the width of a drop-down list of an input field is adjusted according to the width of data displayed in that list. Pressing the Home or End key (as a single key or with any modifier keys) is handled directly in the input field. | In a managed form, each drop-down list of an input field had a fixed width set by the platform or by a developer. Pressing the Home or End key (as a single key or with any modifier keys) in an input field had no effect. | Improved usability of input fields in drop-down lists. |
| Development tools. | The following features are implemented in the compare and merge modules window :
The following features are implemented in the window that displays the result of merging with a third-party tool:
When a supported configuration is being updated, the compare and merge configurations window has a new filter option: Show only properties with merge conflicts. The filter displays the objects that are not merged with a third-party tool. | This feature was not provided. | Improved usability for developers working on applied solution update functionality. |
| Development tools. | The Explanation field of the property palette displays Russian property names only when the Russian 1C:Enterprise script variant or the Russian platform interface is selected. | The Explanation field of the property palette always displayed both Russian and English property names.
| Improved Designer usability for English-speaking developers. |
| Web client. Spreadsheet documents. | In the web client, the option to display a background picture and a pattern in a spreadsheet document cell is implemented. | In the web client, displaying background pictures and patterns in spreadsheet document cells was not supported. | Extended spreadsheet document style options in the web client. |
| Data display. Spreadsheet documents. | In spreadsheet documents exported to PDF format, font substitution for characters that are not available in the current font is implemented. This change is not implemented in 8.3.7 compatibility mode.
| In spreadsheet documents exported to PDF format, characters that were not available in the current font were displayed as missing characters (squares). | In spreadsheet documents exported to PDF format, non-English characters are displayed correctly. |
| Spreadsheet documents. | When a spreadsheet document is exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells is implemented. This option is not available when exporting spreadsheet documents to XLS (Microsoft Excel 95) format. This change is not implemented in 8.3.7 compatibility mode. | When a spreadsheet document was exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells was not supported. | Better conversion of spreadsheet documents to Microsoft Excel and ODS formats. |
| Configuration extensions. | When an attribute of composite type that does not include references to configuration objects is adopted, the composite type is fully adopted. During the next adoption attempt, the composite type is supplemented with the set of types from the main configuration. When an attribute of composite type that includes references to configuration objects (nonprimitive types) is adopted, it is adopted as AnyRef. During the next adoption attempt, the AnyRef type is only added if the type is no longer composite and does not include CatalogRef, DocumentRef, and similar types. When a configuration extension is attached, the following rules apply:
If an attribute of composite type cannot include AnyRef type, any composite type adopted for this attribute is adopted with a single Arbitrary type. Such attributes cannot cause configuration extension attachment errors. | When a composite type was adopted, primitive types were always adopted, and a single type from the configuration object reference types was adopted. When a configuration extension was attached, the following rule applied: if an extension attribute type included composite types, this required the matching main configuration attribute to include exactly the same composite types. | Simplified usage of composite types in configuration extensions. |
| Web services and HTTP services. | During a web service call, if an internal server infrastructure error that is not related to SOAP occurs, the error message contains the correct diagnostics text. The web service call error message is more detailed and can include data from the faultfactor (Node) and Role tags of the web service response. | During a web service call, if an internal server infrastructure error that was not related to SOAP occurred, an incorrect error message was displayed, and the information about the actual error cause was lost. The web service call error message did not include additional details from the web service response.
| The web service call error message is more detailed, which simplifies error diagnostics. |
| Background and scheduled jobs. | When a client application is started with a file infobase, there is a 2-minute delay before starting the execution of scheduled jobs. | When a client application was started with a file infobase, there was a 1-minute delay before starting the execution of scheduled jobs. | Faster startup of client applications in file mode. |
| Web client, web service, and HTTP service publishing tools. | When a user disables publishing to a web server from Designer, they are prompted to restart the web server. | When a user disabled publishing to a web server from Designer, they were not prompted to restart the web server. | Users are given better understanding of the disable publishing operation, since the publishing is actually disabled when the server is restarted. |
| Development tools. | In Designer, the option to customize the background of the context method parameter help is implemented. In the context help, links to the Syntax Assistant have the Identifiers color and normal text has the Miscellaneous color. | In the context help, links to the Syntax Assistant had the default Identifiers color and normal text had the default Miscellaneous color. | You can customize the context help of method parameters to make it readable when the module editor color scheme has dark background. |
| XML and XDTO support. Web services and HTTP services. | In the XDTO model, new properties are implemented. They ensure correct processing of XSD schemas with any combinations of the following attribute values: elementFormQualified (Qualified element form package property), attributeFormQualified (Qualified attribute form package property), and form (property of the Qualified element). The XDTO package editor provides the option to view and edit the new properties. In Version 8.3.7 or earlier compatibility mode, the new properties have their default values. | When processing XSD schemas, the XDTO model ignored actual values of elementFormDefault and attributeFormDefault attributes. It also ignored the form attribute of XSD schema elements and attributes. Instead, it always used the following values:
| Extended list of web services that are compatible with 1C:Enteprise as they are, without any manual corrections to their descriptions. |
| Administration tools. | The wizards used to add and edit infobases are refactored, the number of wizard pages is reduced. Automatic detection of the infobase connection type is implemented, based on the string stored in the clipboard or the string entered in the Specify infobase name field. This includes the detection of the path to a file infobase or the URL for accessing an infobase running on a web server. Once the infobase type is detected, all of the related wizard fields are filled in. | The wizards used to add and edit infobases were more complex and had more pages. | Simplified adding of infobases to the list. |
| Managed forms. | If an input field of a managed form displays ValueList data, the value list form that is opened for editing the data gets the following properties from the input field:
| If an input field of a managed form displayed ValueList data, the value list form that was opened for editing the data received the following properties from the input field:
| Eliminated unexpected system behavior. |
| Full-text search. Input by string. Dynamic lists. | Input by string and full-text search in dynamic lists find data that is not yet indexed for the full-text search. | Input by string and full-text search in dynamic lists did not find data that was not yet indexed for the full-text search. | Data that is not yet indexed for the full-text search is included in full-text search results and input by string results. |
| Managed forms. | In the Taxi interface, the appearance of managed form buttons and command bar buttons is changed. For the CommandBarButton and CommandBarHyperlink buttons, support of the following properties is implemented: BackColor, TextColor, Font, BorderColor (except CommandBarHyperlink buttons). For form group extension submenus, support of the following properties is implemented: BorderColor, BackColor, TitleTextColor, and TitleFont. This change is not implemented in version 8.3.7 compatibility mode and in version 8.2 interface compatibility mode. For the standard Copy command of dynamic list table extension:
For MoveUp and MoveDown managed form table commands, the Auto value of the OnlyInAllActions property is equivalent to No. These commands are included in a compact button group. This change is not implemented in version 8.3.7 compatibility mode. In version 8.3.7 compatibility mode with compact interface the button height in the thin client differs from the button height in the web client. | In the Taxi interface, the appearance of managed form buttons and command bar buttons was different. The CommandBarButton buttons had BackColor, TextColor, Font, and BorderColor properties, which were never used. Form group extension submenus had BorderColor, BackColor, TitleTextColor, and TitleFont properties, which were never used. For the standard Copy command of dynamic list table extension:
For MoveUp and MoveDown managed form table commands, the Auto value of the OnlyInAllActions property was equivalent to Yes. | Improved form creation capabilities in the Taxi interface. The default location of some frequently used buttons (Copy in dynamic lists and row movement commands in other tables) changed from the More menu to the command bar. |
| Managed forms. | The option to display command bar commands as hyperlinks is implemented. Pop-up menus do not support displaying commands as hyperlinks. For the FormButtonType enumeration, the CommandBarHyperlink value is implemented. In 8.3.7 compatibility mode, the FormButtonType.CommandBarHyperlink value is treated as FormButtonType.CommandBarButton. In the Taxi interface, the option to set horizontal picture alignment for managed form buttons is implemented. Pop-up menus do not support this feature. For managed form buttons, the PictureLocation property is implemented. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode. The option to set command bar button spacing is implemeneted. Managed form group extension for a button group is implemented. Pop-up menus do not support this feature. The ButtonGroupRepresentation system enumeration is implemented. In 8.3.7 compatibility mode and version 8.2 interface compatibility mode, the button spacing value is ignored. The option to set button shape (except pop-up menu buttons) is implemented. For managed form buttons and form group extensions for popups, the Shape property is implemented. Pop-up menu commands do not support this property. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode. The option to set managed form button shape is implemented. For managed form buttons and form group extensions for popups, the ShapeRepresentation property is implemented. The ButtonShapeRepresentation system enumeration is implemented. Pop-up menu commands do not support this feature. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode. | Command bar commands could not be displayed as hyperlinks. The option to set horizontal picture alignment for managed form buttons was not available. The option to set command bar button spacing was not available. The option to set button shape was not available. The option to set command bar button appearance was not available. | More managed form appearance options in the Taxi interface. |
| Managed forms. | Recommendations about the usage of user messages are added to the documentation. The recommendations are aimed to reduce the chance of situations where users cannot read the displayed messages. | The documentation did not contain the recommendations aimed to reduce the chance of situations where users cannot read the displayed messages. | The documentation is improved. |
| Software licensing. | Updates of Windows 10 operating system never deactivate software licenses. | The software licensing system was not fully compatible with Windows 10. Updates of Windows 10 could deactivate a software license. | Improved compatibility of the software licensing system with Windows 10. |
| Localization. | The Kazakh interface language (language code: kk) is not supported. | The Kazakh interface language (language code: kk) was supported. | The Kazakh interface language is not supported. |
| Regional settings. | For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ (Zabaikalye Territory), 27-FZ (Astrakhan Region), 57-FZ (Altai Territory), 58-FZ (Republic of Altai), 59-FZ (Sakhalin Region), 69-FZ (Ulyanovsk Region), 87-FZ (Magadan Region), 109-FZ (Tomsk Region), 271-FZ (Novosibirsk Region), and 395-FZ (Saratov Region). This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers. | The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ, 87-FZ, 109-FZ, 271-FZ, and 395-FZ. | The time offset changes introduced by the new law are implemented. |
| Spreadsheet documents. | Text copied from Microsoft Excel speadsheet cells is fully pasted to 1C:Enterprise spreadsheet cells, regardless of its length. | Text copied from Microsoft Excel spreadsheet cells and pasted to 1C:Enterprise spreadsheet cells was cut, only the first 255 characters were copied. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | Improved processing of data having date and time format during the import from Microsoft Excel:
This change is not implemented in 8.3.7 compatibility mode. | Processing of data having date and time format during the import from Microsoft Excel was performed as follows:
| Improved accuracy of date and time import from Microsoft Excel. |
| Web services and HTTP services. | For configurations that include HTTP services, setting compatibility mode to Version 8.3.4 or earlier is allowed. If your configuration includes HTTP services and you previously opened it with 1C:Enterprise Designer 8.3.4, when you open it with 1C:Enterprise 8.3.8, perform the following steps:
| In 1C:Enterprise 8.3.7 or earlier, if a configuration included HTTP services, setting its compatibility mode to Version 8.3.4 or earlier was not allowed. | You can add HTTP services to configurations that run in compatibility mode Version 8.3.4 or earlier. |
| Client application. Internet-enabled functionality. | You have the option to select the set of external resources that the platofrm uses (in ExternalResourcesMode parameter of conf.cfg configuration file). If this parameter is not specified, the platform selects its value automatically. | This feature was not provided. | You have the option to select the set of external resources that the platofrm uses. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Internet-enabled functionality. | The NSSSecureConnection object and NSS certificates are no longer available for use in 1C:Enterprise script. | 1C:Enterprise supported NSS certificates in 8.3.6 compatibility mode. | Support of NSS certificates is discontinued. |
| Internet-enabled functionality. | Support of TLS protocol versions 1.1 and 1.2 is implemented for scenarios where the client certificate is not specified in the connection settings. The SSL protocol version 3.0 is only used when the client application is started with /HttpsForceSSLv3 command-line option. In all other scenarios SSL version 3.0 is not used. 1C:Enterprise ignores the AllowSSLv3 parameter in conf.cfg file. The InternetMail object does not support SSL version 3.0. | 1C:Enterprise only supported TLS protocol version 1.0. The AllowSSLv3 parameter was available for use in conf.cfg file. The InternetMail object supported SSL version 3.0.
| Increased security of connections established by client applications for Internet operations. |
| Internet-enabled functionality. | The platform no longer uses cacert.pem file for creating HTTPS/FTPS connections. The platform uses the root certificate store of the operating system for creating HTTPS/FTPS connections. This change is not implemented in 8.3.7 compatibility mode. | The platform used cacert.pem file for creating HTTPS/FTPS connections in scenarios where no certificate stores were specified explicitly. | The outdated technology is no longer supported. |
| Managed forms. | For managed forms, the option to update data presentations only for the specified set of form items is implemented. For the RefreshDataRepresentation() method, the UpdateItems parameter is implemented. For the EditTextUpdate system enumeration, the Always value is implemented. | The option to specify a set of form items when updating data presentations using the RefreshDataRepresentation() method was not available. | Form data can be updated in idle handlers without losing the text being edited in a text box. |
| Dumping/loading configurations to files. | The dump of the Source property of the FormItemAddition object to a file is more human-readable. You can restore configuration from files having both property dump formats. | The dump of the Source property of the FormItemAddition object to a file was less human-readable. | Dumping configurations to files produces files that are more human-readable. |
| XML and XDTO support. Development tools. | Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) is much more detailed. During the creation of WSDefinitions object, exceptions are raised if the used WSDL description has errors. The WSDL description used to create WSDefinitions or WSReference objects must comply with the following rules:
This change is not implemented in 8.3.7 compatibility mode. | Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) was not sufficiently detailed. During the creation of WSDefinitions object, if the used WSDL description had errors, invalid elements were ignored. If the first tag of the WSDL description used to create WSDefinitions or WSReference objects was not <definitions>, empty web service description objects were created. If the WSDL description used to create WSDefinitions or WSReference objects did not include the targetNamespace attribute of the <xs:schema> element, the platform set a pseudorandom namespace. | Better diagnostics for WSDL description operations. |
| Queries. | If a constant stores a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that includes a request to the Value field returns a value of that type. This change is not implemented in 8.3.7 compatibility mode. | If a constant stored a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that included a request to the Value field returned a value of BinaryData type. | Eliminated unexpected system behavior. |
| Print tools. | The following behavior of the RepresentableDocumentBatch.Print() method is implemented:
This change is not implemented in 8.3.7 compatibility mode. The RepresentableDocumentBatch.Title, property is implemented. It is used for generating the batch presentation. | The RepresentableDocumentBatch.Print() method created a job for each document in a batch. | Improved printing of document batches. |
| Data composition system. | Text and Format conditional appearance items are applied to fields of chart grouping templates of data composition systems regardless of the previous Format value (even if the previous value is taken from the data composition system). Text conditional appearance item has higher priority than Format conditional appearance. This change is not implemented in 8.3.7 compatibility mode. | Text and Format conditional appearance items were applied to fields of chart grouping templates of data composition systems only if the Format conditional appearance was not applied to those fields earlier. | Eliminated unexpected system behavior. |
| Data composition system. | The MarkNegatives conditional appearance property is only used if this property is set to True and the Use conditional appearance property is also set to True. This change is not implemented in 8.3.7 compatibility mode. | The MarkNegatives conditional appearance property was only used if the Use conditional appearance property was set to True. | Eliminated unexpected system behavior. |
| Data composition system. | In the query language, the CASE operation result is based on all expression types from all THEN branches of that expression. This change is not implemented in 8.3.7 compatibility mode. | In the query language, the calculation of CASE operation result ignored all THEN branches that included constant expressions with NULL values. | Eliminated unexpected system behavior. |
| Full-text search. | The option to set a size limit for data indexed for the full-text search is implemented. The default size limit is 1 MB. For the FullTextSearchManager object, the SetMaxIndexedDataSize() and GetMaxIndexedDataSize() methods are implemented. The <FTEXTSKIP> technological log event is implemented. This change is not implemented in 8.3.7 compatibility mode. | The option to set a size limit for data indexed for the full-text search was not available. All infobase data was indexed. | You can limit the full-text search scope by excluding large blocks of data you do not need to search. This increases the performance of full-text search indexing and reduces the index size. |
| Client application. Internet-enabled functionality. Administration tools. | The algorithm that retrieves the list of infobases and platform updates over HTTPS no longer uses the cacert.pem file, which is included in the platform distribution kit. On Linux, the platform gets certificates from the certification centers specified in the operating system. On Windows, the platrorm uses the operating system root certificate store. | On Windows, the platform used the cacert.pem file and the operating system root certificate store in order to check an HTTPS connection. On Linux, the platform used the cacert.pem file only. | Simplified administration of platform update over HTTPS. |
| Linux. System requirements. | The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system is refactored. The fontconfig library is used to get the list of fonts. This library is included in the system requirements. The list of directories used for storing fonts is removed from 1C:Enterprise documentation. | The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system used a fixed directory list, which was described in 1C:Enterprise documentation. The fontconfig library was not used for getting the list of fonts. | Extended the list of fonts available to 1C:Enterprise on Linux operating system. Simplified 1C:Enterprise administration. |
| System requirements. | The type specified for a data composition schema parameter affects the type of query fields that use this parameter. This change is not implemented in 8.3.7 compatibility mode. | The type specified for a data composition schema parameter did not affect the type of query fields that used this parameter. | Data displayed in reports better matches the input parameters. |
| Dynamic lists. | The dynamic list implementation is refactored in order to increase its quality. The list of virtual dynamic list fields that are not available for use in filter, grouping, and order settings is extended. If the main dynamic list table does not have key fields (according to 1C:Enterprise script object model) and a grouping is set for this table, an error is generated. When a filter, sorting, or grouping by a field that is not included in a query is specified using 1C:Enterprise script, an error informing that the field is not found is displayed. The list of restrictions to queries used to generate dynamic lists is modified. Dynamic list sorting specifics are described in the documentation. The description of algorithms that dynamic lists use for getting data is changed. The standard row picture is generated based on the standard attributes. If a query includes fields whose aliases are identical to standard attribute names and these fields store other data, these fields are not used in standard picture generation. If a dynamic list filter cannot be converted to a query language expression, an error is generated. Dynamic list column data that is not displayed and does not have the Use always property set is not sent to the client. Client access to such columns is not available. If a dynamic list column has the Use always property but the current user does not have the View right for that column, the column data is not sent to the client. Client access to such columns (using the CurrentData property or the RowData() method) is not available. Automatic dynamic list filters for standard Owner, Parent, Date, Period, and IsFolder fields are applied using data composition system tools. Automatic dynamic list filters for key fields can be applied using data composition system tools or using direct addition of main table filter conditions to query texts. When a filter is applied using data composition system tools, it can be applied in nested queries and virtual table parameters. This can significantly change the dynamic list data selection result (compared to the result obtained in 8.3.7 compatibility mode). The detailed description of all the changes listed above is included in the documentation. This change is not implemented in 8.3.7 compatibility mode. | The following virtual fields were not available in dynamic list sorting and grouping settings: DataVersion, PredefinedDataName, tabular sections fields, and fields having the following types: Type, String (unlimited length), and BinaryData (unlimited length). The list of restrictions to the grouping and ordering settings was different and it was not full. If the main dynamic list table did not have key fields (according to 1C:Enterprise script object model) and a grouping was set for this table, the content of data to be displayed was undefined. When a filter by a field that was not included in a query text was set, the filter might be applied without displaying any errors, or ignored. If grouping or sorting by a field that was not included in a query was specified using 1C:Enterprise script, the field was ignored. The list of restrictions to queries used to generate dynamic lists was different. The list of dynamic list sorting specifics was not documented. The description of algorithms that dynamic lists used for getting data was different. If a dynamic list query had fields with aliases matching the names of standard attributes used to generate standard row pictures, they were used in the generation of standard pictures (except the IsFolder attribute). If a dynamic list filter could not be converted to a query language expression, the filter was applied by data composition schema processor after getting the data, and this might reduce the amount of displayed data. If dynamic list settings included grouping or sorting fields that were unavailable (before applying rights and functional options), these fields were ignored. In some scenarios dynamic list column data that was not displayed and did not have the Use always property set was sent to the client. If dynamic list column had the Use always property but the current user did not have the View right for that column, the column data was sent to the client. In this scenario the default values of specific data types were used as column values. Automatic dynamic list filters for key fields and for standard Owner, Parent, Date, Period, and IsFolder fields were applied by direct addition of their conditions to query texts. | Improved quality and reliability of dynamic lists. More details about dynamic list specifics are added to the documentation. |
| Background and scheduled jobs. | When a nonserializable value is passed to BackgroundJobs.Execute() method as a background job parameter, the background job is not started and an exception is raised. This change is not implemented in 8.3.7 compatibility mode. | When a nonserializable value was passed to the BackgroundJobs.Execute() method as a background job parameter, the background job was started and the Undefined value was stored to that parameter. This did not raise any exceptions. | The start of background jobs complies with the global error diagnostic rules. |
| Administration tools. | During an unexpected shutdown of the thin client, the dump generation includes taking a screenshot (prntscrn attribute of dump element of logcfg.xml file).
| During an unexpected shutdown of the thin client, the dump generation did not include taking a screenshot. | Eliminated unexpected system behavior. |
| Queries. | The result of division by NULL is treated as a number of unspecified length . This number cannot be used in operations that do not accept numeric operands (such as AND, OR, NOT). This change is not implemented in 8.3.7 compatibility mode. | The result of division by NULL was not treated as a number and therefore could be used in operations that did not accept numeric operands (such as AND, OR, NOT). | Eliminated unexpected system behavior. |
| Managed forms. Interface. | The approach to processing the closing of applications and managed forms is changed:
This approach is described in detail in the documentation. For BeforeClose managed form event handler, the Exit and WarningText parameters are implemented. For OnClose managed form event handler, the Exit parameter is implemented. If BeforeClose or OnClose managed form event handler has the Exit parameter, in version 8.3.7 compatibility mode the parameter is set to Undefined. For BeforeExit managed application module event handler, the WarningText parameter is implemented. This change is not implemented in 8.3.7 compatibility mode. | Depending on the modality usage mode, different approaches to closing managed forms and the main application window were used. In some scenarios (especially in the web client) these approaches led to errors that were hard to detect and fix. | Unified approach to closing forms and the main application window, which provides acceptable user interaction capabilities in all client applications. The implemented platform behavior conforms to the methodology and technical requirements of modern web browsers. |
| Administration tools. Client application installation. | When an infobase that has a platform version specified in a local or global list of infobases is started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version is performed regardless of the presence of /AppAutoCheckVersion command-line option. If a version that is not available on the local computer is specified and this version cannot be installed, an attempt to run the infobase with the latest 1C:Enterprise version is made During the client application update over HTTP, the check for operating system user right to perform this operation is disabled. If the user does not have sufficient rights for installing the client application, the UAC dialog box prompting to confirm the installation on behalf of a user that has administrative rights is displayed. Error diagnostics during the download and installation of the client application distribution kit over HTTP is improved. In the /AppAutoCheckVersion command-line option, you can explicitly specify whether the search for a specific 1C:Enteprise version is performed. | When an infobase was started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version was only performed if the command line included the /AppAutoCheckVersion option. During the client application update over HTTP, the check for operating system user right to perform this operation was performed. | The usability of selection and update of the client application used to access a specific infobase is improved. Improved reliability of automatic thin client updates over HTTP. |
| Administration tools. | When the thin client is installed from a custom distribution kit, a single 1cestart shortcut is created in the 1C:Enterprise folder. | When the thin client was installed from a custom distribution kit, the 1C:Enterprise folder included 1cestart shortcut and the Advanced folder with subfolders for each installed 1C:Enterprise version. | Reduced number of 1C:Enterprise startup options available after the installation of the thin client. |
| Administration tools. | In the client application startup command line, the rules for parsing mandatory parameters are modified. If an option that has a mandatory parameter is specified, the parameter must be also specified (or the option must be omitted). Parameters beginning with slash marks "/" are allowed. | In the client application startup command line, the rules for parsing mandatory parameters were different. Mandatory option parameters could be omitted. Parameters beginning with slash marks "/" (full file name on Linux) could be treated as command-line options. | Eliminated unexpected system behavior. |
| Administration tools. | 1C:Enterprise documentation and Designer help include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode, which were previously missing. For the infobase creation mode (CREATEINFOBASE), new /DumpResult option is implemented. It enables writing the operation result to a file. In the file mode, batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option automatically creates an infobase if the database file is not available in the directory. | 1C:Enterprise documentation and Designer help did not include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode. In the file mode, during the batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option, if the dababase file was not found in the specified directory, the user was asked for the confirmation of further actions. | Improved 1C:Enterprise documentation and Designer help. Simplified batch Designer startup in some usage scenarios. |
| Data composition system. | If a data set field of a data composition schema has an ordering expression specified and the data composition settings include ordering by this field (Descending), the direction speficied in the ordering expression is reversed. This change is not implemented in 8.3.7 compatibility mode. | If a data set field of a data composition schema had an ordering expression specified, ordering for this field was always taken from the ordering expression, while the direction specified in the field settings was ignored. | Eliminated unexpected system behavior. |
| Managed locks. Accounting registers. | Managed locks that are set for writing accounting register records in the LockForUpdate mode are set by values of nonturnover extra dimensions only. When you set a lock for further operations with balances, it is recommended that you do not specify turnover extra dimension values (you can use the LockForUpdate property or explicitly use a managed lock). When you set a lock for further operations with turnovers, specify all the required extra dimenstion values, including the values of turnover extra dimensions (use the managed lock explicitly). This change is not implemented in version 8.3.7 compatibility mode. | Managed locks that were set for writing accounting register records in the LockForUpdate mode included locks by all extra dimension values. | The behavior of LockForUpdate property of accounting register object is better suited for solving typical tasks. In the LockForUpdate mode, the resulting lock does not inlcude turnover extra dimensions, which fits the frequently used scenarios where the lock is used to check the balances but not the turnovers. |
| Queries. | In a query, if a single system enumeration is retrieved and it is not combined with other types, the GROUP BY operation groups the values of this field regardless of the enumeration value source. A similar behavior is implemented for UUIDs and references to external data source tables. This change is not implemented in 8.3.7 compatibility mode. | In a query, if a single system enumeration was retrieved and it was not combined with other types, the GROUP BY operation might not group the values of this field (depending on the enumeration value source). | Eliminated unexpected system behavior. |
| DBMS operations. | For Microsoft SQL Server DMBS, types of table fields that store some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) are changed. New field types are used if no compatibility mode is selected and only after restructuring configuration objects. To perform database table restructuring with modification of field types, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair). This change is not implemented in 8.3.7 compatibility mode. | For Microsoft SQL Server DMBS, table fields that stored some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) had different types. | Better mapping between the stored types and Microsoft SQL Server table field types. |
| DBMS operations. | For all DBMS, the structure of indexes by fields of composite type is modified. This reduces the total number of indexes. Such indexes are built if no compatibility mode is selected and only after restructuring configuration objects. To perform database table restructuring with index update, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair). This change is not implemented in 8.3.7 compatibility mode. | For all DBMS, the structure of indexes by fields of composite type was different. | Reduced number of indexes for tables storing objects with fields of composite types. This increases the performance of operations with these object types. |
| Configuration extensions. | When a background job is executed, all the configuration extensions available in the session that startes the job are also attached in the background job session. This change is not implemented in 8.3.7 compatibility mode. For ConfigurationExtensionsManager object, the ExecuteBackgroundJobWithDatabaseExtensions method is implemented. It duplicates the background job execution procedure implemented in earlier 1C:Enterprise versions. | When a background job was executed, all the configuration extensions available in the infobase were attached in the background job session. | Background job execution environment is closer to the parent session environment. |
| Managed forms. | In the thick and thin clients, when a user starts typing in a cell of a managed form table, the AutoComplete event is fired. This change is not implemented in version 8.3.7 compatibility mode. | In the thick and thin clients, when a user starts typing in a cell of a managed form table, the StartChoice event is fired. | The behavior of the input field in the scenario where a user starts typing in a table cell is uniform with other input scenarios. |
| Technological log. | The recommendation to have no more than 20 <LOG> elements in the logcfg.xml file is added to the documentation. Adding more than 20 <LOG> elements can impact the platform performance. | The recommendation to have no more than 20 <LOG> elements in the logcfg.xml file was absent from the documentation. | The recommendation to avoid inefficient technological log usage scenarios is added to the documentation. |
| Automated testing. | A sections panel that is not displayed in the main window because it contains no items is no longer included in the list of subordinate objects returned by the TestedWindowCommandInterface.GetChildObjects() method. | A sections panel that was not displayed in the main window because it contained no items was included in the list of subordinate objects returned by the TestedWindowCommandInterface.GetChildObjects() method. | Eliminated unexpected system behavior. |
| Automated testing. | The recommendation to use FindObject() and FindObjects() methods to access a required item of a subordinate object list (instead of accessing it by index) is added to the documentation. | The recommendation to use FindObject() and FindObjects() methods to access a required item of a subordinate object list was absent from the documentation. | Improved 1C:Enterprise documentation. |
| Managed forms. | The OnClose event handler and the notification specified in the OnCloseNotifyDescription form property are not called when a managed form is closed using the Close() method called in the OnOpen event handler. This change is not implemented in 8.3.5 compatibility mode. | When a managed form was closed using the Close() method called in the OnOpen event handler:
| Unified client application behavior. |
| Managed forms. | The documentation describes the following platform behavior: when a value is assigned to a variable that is not declared earlier and has a name identical to a property name available in the current context, this can generate a runtime error or a configuration check error. It is recommended that you declare variables with such names using the Var operator to eliminate possible errors. | The documentation did not contain a clear description of this scenario. | The documentation contains a clear description of a possible scenario and provides recommendations for eliminating possible issues. |
| Window-based interface. | The order of elements in the collection returned by the GetWindows() method is changed. The documentation and the Syntax Assistant state that the order of elements in that collection does not follow any specific rule and application algorithms must not rely on that order. | The documentation did not state that the order of items in the collection returned by the GetWindows() method does not follow any specific rule. | The documentation provides more detail about the GetWindows() method. |
| XML and XDTO support. | An attempt to write an invalid qualified element name generates an exception. This change is not implemented in 8.3.6 and 8.3.7 compatibility modes. | An attempt to write an invalid qualified element name did not generate an exception. This might produce an invalid XML file. | Eliminated unexpected system behavior introduced in version 8.3.6. |
| Dynamic lists. | If the current user does not have the View right for a dynamic list key field, an attempt to get dynamic list data generates an access violation error. Information for technical support includes the list of fields that cannot be accessed due to insufficient rights. This change is not implemented in 8.3.7 compatibility mode. | If the current user did not have the View right for dynamic list key fields, this did not affect the list availability. If a form had conditional formatting based on these key fields, it could not be opened. | Eliminated unexpected system behavior. |
| Data exchange. | Unexpected system behavior during the writing of ThisNode exchange plan object, which was found in 1C:Enterprise versions 8.3.8.1606 - 8.3.8.1861, is eliminated. If you migrate to a new 1C:Enterprise version:
If your infobase contains objects that refer to exchange plan items and they can contain references to ThisNode item, it is recommended that you correct the references using the Replace references to incorrect ThisNode records data processor (read more). The data processor can use the result provided by the administration console (recommended) of the exchange plan record deletion marks as an input. It is recommended that you run the cluster administration console (1cv8a) in verification and repair mode, with report generation enabled. Then use the report as an input for the Replace references to incorrect ThisNode records data processor. | 1C:Enterprise versions 8.3.8.1606 - 8.3.8.1861 generated incorrect exchange plan records for ThisNode element. This might result in a variety of errors, such as the following:
1C:Enteprise versions 8.3.7 and earlier did not have this issue. | Eliminated unexpected system behavior. |
| Dynamic lists. | In the source of available data composition system settings for dynamic lists, the following fields are not available for filtering, sorting, or grouping:
The search initiated by typing a search string excludes reference fields that represent aggregate functions of the query language. This change is not implemented in 8.3.7 compatibility mode. | In the source of available data composition settings for dynamic lists, the following fields were available for filtering, sorting, or grouping:
When a filter by any of these fields was applied, a dynamic list might display incorrect data (some data or all data might be missing). An attempt to search in reference fields that represented aggregate functions of the query language initiated by typing a search string might generate errors. If errors we not generated, a dynamic list might display incorrect data (some data or all data might be missing). | The search intiated by typing a search string in dynamic lists is improved. Reduced number of errors that did not have clear descriptions. |
| Dynamic lists. | In 1C:Enterprise mode, in a dynamic list with a custom query and the main table specified, the availability of main table fields and their subordinate fields for filtering does not depend on the availability of these fields in the dynamic list query. If main table fields are absent from the query text, they are added implicitly. If a dynamic list query text includes a field with alias identical to an alias of a main table field, this field is used in the filter, regardless of whether the fields themselves are identical. Fields having multiple paths (in different 1C:Enterprise script languages) are only available in the current 1C:Enterprise script language. This change is not implemented in 8.3.7 and earlier compatibility modes. | Only fields available in a query text and standard main table fields (such as Ref) were available for filtering. A filter that included unavailable fields with names indentical to main table field names might be applied without any errors generated. | For a dynamic list with a custom query and the main table specified, you can include main table fields that are absent from the query text in choice parameters and choice parameter links. |
| Accumulation registers. Accounting registers. | Eliminated unexpected system behavior during the calculation of accumulation register and accounting register totals in scenarios where a dimension list includes a dimension of String type and an index by dimensions includes more that 16 database fields. When you migrate to 1C:Enterprise version 8.3.8 or later, it is recommended that you use the data processor available for download at 1c-dn.com (read more). The data processor determines whether additional actions are required. If they are required, after the migration perform infobase verification and repair with Check logical infobase integrity and Recalculate totals check boxes selected, or use the cluster administration console (1cv8a). The latter option is recommended because it is faster. | Accumulation register and accounting register totals might be calculated incorrectly in scenarios where a dimension list included a dimension of String type and an index by dimensions included more that 16 database fields. | Eliminated unexpected system behavior. |
| Internet-enabled functionality. Web client, web service, and HTTP service publishing tools. | The option to block redirection to potentially harmful sites after completing an OpenID provider operation is implemented. In the default.vrd file, the <returnto> element (subordinate to <provider> element) is implemented. It contains the list of allowed redirection URLs. Note that publishing OpenID providers from Designer does not support <returnto> elements (existing elements of this type are deleted and new ones are not generated). You have to add these elements manually. If you migrate to a new 1C:Enterprise verson, requests to OpenID providers that include the openid.return_to parameter will return HTTP error 400. To eliminate this issue, in the default.vrd file, add the required number of <returnto> elements with available redirection URLs. | The option to affect redirection after completing OpenID provider operations was not provided. | Improved security of OpenID provider operations. |
| System requirements. | The list of supported operating systems and web browsers is changed:
| The list of supported operating systems and web browsers was different:
| 1C:Enterprise requires more secure versions of operating systems of Windows family. |
| Client application. Client application installation. Add-ins. | Since Windows versions 2008 R2 and later stop trusting SHA-1 certificates in January 2017, the following changes are implemented:
| All files included in 1C:Enterprise platform distribution kit were signed with SHA-1. The following recommendations were not available in the add-in development technology documentation (read more):
| The platform executable files are verified on all supported operating systems of Windows family. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Development tools. Mobile application builder. | In the mobile platform, support of in-app billing services is added. This includes Apple In-App Purchase (for iOS) and Google Play In-App Billing (for Android). Support of in-app billing for Windows is not provided. The In-app purchases mobile application permission is implemented. The InAppPurchases, InAppPurchase, InAppPurchaseReceipt, and InAppPurchasesValidation objects are implemented. In the desktop platform, the InAppPurchasesValidation object is implemented. It is intended for testing in-app purchase algorithms. In the mobile platform for developers, a service providing an API similar to Google Play In-App Billing is implemented for Android operating system. It is intended for debugging in-app purchase algorithms. The option to test the full purchase cycle is implemented. This includes the purchase creation and the emulation of some related scenarios. The HTTP service (named PurchaseTest) and the testing tools are provided by the mobile application builder. The mobile application builder supports building mobile applications with in-app purchases. | This feature was not provided. | The option to implement purchases and subscriptions in mobile applications is available. You can create applications with paid features. |
| Development tools. Mobile application builder. | For mobile applications, the option to display ads is implemented. It uses iAd service (for iOS) and AdMob service (for Android). Displaying ads on Windows is not supported. The AdRepresentation object is implemented. Mobile application builder supports applications that display ads. | This feature was not provided. | The option to create mobile applications with advertising monetization model is available. |
| Spreadsheet documents. | Exporting spreadsheet documents fo PDF format is implemented. | This feature was not provided. | More options for data presentation in mobile applications. |
| Data display. | On Android version 4.1 or later, numbers are displayed correctly if the NG parameter of the Format function contains two groups. | On Android version 4.1 or later, numbers were displayed incorrectly if the NG parameter of the Format function contained two groups. | Eliminated unexpected system behavior. |
| File operations. | In the mobile platform, support of asynchronous file operation methods is implemented (this includes global context methods and the File object). | This feature was not supported by the mobile platform. | Improved parallel code implementation for both mobile and desktop platforms. |
| Full-text search. | On the mobile platform, support of FullTextSearchManager.CheckIndex() method is implemented. In the Syntax Assistant, methods of FullTextSearchManager object are marked as available on the mobile platform. | This feature was not supported by the mobile platform. The Syntax Assistant erroneously stated that methods of the FullTextSearchManager object were not available on the mobile platform. | Extended full-text search support on the mobile platform. The Syntax Assistant description is up-to-date. |
| Internet-enabled functionality. | On the mobile platform, when specifying request body as a string for an HTTPRequest or HTTPServiceResponse object, you have the option to include BOM characters to the request or exclude them. On the mobile platform, the ByteOrderMarkUsage system enumeration is implemented. | This feature was not supported by the mobile platform. | Simplified mobile application integration with systems that do not expect BOM characters in HTTP requests. |
| Common objects. | The MobileDeviceApplicationRun object is now available on iOS and Windows platforms. The MobileDeviceApplicationRun.RunningSupported method is implemented to test the availability of this feature. Developers can use this method to determine whether their mobile devices support running external applications. | The MobileDeviceApplicationRun object was not available on iOS and Windows platforms. | The platform behavior related to functionalities that are not available on some mobile devices or operating systems is unified across all platforms.
|
| Managed forms. | In the Syntax Assistant, more information is added to the descriptions of Activate by default and Default button managed form items. The Unfilled selection mode property of managed form input fields is available in mobile platform forms. The Row selection mode property of managed form tables is no longer available in mobile platform forms.
| The information in the Syntax Assistant was outdated. The availability of some properties of managed form input fields did not match the capabilities of the mobile platform. | Designer and Syntax Assistant now match the capabilities of the mobile platform. |
| Mobile application builder. | Data storage structure implemented in the mobile application builder is modified. When the mobile application builder is started for the first time after the update, the data conversion may take significant time. | Data storage structure implemented in the mobile application builder was different. | Data storage structure implemented in the mobile application builder is now more efficient. |
| Development tools. | When a debug server that does not support HTTP is specified in a mobile application, the error message clearly explains the problem: The mobile platform only supports debugging over HTTP. | When a debug server that did not support HTTP was specified in a mobile application, the error message did not clearly explain the problem. | Better problem diagnostics during mobile applicatiobn development. |
| Print tools. | In the mobile platform, the design of the page setup form is changed:
| In the mobile platform, the design of the page setup form was different:
| Improved design of the page setup form. |
| Mobile device-specific features. | On iOS devices, receiving location updates when an application is running in background is not supported. | The option to receive location updates when an application is running in background on iOS devices was not documented. | Clarified the specifics of using mobile applications on iOS devices. |
To migrate data between infobase formats, you can use a .dt file (provided that the target infobase has the required format) or convert the infobase file using cnvdbfl utility. The cnvdbfl utility can change the infobase file page size during the conversion.
If your infobase contains objects that refer to exchange plan items and they can contain references to ThisNode item, it is recommended that you correct the references using the Replace references to incorrect ThisNode records data processor (read more). The data processor can use the result provided by the administration console (recommended) of the exchange plan record deletion marks as an input.
It is recommended that you run the cluster administration console (1cv8a) in verification and repair mode, with report generation enabled. Then use the report as an input for the Replace references to incorrect ThisNode records data processor.
If it is required, after the migration perform infobase verification and repair with Check logical infobase integrity and Recalculate totals check boxes selected, or use the cluster administration console (1cv8a). The latter option is recommended because it is faster.
Version 8.3.7 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.6 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, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4 and 8.3.5. | In version 8.3.7 you can run configurations created in version 8.3.6 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.7 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.6 for working with the infobase even after the transition to version 8.3.7. 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). |
| ZIP archive operations. | The ZipFileWriter and ZipFileReader objects are revised to improve stability during intense simultaneous work of a large number of users and to eliminate the issue with national characters in file names. ZIP archive support is implemented using the zipArchive library. The ZIPCompressionMethod.BZIP2 system enumeration value is implemented. | The ZipFileWriter and ZipFileReader objects had an issue related to intense simultaneous work of a large number of users, and an issue related to national characters in file names. The Info-ZIP library was used for ZIP archive support. The BZIP2 compression method was not supported. | Improved support of ZIP archives (including the support of national characters in file names). You can use the prevalent archive file format on Linux. |
| Development tools. | Configuration support settings management is available in Designer batch mode. The /ManageCfgSupport command-line option is implemented for Designer batch mode. | This feature was not provided. Configuration support settings management was only available in the interactive mode. | Simplified automated building and testing of applied solutions. |
| Internet-enabled functionality. Web services and HTTP services. | You can use OS authentication for Internet operations and web services. When a WS-reference is created in Designer, the OS authentication option cannot be disabled. When the list of infobases is retrieved using a web service, OS authentication is used, unless the URL contains authentication data. OS authentication is not supported on Linux. For the InternetProxy object, the option to enable or disable OS authentication for each protocol is implemented. This change is not implemented in 8.3.6 compatibility mode. The UseOSAuthentication parameter is implemented for constructors of the following objects: HTTPConnection, WSDefinitions, and WSProxy. The UseOSAuthentication property is implemented for the following objects: HTTPConnection and WSProxy. For the WSReferenceManager.CreateWSProxy() method, the UseOSAuthentication option is implemented. For the InternetProxy.Set() method, the UseOSAuthentication option is implemented. For the InternetProxy object, the UseOSAuthentication() method is implemented. | OS authentication was not implemented for Internet operations and web services. OS authentication was never used for retrieving a list of infobases using a web service. For the InternetProxy object, basic authentication was used, provided that the user name and password were set. | Extended capabilities for web service operations, Internet operations, and retrieving the list of infobases in corporate environments. |
| Web services and HTTP services. | You can use a web service whose address is different from the address specified in a WSDL file imported to the applied solution (a WS-reference object). For the WSProxy object constructor, the Location parameter is implemented. For the WSReferenceManager.CreateWSProxy() method, the Location parameter is implemented. | This feature was not provided. A web service could be used only if it was located at the address specified in a WSDL file imported to the applied solution (a WS reference configuration object). | New usage options for Web services in scenarios where a web service has a fixed interface but can be located at different addresses in the Internet. For example, you can use a web service of some broadly used applied solution. |
| JSON support. XML and XDTO support. | XDTO objects can be serialized to JSON. | This feature was not provided. Only streaming API and object model were supported for JSON. | Simplified usage of JSON format for exchange between various 1C:Enterprise-based systems. |
| JSON support. | When data is written in JSON format, slash marks (/) can be escaped. For the JSONWriterSettings constructor, the EscapeSlash parameter is implemented. For the JSONWriterSettings object, the EscapeSlash property is implemented. The EscapeSlash property is used by the JSONWriter.WriteValue() method. | The option to enable or disable escape of slash marks in JSON operations was not available. | Better compatibility with external systems that use exchange in JSON format. |
| Localization. | The NumberInWords() and PeriodPresentation() global context methods support the Azerbaijani language. The language code is az. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant. | The NumberInWords() and PeriodPresentation() global context methods did not support the Azerbaijani language. | Simplified implementation of data presentation for Azerbaijani-speaking users. |
| Localization. | The NumberInWords() and PeriodPresentation() global context methods support the Turkish language. The language code is tr. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant. | The NumberInWords() and PeriodPresentation() global context methods did not support the Turkish language. | Simplified implementation of data presentation for Turkish-speaking users. |
| Localization. | The NumberInWords() and PeriodPresentation() global context methods support the Hungarian language. The language code is hu. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant. | The NumberInWords() and PeriodPresentation() global context methods did not support the Hungarian language. | Simplified implementation of data presentation for Hungarian-speaking users. |
| Spreadsheet documents. | When a spreadsheet document is exported to XLS (Microsoft Excel 97-2003) format, Microsoft Office OpenXML (Microsoft Excel 2007- 2010) format, or ODS (OpenDocument Spreadsheet) format, the following print settings are exported to the resulting file:
This change is not implemented in 8.3.6 compatibility mode. | When a spreadsheet document was exported to XLS (Microsoft Excel 97-2003) format, Microsoft Office OpenXML (Microsoft Excel 2007- 2010) format, or ODS (OpenDocument Spreadsheet) format, its print settings were not exported. | More accurate export of spreadsheet documents to popular spreadsheet document formats. |
| Configuration extensions. | In configuration extensions, you can create WS references, XDTO packages, web services, and HTTP services. You can publish Internet services belonging to configuration extensions to web servers. In the default.vrd file, the publishExtensionsByDefault attribute is implemented for ws and httpServices elements. | This feature was not provided. | New functionality introduced for configuration extensions. |
| OData interface. | You can use independent information registers that do not have dimensions in the standard OData interface. The SurrogateKey property is implemented. | This feature was not provided. | The 1C:Enterprise object implementation better complies with the OData standard. |
| Background and scheduled jobs. | You can quickly determine whether the current session is a background job session. The GetCurrentInfoBaseSession() global context method is implemented. The InfoBaseSession.GetBackgroundJob() method is implemented. | This feature was not provided. The only way to determine the session type was getting all infobase sessions and iterating through them. | Optimized procedure for determining whether the current session is a background job session. This is handy in such scenarios as dividing initialization scripts for client applications and background jobs. |
| DBMS operations. | Dumping an infobase to a .dt file is interrupted if any issues related to the internal infobase structure are encountered. | Dumping an infobase to a .dt file did not include a verification of the internal infobase structure. | Reduced chance of obtaining a .dt file that cannot be loaded. |
| Common objects. | The option to read and write data in a scenario where synchronous calls are not allowed is implemented for the following objects: TextDocument, SpreadsheetDocument, FormattedDocument, GraphicalSchema, and RepresentableDocumentBatch (write operation only). The BeginWriting() method is implemented for the following objects: TextDocument, SpreadsheetDocument, FormattedDocument, and GraphicalSchema. The BeginReading() method is implemented for the following objects: TextDocument and GraphicalSchema. The RepresentableDocumentBatch.BeginWritingFileForPrinting method is implemented. | These features were not provided. | The missing functionality is implemented for compatibility with the recent Google Chrome changes. |
| Cryptography support. | For the Issuer and Subject properties of the CryptoCertificate object the option to get access to all certificate fields that describe issuer and subject is implemented. For the Issuer and Subject properties of the CryptoCertificate object the Street field is implemented. Each of the Issuer and Subject structure fields of the CryptoCertificate object is accessible by:
| The Issuer and Subject properties of the CryptoCertificate object did not provide access to all certificate fields. | All certificate fields can be accessed, even those that are present due to regulator requirements. |
| DBMS operations. | When the platform attempts to build an index by more than 3 string fields in Oracle DBMS, it automatically creates V81C_INDEX_BIG tablespace. | When the platform attempted to build an index by more than 3 string fields in Oracle DBMS, if V81C_INDEX_BIG tablespace was missing, an error was generated. Creating the tablespace manually eliminated the error. | The need to create the tablespace manualy is eliminated. |
| Configuration extensions. Predefined data. | The option to adopt predefined data items is implemented for configuration extensions. This makes the following operations available: check extensions for availability of predefined data items, check whether extension exchange plan content and object registration rules include predefined data items, and use extension predefined items in the query builder. | This feature was not provided. | Expanded configuration extension functionality. |
| Development tools. | The option to dump configurations to hierarchical file structures, as well as restore them from such file structures, is implemented. Name length for new configuration objects is limited by 80 characters. Existing configuration objects can have names longer than 80 characters until you attempt to edit their names. 1C:Enterprise script modules are dumped to .bsl files. In the dump configuration files dialog box you can select the dump format: flat or hierarchical. The Format parameter is implemented for /DumpConfigToFiles Designer batch mode command-line option. The new parameter describes the dump format. By default configurations are dumped to hierarchical file structures.
| Configurations were always dumped to flat file structures. No length restrictions were applied to configuration object names. 1C:Enterprise script modules were dumped to .txt files. | Chance of configuration dump procedure being terminated due to length of the output file path and name exceeding the file system limits is significantly reduced (file names are derived from configuration object names). |
| Development tools. | A configuration can be partially restored from files. The following operations are available: adding, modifying, deleting, and renaming configuration objects and modifying some properties of configuration objects (such as their modules or help topics). You can simultaneously load a configuration from files and update database configuration. For the /LoadConfigFromFiles Designer batch mode command-line option, the following parameters are implemented: -files (files to load) and -listfile (file containing a list of files to load). In the technological log, the CONFLOADFROMFILES event is implemented. | This feature was not provided. Only restoring the entire configuration from files was available. | Better performance of configuration updates in scenarios where a configuration is stored in an external system. |
| Development tools. | New debug option is available: debugging over HTTP. Developers can select this option in Designer. The dialog box with automatic debug item attachment settings is refactored. Debug server (dbgs) is implemented, it can be started from the command line, and also as an operating system service. The new debug protocol is not supported on Linux servers in the scenario where 1C:Enterprise starts automatically during operating system startup. The following command-line options are implemented for the server agent (ragent): /debug, /debugServerAddr, /debugServerPort, and /debugServerPwd. For the client application the following command-line option is implemented: /debug. In default.vrd file, for the <debug> element, the protocol attribute is implemented. In comcntrcfg.xml file, for the <config> element, the protocol attribute is implemented. This option is implemented as beta version. | A single debug option was available. | You can debug applied solutions when HTTP is the only available connection protocol. This expands Debugger functionality. |
| Localization. | The option to localize only a part of 1C:Enterprise platform interface required for a specific applied solution is implemented. Localization tools that support this option are available upon request from 1C Company at MAIL:int@1c.com. This option has the following limitations:
| Only the full localization option was available. Localizations were always delivered as part of the platform distribution kit. | The option to localize the platform interface for specific applied solutions or specific delpoyments is implemented. This option is in demand by users whose native languages are not included in the list of platform localization languages. |
| Development tools. | Designer help includes the list of executable files of predefined external tools used for comparing and merging modules. It is recommended that you specify these names in the settings for comparing and merging modules with external tools. | Designer help did not include executable file names of predefined external tools used for comparing and merging modules. | Improved Designer help. |
| Dumping/loading configurations to files. | Versioning is implemented for the format of dumping configurations to files. 1C:Enterprise 8.3.6 has dump format version 1.0, and 1C:Enteprise version 8.3.7 has dump format version 2.0. If the dump files do not include a version number, they are treated as version 1.0-compliant. Files are always dumped in the format that matches the 1C:Enterprise platform version. A configuration can be restored from files only if the version of the files is earlier than or equal to the version supported by the 1C:Enterprise platform. | Versioning was not available for the format of dumping configurations to files. | Some issues related to the incompatibility of dump files generated by different 1C:Enterprise versions are eliminated. |
| Dumping/loading configurations to files. | The method of dumping the Parameter property of the Button managed form item to files is changed. If the Parameter value references a configuration object, the full name of that configuration object is dumped to files. | The Parameter property of the Button managed form item was dumped as a UUID of the configuration object type if the Parameter property referenced a configuration object. | Eliminated the configuration dump format inconsistency. |
| Administration tools. | Applied solution license validity check is implemented at 1C:Enterprise platform level. The check is performed for applied solutions running in file mode, and it is also performed on the server for 1C:Enterprise 8.3 Server MINI. The license validity check is not performed for applied solutions that use the base version of 1C:Enterprise. The check involves an Internet connection to the Update Validation Center. The result of the check is displayed in the About 1C:Enterprise dialog box. The Designer interface includes new commands related to this functionality. The following global context methods are implemented: GetConfigurationID, GetLicensingClientName, GetLicensingClientAdditionalParameter, SetLicensingClientParameters, AttachLicensingClientParametersRequestHandler, and DetachLicensingClientParametersRequestHandler. For the conf.cfg configuration file, the LicConfigDebugTimeouts parameter is implemented. The parameter is used to reduce the check interval. The implementations of this functionality are subject to future announcement. | This feature was not provided. | The option to perform a license validity check after updating an applied solution is implemented. |
| DBMS operations. | Support of Oracle Database version 12.1.0.2 (Linux) is implemented. | This Oracle Database version was not supported. | Extended list of supported Oracle Database versions. |
| Designer. Client application. Cross-platform architecture. System requirements. | The client application for OS X 10.8 or later is available (64-bit version only). It supports the following features:
Running 1C:Enterprise server on OS X is not supported. The limitations of the OS X client application are provided in the documentation. Installation and simultaneous work of multiple 1C:Enteprise versions is supported. This option is implemented as beta version. | Infobase access via a web client was available on OS X. | You can develop applied solutions and run client applications on OS X. |
| System requirements. | Astra Linux Special Edition 1.4 is supported. | This release was not supported. | New Linux release is supported. |
| Add-ins. | The English description of the add-in development technology is provided as an HTML document. This document is available for download for each platform version as a part of 1C:Enterprise platform 8.3 Add-in technology archive. | The description of the add-in development technology available for download as a part of 1C:Enterprise was only provided in Russian. | Better accessibility of add-in development documentation. |
| ZIP archive operations. | File names in ZIP archives generated by 1C:Enterprise have both UTF-8 encoding and the current operating system encoding (if is not UTF-8). The ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, read ZIP archives correctly even when the file names inside the archives contain non-English characters. Note that the built-in decompression program for OS X displays file names in such archives incorrectly. | File names in ZIP archives generated by 1C:Enterprise had UTF-8 encoding only. The ZipFileReader object in 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs in Windows XP/2003/2008/7, displayed file names with non-English characters inside ZIP archives incorrectly. | The ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, read ZIP archives correctly even when the file names inside the archives contain non-English characters. Note that the built-in decompression program for OS X displays file names in such archives incorrectly. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Interface. | In the Taxi interface, when an item is deleted from the Favorites list, a modal confirmation dialog box is no longer displayed. After the deletion, a link for restoring the deleted item is displayed in the Favorites panel. | In the Taxi interface, when an item was deleted from the Favorites list, a modal confirmation dialog box was displayed. | The Favorites pane functionality is fully supported in web browsers that do not support modal dialog boxes. |
| Interface. | In the Taxi interface, you can pin forms in the main window work area (so that a form is always available). You can also combine two forms in order to have them always displayed together when any of the two forms is opened. In the system menu, context menu of the opened windows panel, and form title context menu, the corresponding commands are implemented. | This feature was not provided. | Improved platform usability. For example, users have the option to compare two instances of a single report featuring different periods. |
| Data display. | Web service authentication error messages no longer contain HTML text returned by the web server, at no cost to message information value. | Web service authentication error messages contained HTML text returned by the web server. | All information that was not user-friendly is removed from web service authentication error messages |
| Interface. | Replacement of style elements with actual fonts and colors is improved in some scenarios. | In some scenarios, replacement of style elements with actual fonts and colors was performed incorrectly. | Eliminated unexpected system behavior. |
| Client application. | The client application help includes the description of the keyboard shortcut Ctrl+Shift+H, which opens the history panel. | Description of this shortcut was not available in the client application help. | Client application help is up-tp-date. |
| Web client. | In Google Chrome web browser, access to clipboard using context menu commands is implemented (in addition to the previously available keyboard shortcuts). This options requires installing a browser extension. The web client propmts the user to install the extension first time they attempt to access the clipboard using context menu commands. If the extension is not installed, the clipboard can be only accessed using keyboard shortcuts. | In Google Chrome web browser, the clipboard could only be accessed using keyboard shortcuts. Clipboard access using context menu commands was not supported. | Improved web client usability in Google Chrome. |
| Web client. | New version of the browser extension for Mozilla Firefox is available. The extension only supports asynchronous operations. The synchronous methods are no longer supported. | Another version of browser extension for Mozilla Firefox was available. It supported synchronous operations. | Support of Mozilla Firefox versions 40 and later, which do not support synchronous operations (just like Google Chrome versions 45 and later), is implemented. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Development tools. | The performance of the following Designer operations is improved:
| The performance of some Designer operations was insufficient. | Streamlined execution of some Designer operations. |
| Geographical schemas. | The following geographical schema operations are optimized:
| The performance of some geographical schema operations was insufficient. | Improved usability of geographical schemas. |
| Full-text search. | Improved performance of full-text search and of building the full-text search index. | Insufficient performance of full-text search and of building the full-text search index. | Improved performance of full-text search and of building the full-text search index. The improvement is noticeable if the infobase contains indexed objects with a large number of words. |
| Full-text search. Dynamic lists. | In dynamic lists, the performance of the search initiated from the search string is improved in the following scenario: the full-text search is enabled for the dynamic list main table and filters with Equal to comparison type are applied to the main table fields. | In dynamic lists, the performance of the search initiated from the search string was insufficient. | In dynamic lists, improved performance of the search initiated from the search string. |
| Queries. | When a query that accesses only tabular section data is executed, the retrieved table is not joined to the parent object table. | When a query that accessed only tabular section data was executed, the retrieved table was automatically joined to the parent object table. | Eliminated unexpected system behavior. |
| DBMS operations. | Improved performance of reading objects of the following types from DBMS: DocumentObject, CatalogObject, BusinessProcessObject, TaskObject, ChartOfCalculationTypesObject, ChartOfCharacteristicTypesObject, ExchangePlanObject, and ChartOfAccountsObject. Reading any of these objects is followed by implicit transaction creation only if the object has tabular sections and "dirty read" outside of transactions is allowed in the DBMS. | Reading objects of the following types from the DBMS was followed by implicit transaction creation if the object had tabular sections: DocumentObject, CatalogObject, BusinessProcessObject, TaskObject, ChartOfCalculationTypesObject, ChartOfCharacteristicTypesObject, ExchangePlanObject, and ChartOfAccountsObject. | The following values are reduced:
|
| Managed forms. | Improved performance of managed form conditional appearance. Faster opening of managed forms with a large number of conditional appearance items. | Insufficient performance of managed form conditional appearance. | Improved performance of opening managed forms, especially for file mode infobases and on low-performance computers. |
| Predefined data. | Improved performance of retrieving predefined data using the PredefinedValue() method. | Insufficient performance of retrieving predefined data using the PredefinedValue() method. | Improved performance of processing predefined data. |
| Development tools. | The configuration database update time is reduced for configurations that include a large number of roles, provided that the update does not require database restructuring. | The configuration database update required significant time for configurations that included a large number of roles, provided that the update did not require database restructuring. | Reduced database configuration update time. |
| Managed forms. 1C:Enterprise script. | The performance of opening managed forms is improved in the thin client and web client. | The performance of opening managed forms in the thin client and web client was insufficient. | Improved platform performance. |
| Platform algorithms. | Internal caching algorithms of 1C:Enterprise are optimized. This improves the performance of many 1C:Enterprise features, including the following:
| System performance was suboptimal. | Improved platform performance, especially for infobases running in the file mode and on computers with limited RAM (less than 4 GB). |
| Data access restrictions. | Query execution is optimized for users that do not have full rights in configurations that use access restrictions and have a large number of roles. The query execution time is not significantly affected by the number of roles assigned to a user. | Query execution time was insufficient for users that did not have full rights in configurations that used access restrictions. The query execution time was significantly affected by the number of roles assigned to a user. | Improved performance of configurations with a large number of roles (including form opening performance). |
| Dynamic lists. Full-text search. | When a dynamic list is searched from a search box by fields that do not belong to the main dynamic list table, full-text search by source objects of the fields is performed first. Fields of objects where nothing is found by the full-text search are excluded from further search. | When a dynamic list was searched from a search box, additional conditions were applied to all fields displayed in the table linked to the dynamic list. | Improved performance of search in dynamic lists in some usage scenarios. |
| Queries. | In the query language, expressions that include both comparison operators and CASE operators that return only constant values are optimized. The optimization simplifies expressions or their parts. | In the query language, optimization was not available for expressions that included both comparison operators and CASE operators that returned only constant values. | Improved query performance in some scenarios. |
| Full-text search. | The performance of the input by string feature is improved. The full-text search index data structure is modified. Full-text search index is created in the new format. To convert the index to the new format, clear the index, ensure that the Compatibility mode configuration property is set to Do not use, and then generate the index. The <INPUTBYSTRING> technological log event is implemented, it is used for monitoring events related to input by string. This change is not implemented in 8.3.6 compatibility mode. | The performance of the input by string feature was insufficient. Full-text search index had a different format. | Improved performance of the input by string feature, which, in turn, improves the usability of all platform objects that use this feature. |
| Automated testing. | In the web client running in the testing client mode, the performance of test scenario commands is improved. | In the web client running in the testing client mode, the performance of test scenario commands was insufficient. | Improved performance of automated testing in the web client. |
| Data exchange. Common attributes / Data separation. | Improved performance of initial infobase image creation in scenarios where the exchange plan used to create the initial image includes a register that is included in independent separator content (provided that separator is not used in the current session). | The performance of initial infobase image creation in scenarios where the exchange plan used to create the initial image included a register that was included in independent separator content (provided that separator was not used in the current session) was insufficient. | Improved performance of initial image creation in some scenarios. |
| Common objects. | The algorithms of the following methods are optimized: QuerySchemaAvailableTables.Find(), QuerySchemaSources.Add(), and QuerySchemaTableParameters.Count(). | The performance of QuerySchemaAvailableTables.Find(), QuerySchemaSources.Add(), and QuerySchemaTableParameters.Count() methods was insufficient. | Improved performance of query schema operations in 1C:Enterprise script. |
| Development tools. | Operations in the configuration command interface editor form are optimized for scenarios with a large number of roles. The performance of moving table rows is improved. | The performance of operations in the configuration command interface editor form was insufficient in scenarios with a large number of roles. | Improved usability for application developers that edit the command interface of configurations with a large number of roles. |
| DBMS operations. Calculation registers. | Both in PostgreSQL and IBM DB2, in scenarios where large calculation register record sets are deleted, deletion of records storing actual action periods is performed faster. This change is not implemented in 8.3.6 compatibility mode. | Both in PostgreSQL and IBM DB2, in scenarios where large calculation register record sets were deleted, deletion of records storing actual action periods was impaired. | Both in PostgreSQL and IBM DB2, optimized deletion of large calculation register record sets. |
| Spreadsheet documents. | The performance of setting the size and position of spreadsheet document pictures at 1C:Enterprise server side is improved. | The performance of setting the size and position of spreadsheet document pictures at 1C:Enterprise server side was insufficient. | Improved performance of spreadsheet document generation in scenarios where the size and position of spreadsheet document pictures are set from 1C:Enterprise script. |
| Managed forms. Web client. Server clusters. | The performance of opening managed forms is improved in the following scenario: the web client is running in client/server mode and the server cluster is deployed on a Linux computer. | The performance of opening managed forms was insufficient in the following scenario: the web client was running in client/server mode and the server cluster was deployed on a Linux computer. | Improved web client performance for Linux server clusters. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Managed forms. | The Create menu (in a document journal form) does not contain document types disabled by functional options. The Show in list menu (in a document form) does not contain list forms disabled by functional options. | The Create menu (in a document journal form) contained document types disabled by functional options. The Show in list menu (in a document form) contained list forms disabled by functional options. | Eliminated unexpected system behavior. |
| Server clusters. | In client/server mode, dynamic updates do not require restarting Designer. When a scheduled job is started or completed in an infobase, this does not affect the performance of other infobases in the cluster. Improved system reliability in the following scenarios:
| In client/server mode, dynamic updates required restarting Designer. When a scheduled job was started or completed in an infobase, this affected the performance of other infobases in the cluster. The system reliability was insufficient in several scenarios. | Increased stability and reliability of server clusters. |
| Predefined data. | During infobase verification and repair operations, the platform checks whether the main table of an object (catalog, chart of characteristic types, chart of calculation types, or chart of accounts) contains no more than 1 record for each predefined item in each area. If a duplicate item is found, a predefined item mark is removed from it and a deletion mark is set instead. | This feature was not provided. | Improved infobase verification and repair operation. |
| External data sources. | Table fields and cube table dimension fields of external data sources can have NULL values only if the NULL allowed check box is selected in the object settings. For external data source cube table fields NULL values are always allowed. This change is not implemented in 8.3.6 compatibility mode. | All external data source table fields could have NULL values. | Improved performance of sorting dynamic lists by fields whose ability to store NULL values is specified correctly. |
| Data composition system. | In a data composition schema, if a query with a nested query is used in a data set, selected fields of the nested query are available for filtering, provided that these fields are not used in aggregate functions of the parent query. This change is not implemented in 8.3.6 compatibility mode. | In a data composition schema, if a query with a nested query was used in a data set, selected fields of the nested query were not available for filtering (except virtual table parameters). | In a data composition schema, the generation of a resulting query is optimized for scenarios that utilize nested queries with filters by nested query fields. |
| Infobase verification and repair. Common attributes / Data separation. | Infobase verification and repair can detect and repair the following issue: objects linked to some tabular section rows are absent from the infobase. The search and restoration are performed taking into account all independent separators that include the missing objects. | This feature was not provided. | Improved infobase verification and repair procedure. |
| Dynamic lists. | In dynamic lists, search by reference fields with custom presentations is performed by fields that form the presentation. Such fields are obtained with the help of the PresentationFieldsGetProcessing() handler. | In dynamic lists, search by reference type fields with custom presentation was performed only by fields used in default presentation. | Improved search by reference fields with custom presentations in dynamic lists. |
| Managed forms. Command interface. | In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command is executed from the navigation panel, the Uniqueness command handler parameter is assigned a BOOLEAN value (TRUE if the command is executed through the Open new item context menu command, otherwise FALSE). In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command is executed from a form navigation panel, the uniqueness of the form being opened is not set. This change is not implemented in 8.3.6 compatibility mode and in the Forms in separate windows mode. | In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was set to the main window identifier. In the web client, in the Taxi interface or in the Forms in tabs mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was assigned a BOOLEAN value. In the thin and web clients, in the Taxi interface or in the Forms in tabs mode, when a command was executed from a form navigation panel, the Uniqueness command handler parameter was set to the main window identifier. In the Forms in separate windows mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was set to the main window identifier. In the Forms in separate windows mode, when a command was executed from a form navigation panel, the Uniqueness command handler parameter was set to the main window identifier. | Unified platform behavior in various client applications and usage scenarios. |
| Server clusters. | For the ragent, rmngr, and rphost commands, which start server cluster processes, the pingPeriod and pingTimeout command-line options are implemented. In default.vrd file, for the pool item, the serverPingPeriod and serverPingTimeout attributes are implemented. In the web server publishing dialog box, the Check period and Check timeout properties are implemented. In the technological log, for the CONN event, the list of logged events related to the detection of connection losses between processes in a single cluster is extended. | A less-efficient algorithm was used for detection of connection losses in a cluster. | Improved server cluster stability, faster and more efficient detection of connection losses in a cluster. |
| Full-text search. Dynamic lists. Server clusters. | When a form that contains a dynamic list is closed, the server cluster is notified about that in order to cancel the background job that performs search in the list (if it was initiated earlier). | When a form that contained a dynamic list was closed, the server cluster was not notified about that. If a background job that performed search in the list was running at the moment of closing, it was not interrupted once the form was closed. Instead, it continued running till the completion. | Eliminated unexpected system behavior. Reduced server cluster load in some scenarios. |
| Development tools. | In Designer, the П shortcut is removed from the Move up and Move down commands in the Russian interface (it was assigned to both commands previously). Other keyboard shortcuts for these commands are still in effect, as well as the actions associated with these commands. | In Designer, the П keyboard shortcut was assigned to both Move up and Move down commands in the Russian interface. | Eliminated unexpected system behavior. |
| Data composition system. | Presentations of filter items displayed in reports is changed. If a report includes a filter item from the user settings and the user settings item presentation is specified for this filter item, the presentation is used for displaying the filter in the resulting report. This change does not affect reports that include filter items that do not belong to user settings. It also does not affect filter items that do not have user settings item presentations specified. This change is not implemented in 8.3.6 compatibility mode. | If a report included a filter item whose presentation was specified, only this presentation was displayed in the report. Otherwise the filter item was displayed in the following format: <Left value> <Comparison type> <Right value>. | Filter list presentations in reports are easier to read. |
| Spreadsheet documents. | The spreadsheet document behavior is modified in scenarios where a rectangular area of cells is inserted or deleted (interactively or using 1C:Enterprise script). If an area being moved overlaps an area of merged cells and the merged area is not fully included into the area being moved, the merging is removed and the cells previously included in the merged area inherit the formatting of the merged area. This change is not implemented in 8.3.6 compatibility mode. | When a rectangular area of cells was inserted or deleted, merged cells that partially overlapped the area being moved were not modified. | Eliminated unexpected spreadsheet document behavior. |
| DBMS operations. | In Oracle Database DBMS an index created for a temporary table that includes more than three dimensions of String type, each of them containing at least 60 characters, might be truncated (with the last fields discarded) if the index key length does not fit the block size. | In Oracle Database DBMS an index created for a temporary table that included more than three dimensions of String type resulted in unexpected system shutdown due to DBMS error. | Eliminated unexpected system behavior. Improved system reliability. |
| Administration tools. | The following requirement is described in the documentation: when an application is updated over HTTP or HTTPS, all .mst, .msi, and .cab files in the distribution kit .zip archive must have a digital signature. The signature is verified on the computer where the application is installed. | Thew documentation did not include the file digital signature requirement. | Documentation issue corrected. |
| Development tools. | Setting a correspondence between Debugger and a debug item no longer requires the exact match of infobase connection strings in Debugger and in the debug item. The option to edit a variable value during debugging is implemented. The option to view all local variables of a method being debugged in a dedicated window is implemented. The state of folders (expanded or collapsed) in the immediate window and in the local varibles window is preserved when switching to the next debug step. If you use the Break command (Shift+F5) to close an application being debugged, the modal exit confirmation dialog box is never displayed. | Setting a correspondence between Debugger and a debug item required the exact match of infobase connection strings in Debugger and in the debug item. The option to edit a variable value during debugging was not provided. The option to view all local variables of a method being debugged in a dedicated window was not provided. The state of folders (expanded or collapsed) in the immediate window and in the local varibles window was not preserved when switching to the next debug step. Using the Break command (Shift+F5) to close an application being debugged sometimes opened the modal exit confirmation dialog box. | Expanded debug functionality. |
| Data composition system. | The overall columns of a data composition system table display the titles of grouped resource fields if grouping templates are specified for the table columns. This change is not implemented in 8.3.6 compatibility mode. | The overall columns in the data composition system table header did not display the titles of grouped resource fields if grouping templates were specified for the table columns. | Eliminated unexpected system behavior. |
| Common objects. Development tools. | The Language code property of the Language configuration object cannot contain the following characters: #, *, |, \, :, ", <, >, ?, /. | The Language code property of the Language configuration object could not contain the # character. | Chance of configuration dump procedure being terminated due to incorrect generation of the file name (which is based on the language code) is reduced. |
| Command interface. | In the thin client, in the Forms in separate windows mode, if a navigation command handler includes the GotoURL() global context method with a navigation point reference parameter, after the command execution the current navigation point is set to this command.
| In the thin client, in the Forms in separate windows mode, if a navigation command handler included the GotoURL() global context method with a navigation point reference parameter, after the command execution the current navigation point was set to the point passed in the parameter. | Eliminated unexpected system behavior. |
| Managed forms. | In the thin client, the Window property of managed form object is read-only. This change is not implemented in 8.3.6 compatibility mode. | In the thin client, the Window property of managed form object was available for both reading and writing. In the web client, the Window property of managed form object was read-only. | Unified system behavior in different client applications. |
| Information registers. | For periodic information registers with resources or attributes indexed, the structure of the index of the slice first/last table is changed. If the information register periodicity is set to By recorder position, register dimensions are added to the index. If the periodicity has any other value, the index is not unique. When the Compatibility mode configuration property is set to None, the platform performs the restructuring of the slice tables. This change is not implemented in 8.3.6 compatibility mode. | For periodic information registers with periodicity set to By recorder position, register dimensions were not included in the index of slice first/last tables. For periodic information registers with other periodicity values, the index of slice tables was unique. | An nonunique index issue is eliminated. |
| Predefined data. | The configuration check that is always performed before database configuration update includes a check for duplicate predefined item names. No duplicate predefined item names are allowed for any configuration object. If duplicate predefined items are found, this is reported to the message window but does not prevent the configuration update. This change is not implemented in 8.3.6 compatibility mode. | The configuration check that was always performed before database configuration update included a check for duplicate predefined item names, however, duplicate names did not prevent the database configuration from updating. | Improved reliability of configuration updates for configurations that include predefined data. |
| Technological log. | Logging of debugger exceptions in the technological log is implemented. The <EXCP> event is used for that logging. | Logging of debugger exceptions was not performed. | Better debugger error diagnostics. |
| Administration tools. | The infobase verification and repair procedure no longer includes a check for spaces at the end of attribute values that have String type and variable length. | The infobase verification and repair procedure included a check for spaces at the end of attribute values that had String type and variable length. | Eliminated unexpected system behavior. |
| Regional settings. | For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ, and 87-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers. | The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ. and 87-FZ. | The time offset changes introduced by the new law are implemented. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Internet-enabled functionality. | The NSSSecureConnection object and NSS certificates cannot be accessed from 1C:Enterprise script. This change is not implemented in 8.3.6 compatibility mode. | 1C:Enterprise system supported NSS certificates. | Future platform versions will not support NSS certificates. |
| Common objects. | In the thin client, the ValueStorage.Get() method raises an exception. This change is not implemented in 8.3.6 compatibility mode. | In the thin client, the ValueStorage.Get() method did not raise an exception and returned the Undefined value instead. Running this method in the web client raised an exception. | Uniform system behavior across multiple client applications. |
| Interface. Managed forms. | The choice history generation rules for managed form text boxes are modified. In particular, the frequency of history item usage is taken into account. The history consists of up to 7 items, which include both frequently used and last used values. The history generation rules are described in detail in the documentation. The system storage of managed form text box choice history stores a value of the ChoiceHistorySettings type. This change is not implemented in 8.3.6 compatibility mode. | The choice history generation rules for managed form text boxes were different. The history stored 5 last values. The system storage of managed form text box choice history stored a value of the Array type. | Improved usability of managed form text box choice history. |
| Managed forms. | New algorithm for automatic arrangement of managed form items is implemented. As a result, item positioning is improved, new item placement options are added, changing some item properties on the client does not require a server call (this includes expanding or collapsing groups and showing or hiding form item addition extension for view status), rules for automatic generation of form separators are modified, and more. In many cases toggling form item visibility no longer requires a server call. Detailed description of this feature is provided in the documentation. In the managed form editor, quick preview of a form with specific screen resolution and specific screen orientation is available. For the ChildFormItemsGroup system enumeration, the HorizontalIfPossible value is implemented. The AutoMaxWidth, MaxWidth, AutoMaxHeight, and MaxHeight properties are implemented for the following objects: managed form field extension for a label field, text box, picture field, spreadsheet document field, text document field, formatted document field, calendar field, progress bar field, track bar field, chart field, Gantt chart field, dendrogram field, geographical schema field, HTML document field, graphical schema field, period field, planner field, and for managed form items of table, decoration, and button types. For managed form items of form, group, and page types the following properties are implemented: HorizontalSpacing, VerticalSpacing, ItemsAndTitlesAlign, ChildItemsHorizontalAlign, and ChildItemsVerticalAlign. For managed form fields of field, table, decoration, group, button, and addition types, the HorizontalAlignInGroup and VerticalAlignInGroup properties are implemented. For managed form item addition extensions for search string, search control, and view status, the AutoMaxWidth and MaxWidth properties are implemented. For managed form groups, the ThroughAlign property is implemented. For the VerticalFormScroll system enumeration, the UseWithoutStretch value is implemented. For managed form group extension for a usual group, the United property is implemented. For managed form group extension for a page, the VerticalScrollOnReduceSize property is implemented. This change is not implemented in 8.3.6 compatibility mode. The HorizontalStretch and VerticalStretch properties are implemented for the following objects: managed form extensions for graphical schema field and HTML document field, and managed form buttons. For managed form item addition extension for search control, the HorizontalStretch property is implemented. The ChildFormItemsWidth property of form, page, and usual group objects is obsolete and only supported in version 8.3.6 compatibility mode. In configurations that do not use compatibility mode, this property is ignored. | A different algorithm was used for arranging managed form items. | In managed forms, automatic item arrangement is revised. New arrangement options are available. Several known managed form issues are eliminated. |
| Web services and HTTP services. | If a configuration includes HTTP services, saving a configuration with compatibility mode lower than Version 8.3.5 is not allowed. | Saving configurations was performed without checking the correspondence between configuration compatibility mode and the availability of HTTP services in the configuration. | Eliminated unexpected system behavior. |
| Common objects. | Synchronous call usage mode for extensions and add-ins configuration property value is taken into account by the following methods:
| The Synchronous call usage mode for extensions and add-ins configuration property was ignored by the listed methods. | Eliminated unexpected system behavior. |
| Server cluster. | The following background job names are used for specifying requirements of functionality purposes:
This change is not implemented in 8.3.6 compatibility mode. | The following background job names were used for specifying requirements of functionality purposes:
| Background job names comply with the internal platform requirements, Background job names are more precise. |
| Queries. | The ValueType() query language function returns UNDEFINED when UNDEFINED is passed as the function parameter. This change is not implemented in 8.3.6 compatibility mode. | The ValueType() query language function returned NULL when UNDEFINED was passed as the function parameter. | Eliminated unexpected system behavior. |
| Server cluster. | You can restrict access to cryptography features using security profiles. For ISecurityProfile object, the CryptographyAllowed property is implemented (programmed administration of server clusters using COM objects). For ISecurityProfile object, the getCryptographyAllowed() and setCryptographyAllowed() methods are implemented (Java server administration interface). For the server cluster command-line utility (rac) the crypto parameter for the profile command is implemented. This change is not implemented in 8.3.6 compatibility mode. | The option to restrict access to cryptography features using security profiles was not provided. | Extended security profile capabilities. |
| Access rights. | The access rights check for document journal graph attributes performed using the AccessRight() method with User/Role parameter specified takes into account the availability of all objects included in the journal graph content. The AccessRight() result is cached by the platform, which is similar to caching reusable return values. This change is not implemented in 8.3.6 compatibility mode. | The access rights check for document journal graph attributes performed using the AccessRight() method with User/Role parameter specified did not take into account the availability of all objects included in the journal graph content. The AccessRight() result was not cached by the platform. | Eliminated unexpected system behavior. Improved performance of access rights check for applied solutions with a large number of roles, and for file mode infobases on low-performance computers. This improves the performance of form opening in the listed scenarios. |
| Localization. | The option to specify the first day of the week is implemented. It can be accessed in Designer (on the Administration menu, click Regional infobase settings). When you create an infobase using platform version 8.3.7 or later without compatibility mode set, the first day of the week value is set to Auto. It is defined based on the Language (Country) property in regional infobase settings. The choice of the first day of the week affects the following features:
This change is not implemented in 8.3.6 compatibility mode. | The first day of the week was always Monday. | Better usability in countries where the first day of the week in not Monday. |
| Spreadsheet documents. | You can edit multilingual spreadsheet documents in managed forms, provided that these documents are templates. The list of languages is obtained directly from a template. In managed forms, spreadsheet documents are edited and displayed using the language specified in the LanguageCode spreadsheet document property. Strings in other languages are never changed. The SpreadsheetDocument.Template property is implemented. This change is not implemented in 8.3.6 compatibility mode. The FillPropertyValues() method never copies the Template property (regardless of the compatibility mode). | In managed forms, spreadsheet documents were always edited using the current language. When the platform displayed a spreadsheet document:
When spreadsheet document text was edited using 1C:Enterprise script, strings in the current language were written and strings in other languages were lost. | You can edit multilingual spreadsheet documents in 1C:Enterprise mode. |
| Applied objects. | When the Presentation field of the TasksByPerformer virtual table is generated, the fact that the presentation of the corresponding Task object can be redefined is taken into account. This change is not implemented in 8.3.6 compatibility mode. | When the Presentation field of the TasksByPerformer virtual table was generated, the fact that the presentation of the corresponding Task object could be redefined was not taken into account. The default presentation was always used instead. | Eliminated unexpected system behavior. |
| Queries. | The query object model is improved. The Find() method is implemented for the following objects: QuerySchemaIndexExpressions, QuerySchemaExpressions, QuerySchemaOrderExpressions, QuerySchemaAvailableFields, QuerySchemaAvailableTableParameters, QuerySchemaTableParameters, QuerySchemaFields, QuerySchemaColumns, QuerySchemaTableForUpdate, and QuerySchemaAvailableTables. The FindByName() and FindByAlias() methods are implemented for the following objects: QuerySchemaQuerySourceJoins and QuerySchemaSources. The FindByExpression() method is implemented for the following objects: QuerySchemaTotalCalculationFields and QuerySchemaTotalExpressions. The QuerySchemaTotalCalculationFields.FindByColumnName() method is implemented. The QuerySchemaTotalExpressions.FindByField() method is implemented. The QuerySchemaSources.GetRootSources() method is implemented. New Add() method variant is implemented for the following objects: QuerySchemaOrderExpressions, QuerySchemaQuerySourceJoins, QuerySchemaTablesForUpdate, and QuerySchemaTotalExpressions. For the QuerySchemaFields.Add() method the optional Column parameter is implemented. The SourceAlias parameter of QuerySchemaQuerySourceJoins.Add() method can have values of the following types: String and QuerySchemaSource. The QuerySchemaTotalExpressions.Add() method parameter can have values of the following types: String, QuerySchemaColumn, and QuerySchemaExpression. The behavior of QuerySchemaTotalCalculationFields.Add() method is modified for scenarios when its parameter has a value of String type. The QuerySchemaNestedTable.Fields property has QuerySchemaFields type. Passing a text containing a batch query or a table drop query to the QuerySchemaSelectQuery.SetQueryText() method raises an exception. The "For a nested table" variant of the QuerySchemaExpressions.Add() method is declared obsolete. This change is not implemented in 8.3.6 compatibility mode. | These features were not provided. The QuerySchemaNestedTable.Fields property had QuerySchemaExpressions type. If a text containing a batch query was passed to the QuerySchemaSelectQuery.SetQueryText() method, the first query in the batch was used. If a text containing a table drop query was passed to the QuerySchemaSelectQuery.SetQueryText() method, an empty query was created. The "For a nested table" variant of the QuerySchemaExpressions.Add() method was available. | Improved usability of query object model. |
| Data composition system. | In the data composition system, the data set link type is replaced with inner link if a filter containing only fields from the data set being linked is applied. Conditions that do not include inner links are added to the RecordsFilter property of groupings that contain at least one data set with fields used in these conditions. This change is not implemented in 8.3.6 compatibility mode. | In the data composition system, the data set link type was always set to inner link when a filter included a linked data set field. | Eliminated unexpected system behavior when fields from multiple data sets were used in a filter. |
| Navigation links. | The GotoURL method parameter value is not decoded prior to passing it to the operating system (the original link is passed). This change is not implemented in 8.3.6 compatibility mode. | The GotoURL method parameter value might be decoded prior to passing it to the operating system:
| Eliminated unexpected system behavior. |
| Configuration extensions. | Writing an extension to an infobase is available in the following cases: the session that performs the writing is not running in the safe mode, or the session security profile allows this operation. When attaching an extension, the platform does not check whether the extension fits the session security profile restrictions. | Writing an extension to an infobase was only available if the session was running in the safe mode, When attaching an extension, the platform checked whether the extension fit the session security profile restrictions. | Security profiles process extensions in the same way as they process external reports and data processors. |
| Applied objects. | If a new object number (this includes document, catalog item, chart of characteristic types item, business process, and task numbers) is issued inside a transaction, it is reused even if the autonumbering mode is set to Do not Release Automatically, including scenarios where the object is not written inside the transaction. The Do not Release Automatically autonumbering mode only affects the numbers issued outside transactions. In other words, if a number is issued outside a transaction and it is not used (because the object is not written), it is not reused in the Do not Release Automatically mode, and it is reused in the Release Automatically mode. | If a new object number (this included document, catalog item, chart of characteristic types item, business process, and task numbers) was issued inside a transaction and the object was not written, that number was not reused in the Do not Release Automatically mode. | Reduced number of unused object numbers in scenarios where object numbers are issued in transactions and those objects are not written. |
| Client application. Data display. | If you want to use fonts other than Auto in your applied solutions, it is recommended that you select from the following fonts:
If you use a font that is not listed here, from items might not be displayed correctly in some modes (including client applications). | The list of recommended fonts was not available. | A list of fonts recommended for use to ensure uniform applied solution appearance across environments is now available. |
| Managed forms. | The algorithm that calculates the font size based on the font properties specified for a fortm item is changed. This might lead to the change of the font scale for the form items that have the Scale part of the Font property set to a nondefalut value. This change is not implemented in 8.3.6 compatibility mode. | In some cases the Scale part of the Font property of form items was ignored, so that the text displayed on a form item had the default size. | Eliminated unexpected system behavior. In some cases the font size of form items might change. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Development tools. | The option to debug configurations on the mobile platform is implemented. The debugging can only be performed over HTTP (you can select this option in Designer). | This feature was not provided. | Streamlined development of applied solutions for the mobile platform. |
| Print tools. | The Print mobile application extension, which is used for printing from mobile applications, is implemented. The mobile application builder supports building mobile applications that require this extension. | This feature was not provided. | Reduced list of required permissions for mobile applications that do not require printing. |
| Spreadsheet documents. | The brightness of frozen spreadsheet document areas is reduced by 2.5%. | The brightness of frozen spreadsheet document areas was reduced by 10%. | Better look and feel of spreadsheet documents with frozen areas. |
| 1C:Enterprise script. | The following string processing functions previously available for the personal computer platform are now implemented for the mobile platform: StrTemplate(), StrCompare(), StrStartWith(), StrEndsWith(), StrFind(), SrtSplit(), and StrConcat(). The SearchDirection system enumeration is implemented. | This feature was not provided. | Unified string processing for the personal computer platform and the mobile platform. |
| Managed forms. | The Representation property of a managed form button located in a form title command bar affects the button view. When the platform defines the button view, it ignores the properties of the command linked to the button. | The Representation property of a managed form button located in a form title command bar did not affect the button view. When the platform defined the button view, it ignored the properties of the command linked to the button. | You can manage the view of buttons located in form title command bars using the button properties. |
| Special tools. | For the TelephonyTools.NumberDialingSupported() method the DirectCall parameter is implemented. The parameter streamlines the check for number dialing support. | The TelephonyTools.NumberDialingSupported() method did not support any check options. | Унифицирована возможность проверки работы со специальными возможностями на мобильной платформе. |
| System requirements. | Support of Windows Phone operating system version 8.1 or later (ARM and x86 architectures) and touch devices that run Windows version 8.1 or later (ARM and x86) is implemented. The mobile platform for Windows Phone supports all mobile platform features available on other operating systems, excluding:
The mobile platform specifics are described in the documentation. The mobile platform distribution file mobile.zip is complemented with new data. This option is implemented as beta version. | This feature was not provided. | Extended support of operating systems for mobile and touch devices. |
| Mobile application builder. | Mobile application builder for Windows Phone operating system is implemented. It supports Windows Phone 8.1 or later. New builder parameters are added:
Publishing of built applications to Windows Store is not supported. When loading mobile platform data from the mobile.zip file to mobile platform builder, you have the option to load only mobile operating systems that are present in the archive. The option to specify different application IDs for different mobile operating systems is supported. The option to export developer certificates from the mobile application builder database is implemented. | Mobile application builder did not support Windows operating system. Attempts to load the mobile platform from the mobile.zip file to mobile application builder were only successful if the file contained platform versions for both Android and iOS. A single mobile application ID was assigned for Android and iOS builds. Exporting developer cerificates from the mobile application builder database was not supported. | Mobile application builder supports Windows operating system, and features other improvements. |
| Command interface. Managed forms. | On the mobile platform, the Show in list command, which was perviously available only on the personal computer platofrm, is implemented. The ManagedForm.ExecuteNavigation() method and the NavigationProcessing managed form event are implemented. | This feature was not provided. | The interfaces of the mobile and personal computer platforms are unified. |
| Web services and HTTP services. | On the mobile platform, the option to use a web service whose address does not match the address specified in a WSDL file imported to the applied solution (WS-reference configuration object) is implemented. | This feature was not provided. | Web servfice operations on the mobile and personal computer platforms are unified. |
| Managed forms. | On the mobile platform, the option to use a selection list to provide a value for a managed form input field that displays date and time is implemented. | On the mobile platform, drop-down lists were not available. | On the mobile platform, the option to use drop-down lists in the input fields that display date and time is now available. |
| Managed forms. | The option to switch between the input fields using the Enter button of the virtual keyboard (i.e. without closing the keyboard) is implemented. The option to switch between the input fields using Tab/Shift+Tab keys of a physical keyboard connected via Bluetooth is also implemented. | The option to switch between the input fields without closing the virtual keyboard was not available. To switch between the fields, a mobile application user had to close the keyboard, then switch to another field, and then open the keyboard. | Improved mobile application usability is scenarios where multiple input fields are available in a single form. |
Version 8.3.6 includes known bug fixes and functionality modifications.
To obtain a link to an entry of the V8Update file, double-click any of the entry lines. This opens a pop-up window with the link available for copying to the clipboard. This feature is only available if JavaScript is enabled.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.5 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, 8.2.16, 8.3.1, 8.3.2, 8.3.3 and 8.3.4. | In version 8.3.6 you can run configurations created in version 8.3.5 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.6 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.5 for working with the infobase even after the transition to version 8.3.6. 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. | In Designer, in module text, bookmarks can be preserved between different work and module editing sessions. To access the full list of bookmarks, on the Edit menu, click Bookmarks. | This feature was not provided. | Improved Designer usability, |
| Development tools. | When renaming a configuration object, you have the option to update the object name usage instances in the entire configuration. When deleting a configuration object, you have the option to search for the object name usage instances in the entire configuration. When modifying or deleting a managed form item, attribute, or parameter, the check for usage instances of its name in the form module is performed. When renaming an item, attribute, or parameter, you have the option to update its name usage instances in the form module. The Find references to object operation now includes the search in module texts. You can specify whether you want to use these options in the Designer options window. | These features were not provided. | Reduced chance of making errors when renaming or deleting configuration objects. Improved usability for developers. |
| Managed forms. | Planner (a visual tool for managing schedule data) is implemented. A new "planner field" type is implemented for managed form fields. The Planner object is implemented. In the TimeScalePosition system enumeration, the following values are implemented: Left and Right (when applied to a Gantt chart, both are treated as Top). | This feature was not provided. | Improved user experience for scheduling (appointments, calendars, and so on). |
| Configuration repositories. | In Designer batch mode, you can bind an infobase that is not yet bound to the configuration repository (command-line option /ConfigurationRepositoryBindCfg). | This feature was not provided. Infobases could be bound to repositories only interactively. | You can automate more configuration repository operations. |
| Command interface. Managed forms. | For managed form extensions for objects, catalogs, documents, charts of characteristic types, business processes, tasks, and information register records, the Show in list command is implemented. For managed forms, the ExecuteNavigation() method and NavigationProcessing event handler are implemented. | This feature was not provided. | Improved system usability for automatic object selection in a list being opened. |
| System enumerations. Client application. | For the SectionsPanelRepresentation system enumeration, the following values are implemented: PictureOnTopAndText and PictureOnLeftAndText. In the client application, in the sections panel editor, the following section view features are available:
| For the SectionsPanelRepresentation system enumeration, the following values were available: Picture, Text, PictureAndText. |
Extended section view capabilities for the sections panel in the Taxi interface. |
| Managed forms. | The option to specify a graphical schema field as a source of command bar and managed form button commands is implemented. The only commands available in the web client are print and preview. In the Russian interface some of the graphical schema commands are renamed to the following:
| The option to specify a graphical schema field as a source of command bar and managed form button commands was not provided. In the Russian interface some of the graphical schema commands had different names:
| Increased graphical schema usability. |
| Administration tools. | An object integrity check utility is implemented. It checks the state of file system objects and database objects used by 1C:Enterprise and monitors their changes. The 32-bit and 64-bit versions of the utility are available for Windows and Linux operating systems. | This feature was not provided. File change monitoring was only available using third-party tools. Monitoring of database object changes was not available. | The option to perform system integrity checks to provide protection against unauthorized modifications is implemented. |
| Internet-enabled functionality. | For the Get() method of the InternetMail object, the MarkAsRead parameter is implemented. This parameter only makes sense when the platfrom uses IMAP for email operations. If the platform uses POP3, an attempt to use this parameter when it is set to False generates an exception. The platform behavior in 8.3.5 compatibility mode is not changed (for the part where the parameter is set to False). | If the platform used IMAP for email operations, the execution of the Get() method of the InternetMail object gave different results depending on the value of the ArrayOfMessageHeadersOrIdentifies parameter.
| Eliminated inconsistency in the platform behavior during email operations that use IMAP. |
| Technological log. | For the SCALL and CALL technological log events, new IName and MName fields are implemented. They store additional internal system call data. 1C Company experts might use that data while handling support requests. | This feature was not provided. | The technological log provides additional data that can be helpful for solving complex issues. |
| Dynamic lists. | The option to get data from a dynamic list (adjusted for column visibility settings and search options applied) is implemented. The following methods are implemented for the managed form table extension for dynamic lists:
| This feature was not provided. | The option to get dynamic list data that is visible to a user for future processing is available. |
| Data composition system. | The following subordinate fields are implemented for data composition system fields that have Data among their types: BegOfDay, BegOfWeek, BegOfTenDays, BegOfMonth, BegOfQuarter, BegOfHalfYear, BegOfYear, EndOfDay, EndOfWeek, EndOfTenDays, EndOfMonth, EndOfQuarter, EndOfHalfYear, EndOfYear, Day, WeekDay, WeekDayName, DayOfYear, WeekOfYear, Month, MonthName, Quarter, Year, BegOfMinute, BegOfHour, EndOfMinute, EndOfHour, Minute, and Hour. | This feature was not provided. One could use user-defined expression fields to retrieve this data. | Simplified end-user operations with fields that include date and time. |
| 1C:Enterprise script. | The following string processing functions are implemented:
The SearchDirection system enumeration is implemented. The Find() function is declared obsolete, it is supported for compatibility purposes. This change is not implemented in 8.3.5 compatibility mode. | This feature was not provided. Developers had the option to implement the functionality introduced in the new functions using 1C:Enterprise script. | Simplified implementation of some standard string processing algorithms. |
| Web client. | Storing accumulated web client statistics is implemented. This feature is intended for 1C Company experts. To enable it, run the web client with the SYSTEMWEBCLIENTSTAT command-line option. | This feature was not provided. | The set of tools intended for platform performance quality control is expanded with a new tool. |
| Spreadsheet documents. | Importing data from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument) formats to spreadsheet documents is implemented. This operation can be performed both interactively and from 1C:Enterprise script. The SpreadsheetDocumentValueReadingMode system enumeration is implemented. For the Read() method of the SpreadsheetDocument object, the ValueReadingMode parameter is implemented. Support of pasting areas copied to the clipboard from Microsoft Excel and OpenOffice Calc documents is implemented. | This feature was not provided. | Simplified data import from spreadsheet documents of the following formats: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument). |
| Data composition system. Dynamic lists. | For the DataCompositionSettingsComposer object. the GetAvailableSettingsSource() method is implemented. | This feature was not provided. | Simplified access to the available settings source of a data composer from another data composer. For example, you can use this feature when you open a new data composition settings editor form that uses the same source as the previous form. |
| Internet-enabled functionality. Web services and HTTP services. | You can process JSON data using both stream and object approaches. The following objects can be serialized to or deserialized from JSON: primitive types, Array, FixedArray, Structure, FixedStructure, Map, and FixedMap. The JSONReader and JSONWriter objects are implemented. The WriteJSON(), ReadJSON(), WriteJSONDate(), and ReadJSONDate() global context methods are implemented. | This feature was not provided. One could implement processing JSON data using 1C:Enterprise script tools. | Simplified interaction with applications (including web applications) that use JSON data format. You can store various data types in JSON format, which provides an alternative to other formats, such as XML. |
| Web services and HTTP services. | Web services and HTTP services. For the standard OData interface, getting responses in JSON format is implemented. | This feature was not provided. For the standard OData interface, responses were only available in Atom format. | The OData format is supported in more detail. Using JSON format minimizes the volume of data transferred between the client and the server. |
| Queries. | You can use logical expressions in descriptions of selection fields and in query result filter expressions (in the WHERE clause). | This feature was not provided. If a logical expression was required for describing a selection field, you had to use a selection clause. Logical expressions in the WHERE clause could be connected only by AND, OR, and NOT logical operators, and they could not be composite. | Simplified writing and understanding of complex queries. |
| Server clusters. Administration tools. | The automatic server cluster status monitoring feature is implemented. This includes monitoring of several cluster parameters and termination of processes that might cause any issues. The central cluster server agent performs the monitoring. The monitoring results are recorded to the technological log. For the cluster, the Server errors threshold and Terminate corrupted processes properties are implemented. For the IServerAgentConnection object, the SetClusterRecyclingErrorsCountTheshold() and SetClusterRecyclingKillProblemProcesses() methods are implemented. For the rac utility, the --errors-count-threshold and --kill-problem-processes command-line options are implemented. For the technological log, the ATTN event is implemented. | Automatic server cluster status monitoring was not provided. | Increased server cluster reliability by timely detection and termination of processes that might cause issues. |
| Automated testing. | The automated testing supports the Taxi interface. New automated testing features are added:
| The automated testing did not support the Taxi interface. | The automated testing can be used with the Taxi interface. |
| Data composition system. Dynamic lists. | Items of report user settings and dynamic list user settings can be linked to managed form tables. For the DataCompositionUserSettings object, the Filter, Order, Selection, ConditionalAppearance, and Structure columns are implemented. The report user settings form and the dynamic list user settings form are modified: instead of text boxes with the option to open editors (filter, order, and so on), tabs with tables are implemented to provide uniformity with the data composition schema editor in Designer. The Settings command of the report form is displayed in the main form command bar. | Items of user report settings and dynamic list settings could be linked only to managed form text boxes. The report and dynamic list user settings forms had a different layout. The Settings command of the report form was available in the More menu. | Improved standard report and dynamic list user settings form. |
| Managed forms. | For the Enum metadata object, the ChoiceHistoryOnInput property is implemented. This property defines whether the choice history of a text box linked to an attribute of enumeration type is displayed and saved. For enumerations whose values can be selected in a form, the input history is displayed and saved automatically. This change is not implemented in 8.3.5 compatibility mode. | This feature was not provided. The choice history for a text box linked to an attribute of enumeration type was neither displayed nor saved. |
You can specify whether the choice history for a text box linked to an attribute of enumeration type is displayed and saved. |
| Data composition system. | For the DataCompositionDetailsFieldValues object a constructor is implemented. | The DataCompositionDetailsFieldValues object did not have a constructor. | You can fill detailed data using 1C:Enterprise script. |
| Web services and HTTP services. | For the HTTPConnection object, you can call any HTTP methods (passing the method name as a string). In order to simplify the usage of PATCH and HEAD HTTP methods, the Patch() and Head() methods are implemented for the HTTPConnection object. | These features were not provided. The HTTPConnection object could only be used to call the GET, PUT, POST, and DELETE methods. | Easier access to the full range of HTTP methods from applied solutions. |
| Server clusters. Administration tools. | External session management functionality is extended. Methods that are called when a session is hibernated or restored from hibernation are implemented. You can specify a timeout for the external session management web service response. For the external session management web service, the onHibernateSession() and onWakeupSession() methods are implemented. For external session management web service connection string, the optional parameters are implemented: tout sets an external session management web service response timeout, and wsver specifies the external session management web service interface version. The new features are only available if the wsver parameter is set to 2. | These features were not provided. | The web service behavior is uniform with the licensing subsystem behavior. |
| XML and XDTO support. | FastInfoSet operations are refactored. | FastInfoSet operations had a different implementation. | Improved stability of FastInfoSet operations. |
| Full-text search. | The full-text search index integrity check is implemented. For the full text search manager, the CheckIndex() method is implemented. The full-text search index update operations are recorded to the tecnological log. In the tecnological log, the FTEXTCheck and FTEXTUpd events are implemented. In the technological log the ftextupd item is implemented. | These features were not provided. | Improved stability of full-text search. An invalid full-text search index can be rebuilt. |
| Queries. | For the QuerySchemaTempTableDescription object, the TableName property is implemented. You can specify a temporary table name in the query builder. For the QuerySchemaSources object, the Alias parameter of the Add() method is implemented. | These features were not provided. | Improved functionality of the query software model. |
| Development tools. Common attributes / Data separation. Configuration extensions. | More options for modification of applied solutions (including cloud systems) without disabling their support. You can create configuration extensions and use them to implement applied solution modifications (which do not affect the data structure), so that the applied solution support is not disabled, and all modifications take place in a dedicated object (extension), which is easily connected to and disconnected from the applied solution. You can use extensions to modify forms, create reports and data processors, and create new subsystems. You can apply a configuration extension both in 1C:Enterprise mode and in Designer. You can specify a custom extension set for each separated infobase area. | This feature was not provided. Applied solution developers could create external reports and data processors and modify the applied solution configuration, which resulted in disabling support and did not allow making modifications in different areas of a separated infobase. | The new feature is intended for making small configuration modifications at the deployment stage (including modifications of separated infobases and cloud systems) more easily and with less dependence on vendor configuration modifications. |
| Data display. | New pictures are added to the picture library: GoForward, GoBack, GoToBegin, GoToEnd, Today, ShowInList. | The listed pictures were not available in the picture library. | More content for the picture library. |
| Database configuration updates. | The documentation describes Designer batch mode command-line options that manage background and dynamic database configuration updates. | The new Designer batch mode command-line options that manage background and dynamic database configuration updates were not listed in the documentation. | Fixed documentation error. |
| System requirements. Web client. | Support of Microsoft Windows 10 operating system is implemented. Support of Microsoft Information Services 10.0 web server is implemented. Support of Microsoft Edge web browser is implemented, with the following limitations:
| Microsoft Windows 10 operating system was not supported. Microsoft Information Services 10.0 web server was not supported. Microsoft Edge web browser was not supported. | Extended list of supported operating systems and web browsers. |
| DBMS operations. | Support of PostgreSQL version 9.4 is implemented. | This PostgreSQL version was not supported. | Extended list of supported PostgreSQL versions. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Command interface. | In the Taxi interface, in the functions menu, you can search for commands by their presentations. The search is performed in all sections (not only in the commands of the current section). Commands for specifying navigation and action panel settings are moved to the submenu to the right of the search field. In the Taxi interface, pressing F10 opens the functions menu. | The option to search for a command by a part of its presentation was not provided. Commands for specifying navigation and action panel settings were displayed as links in the right part of the functions menu. In the Taxi interface, pressing F10 opened the main menu. | Improved usability of the function menu. |
| Managed forms. | If all of the managed form command bar buttons have their OnlyInAllActions parameters set to False and some of these buttons do not fit the command bar width, the More button is added to the command bar, with a submenu that contains all of the command bar commands. | If all of the managed form command bar buttons had their OnlyInAllActions parameters set to False and some of these buttons did not fit the command bar width, there was no way to access the commands that did not fit. | If the command bar has small size, all of its commands are still available. |
| Client application. | You can fully replace the splash screen that is displayed during the startup of the thin, thick, and web clients. To replace a splash screen in your applied solution, submit a request to 1C Company | This feature was not provided. | In particular cases, you can use a splash screen that is fully customized by the company that uses the applied solution, provided that the splash screen is approved by 1C Company. |
| Web client. | Web browser pop-up windows are no longer displayed during the printing of spreadsheet documents. | When spreadsheet documents were being printed, web browser pop-up windows were displayed. | Simplified printing of spreadsheet documents for end users. In the Taxi or Forms in tabs interface mode, if the applied solution does not use modal calls, it does not require additional web browser setup. |
| Managed forms. | In managed forms, if the Create command is available for a text box, it is present in the context menu of the text box. | The Create command was never present in text box context menus. | Improved usability of text boxes. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Full-text search. | The full-text search algorithm is optimized for scenarios where a search string is used multiple times (for example, getting the next batch of search results). The full-text search algorithm is optimized for scenarios where a user does not have access rights for some objects returned by the search. | The full-text search performance was insufficient. | Improved full-text search performance for infobases containing a large number of items, and also in scenarios where a user does not have access rights for some objects returned by the search. |
| Full-text search. | Optimized memory usage for fuzzy search (the search that uses the # operator). The search for similar words is optimized. | Fuzzy search might cause a memory overflow which, in turn, caused the system shutdown. The search for similar words might take a long time. | Increased stability of the fuzzy search in scenarios where the full text search index has a large size. |
| Web client. | The web client performance is improved in the following scenarios:
The web client now uses Google Closure Compiler. | The web client performance was insufficient. | Improved web client performance. |
| 1C:Enterprise script. | The loading time of 1C:Enterprise script modules is slightly reduced. | The loading of 1C:Enterprise script modules was not fast enough. | Slightly reduced startup time for applied solutions that include a large number of 1C:Enterprise script modules. |
| Client application. | The startup time of the client application (before the authentication dialog appears) is slightly reduced. | The client application startup was not fast enough. | Slightly reduced startup time of the client application. |
| Configuration repositories. | The performance of the following operations is improved:
The performance of compatibility mode change operations is improved. The 1C:Enterprise version 8.3.3 compatibility mode is implemented for configuration repositories. The configuration repository performance is improved in scenarios where the configuration repository compatibility mode is set to Do no use. | The performance of configuration repository operations was insufficient. | Improved configuration repository performance. |
| Managed forms. | The strong data compression algorithm for large data volumes (more than 64 KB) transferred between the client and the server (or a web server extension) is optimized. This slightly reduces the time required to open managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode. | The strong data compression algorithm was less efficient. | Slightly reduced time of opening managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode. |
| Web services and HTTP services. | Faster processing of requests that call the standard OData interface. | Performance of requests that called the standard OData interface was insufficient. | The performance of operations with the standard OData interface is improved. |
| Managed forms. | Improved performance of opening managed forms in the following scenarios:
| The performance of opening managed forms in the listed scenarios was lower. | Improved usability of managed forms. |
| Managed forms. | Managed form conditional appearance is optimized. | The performance of managed form conditional appearance was lower. | Improved usability of managed forms with conditional appearance. |
| Development tools. | Performance of base configuration updates (update configuration from file, load configuration from file, and get specific configuration version from configuration repository) is improved. | Performance of base configuration updates was insufficient. | Better usability for developers. |
| DBMS operations. Administration tools. | For the file mode, the option to restructure the infobase so that all data required to open the infobase is at the beginning of the 1Cv8.1CD file is implemented. This improves the performance of infobase opening. This type of restructuring is performed during the compressing of infobase tables (which is available from a Designer dialog box and as a command-line option), or during infobase verification with the chdfl utility with the Correct errors check box selected. It is recommended that you always perform this optimization after you make any configuration changes (and the associated infobase restructuring) that result in database structure changes. | Internal information required for opening an infobase was evenly distibuted within the 1Cv8.1CD infobase file. | Improved performance of opening file infobases, especially in scenarios where the infobase is located on a network resource. |
| DBMS operations. | In client/server mode with PostgreSQL DMBS, the query that is executed when deleting records from tables of extra dimensions of accounting registers is optimized. | In client/server mode with PostgreSQL DMBS, the performance of the query that was executed when deleting records from tables of extra dimensions of accounting registers was insufficient. | Improved performance of deleting accounting register records. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. | When a client application is restarted with the /AppAutoCheckMode key, the platform checks the user rights for running the client application. If the user attempts to start the application in the ordinary mode and does not have the right to run the thick client, they are not allowed to access the infobase. In other scenarios the client application that suits the selected start mode best is selected. | When a client application was restarted with the /AppAutoCheckMode key, the platform did not check the user rights for running the client application. | The client application selection algorithm is improved. |
| Managed forms. | If editing text in a form field extension for a text box is not allowed (the TextEdit property is set to False), the drop-down list of that box does not display the text "Enter the search string". | The drop-down list always displayed the text "Enter the search string". | The recommendation to perform an action that is not allowed is no longer displayed. |
| Development tools. | During the merging of configurations you can modify the results of module merging. You can use external software (not incorporated in Designer) for comparing and merging module texts. You can specify the external software in the Designer options dialog box. Ready-to-use settings are available for the following external software:
You can specify settings for external software that is not on the list. | The results of module merging could not be modified while merging configurations. Only built-in Designer features were available for comparing and merging module texts. | Developers can use any tool that they find convenient for comparing and merging module texts. They can make changes during the merging of configurations (with the help of external software). |
| Development tools. | Improved setup for the comparison and merging of managed forms. You can specify the comparison and merging rules for a form and for its module directly in the comparison and merging dialog box. | The comparison and merging rules for managed forms were specified in another dialog box. Also, the rules for the form itself and for its module were separated. | Simplified setup for the comparison and merging of managed forms and their modules. |
| Development tools. | The following features are implemented in the managed form editor:
| The window title bar in the preview area of the form editor did not have any functionality. | Improved usability of the form preview area in the managed form editor. |
| Internet-enabled functionality. | Automatic selection of text encoding in email messages containing national characters is implemented. The automatic selection is only performed when the text contains national characters but their encoding is not specified, which does not comply with the standard. This applies to the following email message parts:
| Email message text was displayed in incorrect encoding when no encoding was specified. | Email messages that do not comply with the standard are processed correctly. |
| Background and scheduled jobs. | The duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases is reduced. Now the duration of the first access is approximately the same as the duration of subsequent accesses. | The long duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases might cause the user interface to stop responding until loading the backgound job scheduler was complete. | Reduced duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases. Faster start of client applications in the file mode (when the background job manager is accessed during the startup). |
| Background and scheduled jobs. | In file infobases, if a client application that performs background jobs is closed, the background jobs are terminated after a 30-second timeout. When a job is terminated, a_$Job$_.Terminate event is recorded to the event log. | In file infobases, if the platform could not complete background jobs correctly, it displayed a message prompting the user to choose between waiting and terminating the jobs. | Eliminated unexpected (and not user-friendly) system behavior. |
| Error handling. | When properties or methods of MetadataObject objects related to external reports or data processors that are no longer available are accessed, the platform generates an exception. | When properties or methods of MetadataObject objects related to external reports or data processors that were no longer available were accessed, the platform was shut down unexpectedly. | Improved system stability. |
| Development tools. Internet-enabled functionality. | The following information is added to the Syntax Assistant:
| The Syntax Assistant did not contain this information. | Improved Syntax Assistant quality. |
| Spreadsheet documents. | When a spreadsheet document is exported to Microsoft Excel 2007-2010 format, its comments are converted to Excel table comments. This change is not implemented in 8.3.5 compatibility mode. | When a spreadsheet document was exported to Microsoft Excel 2007-2010 format, its comments were converted to Excel pictures. | Better conversion of spreadsheet document items to Microsoft Excel format. |
| Background and scheduled jobs. | When a client application is started with a file infobase, there is a 1-minute delay before starting the execution of scheduled jobs. | When a client application was started with a file infobase, there was no delay before starting the execution of scheduled jobs. | Faster startup of client applications in file mode. |
| Defined types. | During the update of a supported configuration you have the option to merge the following properties with priorities: the Type property of the DefinedType configuration property and the Type property of the ChartOfCharacteristicTypes object. | This feature was not provided. | Improved algorithm for comparing and merging defined types, which simplifies usage of those types in library development tasks. |
| Managed forms. | Presentations of items found during the input by string with full-text search enabled are identical to presentations of items found with full-text search disabled. The order of items in drop-down lists generated by the input by string feature with full-text search enabled matches the order of items returned by the full-text search algorithm. The algorithm that generates presentations for Task objects in drop-down lists generated by the input by string feature is modified. | Presentations of items found during the input by string with full-text search enabled were different from presentations of items found with full-text search disabled. The order of items in drop-down lists generated by the input by string feature with full-text search enabled was not defined. The algorithm that generated presentations for Task objects in drop-down lists generated by the input by string feature was different. | Improved usability of the input by string feature. Unified generation of presentations for search results. |
| Configuration repositories. | The configuration repository window now displays names of computers where objects are locked. | The configuration repository window displayed the name of the computer that the current user used for their first connection to the repository. | Eliminated unexpected system behavior. |
| Internet-enabled functionality. | For the InternetMailMessage object, the PostingDateOffset property is implemented. | This feature was not provided. | You can define the true date of sending an email message. |
| Dynamic lists. | When a form is opened, the Period property of managed form table extension for dynamic lists and the Representation property of a form table linked to a dynamic list are loaded simultaneously with dynamic list user settings. It is recommended that you get the Period property in the OnLoadUserSettingsAtServer managed form event handler. This change is not implemented in 8.3.5 compatibility mode. | The Period property of managed form table extension was obtained from the user settings before the execution of the OnCreateAtServer managed form event handler. The Representation property of a form table linked to a dynamic list was obtained from the client settings during the form opening. |
The Period and Representation properties are stored in a similar way to other dynamic list settings, which simplifies operations with these properties using 1C:Enterprise script. |
| Spreadsheet documents. | When nonempty spreadsheet document cells with Placement properties are set to Auto are displayed, the cells are not merged up to the next filled cell or up to the horizontal boundary of the spreadsheet document. | When nonempty spreadsheet document cells with Placement properties set to Auto were displayed, the cells were merged up to the next filled cell or up to the horizontal boundary of the spreadsheet document. | The spreadsheet document view in the web client is now closer to the spreadsheet document view in the thin client. |
| DBMS operations. | In the client/server mode with Oracle Database DBMS, executing a query that contains a subquery in the SELECT section and also an aggregate function adds a GROUP BY section with a constant, provided that such section is not yet present in the query. | In the client/server mode with Oracle Database DBMS, executing a query that contained a subquery in the SELECT section and also an aggregate function resulted in the ORA-937 run-time error. | Improved stability of Oracle Database operations. |
| Managed forms. | The prevention of unexpected working process or client application shutdown due to managed form operation issues (loss of synchronization between the client and server parts of form data) is implemented. When an issue is detected, only the affected session is closed, and the working process that processes the session is not shut down. By default, the issue details are recorded to the technological log. | A loss of synchronization between the client and server parts of form data could result in a shutdown of the client application or a working process that processed the affected session. |
Improved 1C:Enterprise server stability during managed form operations. |
| DBMS operations. | The chance of deadlocks in queries that include comparisons with UNDEFINED is reduced. | The chance of deadlocks in queries that included comparisons with UNDEFINED was higher. | Increased system stability. Reduced chance of deadlocks that do not have obvious reasons. |
| Client application. Managed forms. Data display. | For client applications that run on Windows operating systems, Windows scaling is supported. If a custom DPI value is set, interface items are scaled correctly, except pictures that might look a bit blurry. | Client applications that run on Windows operating systems had scaling issues. | Eliminated unexpected system behavior in scenarios where a user sets a custom DPI value for their display. |
| Configuration repositories. | When a user cancels binding to a configuration repository or when an infobase bound to a repository changes location, the dialog box stating that unbinding from the repository is required is no longer displayed. To unbind a configuration from a repository, you can use the corresponding Designer command. | When a user canceled binding to a configuration repository or when an infobase bound to a repository changed location, the dialog box stating that unbinding from the repository was required was always displayed. | Improved usability of configuration repositories in some scenarios. |
| Command interface. | The visibility settings for commands in subordinate subsystems are no longer lost when command interface settings of a subsystem that contains subordinate subsystems are copied using the Load() and Save() methods of the StandardSettingsStorageManager object. | When command interface settings of a subsystem that contained subordinate subsystems were copied using the Load() and Save() methods of the StandardSettingsStorageManager object, the visibility settings of commands in subordinate subsystems were lost. | Eliminated unexpected system behavior. |
| Web client. Spreadsheet documents. | In the web client, the option to select pictures in spreadsheet documents is implemented, and when they are selected, the respective event is called. Improved representation of pictures in spreadsheet documents when viewed in the web client:
|
Selecting pictures in spreadsheet documents was not supported. Spreadsheet documents had some picture-related issues. | Improved quality of displaying spreadsheet documents with pictures in the web client. |
| Development tools. Mobile application. | The picture editor dialog box in Designer supports editing template pictures and the new picture variants format that includes a manifest. Template pictures are used in applied solution development for the mobile platform. | Editing template pictures and the new picture variants format that includes a manifest were not supported. | Template picture support is implemented. |
| DBMS operations. | The DBMS request that the platform generates based on the VALUETYPE function of the query language is simplified. | The DBMS request based on the VALUETYPE function was more complicated. | Eliminated issueds that occured when DBMS could not process a complex request. |
| Development tools. | During configuration merging and during configuration repository operations, the platform does not perform refactoring operations that are normally performed when configuration objects are renamed or deleted. | During configuration merging and during configuration repository operations, the platform performed refactoring operations that were normally performed when configuration objects were renamed or deleted. | Eliminated unexpected system behavior. Operations whose results were ignored are not performed. |
| 1C:Enterprise script. | If an object is passed to a method written in 1C:Enterprise script and its set of properties is changed during the method execution but the property names are not changed, the object property calls are executed correctly. In particular, when a method being executed adds a property, calls of other properties are executed correctly. If any property names are modified, object property calls might not be executed correctly. This change is not implemented in 8.3.5 compatibility mode. | If an object was passed to a method written in 1C:Enterprise script, the method called object properties by their numbers, which were defined at the moment the method was called. If a property number was changed during the method execution (for example, a new property was added), this was not taken into account and the property call was performed using the old number. | Improved system reliability and reduced chance of errors when a set of properties is changed during method execution. |
| Managed forms. | In the thin client, formatted strings that are defined during the generation of a drop-down list are displayed accordingly to their formatting if the text box is linked to an attribute of complex type and this attribute has the Undefined value. | In the thick client, formatted strings that were defined during the generation of drop-down lists were displayed without formatting if the text box was linked to an attribute of complex type and this attribute had the Undefined value. | Eliminated unexpected system behavior. |
| Web client. Managed forms. | In the web client, drop-down lists have the same color scheme as in other client applications. | In the web client, drop-down lists had a color scheme different from the color scheme used in other client applications. | In the web client, drop-down list appearance is uniform with other client applications. |
| Web client. | In the web client, the appearance of the following interface items is almost identical to their appearance in the thin client:
| In the web client, the appearance of the following interface items was different from their appearance in the thin client:
| Uniform client application appearance. |
| Command interface. | When a user command group is deleted, standard commands that belong to the group are automatically moved to the default standard group specified for those commands. This change is not implemented in 8.3.6 compatibility mode. | When a user command group was deleted, standard commands that belonged to the group were no longer available in the command interface. | Eliminated unexpected system behavior. |
| Event log. | The UnloadEventLog() method truncates the event time passed to it to an integer number of seconds. When a filter by time is applied to the event log (UnloadEventLog(), CopyEventLog(), or ClearEventLog() method), an event is included in the result even if the millisecond part of the actual event time exceeds the millisecond part of the time specified in the filter. | The UnloadEventLog() method provided the event time with millisecond accuracy. When a filter by time was applied to the event log (UnloadEventLog(), CopyEventLog(), or ClearEventLog() methods), an event was included in the result only if the exact condition was met (including the millisecond part). | Eliminated unexpected system behavior. The behavior of the .lgd log is uniform with that of the .lgf log (regarding the event time presentation and filter functionality). |
| Print tools. Spreadsheet documents. | The algorithm that calculates spreadsheet document column width for printing is modified. The printed document column width more closely matches the on-screen column width. The chance is noticeable in spreadsheet documents with background pictures. This change is not implemented in 8.3.5 compatibility mode.
| For spreadsheet documents, the printed document column width did not exactly match the on-screen column width.
| Improved print layout of spreadsheet documents. |
| Regional settings. | For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, and 69-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers. | The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, and 69-FZ. | The time offset changes introduced by the new law are implemented. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Internet-enabled functionality. | Future 1C:Enterprise versions will not support NSS certificates and related objects, regardless of the compatibility mode. The NSSSecureConnection object will be unavailable for use in 1C:Enterprise script and in thin client HTTPS connection settings. | 1C:Enterprise system supports NSS certificates. | Future platform versions will not support NSS certificates. |
| Automated testing. | For the TestedFormGroup object, the CurrentVisible() function returns False if the object is linked to form group, which is inactive page located in a page group where tabs are not displayed. This change is not implemented in 8.3.5 compatibility mode. | For the TestedFormGroup object, the CurrentVisible() function returned True if the object was linked to a form group, which was an inactive page located in a page group where tabs were not displayed. | The automated testing feature emulates the system functioning and provides form item status data more accurately. |
| Managed forms. | For managed form attributes of spreadsheet document, graphical schema, and text document types, calling the Show() method raises an exception. This change is not implemented in 8.3.5 compatibility mode. | The system behavior depended on the attribute location on a form and the client application type:
| Unified behavior of various objects in different client applications. |
| Managed forms. | In the thin and thick clients, buttons (or hyperlinks) located in managed forms become unavailable when commands (or hyperlinks) linked to these buttons become unavailable. This change is not implemented in 8.3.5 compatibility mode. | In the thin and thick clients, buttons (or hyperlinks) located in managed forms stayed available even when commands (or hyperlinks) linked to these buttons were unavailable. | The system behaves as expected. Unified system behavior in different client applications. |
| Managed forms. | When an item is created in the drop-down list of a text box, you can verify whether the created item matches the choice parameters used for opening the new item form. If the item does not match the choice parameters, a diagnostic message is displayed and the created item is not placed in the text box. The verification is implemented for managed form extensions for objects, catalogs, documents, charts of characteristic types, business processes, and tasks. The following features are implemented:
The ChoiceParameters and ChoiceAvailable properties of the managed form extension are not available in version 8.3.5 compatibility mode. | A new item that did not match the choice parameters specified for a text box could be created and selected in the text box. | Reduced chance of creating items (from a text box choice list) that do not match the choice parameters specified for the text box. |
| Managed locks. | The Period field whose value is specified in a periodic information register record set filter is included in the set of managed lock fields for read and write operations on record set data. This change is not implemented in 8.3.5 compatibility mode. | The Period field was not included in the set of managed lock fields for read and write operations on periodic information register record set data. | Improved user experience for periodic information register operations. Reduced chance of deadlocks. |
| Common attributes / Data separation. Information registers. | When an information register data set is recorded, the default values of independent and shared separators that include the information register are replaced by the separator values set in the current session. If a separator value is not identical to the default value of that separator type or is not equal to the separator value set in the current session, an error is generated. This change is not implemented in 8.3.5 compatibility mode. | When an information register data set was recorded, the default values of independent and shared separators that included the information register were always replaced by the separator values set in the current session | Eliminated unexpected system behavior. |
| Internet-enabled functionality. | When the InternetMail object is used for interaction with a Microsoft Exchange server, if the filter criterion string value (the Filter parameter of the GetHeaders() and GetUIDL() methods of the InternetMail object) only includes US-ASCII characters, the platform notifies the Exchange server about this in addition to passing the string to the server. Otherwise the platform passes a UTF-8-encoded string. If the filter criterion string value passed to the Exchange server contains not only US-ASCII characters (for example, it includes Cyrillic characters), an error is generated. This change is not implemented in 8.3.5 compatibility mode. | The GetHeaders() and GetUIDL() methods of the InternetMail object always returned an empty array when a string value of the Filter parameter was used in interactions with Microsoft Exchange. | Improved compatibility with Microsoft Exchange during operations with the InternetMail object. You can search in the filter criterion string if all its characters belong to the US-ASCII encoding. |
| Internet-enabled functionality. | The libetpan library is used to work with IMAP, SMTP, and POP3. This change is not implemented in 8.3.5 compatibility mode. | The UW IMAP toolkit library was used to work with IMAP, SMTP, and POP3. | Improved performance and stability of email management features. |
| Internet-enabled functionality. | During the creation of an InternetProxy object on Linux operating systems, if the DefaultProxy constructor parameter value is True and the platform cannot find the file inetcfg.xml, the constructor uses the values of the following operating system environment variables: http_proxy, https_proxy, ftp_proxy, ftps_proxy, and all_proxy. The methods of the HTTPConnection and FTPConnection objects do not attempt to determine the proxy server settings. Instead, they use the settings stored in the Proxy property of the respective object. For the Set() method of the InternetProxy object, the User and Password parameters are implemented. For the InternetProxy object, the User and Password methods are implemented. The User and Password properties of the InternetProxy object are declared obsolete, they are suported for compatibility purposes. This change is not implemented in 8.3.5 compatibility mode. | Environment variables were never used for creation of InternetProxy objects on Linux operating systems. If the proxy server parameters were not specified during the creation of HTTPConnection and FTPConnection objects, methods of these objects attempted to retrieve the proxy server settings from environment varaibles. | Eliminated the difference in platform behavior on Windows and Linux operating systems. Eliminated unintuitive platform behavior where methods of HTTPConnection and FTPConnection objects attempted to determine the proxy server settings. |
| Client application. | Idle handlers are not called while a client application is locked using the LockApplication() global context method or the Temporary lock command. This change is not implemented in 8.3.5 compatibility mode. | Locking a client application using the LockApplication() global context method or the Temporary lock command did not affect the execution of idle handlers. | Increased system security. |
| xBase support. | If an error occurs during a .dbf file operation performed using the XBase object, an exception is generated. This change is not implemented in 8.3.5 compatibility mode. | If an error occurred during a .dbf file operation performed using the XBase object, dialog boxes were generated. | Eliminated scenarios that looked as if the platform stopped responding (for example, errors generated by .dbf file operations at 1C:Enterprise server side). |
| Managed forms. | For the TypeLink object constructor, you can specify the first parameter (DataPath) as an empty string. | The TypeLink object constructor did not accept an empty string as the DataPath parameter value. | You can clear the TypeLink property of a managed form field by replacing its value with a new object of that type that does not have the data path specified. |
| External data sources. | For the ExternalDataSourceTableObject, the GetChangeableFields() and SetChangeableFields() methods are implemented. These methods are intended both for restricting the list of writable external data table fields and for expanding that list with fields have the read-only flag set in the configuration (the ReadOnly property set to True). The GetFieldsToWrite() and SetFieldsToWrite() methods are declared obsolete, they are supported for compatibility purposes. | The GetFieldsToWrite() and SetFieldsToWrite() methods only provided the option to reduce the number of fields that were recorded to external data source tables. The option to record data to fields that are marked as read-only in Designer was not provided. | The platform supports custom algorithms for external data source management. For example, data that is normally not recorded to external data source table fields can now be recorded using a custom algorithm. |
| Administration tools. | When a list of infobases is updated or when a client application distribution kit is downloaded via the Internet, the root certificates of certification authorities are obtained from the Windows certificate store. | When a list of infobases was updated or when a client application distribution kit was downloaded via the Internet, the root certificates of certification authorities were only obtained from the cacert.pem file. | Improved usability of self-signed certificates in the enterprise environment. |
| Server clusters. | You can specify the user on whose behalf the cluster manager (rmngr) is started, and it can be different from the user on whose behalf the cluster agent (ragent) is started. You can specify users on whose behalf the cluster manager (rmngr) and working processes (rphost) is started for each cluster on a given computer. You can specify a custom cluster register directory for each cluster manager (rmngr) on a given computer. The following parameters and parameter groups are implemented for the swpuser.ini file:
| Only the user on whose behalf the working process (rphost) was started could be changed. | You can increase server cluster security in scenarios like this: service users use their own applied solutions, external data processors, and add-ins whose access to the server cluster computer infrastructure should be restricted. |
| Data access restrictions. | Access restriction template parameters that are specified in comments are not replaced by actual values when the template is applied. This change is not implemented in 8.3.5 compatibility mode. | Access restriction template parameters that were specified in comments were not replaced by actual values when the template was applied. | Increased stability of the access restriction system in some scenarios. |
| Data composition system. | The option to use nested reports during the export of data composition result to a value collection is implemented. Columns with duplicate names are never created during the export. This change is not implemented in 8.3.5 compatibility mode. | The option to use nested reports during the export of data composition result to a value collection was not available. The check for duplicate column names was never performed during the export, so columns with duplicate names might be created. | Extended data composition system functionality. |
| Data composition system. | When additional data is displayed for hierarchical records, hierarchical record data is used. This change is not implemented in 8.2.16 compatibility mode.
| When additional data was displayed for hierarchical records, the detailed record data was used. | Reports display expected data: if a report contains a table with hierarchical groupings in its rows, the data obtained from the hierarchical records is displayed in the columns of additional data for hierarchical grouping rows, not from the detailed records, as it was implemented earlier. |
| Data composition system. | The value assigned to the Text conditional appearance parameter, which is enabled, is applied to fields of predefined grouping templates and fields of data composition system reports. This change is not implemented in 8.3.5 compatibility mode. | The value assigned to the Text conditional appearance parameter, which was enabled, was not applied to fields of predefined grouping templates or fields of data composition system reports. | Predefined grouping templates can be used together with the Text parameter of data composition conditional appearance. |
| Data composition system. | The appearance of cells that store parent grouping fields is based on the field expressions obtained for the current grouping. This change is not implemented in 8.3.5 compatibility mode. | The appearance of cells that stored parent grouping fields was based on the field expressions obtained for the parent grouping. | The cell appearance is formed as expected. |
| Dynamic lists. | If the platform cannot generate the list of available dynamic list settings, an exception is generated and the form is not generated. This change is not implemented in 8.3.5 compatibility mode. | If the platform could not generate the list of available dynamic list settings, no exceptions were generated and the managed form continued functioning as if the dynamic list data source did not have any fields available. All of the form items related to dynamic list data disappeared from the managed form. | Improved error diagnostics during dynamic list operations. |
| Data composition system. | The data composition template composer uses detailed data set fields for hierarchical grouping records. You can use the EvalExpression() function for getting hierarchical record values within aggregate functions. This change is not implemented in 8.3.5 compatibility mode. | The data composition template composer used hierarchical data set fields for hierarchical records (provided that the fields were available in the set). | You can use all detailed record fields in aggregate functions calculated for hierarchical records. |
| 1C:Enterprise script. | The FindMarkedForDeletion() method only processes data available to the current user. In the Syntax Assistant, the descriptions of the FindByRef() and DeleteObjects() methods are modified to describe their actual behavior. This change is not implemented in 8.3.5 compatibility mode. | The FindMarkedForDeletion() method did not check data access rights. If access was denied, a run-time error was generated. In the Syntax Assistant, the descriptions of the FindByRef() and DeleteObjects() methods did not describe their actual behavior. | The generation of run-time errors during the search for objects marked for deletion is eliminated in scenarios where the user does not have access rights for all objects involved in the search. The description of the system behavior is now correct. |
| Managed forms. | In the thin client, in the OnOpen managed form event handler, if the Cancel parameter is set to TRUE, the OnClose event handler and the notification set in the OnCloseNotifyDescription managed form property are not called. This change is not implemented in 8.3.5 compatibility mode. | In the OnOpen managed form event handler, if the Cancel parameter was set to TRUE, the OnClose event handler and the notification specified in the OnCloseNotifyDescription managed form property had the following behavior:
| Uniform system behavior across multiple client applications. |
| Automated testing. | New automated testing features:
The GetCurrentAreaText() method of the TestedFormField is declared obsolete. It is recommended that you use the GetAreaText() method of the TestedFormField object. In the event of unexpected shutdown of a client application the user actions are automatically recorded to the user action log (provided that the user action log recording is enabled). A dump is also recorded to the dump directory. The data processor that converts the log of user actions to a 1C:Enterprise script scenario is updated URL2. | Operations with performance indicators were not supported, as well as managed form table and managed form group operations. Progress bar fields, track bar fields, and the Tumbler radio button field type were not supported. In the event of an unexpected shutdown of a client application, the user actions were not recorded to the user action log and the accumulated action log was lost. | New automated testing features. Reduced number of manual operations during the testing. |
| Data display. | In sessions that do not have user interface (background and scheduled jobs, web services, and so on), the BriefErrorDescription() and DetailErrorDescription() method generate results that exactly match the results provided by these methods in managed application client sessions. This change is not implemented in 8.3.5 compatibility mode. | In sessions that did not have user interface (background and scheduled jobs, web services, and so on), the BriefErrorDescription() and DetailErrorDescription() methods generated results that exactly matched the results provided by these methods in ordinary application client sessions. | Eliminated unexpected system behavior. |
| Common objects. | When a configuration is saved, a check for style elements whose names match the values of the corresponding system value sets is performed:
If such elements are found, an error is displayed and the configuration is not saved. | When a configuration was saved, a check for style elements whose names matched the values of the corresponding system value sets was not performed. | Eliminated unexpected system behavior. Eliminated situations where two values with the same name were present in a single system value set whose values were connected to style elements. |
| Internet-enabled functionality. | In the parsing of Internet mail messages, the message validity check is implemented. The check is available both for messages received from the server and during the generation of outgoing messages using the SetSourceData() method of the InternetMailMessage object. For the InternetMailMessage object, the ParseStatus property is implemented. In the technological log, the <MAILPARSEERR> event is implemented. This change is not implemented in 8.3.5 compatibility mode. | Detection of invalid mail messages resulted in an unexpected shutdown. | Improved system reliability during email operations in scenarios where email messages being processed contain errors. |
| Internet-enabled functionality. | For the SetBodyFromString() method of the HTTPRequest and HTTPServiceResponse objects, the UseBOM parameter is implemented. It manages the availability of BOM in the specified text. In version 8.3.5 compatibility mode, the BOM mark is added by default. | This feature was not provided. | Simplified interaction with systems that do not expect BOM in HTTP queries. |
| Ordinary forms. | The Name property of ordinary form items is read-only. This change is not implemented in 8.3.5 compatibility mode. | The DBMS request based on the VALUETYPE function was more complicated. | Eliminated issues that occurred when a DBMS could not process a complex request. |
| OData operations. | The list of functions supported by OData standard interface is revised. The description of mod function is removed from the documentation. | The documentation stated that the mod function was supported by standard Odata interface. |
The documentation describes the actual platform behavior. |
| File operations. Client application. | Both in thin and thick clients, when a file is obtained interactively using the GetFile() method with the "open file" option, the search for associated application is performed (by the file extension). If an associated application is found, a system dialog box for selecting an application to open the file is displayed. If an associated application is not found, getting the file is canceled. In the web client, the behavior is not changed, so it is now uniform with the behavior of thin and thick client applications. | In both thin and thick clients, when a file was obtained interactively using the GetFile() method with the "open file" option, the search for associated application was performed (by the file extension). If an associated application was found, the file was opened using this application. If an associated application was not found, getting the file was canceled. The web client displayed a system dialog box for selecting an application to open the file. | Eliminated the difference in the web client, thin client, and thick client behavior. |
| File operations. Web client. | The File object constructor with a file name parameter is available regardless of the Synchronous call usage mode for extensions and add-ins configuration property value. Configuration verification and refactoring no longer treat the File constructor with a file name parameter as a legacy synchronous call. Execution of this constructor no longer causes an exception in 1C:Enterprise mode. In the web client execution of File constructor with a file name parameter no longer requires installing the file system extension. The descriptions of File constructor without parameters and File.BeginInitialization() methods are removed from the documentation. The File.BeginInitialization() method is supported for compatibility purposes. | The File object constructor with a file name parameter was available when the Synchronous call usage mode for extensions and add-ins configuration property was set to Use or Use with warnings. Configuration verification and refactoring treated the File constructor with a file name parameter as a legacy synchronous call. If the Synchronous call usage mode for extensions and add-ins configuration property was set to Do not use, execution of this constructor caused an exception in 1C:Enterprise mode. In the web client execution of File constructor with a file name parameter required installing the file system extension. | Operations with the File object that do not require access to the file system (such as getting a file extension) no longer require installing the file system extension. |
| Internet-enabled functionality. | IDs of email messages received using IMAP do not depend on whether you specify the mailbox by name or use the default one. Once you disable the compatibility mode, the option to map messages to each other using the InternetMailMessage.MessageID property becomes available. This change is not implemented in 8.3.5 compatibility mode.
| IDs of email messages received using IMAP did not depend on whether you specified the mailbox by name or used the default one. | You can unambiguously identify each email message, regardless of the selected mailbox. This simplifies the algorithm for distinguishing between received and new messages.
|
| Web client. System requirements. | The list of supported web browsers includes Google Chrome for x86-64 architecture. The platform uses 32-bit versions of add-ins and extensions with this browser. | The list of supported web browsers did not include Google Chrome for x86-64 architecture. | Extended list of supported web browsers. |
| Data composition system. | When columns of a data composition system report template are output to a value tree or a value table, invalid characters are removed from column names. This change is not implemented in 8.3.5 repository compatibility mode.
| When columns of a data composition system report template were output to a value tree or a value table, the column names matched the field names. | Eliminated unexpected system behavior. |
| Add-ins. | In the add-in development technology, Mozilla Firefox and Google Chrome support (for all Windows, Linux, and MacOS X architectures) is now uniform. The xulrunner utility is no longer required for building add-ins and is removed from the distribution kit. It is recommended that you build new installer packages (.msi and .sh) for Mozilla Firefox and create a new archive with version 40.* specified in the manifest. For support of earlier platform versions, also add legacy (.xpi) packages to the archive with version 31.0 specified in the manifest. The add-in development technology documentation and examples are updated accordingly. | Add-ins created for Mozilla Firefox and Google Chrome were different. The xulrunner utility was used to build Mozilla Firefox add-ins. | Support of add-ins for browsers that no longer support legacy add-in creation functions is implemented. |
| Predefined data. | The configuration check that is always performed before database configuration update includes a check for uniqueness of predefined item names. No duplicate predefined item names are allowed for any configuration object. If duplicate predefined items are found, this is reported to the message window but does not prevent the configuration update. | The configuration check that is always performed before database configuration update did not include a check for uniqueness of predefined item names. | Improved reliability of configuration updates for configurations that include predefined data. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. | Faster startup of mobile applications. | Insufficient startup speed of mobile applications. | Improved usability of mobile applications. |
| Development tools. Data display. | The set of data stored in picture archives that include variants is modified. The manifest file manifest.xml, which is included in the archive, stores descriptions of picture variants. Custom names for pictures designed for specific display resolutions are allowed. Template pictures (pictures that have transparent background, which is displayed using the current text color) are supported. It is recommended that you store template pictures in PNG format. | Picture variants were described by their file names. A manifest file was not included. Template pictures were not supported. | You can use more of mobile application system appearance design features. |
| Full-text search. | In the mobile platform, you can use full-text search. The full-text search index is updated automatically upon data modification. The search is not morphological. Additional dictionaries and text extraction are not supported. The index is updated when the mobile platform is not performing any server calls or background jobs. | The mobile platform did not support full-text search. | You can use full-text search in the mobile platform. |
| System requirements. | The Google Play store now considers mobile applications optimized not only for phones but also for tablet PCs. The change takes effect when you rebuild the mobile application using the new mobile platform and then republish the application to Google Play. | The Google Play store considered mobile applications optimized for phones only. | Tablet PC users can see mobile applications in the default Google Play list. Searching by title is not necessary. |
| Calendars. | During the creation of data composition fields, if they include calendar or contact data, you can specify just a field name, without specifying its data type. Creation of data composition fields with data types specified is supported forn compatibility purposes. | During the creation of data composition fields, if they included calendar or contact data, specifying the full field name with its data type was required. | The system behaves as described in the documentation. Simplified interaction with calendars and contacts in some scenarios. |
| Window management. | The option to handle the change of mobile device display parameters is now available. The OnChangeDisplaySettings event handler is implemented. The event occurs when the client application display parameters are changed. The Width and Height properties of the ClientDisplayInformation object store the actual values (which depend on the screen orientation). | This feature was not provided. The platform could not detect the changes of display parameters. The Width and Height properties of the ClientDisplayInformation object stored constant (canonical) values. | You can handle the display size changes caused by mobile device orientation changes or by connecting the mobile device to external displays. You can create applications with better usability. |
| Multimedia support. | Photo shoot and video recording quality control implemented (for Android only). Camera control for photo shoots and video recording is implemented. In the MultimediaTools object, for the PhotoSupported() and VideoRecordingSupported() methods, the CameraType parameter is implemented. In the MultimediaTools object, for the MakePhoto() method, the CameraType, Resolutions, Quality, and Monochrome parameters are implemented. For the MakeVideoRecording() method of the MultimediaTools object, the CameraType and Quality parameters are implemented. For the MultimediaTools object, the GetSupportedCameraResolutions() method is implemented. | These features were not provided. | Extended capabilities for mobile device cameras. |
| Printing. | On the mobile platform, you can print spreadsheet documents. Printers that use PCL3 and ZPL protocols are supported. WiFi and Bluetooth are used for connecting to printers (only for Android). | This feature was not provided. | You can print spreadsheet documents from mobile applications. |
| Configuration properties. |
The documentation now contains the description of the mobile platform compatibility mode:
The documentation also describes the correspondence of PC platform versions and mobile platform versions. |
The mobile platform compatibility mode was not described in the documentation. | The documentation is updated with the latest information. |
| Managed forms. Development tools. | Asynchronous dialog box operations are available to mobile platform developers. Selecting Mobile device in the Use purposes configuration property does not change the Modality usage mode configuration property. | Only synchronous dialog box operations were available to mobile platform developers. When the Mobile device value was selected in the Use purposes configuration property, a request to confirm the change of the Modality usage mode configuration property value was displayed (only if the change was required). | Applied solution development for the mobile platform is simplified. Developers no longer need to support two sets of dialog box operations, one for the mobile platform and the other one for the PC platform. |
| 1C:Enterprise script. | In the mobile platform, the language of generated names of form items, form attributes, form commands, form parameters, and structure properties is defined by the value of the Script variant configuration property. | In the mobile platform, the language of generated names of form items, form attributes, form commands, form parameters, and structure properties was English only if the default configuration language was English. Otherwise it was Russian. | The mobile platform behavior is uniform with the PC-based platform behavior. |
| Development tools. | Push notification and local notification support is implemented. This feature relies on Apple push notification service and Google Cloud Messaging. The option to display the number of notifications that are not yet processed is implemented: mobile application icon badges (for iOS) or status bar notifications (for Android). Devices running Android 4.1 or later display the notifications diferently from devices with earlier Android version. A dedicated service provided by 1C Company is implemented to simplify the development of notifications for applied solutions that run on the PC platform. Notification senders can choose between using this service, Apple push notification service, and Google Cloud Messaging. For the mobile platform, the DeliverableNotifications global context property, the DeliverableNotificationManager object, and the DeliverableNotification object are implemented. For the PC platform, the DeliverableNotificationSend global context property, the DeliverableNotificationSendManager object, and the DeliverableNotification object are implemented. For mobile applications, the Push notifications and Local notifications permissions are implemented. The mobile application builder supports building mobile applications that use notifications. | This feature was not provided. | You can use standard user notifications in mobile applications. Notifications can be generated either by a mobile application on the mobile device (local notifications) or by an applied solution running on a PC (push notifications). |
| Dynamic lists. | Improved performance of dynamic list opening. The process of loading list data now has a visual presentation. | The process of loading dynamic list data had no visual presentation and took more time. | Optimized dynamic list operations. |
| Internet-enabled functionality. | The following mobile platform features support secure connection (HTTPS):
Support of IMAP email operations (including secure connection) is implemented. Support of client certificates and certification authority center certificates stored in files is implemented. In the mobile platform the FileClientCertificate, FileCertificationAuthorityCertificates, and OpenSSLSecureConnection objects are implemented, together with the corresponding properties of the HTTPConnection, InternetMailProfile, and InternetMail objects. | The mobile platform did not support the following features:
Client certificate operations and authority center certificate operations. |
The mobile platform supports secure operations with email and with other resources. |
| Error handling. | In the mobile platform for developers, you can obtain error details (the Details button in the error dialog box) and information for technical support (in the About 1C:Enterprise window). | Error details and information for technical support were not available in the mobile platform. | Improved issue diagnostics in the mobile platform for developers. |
| Interface. | New interface for the mobile platform client application, with a large number of improvements. The most significant changes are:
| The mobile application interface was similar to managed application interface version 8.2. | The mobile application interface meets the modern requirements to mobile interfaces. Improved mobile application usability. New interface uses the same color scheme and style as the Taxi interface, at the same time it is optimized for mobile devices. |
| Managed forms. | For devices that run Android operation system, predictive text input in multiline text boxes is implemented (with optional automatic correction of the entered text). This feature is available when it is enabled in the virtual keyboard settings. | This feature was not provided. | Improved usability for text input. |
| Mobile application builder. | In mobile application builder, you can publish an application to Apple App Store and Google Play directly from the builder. The mobile application builder help describes how to connect to Google Play Market. | This feature was not provided. Mobile applications required manual publishing. | Publishing mobile applications to Apple App Store and Google Play is simplified. |
| Dynamic lists. | The option to specify dynamic list settings using 1C:Enterprise script is implemented. The DynamicList.SettingsComposer property is now available on the mobile platform. The following objects are implemented: DataCompositionSettingsComposer, DataCompositionUserSettings, and DataCompositionSettings, as well as their constructors and methods. Their methods are not available on the mobile platform. The DataCompositionUserSettingsItemCollection object is implemented. | This feature was not provided. | Работа с настройками динамического списка на мобильной платформе приближена к возможностям платформы для персонального компьютера. |
| Dynamic lists. Interface. | When the selection mode is on, dynamic list rows that represent parent groups have left arrows displayed. | When the selection mode was on, dynamic list rows that represented parent groups did not have left arrows displayed. | Improved navigation of hierarhical dynamic lists in the selection mode. |
Version 8.3.5 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.4 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, 8.2.16, 8.3.1, 8.3.2, and 8.3.3. | In version 8.3.5 you can run configurations created in version 8.3.4 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.5 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.4 for working with the infobase even after the transition to version 8.3.5. 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. | In Designer, new icons for external data source tables and cubes are implemented. | Pictures for external data source tables and cubes were different. | Icons for external data source tables and cubes are uniform with other platform pictures. |
| Development tools. | In Designer, you can filter objects by parts of names, synonyms, comments, or presentations. The filter is available in the following windows:
For the Subsystem configuration object, a quick filter is implemented in the configuration window. The filter is available from the Subsystem objects context menu command of the object. In the configuration window, you can set a quick filter for configuration repository objects locked by the current user. | This feature was not provided. Only filtering by objects included in subsystems was available. | Improved usability for developers. |
| Interface. | 1C:Enterprise script provides tools for managing start page (desktop) form contents and positions. The StartPageForms object is implemented. For the StartPageSettings object, the GetForms() and SetForms() methods and the default constructor are implemented. The global context method RefreshInterface() rebuilds the start page (desktop) based on the settings from the system settings storage. | The StartPageSettings object stored the differences between the start page (desktop) settings of the client application and the settings specified in Designer. 1C:Enterprise script did not provide tools for managing form contents and positions. | You can manage contents and positions of the client application start page (desktop) forms using 1C:Enterprise script. |
| Administration tools. | For the Purpose column of value table returned by the GetDBStorageStructureInfo() method, new purposes are specified. The full list of database table purposes is available in the description of the GetDBStorageStructureInfo() method in the Syntax Assistant. | The list of table purposes did not fully describe the current database schema. | The purposes of database scheme tables are described more clearly. |
| Data exchange. | For exchange plans, the ThisNode standard attribute is implemented. It specifies whether the exchange plane node describes the current infobase. For the ExchangePlanObject object, the DataExchange property is implemented. Only the Load property can be used in this property. The DataExchange property is used for disabling the uniqueness check of the ThisNode item when exchange plan items are edited or deleted. This change is not implemented in 8.3.4 compatibility mode. | The ThisNode standard attribute was not available in exchange plans. Replacing the exchange plan node that described the current infobase was impossible. The ExchangePlanObject object did not have the DataExchange property. | You can define ThisNode items in a distributed infobase in a session that does not use separators. You can replace the data item that describes the current infobase in the exchange plan. |
| Managed forms. | For managed form text boxes, the EditTextChange event is implemented. This event occurs when one of the following actions modifies the text box content:
The event occurs before the AutoComplete event. | There was no event that occurred when text box content was modified. Actions triggered by this modification could be performed in the AutoComplete event handler (with limitations). | In managed forms, complete implementation of the following scenario is available: text being typed in a text box is used as a filter parameter in the linked dynamic list. |
| Development tools. | New features in the module editor:
Commands that perform these functions are located in the Refactor submenu of the module text editor context menu and in the Configuration section of the Designer main menu. | These features were not provided. | Improved efficiency of routine operations performed by developers. |
| Managed forms. | In text boxes that display values of StandardBeginningDate type, in the date input mode, the AutoComplete (on value input) and TextEditEnd (on generating a value based on the input string) event handlers are implemented. This change is not implemented in 8.3.4 compatibility mode. | In text boxes that display values of StandardBeginningDate type, in the date input mode, the AutoComplete (on value input) and TextEditEnd (on generating a value based on the input string) event handlers were not implemented. | The behavior of text boxes linked to values of StandardBeginningDate type in the date input mode is identical to behavior of text boxes linked to values of Date type. |
| Client application. | The option to follow a navigation link during client application startup is implemented, with the navigation link passed as a parameter. This feature is implemented for the 1C:Enterprise launcher, thin and thick clients, the GotoURL() method, the standard full-text search form, and the new Go to link command in the startup window. Only external navigation links (which contain infobase connection settings) are supported. When following a link, the platform attempts to use running client application instances connected to the infobase specified in the navigation link. In 8.3.4 version compatibility mode, the GotoURL() method is not modified. The /url startup option is implemented for the launcher, thin client, and thick client. | This feature was not provided. Users could only follow external links when they accessed the infobase using the web client. | Simplified access to infobase data if a link to this data is provided by third-party tools, such as email. |
| Internet-enabled functionality. | For the InternetMailMessage object, the GetSourceData(), SetSourceData(), and GetSourceText() methods are implemented. These methods are intended for getting original email messages without changing the encoding and processing source texts of messages whose encoding was changed. | This feature was not provided. | You can save email messages to files and load them from files, provided that they comply with RFC 822 URL9, and you can also perform custom processing of email message source texts. |
| Data display. Charts. | Animated charts are implemented. The Animation property is implemented for the Chart object. The ChartsViewSettings object is implemented. The chart display settings are stored in the system settings storage. This change is not implemented in 8.3.4 compatibility mode. | This feature was not provided. | More chart display options are available. |
| Web services and HTTP services. Data exchange. Database operations. Web client and web service publishing tools. | 1C:Enterprise infobase data can be retrieved and modified using the OData protocol (read more) v3 (read more). The following data presentation is supported: atom-xml. Enabling this feature does not require modification of applied solution, it is performed using a web server publication. The enableStandardOData attribute is implemented for <point> tag in the default.vrd file. In 8.3.4 version compatibility mode, all configuration objects that support OData protocol are available through this interface. If the compatibility mode is disabled, the access to objects is managed using the SetStandardODataInterfaceContent() method. | Universal access to 1C:Enterprise infobase data was only available on Windows operating systems and was based on COM/OLE features. It was not available on Linux. The option to access data using web services implemented in applied solutions was also available. | Extended integration features for 1C:Enterprise data, including data access from external Linux systems, which does not require modification of applied solutions . |
| Configuration repositories. | Optimized selective comparison of forms, access rights, and command interface fragments in scenarios where the configuration repository is located on a network drive or on a repository server. Local data cache is implemented for configuration repositories. You can manage the size and location of local and global repository caches using the configuration repository administration settings dialog box or cfgrepo.conf configuration files. These files are located in the cfgrepo subdirectory of the infobase service files directory (for the local cache) or in the configuration repository directory (for the global cache). The following features are implemented for batch Designer startup mode:
| The selective comparison of forms, access rights, and command interface fragments lacked efficiency if the configuration repository was located on a network drive or on a repository server. Editing the size and location of the global configuration repository cache was not available. The local cache for configuration repository data was not available. | Selective comparison and some other configuration repository features are optimized. You can manage the size and location of configuration repository data cache. |
| Dynamic lists. | Extended search capabilities in tables that display dynamic lists. A standalone search string box that provides full-text search is implemented. Search by current cell value is available. The search history is implemented. The current search state is clearly visible. The search result includes items that have search words located both in a single column and in different columns. In each column, search by a single value is available (the Find in search results option is not supported). For automatically created forms that contain tables linked to dynamic lists, the set of items related to search in dynamic lists is modified (together with their appearance). The search dialog box layout is modified. The new FormItemAddition managed form item stores additional properties of form items. Extensions of form items intended for displaying a search string, a view status, and a search control are implemented. For the FormTable managed form item, the predefined items SearchString, ViewStatus, and SearchControl, and also properties SearchStringLocation, ViewStatusLocation, and SearchControlLocation are implemented. The search history is stored in the system settings storage with the following key: Common/TableSearchHistory/<Form name>.<Table name>. The SearchControl picture is added to the picture library. | Search in tables was performed using the search dialog box. The option to search a column by multiple values (the Find in search results check box) was available. The search dialog box had a different layout. There was no simple way to determine whether the search is applied to a table (except for checking the availability of the Cancel search button if it was present on the command bar). | The search in managed form tables is improved, it is clearly visible whether the search is applied to a table. |
| Web services and HTTP services. | Developers can create HTTP services in applied solutions. Developers can access HTTP request body, headers, and line. Publishing HTTP services is similar to publishing web services. To access HTTP services, use URLs of the following format: http://<host name>/<base name>/hs/<resourсe identifier>. You can create HTTP services in the Common/HTTP services branch of the configuration tree. The following objects are implemented: HTTPServices, HTTPService, HTTPServiceRequest, and HTTPServiceResponse. | This feature was not provided. Only access to web services implemented in the applied solution was available. | You can create services that have the following advantages over web services:
A different usage model (RESTful services). |
| Client application. Database operations. | The Hibernated session state is implemented, which is intended for preserving sessions after unexpected connection losses. Sessions that require licenses release the occupied licenses once they are hibernated. If a connection is assigned to a hibernated session, the session loses its Hibernated state. During the recovery from hibernation, sessions that require licenses attempt to obtain licenses. If a license cannot be obtained, the session is terminated. The option to set a timeout for automatic shutdown of hibernated sessions is implemented. If a connection to the client is closed by the 1C:Enterprise server, the session is hibernated(instead of being terminated). For the ISessionInfo object, the following properties are implemented: Hibernate, PassiveSessionHibernateTime, and HibernateSessionTerminateTime. New global context methods are implemented: SetPassiveSessionHibernateTime(), GetPassiveSessionHibernateTime(), SetHibernateSessionTerminateTime(), and GetHibernateSessionTerminateTime(). The hibernation timeout and the timeout for closing hibernated sessions can be set in Designer, in the infobase parameters dialog box. | This feature was not provided. If a client application was inactive for 20 minutes, the session was closed. | In the client/server mode, in some scenarios the client application continues functioning even when the client computer stays in hibernation mode for a long time. |
| Data composition system. | In the data composition system, new options are implemented for comparison of string data: BeginsWith, NotBeginsWith, Like, and NotLike. | This feature was not provided. | Extended features for filtering by string expressions in reports created using the data composition system and in dynamic lists. |
| Applied objects. | For catalog, chart of characteristic types, chart of accounts, chart of calculation types configuration objects, the GetPredefinedNames() method is implemented. | This feature was not provided. | You can get the flag indicating that a configuration object has predefined items, as well as the full list of predefined item names. Using this list, you can check whether data items are set for all predefined items. |
| External data sources. | You can write data to external data source tables. This feature is intended for integration with other applications, external sources should not be used as applied solution data storages. | This feature was not provided. External data source table data was read-only. | New options for integration with information systems and databases. |
| Queries. | A query wizard for managed mode is implemented. For the QueryWizard object, the Show() method is implemented. The following pictures are added to the picture library: Rename, Attribute, Dimension, Resource, NestedTable, QueryWizardShowChangesTables, QueryWizardCreateNestedQuery, QueryWizardCreateTempTableDescription, QueryWizardReplaceTable, QueryWizardTableParameters, QueryWizardCreateTempTableDropQuery QueryWizardTempTableDescription, QueryWizardGroupTempTables, QueryWizardTempTable, QueryWizardNestedQuery, and CustomExpression. | This feature was not provided. | New features for using queries in managed applications. |
| Queries. | An object model intended for modification of query texts is implemented. The QuerySchema object is implemented. | This feature was not provided. |
You can modify queries from 1C:Enterprise script without analyzing the query text. |
| Spreadsheet documents. | You can insert pictures in spreadsheet document cells. You can specify text position relative to the picture in a cell (or an area of cells) of a spreadsheet document. A picture is linked to a cell where it is inserted. For the SpreadsheetDocumentRange object, the following properties are implemented: Picture, PictureSize, PictureHorizontalAlign, PictureVerticalAlign, TextPositionRelativeToPicture, and PictureParameter. | Pictures could only be inserted in spreadsheet documents as images that were not linked to any specific cell (or an area of cells). | Improved usability of pictures in spreadsheet documents. |
| System requirements. | Alt Linux SPT 6.0 distribution kit is supported. | This distribution kit was not supported. | New Linux distribution kit is supported. |
| Data composition system. | For the DataCompositionFilter object, the default constructor is implemented. | This feature was not provided. | In a mobile application, you can set a filter for a list of contacts. |
| Event log. | The _$Data$_.TotalsMaxPeriodUpdate event with presentation Data.Modify maximum calculated totals period is implemented. The event is registered when the SetMaxTotalsPeriod() or SetMinAndMaxTotalsPeriods() method is called. The _$Data$_.TotalsPeriodUpdate event is used for compatibility purposes. | The _$Data$_.TotalsPeriodUpdate event was registered when the maximum totals period was set. | The event log displays actions that set the totals period more consistently. |
| Linux. Client application. | 1C:Enterprise searches for the ImageMagick library by name libMagickWand-6.Q16. | 1C:Enterprise did not search the ImageMagick library by name libMagickWand-6.Q16. | During the startup, 1C:Enterprise is not shut down if the ImageMagick library was renamed and then reinstalled. |
| DBMS operations. | Microsoft SQL Server 2014 DBMS is now supported. | Microsoft SQL Server 2014 DBMS was not supported. | New Microsoft SQL Server version is now supported. |
| Developer tools. | For the Technological log configuration file editor (read more) and User action log conversion (read more), data processors, which are distributed via 1c-dn.com, the English interface is implemented. Both data processors are rewritten using the English variant of 1C:Enterprise script. | The Technological log configuration file editor and User action log convertor data processors had Russian interface only. Both data processors were written using the Russian variant of 1C:Enterprise script. | Simplified usage and modification of the Technological log configuration file editor and User action log convertor data processors for non-Russian-speaking developers. |
| Development tools. | In the "dump configuration to files" feature, the approach to dumping standard attribute data is modified. Only attributes whose properties differ from the default values (for the given attribute) are dumped. Changing properties of a single standard attribute results in dumping all of the standard attributes of the configuration object. The same behavior is implemented for loading: if an XML file contains a description of a standard attribute, it is loaded to the configuration even if the description of the standard attribute contains only default values. An external data processor intended for deleting descriptions of standard attributes with default values from XML dump files is implemented. The data processor can be used only with files dumped by 1C:Enterprise version 8.3.5. You have to use it once before loading the dumped files back to the configuration.
| While dumping configuration files, standard attribute data was always dumped, even if all of the standard attribute properties had default values. | Reduced configuration file size. Reduced number of "different" objects found when comparing configurations after dumping and subsequent loading. |
| Predefined data. Applied objects. Common attributes / Data separation. | You can edit the flag that shows whether predefined data is initialized in a data area or in the entire infobase. The GetPredefinedDataInitialization() and SetPredefinedDataInitialization() methods are added for catalog managers, charts of characteristic types, charts of accounts, and charts of calculation types. This change is not implemented in 8.3.4 compatibility mode. | Editing the flag that shows whether predefined data is initialized in a data area or in the entire infobase was not available. | Extended capabilities for processing predefined data. You can inform the system at any time that predefined data in a data area or in the entire infobase is initialized (or not initialized). In a distributed infobase, when you remove infobase subordination to the master node, you can specify that all of the predefined data items are created in the infobase whose subordination is being removed. |
| System requirements. | Microsoft Windows Server 2012 R2 (x86-64) is now supported. | Microsoft Windows Server 2012 R2 (x86-64) was not supported. | New version of the Microsoft operating system is now supported. |
| Server clusters. Administration tools. | You can use an external utility for generating dumps when the platform stops responding. In the logcfg.xml file, the externaldump attribute of the dump element is implemented. The dumper.exe utility, which is now included in the platform delivery kit, is implemented. | Dumps were generated by the process that stopped responding. | Eliminated the issue where the system stopped responding while generating a dump for a process that stopped responding. |
| Data exchange. | The instructions for unbinding an infobase from the root node and restoring a configuration in a distributed infobase node, which take into account the specifics of predefined data usage, are available in the platform documentation. | This information was not available in the documentation. | The documentation contains recommendations for using distributed infobases that include predefined data. |
| Client application. Managed forms. | In thin and thick client applications, the system behavior based on the Modality usage mode configuration property value is modified. For thin and thick client applications, the EnableCheckModal startup parameter is implemented. If EnableCheckModal is not used, modal methods are executed without any warnings or exceptions. If EnableCheckModal is used, executing a modal method generates a warning or an exception (depending on the Modality usage mode configuration property value). When an applied solution is started from Designer, the EnableCheckModal parameter is automatically added to the applied solution command line (this behavior cannot be disabled). The web client behavior is not modified: the command-line parameter is not used. The web client always generates a warning or an exception (depending on the Modality usage mode configuration property value) when modal methods are executed. | The modal method behavior was based on the Modality usage mode configuration property value only. Depending on this property value, modal methods were executed with warnings or exceptions. This behavior could not be changed using command-line parameters. | You can use external data processors that include modal methods in applied solutions where modality is disabled. |
| System requirements. | Support of Microsoft Windows 8.x operating system is implemented. | Microsoft Windows 8.x operating system was not supported. | Extended list of supported operating systems. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application installation. | While the client application is being updated via the Internet, a dialog box displaying the progress of downloading the distribution kit from the server is being displayed. You have the option to cancel the download. | While the client application was being updated, the progress of downloading the distribution kit was not displayed. | Improved process of updating the client application using Internet services: the progress is displayed and the download can be canceled. |
| Client application. | The Help window is opened like any other form:
The help command bar is modified. The search is started either when the focus leaves the search text box or when the user clicks Find. | Help was always opened in a new window, regardless of the main application window interface settings. The help command bar had different content. The search started while the search expression was still being typed (during a pause in the typing). | The behavior of the Help window is unified with other forms. |
| Configuration installation. | New splash screen in the configuration installation wizard. | The configuration installation wizard used a different splash screen. | The configuration installation wizard and the platform installation wizard have uniform looks. |
| Client application. | If OpenID authentication is available in an infobase, once you run the thin client and select the infobase, the authentication dialog box will display the name of the last authenticated user. | The user name box in the OpenID authentication dialog box was always empty. | The user name box behavior is uniform for all authentication methods.
|
| Predefined data. | When a catalog, chart of characteristic types, or chart of accounts folder is marked for deletion, unmarked for deletion, or deleted, the platform checks whether the user has enough rights to access subordinate predefined objects. | When a catalog, chart of characteristic types, or chart of accounts folder was marked for deletion, unmarked for deletion, or deleted, the platform did not check whether the user had enough rights to access subordinate predefined objects. | The platform does not allow deletion of a catalog, chart of characteristic types, or chart of accounts folder if the folder contains a predefined item and the user does not have the right to delete that item interactively. |
| Web client. | When the web client is started in Google Chrome web browser on MacOS X operating system, the message that the web browser is not supported is not displayed. | When the web client was started in Google Chrome web browser on MacOS X operating system, the message that the web browser was not supported was displayed. | Improved usability of applied solution startup in the web client that is started in Google Chrome web browser on MacOS X operating system (the message is removed). Support of this web browser is subject to further discussion. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Common attributes / Data separation. File mode. | In separated infobases that run in the file mode, query execution is optimized. |
In separated infobases that ran in the file mode, query execution lacked efficiency. | Improved performance of separated infobases that run in the file mode. |
| Managed forms. | In some scenarios, forms are opened faster. | Opening forms was not optimized. | Improved system performance in some scenarios. |
| Database operations. | Improved performance of establishing a connection to an infobase that is running in the file mode and located on a network resource. | The performance of establishing a connection to an infobase that was running in the file mode and located on a network resource was insufficient. | For the second and following users, improved performance of establishing a connection to an infobase running in the file mode and located on a network resource. |
| 1C:Enterprise script. | Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties. | The performance of the following operations was insufficient: execution of 1C:Enterprise script methods and getting configuration object properties. | Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties. |
| Accounting registers. | Improved performance of writing to accounting registers for record sets that contains no more than 10 records. | When a record set with no more than 10 records was written to an accounting register, the writing performance was insufficient. | Optimized accounting register operations. |
| DBMS operations. Accounting registers. Common attributes / Data separation. | In the client/server mode with IBM DB2 or Oracle Database DBMS, improved performance of writing to accounting registers that are included in the contents of common attributes used as separators. | In the client/server mode with IBM DB2 or Oracle Database DBMS, the performance of writing to accounting registers included in the contents of common attributes that were used as separators was insufficient. | Optimized accounting register operations in the client/server mode with IBM DB2 or Oracle Database DBMS. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Defined types. | The list of types that can be included in defined types is significantly extended. You can use defined types in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators. The algorithm of the configuration check for correct usage of defined types is modified: a defined type is considered valid (in each usage instance) if all types that form the defined type are valid when the check is performed. The configuration check algorithm is not modified in 8.3.4 compatibility mode. | The list of types that could be included in defined types was significantly shorter. The configuration check was performed as follows: check whether the defined type only includes allowed types, and check whether the defined type is not included in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators. | New defined type usage options in applied solution development. Particularly, integration of applied solutions with third-party subsystems is now simpler. |
| Development tools. | The order of standard attributes in the standard attributes window and in the role settings is modified. The form wizard allows adding predefined data name fields to forms. | The list of standard attributes in the standard attributes window and in the role settings was not ordered. The form wizard did not allow adding predefined data name fields to forms. | Display of standard attributes is uniform with other system features. |
| Client application. | For text documents, the Save as command now saves the document encoding, provided that one of the following encodings is used: ANSI, OEM, UTF-8, or UTF-16. Otherwise, the UTF-8 encoding is set. Closing the Save as dialog box by clicking Cancel does not modify the encoding of the open document. This change is not implemented in 8.3.4 compatibility mode. | For text documents, the Save as command set the UTF-8 encoding for the document being saved, regardless of the encoding that was used when the document was opened. Closing the Save as dialog box by clicking Cancel set UTF-8 encoding for the open document. | Eliminated unexpected system behavior. |
| Managed forms. Dynamic lists. | In the Customize form dialog box, the DataVersion field cannot be added to a form. | In the Customize form dialog box, the DataVersion field could be added to a form. | Eliminated unexpected system behavior. |
| Background and scheduled jobs. | At the start of a background job, the SessionParametersSetting event handler is run after the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on). | At the start of a background job, the SessionParametersSetting event handler was run prior to the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on). | Eliminated unexpected system behavior. |
| Common attributes / Data separation. Information registers. Accumulation registers. Accounting registers. Calculation registers. | The configuration check and database configuration update include the check whether registers affecting a sequence are included in the same separator content as the documents included in the sequence. If a register affecting a sequence is included in separator content and a document included in a sequence is not included in the content of this separator, the separator is ignored when sequence boundaries are updated in 1C:Enterprise mode. | The check for correspondence between separators included in a document sequence and registers affecting this sequence was not performed. | Eliminated unexpected system behavior. |
| Temporary storages. | The volume of data transferred between the client and the server cannot exceed 4 GB (in the serialized form) in the following cases:
An attempt to transfer more than 4GB leads to an unrecoverable error. | During an attempt to transfer more than 4GB of data (in serialized form) to the server, the client application stopped responding. | Eliminated unexpected system behavior. |
| Internet-enabled functionality. | The cURL library is updated to version 7.32. It supports new options, such as downloading files with Cyrillic names from FTP servers. | The cURL library version 7.18.2 was used. | Resolved some issues of the previous library version. |
| XML and XDTO support. | If an error related to an attempt to write an invalid character to an XML object occurs at the server side, an unrecoverable error is not generated at the client side, and the user is not prompted to restart the client application. The error can be handled using the Try...Except syntax. | If an error related to an attempt to write an invalid character to an XML object occurred at the server side, the unrecoverable error was generated at the client side, and the user was prompted to restart the client application. | Eliminated unexpected system behavior. |
| XML and XDTO support. | If the FindDisallowedXMLCharacters() method finds an incomplete surrogate Unicode pair, it returns the position of the first character of the incomplete pair. | If the FindDisallowedXMLCharacters() method found an incomplete surrogate Unicode pair, it returned the position of the character that followed the first character of the incomplete pair. | Eliminated unexpected system behavior. |
| Managed forms. |
In a text box that is in the "choice from the list" mode and displays an empty reference, clicking the Cancel button is ignored. | In the text box that was in the "choice from the list" mode and displayed an empty reference, clicking the Cancel button displayed a dialog box with Undefined text. | Eliminated unexpected system behavior. |
| Navigation links. | When a navigation link is followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation link are ignored. This feature is implemented in the following scenarios:
| When navigation links were followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation links were ignored. Users had to delete these characters manually. | Improved management of navigation links. |
| XML and XDTO support. Web services. | When string values are read using the XMLReader object or obtained using a web service, line feed characters keep their original format (they are not converted). This change is not implemented in 8.3.4 compatibility mode. | When string values were read using the XMLReader object or obtained using a web service, the following replacements were made:
| Eliminated unexpected system behavior. |
| Spreadsheet documents. XML and XDTO support. | Settings of text boxes located in spreadsheet documents can now be serialized to XDTO. A spreadsheet document deserialized from XDTO is equivalent to its source. |
During XDTO serialization of spreadsheet documents and the following deserialization, text box settings were lost. | Settings of text boxes located in spreadsheet documents are saved after dumping/loading configuration to/from XML files. |
| Development tools. |
| In the Evaluate expression dialog box and in the Immediate window, expressions were calculated twice in the following cases:
| Eliminated the issue that introduced inaccuracies to the calculated expression result because the expression could only be calculated once (at the current debugging step). |
| Configuration repositories. |
You can perform selective comparison of form modules without building a form comparison report. The Form (module) command is added to the following context menus: Perform selective comparison with the repository object, Perform selective comparison with the configuration object, and Perform selective comparison of object versions. | During selective comparison of forms, two comparisons were performed: the comparison of form modules and the comparison of forms. Two reports were displayed as a result of comparison. |
Improved usability of selective comparison. Comparison of form modules is now a separate command. |
| Data composition system. | In data composition system, the automatically generated title of a field linked to data retrieved using "." (dot) from a Ref field of a tabular section contains the field presentation only. In particular, a field related to the TabularSection.Ref.Number attribute will have the Number title. This change is not implemented in 8.3.4 compatibility mode. | In data composition system, the automatically generated title of a field linked to data retrieved using "." (dot) from a Ref field of a tabular section contained the Ref word and a presentation of the data attribute retrieved using "." (dot). | Improved appearance of reports. |
| Managed forms. | Pessimistic lock of data described by the main form attribute is performed for the following actions in text boxes:
If the lock cannot be set, the action is not performed. | Pessimistic data lock was set for the following actions in text boxes:
| Pessimistic data lock is set for all actions that change text box contents. |
| XML and XDTO support. Development tools. | In the "dump configuration to files" feature, XML file format is changed for the following configuration parts: managed forms, dynamic list settings, graphical schema items, geographical schemas, functional option content, and field lists. Tag names now match the names used in 1C:Enterprise script, the XML element name spelling is unified. The dump format is more compact and clear. The properties filled with default values are not dumped. Dynamic list settings are dumped to a single element, which has the data composition schema settings format. Managed forms dumped using the previous platform versions cannot be loaded by the latest platform version. | In the "dump configuration to files" feature, XML files that stored managed forms, dynamic list settings, graphical schemas, geographical schemas, functional option content, and field lists had a different format. | XML files that store configuration data are more compact and better structured. |
| Charts of accounts. Accounting registers. Data exchange. | While a chart of accounts item is being written with DataExchange.Load property set to True, new extra dimension types are checked for uniqueness. The unique ones are added to the table of extra dimension values, and the nonunique values are not added, which eliminates possible errors. | If a chart of accounts item was being written with DataExchange.Load property set to True, the check for uniqueness of extra dimensions was not performed. This could cause errors while items were being added to the table of extra dimension values. | The order of loading chart of accounts data and data of linked accounting registers does not matter. |
| Development tools. | In the property palette, the Sort alphabetically command sorts properties by presentation (if displaying property names is disabled) or by name (if displaying property names is enabled). If a property does not have a name, the sorting is always performed by text presentation. | In the property palette, the Sort alphabetically command sorted properties by presentation. | The sorting command behavior depends on object property presentations. |
| Data composition system. | In the data composition system, the conditional appearance with Fields header usage area is applied to an area of a vertical template that contains names of displayed fields. The conditional appearance with Group usage area is applied to an aria of vertical template that contains values of displayed fields. This change is not implemented in 8.3.4 compatibility mode. | In the data composition syste, the conditional appearance with Group usage area was applied to all areas of a vertical template. | Improved usability of data composition system conditional appearance. |
| Thick client. | If more than two parameters are passed to the Insert() method of the TableBoxColumns object, an error is generated. This change is not implemented in 8.3.4 compatibility mode. | Up to five parameters could be passed to the Insert() method of the TableBoxColumns object, while only two parameters were used. No errors were generated. | Eliminated unexpected system behavior. |
| Event log. | The event log format is modified. The log is now stored in an SQLite database. The log file has .lgd extension. The log location is not changed. The SQLite log format is the default format for new infobases. The performance of accessing event log data is improved. Existing event logs can be converted to a new format. Conversion back to the legacy format is not supported. The CopyEventLog() and ClearEventLog() methods are implemented. The event log stores time in UTC format. The standard event log viewer supports new log file format (.lgd). In the standard event log viewer form the command for viewing a log stored in a file is renamed to More - View from file. | The event log had text format. In the standard event log viewer form the command for viewing a log stored in a file had the following name: More - Load from file. | Improved performance when accessing event log data. Improved event log reliability. Better name for the command for viewing a log stored in a file. |
| Event log. | Deletion of a large number of event log records (more than 10 million) takes much less time. You can terminate the reducing of event log size by pressing Ctrl+Break in Designer or by closing the session using administrative tools (as a result, a part of records is deleted, and the rest are not deleted). | The performance of event log record deletion was insufficient. Reducing the event log size could not be terminated. | Reducing the size of a large event log takes reasonable time. This operation can be terminated if needed. |
| Spreadsheet documents. | When a spreadsheet document is saved to a PDF file, a single document copy is saved. The Copies spreadsheet document property is ignored. To include multiple copies into the PDF file, use the WriteFileForPrinting() method of the RepresentableDocumentBatch object. This change is not implemented in 8.3.4 compatibility mode. | When a spreadsheet document was saved to a PDF file, the file contained the number of document copies specified in the Copies property. | Eliminated unexpected system behavior. |
| Client application. Development tools. | In Designer and thick client, customization of the search result selection background is available. | In Designer and thick client, the search result background color could not be customized. | Users can specify search result selection background color that fits their text editor settings. |
| Data exchange. Common attributes / Data separation. | In a session that does not use any separators, while session changes are being registered, the Update right is not required for tables of objects being registered. For sessions that use separators, the following features are implemented:
| In a session that did not use any separators, while session changes were being registered, the Update right was required for tables of objects being registered. For sessions that used separators, registering changes for empty record sets that were subordinate to recorders was not available. | In separated mode, changes are registered correctly. |
| Common attributes / Data separation. Database operations. | New options for FindMarkedForDeletion(), FindByRef(), and DeleteObjects() methods:
For value tables that are returned by the FindByRef() and DeleteObjects() methods, a new column is implemented. It contains separator values that define the data area where the found object or the object that prevents deletion of another object is located. The DeleteObjects() method returns a value of Number type, which stores the number of deleted objects. | The search for references, search for objects marked for deletion, and deletion of marked objects were performed only in data available in the current session with the current separator values. Including individual configuration objects to (or excluding configuration objects from) search or deletion was not available. The value tables that were returned by the FindByRef() and DeleteObjects() methods did not contain columns with separator values. The DeleteObjects() method was a procedure. | You can customize the deletion of marked objects, especially in separated infobases. You can design more detailed messages about deletion results (total objects deleted, total objects not deleted, and so on). |
| Defined types. | In Designer, properties palette contents for objects that have defined type are generated based on the actual type that describes the defined type. | The properties palette contents for objects that had defined types were always displayed as if all of the objects had complex type, regardless of their actual types. | Property customization for objects that have defined types is now similar to property customization for objects whose types are specified explicitly. |
| Software licensing. | In the license activation dialog box, each PIN code is entered in a single text box, which includes an input mask (in all license acquisition scenarios). During license activation by phone, each Licensing Center response line is entered in a single text box, which contains an input mask). Pressing Tab switches between these text boxes. The license registration page contains the descriptions of activation options for 5-, 10-, and 20-user licenses. Extended error diagnostics during license activation is implemented. | In the license activation dialog box, each PIN code was entered in 5 text boxes (in all license acquisition scenarios). During license activation by phone, the license activation dialog box had 5 text boxes for entering each Licensing Center response line. Pressing Tab switched between the text boxes and response lines. Help for various license activation methods was not available directly in the dialog box. Some license activation error messages had complicated descriptions that might not be clear to users. | The software license activation dialog box is improved. PINs can be pasted from the clipboard. Improved usability of entering the response from the Licensing Center during license activation by phone. The error messages are clearer to users. |
| Common attributes / Data separation. | In version 8.2.16 or earlier compatibility mode, configuration checks and database configuration updates include the check whether each document journal is included in contents of at least one common attribute, and if it does, the appropriate diagnostics is performed. The configuration is not updated in this case. | In version 8.2.16 or earlier compatibility mode, the configuration check did not detect configuration errors if document journals were included in contents of common attributes, and therefore such errors did not prevent the configuration update. | The system cannot become inconsistent due to the fact that in version 8.2.16 or earlier document journals could not be included in common attribute contents. |
| Data composition system. | The GroupPlacement parameter of the data composition system does not affect the displaying of totals. This change is not implemented in 8.3.4 compatibility mode.
| Grouping totals were not displayed if the GroupPlacement data composition system parameter was set to End or None for the selected grouping. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | For cells that have single-line height, tooltips that do not fit a single text line are displayed as multiple text lines. This change is not implemented in 8.3.4 compatibility mode. | For cells that had single-line height, tooltips were displayed as single text lines. If tooltip text did not fit a single line, it ended with "...." | Eliminated unexpected system behavior. |
| Spreadsheet documents. | In the thin client, when a spreadsheet document is obtained from the server, empty rows located in document cells are preserved. This change is not implemented in 8.3.4 compatibility mode. | In the thin client, when a spreadsheet document was obtained from the server, empty rows located in document cells were lost. | Eliminated data loss during the transfer of spreadsheet documents from the server to the client. |
| Managed forms. | In a managed form table cell that has a drop-down list available and the Directly editing mode set, pressing Down Arrow or Up Arrow keys moves the selection to another cell and does not open the drop-down list. The drop-down list is only opened when a new row is added. To open the drop-down list, press Ctrl+Down Arrow. | In a managed form table cell (with the Directly editing mode set), pressing Down Arrow or Up Arrow keys might open a drop-down list. This eliminated the option to add a new row by pressing Down Arrow. | Eliminated unexpected system behavior. |
| Data composition system. | When a data composition template is generated, expressions for calculating details that contain fields unavailable due to functional options are removed from predefined templates. This change is not implemented in 8.3.4 compatibility mode. | When a data composition template was generated, details expressions were copied from the predefined templates without any modifications. | During report generation, errors do not occur when templates include fields unavailable due to functional options. |
| Client application. | In managed mode, if any connection issues or server-side issues occur, the client application allows to repeat a request, interrupt the operation, or shut down the application. | If any connection issues or server-side issues occurred, users were not allowed to repeat their requests. In most cases the client application was simply shut down. | The client application is more robust against connection issues or 1C:Enterprise server issues. |
| Mobile application. | If the interface compatibility mode is set to Taxi and then the Use purposes configuration property is set to Personal computer and Mobile device, the Interface compatibility mode property is automatically set to Taxi. Version 8.2 allowed. If changing the Use purposes property requires modification of Modality usage mode and Interface compatibility mode configuration property values, the user is prompted to confirm the change. | Selecting the Mobile device value in the Use purposes configuration property made the following changes in configuration properties without any warnings:
| Designer behaves as expected. |
| Software licensing. | Users that do not have administrative rights can activate software licenses. In this scenario the license is activated for the current user. | Only users with administrative rights could activate licenses. |
A user without administrative rights that does not have write access to the directory where license files for all computer users are located still can activate a software license. |
| Predefined data. Data exchange. Common attributes / Data separation. | When predefined data is changed, changes are only registered for items that are actually modified, added, or deleted. When the compatibility mode is changed from Version 8.3.2 (or earlier) to Version 8.3.3 (or later), all predefined item changes are registered. When the compatibility mode is changed from Version 8.3.3 (or later) to Version 8.3.2 (or earlier), registration of all predefined items is removed. When changes are registered for predefined items:
| When predefined data belonging to a specific object was changed, all predefined items of this object were registered as if they were changed. Predefined item changes were registered for all exchange plan nodes available from the session where the predefined items were changed. | When object predefined data is changed, object change registration tables do not significantly increase in size. |
| Managed forms. Web client. | In the web client, if a managed form table cell contains multiple text lines, only lines that fit the cell height are shown. If the text does not fully fit, ellipsis (…) is added to the end of the last line. In Microsoft Internet Explorer 8 web browser, the ellipsis is not displayed. In the thin client, text in managed form table cells better fits the cell height. | In the web client, if a managed form table cell contained multiple text lines, the lines might be cut in the manner that made them unreadable (only the upper character halves were displayed and the lower ones were cut). The ellipsis was not added to the end of the last line. In the thin client, sometimes text in managed form table cells did not fit the cell height well, a redundant empty line was added to the bottom of the cell. | Eliminated unexpected system behavior. |
| Data composition system. | While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items are removed:
This change is not implemented in 8.3.4 compatibility mode. | While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items were removed:
| Improved system stability. |
| Database operations. | You can load the infobase dump file (*.dt) that was generated with the following conditions:
In some scenarios, the aggregates of turnover accumulation registers are cleared after the loading. | Loading the infobase dump file (*.dt) was not available if the file was generated with the following conditions:
| Eliminated unexpected system behavior. |
| Data display. | Text fragments found during a search by substring are displayed in a uniform way (bold font and green text) in the following cases:
| The substrings that were found had different looks. | Uniformed look for different features. |
| XML and XDTO support. | For charts of accounts and charts of calculation types, the Predefined field of predefined tabular sections is available for writing. In charts of accounts and charts of calculation types, the predefined records of predefined tabular sections can include only predefined items. During a serialization of a chart of accounts item or a chart of calculation types item to XML(XDTO), the Predefined item, which matches the Predefined property, is written. During the deserialization, the Predefined item value is written to the Predefined property only if the compatibility mode is disabled. This change is not implemented in 8.3.4 compatibility mode. | For charts of accounts and charts of calculation types, the Predefined field of predefined tabular sections was read-only. During the serialization of a chart of account item or a chart of calculation types item to XML(XDTO), the Predefined item was not generated. | During data exchange between configurations, the flags of predefined data are no longer lost in the chart of accounts and chart of calculation types items. |
| Managed forms. | Getting a choice form in a slow connection scenario is implemented identically to getting forms in other scenarios. | Getting a choice form in a slow connection scenario was implemented differently from getting forms in other scenarios, it included caching the form. | Increased relaibility for getting choice forms in a slow connection scenario. |
| Applied objects. | During the restructuring of hierarchical predefined data, if an item parent is not found during the update, the item is moved to the top level. During the creation or restructuring of predefined data, if references to subordinate items are missing from predefined tabular sections, rows with missing references are deleted. Upon deletion, the platform generates a diagnostics message or an event log record, and the tabular section row numbering is updated accordingly. This change is not implemented in 8.3.4 compatibility mode. | Invalid references to parent items or subordinate items in predefined data might cause errors during infobase retructuring. | Increased system stability in the scenario where predefined data items contain invalid references to parent or subordinate items. |
| Command interface. | In the Taxi interface the scaling of pictures in the sections panel of the web client is now identical to that of the thin client. The picture height is calculated as follows:
| In the Taxi interface of the web client 48x48 pixel squares were reserved for section panel pictures. The size of larger pictures was reduced proportionally and smaller pictures were centered within those squares. The section panel height was never reduced. | The Taxi interface behavior in the web client is unified with that of the thin client. |
| Spreadsheet documents. XML and XDTO support. | When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file is not important. | When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file was important. | Spreadsheet documents serialized to XDTO using 1C:Enterprise version 8.3.4 and earlier can be read without errors. |
| Third-party software. | The OpenSSL library is updated to version 1.0.0r. | OpenSSL version 1.0.0m was used. | Eliminated OpenSSL security issues. |
| Web client. | The web client is optimized for Google Chrome 37 web browser. The managed form issues where text did not fit the desired area are eliminated. | The web client had issues related to displaying text in Google Chrome 37 web browser. |
Improved Google Chrome 37 web browser support. |
| DBMS operations. | Improved reliability of PostgreSQL DBMS operations in certain scenarios. | Insufficient reliability of PostgreSQL DBMS operations in certain scenarios. | Improved reliability of PostgreSQL DBMS operations. |
| Regional settings. | For Russia, a single one-hour time zone shift is applied in line with Federal Law #248-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.
| The platform did not reflect the changes introduced by Federal Law #248-FZ. | The time offset changes introduced by the new law are implemented. |
| Add-ins. | A section describing add-in limitations is added to the Add-in development technology document (read more). | The Add-in development technology document did not describe add-in limitations. | Improved add-in technology description. |
| Client application. Development tools. | When the thick client (1cv8) is started in ordinary application mode, the performance indicator window is not displayed. | When the thick client (1cv8) was started in ordinary application mode, the performance indicator window was not displayed. | The display of performance indicators in ordinary applications is disabled because they are rarely used in this mode. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Dynamic lists. | Dynamic lists cannot be ordered by extra dimension fields of accounting registers. An attempt to order a dynamic list by these fields (for example, by clicking the column header) does not result in a server call. This change is not implemented in 8.3.4 compatibility mode. | An attempt to order a dynamic list by extra dimension fields of accounting registers generated an error message and initiated a server call, which did not retrieve any data. | Dynamic lists do not allow ordering that does not make sense, therefore the system behaves as expected (from the user’s point of view). |
| Applied objects. | An attempt to set a value to ThisObject or AdditionalProperties attribute of a CatalogObject, ExchangePlanObject, or ChartOfCharacteristicTypesObject raises an exception. An attempt to set a value to the DataExchange attribute of a CatalogObject or ChartOfCharacteristicTypesObject raises an exception. This change is not implemented in 8.3.4 compatibility mode. | An attempt to set a value to ThisObject or AdditionalProperties attribute of a CatalogObject, ExchangePlanObject, or ChartOfCharacteristicTypesObject did not raise an exception, and the value was not set. An attempt to set a value to the DataExchange attribute of a CatalogObject or ChartOfCharacteristicTypesObject did not raise an exception, and the value was not set. | Unified processing of the specified properties: an attempt to set a value for a read-only attribute raises an exception. |
| Client application. Server clusters. | If the client and server application versions do not match, the search for client application distribution kit is performed in the following order:
| If the client and server application versions did not match, the search for client application distribution kit was performed in the following order:
| Search for updates behaves as expected: search in the local network precedes search using Internet services. |
| Common attributes / Data separation. | The SetPredefinedDataUpdate() and SetInfoBasePredefinedDataUpdate() methods can only be executed in sessions that do not have any separators (in addition to the fact that they require the Administration right). This change is not implemented in 8.3.4 compatibility mode. | The SetPredefinedDataUpdate() and SetInfoBasePredefinedDataUpdate() methods could be executed in any session, provided that the user had the Administration right. | Users cannot change the infobase predefined data update mode if they do not have the required rights. |
| Navigation links. Client application. | The ReferencesArray parameter of the GetURLsPresentations() function is mandatory. The return value of this function is always an array. For input array items whose presentations cannot be obtained, the matching output array items contain UNDEFINED. This change is not implemented in 8.3.4 compatibility mode. | The ReferencesArray parameter of the GetURLsPresentations() function was not mandatory. In cases when a parameter value presentation could not be obtained by its value, uniform system behavior across all client applications was not guaranteed. | The GetURLsPresentations() function is uniform across all client applications. |
| Web client. | In the web client, performing the Execute() operator ends in exception. | In the web client, calling the Execute() operator was ignored and no diagnostic messages were displayed. | Implemented applied solution error diagnostics (for calling the Execute() operator in the web client). |
| Spreadsheet documents. | In the SpreadsheetDocumentRange object, the TopBorder, RightBorder, BottomBorder, and LeftBorder properties contain the UNDEFINED value if the corresponding border is not the same for all cells. This change is not implemented in 8.3.4 compatibility mode. | In the SpreadsheetDocumentRange object, values of the TopBorder, RightBorder, BottomBorder, and LeftBorder properties were retrieved from the properties of a random cell within the specified range | Eliminated unexpected system behavior. |
| Data composition system. | In data composition system batch queries, when a temporary table is created, if the table fields are not used by the next queries of the batch and the table is not included in required joins, the query that creates the table is removed from the batch. This change is not implemented in 8.3.4 compatibility mode | In data composition system batch queries, temporary tables were deleted from the batch if the table fields were not used by the next queries of the batch and the table was not used in other queries of the batch that also created temporary tables. | Improved management of temporary tables in the data composition system. |
| Data exchange. Information registers. | Changes in information registers that have dimensions of UUID type that are included in the main filter are recorded correctly. In tables that store the register change records, fields describing dimensions of UUID type have UUID type. | Changes in information registers that had dimensions of UUID type were recorded incorrectly. In tables that stored the register change records, fields describing dimensions of UUID type had BinaryData type. | Eliminated unexpected system behavior. In exchange plans containing information registers with dimensions of UUID type that are included in the main filter, registering all dimensions is required. |
| 1C:Enterprise script. Common objects. | In the thin client, the following types are not available: ValueTableRow, ValueTableColumnCollection, ValueTableColumn, CollectionIndexes, CollectionIndex, ValueTreeRowCollection, ValueTreeRow, ValueTreeColumnCollection, and ValueTreeColumn. This change is not implemented in 8.3.4 compatibility mode. | In the thin client, the following types were available: ValueTableRow, ValueTableColumnCollection, ValueTableColumn, CollectionIndexes, CollectionIndex, ValueTreeRowCollection, ValueTreeRow, ValueTreeColumnCollection, and ValueTreeColumn. | Eliminated unexpected system behavior. |
| Managed forms. | In managed form text boxes, the TextEditEnd event handler is not called when the spin buttons are clicked. This change is not implemented in 8.3.4 compatibility mode. |
In managed form text boxes, the TextEditEnd event handler was called when spin buttons were clicked. | Eliminated unexpected system behavior. |
| Applied objects. Managed forms. | When an object is created from a dynamic list filtered by an attribute of Date type, object attributes of that type are filled from the filling data. This change is not implemented in 8.3.4 compatibility mode. | When an object was created from a dynamic list filtered by an attribute of Date type, object attributes of that type were not filled from the filling data. For such attributes, the standard FillingValues parameter of the new item form contained values of the StandardBeginningDate type passed from the dynamic list filters. | Eliminated unexpected system behavior. |
| Managed forms. | In managed form text boxes, if editing a string with an input mask results in a string that matches an empty input mask, an empty string is recorded to the form attribute displayed in the text box. If the string has fixed length, the string consists of spaces. This change is not implemented in 8.3.4 compatibility mode. | In managed form text boxes, if editing a string with an input mask resulted in a string that matched an empty input mask, a string that contained spaces and fixed input mask characters was recorded to the form attribute displayed in the text box. | When a text box is cleared, an empty string is recorded to the linked attribute regardless of the input mask availability. In text boxes linked to attributes of Text type with the input mask set, the automatic "incomplete" mark is displayed correctly. |
| Managed forms. | In managed form text boxes, the procedure of generating a drop-down list during input by string is modified. The procedure is described in the documentation. This change is not implemented in 8.3.4 compatibility mode. | In managed form text boxes, the following procedure was used for generating a choice list during input by string:
| In managed form text boxes, eliminated issues in the procedure of drop-down list generation when search is performed both by beginning of string and by substring. |
| Managed forms. | Getting the list of desktop forms is implemented. For the Forms in tabs and Taxi interface modes, the ClientApplicationWindows collection contains a separate item that describes the start page (desktop). The Content property of this item contains the list of forms available on the start page (desktop). For the Forms in separate windows interface mode, the ClientApplicationWindows collection contains ClientApplicationWindow objects that describe forms located on the desktop. For the ClientApplicationWindow object, the StartPage and Content properties are implemented. The GetContent() method of the ClientApplicationWindow is supported for compatibility purposes. This change is not implemented in 8.3.4 compatibility mode. | This feature was not provided. For the Forms in tabs and Taxi interface modes, the ClientApplicationWindows collection did not contain objects describing the start page (desktop). For the Forms in separate windows interface mode, the ClientApplicationWindows collection did not contain objects describing forms opened on the desktop. | Developers can access forms located on the start page (desktop) using 1C:Enterprise script. |
| Automated testing. | For subordinate objects of the TestedApplication object, the TestedClientApplicationWindow object is implemented. The object describes the start page (desktop). Forms (objects of TestedForm type) included in the start page (desktop) content are subordinate to the TestedClientApplicationWindow object that describes the start page (desktop). For the TestedClientApplicationWindow object, the StartPage property is implemented. This change is not implemented in 8.3.4 compatibility mode. | The TestedClientApplicationWindow object that described the start page (desktop) was not included in the subordinate objects of the TestedApplication object. Forms included in the start page (desktop) were subordinate to the TestedClientApplicationWindow object that had its IsMain property set to True. | You can access forms located on the start page (desktop) from 1C:Enterprise script using automated testing tools. |
| Common attributes / Data separation. Data exchange. | An exception that does not cause application termination occurs when predefined data is registered for an unseparated configuration object in a separated exchange plan from a session that uses all separators. | An exception that caused application termination occurred when predefined data was registered for an unseparated configuration object in a separated exchange plan from a session that used all separators. | Eliminated issues that resulted in application termination. |
| Common attributes / Data separation. Data exchange. | If a configuration object does not use all separators where it is included, calling the InitializePredefinedData() method does not initialize predefined data items for this object. This change is not implemented in 8.3.4 compatibility mode. | If a configuration object did not use all separators where it was included, calling the InitializePredefinedData() method caused an error. | The InitializePredefinedData() method can be used in any session, not only when all separators are used. |
| DBMS operations. Data composition system. Dynamic lists. | For the LIKE query language operation, search in dynamic lists, and filter in the data composition system, the search template length is limited. The limit depends on the DBMS type. If the template length exceeds the limit, an error is generated, which does not lead to 1C:Enterprise shutdown. | For the LIKE query language operation, search in dynamic lists, and filter in the data composition system, if the search template exceeded 1024 characters, this could cause a DBMS error and 1C:Enterprise shutdown. | 1C:Enterprise is not shut down when a search template is too long. |
| Applied objects. | The value of the IsFolder field is correctly passed to the PresentationGetProcessing handler. This change is not implemented in 8.3.4 compatibility mode. | The value of the IsFolder field passed to the PresentationGetProcessing handler was inverted. | Eliminated unexpected system behavior. |
| Managed forms. | The managed form visibility setting is stored in the system setting storage with a purpose use key. The object key is generated as follows: <Full form name>/<Purpose use key>/FormSettings. This change is not implemented in 8.3.4 compatibility mode. | The managed form visibility setting was stored in the system setting storage without a purpose use key. The object key was generated as follows: <Full form name>/FormSettings. | You can use a single form for different use purposes, with custom display settings for each use purpose. |
| Data composition system. | Data composition system expressions are calculated in the safe mode. This change is not implemented in 8.3.4 compatibility mode. |
The safe mode was not used when data composition system expressions were calculated. | Improved security of executing reports that might use insecure methods from common modules. |
| Managed forms. | In managed form tables, you can start dragging from an available table cell only. This change is not implemented in 8.3.4 compatibility mode. | In managed form tables, dragging from any table cell was allowed. When an attempt to drag an unavailable cell was made, the currently selected cell was dragged instead. | Eliminated unexpected system behavior. |
| Data composition system. | The Text parameter of conditional appearance that is specified for the Fields header usage area is applied to grouping field headers. This change is not implemented in 8.3.4 compatibility mode. | The Text parameter of conditional apperance was never applied to grouping field headers. | Eliminated unexpected system behavior. |
| Data composition system. | The data composition template generator always generates the VerticalLevel property for nested reports. The parent report level is added to the value of this property. This change is not implemented in 8.3.4 compatibility mode. |
Parent report groupings were not taken into account when nested reports were displayed. | Parent report groupings affect nested reports: nested reports are displayed at the same grouping level as the parent report. |
| Managed forms. | For managed form fields, the PeriodField field type is implemented. It is intended for simplifying selection of periods of several full months. For managed form field extensions for calendar fields, the Border property is implemented. It specifies border parameters for the calendar field. The dialog box that was used in the following scenarios is modified:
This change is not implemented in 8.3.4 compatibility mode. | For managed form fields, the PeriodField field type was not available. For managed form field extensions for calendar fields, the Border property was not available. A different dialog box was used in the following scenarios:
If the period variant was not custom, a drop-down list containing available options was opened in the input field. | The period selection dialog box is improved. |
| Managed forms. | In managed form tables, if a row is added because editing the previous row is finished or by pressing the Down Arrow, and then the row is neither edited from 1C:Enterprise script nor edited interactively, the new row is automatically deleted once the selection is moved away from it. This change is not implemented in 8.3.4 compatibility mode. | In managed form tables, if a row was added because editing the previous row was finished or by pressing the Down Arrow, and then the row was not edited interactively, the new row was automatically deleted once the selection was moved away from it. | Eliminated unexpected system behavior. |
| Managed forms. | While a text box choice history is being filled, the check for deleted items is performed. A value presentation is removed from the list if its data was deleted in the current session or its data was deleted in another session but the presentation of deleted data was obtained in this session. If a value is deleted after the choice history is generated, when a user attempts to select this value, a warning is displayed, the value is not selected, and the item is removed from the history list. The feature is implemented for thin and web clients. | Deleted values were displayed in text box choice history as Object not found items. | References to objects that are no longer available for selection are removed from the choice history. |
| Managed forms. | In managed forms, the length of the PurposeUseKey property value is limited to 128 characters. An attempt to set a value longer than 128 characters or open a form with this property value longer than 128 characters ends with a exception. This change is not implemented in 8.3.4 compatibility mode. |
In managed forms, the length of the PurposeUseKey property value was not limited. | Simplified diagnostics of issues related to PurposeUseKey value being too long. |
| Data access restrictions. | For each configuration object that is included in separator content and has tabular sections, a data access restriction check is performed (after writing) if the access restriction conditions include attributes from the object tabular section. As a result, a message about insufficient access rights might be displayed in situations where it was not displayed earlier.
| For configuration objects that were included in separator content and had tabular sections, data access restriction checks were not performed (after writing) if the access restriction conditions included attributes from the object tabular sections. | Eliminated unexpected system behavior. |
| Predefined data. Charts of accounts. Charts of calculation types. | The following rules now apply during infobase restructuring:
In addition to that, the order of tabular section rows might be changed to ensure that all of the predefined items are at the top. This change is not implemented in 8.3.4 compatibility mode. | In a chart of accounts, adding a predefined extra dimension type in Designer mode was impossible if the extra dimension type was added in 1C:Enterprise mode earlier. When an attempt to delete a predefined row from a predefined tabular section of a chart of accounts was made, the actual row was deleted. Charts of calculation types had the following behavior:
| Editing predefined tabular sections no longer might cause data losses. Editing the list of extra dimension types of a predefined account in Designer might result in a message that the account's maximum number of extra dimension types is exceeded. |
| Accounting registers. Accumulation registers. Information registers. Calculation registers. | In a value table obtained by the Unload() method of an accounting register, accumulation register, calculationregister, or information register record set, the value of the LineNumber column is equal to the line number in the record set. This change is not implemented in 8.3.4 compatibility mode. | In the value table obtained by the Unload() method of an accounting register, accumulation register, calculation register, or information register record set, the value of the LineNumber column was equal to the index of the record set index. | Eliminated unexpected system behavior. |
| Client application. Internet-enabled functionality. | The TLS protocol is recommended for secure connections as it is more secure. The SSL protocol version 3.0 is disabled by default. If the web server used for thin client connections can use SSL version 3.0 for connecting to a web server, you can use the thin client command-line option /HttpsAllowSSLv3. SSL version 3.0 is not used (by default) with the HTTPConnection, FTPConnection, InternetMail, WSProxy, WSReference, and WSDefinition objects, when connecting to the configuration repository, and in Debugger. If you need to use SSL version 3.0 in these scenarios, use the AllowSSLv3 option in the conf.cfg file. For the conf.cfg configuration file, the AllowSSLv3 option is implemented. For the InternetMail object in version 8.3.5 and earlier compatibility mode and in earlier 1C:Enterprise versions:
| The SSL protocol version 3.0 was used for secure connections. | Improved security of connections established by client applications that work over the Internet. |
| Web client. Add-ins. | The file system extension and the cryptography extension are modified (for all supported Windows web browsers). The reason is that the NPAPI technology is no longer supported in Google Chrome browser. New extension versions perform all file and cryptography operations asynchronously (using notifications). To be able to use 1C:Enterprise extensions and browser extensions, you are required to install a dedicated web browser extension. The web client prompts you to install that extension once you attempt to enable a browser extension. On the client side, add-ins, the file system extension, and the cryptography extension run asynchronously. Synchronous add-in, file system extension, and cryptography extension operations are supported on the client side for compatibility purposes. Refactoring applied solutions, including those that have add-ins, is required to support synchronous operations:
Refactoring add-ins is not required. The platform automatically adds prefixes and asynchronous behavior support to add-in methods. The SynchronousExtensionAndAddInCallUseMode configuration property is implemented. If the property is set to Do not use, NPAPI-based extensions are not loaded in the web client and, as a result, synchronous methods cannot be executed. In other cases, an attempt to load an NPAPI-based extension is performed. If an extension is successfully loaded, both synchronous and asynchronous methods can be executed. For more information, see the documentation. Previous extension versions can be uninstalled in a regular way. Improved add-in development technology (read more). The following global context methods are implemented: BeginAttachingCryptoExtension(), BeginAttachingFileSystemExtension(), BeginAttachingAddIn(), BeginCopyingFile(), BeginMovingFile(), BeginDeletingFiles(), BeginFindingFiles(), BeginCreatingDirectory(), BeginGettingTempFilesDir(), BeginGettingDocumentsDir(), BeginGettingUserDataWorkDir(), BeginGettingFiles(), BeginPuttingFiles(), BeginRequestingUserPermission(), and BeginRunningApplication(). For the CryptoManager object, a constructor without parameters is implemented, and also the following methods: BeginInitialization(), BeginEncrypting(), BeginSigning(), BeginGettingCryptoModuleInformation(), BeginGettingCertificatesFromSignature(), BeginGettingCertificateStore(), BeginVerifyingSignature(), BeginCheckingCertificate(), and BeginDecrypting(). For the CryptoCertificate object, a constructor without parameters is implemented, and also the following methods: BeginInitialization() and BeginUnload. For the CryptoTools object, the BeginGettingCryptoModuleInformation() method is implemented. For the CryptoCertificateStore object, the BeginAdding(), BeginFindingByThumbprint(), BeginFindingBySerialNumber(), BeginFindingBySubject(), BeginGettingAll(), and BeginDeleting() methods are implemented. For the FileDialog object, the Show() method is implemented. For the File object, a constructor without parameters is implemented, and also the following methods: BeginInitialization(), BeginGettingModificationTime(), BeginGettingHidden(), BeginGettingReadOnly(), BeginGettingSize(), BeginGettingModificationUniversalTime(), BeginCheckingExist(), BeginSettingModificationTime(), BeginSettingHidden(), BeginSettingReadOnly(), BeginSettingModificationUniversalTime(), BeginCheckingIsDirectory(), and BeginCheckingIsFile(). You can use the refactoring feature to convert synchronous extension and add-in methods to their asynchronous counterparts. New refactoring settings are available. | The file system extension and the cryptography extension were implemented using the NPAPI technology. The extension methods were executed synchronously. In Google Chrome web browser synchronous execution of methods from add-in APIs was possible. |
The platform supports asynchronous add-in, cryptography extension, and file system extension operations in the web client, which ensures Google Chrome support. Important! Support of synchronous operations in Google Chrome is disabled by default since version 42 (April 2015) and discontinued since version 45 (September 2015). Therefore, synchronous 1C:Enterprise script methods will stop working in Google Chrome even if you use a platform version that supports them.
|
| Web client. Add-ins. | The add-in technology (read more) no longer supports add-in development for Safari web browser for Windows. | The add-in technology supported add-in development for Safari web browser for Windows. | The outdated web browser is no longer supported. The Apple company stopped updating Safari web browser for Windows. |
| Add-ins. | The add-in development technology supports Mozilla Firefox web browser versions 31.0 and later. It is recommended that you build a new installer package for Mozilla Firefox using the new adapter. It is also recommended that you remove installer packages for Mozilla Firefox versions 30.0 and earlier from the add-in archive. The add-in development technology does not support Mozilla Firefox web browser versions 30.0 or earlier. Adapters for Mozilla Firefox versions 30.0 or earlier are removed. | The add-in development technology did not support Mozilla Firefox web browser versions 31.0 or later. The add-in development technology supported Mozilla Firefox web browser versions 30.0 and earlier. | The add-in development technology supports the latest versions of Mozilla Firefox web browser (31.0 or later). The add-in development technology does not support older versions of Mozilla Firefox web browser (30.0 or later). |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Dynamic lists. Queries. | Custom queries, including queries that generate dynamic lists, are now available in the mobile platform. | This feature was not provided in the mobile platform. | In mobile applications, you can use dynamic lists generated based on custom queries, and use queries to the infobase for implementing various features, such as checking balance while posting documents |
| Managed forms. | Faster form opening and faster execution of context server calls. | Insufficient performance of form opening and execution of context server calls. | Improved user experience by improving the performance of form operations. |
| Applied objects. | Predefined items are created at the first call of the corresponding table. Calling the SetPredefinedDataUpdate() method before the first call modifies the flag that shows whether predefined data is created. | Predefined items were only created when mobile application configuration was updated. After calling the SetPredefinedDataUpdate() method, predefined data was only modified during the next mobile application configuration update. | Mobile platform behavior is uniform with that of PC platform version 8.3.3. |
| Background and scheduled jobs. | Background jobs are now available in the mobile platform. | This feature was not provided in the mobile platform. | Background jobs are available in mobile applications. |
| Access rights. Functional options. | In the mobile platform, the following features are available:
Limitations of the implemented features are described in the documentation. | These features were not provided in the mobile platform. | Extended features for applied solution interface management. |
| Database operations. | The EraseInfoBaseData() global context method is implemented. | This feature was not provided on the mobile platform. | On the mobile platform, you can delete all infobase data. |
| Development tools. | In Designer, support of Android Debug Bridge (adb) is added. Now you can start a mobile application from Designer on a mobile device emulator or on a physical device connected to a computer. | This feature was not provided. | Easier development and debugging of mobile applications for Android OS. |
| Internet-enabled functionality. Telephony. | New features:
The limitations of the telephony tools on supported operating systems are listed in documentation. | Sending SMS messages and making calls was available with some limitations using parameters of the RunApp() and GotoURL() methods. Access to the call history and sent email messages from the built-in email client was not available. | Easy access to mobile device functionality: SMS and MMS, call history, and making calls. |
| System requirements. | The configuration property RequiredMobileApplicationPermissions, specifies permissions that mobile application will require on Android:
The Mobile application builder uses the specified permissions. | This feature was not provided. | You can specify permissions required for your mobile applications more clearly. |
| Multimedia tools. | Scanning barcodes using the mobile device camera is supported. For the MultimediaTools object, the following methods are implemented: BarcodeScannerScanning(), ShowBarcodeScanning(), and CloseBarcodeScanning(). | This feature was not provided. | New mobile platform feature. |
| Development tools. | In Designer, you can edit pictures with variants. You can convert images to images with variants and back. | You could only load pictures with variants without editing them. | Creating images for mobile applications became easier. |
| Access to mobile device features. | Access to mobile device contact lists, both local and linked to specific accounts, is implemented. The following objects are implemented: ContactManager, ContactData, AccountContactData, LocalContactKey, ContactAccount, ContactDataItem, and ContactDataItemInstantMessaging. | This feature was not provided. | You can access mobile device contacts. |
| Access to mobile device features. | Access to mobile device calendars linked to specific accounts is implemented. The following objects are implemented: CalendarManager, CalendarAccount, LocalCalendarKey, LocalCalendarEventKey, CalendarEventData, AccountCalendarEventData, CalendarData, and AccountCalendarData. | This feature was not provided. | You can access mobile device calendars. |
| Location tools. | For the AddressData object, the AddressString property is implemented. It stores an address fragment starting from the street. | This feature was not provided. | The AddressData object functionality is extended. It can be used not only for geolocation purposes, but also for storing various types of contact information. |
| Development tools. | The mobile platform distribution kit mobile.zip now includes the version.txt file. The file contains the version number of the mobile platform delivered in the archive. | This feature was not provided. | Simplified identification of the mobile platform version, including scenarios that use Mobile application builder. |
| Mobile application builder. | The mobile application builder, which is included in the mobile platform, is improved:
| The mobile application builder had the following features:
| The usability of the mobile application builder is improved. |
| Client application. | The text displayed on the mobile platform splash screen is translated to all localization languages. | The text displayed on the mobile platform splash screen was always displayed in Russian. | Eliminated unexpected system behavior. |
| Common objects. | The option to run external applications on mobile devices and get the results of their execution is implemented. This feature is only available on operating systems of Android family. The MobileDeviceApplicationLaunch and MobileDeviceApplicationLaunchExtrasData objects are implemented. | This feature was not provided. | Simplified applied solution integration with mobile applications, including the option to get mobile application execution result. This feature is only available on operating systems of Android family. |
| Development tools. | During the building of an Xcode project, the "executable" attribute is set for the 1cem file included in the project. | During the building of an Xcode project, the attributes of the 1cem file included in the project were not changed. | Eliminated the problem that occurred when a project file was rebuilt on an operating system of Windows family: the "executable" attribute of the 1cem file was cleared. |
| Data display. Mobile application builder. | In the mobile platform, graphical assets for iPhone 6 and iPhone 6 Plus devices are implemented:
In the mobile application builder, support of graphical assets for iPhone 6 and iPhone 6 Plus devices is implemented. | The mobile platform and mobile application builder did not support graphical assets required for iPhone 6 and iPhone 6 Plus devices. | New Apple mobile devices are supported. |
Version 8.3.4 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.3 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, 8.2.16, 8.3.1, and 8.3.2. | In version 8.3.4 you can run configurations created in version 8.3.3 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.4 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.3 for working with the infobase even after the transition to version 8.3.4. 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). |
| Common objects. | In the RepresentableDocumentBatchItems object, the optional parameter DocumentAddress is implemented for the Add() and Insert() methods. This parameter stores the address of the temporary storage for the document being saved. | This feature was not provided. | Improved usability of generating document batches for saving and printing. |
| Spreadsheet documents. | You can save spreadsheet documents in HTML 5 format. Сharts and grafic primitives are saved in SVG format; free text rotation is supported. | This feature was not provided. | You can save spreadsheet documents in HTML 5 format. |
| Background and scheduled jobs. | When specifying a value for the Parameters property of the BackgroundJobs object or for the Parameters property of the Execute() method of the ScheduledJob object, you can omit any number of last parameters, provided that their default values are defined in the method that implements the background or scheduled job. | During the start of a background or scheduled job, if any number of last parameters with default values specified were not specified explicitly, an exception was raised. | You can modify methods implementing background or scheduled jobs by adding new parameters to the end of the parameter list, provided that their default values are defined. In this case modification of previously created code fragments that describe creation of background or scheduled jobs is not required. |
| Development tools. | In Designer, the following module editor features are available:
Selecting identifiers is disabled by default. To use this feature, enable it in Designer options dialog box. Selecting the search expression is available in Designer, thick client, and thin client. | This features were not provided. | The 1C:Enterprise script editor is improved. |
| External data sources. | External data sources support all features of the MySQL query language. In the ExternalDataSourceConnectionParameters object, the MySQL value is implemented for the DBMS property. In the technological log, the DBMySQL property is implemented for the DBMS property of the EDS event.. | External data sources did not support all features of the MySQL query language. | Dynamic lists, temporary tables, and other platform features are now supported for MySQL external data sources. |
| Interface. | Management of client application interface content from 1C:Enterprise script is implemented. The objects ClientApplicationInterfaceContentSettings, ClientApplicationInterfaceContentSettingsGroup, and ClientApplicationInterfaceContentSettingsItem are implemented. Calling the RefreshInterface() global context method rebuilds interface panels according to the settings from the system storage. For the ClientApplicationInterfaceSettings object, a constructor and methods GetContent() and SetContent() are implemented. | The ClientApplicationInterfaceContentSettings object stored the differences between the client application settings and the settings specified in Designer. Interface management from 1C:Enterprise script was not supported. | 1C:Enterprise script-based management of application interface panel visibility and positions. |
| Automated testing. | For the TestedFormField object, the WaitForDropListGeneration() method is implemented. | This feature was not provided. | The option to wait while a dynamic list is being generated is now available. You can use it when the generation takes significant time. |
| Interface. | A new display option intended for improving the view of item-heavy forms without introducing any significant form changes is available in the Taxi interface. The Scale property is implemented for managed forms. The property is only available if the Interface compatibility mode configuration property is set to Version 8.2. For the ClientSettings object, the ClientApplicationFormScaleVariant property is implemented. This property modifes the scale of all forms in the applied solution for a specific user. | This feature was not provided. There was no simple way to make a form compact. | For applications designed for Version 8.2 interface and not yet migrated to Taxi, a new option that regulates the scale of managed form items is implemented. You can modify both a scale of a single form (which is not yet redesigned for Taxi interface mode) and the scale of the entire application (you might need this if the applied solution runs on a computer with a low-resolution or small-sized display). The scale of a single form is specified in Designer, while the scale for the entire application is specified in the settings for a specific user. |
| Managed forms. | Passing additional parameters to an object creation form that is opened from a managed form text box is implemented (in addition to passing filters and standard parameters). Choice forms are used for storing additional parameters and passing them to item creation forms. Additional parameters are specified in choice parameters and choice parameter links using parameter naming forms (the parameter names must have the Additional. prefix). When item creation is initiated from a text box, these parameters are passed directly to the item creation form. When item creation is initiated from a drop-down list in a text box, they are first passed to the list form and then, when item creation is actually initiated, they are passed to the item creation form. The standard parameter AdditionalParameters of Structure type is implemented for managed form extensions of objects, catalogs, documents, charts of characteristic types, business processes, tasks, and dynamic lists. For dynamic list table extensions, the AdditionalCreateParameters property of FixedStructure type is implemented. | Filter values could be passed from text fields to item creation forms as filling values. Additional parameters could not be passed. | You can pass additional parameters (that are not filter options) to an item creation form that is opened from a text box. |
| Managed forms. | You can enable or disable history for text fields linked to data of the following types: catalog, document, business process, task, chart of characteristic types, chart of calculation types, chart of accounts, or exchange plan. The ChoiceHistoryOnInput property of configuration objects, configuration object attributes, and form items defines whether the history is enabled. | This feature was not provided. | For text fields whose business logic does not require keeping the history of values, you can disable the history. |
| Managed forms. | You can use the DropListWidth property to specify minimum width of drop-down lists for managed form text fields. The actual list width is the minimum value of the following: the property value and the stabdard width (40 characters). | Drop-down lists in text fields had fixed width (40 characters). | You can increase the width of drop-down lists that contain long items. |
| Configuration repositories. | In Designer batch mode, the following features are available:
| This feature was not provided. Configuration repository administrators only could create new configuration repositories and users interactively. | You can automate administrative operations on configuration repositories, including automatic creation of repositories for project parts that are being developed independently. |
| Dynamic lists. Document journals. | In document journals, you can use "Create" commands parametrized by the type of document being created. In a dynamic list that has a document journal table specified as its main table, a document creation button that opens a submenu with the list of documents available for the current user can be generated automatically. For dynamic list form table extensions, a standard CreateByParameter command is implemented. For the Button form item, the Parameter property is implemented. It is available only if the button is linked to the CreateByParameter command. For the BeforeAddRow event handler of form tables, the Parameter parameter is implemented. It is used for passing document type values during document creation. This change is not implemented in 8.3.2 compatibility mode. | In a dynamic list that has a document journal specified as a main table, a single Create command that did not open submenus was available. Running this command opened a dialog box for selecting document type. The type of document being created was not passed to the BeforeAddRow event handler of the form table linked to the dynamic list. | In document journals that contain a small number of document types, you can simplify the type selection during document creation. Easy and fast generation of individual buttons for creating documents of specific types on the form command bar. |
| Server clusters. | Licenses with a limited number of simultaneous sessions are implemented for the 1C:Enterprise server. The limitations apply to the following sessions:
Licenses can be activated for both 32-bit and 64-bit server versions. The server cluster that uses this license type can only contain a single working server. | This feature was not provided. 1C:Enterprise server did not have limitations for the number of simultaneously connected users. | Extended list of supported licenses for 1C:Enterprise server. New delivery option focused on using the server in small businesses or subsidiaries. |
| Internet-enabled functionality. | The thin client supports the TLS protocol since 1C:Enterprise version 8.3.4.428. For the thin client, the /HttpsForceSSLv3 command-line option is implemented. It forces the system not to use the TLS protocol (if the connection is established using a web server), even if the web server supports this protocol. | 1C:Enterprise versions 8.3.4.408 (and earlier) and 8.2.19 did not support the TLS protocol. | You can use the TLS protocol when needed. |
| National settings. | The following Mongolian locales are supported:
| Mongolian locales were not supported. | When 1C:Enterprise is started on a computer with Mongolian national settings, it is not shut down unexpectedly. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Web client. | In Mozilla Firefox web browser, wordings in the web browser extension installation dialog box are clarified. The user is explicitly offered to install the extension. | The web browser extension installation dialog box offered the user to enable the extension. | For the web browser extension, the installation process is clearly differentiated from enabling the installed extension. |
| Advanced error handling. | Improved dump generation algorithm in the event of unexpected shutdown. The dump is generated even if a new exception occurs while the first exception is being processed. | If a new exception occurred while an exception was being processed, the dump was not generated. | The frequency of cases where the cause of an unexpected shutdown cannot be found by analyzing dumps is reduced. |
| Client application. | In the web client, the following managed system forms are revised:
In all managed system forms, the Help button is located in the command bar, instead of the More (All actions) menu. | Managed system forms had different layouts. | Managed system forms are improved. |
| Internet-enabled functionality. Client application. | Microsoft Internet Explorer 11 web browser is now supported. | Microsoft Internet Explorer 11 web browser was not supported. | The new version of Microsoft web browser is now supported. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Configuration change checks are optimized. The execution time is reduced for the following configuration check operations:
Reading changes using the ReadChanges() method of an exchange plan manager. | The performance of configuration change checks lacked efficiency. | Improved performance of configuration change checks. |
| Web client. | Improved web client performance with the Taxi interface when a large number of forms are open. | The web client performance with the Taxi interface when a large number of forms were open lacked efficiency. | Improved web client performance in the Taxi interface mode. |
| Server clusters. Applied objects. | In the client/server mode, the impact of the numbering service on transaction start and end times is reduced, even when the numbering service is not used within the transaction. In the client/server mode, the performance of the numbering service with a large number of prefixes is improved. | In the client/server mode, the numbering service had negative impact on transaction start and end times, even when the numbering service was not used within the transaction. In the client/server mode, the performance of the numbering service with a large number of prefixes lacked efficiency. | Improved performance in the client/server mode when the numbering service is actively used with a large number of prefixes, e.g. in infobases with a large number of areas. |
| Managed forms. | Editing a large number of text lines in text boxes with the MultiLine property set to Yes was sped up for both thick and thin clients | The performance of text boxes that contained a large number of text lines was insufficient. | Reduced response time while editing large multiline texts in text boxes. |
| Configuration repositories. | For configuration repositories that do not use the compatibility mode, performance is improved for the following action types:
| The specified operations lacked efficiency. | Improved performance of configuration repository operations. |
| Web client. | In Microsoft Internet Explorer 8 web browser, rounded borders of controls are not displayed in order to increase performance. | In Microsoft Internet Explorer 8 browser, rounded borders of controls were displayed. | Improved performance in Microsoft Internet Explorer 8 web browser. |
| Linux. | Performance of Linux clients is impoved for some scenarios. | In some scenarious, Linux clients lacked efficiency. | Improved performance of Linux clients. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Applied objects. | Before restructuring an infobase, the platform checks whether user-created object attributes or tabular sections with reserved names are present in exchange plans. The list of reserved names in English includes: Ref, Code, Description, DeletionMark, ThisObject, DataVersion, AdditionalProperties, SentNo, and ReceivedNo. The list or reserved names in Russian includes: Ссылка, Код, Наименование, ПометкаУдаления, ЭтотОбъект, ВерсияДанных, ДополнительныеСвойства, НомерОтправленного, and НомерПринятого. If any exchange plan contains attributes or tabular sections with names listed above, the infobase cannot be restructured. This change is not implemented in 8.3.3 compatibility mode. | Before restructuring an infobase, the platform did not check whether object attributes and tabular sections with reserved names were present in the exchange plans. | The system behaves as expected during infobase restructuring. |
| Applied objects. | In the FillCheckProcessing() handler, if the Cancel parameter is set to True, event subscription execution is interrupted for the following objects: catalogs, documents, register record sets (including recalculations), document sequences, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks. This change is not implemented in 8.3.3 compatibility mode. | In the FillCheckProcessing() handler, if the Cancel parameter was set to True, event subscription execution was never interrupted. | The system behaves as expected. |
| Common attributes / Data separation. Managed locks. | In sessions that do not use separators, when data is being written or deleted, managed locks are set not only by reference and explicitly specified fields, but also by common attributes that serve as separators and include the object being written or deleted. The common attributes that are not separators can be used in the DataLockFields configuration object property. The DataLockFields list of attributes cannot contain common attributes that serve as separators in the Independently and simultaneously mode. You can specify such attributes as names for lock spaces of DataLock objects. If the separator value used in the DataLock object differs from the separator value used in the session, an exception is raised. These changes are implemented for the following object types:
| In sessions that did not use separators, when data was being written or deleted, managed locks were set only by reference and explicitly specified fields. The common attributes that were not separators could not be used in the DataLockFields configuration object property. Such common attributes could not be used as names for lock spaces of DataLock objects. | The number of lock collisions is reduced. In sessions that do not use separators, you can modify data in any data areas within a lock space provided that the data does not belong to the area where the lock has been set. For example, a lock is set to the Products catalog in the O1 area. You can modify data in any areas where the separator value is not equal to O1. |
| Spreadsheet documents. | When a spreadsheet document is saved to a PDF file, charts (Chart, GanttChart, and Dendrogram objects) are saved in the vector format. | When a spreadsheet document was saved to a PDF file, charts were saved as bitmap images. | The resulting PDF file size is reduced. Charts are resized when the file display area is changed in the PDF file viewer program. |
| Configuration repositories. | The history of comments entered by users when they store objects to the configuration repository is implemented. The history stores last 20 comments. Users can enter comments (which are saved to the history) when they lock repository objects. Users can select comments from the history when they store objects to the repository. | Comments that users entered when they stored objects to configuration repositories were not saved to a history. |
In the configuration repository, improved usability of repeated object storing operations related to a single task, such as step-by-step implementation of a single feature. |
| Access rights. | You can specify multiple roles to be used for defining access rights when the user list is empty. The DefaultRoles configuration property is implemented. The DefaultRole property is supported for compatibility purposes. If the compatibility mode is disabled, accessing the DefaultRole property raises an exception. In 8.3.3 version compatibility mode, you can only specify a single role in the DefaultRoles property. | Only a single role could be specified as the default one. | Simplified development of applied solutions that can be run with or without user list. |
| Applied objects. | For configuration objects that can contain predefined data, you can set the PredefinedDataName property to a value of a custom type, which consists of the # character and the text presentation of a unique identifier. | The value of the PredefinedDataName property could be set only in the load mode (when the DataExchange.Load property was set to True). | You can load predefined data from files that have custom format. |
| Automated testing. | For user action log entries that are generated as a result of user interaction with managed form fields, buttons, groups, tables, and decorations, the name attribute is implemented. It stores the name of the form item accessed by user. The user action log conversion data processor includes the option that defines how the search for form items is performed: by presentation or by name. | Form item presentations were recorded to the user action log. The user action log conversion data processor only supported search for form items by item presentation. | The automated testing is more reliable. Search for form items by name is available, which eliminates the dependence of automated tests on localization language, item presentation typos, item presentation uniqueness, and so on. |
| Spreadsheet documents. | Spreadsheet documents are printed with the scale specified in their print options. This change is not implemented in 8.3.3 compatibility mode. | On some printers, spreadsheet documents were printed at 200% scale. | If a spreadsheet document is printed using a scale different from 100%, the system behaves as expected. |
| Dynamic lists. | In dynamic list filters, you can specify tabular section fields of objects that are used in the query that generates the dynamic list. This change is not implemented in 8.3.3 compatibility mode. | Tabular section fields of objects could not be used in dynamic list filters. | The list of dynamic list features is extended. |
| Dynamic lists. | During the retrieval of dynamic list data, dynamic list settings that are disabled by functional options are deleted. This change is not implemented in 8.3.3 compatibility mode. | Settings disabled by functional options were not removed from dynamic list settings. | Unexpected system behavior is eliminated. |
| Interface. | The colors of the sections panel and current section command panel in the Taxi interface are changed. When the current section command panel orientation is vertical, its title is not displayed. The presentation of current section command panel is changed to current section function panel. | The colors of the sections panel and current section command panel in the Taxi interface were different. If the current section command panel orientation was vertical, its title was displayed. | Better usability inTaxi interface mode. |
| Development tools. Configuration repositories. | You can quickly view the selective change history of configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. Selective history is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, objects included in exchange plans, styles, main section working areas, flowcharts, forms, help pages, predefined items, command interface fragments, and role rights. To view the selective history, right-click anywhere in any of the repository dialog boxes or in the configuration comparison window, and then click View selective history. In the Filter repository versions dialog box, filter by properties of selected configuration objects is added. Viewing selective history is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later. | This feature was not provided. Only the full object change history was available. | Improved usability of configuration repository. Viewing the history of items that are parts of configuration objects is simplified. |
| Web client and web service publishing tools. | In Designer, in the dialog box for publishing the web client and web services:
| Managing execution of background jobs in file mode and specifying whether web services are published by default were only available when publishing was performed using the webinst utility (based on a template). The publishing dialog did not provide access to managing these features. | You can specify all of the options available in the default.vrd file during interactive publishing. |
| Spreadsheet documents. | You can use the ViewScalingMode property of spreadsheet document form extension to specify how the spreadsheet document will be displayed: as in platform version 8.2 or enlarged. | This feature was not provided. Reports with large fonts looked too large in the Taxi interface mode. | You can scale displayed spreadsheet documents that have custom (large) fonts. |
| Dynamic lists. | In dynamic lists, presentation fields cannot be used in filters, groupings, or ordering. Searching by presentation fields is not available. | In dynamic lists, presentation fields could be used in filters, groupings, or ordering. Search by presentation fields was available. | Unexpected system behavior is eliminated. |
| External data sources. Data composition system. Queries. | In external data sources, you can use functions specified in them. A function can return a value, or a table, or nothing.
You can specify types of external data source tables: table or expression (this is required to describe functions that return tables).
To call an external data source function, use one of the following query language expressions:
You can call functions using the object model. This can be performed with either external data source managers or external data source table managers. In the picture library, the ExternalDataSourceFunction is implemented. | External data sources did not support functions. |
The external data source functionality is extended. |
| Data composition system. | If an aggregate function is used in the RecordsFilter parameter of the EvalExpressionWithGroupArray() or EvalExpressionWithGroupValueTable() functions, an error is generated. This change is not implemented in 8.3.3 compatibility mode. | Using aggregate functions in the RecordsFilter parameter of the EvalExpressionWithGroupArray() and EvalExpressionWithGroupValueTable() functions did not generate an error. | Unexpected system behavior is eliminated. |
| Web client. | In Microsoft Internet Explorer 10 web browser, in managed form text boxes, the Clear input system button is removed. | In Microsoft Internet Explorer 10 web browser, in the managed form text box, the Clear input system button had the same functionality as the Clear button, which was added by the platform. | Eliminated web client appearance differences between Microsoft Internet Explorer 10 and other web browsers. |
| Configuration repositories. | The Update configuration from repository command is executed without displaying a dialog box if new objects are found in the repository. New objects are automatically created in the target configuration. | The Update configuration from repository command opened a dialog box if new objects were found in the repository. If a configuration was updated using Designer batch mode and new objects were found in the repository, the update was not performed. | Applied solution configurations can be updated automatically (for example, using the a batch file). You can include the update in various scheculed tasks, such as automated testing. The configuration update no longer requires interactive actions, which can pause the batch file execution. |
| Interface. | The splash screens for Designer and all types of client applications are modified: borders are used instead of shadows. | The splash screens had shadows. | Eliminated splash screen drawing issues in a number of scenarios. |
| Common objects. | Checks that determine whether defined type contents are valid are performed for each defined type call in the following scenarios:
The check is only performed when the Compatibility mode configuration property is set to Version 8.3.3 or None. If the compatibility mode is set to version earlier than version 8.3.3, defined type contents are only checked for the presence of external data source functions. | The checks whether defined type contents were valid were only performed when the dialog box for specifying configuration object attribute type was generated. When a configuration was saved, the checks whether defined type contents were still valid were not performed for each defined type call. | Eliminated several potential issues that could occur during the development of applied solutions with defined types. |
| Managed forms. | In 8.2.16 version compatibility mode, if a text box does not have the selection list mode enabled, its drop-down lists do not contain the selection list specified in the text box properties. | In version 8.3.3, drop-down lists in text boxes always contained the choice lists specified for these text boxes. | Redesign is not required for applied solutions that run in version 8.2.16 compatibility mode. |
| Standard functions. Common attributes / Data separation. | The standard Delete marked objects data processor attempts to set the exclusive mode for object deletion if the configuration compatibility mode is set to Version 8.3.3 or later (including the None value of the Compatibility mode property). If the configuration has Version 8.3.2 or earlier compatibility mode, the exclusive mode is only set for sessions that do not use separators or in configurations that are not separated. | The standard Delete marked objects data processor attempted to set the exclusive mode for object deletion only if deletion was performed either in a session that did not use separators or in a configuration that was not separated. The compatibility mode did not affect the criteria for setting exclusive mode. | You can delete marked objects in sessions that use separators. |
| Applied objects. | An automatically assigned object number is reused if the transaction where the object was written is cancelled, regardless of the value of the Objects Autonumbering Mode configuration property. | If the Objects Autonumbering Mode configuration property was set to Do not Release Automatically, an object number was not reused when the transaction where the object was written was canceled. | Eliminated unexpected system behavior. |
| XML and XDTO support. | When data is deserialized from XML- or XDTO-serialized files, the Predefined items are ignored for tabular sections of charts of accounts and charts of calculation types. If such items are found, no errors occur and data is deserialized successfully. | During the attempt to deserialize items of a chart of accounts or a chart of calculation types, having the Predefined item in a tabular section resulted in an exception and the deserialization could not be performed. | You can load data serialized in later versions of 1C:Enterprise (version 8.3.5 and later). |
| Third-party software. | The OpenSSL library is updated to version 1.0.0m. | OpenSSL version 1.0.0l was used. | Eliminated OpenSSL security issues. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Information registers. | For information registers with Enable totals for retieving slice first or Enable totals for retrieving slice last property enabled, the Active and LineNumber fields are removed from the list of fields of information register slice first/last virtual tables. If Enable totals for retieving slice first or Enable totals for retrieving slice last property is disabled, the Active and LineNumber fields are included in the slice first/last virtual tables.
| The Active and LineNumber fields were included in the list of fields of information register slice first/last virtual tables. | The system behaves as expected. In managed forms, the form items linked to the Active and LineNumber fields are removed automatically. |
| Managed locks. | Managed transaction locks (the DataLockFields property) cannot be set by attributes of objects of the following types: string of unlimited length, value storage, characteristic value type, and complex types that include these types. The check is performed during the configuration check, and an error message is displayed if any field does not comply with the limitations. | It was recommended that you did not use attributes of the following types in managed locks: string of unlimited length, value storage, characteristic value type, and composite types that included these types. During the configuration check, the check for managed locks by attributes of these types was not performed. | The configuration performance is optimized. Improved quality control during configuration development. |
| Access rights. | The IsInRole() function raises an exception in the following cases:
This change is not implemented in 8.3.3 compatibility mode. | The IsInRole() function did not check the parameter value and returned True even when the passed role was missing from the configuration. | The system behaves as expected. |
| Data composition system. | When data composition is performed from 1C:Enterprise script, the platform checks whether the privileged mode is enabled while getting the list of available fields. This change is not implemented in 8.3.3 compatibility mode.
| When data composition was performed from 1C:Enterprise script, the platform did not check whether privileged mode was enabled. | If privileged mode is enabled, data composition can include fields that users cannot access. |
| Web services. | The values of the WSParameterDirection system enumeration are corrected:
This change is not implemented in 8.3.3 compatibility mode. | The values of the WSParameterDirection system enumeration represented the following:
| Unexpected system behavior is eliminated. |
| Data exchange. |
A flag that specifies whether predefined data should be updated for the entire infobase is now available. It can be set both in 1C:Enterprise script and in the command line. In the 1C:Enterprise mode, the predefined data update procedure checks the flag that is set for the entire infobase (in addition to checking the flags set for individual configuration objects, checking the flags set for infobase data, and checking the infobase type: master/not distributed infobase or subordinate infobase). The global context methods SetInfoBasePredefinedDataUpdate() and GetInfoBasePredefinedDataUpdate() are implemented. The command-line option /SetPredefinedDataUpdate is implemented for Designer batch mode. This change is not implemented in 8.3.3 compatibility mode. | The check whether predefined data should be updated was based on infobase data and metadata flags and on the infobase type. | You have the option to set predefined data update flags easily for infobases that are disconnected from distributed systems for maintenance. Also, the following scenario is now supported: exchange in a nondistributed infobase between two similar applications where predefined data is set in one of the applications and should be replicated to the other one during the exchange. |
| Applied objects. | In the thick and thin clients, the WriteParameters parameter is implemented for the AfterWrite handler of managed form extension handlers for constants, information register records, and register record sets. In version 8.3.3 or earlier compatibility mode, the parameter always has the Undefined value. The description of the WriteParameters parameter is added to the AfterWrite Syntax Assistant entry. | The AfterWrite handler of managed form extension handlers for constants, information register records, and register record sets lacked the WriteParameters parameter. The description of the WriteParameters parameter was missing from the AfterWrite Syntax Assistant entry. | Unexpected system behavior is corrected. |
| Dynamic lists. Functional options. | The main managed form attribute of Object(CatalogObject, DocumentObject, and so on) type is disabled if a functional option disables the corresponding configuration object. The main managed form attribute of DynamicList type is disabled if a functional option disables a configuration object that is used a main table for the dynamic list. In both cases, only functional options without parameters are taken into account. | In 1C:Enterprise version 8.2, the main form attribute of Object type was not disabled even if any functional option disabled the corresponding configuration object. In 1C:Enterprise version 8.3, the main form attribute of Object type was disabled if a functional option disabled the corresponding configuration object. All functional options were taken into account. In the previous 1C:Enterpise versions, the main form attribute of DynamicList type was disabled if a functional option disabled the configuration object that was used as a main table of the dynamic list. All functional options were taken into account. | The system behaves as expected. In particular, the following issue is eliminated:
|
| Managed forms. | If the interface compatibility mode is set to Version 8.2, text boxes have the following specifics:
| In Version 8.2 interface compatibily mode,the text box behavior was identical to the text box behavior in Taxi interface compatibility mode. | For users who migrated to 1C:Enterprise version 8.3 while keeping Version 8.2 interface compatibility mode, the system behavior is similar to previous versions. |
| System requirements. | Microsoft Windows 2000 operating system is no longer supported. | Microsoft Windows 2000 operating system was supported. | An outdated operating system is no longer supported. |
| Client application. | Client computers that run operating systems of Windows family require Microsoft Internet Explorer web browser version 7.0. On computers with Microsoft Internet Explorer version 6.0 or earlier, users of thick and thin clients of version 8.3.4 or later might experience various issues. | Client computers that run operating systems of Windows family required Microsoft Internet Explorer web browser version 6.0 or later. | The out-of-date web browser is no longer supported. The platform features that use Microsoft Internet Explorer now require Microsoft Internet Explorer version specified in the platform system requirements. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| System requirements. | Mobile platform now supports x86 Intel CPU-based devices that run Android OS. The mobile platform for x86 architecture is provided in a separate file. The mobile platform distribution kit contains the following files:
| The mobile platform did not support x86 Intel CPU-based architecture. | More devices are now supported. |
| Development tools. | Mobile application builder is a new applied solution intended for building mobile applications. It has the following features:
Mobile application builder can build mobile applications for Android x86 operating systems. It can also perform full building of mobile applications for iOS using a Mac computer with Xcode installed. The configuration is delivered together with the mobile platform distribution kit. The data processor used for building mobile applications is removed from the mobile platform distribution kit. Building can be performed using any Android SDK version. | A data processor was used for building mobile applications. It was included into the mobile platform distribution kit. | Simplified building of mobile applications. Building mobile applications for iOS no longer requires additional steps. |
| System requirements. | Android version 2.2 is no longer supported. | Android version 2.2 was supported. | Support of the obsolete operating system version has ended. |
Version 8.3.3 includes known bug fixes and functionality modifications.
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.2 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, 8.2.16, and 8.3.1. | In version 8.3.3 you can run configurations created in version 8.3.2 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.3 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.2 for working with the infobase even after the transition to version 8.3.3. 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). |
| Managed forms. | You can specify settings for vertical scaling of form elements, namely the minimum element height, at the development stage in Designer using the new VerticalScroll property. If a form has a vertical scroll bar and the command bar is located above or below all form elements and occupies the entire form width, the area being scrolled does not include the command bar. | Managed form elements could be reduced to the default minimum height by reducing the form height. If a managed form had a vertical scroll bar, the area being scrolled included all form elements. | Elements of managed forms with vertical scroll bars cannot be compressed below the minimum height guaranteeing comfortable work. The command bar with important form commands, such as Write and close, is always available because it is not included in the area being scrolled. |
| Managed forms. Web client. | In the web client, if the VerticalScroll property of the managed form is set to UseIfNecessary, reducing the vertical form size never leads to reducing the vertical size of the form elements to the point where they can no longer be used. | In the web client, reducing the vertical form size could lead to reducing the vertical size of the form elements to the point where they could no longer be used. | Eliminated situations when reducing the vertical form size led to reducing the vertical size of the form elements to the point where they could no longer be used. |
| Development tools. | In the built-in script editor, you can group an arbitrary number of lines in the same way as they are grouped in some syntax units (conditions or cycles). #Region and #EndRegion preprocessor instructions are implemented. These instructions are ignored during script execution. A template for creating a script fragment with line grouping is added to the set of standard templates. | This feature was not provided. Only a few script syntax units allowed line grouping. | Improved usability for working with source text. You can group parts of source text in a logical way and hide text that is not used at the moment. |
| External data sources. | Support of the following OLAP sources is added to the external data sources mechanism:
Requests to OLAP sources and errors that occur during the request execution are recorded to the EDS event of the technological log. The following pictures are added to the picture library: ExternalDataSourceCube, ExternalDataSourceCubeDimensionTableObject. | External data sources provided access to relational tables only. | Both relational data and OLAP sources can be used when creating reports based on data from external systems (external data sources). |
| Interface. | You can get the resolution and DPI of monitors connected to a computer in the client application (thin client, thick client, web client) and at the server. For the external connection, the GetClientDisplayInformations() method returns UNDEFINED. The information on characteristic of client computer monitors is passed through at the session start and when the RefreshInterface() method is called. | You could get the information on monitors connected to a computer only on the mobile platform. | You can determine the number of monitors connected to the computer where the application is being executed, as well as their characteristics. |
| Data composition system. | For conditional appearance elements, you can specify areas where the given conditional appearance element will be used. This feature is not used in dynamic lists. This change is not implemented in 8.3.2 compatibility mode. | The conditional appearance was applied both to data area and area header, without further customization | Extended formatting capabilities for complex reports. |
| Web client and web service publishing tools. | Infobases, web services, and mobile applications can be published from Designer that is running on Linux. Publishing can only be performed to Apache web servers and only if Designer is running under root account. | Publishing of infobases and web services on Linux was possible only using the webinst utility. Publishing mobile applications was not available on Linux. | Eliminated some Designer limitations on Linux. |
| Linux. | You can create distribution kits in the Linux version of Designer. The platform distribution files now include an installation program that installs templates and updates for applied solutions that run on Linux. The installation program supports both 32-bit and 64-bit Linux versions. The installation program shares the list of Linux operating systems with the client application. | Creation of distribution kits was not available on Linux. | You can install templates and update applied solutions on Linux operating systems. |
| Autorun. | The Autorun application is capable of running on Linux. The application supports both 32-bit and 64-bit Linux versions. The application shares the list of Linux operating systems with the client applications. The following properties are added to the Element section of the autorun.lst configuration file: CommandWindows, CommandLinux, and RunAsRoot. The properties specify how a given item is executed in various operating systems. | The Autorun application was not available for Linux systems. The autorun.lst configuration file did not include CommandWindows, CommandLinux, and RunAsRoot properties. | You can create applied solution distribution kits that include the Autorun application and are delivered on removable media that can be used to install the solution on both Windows and Linux operating systems. |
| Applied objects. Managed forms. | Objects of reference types can be created while data is being entered in a form. A new property of configuration objects and form elements is implemented for this feature. The form element property manages the visibility of the command that creates a choice list element. The feature is implemented for catalogs, documents, charts of characteristic types, charts of accounts, charts of calculation types, business processes, tasks, and exchange plans. The command for creating a choice list element is not available in version 8.3.2 compatibility mode. | This feature was not provided. Users had the option to open the choice form and create an object there, and then select the created object. | Improved usability in cases when object creation is required while data is being entered. |
| Managed forms. Development tools. | In the managed form editor, the list of elements available for adding to the form now includes a usual group without a title. | In the managed form editor, in order to create a usual group without a title, a developer had to add a usual group and then change the properties that define whether the title is displayed. | Improved usability of editing managed forms when groups are used for defining element positions on the form. |
| Managed forms. Development tools. | During the generation of event handlers for client form elements and commands, you can specify which procedures will be generated:
A context server procedure cannot be generated for those client handlers where calling context server procedures is not recommended. | When a client handler was generated, this only included the generation of the handler itself. The associated procedures were not generated. | Simplified development of forms where actions that are called at client are executed at server. Developers no longer have to create the server method manually and then add the method call to the client handler body. |
| Configuration repositories. | The data storage format of the configuration repository is modified. Repository objects are stored in the file system. The 1cv8ddb.1CD file stores information on changed objects. The compatibility mode is implemented for the configuration repository. The new storage format is available only if the compatibility mode is disabled. Optimization of configuration repository data is introduced. The optimization procedure is available both from the repository administration window and by using the ConfigurationRepositoryOptimizeData command-line option when Designer is started in batch mode. The format of configuration repository files is not intended for reading or writing by any tools other than 1C:Enterprise. | All configuration repository data was stored in the 1cv8ddb.1CD file. Optimization of the configuration repository was not available. | Significantly increased number of changes (versions) that can be stored in the configuration repository. |
| Development tools. Client application. | The infobase selection dialog box and the two authentication dialog boxes (for access to infobases and configuration repositories) that are displayed during the start of a client application or Designer can be disabled. To disable them, use the DisableStartupDialogs command-line option for the 1cv8.exe/1cv8 file. If the command-line that starts a client application or Designer contains errors that led to displaying these dialog boxes in earlier platform versions, the dialog boxes are not displayed; diagnostic messages are generated instead. These messages are recorded to the file that stores service messages (the Out command-line option). | During the start of client application or Designer in the batch mode, provided that infobase parameters or authentication parameters contained any errors, modal dialog boxes that prompted users to enter the correct parameters were displayed. This paused the execution of the entire batch. | When Designer is started in batch mode - especially if Designer is started from another application or service - it is now possible to avoid the hard-to-detect situations when Designer attempts to create a selection dialog box for parameters that cannot be specified interactively, and therefore stops responding. |
| Localization. | The NumberInWords() and PeriodPresentation() global context methods support French language. The language code is as follows: fr, fr_CA. Values of the NumerationItemOptions parameter of the NumberInWords() method are specified similar to English, Finnish, and Kazakh languages. | The NumberInWords() and PeriodPresentation() global context methods did not support French language. | Improved presentation of information for French-speaking users. |
| Managed forms. Full-text search. | For the FullTextSearchList object, you can disable the search by presentations of configuration objects. Use the MetadataUse property of this object to enable or disable this feature. | The search by presentations of configuration objects could not be disabled. | You can search by data only, without seaching by presentations of configuration objects at the same time. |
| 1C:Enterprise script. | For the Array, Structure, and Map collections implemented constructors that create these objects based on the corresponding fixed collections (FixedArray, FixedStructure, and FixedMap). Recursive conversion is performed for arrays—a fixed array item that is a fixed array itself is recorded to a regular array. | Fixed collections could be converted to their regular analogs only by using program loops. | Simplified editing of values stored in fixed collections. |
| Common attributes / Data separation. | Exclusive access can be set for a data area. Exclusive access is not compatible with any data locks set by other sessions in this area. Exclusive access to a data area must be explicitly set or removed using the SetExclusiveMode() method. When a background job is started from a session that set exclusive access to a data area, the background job obtains exclusive access and the parent session loses exclusive access until the parent session is completed. At this time, changing data from the parent session is not available. Exclusive access is returned to the parent session after the background job completion. When a session switches to a different area, this does not affect the list of areas where the session has exclusive access. Exclusive access to an area prohibits the following actions:
Setting shared managed locks for an area is ignored if exclusive access is set for this area. | Exclusive access to a data area could not be set. Instead, you only could set an exclusive managed transaction lock to all area-contained data. | You can perform consistent changes of the data area even if they cannot be included into a transaction. |
| Common objects. | The DataHashing object can calculate the SHA1 and SHA256 hash functions. | The DataHashing objects could calculate only the MD5 and CRC32 hash functions. | The list of supported hash functions is extended. |
| Applied objects. | You can create defined types. A defined type consists of one or several allowed types, and it has a unique name. Defined data types can be used as types of configuration object attributes. Defined types cannot be included in complex types and cannot be used as data types for charts of characteristic types. If you want to run the applied solution on a previous platform version, you have to remove all defined types from the configuration. | This feature was not provided. | You can create a type that can be used for defining types of specific attributes. For example, in a universal multipurpose configuration fragment, you can describe attributes that refer to data that will be defined when the fragment is included into a specific configuration. |
| Mobile application. | You can choose a ZIP archive containing multiple pictures of different sizes, instead of a single picture, for the application. This option is targeted for mobile applications that can be used in devices with different screen resolutions. The following mobile device screen types are supported:
Each picture corresponds to specific screen settings of the target device. It is recommended that you use the PNG format for the archived pictures and you create the archive without compression. For the Picture object, the ChoiceSet property is implemented. | This feature was not provided. On the mobile platform, the developer had to specify multiple picture versions for various screen resolutions using 1C:Enterprise script. | Simplified process of creating applications intended for running on both PC and mobile devices. The developer only has to provide pictures for different display resolutions, and they do not have to write the script for resizing the pictures before displaying them in the 1C:Enterprise mode. |
| Accumulation registers. Accounting registers. | In accumulation and accounting registers, the interval for storing totals by periods can be limited. You can specify both the lower and the upper boundary of the interval. Totals within this interval can be recalculated automatically when totals outside of the interval are changed. Totals by periods are not stored outside of the interval. They are calculated by register record tables when needed. For accumulation register managers and accounting register managers, the following methods are implemented: SetMinTotalsPeriod(), GetMinTotalsPeriod(), and SetMinAndMaxTotalsPeriods(). The totals storage limits are taken into account when the chart of accounts is changed, when register records are generated, when totals are recalculated, and when balance is obtained by balance accumulation and accounting registers. When totals are enabled, periods are only recalculated if they contain actual changes. This change is not implemented in 8.3.2 compatibility mode. | Totals were stored by all periods later than the period of calculated totals for the register. When register records were changed for a prior period, all totals were recalculated for periods later than the modified date. When using totals was turned on, all register totals were also recalculated. | This change reduces database size and optimizes performance of administrative operations. This decreases the system load for databases that store data for long periods (several years), and where changes in prior periods are performed on regular basis but regular data retrieval (using totals) is performed within a limited time interval from the current date. |
| Add-ins. | The add-in creation functionality includes the option to display interactive messages to users and the option to store values between sessions in a local web browser cache. The add-in development technology documentation (http://1c-dn.com/library/add_in_creation_technology/) is updated by enhancing examples and adding new versions of web browser adapters. | The add-in creation functionality did not include the option to display interactive messages to users or the option to store values between sessions in a local web browser cache. | When a web browser add-in attempts to access local resources, warnings can be displayed. They are similar to warnings available in the built-in platform features. |
| Web client. Spreadsheet documents. Printing documents. | Documents intended for printing can be combined into batches. To print the entire batch, you only have to start printing once. You can specify printing options for batches. Batches can be nested. A batch can be written to a single PDF file, which simplifies printing in the web client. The RepresentableDocumentBatch object is implemented. | Batch printing was not available in the web client. To print a set of documents, the user had to click the Print button for each single document. | Improved usability of printing muptiple documents (with different printing options) in the web client. To print a batch of documents, the user has to start printing once (regardless of the number or documents in the batch), and the printing options (including page orientation and the number of copies) will be set for each individual document. |
| Server clusters. | In the client/server mode, security profiles are implemented for the purpose of managing applied solution access to the following external resources on 1C:Enterprise server: file system, COM objects, add-ins, operating system applications, Internet resources, privileged mode, external reports and data processors, and global context methods Execute() and Eval(). A security profile can be assigned to each infobase; a security profile can also be assigned to the source code that is executed in the safe mode. For the purposes of software cluster administration:
Similar changes are implemented in:
| This feature was not provided. | You can limit access of applied solutions to the resources of the system in which they run by using administrative tools (without modification of the applied solution source code). The functionality of the source code that is executed in the safe mode (for example, code developed by user) can be extended while preserving the required security level. For example, you can use security profiles to organize individual temporary storage directories for each data area, or describe the list of Internet resources available for use in a specific infobase. |
| Automated testing. | The following objects are implemented: TestedCommandInterfaceButton, TestedCommandInterfaceGroup, and TestedWindowCommandInterface. For tested objects, the GetObject() method is implemented. Its set of parameters is similar to that of the FindObject() and FindObjects() methods. If the object is not found, the GetObject() method raises an exception. Methods for testing user messages are implemented. The list of properties and methods for managing tested objects is extended. You can get the form name, the current window, the command interface, and so on. You can get the information on the last error that occurred in the tested client application. For the TestedApplication object, the methods GetActiveWindow() and GetCurrentErrorInfo() are implemented. For the TestedClientApplicationWindow object, the methods GetCommandInterface(), GetUserMessageTexts(), and ChooseUserMessage() are implemented. For the TestedForm object, the FormName property and the methods FindDefaultButton(), CurrentModified(), and GetCommandBar() are implemented, while the Close() method is moved to the TestedClientApplicationWindow object. For the TestedFormField object, the methods CurrentModeIsEdit() and GetEditText() are implemented, and the methods BeginEditCurrentArea() and EndEditCurrentArea() are modified. For the TestedFormTable object, the method CurrentModeIsEdit() is implemented, and the methods ChangeRow(), EndEditRow(), GotoPreviousRow(), GotoNextRow(), Expand(), and Collapse() are modified. For objects that describe tested form elements, the methods GetToolTipText(), CurrentVisible(), CurrentEnable(), CurrentReadOnly(), GetContextMenu(), and GetCommandBar() are implemented.
| The application window command interface could not be tested automatically. Operations on user messages were not available during the automated testing. | You can test the application window command interface automatically. In test scenarios, simplified the processing of errors that occur when attempts to get non-existent objects are made. |
| Dynamic lists. | Dynamic list settings can be saved automatically. For managing this feature, the Auto save user settings property is implemented for dynamic lists. For storing settings, the dynamic list settings storage is implemented. For managed form tables linked to dynamic lists, the following functionality is implemented: commands for saving and restoring settings, and events for implementing custom responces to saving, restoring, or editing dynamic list settings. The view mode of the dynamic list (list, tree, or hierarchical list) is stored together with form element settings. You can edit user settings of a dynamic list in a separate group of the form that displays the dynamic list. For that purpose, the User settings group property is implemented. Dynamic list settings can be edited in a separate common form, which is specified using the Default dynamic list settings form configuration property. For the DynamicList object, the SettingsComposer property is implemented, which is similar to the corresponding property of report objects. This change is not implemented in 8.3.2 compatibility mode. | For dynamic lists, only the following settings were saved automatically: filters (that were restored with disabled usage flag) and conditional appearance. To save and restore other settings, developers had to create custom algorithms in 1C:Enterprise script. | Improved usability of dynamic lists for end users. Simplified development of dynamic lists with quick access to filters for developers. Development of custom algorigthms for saving or restoring dynamic list settings is not required. |
| Managed forms. | A new permission allowing end users to expand or collapse a managed form group (only vertically) was added. If the permission is granted, a user can collapse the group (hide all of the items that are included in the group). For managed form groups, the following properties are implemented: Behavior, ControlRepresentation, ShowLeftMargin, and CollapsedRepresentationTitle. Only usual groups with displayed titles can be collapsed. | This feature was not provided. The only available method to hide unused items was to change their visibility. |
Hiding form items that are rarely used is available. This decreases the amount of data that is displayed to an end user. To view the hidden data, an end user can expand the group.
|
| Development tools. | On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed is displayed in the message window. | On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed was displayed in a modal window. |
Developers no longer have to close modal dialog boxes many times when they attempt to perform mass modification of objects that cannot be modified (for example, objects stored in a configuration repository that are not locked). |
| Interface. | A new client application interface type "Taxi" is implemented. The Taxi interface includes a large number of changes, with the following highlights:
Use the iTaxi command-line option of the client application for the forced start of this interface mode (provided that using Taxi is allowed in the applied solution). You can also switch between interface modes using the client application settings window. The following configuration properties are implemented:
A brand new look for the calendar. For the managed form calendar field, the following properties related to the new features are implemented: HeightInMonths, WidthInMonths, and ShowMonthsPanel. These properties are only used in the Taxi interface. For the ClientApplicationInterfaceVariant object, the ClientApplicationInterfaceVariant property is implemented (it is used for getting the interface mode), and the global context method ClientApplicationInterfaceCurrentVariant(). The ClientApplicationBaseFontCurrentVariant() global context method is implemented. It gets the size of the base font in the client application. For the UserWorkFavoritesItem object, the Important and Presentation properties are implemented. In the Taxi interface, the Desktop is renamed to Start page (the related commands are renamed accordingly). The Dashboard section of the section pane is used for accessing the command interface. In the Taxi interface:
The link to the start page (desktop) of the applied solution has the following format: e1cib/navigationpoint/startpage. Start page (desktop) settings are stored with the settings key StartPage/WindowSettings (for Taxi interface, StartPage/Taxi/WindowSettings). In the managed form editor, switching between interface 8.2 and Taxi modes in the preview window is implemented.
| The interface implemented in platform version 8.2 was used in managed applications. | Improved applied solution navigation, improved usability, development according to modern interface design trends. |
| Interface. | The NormalTextFont style font used as a basis for size calculation for other style fonts except the TextFont is implemented. The actual choice of font depends on the interface mode of the applied solution (Taxi or interface 8.2). | This feature was not provided. | Using the new font (and the fonts based on it) allows storing fort size proportions for managed form elements in both interface modes. |
| Interface. | The MainSectionPicture configuration property is implemented. In this property, you can specify a picture that will be used for the main section (desktop) in the section panel. | The desktop had a fixed picture that could not be changed. | You can create a uniform graphic design for your applied solution, and you can create a desktop look that will be friendly to the primary audience of the solution. |
| Development tools. | A context tooltip can be displayed for the parameters of the function or procedure that is being edited in the module text editor. If the method has several syntax variants, you can select the required variant. Automatic parsing of procedure and function comments for displaying them in context tooltips is implemented. Procedure and function comments can be sorted for displaying in the context tooltip. The comment format is described in the documentation and complies with the applied solution development standards. Procedure and function templates that comply with this format are included into the distribution kit. The option that shows or hides the context tooltips is implemented in Designer. In the source code editor, you can open the context tooltip by pressing Ctrl+Shift+Spacebar. | In Designer, context tooltip for procedure and function parameters was not available. The context tooltip was only available for names of applied solution procedures and functions. Comments to procedures and functions were not used for getting information on their parameters. | Improved usability of writing source codes. The Syntax Assistant is not required for a quick reference on the order and types of procedure or function parameters. |
| Administration tools. | The documentation describes DBMS setup and maintenance features that can be used for 1C:Enterprise administration. | The documentation did not describe the administration tools that could be used without violating the license agreements. | You can use DBMS features that do not affect the structure of data used by 1C:Enterprise (the changes that are made do not affect the restructuring and are saved after the restructuring). |
| Managed forms. | For fields of check box and radio button types, the tumbler look is implemented (several adjacent buttons where the active value has a different color). For managed form fields of these types, the properties CheckBoxType and RadioButtonsType are implemented. | This feature was not provided. | New presentation features. Improved usability for touch interfaces. |
| Database configuration updates. Server clusters. | Infobase restructuring is required when a chart of characteristic types is modified or when a chart of accounts where a chart of characteristic types is used as an extra dimension,is modified. The following changes are implemented in the background restructuring procedure:
| Charts of characteristic types were restructured when they were modified. All charts of characteristic types and exchange plans were restructured when the changes were applied (during the background restructuring). | In the background database configuration update, the specifics of changing some data structures are taken into account. This prevents mismatching of object data. |
| System requirements. | Microsoft Windows Server 2012 (x86-64) is now supported. | Microsoft Windows Server 2012 (x86-64) was not supported. | New version of the Microsoft operating system is now supported. |
| Data display. | If the Interface compatibility mode configuration property is set to Taxi or Taxi.Version 8.2 enabled, the Help picture from the picture library corresponds to the Taxi interface. | The appearance of the Help picture in the picture library did not depend on the configuration property values. | The appearance of the Help button depends on the interface mode. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Printing documents. | Changed behavior of print status forms in managed applications in thin and thick clients:
The form cannot be resized. | The print status form had different behavior. | Improved usability of printing documents. |
| Linux. | The Primary Selection clipboard is now supported (data is copied to this clipboard when a text fragment is selected, without the need to press any keys). Copying to the Primary Selection clipboard is supported for the following form elements:
Insertion from the Primary Selection clipboard (available by pressing the middle mouse button) is supported in text boxes. | This feature was not provided. | Improved usability of client application for users with Linux experience. |
| Managed forms. Functional options. | If a text box is linked to an attribute of complex type where all types except one are disabled by access rights or functional options, when user attempts to select a value in the text box, the choice value form is opened. This change is not implemented in 8.3.2 compatibility mode. | If a text box was linked to an attribute of complex type, when a user attempted to select a value in the text box, the type selection dialog box, was displayed even if the list of types contained a single value. |
Users do not have to select from a single value in the type selection dialog box. |
| Automated testing. | On closing an application, if the log of user actions is being recorded at the moment, a request for saving the log is sent. | On closing the application, unsaved data from the log of user actions was lost. | Reduced chance of losing unsaved data from the log of user actions when the application window that initiated recording to the log of user actions is closed. |
| Web client. | During the startup of the web client, the check for a pop-up window blocker is only performed if the separate window interface is used and modal windows are enabled.
The check for a pop-up window blocker is performed after the user authentication.
| The check for a pop-up window blocker was always performed during the web client startup. | Users are not prompted to specify the pop-up blocker settings when it is not required. |
| Interface. | On interface mode change, the user is prompted to restart the client application. | Changing interface mode did not prompt to restart the client application. | The procedure of changing the interface mode became more user-friendly: the system now informs the user what they have to do to have the changes take effect. |
| Standard functions. | The following changes are implemented in the standard functions:
| Standard function dialog boxes were less user-friendly. | Improved usability of standard functions. |
| Web client. | The documentation includes recommendations for choosing a web browser for low-performance computers. | The documentation did not include recommendations for choosing a web browser. | Recommendations for choosing a web browser are available. |
| Web client. | In Microsoft Internet Explorer web browser, notification windows do not fade out of view when they are closed automatically. | In Microsoft Internet Explorer web browser, notification windows faded out of view when they were closed automatically. | Improved performance of notification windows in Microsoft Internet Explorer web browser. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| DBMS operations. Accumulation registers. Queries. | Optimized performance of accumulation register virtual tables when obtaining totals with a filter that does not include all dimensions. | Insufficient performance of accumulation register virtual tables when obtaining totals with a filter that did not include all dimensions. | Performance of accumulation register virtual tables is increased. |
| Server clusters. | Creation of new sessions is optimized. | Creating of new sessions was performed inefficiently. | Optimized performance when establishing connections to the 1C:Enterprise server in the following cases:
|
| Information registers. | Improved performance of independent, non-periodic information registers that have more than 1 dimension. This change is not implemented in 8.3.2 compatibility mode. | Insufficient register performance. | Increased speed of writing to a register, especially when a large number of users are working. |
| Applied objects. | Optimized selections from catalogs and charts of characteristic types for certain scenarios. | In certain scenarios performance of selections from catalogs and charts of characteristic types was inefficient. | Increased performance of selections from catalogs and charts of characteristic types in certain scenarios. |
| Dynamic lists. | Improved dynamic list performance in client/server mode when a large number of users are working. | In certain scenarios dynamic list performance was insufficient. | Improved dynamic list performance in certain scenarios. |
| Server clusters. | Optimized processing of session data for some scenarios. | In some scenarios processing of session data was inefficient. |
Improved performance and scalability of 1C:Enterprise servers. |
| Accumulation registers. | Optimized execution of queries to turnovers registers with a large number of dimensions that include aggregates (for some scenarios). This change is not implemented in 8.3.2 compatibility mode. | In some cases execution of queries to turnovers registers with a large number of dimensions that included aggregates was inefficient. | You can use aggregate functions in more scenarios than before. |
| DBMS operations. | In order to optimize some queries to IBM DB2 DMBS, the recommendation to run the db2set DB2_OVERRIDE_BPF=5000 command and then restart the DBMS is included into the documentation. Methods of detecting situations when the optimization is required are also described in the documentation. | Some queries to IBM DB2 DBMS were performed inefficiently. | Optimized performance during the execution of some types of IBM DB2 DBMS queries. |
| Information registers. | For periodic information registers that are subordinate to recorders, the Active field is listed in the following indexes:
The Active field is the last one in these indexes. After changing the compatibility mode, full infobase restructuring must be performed for rebuilding indexes. This change is not implemented in 8.3.2 compatibility mode. | The Active field was not included in the list of indexes of periodic information registers subordinate to recorders. | Improved performance when retrieving the first and the last slices. |
| Server clusters. | 1C:Enterprise server is optimized to reduce memory usage and fragmentation. | In some scenarios, 1C:Enterprise server used memory inefficiently. This led to memory fragmentation and increased memory consumption. | Reduced memory consumption of 1C:Enterprise server, and lower memory fragmentation. This allows to reduce the number of planned 1C:Enterprise server restarts and improves the system stability. |
| DBMS operations. | Indexes of attributes with additional ordering include deletion marks and all fields that are indexed with additional ordering. This data is added to the end of the index. | Indexes of attributes with additional ordering did not include deletion marks and all fields that were indexed with additional ordering. |
Improved performance of dynamic lists filtered by multiple attributes (including the deletion mark). |
| Managed forms. | Optimized performance of displaying managed forms after server calls (both explicit and implicit ones) that change the form appearance. | Forms were not displayed fast enough when their appearance was changed from 1C:Enterprise script. | Optimized performance of displaying forms, for example, when the displayed title of a form element is modified. |
| Common attributes / Data separation. | Once the version 8.3.2 compatibility mode is disabled, optimization is performed on the structure that stores data on the table separators connected to objects included in the separator contents. When the version 8.3.2 compatibility mode is enabled, the reverse restructuring of the database tables is performed. | The structure that stored separator data was not optimal. | Improved performance due to the changes in the structure that stores separator data. |
| Server clusters. | In server cluster, the algorithm for balancing the working process load is optimized. The following parameters are used in addition to parameters used in the previous versions to define the available server performance: size of CPU queue, current processor load, and number of CPU cores. Values used for defining the available server performance are recorded to the TXT property of the CLSTR event in the technological log. To obtain performance parameters, the user on whose behalf the 1C:Enterprise server is running must be included in the Performance Log Users group. | In the server cluster, the algorithm for balancing the working process load took less number of parameters into account. | Improved reactivity of the load balancing algorithm. The algorithm defines overloaded CPUs and stops sending new tasks to them. |
| Managed forms. | Optimized performance of opening managed forms with multiline text boxes that contain a large number of line breaks. | Performance of opening forms with multiline text boxes containing a large number of line breaks was not high enough. | Forms with multiline text boxes that contain a large number of line breaks are opened faster. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Software licensing. | Licenses for basic configurations are available on Linux. | Basic version licenses for Linux were unavailable. | You can run basic 1C:Enterprise configuration versions on Linux. |
| Applied objects. | Infobase object autonumbering logic is revised. The check for number or code uniqueness (including automatically generated codes and numbers) is always performed while the object is being written. The message informing the user that a number or code is not unique now specifies the value of the non-unique number or code. Numbers or codes that are no longer used are never re-assigned automatically, even when the desired prefix is not specified explicitly. In the event when the desired prefix is not specified explicitly, the platform forms a number or code as follows: it selects the greatest of the prefixes that match the specified pattern and then adds the next subsequent number (prefixes are compared according to their alphabetical order, for example, B is greater than A). | The uniqueness check was not performed for automatically generated numbers or codes while the object was being written. The message informing the user that a number or code was not unique did not include the value of the non-unique number or code. Numbers or codes that were no longer used might be re-assigned automatically in the event when the desired prefix was not specified explicitly–the platform might assign a code that was used before when its prefix matched the specified pattern and the prefix was not the greatest one among those matching the pattern (prefixes are compared according to their alphabetical order, for example, B is greater than A). | Increased stability and reliability of infobase object autonumbering. Messages informing the user that a number or code is not unique now contain more information. The autonumbering is more logical: numbers or codes are always issued in the ascending order. |
| Applied objects. | If a text value presentation cannot be calculated during debugging, the string Error getting value presentation is returned as a text presentation. | If a text value presentation could not be calculated, Designer might stop responding. | Improved system stability during debugging. |
| Managed forms. | Visibility of the command for switching to the calculation register (in a recorder form) is set to True by default. This change is not implemented in 8.3.2 compatibility mode. | Visibility of the command for switching to the calculation register (in a recorder form) was set to False by default. | Default visibility of commands for switching to registers is the same for all registers. |
| Managed forms. | When attributes of Number type that have minimum or maximum values set are cleared interactively, the attribute values after clearing cannot exceed the specified limits. This change is not implemented in 8.3.2 compatibility mode. | When attributes of Number type were cleared interactively, their minimum and maximum values were ignored. | Users cannot enter data that does not meet the conditions specified by the developer. |
| Applied objects. | When a spreadsheet document is saved to a .docx file, image border styles are preserved. This change is not implemented in 8.3.2 compatibility mode. | When a spreadsheet document was saved to a .docx file, images always had borders. | More accurate export of spreadsheet document styles to .docx format. |
| Applied objects. | When a spreadsheet document is saved to a .docx file the following spreadsheet document print options are preserved:
This change is not implemented in 8.3.2 compatibility mode. | Print options were not preserved when a spreadsheet document was saved to a .docx file. | Improved usability of spreadsheet documents saved in .docx format. |
| Data composition system. | When a user field is added to data composition system settings and the source of available settings is not specified, the file name is generated using the language of the current script variant. This change is not implemented in 8.2.16 compatibility mode. | When a user field was added to data composition system settings and the source of available settings was not specified, the file name was generated in English. | The data composition system behavior is uniform with behavior of similar platform features. |
| File operations. | The look and behavior of the file selection dialog box (including the FileDialog object) in Windows Vista and later Windows versions complies with the standards of these operating systems. In Windows XP and earlier and in the web client the look of the dialog box is not changed. | In Windows Vista and later, an outdated file selection dialog box was used. | The look of the file selection dialog box corresponds to the operating system being used. |
| File operations. | If both Directory and FullFileName are specified for a FileDialog object, the dialog box is opened in the specified directory and with the specified file name. | If both Directory and FullFileName were specified for a FileDialog object, the dialog box ignored the specified directory and used the directory that was obtained from the full file name. | Improved usability of the file choice dialog. |
| Automated testing. | Wildcard support implemented for the InputText() method of the TestedFormField object. | The automated testing mechanism did not support wildcards in text input fields. | Extended functionality of the automated testing system. |
| Dumping/loading configurations to files. | When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName. Configurations dumped using earlier platform versions cannot be loaded. | When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName. | Command names are uniform; you can figure out the command purpose from its name. |
| Dumping/loading configurations to files. | When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName. Configurations dumped using earlier platform versions cannot be loaded. | When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName. | Command names are uniform; you can figure out the command purpose from its name. |
| Dumping/loading configurations to files. | When dumping a configuration to XML files, names of standard commands of managed forms follow this convention: Form.StandardCommand.CommandName. Configurations dumped using earlier platform versions cannot be loaded. | When dumping a configuration to XML files, names of standard commands followed this convention: FormStdCommand.CommandName. | Command names are uniform; you can figure out the command purpose from its name. |
| Dumping/loading configurations to files. | When dumping a configuration to XML files, names of managed form commands follow this convention: Form.Command.FormCommandName. Configurations dumped earlier will not be loaded. | When dumping a configuration to XML files, names of managed form commands followed this convention: FormCommand.FormCommandName. | Command names are uniform; you can figure out the command purpose from its name. |
| Dumping/loading configurations to files. | When dumping a configuration to XML files, names of standard commands of managed form elements follow this convention: Form.Item.ElementName.StandardCommand.StandardCommandName. Configurations dumped earlier will not be loaded. | When dumping a configuration to XML files, the standard commands of managed form elements followed this convention: Form<ElementType>.ElementName.StandardCommandName. | Command names are uniform; you can figure out the command purpose from its name. |
| Dumping/loading configurations to files. | When a configuration is dumped to files:
For elements of business process flowcharts, element identifiers are dumped. |
When a configuration was dumped to files:
| In dumping/loading of configurations, the following improvements are implemented:
|
| Managed forms. | When Esc is pressed in a text box (except multiline text boxes), the following actions are performed:
| Pressing Esc was always processed by the form. The text box did not perform any actions if Esc was pressed while the text was being edited. | You can cancel editing a value in a text box. |
| Managed locks. | The maximum number of managed locks is 100 000 (exceeding this limit locks the entire lock space). | The maximum number of managed locks was 20 000 (exceeding this limit locked the entire lock space). | Improved user experience when using transactions with a large number of locks (more than 20 000) in a single lock space. |
| Information registers. Data exchange. | When a set of information register records is passed to the SelectChanges() method as a filter value, the system behavior depends on the compatibility mode:
| When a set of information register records was passed to the SelectChanges() method as a filter value, the system behavior did not depend on the compatibility mode.
| Improved compatibility with previous platform versions. |
| Dynamic lists. | In the data composition system and query wizard, syntax units enclosed in braces {} do not lead to errors in dynamic lists. | In the data composition system and query wizard, syntax units enclosed in braces led to errors in dynamic lists in some cases. | Better stability of dynamic list. |
| Cryptography. | The value of the CryptoModuleName parameter in the CryptoManager object wizard is case insensitive. | The value of the CryptoModuleName parameter in the CryptoManager object wizard was case sensitive. | The system behavior complies with common standards. |
| Managed forms. Ordinary forms. | In managed and ordinary forms, if the second parameter (FormElement) of the ChooseFromMenu() method is a managed form table, a managed form, a table box, or an ordinary form, the menu that is opened using this method is displayed in the following location:
This change is not implemented in 8.3.2 compatibility mode. |
If the second parameter (FormElement) of the ChooseFromMenu() method was a managed form table, a managed form, a table box, or an ordinary form, the menu was displayed in the following location:
| Uniform behavior when the system opens similar menus (e.g. context menu in a managed form table) or the applied solution opens such menus (using the ChooseFromMenu() method). |
| Managed forms. Ordinary forms. | In managed and ordinary forms, if the second parameter (FormElement) of the ChooseFromList() method is a managed form table, a managed form, a table box, or an ordinary form, the list that is opened using this method is displayed in the following location:
This change is not implemented in 8.3.2 compatibility mode. | If the second parameter (FormElement) of the ChooseFromList() method was a managed form table, a managed form, a table box, or an ordinary form, the list was opened in the following way:
| Uniform behavior when executing similar actions (the ChooseFromMenu() and ChooseFromList() methods). |
| Development tools. | You can search and replace in the ChoiceParameters property of configuration objects. The search and replace algorithm is modified for the ChoiceList and ChoiceParameterLinks configuration objects.
The search and replace are performed:
Search in the LinkByType property of configuration objects is no longer supported. | Search and replace in the ChoiceParameterLinks property of configuration objects was performed only in the Name column. Search and replace in the ChoiceList property of configuration objects was performed only in the Presentation column. Search and replace was not performed in the ChoiceParameters property of configuration objects. Search could be performed in the LinkByType property of configuration objects. | The search and replace operations in configuration object properties are now uniform to similar operations in texts. |
| Development tools. | The presentation of the ChoiceParameters property of configuration objects in the object properties editing window is changed. If a value of any property element is a fixed array, presentations of array values are used. The presentation of the ChoiceList property of configuration objects in the object properties window is changed. A presentation now consists of both list item values and their presentations (if the presentations are specified). | If an element of a ChoiceParameters property was a fixed array, its presentation was a FixedArray string. For the ChoiceList property of configuration objects, the presentation in the object properties window was generated from the list item values only. | Improved usability of ChoiceParameters and ChoiceList properties in Designer. |
| Managed forms. | Improved look and behavior of drop-down lists in text box fields that can be edited and contain data of reference type, enumerations, or system enumerations:
If the drop-down list is not displayed and the characters typed in the field match multiple choice list values, pressing Tab, Shift+Tab, or Enter opens the drop-down list. Clicking another form element also opens the drop-down list. | The drop-down list had a different look and behavior. | Improved usability of text box fields that contain data of reference type, enumerations, or system enumerations. |
| Accumulation registers. | You can enable the aggregates mode for any turnovers accumulation register, regardless of the actual presence of aggregates in metadata. In the client/server mode you can create new optimal aggregates (and remove outdated ones) when aggregates are being rebuilt in 1C:Enterprise mode. This change is not implemented in 8.3.2 compatibility mode. | Developers had to add aggregates in Designer to keep the list of optimal aggregates up to date. | Simplified support of optimal aggregate list: you only have to rebuild aggregates on regular basis. |
| Managed forms. | In text boxes containing data of reference type, only the color of the text presentation of the value is changed on element activation. | In text boxes containing data of reference type, the color of the entire field changed on element activation. | Better text box usability. A tooltip can be displayed in a text box linked to data of reference type if the text box is first in the tab order of the form. |
| Development tools. Configuration repositories. | You can perform quick comparison of selected configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. Selective comparison is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, exchange plan content objects, styles, desktop workspaces, maps, forms, online help pages, predefined items, command interface fragments, and role rights. To run the selective comparison command, right-click anywhere in any of the repository dialog boxes or in the compare configurations window, and then click Perform selective comparison with the configuration object. Selective comparison of configuration objects is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later. | This feature was not provided. When comparison was initiated for a specific object, full comparison of two configurations was performed. The focus in the comparison window was set to that object. | Improved usability of configuration repository. Optimized comparison procedure when it is performed for a single configuration object. |
| DBMS operations. | Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later is now available. All of the required settings are specified automatically by the installation program of the patched PostgreSQL version unless a cluster created by the standard PostgreSQL version is found on the computer. | Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later was not available. | 1C:Enterprise supports clusters created by the following versions of PostgreSQL DBMS:
You can upgrade or downgrade 1C:Enteprise without upgrading or downgrading the associated PostgreSQL instance; this does not require any manual configuration. Note that once you migrate to a new PostgreSQL version, you cannot use 1C:Enterprise version 8.3.2 or earlier. This only applies to new infobases that were created using PostgreSQL 9.2.1-2.1C. Do not create infobases using PostgreSQL 9.2.1-2.1C if you are planning to access them from earlier platform versions. |
| Managed forms. | If the ChoiceDataGetProcessing event handler of the enumeration manager returns an empty list and the formal parameter StandardProcessing returned by this handler is set to False, the returned list is used for filling the choice list. This change is not implemented in 8.3.2 compatibility mode. | If the ChoiceDataGetProcessing event handler of the enumeration manager returned an empty list and the formal parameter StandardProcessing returned by this handler was set to False, the client application filled the choice list by all enumeration values. | The system behaves as expected when a developer decides to disable selection of enumeration values. |
| Standard functions. | In the default event log form, filter presentation is localized. | In the default event log form, filter presentation was always displayed with Russian names of event log columns. | The filter presentation is uniform with other platform features. |
| Configuration repositories. | Optimized the reference integrity check algorithm for configuration repository operations (storing and retrieving) on objects that are deleted from the repository and objects that reference to deleted ones. In some cases, it is not necessary to lock objects that contain references to objects being deleted during the deletion. The reference integrity check algorithm used when deleting objects from the repository is uniform with the reference integrity check algorithm used when deleting objects from a configuration that is not bound to a repository. This change is not implemented in 8.3.2 compatibility mode. | The reference integrity check algorithm for configuration repository operations was not optimized. The reference integrity check algorithm used when deleting objects from a repository was different from the reference integrity check algorithm used when deleting objects from a configuration that was not bound to a repository. | Eliminated problems that occurred when deleting objects from configurations because of the reference integrity check differences. Storing deleted objects to the configuration repository is optimized. |
| Managed forms. | In the managed mode of the thick client, if the In list editing mode is selected for a configuration object, calling the OpenValue() method or clicking the Open button in the text input area opens the regular list form, provided that the following conditions are met:
In all other cases, this opens the object form. This change is not implemented in 8.2.16 compatibility mode. | In the managed mode of the thick client, if the In list editing mode was selected, calling the OpenValue() method or clicking the Open button in the text input area opened the managed list form. | To display configuration objects that have the In list editing mode set, or for editing their elements, the system opens the regular list form. This behavior is more consistent than before. |
| Development tools. | The following changes are implemented in the configuration comparison feature:
| When configurations were compared:
| The configuration comparison is perfomed as expected. |
| Managed forms. | When a choice list is generated for form fields linked to data of EnumRef type, it is based on the choice parameters and choice parameter links of the form element. This change is not implemented in 8.3.2 compatibility mode. | When a choice list was generated for form fields linked to data of EnumRef type, the choice parameters and choice parameter links were not taken into account. | The choice list generation for enumerations is uniform with other similar system features. |
| Internet-enabled functionality. | For the InternetMailProfile object, the SMTPAuthentication property (which is obsolete) is set to SMTPAuthenticationMode.Default. This change is not implemented in version 8.2.16 compatibility mode. | For the InternetMailProfile object, the obsolete property SMTPAuthentication was set to SMTPAuthenticationMode.None. | The default settings of the authentication method is the safest among those supported by the mail server. |
| Internet-enabled functionality. | If the SMTPSecureAuthenticationOnly property of the InternetMailProfile object is set to TRUE, authentication attempts are performed independently of other settings. User authentication on the SMTP server is not performed in the following scenarios:
| User authentication on the SMTP server was not performed if the name of the SMTP server user was not specified (the SMTPUser property of the InternetMailProfile object). | User authentication on the SMTP server can be performed using a POP3 server if the SMTPSecureAuthenticationOnly property is not set. The value of the SMTPUser property of InternetMailProfile object does not affect this behavior. At the same time, the authentication is not performed if the mail server does not support the secure authentication methods. When connecting to a mail server, you can exclude insecure authentication methods from the list of available ones. |
| Software licensing. | If a license acquisition dialog box appears at the start of the client application, the first page of the dialog box specifies which kind of license (server or client) the application requires.
A hyperlink to 1C:Licensing center contact information is displayed on the license registration pages and on the page that appears when license activation is not successful. A dialog box that displays 1C:Licensing center contact information is added.
When a user types a PIN code or a response from a licensing center operator in the license aсquisition dialog box, once they have completed a text field, the cursor moves to the next field automatically.
| If a license acquisition dialog box appeared at the start of the client application, the first page of the dialog box did not specify which kind of license (server or client) was not found. The license registration pages and the page that appeared when license activation was not successful only contained information how to find 1C:Licensing center contacts in the printed documentation. When a user typed a PIN code or a response from a licensing center operator in the license aсquisition dialog box, the cursor did not move to the next field automatically. | Improved usability of license acquisition dialog box. |
| Spreadsheet documents. Web client. | The web client now supports text orientation in spreadsheet document cells. | The web client did not support text orientation in spreadsheet document cells. | Extended formatting capabilities for spreadsheet documents in the web client. |
| Server clusters. | When a cluster service is reassigned from one cluster manager to another, the service status is replicated to the new cluster manager and the service is shut down on the former cluster manager, which releases the resources used by the service. The status is replicated for the following services: object locks, numbering, and background restructuring. In the technological log, the <SRVC> event is implemented. It describes the following operations with cluster services: starting, stopping, and various alerts. Descriptions of operations being executed are generated in the Descr property. Each cluster manager stores its session data in a dedicated directory. You can choose how a working process is selected when a new connection is created: by available performance or by available memory. If the selection is performed by available memory, either the working process that currently maintains connections to the infobase is used, or the working process that is running on the server and has the maximum amount of available memory. In the cluster properties, the Load balancing mode property is implemented. For the IClusterInfo object, the LoadBalancingMode property is implemented. For starting a background job, the working process that maintains the session that initiated the background job is selected with the highest priority (this rule is ignored if the selection is performed by available memory). You can specify a priority for each assignment rule. If several identical assignment rules are found during assignment rule selection and all other conditions are equal, the rule with the highest priority is used. Assignment rules now have the Priority property. For the IAssignmentRule object, the Priority property is implemented. In the cluster mode of the server cluster administration utility (rac), the load-balancing-mode parameter is implemented for the create and update commands. Similar changes are implemented in the Java server administration API. When determining available working process performance, the CPU load of the working server and the number of threads in the execution queue are taken into account, in addition to other factors. | In some cases, used resources were not released after the reassignment of services. The status was not replicated for the following services: object locks, numbering, and background restructuring. In the technological log, there were no events that described operations with cluster services. Data belonging to all sessions was stored in a single directory, which could lead to access collisions. When a background job was created, the working process for handling the job was always selected by available performance. If several identical assignment rules were found during assignment rule selection, the rule that was applied could not always be determined unambiguously. When available working process performance was determined, the CPU load and the number of threads in the execution queue were not taken into account. | Increased fault tolerance of clusters. Improved quality and manageability of load balancing between cluster servers. A new setting ensures efficient memory usage when a cluster maintains a large number of infobases with a small number of sessions from each infobase. |
| Managed forms. | For unavailable groups, colors of the title and border (line) are changed. | For unavailable groups, the title and border (line) had different colors. | The look of unavailable groups is uniform with the look of other unavailable elements. |
| Applied objects. Common attributes / Data separation. Access rights. Data exchange. Mobile application. | Predefined data is available for configuration objects included in separator contents in the Independent and Shared mode. Predefined items can be linked to any data elements of matching type. The linking is optional. If data elements are not linked, the predefined data is considered empty. For configuration objects that can contain predefined data, the PredefinedDataName property is implemented. Support of predefined data items that refer to deleted predefined items is implemented. Identical references to predefined items are never generated, even for objects included in separator contents in the Independent mode, and even for items that belong to different areas. The GetPredefinedItemName() method is declared deprecated is only supported for compatibility purposes. Predefined data is registered in exchange plans like any other data. You can manage creation and update of predefined data in the infobase using the new configuration object property PredefinedDataUpdate and the new methods GetUpdatingPredefinedData() and SetPredefinedDataUpdate(). The global context method InitializePredefinedData() is implemented. Using this method, you can create data objects for predefined items that are not linked to any data (in the current data area).
Access rights and restrictions are specified simultaneously for the Predefined and PredefinedDataName fields.
These features are also implemented for the mobile platform. The new access rights InteractiveDeletePredefinedData, InteractiveSetDeletionMarkPredefinedData, InteractiveClearDeletionMarkPredefinedData, and InteractiveDeleteMarkedPredefinedData are implemented. They specify whether editing of predefined data is allowed. Restrictions for editing predefined data in charts of accounts and charts of calculation types are eliminated. Predefined data can be marked for deletion, and it can be completely deleted. A chart of accounts must be included into the contents of all separators that contain all extra dimensions used in the chart. The infobase restructuring process is modified. This change is not implemented in 8.3.2 compatibility mode. | Predefined data was not available for configuration objects included in separator contents in the Independent and Shared mode. Predefined data could not be linked to any existing data object. Each predefined item had identical references in all data areas. During data exchange in a distributed infobase, predefined data was replicated only together with applied solution configuration changes. Creation and update of predefined data were not available. | You can use predefined data in all separation modes. Predefined data management is more flexible than before. |
| Interface. | In the help topics, links to external resources are opened in the default web browser of the operating system. | In the help topics, links to external resources were opened in the built-in web browser of 1C:Enterprise. | Improved usability of viewing the resources that are opened by clicking links in the help topics. |
| Interface. | For new users, the interface mode is set to Forms in tabs, provided that the platform version compatibility mode is not used and the interface compatibility mode is set to Version82 or Version82TaxiAllowed. | For new users, the interface mode was set to Forms in separate windows. | The Forms in tabs interface is the default option for new users. This interface mode provides better usability. |
| Interface. | For a text box in a managed form table, the drop-down list is always opened at the start of editing. | For a text box in a managed form table, the drop-down list was opened at the start of editing only if the editing was started using the mouse. | Quick access to the drop-down list is implemented for text boxes located in managed form tables. |
| Common attributes / Data separation. 1C:Enterprise script. | After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state matches the state that the data area had when it was accessed for the first time. In particular:
| After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state did not match the state that the data area had when it was first accessed:
| After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the state of the data area now reflects its initial state much better than it did in the previous platform versions. |
| Application appearance. | New splash screens are implemented for Designer, client application, Autorun program, and the installation program. The splash screen size (and the size of the applied solution splash screen template) is 600 x 255 pixels. | Splash screens that were used for various parts of the system had different looks. The size of the applied solution splash screen template was 305 x 110 pixels. | The new splash screens better fit the new user unterface. |
| Managed forms. | When a value is entered or selected in a text box, it is converted to the text box value type, and then the value presentation is displayed in the text box. This change is not implemented in 8.3.2 compatibility mode. | When a value was entered or selected in a text box, the resulting text displayed in the box might not match the entered or selected value. | The system behaves as expected. Eliminated incorrect system behavior. |
| Client application. | The message that is displayed before updating a client application using an insecure connection is clarified. | The message was not clear enough. | The message describes the situation more clearly. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Dumping/loading configurations to files. | Only access rights that have nondefault values are included in dump files. The default values are defined by the Set rights for new objects and Set rights for attributes and tabular sections by default properties. Values of these properties are default values for access rights to metadata objects and access rights to attributes and tabular sections respectively. | All access rights were included in dump files, including those having default values. | Improved performance of dumping configurations to files. Reduced size of dump files. |
| Dumping/loading configurations to files. Applied objects. | When dumping a configuration to XML files, English descriptions of document journal selection types follow this convention: DocumentJournalSelection.DocumentJournalName. | When dumping a configuration to XML files, English descriptions of document journal selection types followed this convention: DocumentJournalsManager.DocumentJournalName. | Type names are uniform. |
| File operations. | When one or multiple files are obtained from the infobase using the GetFile() or GetFiles() method, the View right is checked for the attributes that store the file data. If the GetFiles() method is used and access to at least one the requested files is denied, the entire operation is canceled. This change is not implemented in 8.3.2 compatibility mode. |
When one or multiple files are obtained from the infobase using the GetFile() or GetFiles() method, the View right was not checked for the attributes that stored the file data. | The behavior of the GetFile() and GetFiles() methods is uniform with other system features. |
| Development tools. | Before database configuration update, the check whether the Ref attribute is present is performed for tabular sections of catalogs, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks. If this attribute exists, restructuring cannot be performed. This change is not implemented in 8.3.2 compatibility mode. | Before database configuration update, the check whether the Ref attribute is present was not performed for tabular sections of catalogs, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks. | Eliminated this type of errors in applied solutions. |
| Server clusters. | In the server cluster administration utility (rac), the name and cluster-port options of the server update command are removed. In the Java-based administration server interface, the setName() and setClusterMainPort() methods are removed from the IWorkingServerInfo interface. In the server cluster administration utility (rac), the security-level option of the infobase update command is removed. In the Java-based administration server interface, the setSecurityLevel() method is removed from the IInfoBaseInfo interface. | In the server cluster administration utility (rac), the name and cluster-port options were available for the server update command. The values specified in these options were never used and no error messages were displayed when the command was run with these options. In the Java-based administration server interface, the IWorkingServerInfo interface included the setName() and setClusterMainPort() methods. These methods did not perform any actions and there were no error messages when these methods were called. In the server cluster administration utility (rac), the security-level option was available for the infobase update command. The value specified in this option was never used and no error messages were displayed when the command was run with this option. In the Java-based administration server interface, the IInfoBaseInfo interface included the setSecurityLevel() method. This method did not perform any actions and there were no error messages when this method was called.
| Options of the administration utility (rac) and the set of Java-based administration server interface methods match the set of actions that the system can actually perform. Working server parameters can be specified during the registration of the working server in the cluster. The infobase security level can be specified while adding the infobase to the cluster. |
| Administration tools. Server clusters. | The server cluster administration utility (rac) from the previous platform versions (8.3.1 and 8.3.2) cannot be connected to the administration server (ras) of the current platform version. The server cluster administration utility (rac) from the current platform version cannot be connected to the administration server (ras) of the previous platform versions (8.3.1 and 8.3.2). | The server cluster administration utility (rac) could be connected to the administration server (ras) of any platform version. | The server cluster administration utility (rac) and the administration server (ras) that have incompatible versions cannot interact with each other. |
| File operations. Linux. | You can get a file mask that describes all files for the operating system where 1C:Enterprise runs. The following methods are implemented: GetAllFilesMask(), GetClientAllFilesMask(), and GetServerAllFilesMask(). | This feature was not provided. | You can write a source code that processes files and does not depend on the operating system where 1C:Enterprise runs. |
| File operations. Linux. | You can get a file path separator for the operating system where 1C:Enterprise runs. The following methods are implemented: GetPathSeparator(), GetClientPathSeparator(), and GetServerPathSeparator(). | This feature was not provided. | You can write a source code that processes files and does not depend on the operating system where 1C:Enterprise runs. |
| ZIP archive operations. | The behavior of the ZipFileWriter object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in a source directory:
The behavior of the ZipFileReader object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in the directory containing the archive file, the archive is opened in the read-only mode. This change is not implemented in 8.3.2 compatibility mode. | During the creation of an archive using the ZipFileWriter object, if the user under whose account the system was running did not have rights for viewing the list of files in the source directory, the files were not added to the archive and the resulting archive did not contain expected data. The archive could not be opened using the ZipFileReader object if the user under whose account the system was running did not have rights for viewing the contents of the directory containing the archive file. | The behavior of ZipFileWriter and ZipFileReader objects became more logical. Decreased chance of creating archive files with incorrect data. |
| Configuration repositories. | The compatibility mode with 1C:Enterprise versions 8.3.2 and earlier is implemented for the configuration repository. If the compatibility mode is disabled:
If the compatibility mode is disabled, only 1C:Enterprise version 8.3.3 or later can be used to access the repository. The command line option ConfigurationRepositoryClearCache is implemented in Designer. It is intended for clearing the local configuration cache. The option to stop the execution of repository operations by pressing Ctrl+Break is implemented (this does not depend on repository compatibility mode). | A different configuration repository database structure was used. Some repository operations were performed inefficiently. The Designer command line option ConfigurationRepositoryClearCache was not available. Pressing Ctrl+Break did not stop the execution of repository operations. | Improved performance when accessing a configuration repository server. |
| Applied objects. | The Filter property of the parameter structure that is passed to the formal parameter of the GetChoiceData() method or the ChoiceDataGetProcessing handler can contain elements with values of ValueList and Array types. The system applies the In list comparison type to such values (it is the same comparison type that is used with FixedArray values). | The Filter property of the parameter structure that is passed to the formal parameter of the GetChoiceData() method or the ChoiceDataGetProcessing handler could not contain elements with values of ValueList and Array types. | Extended filtering options when retrieving selection data. Removed unnecessary data conversions. |
| Background and scheduled jobs. | Background and scheduled jobs can now run in the file mode without using the ProcessJobs() global context method. The ProcessJobs() method does not perform any actions. Background and scheduled jobs are executed in one of the client applications connected to the infobase. The behavior of background and scheduled jobs has some specifics (see the full list in the documentation):
For specifying the client application that will execute scheduled jobs, the AllowExecuteScheduledJobs command-line option is implemented for the client application. The Background jobs check box, which is located in the Autoattach dialog box in Designer, affects the attachment to background jobs both at server and at client. This change is not implemented in 8.3.2 compatibility mode. | The only way to run background and scheduled jobs in the file mode involved using the ProcessJobs() global context method. The Background jobs check box, which is located in the Autoattach dialog box in Designer, only affected attachment to background jobs at server. | Reduced developer efforts during implementation of background and scheduled job execution in the file mode. |
| Applied objects. Common attributes / Data separation. | In order to successfully read or write separated constants using the Constants method of the global context, values of all shared separators that split the constant must be specified. Otherwise an exception is generated. This change is not implemented in 8.3.2 compatibility mode. | Reading or writing separated constants using the Constants method of the global context was performed successfully even when values of all combined separators that split the constant were not specified. | The feature is uniform with other similar platform features. |
| Linux. | The config_system configuration utility for Linux is removed from the distribution kit.
The search for MS Core Fonts required by the platform is performed automatically in the following directories:
The system automatically searches for required dynamic libraries when functions from these libraries are used. If the required font or dynamic library is not found, an error message is displayed. The operating system setup instructions for Linux are provided in the documentation. | The config_system configuration utility for Linux was included in the distribution kit. If required fonts or dynamic libraries were missing, this was not detected directly and could lead to various errors or unexpected behavior. The operating system setup instructions for running 1C:Enterprise on Linux were not provided in the documentation. | Simplified operating system for running 1C:Enterprise on Linux. Improved issue diagnostics. |
| Access rights. Queries. Accumulation registers. Accounting registers. | Access rights for autogenerated period fields (YearPeriod, HalfYearPeriod, QuarterPeriod, MonthPeriod, TenDaysPeriod, DayPeriod, HourPeriod, and SecondPeriod) in virtual tables of accumulation and accounting registers are obtained from the corresponding access rights of the standard Period attribute. This change is not implemented in 8.3.2 compatibility mode. | Access rights for autogenerated period fields in virtual tables of accumulation and accounting registers depended on the state of the Set rights for attributes and tabular sections by default check box. If the property was set to True, the user was granted the right. | Access right management is more consistent. |
| Development methodology. | The documentation includes a section with recommendations for developing cross-platform applied solutions. | The documentation did not include recommendations for developing cross-platform applied solutions. | Recommendations for creating the cross-platform applied solutions at minimal costs are available. |
| Managed locks. | Managed transaction locks can be set by object attributes. For specifying attributes whose values are taken into account when setting transaction locks, the DataLockFields property is implemented for the following configuration objects:
While objects are being written or deleted, they will be temporarily locked by all attributes specified in the DataLockFields property and the Ref field. For objects being written, attribute values available at the beginning of the writing process are used. For objects being deleted, current attribute values are used. This change is not implemented in 8.3.2 compatibility mode. | Managed locks for the following objects could be set only by the standard attribute Ref: catalog, document, chart of characteristic types, charts of calculation types, business process, task, chart of accounts, and exchange plan. | Extended managed lock functionality. When you need to perform a coordinated action on a set of objects filtered by a specific attribute and at the same time prohibit the creation of new objects that match the filter, you have the option to set a lock by the attribute, rather than lock the entire set of objects of the given type. |
| Managed locks. | Using the DataLock object outside of a transaction or in the automatic data lock control mode raises an exception. This change is not implemented in 8.3.2 compatibility mode. | Using the DataLock object outside of a transaction or in the automatic data lock control mode did not raise an exception and did not lead to any locks. | Situations when the system seemed to work properly but actually did not perform any actions are eliminated. |
| Client application installation. Administration tools. | You can specify whether the latest 1C:Enterprise updates are installed automatically. This is configured using the following new parameters:
When the client application version does not match the 1C:Enterprise server version, or when a specific 1C:Enterprise version is required to access an infobase, the new version is always installed unless the required version is already present at the client computer. The Install new application versions automatically check box is added to the infobase startup settings dialog box. | The non-interactive startup utility installed the latest 1C:Enterprise version, except the following scenarios:
| In the non-interactive startup utility, you have the option to disable the search and installation of the latest 1C:Enterprise version in the event when the required version is already installed at the client computer, but later versions are available and not yet installed. You still have the option to install any 1C:Enterprise version that you need. |
| Development tools. | During the database configuration update, the check for matches between the names of common pictures and the names of pictures from the picture library is performed. If matches are found, the message informing that the names are not unique is displayed and the database configuration is not updated. This change is not implemented in 8.3.2 compatibility mode. | During the configuration update, the check for matches between the names of common pictures and the names of pictures from the picture library was not performed. | The following scenario is no longer possible: when a common picture name matches a picture name from the picture library, in 1C:Enterprise mode the picture from the library is displayed instead of the common picture. |
| Managed forms. | The Close() method called on an additional form closes this form. If this form is active, the default form is made active, otherwise no additional actions are performed. The IsOpen() method called on an additional form that is open returns True. If the user switched to another additional or default form after opening the additional form, the IsOpen() method still returns True. | If the Close() method was called on an additional form, an error was generated and the form was not closed. The IsOpen() method called on an additional form that was open returned False. | The system behaves as expected. |
| XML and XDTO support. | During the generation of the configuration data model, for all properties of the configuration data model that have more than one type in their type descriptions, the Can be empty property (the nillable attribute of the XSD schema) is set to True, otherwise the property value is not set. If you specify the Any ref type for an attribute (such as a resource or dimension) in Designer, the type is converted into one of the following in the configuration data model:
This change is not implemented in 8.3.2 compatibility mode. | During the generation of the configuration data model, for all properties of the configuration data model that have more than one type in their type descriptions, the value of the Can be empty property (the nillable attribute of the XSD schema) was never set. If you specified the Any ref type for an attribute (such as a resource or dimension) in Designer, it was always converted to the {http://v8.1c.ru/8.1/data/enterprise}AnyRef type in the configuration data model. | The XML data model generation for the Any ref type is uniform with other types. |
| Full-text search. | Full-text search indexes include the number of 1C:Enterprise version that was used to create them. If the full-text search index is created in version 8.3.3 or later while the compatibility mode is disabled, and then the infobase is accessed using version 8.3.2 or earlier, the search by presentations of configuration objects is not performed. | Full-text search indexes did not include the number of 1C:Enterprise version that was used to create them. | Reverse compatibility of full-text search indexes is implemented. The full-text search indexes are now compatible with earlier 1C:Enterprise versions that have different index format. |
| Web services. Web links. | You can specify proxy server parameters in constructors of the WSProxy and WSDefinitions objects and in the CreateWSProxy() method. The former constructor and method syntax is supported for compatibility purposes. | Proxy server parameters could not be specified when WSProxy or WSDefinitions objects were created or when the CreateWSProxy() method was called. The proxy server settings could be specified only by editing the inetcfg.xml configuration file. | Extended web service support functionality: the proxy server settings can be specified in the configuration settings rather than by editing the configuration file. |
| Functional options. | If the privileged get mode is set for a functional option, getting the functional option value in the safe mode does not require checking the access rights. This change is not implemented in 8.3.2 compatibility mode. | If the privileged get mode was set for a functional option, getting the functional option value in the safe mode included checking the access rights. | Eliminated the issues related to accessing functional options in the safe mode. The data provided by a functional option that has privileged get mode set is considered safe enough and can be retrieved in the safe mode. |
| Automated testing. | If an object being tested cannot perform the required action, an exception is raised (except methods that search for objects, which never raise this kind of exception). | It was impossible to detect situations when objects being tested could not perform the required actions. | Better error detection during automated testing. |
| Automated testing. | Methods that perform actions on objects being tested do not wait for action completion. Methods that previously returned the execution results now raise exceptions when the actions cannot be performed. | Methods that performed actions on objects being tested waited for action completion. In some cases such methods returned result codes. | Better error detection during automated testing. |
| Managed forms. | For managed form fields, the DropListButton property is implemented. It describes whether the button that opens the drop-down list is present. Depending on the type of the attribute linked to the text box, the list can contain the following data:
During the text input in a text box, the platform displays unique items from all these lists (if they are available for the text box). For managed form fields, the ChoiceButtonRepresentation property is implemented. It describes whether the button that opens the choice form is present in the field. The DropListButton property of managed form fields is no longer available; it is left for compatibility purposes. The StartListChoice event of text box objects is never called. This change is not implemented in 8.3.2 compatibility mode. | The DropListButton property was available for managed form fields. When a user started selecting an item from the list, the the StartListChoice event was generated. Developers could not control whether the choice form could be opened from the choice list. | The choice list is designed to allow users to select values quickly, without opening the choice form, whenever possible. For that, the choice list contains data that helps users to select a value for a text box:
|
| Web client. | In the web client for iPad, only the Forms in tabs mode without modal windows and the Taxi interface are supported. The webclientmode command-line parameter is no longer supported. Standard gestures for zooming in and out are now supported. Form items with content that can be scrolled have scroll bars. | In the web client for iPad, modal windows were supported with some limitations, and the Forms in tabs mode was not supported. The webclientmode command-line parameter was supported. Standard gestures for zooming in and out were not supported. Form items never had scroll bars. | Configuration tuning is no longer required to run applications on iPad (provided that you switch to the mode that does not use modal windows). In earlier versions of the platform, the developer had to remove a part of functionality to make an application compatible with iPad because modal calls were supported with limitations. |
| Managed forms. Command interface. | Enhanced window blocking technology introduces innovative approach to window modality. Blocking windows are used instead of modal windows, while modal windows are supported for compatibility purposes. It is recommended that you replace all modal windows with blocking windows in your applied solutions, and use new platform methods that do not create modal windows. A call of a modal form is broken down into one or more separate calls: the first call opens a blocking form instead of a modal one and the the other one contains a callback procedure that is called by the platform when a form operation is complete (it includes getting the return value). Applied solutions designed for iPad must support the blocking windows technology. The ModalityUseMode configuration property is implemented, it defines the modal window usage mode. In the extended configuration check, the search for methods related to modal windows is implemented. You can also perform this check from the command line by using the CheckUseModality option of the ExtendedModulesCheck command-line parameter. The NotifyDescription object is implemented, it passes the callback procedure description to platform methods that open blocking windows. The global context method ExecuteNotifyProcessing() is implemented. For the FormWindowOpeningMode system enumeration, the LockWholeInterface value is implemented. For managed forms, command interface commands, and common modules, the ThisObject property is implemented. This property is not supported in version 8.3.2 compatibility mode. The global context method OpenForm() is modified. The following global context methods are implemented: ShowQueryBox(), ShowValue(), ShowMessageBox(), ShowInputDate(), ShowInputValue(), ShowInputString(), ShowInputNumber(), BeginInstallAddIn(), BeginInstallFileSystemExtension(), BeginInstallCryptoExtension(), and BeginPutFile(). For objects StandardPeriodEditDialog, FormatStringWizard, FontChooseDialog, ColorChooseDialog, and ScheduledJobDialog the Show() method is implemented. For the DataCompositionDetailsProcess object, the ShowChooseAction() method is implemented. For the ValueList object, the methods ShowCheckItems() and ShowChooseItem() are implemented. For the ManagedForm object, the Open() method is modified, and the methods ShowChooseFromMenu() and ShowChooseFromList() are implemented. For the ManagedForm object, the OnCloseNotifyDescription property is implemented. The ThisForm property of the ManagedForm object is removed but supported for compatibility purposes. The system enumeration value PostingModeUse.Ask is supported for managed forms only in version 8.3.2 compatibility mode. | In the web client on iPad, the modal window support was limited, while modal windows were widely used in applied solutions and in the system part of the interfaces. | The web client meets the modern web technology standards. Removed limitations on modal window usage in the web client on iPad. Configuration modification is required for applied solutions intended to run in the web client on iPad. |
| Technological log. | The resolution of the event time output to the technological log is increased to 1 microsecond. The count of microseconds in technological log event time has six digits. The DurationUs property is implemented. It contains the event duration measured in microseconds. For compatibility purposes, filtering by Duration properties is supported. | The resolution of the event time output to the technological log was equal to 100 microseconds. The count of microseconds in the technological log had four digits. Only the Duration property was available in the technological log. It contained the event duration measured in hundreds of microseconds. | Decreased chance of the time counter overflow that occurred when the count of technological log events exceeded 10 000 events per second. One second can now contain up to 1 000 000 events of the technological log. It is recommended that you use the DurationUs property instead of the Duration property. |
| Web client. System requirements. | The following browsers are no longer supported:
| The following browsers were supported:
| Improved web client stability because rarely used browsers with errors and non-standard behavior are no longer supported. |
| Linux. | The platform supports XBase objects on 64-bit Linux operating systems | The platform did not support XBase objects on 64-bit Linux operating systems | Operations with .dbf files are now available on all supported architectures, except the mobile platform. |
| Dynamic lists. | The DataVersion field is removed from the list of available fields of dynamic list settings. | The DataVersion field was included in the list of available fields of dynamic list settings. | The field that was erroneously added to the list of available fields of dynamic list settings is now removed from the list. |
| Access rights. | Managed forms only display data retrieved using "." (dot) if the user has access rights for all parts of the full path to the data. If they do not have the rights, the item linked to this data is not displayed on the form. | If a user did not have access rights for all parts of the full path to data retrieved using "." (dot), the item linked to the data was displayed in the form, but it did not contain any data. | When accessing data using "." (dot), the form item linked to the data is not displayed on the form if the user does not have access rights for all parts of the full path to the data. |
| Administration tools. | In the Java API for server administration, the value of the RuleType property of the AssignmentRuleInfo object matches the value of the RuleType property of the IAssignmentRule object in the server cluster administration tools that use COM connection. | The values of the RuleType properties differed in the Java API for server administration and in the server administration tools that used COM connection. | The server cluster administration tools are unified. |
| Internet-enabled functionality. | The OpenID pass-through authentication protocol implementation is revised. The implementation complies with the Direct Identity version 2.0 mode of the OpenID protocol. The format of the OpenID provider address in the default.vrd file is modified (the url attribute of the rely item): httрs://<address of the OpenID provider infobase>/e1cib/oid2op. The default authentication lifetime is 24 hours. The maximum authentication lifetime is 168 hours. The protocol for interaction between the relying party and the OpenID provider is modified. In the authentication dialog box, you can disable storing authentication data. For the web client, a dialog box for entering the user name and password at the OpenID provider side is implemented. | The protocol implementation did not fully comply with the Direct Identity version 2.0 mode of the OpenID authentication protocol. The OpenID provider address in the default.vrd file was as follows: httрs://<address of the OpenID provider infobase>/e1cib/oida. The default authentication lifetime was 1 week. The maximum authentication lifetime was not limited. In the web client, there was no dialog box for entering the user name and password at the OpenID provider side. | The OpenID pass-through authentication protocol complies with the specification. |
| Add-ins. Web client. | The add-in technology now supports Mozilla Firefox browser version 22.0 and later. You can use add-in adapters for Mozilla Firefox 22.0 in the later versions of the web browser without recompiling the adapters. For add-ins intended for use with all supported Mozilla Firefox versions, you have to add several add-in versions to the archive:
It is recommended that you specify only the minimum version of the web browser in the add-in manifest file. Documentation on creating add-ins is updated (read more). Examples are added, new versions of adapters for web browsers. Adapters for Mozilla Firefox versions that are no longer supported by the developer (versions 3.6, 4.0, and 5.0) are removed. | The add-in technology did not support Mozilla Firefox browser version 22.0 or later. | The add-in technology now supports new versions of Mozilla Firefox browser (version 22.0 or later). |
| Managed forms. Full-text search. | When a choice list is generated for the "input by string" feature (for reference configuration objects), the following options are available:
You can specify each of these options in Designer, in the configuration object properties. The full-text search is performed only among the configuration object attributes that are selected in the "input by string" options of the configuration object. If a filter is applied during the input by string, the filter is converted (whenever possible) to a full-text search query in order to increase the search performance. For external data source tables, you can only select the search modes (by substring or by beginning of the string, and instant or background). In the file mode, the background search can be performed only when any other background or scheduled job is not being executed. For the AutoComplete and TextEditEnd event handlers, the formal option Parameters is implemented. It contains settings for getting choice data and allows you to manage this process by changing the properties of the structure that is passed in this parameter. | The following options were not available in the "input by string" feature:
The full-text search and search by substring were available in ChoiceDataGetProcessing handlers. | New standard options for the "input by string" feature in text boxes:
|
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| System requirements. | For iOs-based devices, the iOS version 4.x is not supported. The minimum iOS version is 5.1. For Android-based devices, the minimum RAM size is 256 MB. | iOS version 4.x was supported. Android-based devices required 100 MB of RAM to run 1C:Enterprise. | System requirements for the mobile platform are revised. |
| Managed forms. | In the mobile application, the extended tooltop can be used, except the Balloon option. | Extended tooltips were not available in mobile applications. | On the mobile platform, you can create tooltips for form elements using a variety of tooltip design options. |
| Common objects. | Geolocation functions and multimedia tools (photos, audio- and videorecording) provided by mobile devices are available in mobile applications. The following geolocation functions are implemented: GeographicCoordinates, LocationData, LocationProviderInformation, LocationTools, AddressData. The LocationTools global context property is implemented. Global context methods GetAddressByLocation(), GetLocationByAddress(), and ShowOnMap() are implemented. The GeographicalSchemaCoordinates type is renamed to GeographicCoordinatesp; it is used in geolocation functions. The GeographicalSchemaCoordinates type name is supported for compatibility purposes. The MultimediaData and MultimediaTools objects are implemented to support processing multimedia features. The MultimediaTools global context property is implemented. | These features were not provided. | Geolocation and multimedia functions of mobile device perating systems are now available in the mobile platform. You can add features for defining the current location, making photos of incoming items, and so on. |
| Development tools. | The configuration check verifies whether the conifiguration language code meets the ISO standard. It is recommended that you use ISO-compliant language codes. | The language codes were not checked for compliance with ISO standard. | Reduced chance of incorrect mobile platform language selection based on the mobile device language. |
| 1C:Enterprise script. | Common modules that reuse returned values are now supported | This feature was not provided. | On the mobile platform, you can optimize getting the same data multiple times during a single session or a single server call. |
| Predefined data. | While a mobile application is being updated, metadata objects are compared by their internal identifiers. When a mobile application is updated to version 8.3.3, the corresponding restructuring is performed. | While a mobile application was being updated, metadata objects were compared by their names. | You can rename metadata objects while preserving the object data. |
| Data display. | The mobile platform picture format is replaced by the format that supports several screen resolutions of mobile devices. | All mobile platform pictures had the same resolution. | The sizes of system pictures displayed on mobile device screens depend on the screen resolutions. |
| Backups. | When an infobase is created on iOS-based devices, the directory containing the application data is marked as excluded from the backup. When the infobase data is modified (object form extension data and register data is recorded), the directory with application data is marked for backup and the backup is initiated using the system tools. | On iOS-based devices, the infobase directory was marked for backup since it was created. | The application behavior meets the requirements of the Apple company to user data backup. |
| Spreadsheet documents. | On the mobile platform, resolved issues with displaying spreadsheet documents that have a large number of rows and columns. | In some cases displaying a spreadsheet document with a large number of rows and columns on the mobile platform led to an unexpected shutdown. | Improved mobile platform stability when processing large spreadsheet documents. |
| Internet-enabled functionality. | For the mobile platform, the HTML-document field is implemented. The HTML-document field has the following specifics:
| The HTML-document field was not supported on the mobile platform. | In mobile applications, displaying HTML pages in forms is implemented. For example, you can create a manual for your configuration. |
| Interface. | On mobile devices with Android OS, you can change the order of items in the list of applications. | On mobile devices with Android OS, changing the order of items in the list of applications was not available. | Improved usability of the list of applications. User can arrange applications in any order. |
| Data composition system. | Processing data composition system details on the mobile platform is implemented (this includes opening values and remote processing of the details). For mobile platform, the DataCompositionDetailsID object is implemented. | On the mobile platform, reports that contained data composition system details could not be opened. | On the mobile platform, reports can be generated using the data composition system. Report that contains details can be opened on the mobile platform. |
| Mobile application development. | In the Mobile application creation wizard data processor, you can specify a key for Google Maps. You can also specify a logo for screen resolution 950×1136 (iPhone 5 screen) in this data processor. | These features were not provided. | You can use the Mobile application creation wizard data processor for creating mobile applications that utilize new mobile platform features (geocoding support). Support of iOS-based devices was improved as well. |
| Internet-enabled functionality. | For the objects HTTPConnection, WSProxy, WSDefinitions, and InternetMailProfile, and for the CreateWSProxy() method, the option to set a timeout for interaction with a network resource is implemented.
User names and passwords that are passed to WSProxy, WSDefinitions, and HTTPConnection
objects can contain special characters, except ":".
You can encode (the EncodeString() method) and decode (the DecodeString() method) custom text strings for using them in URLs. Encoding is performed in compliance with the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt).
You can process HTTP request headers and return codes, as well as get and set request bodies as strings or binary data. The HTTPRequest and HTTPResponse objects are implemented. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | On the mobile plaform, the following features are available:
|
| 1C:Enterprise script. | The CurrentUniversalDateInMilliseconds() function is implemented. It gets the number of milliseconds that passed since January 1, year 0001, 0:00:00 UTC. The attempt to assign a value to a fixed structure item raises an exception. In value tables, serialization of index descriptions is implemented. The index contents are not serialized but restored during deserialization. The hash function value can be calculated based on MD5 and CRC32 algorithms using the DataHashing object. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | On the mobile platform, you can do the following:
|
| Managed forms. | When specifying values of managed form fields or tables, you can specify data stored in a specific row of a form attribute that is a table (but not a dynamic list). Data belonging to dynamic lists that are currently not displayed on a managed form is not read during the operations that involve the managed form. For attributes of String type that have fixed length and are located in managed form tables, table boxes, or spreadsheet documents, the appearance of the mark that indicates that the field must be filled is modified. The following style fonts are implemented: SmallTextFont, LargeTextFont, and ExtraLargeTextFont. For the Font type, the Scale property is implemented. It defines increase or decrease of the font relative to the initial size. For groups of "usual group" or "page" type, you can set the background color of form group extensions using the BackColor property. The URLProcessing handler is implemented for the Label form field, Decoration form field of Label type, and managed form. The handler is called when a user clicks a formatted string with a hyperlink in a field. Extended appearance customization options for form fields of label type and decorations of label type. In usual groups with limited width, the size of managed form buttons can vary depending on the width, which is similar to the behavior of other form items in a group with limited width. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | On the mobile platform, you can do the following:
When the size of a usual group is limited, the algorithm used for resizing group items is the same for all item types. |
| Applied objects. | User presentations are implemented for database objects of the following types: Catalog, Document, and ExchangePlan. In document journals, the attribute containing the document number has fixed length if all documents included in the journal have the number field of String type with fixed length. Otherwise, the journal attribute has variable length. A value obtained from an unfilled table attribute, value tree, or tabular section is equal to the default value of the column attribute type, with the type qualifier taken into account. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | On the mobile platform, you can do the following:
|
| Command interface. | In the information register record form, if the OnlyInActions property of the Copy command has the Auto value, the system behavior is changed. This value now means that the command is located in the More (or All actions) menu only. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | On the mobile platform, you can specify the same default location for the Copy command in information register records set forms and in the item forms. |
| Charts. | New types of charts are implemented:
The antialiasing mode is implemented for charts. You can connect series of charts to each other. The semitransparency mode is implemented for charts. The Indicator property is implemented for the tape graph chart. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | Extended chart features on the mobile platform. |
| Information registers. | For periodic information registers, the totals for getting first and last slices are implemented. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | On the mobile platform, you can get first and last slices, which represent data as of the last (current) moment in time, much faster. |
| Spreadsheet documents. | If a fixed area is larger than the displayed area, the spreadsheet document does not use the fixation. The algorithm for horisontal cell placement in different rows is modified. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | On the mobile platform you can:
|
| XML and XDTO support. | If a message to a user contains characters incompatible with XML format (in the thick or thin client), the error XML text contains invalid characters in X position is generated. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | The processing of characters that are incompatible with XML format on the mobile platform is uniform with processing them on the PC-based platform. |
| Data display. | Formatted strings are available (the FormattedString type). You can use a formatted string as:
| This feature was not provided on the mobile platform. | On the mobile platform, the text presentation capabilities are improved. |
| XML and XDTO support. | During the import of XSD schema, if the target namespace definition is missing in the schema, a diagnostic message is displayed. | During the import of XSD schema, when any problems occurred while loading the XSD schema, a diagnostic message was not displayed. | Improved diagnostics during XSD schema import. |
| Managed forms. Command interface. Common objects. | You can specify the Arbitrary type for a subordinate attribute of a managed form attribute (for example, a value table column or a value tree column).
For managed forms, the URL and AutoURL properties are implemented. You can use the URL property to get a link to the main form of the object.
For the GetForm(), OpenForm(), and OpenFormModal() methods, the URL parameter is implemented. Its value is assigned to the URL property of a form when the form is obtained or opened.
Navigation links to lists are implemented. For a form whose main attribute is a dynamic list with a main table specified, the navigation link points to the list of the object specified as the main table. Following the link opens the main form of the list.
You can use navigation links to global command interface commands.
The format of navigation links to navigation points generated by standard commands is modified.
Changes made to a table of totals storage settings for accumulation registers are applied within a transaction.
Values of the ReadOnly and Protection properties are preserved when a spreadsheet document is passed between the client and the server.
For the NumberInWords() global context method, the AU formatting option is implemented. The TextReader and TextWriter objects are implemented. This functionality is similar to the PC-based platform functionality. | This feature was not provided on the mobile platform. | Some mobile platform features are now uniform with PC-based platform. |
| Mobile application. | The mobile platform supports all of the interface languages that are supported in the PC-based platform. The mobile platform delivery that supports only English and Russian interface languages is also available. The content of the mobile platform distribution kit is modified. | The mobile platform supported English and Russian interface languages only. | The system part of the mobile platform interface supports more languages than before. |
| Development tools. | If the Use purposes configuration property is set to Mobile device only, other configuration settings are changed automatically:
| If the Use purposes configuration property was set to Mobile device only, other configuration properties were not changed automatically. | For configurations being developed for mobile platform only, eliminated the chance to save configuration property values that are incompatible with mobile platform limitations. |
In order to use certain optimization improvements, you have to restructure data related to the optimization areas. To restructure data, you can use the Verify and repair mode, or perform forced restructuring of the required objects.
To perform the conversion of the cluster register from version 8.2 to version 8.3 once more, stop the server cluster 8.3, delete the server cluster 8.3 register (the 1CV8Clst.lst file), and then start the server cluster 8.3.3.
Version 8.3.2 includes known bug fixes and functionality modifications.
| 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. |
| Development 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. |
| 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. |
| 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. |
| Development 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. |
| 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. DBMS operations. System requirements. Configuration repositories. | 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. |
| Data display. | 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 documents. | 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 clusters. | 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. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Data display. | 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 documents. | 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. |
Version 8.3.1 does not include changes introduced in version 8.2.17.
Version 8.3.1 includes known bug fixes and functionality modifications.
Improved the list of new and updated features:
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.2.16 is added to the list of available values of the Compatibility mode property. | Compatibility modes were available for the following platform versions: 8.1 and 8.2.13. | 1C:Enterprise provides compatibility of configurations developed using version 8.3.1 or later with previous platform versions. |
| Designer. Cross-platform architecture. | The client application for Linux operating system is available. It includes thin client, thick client, and Designer. It supports file and client/server operation modes. Thin client can connect to infobases using a web browser. Limitations of the client application for Linux are listed in the documentation. Installation of multiple 1C:Enterprise versions is not supported. Shortcuts for noninteractive startup application, thin client, and thick client are added to the application menu of Linux desktop environment. They are located in the Finance subsection of the Office section. | Only the 1C:Enterprise server and the web client were available for Linux operating system. | You can develop applied solutions and run client applications on Linux operating system. |
| Thin client access over the Internet. | The thin client is now HTTPS-enabled, thanks to client certificate support. The following client certificate storage options are supported: file, Windows certificate store, and NSS certificate store. The following command line options for specifying certificate parameters are implemented: HttpsCert, HttpsCA and HttpsNSS. Client applications for Linux operating system do not support Windows certificate store, and HttpsCert, and HttpsCA command line options. | The thin client was not HTTP-enabled, and client certificates were not supported. | The thin client is HTTP-enabled, and client certificates are supported. |
| Web links. | Web services can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store). | Web services could not operate using HTTPS with client certificates. | Web services are operational in cases when the server side requires a client certificate to use HTTPS. |
| Internet-enabled functionality. | HTTP and FTP connections can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store). | HTTP and FTP connections could not operate using HTTPS with client certificates. | HTTP and FTP connections are operational in cases when the server side requires a client certificate to use HTTPS. |
| 1C:Enterprise script. | You can calculate the value of hash function by MD5 and CRC32 algorithms using the DataHashing object. | Calculating the hash function required the use of third-party (add-ins, etc.) tools. | You can quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools. |
| External data sources. Common attributes / Data separation. | A common attribute can include an external data source. Connection parameters for such external data sources are stored by separator values. If a separator is not used in a session, the separator is treated as an independent value for storing connection parameters. Data located in tables of external data sources is not separated by separator values. | Common attributes could not include external data sources. | You can specify connection parameters for each data area in the infobase. This provides you with the option to access either different infobases with the same structure, or a single infobase with different connection parameters. |
| Managed forms. | You can specify data located in a specific row of a form attribute that has table structure (except dynamic lists) as a value of a managed form field or table. | This feature was not provided. | You can implement such interface features as displaying report settings in separate form fields. |
| External data sources. | Operating system authentication is available when working with external data sources. The SessionOSAuthenticationChange access right is implemented. It allows or denies changing the operating system authentication setting both in user settings and in current session parameters. | This feature was not provided. | You can establish connection to external data sources if the only authentication method available is operating system authentication. |
| Applied objects. Data display. | User presentations for data base objects of the following types: Catalog, Document, ChartOfAccounts, ChartOfCalculationTypes, ChartOfCharacteristicTypes, BusinessProcess, Task, ExchangePlan, Table. Implemented the PresentationFieldsGetProcessing and PresentationGetProcessing event handlers for object manager modules of these types. This change is not implemented in version 8.2.16 compatibility mode. | Modification of database objects using script tools was not allowed. | Custom presentations for database objects. The option to obtain presentations for external data source tables when the field that provides the presentation is not specified. The option to obtain presentations of objects that include localized data. |
| External data sources. 1C:Enterprise script. | You can search for references to objects of external data source tables using the FindByRef() global context method or Find references to object standard function. The search is performed both in infobase tables and in external data source tables. | Searching for references to objects of external data sources tables using the FindByRef() global context method or Find references to object standard function was not available. | You can search for references to objects of external data source tables. |
| External data sources. | The AllRefsType() method is implemented for the ExternalDataSourceTablesManager object. | This feature was not provided. | Implementation of missing features for working with external data sources. |
| External data sources. | The OpenValue() global context method allows opening the following value types: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey. | The OpenValue() global context method did not allow opening the following value type: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey. | Implementation of missing features for working with information registers and external data sources. |
| Database configuration updates. Server clusters. | Background database configuration update is implemented. The update is supported in client/server mode only. It is available when the data structure is modified. The update does not require long-lasting exclusive access to the infobase. The exclusive access is required at the final stage of the background update for a short period of time. The database configuration update service is implemented for a server cluster. A system background job that performs the background database configuration update is implemented. The GetDataBaseConfigurationUpdate() global context method and the DataBaseConfigurationUpdate object are implemented. For the /UpdateDBCfg Designer batch mode command line option, the following parameters are implemented: -Dynamic, -BackgroundStart, -BackgroundCancel, -BackgroundFinish, -BackgroundSuspend,and -BackgroundResume. The following events are implemented in the event log: _$InfoBase$_.DBConfigBackgroundUpdateStart, _$InfoBase$_.DBConfigBackgroundUpdateFinish, _$InfoBase$_.DBConfigBackgroundUpdateCancel, _$InfoBase$_.DBConfigBackgroundUpdateSuspend, and _$InfoBase$_.DBConfigBackgroundUpdateResume. | An update of database configuration with modified data structure was possible only in the exclusive mode. | The update of database configuration with significant changes in its data structure does not cause long application downtime for end users. You have the option to perform dynamic infobase configuration update in Designer batch mode. The option is available for both background and regular updates. |
| 1C:Enterprise script. File operations. Web client. | The TempFilesDir() method is implemented for the web client. The method is available when the file system extension is installed. The UserDataWorkDir() method is implemented. It provides access to the user directory created by the system. The method is available for thin, thick, and web clients. In the web client the method is available when the file system extension is installed. The DocumentsDir() method is implemented. It provides access to the default document directory of the operating system. The method is available for thin, thick and web clients. In the web client the method is available when the file system extension is installed. | Standard catalogs (user data directory and document directory) were inaccessible for standard tools. In the thick and thin clients the access could be implemented using third-party tools, which reduced 1C:Enterprise portability between operating systems and client applications types. | Access to certain standard directories on the client computer, which allows storing user file data in designed locations without using third-party tools. |
| Data display. | Formatted strings are available (FormattedString type). You can use formatted strings as:
| Displaying text that included various formatting styles was only available for HTML documents and formatted documents. | Improved text presentation capabilities and usability. |
| 1C:Enterprise script. Managed forms. | The URLProcessing handler is implemented for the form field Label, form field Decoration of Label type, and managed form. The handler is called if the following conditions are met: there is a formatted string in any of the specified form fields, it contains a hyperlink, and the Hyperlink property of the form element is set to False. | Implementing presentation of an entire form element as a hyperlink was allowed, but including multiple hyperlinks in a single field was not allowed. | The option to handle each hyperlink contained in a formatted string separately. |
| Command interface. | You can use navigation links to commands of the global command interface. Using a link executes the command. Support of navigation links to commands is implemented for the GotoURLGotoURL() global context method. | This feature was not provided. | Using a link can execute a command, and this feature can be used in the script. |
| Managed forms. | The URL property is implemented for managed forms. It is used for obtaining a link to the default object form. The AutoURL property is implemented for the managed form. The GetURL() method of the ClientApplicationWindow objects returns a value of the URL property (if the AutoURL property is set to False) or the standard link to the default form.
| This feature was not provided. | You can specify the value of the navigation link obtained from the client application window. |
| 1C:Enterprise script. Common attributes / Data separation. Applied objects. | Document journals can be included in contents of common attributes, which are not used as separators. For compatibility purposes, in infobases created in 1C:Enterprise version 8.2, the value of the Use property of the the common attribute content element is set to Do not use for document journals. | Common attributes could not be displayed in document journals. | Common attributes can be displayed in document journals. |
| Data display. Managed forms. | Implemented the following style fonts: SmallTextFont, LargeTextFont, ExtraLargeTextFont. For the Font type the Scale property is implemented. It specifies increase or decrease of the font size relatively to the original size. | The only method of specifying font size in a managed form was setting absolute font size. | You can specify the size of the form font relatively to the base font of the form, without using absolute font size values. |
| Server clusters. 1C:Enterprise script. | The SafeCallMemoryLimit property is implemented for the IWorkingProcessInfo object. It specifies the amount of memory (in bytes) that the application can use during a single server call. The SafeWorkingProcessesMemoryLimit property for the IWorkingServerInfo object is implemented. It specifies maximum amount of memory (in bytes) available for all running processes on a given working server. | No tools for limiting memory usage were available. It might cause problems in some situations - for example, when users customized reports that selected large amounts of data. | Server stability improved. If a specific session consumes a large amount of memory, it does not cause emergency shutdown of the entire server cluster. Instead, the client application that causes the memory consumption is shut down. |
| Server clusters. 1C:Enterprise script. | While a working process is executing a script in the client/server infobase mode, the stack is monitored to prevent it from overflowing. | Infinite recursion might lead to emergency shutdown of the working process of the server cluster. | Stability of server cluster operation improved. |
| Server clusters. 1C:Enterprise script. | For the ISessionInfo and IInfoBaseConnectionInfo objects the following properties are implemented:
Similar properties are implemented in the cluster console for the list of sessions, list of connections, and connection properties dialog. | This feature was not provided. | Monitoring tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space. |
| Technological log. Server clusters. | Extended the list of properties for the <call> event of the technological log when the event is generated for the rphost process (the process property is set to rphost), and also when the rphost process performs a call to virtual system resources. The following properties are added:
| The listed properties were absent from the <call> event. | Technological log tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space. |
| Common attributes / Data separation. 1C:Enterprise script. | You can delete data from a specific data area or from the entire infobase. The following data can be deleted:
The Administration right is required for deletion. The deletion can be performed:
The _$InfoBase$_.EraseData event is implemented in the event log. | It was impossible to delete a specific data area. | You can delete a data area that is no longer needed (for example, data belonging to a subscriber that stopped using the system). |
| Server clusters. Software licensing. | The licensing service is implemented for the server cluster. The license search algorithm is modified. | The licensing service was not present. | You have the option to bind a software license to a specific computer, which is intended for running the licensing service only and will not be subject to hardware changes. |
| Development tools. | Dumping configurations to files and loading configurations from files is implemented. Most objects are dumped to .xml files. Modules are dumped to the text files. Pictures are dumped to files in their original format, help information is dumped to .html files. Vendor configurations are dumped to configuration files (.cf). Ordinary forms and interfaces are dumped to binary files. Dump configuration to files and Load configuration from files commands are added to the Configuration menu. Dump configuration files and Load configuration files commands are removed from the Configuration menu, but you can restore them using the main menu settings dialog. The DumpConfigToFiles and LoadConfigFromFiles command line options are implemented. | Limited set of data was dumped and loaded: modules, help information, templates, rights, and pictures. Other configuration data was not dumped. Dump configuration files and Load configuration files commands from the Configuration menu were used for dumping and loading data. | You can analyze and modify configurations using third-party tools. |
| Data display. Managed forms. | You can specify the background color for form group extensions of regular groups and pages using the BackColor property. If the background color of a group is different from Auto and the group is displayed as a Group box, the group box (including the title) is filled with the specified background color. | The option to specify background color for form groups was not provided. | The color highlighting of groups improves visibility of form elements and the overall usability of forms. |
| Common attributes / Data separation. | New global context methods for managing the safe mode of data separation are available in 1C:Enterprise script: SetDataSeparationSafeMode and DataSeparationSafeMode. They duplicate the functionality of the safe attribute in the zone tag of the default.vrd file. | Switching to the safe mode of data separation was only available by editing the file default.vrd and only if the web server connection to the infobase (the HTTP protocol) was used. | The new methods enable safe execution of code fragments called from sessions that do not use separator values (but are intended to run in specific data areas, without any way to change the area accidentally). |
| Event log. OpenID authentication. | In case of successful or unsuccessful OpenID authentication the Session.Authentication or Session. Authentication error events are generated in the event log. | OpenID authentication events were not written to the event log. | You can obtain information about OpenID authentication events from the event log. |
| Event log. OpenID authentication. | For infobases that are OpenID providers the OpenIDProvider.PositiveAssertion event is implemented. It is generated in case of a positive response to the authentication request. If the response to the authentication request is negative, the OpenIDProvider.NegativeAssertion event is generated in the event log of the infobase. | This feature was not provided. | Improved tools for administration of OpenID providers. |
| Development tools. | You can view the values of the form element properties Font, TitleFont, FooterFont and ChoiceList in a separate window when editing of these properties is disabled. | These properties could not be viewed if the object was not locked in the repository or was supported. | If an item is not locked in the configuration repository or is supported, you can view its font style and choice list without disabling support and without locking the object in the repository. |
| Server clusters. | When logon to or logout from an infobase that requires a client license is performed, the platform can notify an external application using web service methods. In response to logon notification, the external application can allow or deny the start of the session. This option is only available in client/server infobase mode. For specifying web service parameters, the following properties are implemented:
If a web service for external session management is unavailable, the system behavior is determined using the following properties:
The external session manager service is implemented on the server. Parameters of invoked web services are listed in the documentation. | The only option to limit the number of simultaneous sessions was appropriate modification of the applied solution. A platform mechanism for performing this task was not available. | A platform mechanism for monitoring the number of simultaneously used licenses for various applied solutions, which does not require modification of these applied solutions. |
| Web client. Add-ins. | You can use add-ins in Google Chrome and Safari web browsers (for operating systems of Windows family and Mac OS X). The Mac OS value is implemented for the PlatformType system enumeration. A file system extension is available for these browsers on operating systems of Windows family and Mac OS X. A cryptographic extension is available for these browsers on operating systems of Windows family only. | Add-ins, file system extension, and cryptographic extension were not supported for Google Chrome and Safari web browsers. | A file system extension and cryptographic extension (for operating systems of Windows family only) are available for Google Chrome and Safari web browsers. Add-ins can be created for all supported web browsers. |
| Pictures. | Processing pictures from the script with help of the new PictureProcessor object. The following options are available:
| This feature was not provided. | A way to process pictures before placing them in a spreadsheet document. Usage examples:
|
| Charts. | The managed form editor allows interactive setup for the following attribute types: Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema. You can open the interactive setup dialog box from the property panel of the attribute. | Only the following ways to set up the Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema objects were available: through 1C:Enterprise script, or by putting a set up object to a template and then putting the object from the template to a form element at form creation. | This feature facilitates development. |
| Data display. | New parameter AU for the global context method NumberInWords(). It is only used in the English locale (en, en_XX). It defines the number notation, classic or compact. In the classic notation "and" is always used between the word "hundred" (or "thousand" or "million") and the word representing the last two decimal digits. For example, 150 is "one hundred and fifty", while 100 is "one hundred" and 50 is "fifty". In the compact notation "and" is omitted. | The compact notation was always used for converting numbers to English words. | Correct number-to-word conversion according to the common practice rule in European countries. |
| Charts of characteristic types. | You can use the ALLOWED keyword when retrieving a list of characteristics, provided that the list was defined using one of the following: the CHARACTERISTICS keyword of the query language or the dialog box for specifying object characteristics. If you retrieve the list of characteristics using a query, you have the option to use the ALLOWED keyword there. | The ALLOWED keyword was not used when retrieving lists of characteristics. | Data access restrictions are implemented for tables that store property lists (for example, charts of characteristic types). |
| Data composition system. | Fields from data sets that are not connected can be displayed in details. For DataCompositionTemplateRecordsDataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects, the DataSets properties are implemented. The property value is an array containing names of data sets whose details are displayed. The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects is deprecated. It is recommended that you do not use this property, although it is supported for compatibility purposes. Calling the DataSet property throws an exception if the DataSets property contains an array with more than one item. | It was impossible to display fields from data sets that were not connected. The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords contained the name of the dataset whose details were displayed. | You can create complex analytic reports. |
| External data sources. | The FormGetProcessing event is implemented in the manager module of external data source table. | This feature was not provided. | The default form of the external data source can be redefined when the external data source is opened or obtained. |
| External data sources. | Hierarchical lists can be organized for object data of external data sources. The ParentField and UnfilledParentValue attributes are implemented for the Table metadata object. Hierarchical object tables can be used in the data composition system, queries, and dynamic lists. | This feature was not provided. | You can work with hierarchical data in external data sources. |
| External data sources. Queries. Data composition system. | You can use temporary tables when working with external data sources. Temporary tables are created directly in the database of the external data source. The following syntax is used for calling temporary tables:ExternalDataSource.<External data source name>.TempTable.<Temp table name>. | This feature was not provided. | You can create complex reports based on external data source tables. |
| Charts of characteristic types. Data composition system. | When creating object characteristics using the Additional characteristics of metadata object dialog, if the list of characteristics is not obtained from the chart of characteristic types, the characteristic value type is defined by the attribute type specified in the Value field attribute of this dialog. If this attribute is not specified, the characteristic value type is Boolean. When object characteristics are specified using the CHARACTERISTICS query language extension of the data composition system, if the TYPE property is not specified, the characteristic type is defined by the value type obtained in the CHARACTERISTICVALUES property. If the CHARACTERISTICVALUES property is not specified, the characteristic value type is Boolean. | When object characteristics were specified using the Additional characteristics of metadata object dialog or the CHARACTERISTICS query language extension, if the list of characteristics was not obtained from the chart of characteristic types, the characteristic value type was Boolean.
| You can store characteristic types in catalogs, and you can modify characteristic types using a complex type of the attribute that stores the characteristic value (e.g., type of information register resource). |
| 1C:Enterprise script. | Serialization of value table index descriptions is implemented. The index content is not serialized, but restored during deserialization. | Value table indexes were lost during serialization/deserialization. | More complete restoration of value table state during deserialization. |
| Charts. | New types of charts are implemented:
The following properties are implemented for the Chart object: FunnelNeckHeight, FunnelNeckWidth, and FunnelSpace. These properties are applicable for the new charts types only. | This feature was not provided. | New chart functionality. |
| Charts. | Antialiasing mode is implemented for charts. SplineMode and SplineStrain properties are implemented for the Chart object. These properties are applicable to the following chart types: line, stacked line, area, stacked area, normalized area, ceil graph, tape graph, waterfall, funnel, and 3D funnel, and also for the following chart types, which have the Indicator flag set for the series: column, 3D column, bar, 3D bar, stacked column, 3D stacked column, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar. | This feature was not provided. | New chart functionality. |
| Charts. | You can connect series of charts with each other. For the Chart object the following properties are implemented: ValuesBySeriesConnection, ValuesBySeriesConnectionLines, and ValuesBySeriesConnectionColor. These properties are applicable to the following chart types: stacked column, 3D stacked column, stacked bar, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar. | This feature was not provided. | New chart functionality. |
| Charts. | The semitransparency mode is implemented for charts. SemitransparencyMode and SemitransparencyPercent properties are implemented for the Chart object. These properties are applicable to the following chart types: area, bar graph, pyramid graph, ceil graph, tape graph, waterfall, funnel, 3D funnel, and 3D normalized funnel. | This feature was not provided. | New chart functionality. |
| Charts. Data composition system. | For the objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance the following properties are implemented: ChartType.ValuesBySeriesConnection, ChartType.ValuesBySeriesConnectionLines, ChartType.ValuesBySeriesConnectionColor, ChartType.SplineMode, ChartType.SplineStrain, and ChartType.SemitransparencyMode. These properties are used for setting data composition template parameters. | This feature was not provided. | New chart management options in the data composition system. |
| Data composition system. | In the data composition system expression language the following aggregate functions are implemented: Every(), Any(), Stddev_Pop(), Stddev_Samp(), Var_Samp(), Var_Pop(), Covar_Pop(), Covar_Samp(), Corr(), Regr_Slope(), Regr_Intercept(), Regr_Count(), Regr_R2(), Regr_AvgX(), Regr_AvgY(), Regr_SXX(), Regr_SYY(), and Regr_SXY(). | These aggregate functions were not provided in the data composition system expression language. | The new functions facilitate creation of complex analytic reports. |
| Data composition system. | In the data composition system expression language the following functions are implemented: ACos(), ASin(), ATan(), Sin(), Cos(), Tan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Round(), Int(), ValueType(), and Type(). | These functions were not provided in the data composition system expression language. | The new functions facilitate creation of complex analytic reports. |
| Data composition system. | New aggregate function Rank() in the data composition system expression language. The function returns a sequence number of the current record in the current grouping, provided that all records of the current grouping are sorted in the specified order. | This aggregate function was not provided in the data composition system expression language. | The new functions facilitate creation of complex analytic reports. |
| Data composition system. | New aggregate function ClassificationABC() in the data composition system expression language. The function returns the class number: 1 – class "А", 2 – class "B", 3 – class "C". | This aggregate function was not provided in the data composition system expression language. | The new function facilitates creation of complex analytic reports. |
| Spreadsheet documents. | The Merge command is added to the shortcut menu of a spreadsheet document. It is also accessible through a keyboard shortcut Ctrl+M.
| Merging cells of a spreadsheet document was only available by using the menu command Table - Merge or clicking the corresponding toolbar button. | Improved usability of spreadsheet documents containing a large number of merged cells. |
| Charts. | The Indicator property is supported for the tape graph chart: when antialiasing is disabled, the series with the Indicator property set are displayed semitransparently on the entire chart area, overlapping other series. | This feature was not provided. | New chart functionality. |
| Managed forms. | You can specify the Arbitrary type for a subordinated attribute of a managed form attribute (e.g., column of a value table, column of a value tree, etc.). | It was impossible to store some data types (such as a references to external data source tables) in subordinated attributes of managed form attributes. | You can store references to external data source tables in subordinated attributes of managed form attributes. |
| Data display. | You can manage duplex printing of spreadsheet documents, graphical schemas (using script and interactively), and text documents (interactively only). System enumerations DuplexPrintingType and PagePlacementAlternation are implemented. | This functionality was only available from a printer driver. | You can explicitly specify the duplex printing option in some use cases. |
| Development tools. Web client and web service publishing tools. | In the dialog for publishing to the web server you can edit all tags present in the default.vrd file. You can edit custom default.vrd files in this dialog. The descriptor parameter of the webinst utility allows you to perform publishing by template. The generated default.vrd file is used as a template. | A limited set of tags present in the default.vrd file was available for editing in the dialog for publishing to the web server. The option to publish by template was unavailable in the webinst utility, which limited the capabilities of automatic publication. E.g., publishing of web services using the utility was impossible. | You can edit all tags of the default.vrd file interactively, and you can create templates for the future automatic publication. Using templates allows publishing web services using the command line utility. |
| Client application installation. | You can set up the update of thin client distribution kit and downloading the list of common infobases using an HTTP connection or a web service. If versions of client and server applications do not match, the thin client is downloaded and installed automatically. The following parameters of the 1cestart.cfg file are implemented :
You can specify a link to the thin client distribution kit in the following configuration files:
| Automatic update of the thin client and downloading of list of common infobases were only available in a local network. | You can update the thin client distribution kit and download the list of common infobases without creating common directories. This allows you to obtain an up-to-date version of the distribution kit and the current list of infobases from a remote network. |
| DBMS operations. | DBA rights are not required for creating infobases in Oracle Database. The following actions cannot be performed without DBA rights:
| DBA rights were required for creating infobases in Oracle Database. | Increased security of DBMS operations. New scenario of creating an infobase without DBA rights, provided the database (data schema) already exists. |
| Internet-enabled functionality. 1C:Enterprise script. | Encoding of text strings is implemented (the global context method EncodeString()). It simplifies the following operations:
Decoding of text strings is implemented (method DecodeString()).
| This feature was not available. | Easier generation of URLs containing non-English characters. |
| Administration tools. | You can create a self-extracting archive (SFX archive) of a client application and upload it to a web site. You can include the client application distribution kit and the 1CEStart.cfg configuration file, which is used for installing the client application, into the archive. The created executable file is only intended to run on Windows operating systems. The self-extracting archive is generated using the 1CEClientSetupMake.exe utility, which is distributed via ITS (http://its.1c.ru/db/metod81#content:4914:1). | This feature was not provided. | Simplified installation of client applications on the client computer for infobase access over the Internet (instead of using the web client). |
| Functionality | After | Before | Result of change |
|---|---|---|---|
| Standard functions. | The search for references to external data source tables is available for the standard function Find references to object, which operates in the managed mode. | It was impossible to find references to objects of external data sources tables using the standard function Find references to object. | You can search for references to external data source objects using a standard function. |
| Spreadsheet documents. | In a spreadsheet document that is in the read-only mode, you can expand and collapse groups not only using a mouse, but also using keyboard shortcuts and the shortcut menu of the spreadsheet document. | In a spreadsheet document that was in the read-only mode, expanding and collapsing groups could only be performed using a mouse. | Improved usability of spreadsheet documents. |
| Navigation links. | In the In tabs form opening mode when a form is opened by clicking a navigation panel command and the navigation link is requested, if the managed form property AutoUrl is set to True, the form returns a link to the object displayed by the form. Otherwise, it returns the value of the Url property of the managed form. | In the In tabs form opening mode forms opened by clicking navigation panel commands returned links to navigation points. | You can open a list form in a separate window using the shortcut menu of the tab title. |
| Managed forms. | If the EditMode property of a managed form table cell is set to Directly, pressing the Enter key in this cell moves the cursor to the next editable cell in this row. If the cell is last in a row, the cursor is moved to the first editable cell of the next row. If there is no next row and the managed form table has the Autoinput new row property set to True, a new row is added. | In the row editing mode pressing the Enter key finished editing the table cell and did not move the cursor to the next cell. | Pressing the Enter key is handled in the same way in the new row input mode and in the row editing mode. This simplifies working with the platform and enhances editing table data using the keyboard. |
| Managed forms. | While editing a cell of a managed form table with EditMode property set to Directly:
| These features were not provided. | Improved usability of managed form tables. |
| Managed forms. | In managed forms, in automatic table row adding mode, you can delete rows by pressing Alt+Shift+Del. A row is deleted in the following cases:
You can use this keyboard shortcut even while you are editing a table row. | This feature was not provided. | Improved usability of managed form tables. |
| Managed forms. | If you press the Down Arrow key while the cursor is in the last row of a managed form table, a new row is added. If you press the Up Arrow key while the cursor is in a new row and the new row is still empty, this row is deleted. If you move the cursor from top to bottom by holding down the Down Arrow key, the cursor will stop at the last row of the managed form table. To add a new row, release the Down Arrow key and press it again. | Pressing the Down Arrow key did not create a new row. Pressing the Up Arrow key did not undo the creation of a new row. | Improved usability of managed form tables. |
| Managed forms. | For attributes of String type that have fixed length, the automatic marking of incomplete attributes is modified. The change affects attributes located in managed form tables, table boxes or spreadsheet documents. The check whether the attribute is performed using the ValueIsFilled() method, so the value of String type is considered incomplete if it does not contain any any characters except spaces. | An attribute was considered incomplete only if it contained a blank string. | Unified the behavior of marking of incomplete attributes. |
| Web client. | When the web client is started in a web browser that is not in the list of supported ones, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per week. | The check for supported web browsers was not performed. | The user receives a warning if they use an unsupported web browser or an unsupported version of a supported browser. |
| Web client. | When the web client is started in a web browser whose version is not supported, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month. | The check for supported browser versions was not performed. | The user receives a warning when they use an unsupported web browser or an unsupported version of a supported browser. It is recommended that they change their browser version when they receive the warning. |
| Web client. | When the web client is started in Microsoft Internet Explorer version later than those available during the platform development, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month. | The check for supported Microsoft Internet Explorer versions was not performed. | The user is notified if their Microsoft Internet Explorer version was not tested for compatibility with 1C:Enterprise. |
| Technological log. | You can write information about working with external data sources to the technological log. For this purpose, the <EDS> event is added to the configuration file of the technological log. | Working with external data sources was not reflected in the system technological log. | A tool for analyzing problems that might occur while working with external data sources. |
| Technological log. | You can have all operations that affect server cluster functioning (for example, operations performed during data replication between cluster services) written to the technological log. For this purpose, the <CLSTR> event is added to the technological log configuration file. | Events that were generated during the execution of operations that affected server cluster functioning were not reflected in the technological log. | A tool for analyzing server cluster issues. |
| Server clusters. Administration tools. | Cross-platform administration server (RAS) is implemented for administering the server cluster. The application can run both as a standalone application and a service (daemon). The administration server is installed with 1C:Enterprise server. The cross-platform command line utility (RAC) is implemented for the administrator server. The utility is installed with 1C:Enterprise server. Administration utility version and administration server version may differ. The utility provides the same administration functionality as program cluster administration tools (the V82.ComConnector COM object), except operating system authentication of the administrator in infobases, clusters, or working servers. The utility does not support this feature. An interface for working with the administration server using Java is also implemented. The interface is distributed via ITS (together with its description and usage example) (http://its.1c.ru/db/metod81#content:4985:1). | Tools for 1C:Enterprise server cluster administration were only available for Windows operating system as a cluster administration console and as V82.ComConnector COM object. Linux tools for server cluster administration were not provided. | You can administer 1C:Enterprise server cluster using the command line in various operating systems (Windows and Linux), and also from Java programs. |
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| DBMS operations. | Optimized performance of Oracle DBMS queries that include complex conditions for data access restrictions. | Insufficient performance of queries that include complex conditions for data access restrictions. | Improved performance of operations with data access restrictions in Oracle Database. |
| Applied objects. | Working with memory is optimized for some mechanisms. | Insufficient performance in certain scenarios. | Improved overall system performance in some scenarios. |
| Queries. | When executing a query, for all IN HIERARCHY conditions with the same parameter value a single temporary table per batch query is generated. | When executing a query, for IN HIERARCHY conditions with the same parameter value several temporary tables were generated. | Improved the performance of queries containing the same parameter values in several IN HIERARCHY operations. |
| Queries. | When executing a query, for all IN conditions with the same list of values a single temporary table per batch query (for storing the list) is used. | When executing a query, for IN conditions with the same list of values several temporary tables were generated, one for each condition. | Improved the performance of queries containing the same list of values in several IN operations. |
| Queries. | Improved performance of queries that include the IN HIERARCHY expression. Improved performance of queries that include performing data composition system operations on external data sources by using the IN GROUP and IN GROUP FROM THE LIST expressions. | Insufficient performance of query and report selections in some cases when hierarchy conditions were used. | Improved performance of query and report selections in some cases when hierarchy conditions are used. |
| Server clusters. Client application. | The amount of memory consumed by server working processes is significantly reduced. Reduced client application startup time. The effect is especially noticeable on configurations having large volumes of metadata. | Inefficient use of memory on configurations having large volumes of metadata. | Memory requirements for servers with configurations having large volumes of metadata are reduced. |
| DBMS operations. | For PostgreSQL and Oracle Database, optimized recording register records with update of account register totals. The optimization is achieved by introducing a new index. The performance increase takes effect after restructuring accounting registers and disabling the compatibility mode. | The data structure did not allow using the existing indexes at their full potential, which led to insufficient system efficiency. | Improved performance of operations with accounting registers in PostgreSQL and Oracle Database DBMS. |
| DBMS operations. | Improved performance of requests to main tables when Oracle Database is used. | Response time for some DBMS requests was sub-optimal. | Improved performance of database requests. This includes a significant increase in the speed of configuration updates that require infobase structure updates. |
| DBMS operations. | Optimized some accounting register-related DBMS requests. In particular, optimized requests that include filters by account. | Inefficient usage of DBMS capabilities. | Improved performance for "heavy" accounting register requests (such as, when creating accounting reports or performing month-end closing). |
| DBMS operations. | Optimized operations with temporary tables in Microsoft SQL Server, as well as operations with objects that use temporary tables: accumulation registers, accounting registers, sequences, and so on. | Insufficient performance in case of heavy usage of temporary tables. | Improved performance in case of heavy usage of temporary tables in Microsoft SQL Server. |
| Web client. | Faster start of the web client on slow connections. | A large amount of service information was obtained during the start of the web client. | Faster start of the web client on slow connections. |
| DBMS operations. | Improved performance of operations with Microsoft SQL Server DBMS in the following cases:
| Inefficient usage of DBMS capabilities. | Improved performance of operations with infobases that use Microsoft SQL Server DBMS. |
| Accounting registers. | Improved performance of accounting register operations in the following cases:
The performance increase takes effect after infobase restructuring. | Insufficient performance of accounting register operations in certain use cases. | Improved performance of operations with accounting registers containing a large amount of data. |
| DBMS operations. | The performance of operations with PostgreSQL is improved by changing the index structure. The optimization applies both to new infobases and to existing ones (after restructuring their databases). | Cluster indexes were not used in PostgreSQL operations; regular indexes were created instead. | Faster execution of PostgreSQL operations. |
| DBMS operations. | You can use separate table spaces for indexes (the v81c_index space) and for data (the v81c_data space) in PostgreSQL. Table spaces are not created automatically; a database administrator creates them. If no additional table spaces are created, the default table space (pg_default) is used. | Using a single table space might decrease the performance (due to storage medium overload or performance limitations). | Balancing system performance by recording table spaces to multiple storage media in PostgreSQL. |
| Web client. | Faster opening of the following forms in the web client:
| Delays when opening forms in the web client. | Faster form opening, which improves user experience. |
| Queries. | Improved performance retrieving a selection by group (with a large number of records) from a result of a query containing a TOTALS clause. | Insufficient performance when retrieving a selection by group from a result of a query that contains totals. | Improved performance when processing results of queries that contain totals. |
| Server clusters. | Improved server performance and scalability when processing reference data types. | Insufficient server performance when processing reference data types. | Improved server performance when processing reference data types. |
| DBMS operations. | Temporary tables containing data of unrestricted length are temporary in IBM DB2 version 8.7 and later. | For data of unrestricted length, permanent tables were created and then deleted after use. | System tables cannot get locked. Improved user experience in case when a large number of users are working simultaneously. |
| DBMS operations. | Certain operations with IBM DB2 are optimized. | Insufficient usage of IBM DB2 capabilities. | Faster execution of IBM DB2 operations. |
| DBMS operations. Accounting registers. | Faster processing of accounting register data during database configuration update in the client/server infobase mode. | Insufficient performance when reconfiguring accounting registers. | Faster processing of accounting register data during their reconfiguration. |
| Information registers. | Totals are implemented for periodic information registers. They are intended for retrieving first and last slices, provided that the following conditions are met:
Properties EnableTotalsSliceFirst and EnableTotalsSliceLast are implemented for information registers. Methods RecalcTotals(), SetTotalsUsing(), and GetTotalsUsing() are implemented for information register managers. Access right TotalsControl is implemented for information registers. The Verify and Repair action in Designer includes recalculation of first and last slices if the Recalculating totals option is enabled in the Verifications and modes list and using totals is enabled for the register. | Each slice retrieval resulted in execution of a query to the main register table, with calculation of resource values. | Faster retrieval of first and last slices for the first and the last (current) moments of time. |
| Development tools. | Optimized memory usage in the following cases:
This change is not implemented in 8.2.16 compatibility mode. | In some cases working with configurations that are supported by vendor configurations of large size was impossible. | Reduced RAM usage when working with vendor configurations of large size. |
| Functionality | After | Before | Result of change |
|---|---|---|---|
| DBMS operations. | If a database query contains more than 400 levels of expression nesting, an exception occurs but the system is not shut down. This change is not implemented in 8.2.16 compatibility mode. | If a database query contained more than 400 levels of expression nesting, the system performed emergency shutdown. | The system stability increased, preventing shutdowns when executing complex queries. |
| Attribute fill checks. Functional options. | Attributes disabled by a functional option are not included in the list of checked attributes of the FillCheckProcessingAtServer() handler. This change is not implemented in 8.2.16 compatibility mode. | When generating the list of checked attributes, functional options were not considered. | Application developers do not need to programmatically exclude attributes disabled by functional options from the check. |
| Queries. | If there is a list of totals with a grand total in the query result, unloading the query result using the Unload method (QueryResultIteration.ByGroups) of the QueryResult object results in a tree with a single node with the grand total, while nodes for groupings located in the query after the grand total become the tree elements. This change is not implemented in 8.2.16 compatibility mode. | If there was a list of totals with a grand total in the query result, unloading of the query result using the Unload method (QueryResultIteration.ByGroups) of the QueryResult object created a tree with several nodes of the same level: the grand total and groupings located in the query after the grand total. | The query behavior provides more comfortable work with totals when unloading the result to a tree. |
| Data composition system. | When a data composition result is exported to a collection of values, columns containing calculated fields will have value types specified in the calculated fields. If the calculated field value type is not specified, the value type for the corresponding column is determined automatically based on the calculated field expression. This change is not implemented in 8.2.16 compatibility mode. | When a data composition result was exported to a collection of values, the value types for columns that contained calculated fields were always determined automatically based on the calculated field expressions. | You can specify the calculated field type explicitly in cases when automatic type definition is difficult or impossible. |
| Client/server interaction. | When the server version is changed, sessions running at the time when the server manager is started are not deleted automatically. When a client application that uses a web server is shut down due to the client/server version difference exception, an attempt to delete the session at the server is made. | When the server version was changed, the message Session is missing or deleted was generated. Furthermore, users did not receive messages that clearly described the problem | When the platform version is changed at the server, users receive messages stating that the client application version and the server version differ (instead of the messages stating that the session is missing or deleted). |
| Configuration repositories. | Working with configuration repository is only possible if the repository version matches the Designer version. | The check whether the repository version matches Designer version was not performed. | Prevention of compatibility problems when the configuration repository server and Designer have different versions. |
| Configuration repositories. | When Designer operates in batch mode, if the location of the infobase that is bound to the repository is changed, the infobase is rebound to the repository and no warnings are displayed. When the location check is performed for the infobase bound to the repository, the name of computer from which the connection to the infobase in established is ignored for client/server infobases and for file infobases located on network drives. | In batch mode, a warning about the infobase location change was displayed and user response was expected. When the location check was performed for the infobase bound to the repository, the name of computer from which the connection to the infobase was established was taken into account for client/server infobases and file infobases located on network drives. | In batch mode, an attempt to access a copy of an infobase bound to the repository from the repository user account that is used for accessing the original infobase will lead to disconnecting the original infobase from the repository. A warning about the infobase location change is not displayed for client/server infobases and for file infobases located on network drives if the connections differ only by the name of computer from which the connection is established. |
| DBMS operations. | The following clustered indexes are created when using IBM DB2 DBMS:
| When using IBM DB2 DBMS the following indexes were created:
| Unified approach to the implementation of object indexes in various DBMS. |
| Export to Microsoft Excel. | When a spreadsheet document is exported to Microsoft Excel 97 or Microsoft Excel 2007 format, cells of the spreadsheet document that are left-aligned are exported together with their general formatting. This change is not implemented in 8.2.16 compatibility mode. | When a spreadsheet document was exported to Microsoft Excel 97 or Microsoft Excel 2007, cell values were converted to numbers in the following cases:
| If a cell of a spreadsheet document contains a numeric value, which is intended to be used as text, and the value is left-aligned (e.g., the cell contains a product code or article), when the spreadsheet document is exported to Microsoft Excel format, the cell value is not converted to a number. This simplifies the use of the converted document (including editing and comparison). |
| 1C:Enterprise script. Managed forms. | For methods GetForm(), OpenForm(), and OpenFormModal() the URL parameter is implemented. Its value is assigned to the URL property of received or opened forms, unless the parameter value is Undefined. Furthermore, the AutoURL property of received or opened forms is set to False. For the CommandExecuteParameters object the URL property is implemented. The property usage example is added to the command module example. | This feature was not provided. | You can specify a navigation link for a form that is being opened. The navigation link can be used later in the interactive mode (e.g., stored in the history). |
| Infobase users. | When you press Shift+Del in the list of infobase users, a warning is displayed. | Pressing Shift+Del in the list of infobase users deleted a user without a warning. | Prevention of accidental deletion of infobase users. |
| Software licensing. | If an application license is not found during the start of the application, the differences between the current hardware settings and hardware settings at the moment when the license was obtained are written to the license search log. This information is only written for software licenses. | Information on differences in hardware settings was not listed in the license search log. | Simplified diagnostics of software license problems when the license is not issued due to hardware settings differences. |
| DBMS operations. Managed locks. | In version 8.2.16 compatibility mode, if you use Microsoft SQL Server version 2005 or later and the configuration uses managed lock mode, row versioning is enabled. The transaction isolation level is READ_COMMITED_SNAPSHOT. Consistent read is used for reading data outside of transactions. | Microsoft SQL Server 2005 or later had a lock mode enabled. The transaction isolation level was READ_COMMITED. "Dirty" read was used for reading data outside of transactions. | The following improvements are available:
|
| Managed forms. Data composition system. | You can implement quick choice user settings as a set of form fields in a separate group. You can manage location and other parameters of this group. The User settings group property is implemented for managed form extension for reports. You can create user settings items using the CreateUserSettingsFormElements() method of managed form extension for reports. Before settings elements are created, all existing elements are deleted from the group. Forms that are created automatically (report and user settings forms) include dedicated groups with elements used for editing settings. The OnUpdateUserSettingSetAtServer event is implemented for managed report form extension. The event is called in the following cases:
Presentation of automatically generated report forms is changed: report variant presentation moved to report title; the variant selection button moved to report command bar, etc. This change is not implemented in 8.2.16 compatibility mode. | Quick choice user settings were edited in a special table located in the form. The form for editing user settings contained a table for editing all user settings. There was a field with current report presentation and a button for selecting report variant in the report form. | Improved report settings usability - they are displayed similarly to other form elements because standard form elements (text box, check box, etc.) are used instead of tables for editing settings. |
| Event log. | When event log is being read, events are not filtered by current separator value if the separator is conditionally disabled in the current session. | When event log was being read, records were filtered by value of a conditionally disabled separator. | Eliminated the differences between event log functioning in infobases without separators and infobases with conditionally disabled separators. |
| DBMS operations. | Internal implementation of several query executions for PostgreSQL, IBM DB2, and Oracle Database is modified. This change is not implemented in 8.2.16 compatibility mode. | The implementation took advantage of DBMS specifics to a lesser extent. | Improved the internal implementation of query executions for specific DBMS. |
| Command interface. | Navigation links to lists are implemented. A navigation link request to a form whose main attribute is a dynamic list with the main table specified returns a navigation link to the list of the object specified as the main table. This link opens the default list form. Support of navigation links to lists is implemented for the GotoURLGotoURL() global context method. This change is not implemented in 8.2.16 compatibility mode. | Navigation links to lists were not provided. | Users can store links to lists in history and favorites. |
| Configuration comparison reports. | The configuration comparison report no longer includes added and removed objects whose access rights exactly match their default access rights.
| Added and removed objects whose access rights exactly matched their default access rights were included in the report. | The report no longer displays redundant information that does not help in merging data. |
| Third-party software. | Migrated from OpenSSL 1.0.1 to OpenSSL 1.0.0g. | OpenSSL version 1.0.1 was used. | An HTTP server query error is no longer displayed when the thin client is started. |
| Applied objects. | Value length for Description length and Order length properties of Chart of accounts objects is limited by 628 characters. The current value length is only checked when an attempt to change it is made. | Value length for Description length and Order length properties of Chart of accounts objects was not limited. | Increased platform stability. Prevention of infobase corruption (in the file mode). Prevention of performance losses. |
| Queries. | If a script generated by the query wizard includes result processing, the name of the variable where the result is stored is QueryResult. This change is not implemented in 8.2.16 compatibility mode. | In certain cases (for example, when a query was created with the option to display the processed result in a report), a naming conflict occurred between variable names created by the wizard and attribute names of the report form whose module contained this code. As a result, the generated code did not work properly. | Eliminated naming conflicts between variable names created by the query wizard and report form attribute names (for queries that include result processing). |
| Data composition system. | A query field used in a union operation becomes unavailable to filters if it has the NULL value in all parts of the union. This change is not implemented in 8.2.16 compatibility mode. | If a query field used in a union operation had the NULL value in all parts of the union, filters were applied at the data set level of data composition template, not inside the query. | When the UNION or UNION ALL expression is used in a query that retrieves a data set of the data composition system (with automatic filling of available settings), if a filter is applied to a field attribute, the filter is only applied to the parts of the union where the given attribute exists. When a filter is applied to a field, it is only applied to the parts where the field expression is not equal to NULL. |
| Event log. | The *.elf extension is removed from the Files of type list in the open file dialog box in the thick client and Designer. Opening event logs in the *.elf format is still supported. To open an .elf file, select the Event log (*.lgf) file type and then enter the file name, including the elf extension. | The list of file extensions in the open file dialog box in the thick client and Designer included both *.lgf and *.elf extensions. | Removed obsolete user interface options. |
| Event log. Data display. | Events related to canceled transactions are displayed in gray in the ordinary form of the event log (in the same way as they are displayed in the managed form of the event log). This change is not implemented in 8.1 compatibility mode. | Events related to canceled transactions were displayed in black in the ordinary form of the event log. | Unification of display of ordinary and managed forms of the event log. |
| Standard functions. Data display. | Object presentation in standard functions Find references to object and Delete marked objects is modified. Names of metadata objects types are removed from object presentations. | In standard functions Find references to object and Delete marked objects object presentation contained the name of metadata object type. | System-standard object presentation is introduced. |
| Accumulation registers. Accounting registers. Common attributes / Data separation. Server clusters. | Changes in the table of storage settings for accumulation and accounting register totals are performed within a transaction. While tables are being modified, managed data locks are applied to the corresponding lock namespace. A cache for storing totals storage settings for working processes is implemented. | Changes in the tables of storage settings for accumulation and accounting register totals were performed outside a transaction. Each retrieval of totals storage settings was performed using a database query. | Elimination of conflicts that might occur during the modification of totals storage settings tables from multiple simultaneous sessions that have identical data separator values. Reducing the number of database queries and improving parallel processing for sessions that use separators. |
| Common attributes / Data separation. Accounting registers. Accumulation registers. | If separators are deleted or separator types are modified, during the next update of database configuration records in the tables of totals storage settings for accounting and accumulation registers are merged according to the new sets of separators. | If separators were deleted or separator types were modified, the following situations might occur:
| Improved reliability of operations during database configuration updates caused by deleting separators or modifying separator types. |
| Text operations. | Implemented recording a byte order mark (BOM) to the beginning of files generated by the TextWriter object if the following conditions are met: the file to be recorded does not yet exist, the FinishWriter constructor parameter is set to True, and the text encoding is set to UTF-8. This change is not implemented in the compatibility with 8.2.16 mode. | A byte order mark (BOM) was not added to the beginning of files generated by the TextWriter object if the following conditions were met: the file to be recorded does not yet exist, the FinishWriter constructor parameter is set to True, and the text encoding is set to UTF-8. | A byte order mark (BOM) ensures unique identification of text encoding used in a file. |
| XML and XDTO support. | During the import of XSD schema, if definition is missing from the target namespace schema, a diagnostic message is displayed. | During the import of XSD schema, if any loading problems occurred, a diagnostic message was not displayed. | Improved diagnostics during XSD schema import. |
| DBMS operations. | The documentation describes the specifics of working with the following DBMS: Oracle Database and PostgreSQL. | The documentation did not contain enough details about the specifics of working with the following DBMS: Oracle Database and PostgreSQL. | Documentation is expanded to clarify DBMS usage specifics during configuration development. |
| Spreadsheet documents. | While you are changing the selection area in a spreadsheet document, if the selection area contains rows with different formatting, the platform switches to the row selection mode. Then, if the platform previously was in cell selection mode and after another selection change all selected rows have the same formatting, the platform switches back to the cell selection mode. | The only ways to select rows with different formatting were using headers of spreadsheet document rows or the Alt+Shift+Arrows key combination. | Simplified copying of data from spreadsheet documents with different row formatting. |
| Web client. Spreadsheet documents. | Users can edit spreadsheet documents in the web client. The Table main menu is modified in the web client. Clipboard is implemented for spreadsheet documents in Google Chrome web browser. The clipboard is available within a single browser instance working with a single infobase. | This feature was not provided (except editing cells with values, changing the display mode of groupings, freezing rows and columns, and changing column width). | Users can edit spreadsheet documents after they are generated in the web client. |
| Client application. Web client. Designer. Spreadsheet documents. | In the Table menu of thin client, web client, thick client, and Designer, the Cells submenu is implemented. It includes some of the commands that were previously located in the Table menu, and some new commands. | The Cells submenu was not available in the Table menu of thin client, web client, thick client, and Designer. | Improved usability of spreadsheet documents. Menu items intended for working with spreadsheet document cells are grouped into a single submenu. |
| Dynamic update. | Improved reliability of dynamic update in various situations. | In certain situations dynamic update worked improperly. | Improved reliability of dynamic update operations. |
| Managed forms. | If a width limit is set for a regular group in a managed form, the size of buttons within the group is adjusted (similar to adjusting the size of other elements included in the group). | A width limit set for a regular group might not affect the size of buttons within the group. | Unified the algorithm of adjusting element sizes when a width limit is set for a regular group. |
| Data display. Managed forms. | Tooltips of managed form items can have one of the following types: displayed directly in the text box, displayed near the form item, and opened clicking a button (in a pop-up window). If a tooltip is not specified for a form item, the command bar button linked to this item also does not have a tooltip. You can use the InputHint property, which contains tooltip text, to display a tooltip directly in the text box. This type of tooltip is unavailable for text boxes that display data of Number and Date types. To manage the display of tooltips and their appearance, the ExtendedTooltip and TooltipDisplay properties are implemented for the following form controls: field, table, group, button, and decoration of Text type. | Tooltips were only available in pop-up windows of form items. If a tooltip was not specified for a form item, its title was used as a tooltip for the command bar button linked to this item. | You can manage tooltip formatting and tooltip positions. |
| Functionality | After | Before | Result of change |
|---|---|---|---|
| 1C:Enterprise software system. | 1C:Enterprise version is changed to 8.3. Installation directories are changed:
Names of installation files are changed:
Names of COM objects are changed: V83.Application, V83.ComConnector. The server service name is :
The default name of the user on whose behalf the server service starts is usr1cv8. Default template directory is changed: %APPDATA%\1C\1Cv8\tmplts. Add-in installation directory is changed: %APPDATA%\1C\1Cv8\ExCompT. | 1C:Enterprise version was 8.2. Installation directories had the following names:
Installation files had the following names:
COM objects had the following names: : V82.Application, V82.ComConnector. The server service had the following name:
The default name of the user on whose behalf the server service started was usr1cv82. Default template directory was %APPDATA%\1C\1Cv82\tmplts. Add-ins installation directory was %APPDATA%\1C\1Cv82\ExCompT. | Due to the version number change, names and identifiers that include the version number are changed. |
| Applied objects. | In a document journal the attribute containing the document number is generated with fixed length if all documents included in the journal have a number field of String type of fixed length. Otherwise, the journal field will have variable length. This change is not implemented in 8.2.16 compatibility mode. | In a document journal the attribute containing the number of documents was always generated with fixed length. | The document number is retrieved in a uniform way, which does not depend on the retrieval method (from the document itself or from the document journal). |
| Spreadsheet documents. | When any of the spreadsheet document methods Show(), Print(), Hide(), and Write() is called at server or in an external connection with the SpreadsheetDocumentFileType parameter set to XLS95, an exception occurs. This change is not implemented in 8.2.16 compatibility mode. | When the method was called at server or in an external connection, this did not lead to an error, but the method did not perform any actions either. | Simplified detection of configuration errors related to specifying incorrect file type when working with a spreadsheet document at server or in an external connection. |
| Queries. | Specifying type qualifiers in the Type() function of the query language is not allowed. This change is not implemented in 8.2.16 compatibility mode. | Specifying type qualifiers for the Type() function was allowed, but it did not affect the returned values. | Implemented a check that eliminates the chance to misuse the query language syntax. |
| Spreadsheet documents. | Print scaling of a spreadsheet document does not affect its margin size. This change is not implemented in 8.2.16 compatibility mode. | Print scaling of a spreadsheet document affected its margin size. | Independent management of margin size and print scaling. |
| Data composition system. | When data composition result is put into a collection of values, fields belonging to different groups and referencing to the same data composition field are put in the same collection column. This change is not implemented in 8.2.16 compatibility mode. | When data composition result was put into a collection of values, fields belonging to different groups and referencing to the same data composition field were put in different collection columns. | Output of the result to a collection is performed in the same way as output of the result to a spreadsheet document. |
| Command interface. 1C:Enterprise script. | Format of navigation links to navigation points generated by standard command is modified to the following: e1cib/navigationpoint/Purchases/Catalog.Products.OpenList (example link). The former navigation link format is also supported. This change is not implemented in 8.2.16 compatibility mode. | Navigation links to navigation points generated by standard commands had the following format: e1cib/navigationpoint/Purchases/Catalog.Products.Command.OpenList (example link). | Unified usage of metadata names. |
| DBMS operations. External data sources. | If the Name in the data source property of an external data source field contains a value enclosed in single straight quotation marks, when a DBMS query is generated, this value is not enclosed in double straight quotation marks. Otherwise, if the field value contains special characters, it is enclosed in double straight quotation marks. This change is not implemented in 8.2.16 compatibility mode. | If the Name in the data source property of an external data source field contained special characters (including single straight quotation marks), the value was enclosed in double straight quotation marks. | Compatibility with DMBS that use different field description syntaxes in their query and database fields (for example, MySQL). |
| Software licensing. | The search for available licenses covers all folders where they might be located. | The search for available licenses only covered *.lic files stored in the first folder of the list and skipped any other folders where the license files might be located, regardless of whether the license was found in the first folder. | Increased flexibility of the licensing mechanism. Elimination of problems that occured when the license files were located in multiple folders (for example, the first folder that was searched contained a server license, while another folder contained a multiuser license). |
| Managed forms. | In managed forms, the platform does not read data from hidden dynamic lists. When a form is opened, the value of the CurrentRow attribute of the managed form table connected to the dynamic list is Undefined. The CurrentRow attribute value is changed at the moment when the table is displayed to the user. This change is not implemented in 8.2.16 compatibility mode. | In managed forms, the platform read data from all dynamic lists, whether they were displayed on the form or not. | Reduced time for opening forms that contain multiple pages with dynamic lists. |
| Functional options. Managed forms. | Behavior of the following form elements related to functional options is modified:
This change is not implemented in 8.2.16 compatibility mode. | Attributes and form elements had the following behavior:
| Increased effect of default functional option values on the data composition system. Unification of functional option effect on various application elements.
|
| Functional options. Data composition system. | Functional option effect on the data composition system is modified:
This change is not implemented in 8.2.16 compatibility mode. | The data composition system did not disable fields or query tables connected to data whose type was disabled by functional options. | Increased automatic effect of functional options on the data composition system. Unification of functional option effect on various application elements. |
| Functional options. Command interface. | Commands of the command interface become unavailable in the following cases:
This change is not implemented in 8.2.16 compatibility mode. | The command availability was not changed if the availability of the attribute, which was used as a parameter for the command, was changed, or when the command parameter type was disabled by a functional option. | Increased effect of functional options on the data composition system. Unification of functional option effect on various application elements. |
| Data composition system. Spreadsheet documents. | You can fix rows and columns of a spreadsheet document using the FixedLeft and FixedTop output parameters. If the fixed area exceeds the displayed area, the fixing is automatically turned off. | The data composition system always used fixing of rows and columns in reports. In spreadsheet documents the fixed area might be larger than the displayed area. | Improved usability of row and column fixing in reports. Users can disable fixing in reports when they find it inconvenient. Fixing is disabled automatically when it does not allow scrolling of the spreadsheet document. |
| Managed forms. | It is recommended that you use methods SetObjectAndFormConformity() and GetObjectAndFormConformity(). Methods SetObjectAndFormAttributeConformity() and GetObjectAndFormAttributeConformity() are declared deprecated, they are only supported for compatibility purposes. | Methods SetObjectAndFormAttributeConformity() and GetObjectAndFormAttributeConformity() were not declared deprecated. | New methods with enhanced functionality are implemented, while the old ones that provide similar functionality are declared deprecated. |
| Lock manager. | When using the Range object constructor, an exception is thrown if the left range boundary is greater than the right one. This change is not implemented in 8.2.16 compatibility mode. | Using the Range object constructor was allowed when the left boundary of the range was greater than the right one. | Elimination of unpredictable behavior of the managed locks manager. Elimination of developer errors. |
| Managed locks. | When a managed lock is set in the file mode of the infobase, types are validated for the values located in the DataSource attribute of the DataLockItem object. This change is not implemented in 8.2.16 compatibility mode. | Validation of the value types was not performed in the file mode. | Unified behavior in the file and client/server modes. Easier detections of errors in the applied solution. |
| 1C:Enterprise script. | An attempt to assign a value to an item of a fixed structure causes an exception. This change is not implemented in 8.2.16 compatibility mode. | An attempt to assign a value to an item of a fixed structure did not cause an exception, and the value was not assigned. | Behavior of fixed structures is similar to behavior of other fixed collections. |
| Web client. System requirements. | Mozilla Firefox versions 3.0 and 3.5 are no longer supported. | Mozilla Firefox versions 3.0 and 3.5 were supported. | Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported. |
| Web client. System requirements. | Microsoft Internet Explorer version 6.0 is no longer supported. The warning that was displayed when the web client was started in Microsoft Internet Explorer 6.0 is changed to the warning about unsupported web browser. | Microsoft Internet Explorer version 6.0 was supported. | Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported. |
| Spreadsheet documents. | Whenever a spreadsheet document is transferred between the client and the server, the values of its ReadOnly and Protection properties are preserved. This change is not implemented in 8.2.16 compatibility mode. | Whenever a spreadsheet document was transferred between the client and the server, the values of its ReadOnly and Protection properties were set to False. | Whenever a spreadsheet document is transferred between the client and the server, its properties are preserved in a uniform way. |
| Formatted documents. | Formatted document object model is extended. The document text consists of paragraphs of various types, which are included in the paragraph collection. A paragraph consists of items included in the formatted document item collection. Functionalities for paragraph and item management are implemented. Methods GetItems() and GenerateItems() return the array of formatted document items located between the specified bookmarks. Method FindText() returns the formatted document area (FormattedDocumentRange object) that contains the specified text. The ItemType parameter type in methods Add() and Insert() of the FormattedDocument object was changed. Methods Add() and Insert() of the FormattedDocument object return the added/inserted item. You can add a picture by specifying its URL (in text format). It is recommended that you do not add or insert pictures using binary data, this options is present for compatibility purposes only. It is recommended that you use the Picture object for inserting pictures.
| Formatted document text was not represented as an object model. | You can implement various text processing algorithms that are based on standard formatting elements (paragraphs, lists, and so on). Automated text generation is now simpler. |
| Data access restrictions. | If the Update right of an object includes data access restrictions with conditions that apply to tabular section attributes, writing the object after it was modified is only allowed if tabular section data before and after the modification match the data access restrictions. Requests from data access restrictions to tabular sections increase the processing time. This change is not implemented in 8.2.16 compatibility mode. | If the Update right of an object included data access restrictions with conditions that applied to tabular section attributes, then whenever tabular section attributes were modified, their compliance with the data access restrictions was not be verified. | Data access restrictions apply to object data and object tabular section data in a uniform way. |
| DBMS operations. | For complex Oracle Database queries of certain type, DBMS request generation rules are modified. Cases that led to DBMS errors are eliminated. A slowdown in DBMS request execution can occur if there are many join operations. It is recommended that you do not use queries with a large number of join operations. This change is not implemented in 8.2.16 compatibility mode. | When executing complex Oracle Database queries of certain type, DBMS errors might occur in some cases. | Improved stability when using Oracle Database. |
| Internet-enabled functionality. | You can use secure versions of SMTP and POP3. The following properties are implemented for the InternetMailProfile object: SMTPUseSSL, POP3UseSSL, IMAPSecureAuthenticationOnly, SMTPSecureAuthenticationOnly, and POP3SecureAuthenticationOnly. POP3 supports the GetMessageCount() method of the InternetMail object. It is recommended that you do not use SMTPAuthentication and POP3Authentication properties of theInternetMailProfile object, as well as SMTPAuthenticationMode and POP3AuthenticationMode enumerations. SMTPAuthentication and POP3Authentication properties, as well as SMTPAuthenticationMode and POP3AuthenticationMode enumerations are supported for compatibility. It is recommended that you use SMTPSecureAuthenticationOnly and POP3SecureAuthenticationOnly properties of the InternetMailProfile object. | The InternetMail object did not supportsecure versions of SMTP and POP3. | You can use secure versions of SMTP and POP3. |
| Internet-enabled functionality. | Default values are changed for InternetMailProfile object properties that store port numbers:
This change is not implemented in 8.2.16 compatibility mode. | The InternetMailProfile object properties that store port numbers had the following default values:
| Simplified port setup for the InternetMailProfile object. In most cases the default port values suffice. |
| Managed forms. | Changed the behavior of the drop-down list in form fields that contain reference data types, enumerations, or system enumerations. Changed the look and behavior of the drop-down list. The system storage settings now store the history of previously selected values (the ChoiceHistory setting). If user-generated lists, using a value of the FormattedString type as a value presentation is allowed. This change is not implemented in 8.2.16 compatibility mode. | The drop-down list had a different look and behavior. The choice list did not appear in the drop-down list. | Better usability of fields, which display data of reference types, enumerations, or system enumerations. |
| Linux. | The configuration utility for Linux is named config_system. | The configuration utility for Linux was named config_server. | The new utility name provides a better description of its purpose because it performs the environment check not only at the server side, but also at the client application side. |
| Administration. | The location.cfg configuration file stores the list of directories where 1C:Enterprise searches for system data. During the installation of version 8.3, the search for data (user profiles, configuration files, software license files, etc.) belonging to version 8.2 is performed in directories available to the current user. If directories with data belonging to version 8.2 are found, then location.cfg files are generated in the directories intended for storing data in version 8.3. These files contain links to directories with data from version 8.2. Therefore, installing the new version does not require transferring all data and settings from version 8.2 directories to version 8.3 directories. | This feature was not provided. | After installing version 8.3, you can use a single list of settings for version 8.2.16 and version 8.3. |
| Software licensing. | If the software license is activated "for all users" or using 1C:Enterprise server, the following directory is used for storing software licenses:
The directory is created during 1C:Enterprise installation. Rights for accessing the created directory are granted depending on the operating system being used:
Only users with administrative rights can obtain a client license "for all users". | The following directory was used for storing the software license files:
On Windows, the directory was used when the software license was activated "for all users", and on Linux - when the software license was activated using 1C:Enterprise server. | Administration of software license files is made easier. 1C:Enteprise versions 8.2.16 and 8.3 can use the same set of licenses when their software licenses are activated "for all users" or using 1C:Enterprise server. |
| Server clusters. Administration tools. | The server cluster administration scheme is modified. The management of cluster processes and function distribution between these processes are performed automatically, and therefore the option to manage them manually is removed. You can affect the automatic distribution process by creating service cluster assignment rules or working server connection rules. The server cluster is functional until at least one working server marked as central server is running. The server cluster availability is defined by the Fault tolerance level parameter (the maximum number of working servers that can become unavailable without service interruption). In the cluster console, the server cluster is displayed by its name (the Cluster name property), not by its port. The software tools for administering server cluster version 8.3 are not compatible with the software tools for administering server cluster version 8.2. The SessionFaultToleranceLevel property is implemented for the IClusterInfo object. For the IWorkingServerInfo object the following properties are implemented: MainServer, ClusterMainPort, DedicatedManagers, InfoBasesPerWorkingProcessLimit, ConnectionsPerWorkingProcessLimit, and WorkingProcessMemoryLimit. The IAssignmentRule object is implemented, it allows to manage the functionality of working servers. The list of required functionality assignments is available via the IServerAgentConnection object and the cluster console. For the IServerAgentConnection object the following methods are implemented: RegAssignmentRule(), UnregAssignmentRule(), GetAssignmentRules(), CreateAssignmentRule(), and ApplyAssignmentRules(). The properties of IWorkingProcessInfo, IClusterManagerInfo, and IClusterServiceInfo objects are read-only. For the IServerAgentConnection object the following methods are removed: CreateWorkingProcessInfo(), RegWorkingProcess(), UnregWorkingProcess(), StartWorkingProcess(), StopWorkingProcess(), SetWorkingProcessUsage(), SetClusterMultiProcess(), SetWorkingProcessCapacity(), SetClusterDescription(), CreateClusterManagerInfo(), RegClusterManager(), UnregClusterManager(), RegClusterService(), UnregClusterService(), CreateStandbyClusterItem(), RegStandbyCluster(), UnregStandbyCluster(), and GetStandbyClusterList(). The IStandbyClusterItem object is deleted. The SyncPort property is deleted for the following objects: IWorkingProcessInfo, IClusterManagerInfo, IWorkingServerInfo, and IClusterInfo. | Management of cluster processes and function distribution between these processes could only be performed manually. The server cluster was displayed in the cluster console as a port number. The fault tolerance level could not be set. | Working processes are managed automatically, so that the load distribution in the server cluster is improved. At the same time, an administrator can specify working servers where certain cluster services or connections will be executed (using rules). For example, they can move the license management service to a separate working server with minimal configuration changes, or execute certain background jobs at the working server that is running Windows operating system. |
| Server clusters. | On Linux operating system, a server is not automatically started after it is installed. | On Linux operating system, servers were automatically started after they were installed. | A server is not started in the environment that is not fully configured. To configure the environment, you have to run the config_system utility first, and then you can start the server. |
To perforrm the conversion of the cluster register from version 8.2. to version 8.3 once more, stop the server cluster 8.3, delete the server cluster 8.3 register (the 1CV8Clst.lst file), and then start the server cluster 8.3.