Changes that require modification of configuration and administrative settings




FunctionalityAfterBeforeResult of changes
Dynamic list. Dynamic lists cannot be ordered by extra dimension fields of accounting registers. An attempt to order a dynamic list by these fields (for example, by clicking the column header) does not result in a server call.

This change is not implemented in 8.3.4 compatibility mode.

An attempt to order a dynamic list by extra dimension fields of accounting registers generated an error message and initiated a server call, which did not retrieve any data.Dynamic lists do not allow ordering that does not make sense, therefore the system behaves as expected (from the user’s point of view).
Applied objects. An attempt to set a value to ThisObject or AdditionalProperties attribute of a CatalogObject, ExchangePlanObject, or ChartOfCharacteristicTypesObject raises an exception.

An attempt to set a value to the DataExchange attribute of a CatalogObject or ChartOfCharacteristicTypesObject raises an exception.

This change is not implemented in 8.3.4 compatibility mode.

An attempt to set a value to ThisObject or AdditionalProperties attribute of a CatalogObjectExchangePlanObject, or ChartOfCharacteristicTypesObject did not raise an exception, and the value was not set.

An attempt to set a value to the DataExchange attribute of a CatalogObject or ChartOfCharacteristicTypesObject did not raise an exception, and the value was not set.

Unified processing of the specified properties: an attempt to set a value for a read-only attribute raises an exception.

Client application. Server cluster. If the client and server application versions do not match, the search for client application distribution kit is performed in the following order:
  • Search in the 1C:Enterprise installation directory (the InstalledLocation property in 1cestart.cfg and 1cescmn.cfg files)
  • Search in the directories specified as locations for distribution files of new versions (the DistributiveLocation property in 1cestart.cfg and 1cescmn.cfg files, and the CommonCfgLocation property in the 1cestart.cfg file)
  • Search by the URL that is returned in the server exception about the mismatch of client and server application versions (the PublishDistributiveLocation parameter in the conf.cfg file and the pubdst attribute of the ws tag in the default.vrd file)
  • Search using Internet services for getting the client application distribution kit
If the client and server application versions did not match, the search for client application distribution kit was performed in the following order:
  • Search in the 1C:Enterprise installation directory (the InstalledLocation property in 1cestart.cfg and 1cescmn.cfg files)
  • Search in the directories specified as locations for distribution files of new versions (the DistributiveLocation property in 1cestart.cfg and 1cescmn.cfg files, and the CommonCfgLocation property in the 1cestart.cfg file)
  • Search by the URL, that is returned in the server exception about the mismatch of client and server application versions (the PublishDistributiveLocation parameter in the conf.cfg file and the pubdst attribute of the ws tag in the default.vrd file)
  • Search using Internet services for getting the client application distribution kit
Search for updates behaves as expected: search in the local network precedes search using Internet services.
Common attributes / Data separation. The SetPredefinedDataUpdate() and SetInfoBasePredefinedDataUpdate() methods can only be executed in sessions that do not have any separators (in addition to the fact that they require the Administration right).

This change is not implemented in 8.3.4 compatibility mode.

The SetPredefinedDataUpdate() and SetInfoBasePredefinedDataUpdate() methods could be executed in any session, provided that the user had the Administration right.

Users cannot change the infobase predefined data update mode if they do not have the required rights.
Navigation links. Client application.

The ReferencesArray parameter of the GetURLsPresentations() function is mandatory. The return value of this function is always an array. For input array items whose presentations cannot be obtained, the matching output array items contain UNDEFINED.

This change is not implemented in 8.3.4 compatibility mode.

