Changes that affect system behavior




FunctionalityAfterBeforeResult of changes
Defined types.

The list of types that can be included in defined types is significantly extended.

You can use defined types in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators.

The algorithm of the configuration check for correct usage of defined types is modified: a defined type is considered valid (in each usage instance) if all types that form the defined type are valid when the check is performed.

The configuration check algorithm is not modified in 8.3.4 compatibility mode.

The list of types that could be included in defined types was significantly shorter.

The configuration check was performed as follows: check whether the defined type only includes allowed types, and check whether the defined type is not included in the following objects: common commands, calculation registers, event subscriptions, external data sources, and common attributes that are used as separators.

New defined type usage options in applied solution development. Particularly, integration of applied solutions with third-party subsystems is now simpler.
Development tools. The order of standard attributes in the standard attributes window and in the role settings is modified.

The form wizard allows adding predefined data name fields to forms.

The list of standard attributes in the standard attributes window and in the role settings was not ordered.

The form wizard did not allow adding predefined data name fields to forms.

Display of standard attributes is uniform with other system features.
Client application. For text documents, the Save as command now saves the document encoding, provided that one of the following encodings is used: ANSI, OEM, UTF-8, or UTF-16. Otherwise, the UTF-8 encoding is set.

Closing the Save as dialog box by clicking Cancel does not modify the encoding of the open document.

This change is not implemented in 8.3.4 compatibility mode.

For text documents, the Save as command set the UTF-8 encoding for the document being saved, regardless of the encoding that was used when the document was opened.

Closing the Save as dialog box by clicking Cancel set UTF-8 encoding for the open document.

Eliminated unexpected system behavior.
Managed form. Dynamic list. In the Customize form dialog box, the DataVersion field cannot be added to a form.In the Customize form dialog box, the DataVersion field could be added to a form.Eliminated unexpected system behavior.
Background and scheduled jobs. At the start of a background job, the SessionParametersSetting event handler is run after the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on).At the start of a background job, the SessionParametersSetting event handler was run prior to the execution of service actions (recording to the event log, setting connection parameters for external data sources, and so on).Eliminated unexpected system behavior.
Common attributes / Data separation. Information registers. Accumulation registers. Accounting registers. Calculation registers. The configuration check and database configuration update include the check whether registers affecting a sequence are included in the same separator content as the documents included in the sequence.

If a register affecting a sequence is included in separator content and a document included in a sequence is not included in the content of this separator, the separator is ignored when sequence boundaries are updated in 1C:Enterprise mode.

The check for correspondence between separators included in a document sequence and registers affecting this sequence was not performed.Eliminated unexpected system behavior.
Temporary storage.The volume of data transferred between the client and the server cannot exceed 4 GB (in the serialized form) in the following cases:
  • Setting a session parameter
  • Single call of the PutToTempStorage() method
  • Single call of the PutFile() or PutFiles() method

An attempt to transfer more than 4GB leads to an unrecoverable error.

During an attempt to transfer more than 4GB of data (in serialized form) to the server, the client application stopped responding.Eliminated unexpected system behavior.
Internet-enabled functionality. The cURL library is updated to version 7.32. It supports new options, such as downloading files with Cyrillic names from FTP servers.The cURL library version 7.18.2 was used.Resolved some issues of the previous library version.
Working with XML, XDTO. If an error related to an attempt to write an invalid character to an XML object occurs at the server side, an unrecoverable error is not generated at the client side, and the user is not prompted to restart the client application.

The error can be handled using the Try...Except syntax.

If an error related to an attempt to write an invalid character to an XML object occurred at the server side, the unrecoverable error was generated at the client side, and the user was prompted to restart the client application.Eliminated unexpected system behavior.
Working with XML, XDTO. If the FindDisallowedXMLCharacters() method finds an incomplete surrogate Unicode pair, it returns the position of the first character of the incomplete pair.If the FindDisallowedXMLCharacters() method found an incomplete surrogate Unicode pair, it returned the position of the character that followed the first character of the incomplete pair.Eliminated unexpected system behavior.
Managed form.

In a text box that is in the "choice from the list" mode and displays an empty reference, clicking the Cancel button is ignored.

