Changes that require modification of configuration and administrative settings




Functionality After Before Result of changes
Internet-enabled functionality.
The NSSSecureConnection object and NSS certificates cannot be accessed from 1C:Enterprise script.

This change is not implemented in 8.3.6 compatibility mode.

1C:Enterprise system supported NSS certificates. Future platform versions will not support NSS certificates.
Common objects.
In the thin client, the ValueStorage.Get() method raises an exception.

This change is not implemented in 8.3.6 compatibility mode.

In the thin client, the ValueStorage.Get() method did not raise an exception and returned the Undefined value instead. Running this method in the web client raised an exception. Uniform system behavior across multiple client applications.
Interface.
Managed forms.
The choice history generation rules for managed form text boxes are modified. In particular, the frequency of history item usage is taken into account. The history consists of up to 7 items, which include both frequently used and last used values. The history generation rules are described in detail in the documentation.

The system storage of managed form text box choice history stores a value of the ChoiceHistorySettings type.

This change is not implemented in 8.3.6 compatibility mode.

The choice history generation rules for managed form text boxes were different. The history stored 5 last values.

The system storage of managed form text box choice history stored a value of the Array type.

Improved usability of managed form text box choice history.
Managed forms.
New algorithm for automatic arrangement of managed form items is implemented. As a result, item positioning is improved, new item placement options are added, changing some item properties on the client does not require a server call (this includes expanding or collapsing groups and showing or hiding form item addition extension for view status), rules for automatic generation of form separators are modified, and more. In many cases toggling form item visibility no longer requires a server call. Detailed description of this feature is provided in the documentation.

In the managed form editor, quick preview of a form with specific screen resolution and specific screen orientation is available.

For the ChildFormItemsGroup system enumeration, the HorizontalIfPossible value is implemented. The AutoMaxWidth, MaxWidth, AutoMaxHeight, and MaxHeight properties are implemented for the following objects: managed form field extension for a label field, text box, picture field, spreadsheet document field, text document field, formatted document field, calendar field, progress bar field, track bar field, chart field, Gantt chart field, dendrogram field, geographical schema field, HTML document field, graphical schema field, period field, planner field, and for managed form items of table, decoration, and button types.

For managed form items of form, group, and page types the following properties are implemented: HorizontalSpacing, VerticalSpacing, ItemsAndTitlesAlign, ChildItemsHorizontalAlign, and ChildItemsVerticalAlign.

For managed form fields of field, table, decoration, group, button, and addition types, the HorizontalAlignInGroup and VerticalAlignInGroup properties are implemented. For managed form item addition extensions for search string, search control, and view status, the AutoMaxWidth and MaxWidth properties are implemented. For managed form groups, the ThroughAlign property is implemented. For the VerticalFormScroll system enumeration, the UseWithoutStretch value is implemented. For managed form group extension for a usual group, the United property is implemented. For managed form group extension for a page, the VerticalScrollOnReduceSize property is implemented.

This change is not implemented in 8.3.6 compatibility mode.

The HorizontalStretch and VerticalStretch properties are implemented for the following objects: managed form extensions for graphical schema field and HTML document field, and managed form buttons. For managed form item addition extension for search control, the HorizontalStretch property is implemented.

The ChildFormItemsWidth property of form, page, and usual group objects is obsolete and only supported in version 8.3.6 compatibility mode. In configurations that do not use compatibility mode, this property is ignored.

A different algorithm was used for arranging managed form items. In managed forms, automatic item arrangement is revised. New arrangement options are available. Several known managed form issues are eliminated.
Web services and HTTP services.
If a configuration includes HTTP services, saving a configuration with compatibility mode lower than Version 8.3.5 is not allowed. Saving configurations was performed without checking the correspondence between configuration compatibility mode and the availability of HTTP services in the configuration. Eliminated unexpected system behavior.
Common objects.
Synchronous call usage mode for extensions and add-ins configuration property value is taken into account by the following methods:
  • Read() method of theTextDocument object
  • Write() method of theTextDocument, SpreadsheetDocument, FormattedDocument, and GraphicalSchema objects
  • WriteFileForPrinting() method of the RepresentableDocumentBatch object
The Synchronous call usage mode for extensions and add-ins configuration property was ignored by the listed methods. Eliminated unexpected system behavior.
Server cluster.
The following background job names are used for specifying requirements of functionality purposes:
  • Scheduled job: BackgroundJob.ScheduledJob.<Metadata object name>.
  • Input by string: BackgroundJob.InputByString.<Full metadata object name>.
  • Report: BackgroundJob.GenerateReport.<Full report metadata object name>.
  • External report: BackgroundJob.GenerateReport.<Full report metadata object name>.
  • Search in list: BackgroundJob.DynamicListSearch.<Full form name>.<Name of form table linked to the list>.
  • Background restructuring: SystemBackgroundJob.DBConfigUpdate.

This change is not implemented in 8.3.6 compatibility mode.