The ReferencesArray parameter of the GetURLsPresentations() function was not mandatory. In cases when a parameter value presentation could not be obtained by its value, uniform system behavior across all client applications was not guaranteed.The GetURLsPresentations() function is uniform across all client applications.
Web client. In the web client, performing the Execute() operator ends in exception.In the web client, calling the Execute() operator was ignored and no diagnostic messages were displayed.Implemented applied solution error diagnostics (for calling the Execute() operator in the web client).
Spreadsheet document. In the SpreadsheetDocumentRange object, the TopBorderRightBorderBottomBorder, and LeftBorder properties contain the UNDEFINED value if the corresponding border is not the same for all cells.

This change is not implemented in 8.3.4 compatibility mode.

In the SpreadsheetDocumentRange object, values of the TopBorderRightBorderBottomBorder, and LeftBorder properties were retrieved from the properties of a random cell within the specified rangeEliminated unexpected system behavior.
Data composition system. In data composition system batch queries, when a temporary table is created, if the table fields are not used by the next queries of the batch and the table is not included in required joins, the query that creates the table is removed from the batch.

This change is not implemented in 8.3.4 compatibility mode

In data composition system batch queries, temporary tables were deleted from the batch if the table fields were not used by the next queries of the batch and the table was not used in other queries of the batch that also created temporary tables.Improved management of temporary tables in the data composition system.
Data exchange. Information registers. Changes in information registers that have dimensions of UUID type that are included in the main filter are recorded correctly.

In tables that store the register change records, fields describing dimensions of UUID type have UUID type.

Changes in information registers that had dimensions of UUID type were recorded incorrectly.

In tables that stored the register change records, fields describing dimensions of UUID type had BinaryData type.

Eliminated unexpected system behavior. In exchange plans containing information registers with dimensions of UUID type that are included in the main filter, registering all dimensions is required.
1C:Enteprise script. Common objects. In the thin client, the following types are not available: ValueTableRow, ValueTableColumnCollection, ValueTableColumn, CollectionIndexes, CollectionIndex, ValueTreeRowCollection, ValueTreeRow, ValueTreeColumnCollection, and ValueTreeColumn.

This change is not implemented in 8.3.4 compatibility mode.

In the thin client, the following types were available: ValueTableRow, ValueTableColumnCollection, ValueTableColumn, CollectionIndexes, CollectionIndex, ValueTreeRowCollection, ValueTreeRow, ValueTreeColumnCollection, and ValueTreeColumn.Eliminated unexpected system behavior.
Managed form. In managed form text boxes, the TextEditEnd event handler is not called when the spin buttons are clicked.

This change is not implemented in 8.3.4 compatibility mode.

In managed form text boxes, the TextEditEnd event handler was called when spin buttons were clicked.

Eliminated unexpected system behavior.
Applied objects. Managed form. When an object is created from a dynamic list filtered by an attribute of Date type, object attributes of that type are filled from the filling data.

This change is not implemented in 8.3.4 compatibility mode.

When an object was created from a dynamic list filtered by an attribute of Date type, object attributes of that type were not filled from the filling data.

For such attributes, the standard FillingValues parameter of the new item form contained values of the StandardBeginningDate type passed from the dynamic list filters.

Eliminated unexpected system behavior.
Managed form. In managed form text boxes, if editing a string with an input mask results in a string that matches an empty input mask, an empty string is recorded to the form attribute displayed in the text box. If the string has fixed length, the string consists of spaces.

This change is not implemented in 8.3.4 compatibility mode.

In managed form text boxes, if editing a string with an input mask resulted in a string that matched an empty input mask, a string that contained spaces and fixed input mask characters was recorded to the form attribute displayed in the text box.When a text box is cleared, an empty string is recorded to the linked attribute regardless of the input mask availability. In text boxes linked to attributes of Text type with the input mask set, the automatic "incomplete" mark is displayed correctly.
Managed form. In managed form text boxes, the procedure of generating a drop-down list during input by string is modified. The procedure is described in the documentation.

This change is not implemented in 8.3.4 compatibility mode.