In the text box that was in the "choice from the list" mode and displayed an empty reference, clicking the Cancel button displayed a dialog box with Undefined text.Eliminated unexpected system behavior.
Navigation links. When a navigation link is followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation link are ignored. This feature is implemented in the following scenarios:
  • The GotoURL() script method
  • Following a navigation link from the Go to link dialog box (including the scenario when the link is pasted from the clipboard)
  • Adding a link to Favorites from the Go to link dialog box
When navigation links were followed, white spaces (spaces, line feeds, and so on) in the beginning and in the end of the navigation links were ignored. Users had to delete these characters manually.Improved management of navigation links.
Working with XML, XDTO. Web services. When string values are read using the XMLReader object or obtained using a web service, line feed characters keep their original format (they are not converted).

This change is not implemented in 8.3.4 compatibility mode.

When string values were read using the XMLReader object or obtained using a web service, the following replacements were made:
  • Combinations of line feed characters 0x0D+0x0A (CR+LF) and 0x0D (CR) were replaced with 0x0A (LF).
  • Combination of characters 0x0A+0x0D (LF+CR) was replaced with 0x0A+0x0A (LF+LF).

Eliminated unexpected system behavior.
Spreadsheet document. Working with XML, XDTO. Settings of text boxes located in spreadsheet documents can now be serialized to XDTO. A spreadsheet document deserialized from XDTO is equivalent to its source.

During XDTO serialization of spreadsheet documents and the following deserialization, text box settings were lost.

Settings of text boxes located in spreadsheet documents are saved after dumping/loading configuration to/from XML files.
Development tools.
  • In the Evaluate expression dialog box and in the Immediate window, expressions are not calculated twice in the following cases:
  • Opening a value that has properties
  • Viewing a property as a collection of values in a separate window
  • Viewing property values in a separate window intended for viewing a collection
  • Viewing a string value in a separate window
In the Evaluate expression dialog box and in the Immediate window, expressions were calculated twice in the following cases:
  • Opening a value that has properties
  • Viewing a property as a collection of values in a separate window
  • Viewing property values in a separate window intended for viewing a collection
  • Viewing a string value in a separate window
Eliminated the issue that introduced inaccuracies to the calculated expression result because the expression could only be calculated once (at the current debugging step).
Configuration repository.

You can perform selective comparison of form modules without building a form comparison report. The Form (module) command is added to the following context menus: Perform selective comparison with the repository object, Perform selective comparison with the configuration object, and Perform selective comparison of object versions.

During selective comparison of forms, two comparisons were performed: the comparison of form modules and the comparison of forms. Two reports were displayed as a result of comparison.

Improved usability of selective comparison. Comparison of form modules is now a separate command.

Data composition system. In data composition system, the automatically generated title of a field linked to data retrieved using "." (dot) from a Ref field of a tabular section contains the field presentation only. In particular, a field related to the TabularSection.Ref.Number attribute will have the Number title.

This change is not implemented in 8.3.4 compatibility mode.

In data composition system, the automatically generated title of a field linked to data retrieved using "." (dot) from a Ref field of a tabular section contained the Ref word and a presentation of the data attribute retrieved using "." (dot).Improved appearance of reports.
Managed form. Pessimistic lock of data described by the main form attribute is performed for the following actions in text boxes:
  • Clicking the drop-down list button
  • Attempting to create an item from the drop-down list
  • Attempting to open a choice list
  • Starting text input

If the lock cannot be set, the action is not performed.

Pessimistic data lock was set for the following actions in text boxes:
  • Attempting to open a choice list
  • Starting text input
Pessimistic data lock is set for all actions that change text box contents.
Working with XML, XDTO. Development tools. In the "dump configuration to files" feature, XML file format is changed for the following configuration parts: managed forms, graphical schema items, geographical schemas, functional option content, and field lists. Tag names now match the names used in 1C:Enterprise script, the XML element name spelling is unified. The dump format is more compact and clear. The properties filled with default values are not dumped.

Managed forms dumped using the previous platform versions cannot be loaded by the latest platform version.

In the "dump configuration to files" feature, XML files that stored managed forms, graphical schemas, geographical schemas, functional option content, and field lists had a different format.XML files that store configuration data are more compact and better structured
Chart of accounts.

Accounting registers. Data exchange.

