Changes that require modification of configuration and administrative settings




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:

  • Value lists serialized in version 8.3.10 cannot be read in version 8.3.6 or earlier but can be read in version 8.3.7 or later by using XDTOFactory
  • Value lists serialized in version 8.3.10 can be read in version 8.3.6 or earlier by using XDTOSerializer
  • Value lists serialized in versions 8.3.7 to 8.3.9 can be read in any version.
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:
  • For displaying on monitors: style-based color for text editing
  • For printing: black

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:
  • Restrictions to the length of string that can be entered are removed
  • The input field displaying this data is automatically stretched horizontally

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:
  • 1CEnterprise 8.msi — 32-bit version, full distribution kit
  • 1CEnterprise 8 Thin client.msi — 32-bit version, thin client
  • 1CEnterprise 8 (x86-64).msi — 64-bit version, full distribution kit
  • 1CEnterprise 8 Thin client (x86-64).msi — 64-bit version, thin client

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.
Redesigned user notifications available in Taxi interface. The new notification functionality includes:
  • Displaying multiple notifications simultaneously
  • Displaying notifications while the main application window is minimized
  • Refreshing the notification window until the user closes it
  • Reacting to the user touching the notification window

Implemented notification management through the notification center. Dragging the notification window is not supported. For global context method ShowUserNotification(), implemented parameters UserNotificationStatus and UniqueKey. The parameter of URL method is renamed to ActionOnClick.

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. Notification management in Taxi interface is now more user-friendly.
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:
  • Parameters controlling the appearance of series or points are set to default values
  • The chart is redrawn.

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:
  • If the resulting value table was not transferred between the client and the server, both English and Russian.
  • If the resulting value table was transferred between the client and the server, English only.
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 Consolidated group property set to False.

This change is not implemented in 8.3.9 compatibility mode.

For managed form groups with Consolidated group 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:
  • Loading a report option
  • Calling DataCompositionSettingsComposer.Refresh()

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:
  • Loading a report option
  • Calling DataCompositionSettingsComposer.Refresh()
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.60. 1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 6.60. 1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver.

Comments
0
Add comment