In managed form text boxes, the following procedure was used for generating a choice list during input by string:
  • Search by beginning of the string is performed and the first 10 results are added to the list.
  • If the list contains less than 10 items, search by substring is performed and its results are added to the list until it contains 10 items.
  • If the list still contains less than 10 items, results of search by other fields available for search during input by string are added to the list.
In managed form text boxes, eliminated issues in the procedure of drop-down list generation when search is performed both by beginning of string and by substring.
Managed form. Getting the list of desktop forms is implemented. For the Forms in tabs and Taxi interface modes, the ClientApplicationWindows collection contains a separate item that describes the start page (desktop). The Content property of this item contains the list of forms available on the start page (desktop).

For the Forms in separate windows interface mode, the ClientApplicationWindows collection contains ClientApplicationWindow objects that describe forms located on the desktop.

For the ClientApplicationWindow object, the StartPage and Content properties are implemented.

The GetContent() method of the ClientApplicationWindow is supported for compatibility purposes.

This change is not implemented in 8.3.4 compatibility mode.

This feature was not provided.

For the Forms in tabs and Taxi interface modes, the ClientApplicationWindows collection did not contain objects describing the start page (desktop).

For the Forms in separate windows interface mode, the ClientApplicationWindows collection did not contain objects describing forms opened on the desktop.

Developers can access forms located on the start page (desktop) using 1C:Enterprise script.
Automated testing. For subordinate objects of the TestedApplication object, the TestedClientApplicationWindow object is implemented. The object describes the start page (desktop).

Forms (objects of TestedForm type) included in the start page (desktop) content are subordinate to the TestedClientApplicationWindow object that describes the start page (desktop).

For the TestedClientApplicationWindow object, the StartPage property is implemented. 

This change is not implemented in 8.3.4 compatibility mode.

The TestedClientApplicationWindow object that described the start page (desktop) was not included in the subordinate objects of the TestedApplication object. 

Forms included in the start page (desktop) were subordinate to the TestedClientApplicationWindow object that had its IsMain property set to True.

You can access forms located on the start page (desktop) from 1C:Enteprise script using automated testing tools.
Common attributes / Data separation. Data exchange. An exception that does not cause application termination occurs when predefined data is registered for an unseparated configuration object in a separated exchange plan from a session that uses all separators.An exception that caused application termination occurred when predefined data was registered for an unseparated configuration object in a separated exchange plan from a session that used all separators.Eliminated issues that resulted in application termination.
Common attributes / Data separation. Data exchange. If a configuration object does not use all separators where it is included, calling the InitializePredefinedData() method does not initialize predefined data items for this object.

This change is not implemented in 8.3.4 compatibility mode.

If a configuration object did not use all separators where it was included, calling the InitializePredefinedData() method caused an error.The InitializePredefinedData() method can be used in any session, not only when all separators are used.
Operating with DBMS. Data composition system. Dynamic list. For the LIKE query language operation, search in dynamic lists, and filter in the data composition system, the search template length is limited. The limit depends on the DBMS type. If the template length exceeds the limit, an error is generated, which does not lead to 1C:Enterprise shutdown.For the LIKE query language operation, search in dynamic lists, and filter in the data composition system, if the search template exceeded 1024 characters, this could cause a DBMS error and 1C:Enterprise shutdown.1C:Enterprise is not shut down when a search template is too long.
Applied objects. The value of the IsFolder field is correctly passed to the PresentationGetProcessing handler.

This change is not implemented in 8.3.4 compatibility mode.

The value of the IsFolder field passed to the PresentationGetProcessing handler was inverted.Eliminated unexpected system behavior.
Managed form. The managed form visibility setting is stored in the system setting storage with a purpose use key. The object key is generated as follows: <Full form name>/<Purpose use key>/FormSettings.

This change is not implemented in 8.3.4 compatibility mode.

The managed form visibility setting was stored in the system setting storage without a purpose use key. The object key was generated as follows: <Full form name>/FormSettings.You can use a single form for different use purposes, with custom display settings for each use purpose.
Data composition system. Data composition system expressions are calculated in the safe mode.

