Changes that affect system behavior



Functionality

After

Before

Result of changes

Data composition system.

If a type of one of the operands in a data composition system expression is arbitrary, the resulting expression will also have an arbitrary type.

This change is not implemented in version 8.3.14 compatibility mode.

If a value with an arbitrary type was present in a data composition system expression, an arbitrary type was ignored upon calculating the resulting expression time.

Eliminated unexpected system behavior.

Interface.

Edited pictures in the client application interface (and in the picture library) for the spreadsheet document commands used for collapsing and expanding all groups.

Pictures in the client application interface (and in the picture library) for the spreadsheet document commands used for collapsing and expanding all groups were different.

Now pictures of the spreadsheet document commands used for collapsing and expanding all groups of the spreadsheet document better correspond to performed actions.

Development tools.

In the form editor, the Action property of the adopted form command contains a name of the method, which is a command handler in the extended configuration. Navigation to the command handler is unavailable.

In the form editor, the Action property of the adopted form command contains a name of the method, which is a command handler in the extended configuration. Navigation to the command handler generated an error.

Eliminated unexpected system behavior.

Queries.

Query language operation CASE will be considered a constant and replaced with a constant if all operation branches contain only constant expressions. Therefore, operation CASE can be used in constant parameters of virtual tables if all branches of operation CASE contain only constant expressions. If an operand of operation CASE contains NULL in query totals, then the operation result will be a value specified in ELSE or NULL if it is absent. This change is not implemented in version 8.3.14 compatibility mode.

Query language operation CASE was not replaced with a constant and could not be used in constant parameters of virtual tables. Upon calculating operation CASE in query totals, if the operation operand contained NULL, the operation result was NULL.

Eliminated unexpected system behavior.

Managed forms.

New feature: you can change properties of client application form items without calling a server:

  • Decoration:
  • Decoration label extension:
  • Form group extension for a command bar:
  • Form group extension for a page:
  • Form group extension for a normal group:
  • Button
  • Form field extension for picture field:

This feature was not provided. Accessing the specified properties of client application form items required a server call.

Reduced client/server interaction upon managing a client application form using 1C:Enterprise language.

Collaboration system.

Implemented the following features in the collaboration system interface:

  • Upon editing a message, the cursor is placed at the end of the message text.
  • Upon sending a message, trailing spaces are trimmed in the message.
  • You can open a collaboration system user profile by clicking the user avatar.
  • The unread mark is cleared in a conversation if any of the following actions is carried out:
    • Click a link in a message.
    • Click a username or a user avatar.
    • Click an attachment in a message.
    • Click a message action.
    • Right-click (open the context menu).
  • When the default collaboration system form is first opened, the first conversation is not activated.
  • In the thick and thin client applications, you can select a notification in the notification center by clicking a message picture. The upgrade is ignored in the web client.

Changed the standard user group picture in the drop-down list of user selection.

The collaboration system interface had different behavior:

  • Upon editing a message, the cursor was not placed at the end of the message.
  • Upon sending a message, leading and trailing spaces were trimmed.
  • A user profile was opened by clicking a username.
  • When the default collaboration system form was first opened, the first conversation was activated. In the thick and thin client applications, you could select a notification in the notification center only by clicking a message text. In the web client, you could select a notification by clicking a message text or a message picture.

Improved collaboration system interface.

Data composition system.

Commands Generate, Print, Save, and Compact mode will be added to the report form command bar (with enabled automatic filling) if a property of the report form Report result is set. If a property of the report form Report result is not set, commands Generate, Print, Save, and Compact mode will not be added to the report form command bar, which is filled in automatically. This change is not implemented in version 8.3.14 compatibility mode.

Commands Generate, Print, Save, and Compact mode were always added to the report form command bar with enabled automatic filling.

Eliminated unexpected system behavior.

Charts.

If a format is not set explicitly for number presentations in the chart settings, the default format (considering regional infobase settings) will be applied to the numbers. This change is not implemented in version 8.3.14 compatibility mode.