While a chart of accounts item is being written with DataExchange.Load property set to True, new extra dimension types are checked for uniqueness. The unique ones are added to the table of extra dimension values, and the nonunique values are not added, which eliminates possible errors.If a chart of accounts item was being written with DataExchange.Load property set to True, the check for uniqueness of extra dimensions was not performed. This could cause errors while items were being added to the table of extra dimension values.The order of loading chart of accounts data and data of linked accounting registers does not matter.
Development tools. In the property palette, the Sort alphabetically command sorts properties by presentation (if displaying property names is disabled) or by name (if displaying property names is enabled). If a property does not have a name, the sorting is always performed by text presentation.In the property palette, the Sort alphabetically command sorted properties by presentation.The sorting command behavior depends on object property presentations.
Data composition system. In the data composition system, the conditional appearance with Fields header usage area is applied to an area of a vertical template that contains names of displayed fields.

The conditional appearance with Group usage area is applied to an aria of vertical template that contains values of displayed fields.

This change is not implemented in 8.3.4 compatibility mode.

In the data composition syste, the conditional appearance with Group usage area was applied to all areas of a vertical template.Improved usability of data composition system conditional appearance.
Thick client.If more than two parameters are passed to the Insert() method of the TableBoxColumns object, an error is generated.

This change is not implemented in 8.3.4 compatibility mode.

Up to five parameters could be passed to the Insert() method of the TableBoxColumns object, while only two parameters were used. No errors were generated.Eliminated unexpected system behavior.
Event log. Modified format for storing the event log. The event log is stored in an SQLite database. The event log file has .lgd extension. 

The event log location is not changed. The SQLite event log format is the default format for new infobases. The performance of event log data calls is improved.

Existing event logs can be converted to a new format. Conversion back to the legacy format is not supported.

The CopyEventLog() and ClearEventLog() methods are implemented.

The event log stores time in UTC format.

The event log had text format.Increased performance when accessing event log data. Improved event log reliability.
Spreadsheet document. When a spreadsheet document is saved to a PDF file, a single document copy is saved. The Copies spreadsheet document property is ignored.

To include multiple copies into the PDF file, use the WriteFileForPrinting() method of the RepresentableDocumentBatch object.

This change is not implemented in 8.3.4 compatibility mode.

When a spreadsheet document was saved to a PDF file, the file contained the number of document copies specified in the Copies property.Eliminated unexpected system behavior.
Client application. Development tools. In Designer and thick client, customization of the search result selection background is available.In Designer and thick client, the search result background color could not be customized.Users can specify search result selection background color that fits their text editor settings.
Data exchange. Common attributes / Data separation. In a session that does not use any separators, while session changes are being registered, the Update right is not required for tables of objects being registered.

For sessions that use separators, the following features are implemented:

  • Changes can be registered for an empty record set that is subordinate to a recorder. If any of the separators required for the record set are not used in a session, the separator values are obtained from the corresponding recorder fields.
  • If the full set of separator values cannot be obtained using a recorder available in the memory, an error is generated and the change registration is stopped.
In a session that did not use any separators, while session changes were being registered, the Update right was required for tables of objects being registered.

For sessions that used separators, registering changes for empty record sets that were subordinate to recorders was not available.

In separated mode, changes are registered correctly.
Common attributes / Data separation. Working with database. New options for FindMarkedForDeletion(), FindByRef(), and DeleteObjects() methods:
  • You can specify data areas that will be searched for references or where objects will be deleted.
  • You can include configuration objects to (or exclude configuration objects from) search or deletion.

For value tables that are returned by the FindByRef() and DeleteObjects() methods, a new column is implemented. It contains separator values that define the data area where the found object or the object that prevents deletion of another object is located.

The DeleteObjects() method returns a value of Number type, which stores the number of deleted objects.

This change is not implemented in 8.3.4 compatibility mode.

The search for references, search for objects marked for deletion, and deletion of marked objects were performed only in data available in the current session with the current separator values. Including individual configuration objects to (or excluding configuration objects from) search or deletion was not available.

The value tables that were returned by the FindByRef() and DeleteObjects() methods did not contain columns with separator values.

The DeleteObjects() method was a procedure.