This change is not implemented in 8.3.4 compatibility mode.

The safe mode was not used when data composition system expressions were calculated.

Improved security of executing reports that might use insecure methods from common modules.
Managed form. In managed form tables, you can start dragging from an available table cell only.

This change is not implemented in 8.3.4 compatibility mode.

In managed form tables, dragging from any table cell was allowed. When an attempt to drag an unavailable cell was made, the currently selected cell was dragged instead.Eliminated unexpected system behavior.
Data composition system. The Text parameter of conditional appearance that is specified for the Fields header usage area is applied to grouping field headers.

This change is not implemented in 8.3.4 compatibility mode.

The Text parameter of conditional apperance was never applied to grouping field headers.Eliminated unexpected system behavior.
Data composition system. The data composition template generator always generates the VerticalLevel property for nested reports. The parent report level is added to the value of this property.

This change is not implemented in 8.3.4 compatibility mode.

Parent report groupings were not taken into account when nested reports were displayed.

Parent report groupings affect nested reports: nested reports are displayed at the same grouping level as the parent report.
Managed form. For managed form fields, the PeriodField field type is implemented. It is intended for simplifying selection of periods of several full months.

For managed form field extensions for calendar fields, the Border property is implemented. It specifies border parameters for the calendar field.

The dialog box that was used in the following scenarios is modified:

  • Period selection for dynamic lists
  • Standard period selection for text boxes that display values of StandardPeriod type
  • The StandardPeriodEditDialog object dialog box

This change is not implemented in 8.3.4 compatibility mode.

For managed form fields, the PeriodField field type was not available.

For managed form field extensions for calendar fields, the Border property was not available.

A different dialog box was used in the following scenarios:

  • Period selection for dynamic lists
  • Standard period selection for text boxes that display values of StandardPeriod type
  • The StandardPeriodEditDialog object dialog box

If the period variant was not custom, a drop-down list containing available options was opened in the input field.

The period selection dialog box is improved.
Managed form. In managed form tables, if a row is added because editing the previous row is finished or by pressing the Down Arrow, and then the row is neither edited from 1C:Enterprise script nor edited interactively, the new row is automatically deleted once the selection is moved away from it.

This change is not implemented in 8.3.4 compatibility mode.

In managed form tables, if a row was added because editing the previous row was finished or by pressing the Down Arrow, and then the row was not edited interactively, the new row was automatically deleted once the selection was moved away from it.Eliminated unexpected system behavior.
Managed form. While a text box choice history is being filled, the check for deleted items is performed. A value presentation is removed from the list if its data was deleted in the current session or its data was deleted in another session but the presentation of deleted data was obtained in this session. If a value is deleted after the choice history is generated, when a user attempts to select this value, a warning is displayed, the value is not selected, and the item is removed from the history list.

The feature is implemented for thin and web clients.

Deleted values were displayed in text box choice history as Object not found items.References to objects that are no longer available for selection are removed from the choice history.
Managed form. In managed forms, the length of the PurposeUseKey property value is limited to 128 characters. An attempt to set a value longer than 128 characters or open a form with this property value longer than 128 characters ends with a exception.

This change is not implemented in 8.3.4 compatibility mode.

In managed forms, the length of the PurposeUseKey property value was not limited.

Simplified diagnostics of issues related to PurposeUseKey value being too long. 
Data access restriction. For each configuration object that is included in separator content and has tabular sections, a data access restriction check is performed (after writing) if the access restriction conditions include attributes from the object tabular section.

As a result, a message about insufficient access rights might be displayed in situations where it was not displayed earlier.

For configuration objects that were included in separator content and had tabular sections, data access restriction checks were not performed (after writing) if the access restriction conditions included attributes from the object tabular sections.Eliminated unexpected system behavior.

Table of contents


Comments
0
Add comment