If a format was not specified explicitly for number presentations in the chart settings, no specific formatting was applied to the numbers.

Eliminated unexpected system behavior.

Managed forms.

If an input field is in the list selection mode, you can search for the value as follows:

  • First, presentations are searched by the beginning of the line if the presentation is specified explicitly.
  • Then search considering a list value type is carried out:

This change is not implemented in version 8.3.14 compatibility mode.

If the input field was in the list selection mode, search was carried out by the beginning of the line for all types in the specified presentation or if the presentation was not specified, search was carried out in a string value presentation from the selection list.

Now search in input fields, which use a selection list, is more predictable and better meets user expectations.

Collaboration system.

New feature: in the collaboration system, you can manage a number of received notifications for context and noncontext conversations. You can disable notifications of a conversation, receive notifications only for the messages to a user, or receive notifications of all messages. This feature can be set up using both user interface and 1C:Enterprise language. Implemented methods GetWatchMode() and SetWatchMode() for noncontext conversations. Implemented the User parameter for the GetWatchMode() and SetWatchMode() methods. Implemented the following methods of the collaboration system manager: SetConversationNotificationRepresentation() and GetConversationNotificationRepresentation().

Previously, you could only disable all notifications in a collaboration system. The GetWatchMode() and SetWatchMode() methods were used for context conversations only.

Expanded capabilities of the collaboration system interface.

Managed locks.
Collaboration system.

New feature: now in the client application (thin, thick, and web client), you can unlock object lock set by another user or the same user in another session. An object lock is a lock set interactively upon editing an object in the form or using methods Lock(), LockDataForEdit(), and LockFormDataForEdit(). Now when you find a lock, you can start a conversation with a lock initiator in collaboration system (if the infobase supports the collaboration system).

This feature was not provided.

Simplified operations with infobase data in some cases.

Interface.

Implemented the following features for dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox() (in all client applications and Version 8.2 and Taxi interfaces):

  • Updated the dialog boxes.
  • If a title is not specified for a dialog box (in the relevant method parameter), this dialog box is opened without a title.
  • Upon creating dialog boxes, scaling set for all forms in the Taxi interface is considered.
  • Changed pictures displayed in the relevant dialog boxes in the Taxi interface.

Dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox() had different appearance and did not consider form scale in Taxi interface.

Improved appearance of dialog boxes generated by 1C:Enterprise language methods DoQueryBox(), ShowQueryBox(), DoMessageBox(), and ShowMessageBox().

Spreadsheet documents.

Text orientation set for a spreadsheet document cell area is considered upon text output if the Windows system font is selected as a font.

This change is not implemented in version 8.3.14 compatibility mode.

If the Windows system font was selected as a font of a spreadsheet document cell area, text orientation set for a spreadsheet document cell area was not considered upon text output.

Eliminated unexpected system behavior.

Data composition system.

Now you can apply conditional appearance of a column of a data composition system report table to the entire column if one of the following usage areas is selected for a conditional appearance item: In group, In hierarchical group, or <Everywhere>.

This change is not implemented in version 8.3.14 compatibility mode.

If usage area In group, In hierarchical group, or <Everywhere> was selected for a conditional appearance item upon applying appearance of a column of a data composition system report table, appearance could be specified for a table header and column total only.

Eliminated unexpected system behavior.

Managed forms.

If a client application form contains one of the following items: a spreadsheet document field, a text document field, a graphical schema field, an HTML document field, a formatted document field, a geographical schema field, or a planner field, a submenu containing Print, Save, and Preview commands is generated in the form title. If there is more than one above-listed item in the form, menu commands are available for the current item of the specified type.

Preview command is not displayed in the web client.

This feature was not provided.

Improved form usability.

macOS.

Add-ins work correctly in thin client (macOS) and Safari. Add-in revisions are not required.

Add-ins worked incorrectly in Safari but worked correctly in thin client (running under macOS).

Eliminated unexpected system behavior.

Queries.

