Changes that affect system behavior




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 :
  • Module line numbers
  • Synchronization between the comparison window and the merge result editor window
  • The editor window functionality is closer to that of 1C:Enterprise script editor window
  • Context help is available in the editor window. The context includes the main configuration (before merging) and the current module (after merging)
  • The window title displays the module name

The following features are implemented in the window that displays the result of merging with a third-party tool:

  • The editor window functionality is closer to that of 1C:Enterprise script editor window
  • Context help is available in the editor window. The context includes the main configuration (before merging) and the current module (after merging)

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 extension configuration attribute type includes AnyRef, this requires the matching main configuration attribute type to include any reference.
  • If an extension configuration attribute type includes CatalogRef, DocumentRef, and similar types, this requires the matching main configuration attribute to include any reference type of that kind.

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:
  • elementFormDefault was always qualified.
  • attributeFormDefault was always unqualified.

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:
  • ChoiceParameters, supplemented with values based on the ChoiceParameterLinks property
  • ChoiceForm (in the web client)
  • ChoiceFoldersAndItems (in the web client)
  • Mask
  • EditFormat
  • QuickChoice
  • TypeLink
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:
  • ChoiceParameters, not supplemented with values based on the ChoiceParameterLinks property
  • ChoiceForm (thin client only)
  • ChoiceFoldersAndItems (thin client only)
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:

  • The Auto value of Representation property is equivalent to Picture.
  • The Auto value of OnlyInAllActions property is equivalent to No.

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:

  • The Auto value of Representation property was equivalent to Text.
  • The Auto value of OnlyInAllActions property was equivalent to Yes.

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), and 271-FZ (Novosibirsk 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, and 271-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:
  • For standard Microsoft Excel formats, matching 1C:Enterprise format strings are applied.
  • 1C:Enterprise format strings are defined based on the locale codes explicitly specified in Microsoft Excel format strings.
  • The date type uses the first short date format separator found in the infobase.
  • Dates where the month is specified by its first letter are converted to 1C:Enteprise dates having short month presentation.

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:
  • A fixed list of standard Microsoft Excel formats was applied.
  • Locale codes explicitly specified in Microsoft Excel format strings were ignored. The current infobase settings were used instead.
  • The date type always used the slach (/) separator.
  • Dates where the month was specified by its first letter were converted to dates having full month presentation.
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:

  • Create any configuration object.
  • Save the infobase configuration.
  • Delete that configuration object.
  • Save the infobase configuration.
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.

Comments
0
Add comment