The following background job names were used for specifying requirements of functionality purposes:

  • Background job: BackgroundJob.CommonModule.<Module name>.<Method name>.
  • Input by string: BackgroundJob.SystemBackgroundJob.
  • Report: BackgroundJob.Report.
  • External report: BackgroundJob.Report.
  • Search in list: BackgroundJob.SystemBackgroundJob.
  • Background restructuring: SystemBackgroundJob.
Background job names comply with the internal platform requirements, Background job names are more precise.
Queries.
The ValueType() query language function returns UNDEFINED when UNDEFINED is passed as the function parameter.

This change is not implemented in 8.3.6 compatibility mode.

The ValueType() query language function returned NULL when UNDEFINED was passed as the function parameter. Eliminated unexpected system behavior.
Server cluster.
You can restrict access to cryptography features using security profiles.

For ISecurityProfile object, the CryptographyAllowed property is implemented (programmed administration of server clusters using COM objects).

For ISecurityProfile object, the getCryptographyAllowed() and setCryptographyAllowed() methods are implemented (Java server administration interface).

For the server cluster command-line utility (rac) the crypto parameter for the profile command is implemented.

This change is not implemented in 8.3.6 compatibility mode.

The option to restrict access to cryptography features using security profiles was not provided. Extended security profile capabilities.
Access rights.
The access rights check for document journal graph attributes performed using the AccessRight() method with User/Role parameter specified takes into account the availability of all objects included in the journal graph content.

The AccessRight() result is cached by the platform, which is similar to caching reusable return values.

This change is not implemented in 8.3.6 compatibility mode.

The access rights check for document journal graph attributes performed using the AccessRight() method with User/Role parameter specified did not take into account the availability of all objects included in the journal graph content.

The AccessRight() result was not cached by the platform.

Eliminated unexpected system behavior.

Improved performance of access rights check for applied solutions with a large number of roles, and for file mode infobases on low-performance computers. This improves the performance of form opening in the listed scenarios.

Localization.
The option to specify the first day of the week is implemented. It can be accessed in Designer (on the Administration menu, click Regional infobase settings). When you create an infobase using platform version 8.3.7 or later without compatibility mode set, the first day of the week value is set to Auto. It is defined based on the Language (Country) property in regional infobase settings.

The choice of the first day of the week affects the following features:

  • 1C:Enterprise script methods: BegOfWeek(), EndOfWeek(), WeekOfYear()
  • Query language functions: BeginOfPeriod(), EndOfPeriod(), Week()
  • Data composition system functions: BeginOfPeriod(), EndOfPeriod(), Week(), and functions of nested fields of Date type: BegOfWeek, EndOfWeek, WeekOfYear
  • Scheduled job schedules
  • Balance virtual tables and balance and turnover virtual tables of accumulation registers
  • Balance virtual tables and balance and turnover virtual tables of accounting registers

This change is not implemented in 8.3.6 compatibility mode.

The first day of the week was always Monday. Better usability in countries where the first day of the week in not Monday.
Spreadsheet documents.
You can edit multilingual spreadsheet documents in managed forms, provided that these documents are templates. The list of languages is obtained directly from a template.

In managed forms, spreadsheet documents are edited and displayed using the language specified in the LanguageCode spreadsheet document property. Strings in other languages are never changed.

The SpreadsheetDocument.Template property is implemented.

This change is not implemented in 8.3.6 compatibility mode.

The FillPropertyValues() method never copies the Template property (regardless of the compatibility mode).

In managed forms, spreadsheet documents were always edited using the current language.

When the platform displayed a spreadsheet document:

  • The thin client did not use the LanguageCode property.
  • The web client used the LanguageCode property.

When spreadsheet document text was edited using 1C:Enterprise script, strings in the current language were written and strings in other languages were lost.

You can edit multilingual spreadsheet documents in 1C:Enterprise mode.
Applied objects.
When the Presentation field of the TasksByPerformer virtual table is generated, the fact that the presentation of the corresponding Task object can be redefined is taken into account.

This change is not implemented in 8.3.6 compatibility mode.

When the Presentation field of the TasksByPerformer virtual table was generated, the fact that the presentation of the corresponding Task object could be redefined was not taken into account. The default presentation was always used instead. Eliminated unexpected system behavior.
Queries.
The query object model is improved.

The Find() method is implemented for the following objects: QuerySchemaIndexExpressions, QuerySchemaExpressions, QuerySchemaOrderExpressions, QuerySchemaAvailableFields, QuerySchemaAvailableTableParameters, QuerySchemaTableParameters, QuerySchemaFields, QuerySchemaColumns, QuerySchemaTableForUpdate, and QuerySchemaAvailableTables. The FindByName() and FindByAlias() methods are implemented for the following objects: QuerySchemaQuerySourceJoins and QuerySchemaSources. The FindByExpression() method is implemented for the following objects: QuerySchemaTotalCalculationFields and QuerySchemaTotalExpressions. The QuerySchemaTotalCalculationFields.FindByColumnName() method is implemented. The QuerySchemaTotalExpressions.FindByField() method is implemented. The QuerySchemaSources.GetRootSources() method is implemented.