The following query language functions can be used as virtual table parameters that can have constant values only: SUBSTRING(), YEAR(), QUARTER(), MONTH(), DAYOFYEAR(), DAY(), WEEK(), WEEKDAY(), HOUR(), MINUTE(), and SECOND(). You can use them only if all parameters have constant values in the specified functions. In this case, the calculated function value is added as a parameter value.

This change is not implemented in version 8.3.14 compatibility mode.

The following query language functions could not be used as virtual table parameters that can have constant values only: SUBSTRING(), YEAR(), QUARTER(), MONTH(), DAYOFYEAR(), DAY(), WEEK(), WEEKDAY(), HOUR(), MINUTE(), and SECOND().

Now you can use date/time functions as parameters that can take only constant values, and virtual register tables in the query language. This is possible only if functions have constant values as parameters.

Spreadsheet documents.

Now you can edit (both interactively and using 1C:Enterprise language) page parameters of a spreadsheet document converted into compact mode.

For a compact spreadsheet document, you can now call the SetHorizontalStretch() method.

Upon editing a compact spreadsheet document, both the compact document and the original document are changed.

A compact spreadsheet document did not support setting up page parameters.

Settings of spreadsheet document parameters for print and view are now more convenient.

Managed forms.

In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsHorizontalAlign property set to Left, Center, or Auto (which is the same as Left or Center), all last form items or group items, for which the HorizontalAlignInGroup property value is set to Right up to the item, for which the HorizontalAlignInGroup property value is not equal to Right, are aligned right.

In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsVerticalAlign property set to Top, Center, or Auto (which is the same as Top or Center), all last form items or group items, for which the VerticalAlignInGroup property value is set to Bottom up to the item, for which the VerticalAlignInGroup property value is not equal to Bottom, are aligned bottom.

This upgrade is ignored in 8.3.13 version compatibility mode.

In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsHorizontalAlign property set to Left, Center, or Auto (which is the same as Left or Center), only the last item in a form or a group was aligned right.

In a form or a form group of the Normal or Page type with set horizontal grouping and the ChildItemsVerticalAlign property set to Top, Center, or Auto (which is the same as Top or Center), only the last item in a form or a group was aligned bottom.

Eliminated unexpected system behavior.

Mobile application builder.

New feature: cleanup of the Mobile application builder cache directory. Artifacts saved to the cache directory more than 30 days ago are deleted. Temporary build directories remaining after unexpected build termination or interruption are also deleted.

This does not require setup and is fully automatic.

The Mobile application builder cache could increase in size only. The Mobile application builder did not provide cleanup of unused cached artifacts.

Stopped the uncontrolled growth of the Mobile application builder cache directory. The builder caches only the artifacts used during build for the last 30 days.

Full-text search.
Server clusters.

The full-text search string cannot contain more than 1,000 words. An error occurs upon excess. Functional words and search operators are not considered when counting the number of words.

The number of words in the full-text search string was not limited. Specifying a very large number of words in the search string could significantly reduce server cluster performance.

Improved application stability. Reduced risk of affecting the application responsiveness as a whole by specifying a very large full-text search string.

Database operations.

Enhanced database integrity check upon database configuration update. Several database tables can no longer get the same internal number. In this case, an exception is thrown and the database is not updated.

Upon database configuration update, internal numbers of database tables were not checked for uniqueness. As a result, various unexpected errors could occur when using the information system.

Eliminated unexpected system behavior.

File operations.

If thin client connects to the infobase via web server using HTTPS protocol, upon using the GetFile(), GetFiles(), BeginGettingFiles(), BeginGetFileFromServer(), and BeginGetFilesFromServer() methods, reauthentication on the web server is no longer required.

If thin client connected to the infobase via web server using HTTPS protocol, upon using the GetFile(), GetFiles(), BeginGettingFiles(), BeginGetFileFromServer(), and BeginGetFilesFromServer() methods, reauthentication on the web server was required.

Eliminated unexpected system behavior.


Next page: Changes that require modification of configuration and administrative settings