|Functionality||After||Before||Result of changes|
||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.|
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.|
||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.|
||Implemented additional processing for data received by a dynamic list before the data is displayed. Implemented event OnDataGetAtServer. 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.|
||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.|
||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.|
||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.|
|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.|
||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.|
|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.|
||Implemented control of planner interval background color in accordance with values of measurements associated with this interval. Implemented property PlannerBackgroundInterval.DimesionValues.||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.|
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.|
||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.|
||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.|
||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.|
||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.|
||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.|
||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.|
|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.|
||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 PickVariant.||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.|
||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.|
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 DataCompositionAreaTemplateChartGroupingAppearance and DataCompositionAppearance, implemented parameters ChartTrendline, ShowGraphicalDataRepresentationInChart, and ShowGraphicalDataRepresentationInChartLegend.
|These features were not provided. Value of property ChartSeries.Marker was set to Square, Circle, or Diamond, based on series number.||Additional chart features, related to appearance control and analytics, are now implemented.|
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.BubbleSizing, 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.|
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.|
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.
|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.|
||Implemented the "collaboration system" feature. It is a text message and call system for 1C:Enterprise application users. It features audio calls with optional video feed.. Text conversations can be related to specific infobase objects (context conversations) or not related to any objects (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.
|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.|
||Implemented management of availability of dynamic list fields (including subordinate fields) for use in groupings, filters, and order settings. Implemented methods SetUseRestrictionsInGroup(), SetUseRestrictionsInOrder(), SetUseRestrictionsInFilter(), GetUseRestrictionsInGroup(), GetUseRestrictionsInOrder(), and GetUseRestrictionsInFilter().||These features were not provided.||Now developers can explicitly prohibit groupings, ordering, and filtering for fields not intended for these operations.|
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).|
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.|
||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.|
|Support of PostgreSQL version 9.6 is implemented.||This PostgreSQL version was not supported.||Extended list of supported PostgreSQL versions.|
|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.|
New functionality and changes