Changes that affect system behavior




FunctionalityAfterBeforeResult 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:
  • Charts are displayed in black-and-white mode.
  • Geographical schemas are displayed in black-and-white mode.
  • Pictures and OLE objects are displayed in grayscale.

In black-and-white printing mode:

  • Charts are printed in black-and-white mode (this behavior is not changed).
  • Geographical schemas are printed in black-and-white mode (this behavior is not changed).
  • Pictures and OLE objects are displayed in grayscale.

This change is not implemented in 8.3.11 compatibility mode.

In black-and-white view mode:
  • Charts were displayed in full color.
  • Geographical schemas were displayed in full color.
  • OLE objects were displayed in full color.
  • SVG, EMF, and WMF pictures were displayed in full color.
  • Other pictures were displayed in grayscale.

In black-and-white printing mode:

  • Charts were printed in black-and-white mode.
  • Geographical schemas were printed in black-and-white mode.
  • OLE objects were printed in full color.
  • SVG, EMF, and WMF pictures were printed in full color.
  • Other pictures were printed in grayscale.
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:
  • In the device selection menu (for mobile device view), the current device is marked.
  • In the scale selection menu (for mobile device view), the current scale is marked. Scale options similar to scale options for personal computers are implemented in this menu.
  • In the scale selection menu (for personal computer view), the current scale is marked.
  • In the resolution selection menu (for personal computer view), the following features are implemented:
    • Information about the current resolution.
    • The option to select a display (the one where the Designer window is displayed).
    • Information about typical DPI for each resolution.
    • The option to select display resolutions 4K (3840*2160 pixels) and 5K (5120*2880 pixels).
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:
  • In the thin client, the form table column name.
  • In the web client, the form table column header.
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:
  • For vertical groupings, the maximum value among the minimum width values of subordinate items.
  • For horizontal groupings, the sum of minimum width values of all subordinate items plus the total width of gaps between them.

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 will use the AlwaysHorizontal value, and the mobile platform will use 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.

Comments
0
Add comment