Changes that require modification of configuration and administrative settings




FunctionalityAfterBeforeResult 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 infobase is registered in the collaboration service.
  • The infobase registration is active.
  • There are collaboration system users in the infobase.

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:
  • The infobase was registered in the collaboration service.
  • The infobase registration was active.
  • There were collaboration system users in the infobase.
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.
  • The UserSettingPresentation property of DataCompositionFilter, DataCompositionSelectedFields, DataCompositionConditionalAppearance objects.
  • The UserSettingPresentation, Presentation, LeftValue, Application, Parent properties of the DataCompositionFilterItem object.
  • The UserSettingPresentation, Presentation, Application, Parent, GroupType, Items properties of the DataCompositionFilterItemGroup object.
  • The UserSettingPresentation, Presentation, Fields, Filter, UseInGroup, UseInHeader, UseInFieldsHeader, UseInHierarchicalGroup, UseInOverall, UseInFilter, UseInParameters properties of the DataCompositionConditionalAppearanceItem object.
  • The UserSettingPresentation, NestedParameterValues, Parent, Parameter (only when setting the property value) properties of the DataCompositionSettingsParameterValue object.
  • The UserSettingPresentation, ID, Name, Choice, Filter, OutputParameters, GroupFields, Order, Parent, State, Structure, ConditionalAppearance properties of the DataCompositionGroup, DataCompositionTableGroup, DataCompositionChartGroup objects.
  • The UserSettingPresentation, Choice, ID, Name, Columns, OutputParameters, Parent, Strings, ConditionalAppearance properties of the DataCompositionTable object.
  • The UserSettingPresentation, Choice, ID, Name, OutputParameters, Parent, Sreies, Points, ConditionalAppearance properties of the DataCompositionChart object.
  • The UserSettingPresentation, ID, ObjectID, Name, Settings, Parent properties of the DataCompositionNestedObjectSettings object.
  • The UserSettingPresentation and ViewMode properties of the DataCompositionSettingStructureItemCollection object. This change is available only if the parent of the DataCompositionSettingStructureItemCollection object is a DataCompositionSettingStructure type object that is included in the DataCompositionUserSettingsItemCollection collection.

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:
  • less or equal to 100 rows. The number of event calls was equal to the rows number.
  • more than 100 rows. The event was called once.
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:
  • SetModificationTime()
  • SetModificationUniversalTime()
  • BeginSettingModificationTime()
  • BeginSettingModificationUniversalTime().

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:
  • SetModificationTime()
  • SetModificationUniversalTime()
  • BeginSettingModificationTime()
  • BeginSettingModificationUniversalTime().
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:
  • Number with 1.0 precision
  • String of 1 character
  • DateTime
  • Boolean
  • NULL

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.

Comments
0
Add comment