You can customize the deletion of marked objects, especially in separated infobases. You can design more clear messages containing deletion results (total objects deleted, total objects not deleted, and so on).
Defined types. In Designer, properties palette contents for objects that have defined type are generated based on the actual type that describes the defined type.The properties palette contents for objects that had defined types were always displayed as if all of the objects had complex type, regardless of their actual types.Property customization for objects that have defined types is now similar to property customization for objects whose types are specified explicitly.
Software licensing. In the license activation dialog box, each PIN code is entered in a single text box, which includes an input mask (in all license acquisition scenarios).

During license activation by phone, each Licensing Center response line is entered in a single text box, which contains an input mask).

Pressing Tab switches between these text boxes.

The license registration page contains the descriptions of activation options for 5-, 10-, and 20-user licenses.

Extended error diagnostics during license activation is implemented.

In the license activation dialog box, each PIN code was entered in 5 text boxes (in all license acquisition scenarios).

During license activation by phone, the license activation dialog box had 5 text boxes for entering each Licensing Center response line.

Pressing Tab switched between the text boxes and response lines.

Help for various license activation methods was not available directly in the dialog box.

Some license activation error messages had complicated descriptions that might not be clear to users.

The software license activation dialog box is improved. PINs can be pasted from the clipboard.

Improved usability of entering the response from the Licensing Center during license activation by phone.

The error messages are clearer to users.

Common attributes / Data separation. In version 8.2.16 or earlier compatibility mode, configuration checks and database configuration updates include the check whether each document journal is included in contents of at least one common attribute, and if it does, the appropriate diagnostics is performed.

The configuration is not updated in this case.

In version 8.2.16 or earlier compatibility mode, the configuration check did not detect configuration errors if document journals were included in contents of common attributes, and therefore such errors did not prevent the configuration update.The system cannot become inconsistent due to the fact that in version 8.2.16 or earlier document journals could not be included in common attribute contents.
Data composition system. The GroupPlacement parameter of the data composition system does not affect the displaying of totals.

This change is not implemented in 8.3.4 compatibility mode.

Grouping totals were not displayed if the GroupPlacement data composition system parameter was set to End or None for the selected grouping.Eliminated unexpected system behavior.
Spreadsheet document. For cells that have single-line height, tooltips that do not fit a single text line are displayed as multiple text lines.

This change is not implemented in 8.3.4 compatibility mode.

For cells that had single-line height, tooltips were displayed as single text lines. If tooltip text did not fit a single line, it ended with "...."Eliminated unexpected system behavior.
Spreadsheet document. In the thin client, when a spreadsheet document is obtained from the server, empty rows located in document cells are preserved.

This change is not implemented in 8.3.4 compatibility mode.

In the thin client, when a spreadsheet document was obtained from the server, empty rows located in document cells were lost.Eliminated data loss during the transfer of spreadsheet documents from the server to the client.
Managed form. In a managed form table cell that has a drop-down list available and the Directly editing mode set, pressing Down Arrow or Up Arrow keys moves the selection to another cell and does not open the drop-down list. The drop-down list is only opened when a new row is added.

To open the drop-down list, press Ctrl+Down Arrow.

In a managed form table cell (with the Directly editing mode set), pressing Down Arrow or Up Arrow keys might open a drop-down list. This eliminated the option to add a new row by pressing Down Arrow.Eliminated unexpected system behavior.
Data composition system. When a data composition template is generated, expressions for calculating details that contain fields unavailable due to functional options are removed from predefined templates.

This change is not implemented in 8.3.4 compatibility mode.

When a data composition template was generated, details expressions were copied from the predefined templates without any modifications.During report generation, errors do not occur when templates include fields unavailable due to functional options.
Client application. In managed mode, if any connection issues or server-side issues occur, the client application allows to repeat a request, interrupt the operation, or shut down the application.If any connection issues or server-side issues occurred, users were not allowed to repeat their requests. In most cases the client application was simply shut down.

The client application is more robust against connection issues or 1C:Enterprise server issues.

Mobile application. If the interface compatibility mode is set to Taxi and then the Use purposes configuration property is set to Personal computer and Mobile device, the Interface compatibility mode property is automatically set to Taxi. Version 8.2 allowed.

If changing the Use purposes property requires modification of Modality usage mode and Interface compatibility mode configuration property values, the user is prompted to confirm the change.

Selecting the Mobile device value in the Use purposes configuration property made the following changes in configuration properties without any warnings:
  • The Interface compatibility mode property was set to Version 8.2.
  • The Modality usage mode property was set to Use.