New Add() method variant is implemented for the following objects: QuerySchemaOrderExpressions, QuerySchemaQuerySourceJoins, QuerySchemaTablesForUpdate, and QuerySchemaTotalExpressions.

For the QuerySchemaFields.Add() method the optional Column parameter is implemented.

The SourceAlias parameter of QuerySchemaQuerySourceJoins.Add() method can have values of the following types: String and QuerySchemaSource.

The QuerySchemaTotalExpressions.Add() method parameter can have values of the following types: String, QuerySchemaColumn, and QuerySchemaExpression.

The behavior of QuerySchemaTotalCalculationFields.Add() method is modified for scenarios when its parameter has a value of String type.

The QuerySchemaNestedTable.Fields property has QuerySchemaFields type. Passing a text containing a batch query or a table drop query to the QuerySchemaSelectQuery.SetQueryText() method raises an exception. The "For a nested table" variant of the QuerySchemaExpressions.Add() method is declared obsolete. This change is not implemented in 8.3.6 compatibility mode.

These features were not provided.

The QuerySchemaNestedTable.Fields property had QuerySchemaExpressions type.

If a text containing a batch query was passed to the QuerySchemaSelectQuery.SetQueryText() method, the first query in the batch was used. If a text containing a table drop query was passed to the QuerySchemaSelectQuery.SetQueryText() method, an empty query was created.

The "For a nested table" variant of the QuerySchemaExpressions.Add() method was available.

Improved usability of query object model.
Data composition system.
In the data composition system, the data set link type is replaced with inner link if a filter containing only fields from the data set being linked is applied. Conditions that do not include inner links are added to the RecordsFilter property of groupings that contain at least one data set with fields used in these conditions.

This change is not implemented in 8.3.6 compatibility mode.

In the data composition system, the data set link type was always set to inner link when a filter included a linked data set field. Eliminated unexpected system behavior when fields from multiple data sets were used in a filter.
Navigation links.
The GotoURL method parameter value is not decoded prior to passing it to the operating system (the original link is passed).

This change is not implemented in 8.3.6 compatibility mode.

The GotoURL method parameter value might be decoded prior to passing it to the operating system:
  • In 8.3.4 or earlier compatibility mode it was not decoded (the original link was passed).
  • In 8.3.5 and 8.3.6 compatibility modes it was decoded.
Eliminated unexpected system behavior.
Configuration extensions.
Writing an extension to an infobase is available in the following cases: the session that performs the writing is not running in the safe mode, or the session security profile allows this operation.

When attaching an extension, the platform does not check whether the extension fits the session security profile restrictions.

Writing an extension to an infobase was only available if the session was running in the safe mode,

When attaching an extension, the platform checked whether the extension fit the session security profile restrictions.

Security profiles process extensions in the same way as they process external reports and data processors.
Applied objects.
If a new object number (this includes document, catalog item, chart of characteristic types item, business process, and task numbers) is issued inside a transaction, it is reused even if the autonumbering mode is set to Do not Release Automatically, including scenarios where the object is not written inside the transaction.

The Do not Release Automatically autonumbering mode only affects the numbers issued outside transactions. In other words, if a number is issued outside a transaction and it is not used (because the object is not written), it is not reused in the Do not Release Automatically mode, and it is reused in the Release Automatically mode.

If a new object number (this included document, catalog item, chart of characteristic types item, business process, and task numbers) was issued inside a transaction and the object was not written, that number was not reused in the Do not Release Automatically mode. Reduced number of unused object numbers in scenarios where object numbers are issued in transactions and those objects are not written.
Client application.
Data display.
If you want to use fonts other than Auto in your applied solutions, it is recommended that you select from the following fonts:
  • 1C:Enterprise style fonts:
    • Small text font
    • Normal text font
    • Large text font
    • Very large text font
  • Vector fonts from the "MS Core Fonts" collection:
    • Andale Mono
    • Arial
    • Arial Black
    • Comic Sans MS
    • Courier New
    • Georgia
    • Impact
    • Times New Roman
    • Trebuchet MS
    • Verdana
    • Webdings

If you use a font that is not listed here, from items might not be displayed correctly in some modes (including client applications).

The list of recommended fonts was not available. A list of fonts recommended for use to ensure uniform applied solution appearance across environments is now available.
Managed forms.
The algorithm that calculates the font size based on the font properties specified for a fortm item is changed. This might lead to the change of the font scale for the form items that have the Scale part of the Font property set to a nondefalut value.

This change is not implemented in 8.3.6 compatibility mode.

In some cases the Scale part of the Font property of form items was ignored, so that the text displayed on a form item had the default size. Eliminated unexpected system behavior.

In some cases the font size of form items might change.


Comments
0
Add comment