Designer behaves as expected.
Software licensing. Users that do not have administrative rights can activate software licenses. In this scenario the license is activated for the current user.Only users with administrative rights could activate licenses.

A user without administrative rights that does not have write access to the directory where license files for all computer users are located still can activate a software license.

Predefined data.

Data exchange. Common attributes / Data separation.

When predefined data is changed, changes are only registered for items that are actually modified, added, or deleted.

When the compatibility mode is changed from Version 8.3.2 (or earlier) to Version 8.3.3 (or later), all predefined item changes are registered.

When the compatibility mode is changed from Version 8.3.3 (or later) to Version 8.3.2 (or earlier), registration of all predefined items is removed.

When changes are registered for predefined items:

  • If the configuration object where predefined items are changed and the exchange plan where the changes are registered do not have common separators, the changes are registered for all nodes of the exchange plan.
  • If the configuration object where the predefined items are changed and the exchange plan where the changes are registered have common separators, the changes are only registered for those exchange plan nodes where separator values match the separator values of predefined items.
When predefined data belonging to a specific object was changed, all predefined items of this object were registered as if they were changed.

Predefined item changes were registered for all exchange plan nodes available from the session where the predefined items were changed.

When object predefined data is changed, object change registration tables do not significantly increase in size.
Managed form. Web client. In the web client, if a managed form table cell contains multiple text lines, only lines that fit the cell height are shown. If the text does not fully fit, ellipsis (…) is added to the end of the last line. In Microsoft Internet Explorer 8 web browser, the ellipsis is not displayed.

In the thin client, text in managed form table cells better fits the cell height.

In the web client, if a managed form table cell contained multiple text lines, the lines might be cut in the manner that made them unreadable (only the upper character halves were displayed and the lower ones were cut).

The ellipsis was not added to the end of the last line.

In the thin client, sometimes text in managed form table cells did not fit the cell height well, a redundant empty line was added to the bottom of the cell.

Eliminated unexpected system behavior.
Data composition system. While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items are removed:
  • Items that include references to fields disabled by functional options
  • Items that include references to fields unavailable due to access rights restrictions
  • Items linked to data composition schema fields that no longer exist

This change is not implemented in 8.3.4 compatibility mode.

While loading user settings for reports and dynamic lists (including automatic loading during form opening), the following items were removed:
  • Items that included to fields disabled by functional options
  • Items that included references to fields unavailable due to access rights restrictions
Improved system stability.
Working with database. You can load the infobase dump file (*.dt) that was generated with the following conditions:
  • The dump was created in the file mode .
  • 1C:Enterprise version 8.3.4 was used for dumping.
  • Filled aggregates of turnover accumulation registers were available in the infobase.

In some scenarios, the aggregates of turnover accumulation registers are cleared after the loading.

Loading the infobase dump file (*.dt) was not available if the file was generated with the following conditions:
  • The dump was created in the file mode .
  • 1C:Enterprise version 8.3.4 was used for dumping.
  • Filled aggregates of turnover accumulation registers were available in the infobase.
Eliminated unexpected system behavior.
Display of information. Text fragments found during a search by substring are displayed in a uniform way (bold font and green text) in the following cases:
  • In managed form text box drop-down lists
  • In favorites
  • In history
  • In dynamic lists
  • In the full-text search form
The substrings that were found had different looks.Uniformed look for different features.
Working with XML, XDTO. For charts of accounts and charts of calculation types, the Predefined field of predefined tabular sections is available for writing. In charts of accounts and charts of calculation types, the predefined records of predefined tabular sections can include only predefined items. During a serialization of a chart of accounts item or a chart of calculation types item to XML(XDTO), the Predefined item, which matches the Predefined property, is written. During the deserialization, the Predefined item value is written to the Predefined property only if the compatibility mode is disabled.

This change is not implemented in 8.3.4 compatibility mode.

For charts of accounts and charts of calculation types, the Predefined field of predefined tabular sections was read-only.

During the serialization of a chart of account item or a chart of calculation types item to XML(XDTO), the Predefined item was not generated.

During data exchange between configurations, the flags of predefined data are no longer lost in the chart of accounts and chart of calculation types items.

Table of contents


Comments
0
Add comment