1C:Enterprise 8.3.20. New functionality and changes.

Version 8.3.20

Version 8.3.20 includes known bug fixes and functionality modifications.

New functionality and changes

Functionality After Before Result of changes
Configuration properties. For configuration property Compatibility mode, new value Version 8.3.19 is now implemented. Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.18 was available. Configurations developed using 1C:Enterprise platform version 8.3.19 or earlier can now run on version 8.3.20 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.20 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.19 after the migration to version 8.3.20, even if you disable the compatibility mode (simply enable it again).
Configuration extensions. Integration service. You can now adopt integration services and create native integration services in an extension. This feature was not provided. The configuration extension now provides more features.
Licensing system. You can now activate a ssoftware license from 1C:Enterprise language. New global context property: LicensesAcquisition. This feature was not provided. You can now activate software licenses when it is not possible to start Designer.
Event log. You can now control the period of event log data separation and reduce the event log from 1C:Enterprise language. New methods: GetEventLogDataStorageSeparationPeriod(), SetEventLogDataStorageSeparationPeriod(), GetEventLogPeriod(), and ReduceEventLog(). You can use the Range type to manage locks and the event log. This feature was not provided. It was possible to control the period of event log data separation and reduce the event log only in interactive mode from Designer. You can now implement all functions of managing the event log using 1C:Enterprise language.
Regional settings. You can now work with regional infobase settings from 1C:Enterprise language. New global context methods: GetRegionalInfobaseSettings(), SetRegionalInforbaseSettings(), and GetRegionalSessionSettings(). This feature was not provided. Using 1C:Enterprise language, it was possible to obtain the current locale code and the infobase locale code. It is now possible to work with regional infobase settings using 1C:Enterprise language.
Queries. New query language functions: String(), StringLength(), TrimL(), TrimR(), TrimAll(), Left(), Right(), StrFind(), StrReplace(), Upper(), Lower(), Sin(), Cos(), Tan(), ASin(), ACos(), ATan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Round(), Int(), and StoredDataSize(). If a query uses the above functions, this query will not be sent to Data Accelerator. These features were not provided. Advanced query language features.
Data composition system. New functions in the expression language of the Data Composition System: TrimL(), TrimR(), TrimAll(), Left(), Right(), StrFind(), StrReplace(), Upper(), Lower(), and NStr(). If a filter of the Data Composition System is applied to a calculated field that contains the following functions: Sin(), Cos(), Tan(), ASin(), ACos(), ATan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Round(), Int(), or StringLength(), this field will be processed using a query (if possible). This change is not implemented in 8.3.19 compatibility mode. These features were not provided. If a filter of the Data Composition System was applied to a calculated field that contained the following functions: Sin(), Cos(), Tan(), ASin(), ACos(), ATan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Round(), Int(), or StringLength(), this field was calculated during data composition. Advanced Data Composition System features.
Collaboration system. External (in relation to the information system) users can now participate in conversations of the iCollaboration System (conversationss and video calls). External users participate in conversations using the website https://dialog.online. External users can only communicate with those users who participate in the conversation to which the external user is invited. To access conversations, an external user must send an invitation. New properties for the CollaborationSystemUser object: External and EmailForAuthentication. New methods for the Collaboration System manager: ExternalAccessSupported(), GetExternalAccessURL(), and SendExternalAccessURL(). New object: CollaborationSystemUsersFilter. New parameter for the GetUsers() method of the Collaboration System manager: Filter. New event handler for the managed application module: CollaborationSystemExternalUserInvitationProcessing. Changed the user interface of the Collaboration System. This feature was not provided. Expanded collaboration system capabilities.
DBMS operations. Support of PostgreSQL version 13 (x86-64). is implemented. This PostgreSQL version was not supported. Extended list of supported PostgreSQL versions.
Collaboration system. In the Collaboration System, integration with an arbitrary system is now possible. One-way integration is implemented. The Collaboration System can only receive messages of a certain format. REST interface is used for interaction. New property: CollaborationSystemIntegration.ConnectionPointURL. The CollaborationSystemConversation.Integration property becomes writable. HTML formatting is limited in message texts. This feature was not provided. A limited list of external systems was available for integration. Expanded collaboration system capabilities.
Configuration extensions. Predefined data. You can now create predefined items in native catalogs of configuration extensions. This change is not implemented in version 8.3.19 compatibility mode (for configuration and configuration extension). Native catalogs of configuration extensions did not support creation of predefined configuration items. The configuration extension now provides more features.
Interface. You can now control the display of form groups of the Page type:
  • The value of the TitleFont property of the form group of the Page type sets the font of the page title. This property for the form group of the Pages type controls the font of the title of all pages in the group (for which the font is not explicitly specified).
  • The value of the TitleTextColor property of the form group of the Page type sets the color of the page title text. This property for the form group of the Pages type controls the color of the title text of all pages in the group (for which the title text color is not explicitly specified).
This change is not implemented in 8.3.19 compatibility mode.		 These features were not provided. The TitleFont and TitleTextColor properties were not used to style form groups of the Page type. Improved client application interface.
Dynamic lists. A dynamic list now supports the Presentation expression property for data set fields and calculated fields. This presentation is only used in a dynamic list table, and is not used for a field that appears outside of a dynamic list. The property value can be set interactively or by using the PresentationExpression property of the DataCompositionSchemaDataSetField and DataCompositionSchemaCalculatedField objects. This feature was not provided. New formatting options for dynamic lists.
XML and XDTO support. New global context property: XMLStringProcessing. Use this property to call the FindDisallowedXMLCharacters() method. The global context method of the same name is deprecated. New global context method to remove invalid XML characters from a string: XMLStringProcessing.RemoveDisallowedXMLCharacters(). It was only possible to find the occurrence of an invalid XML character in a string using the FindDisallowedXMLCharacters() global context method. Clearing text with XML-like markup from invalid characters is now more convenient.
Common objects. You can now get the type of the client application that started a given session. You can now determine that a given client application can work with a standalone mobile client server. New methods for the ClientApplication object: ClientApplicationType() and ClientUsingStandaloneServer(). This feature was not provided. It is now easier to determine the client application used.
Data display. The picture library includes the following new pictures:
  • MessageHistory
  • ExternalUser
  • ShowPassword
  • HidePassword
 he listed pictures were not available in the picture library. The picture library is upgraded.
Table of contents

New functionality and changes in the 1C:Enterprise mode

Functionality After Before Result of changes
Collaboration system. The video call ends automatically and the video call window closes when only the current user remains in the participant list. The default video call window displays all video conference participants without activating the speaking user. On screen sharing, the video from the local camera is displayed on the bottom right of the video call window. The video call window remained open after the video call ended. In the video call window, the speaking participant was activated by default, and the rest were displayed in the column to the right of the speaker. On screen sharing, the video from the local camera was not displayed anywhere. Video calls in the Collaboration System are now more user-friendly.
Collaboration system. The Collaboration System now has the following options to control the read status for messages:
  • When viewed. The message is marked as read a few seconds after the user opens the message.
  • Manually. The message is marked as read once the Read hyperlink is clicked in the message list.
  • On reply or manually. The message is marked as read when replying to the message or clicking the Read hyperlink.
The conversation context menu and the More actions menu now have the Mark as read command, which is available for conversations that have unread messages.		 These features were not provided. Messages were always marked as read a few seconds after being viewed. It was impossible to control this. It is now easier to manage the read status of messages. The user can configure the control mode for this feature.
Administration tools. Implemented standard data processors that allow you to edit infobase parameters (Infobase parameters) and the user list (Users). The platform did not allow these operations to be performed in the client application. These tools could be implemented in the application. Advanced features of system administration from the client application.
Collaboration system. The Collaboration System menu now contains the Message history command. This command opens a form that allows you to view messages for the selected date. This form also displays all conversations the user participated in on the selected day. This feature was not provided. A single list of all messages for the day was not available. Improved operations with Collaboration System messages.
Mobile platform. Mobile client. On mobile devices, the appearance and behavior of the following system forms has been changed:
  • Report settings save form
  • Report option save form
  • Dynamic list settings choice form
  • Dynamic list settings save form
  • Report settings choice form
  • Report option choice form
  • Form parameter choice form
  • Form parameter save form
  • Report form
  • Report settings form
  • Dynamic list settings form
  • Settings edit form
  • Report option edit form
  • Conditional appearance item form
We recommend that you check the display of the specified forms in used mobile applications on the new mobile version.		 The specified forms looked different in the mobile application. Improved interface of some forms on mobile devices.
Web client. File operations. When using the File System extension in Google Chrome and Mozilla Firefox, receiving files over HTTPS is now faster. When using the File System extension in Google Chrome and Mozilla Firefox, receiving files over HTTPS took longer. When using the File System extension in Google Chrome and Mozilla Firefox, receiving files over HTTPS is now faster.
Table of contents

Optimization

Functionality After Before Result of changes
Server clusters. Improved performance of the server cluster when working on high load. Optimized use of RAM on Windows. RAM was used less effectively on Windows. Slightly increased system speed and optimized use of RAM on Windows.
Server clusters. Improved server cluster stability. Reduced the number of issues that lead to abnormal termination of the server cluster. A large number of issues that occurred during cluster operation led to abnormal termination of the server cluster. Improved server cluster stability in problematic situations.
Queries. Optimized the LIKE operator of the query language for a file infobase. In a file infobase, the LIKE operator of the query language required more time. Improved performance of the LIKE operator in a file infobase.
Data access restrictions. Improved performance of a query that uses the SELECT FIRST, ALLOWED, and ORDER BY statements and a data access restriction at a time. For optimization purposes, a statement that does not depend on the data in the protected table is extracted from the data access restriction query, if possible. The result of this query is placed in a temporary table (but no more than 6 temporary tables), and this temporary table is then used in the original query. The exact behavior implementation depends on the DBMS used. A query that used the SELECT FIRST, ALLOWED, and ORDER BY statements and a data access restriction at a time could be executed in a suboptimal way due to the fact that the DBMS could not select an adequate query plan. Improved performance of some queries executed on systems with restricted data access.
Server clusters. Fixed identified memory leaks in a working process when sessions served by this working process fail or migrate to another working process. There were memory leaks in a working process when sessions serviced by that working process failed or migrated to another working process. Improved control over resource usage by the cluster working process.
Server clusters. Common attributes / Data separation. Configuration extensions. Reduced RAM consumption by a working process when working with a separated infobase with a large number of separated configuration extensions. A working process used more RAM when working with a separated infobase with a large number of separated configuration extensions. Reduced RAM consumption by the server cluster in the separated mode.
Configuration extensions. Infobase operations. Optimized infobase restructuring if the infobase contains configuration extensions. Restructuring an infobase if it contained configuration extensions took longer. Restructuring an infobase if it contains configuration extensions is now faster.
Standalone serverDumping configurations to files/Restoring configurations from files. Significantly reduced the time to fully load the configuration from XML files when using a standalone server. It took a significantly longer time for a standalone server to perform a full configuration load from XML files. Improved configuration load from XML files when the standalone server is used.
Applied objects. Improved generation of a list of characteristics for a flexible type when settings of characteristics of different types (out of the flexible type) differ only in the filter value for the characteristic type. Generation of a list of characteristics for a flexible type when settings of characteristics of different types (out of the flexible type) differed only in the filter value for the characteristic type took more time and could slow down various platform mechanisms. Improved list of characteristics.
Table of contents

Changes that affect system behavior

Functionality After Before Result of changes
Configuration extensions. You can now extend types of the following adopted objects:
  • Common attribute type if the common attribute is not a separator.
  • Type of the "Type of chart of characteristic types" attribute.
  • Defined type.
You can now create native defined types (if the extension compatibility mode is strictly older than version 8.3.19). In native objects of the configuration extension, you can now use types of the types AnyRef, CatalogRef, and so on, and defined types. References of the type AnyRef, CatalogRef, and so on include references to objects brought in by configuration extensions. The AllRefsType() method includes types from extensions in the return value. This change is not implemented in 8.3.19 compatibility mode.		 These features were not provided. Advanced configuration extension features.
Mobile client. Development tools. You can now debug a standalone server for a standalone mobile client. You can now attach three debug items in a single debug session. New debug item: Standalone server (standalone mobile client). You can now use performance analyzer to analyze the runtime of all three components of the standalone mobile client. Optimized Debugger. This feature was not provided. A single debug session could attach up to two debug items at a time. Simplified debugging of applications that run in an standalone mobile client.
Information registers. Data access restrictions. Information registers can now use dimensions and separators that include a register in expressions for restricting read and edit access to data. Specifying different access restrictions for individual fields only applies when receiving data from information registers using queries and dynamic lists. When using 1C:Enterprise language objects, it is assumed that all fields are accessed and access is allowed only if it is allowed to all fields (restrictions are imposed on all fields combined with "AND"). When writing a record set, only edit restrictions are applied. This change is not implemented in 8.3.19 compatibility mode. For information registers, in data access restriction expressions, it was not possible to specify dimensions and separators that included a register. For read access to dimensions and separator fields, no data access restrictions were applied. Expanded restrictions of access to information register data.
Configuration extensions. On compilation errors of adopted extension modules, the following behavior is implemented:
  • A notification to the notification center is generated.
  • Information about a compilation error is generated (available using the Information for technical support dialog box).
  • The action (that required compilation of the adopted module) is performed without the extension in which the error occurred.
If the application is started in debug mode or in version 8.3.19 compatibility mode, this change is not implemented.		 On compilation errors of adopted extension modules, the following behavior was observed:
  • A module compilation error was generated.
  • The action (that required compilation of the adopted module) was aborted.
 The configuration keeps functioning as much as possible in case of extension issues.
Dumping configurations to files/Restoring configurations from files. The format version of configuration dump to XML files is now 2.13. The format version of configuration dump to XML files was 2.12. The configuration dump to XML files now supports new platform features.
Table of contents

Changes that require modification of configuration and administrative settings

Functionality After Before Result of changes
Administration tools. 1C:Enterprise server distribution package for Linux and Windows now includes Java (Liberica JRE). The utilities for installing 1C:Enterprise server have been changed for these operating systems. Java was not included in 1C:Enterprise server distribution package. To use some features of 1C:Enterprise, the user had to download and install Java on their own. Simplified use of 1C:Enterprise components that require Java system, for example, the v2 restructuring mechanism, the licensing utility, and so on.
Administration tools. The licensing utility is no longer included in 1C:Enterprise distribution package. You can download the licensing utility via 1C:Application update of 1C:ITS Portal Read more.. The licensing utility was part of 1C:Enterprise distribution package. Simplified access to the licensing utility.
Configuration extensions. Administration tools. To specify the name of the file to be signed, use the following parameters:
  • /SignCfg command - -SignedFile parameter.
  • Agent mode commands config sign-cfg - --signed-file parameter. The --result-file parameter is no longer used.
To specify the configuration type, use the following parameters:
  • /SignCfg command - -ConfigurationType parameter. The -Type parameter is no longer used.
  • Agent mode commands config sign-cfg - --configuration-type parameter. The --type parameter is no longer used.
 To specify the name of the file to be signed, the following parameters were used:
  • /SignCfg command - the first positional parameter of the command.
  • Agent mode commands config sign-cfg - --result-file parameter.
To specify the configuration type, the following parameters were recommended:
  • /SignCfg command - -Type parameter.
  • Agent mode commands config sign-cfg - --type parameter.
 The parameters of the /SignCfg command in batch mode and config sign-cfg in Designer agent responsible for specifying file names and configuration types have been unified with similar parameters of other commands.
Administration tools. Client application installation. Linux. Implemented an application for installing 1C:Enterprise components on Linux. The installer is available in three versions: full, thin client, and training version. The installer works both in graphics mode and batch mode (without a window interface). Package files .deb and .rpm are no longer used to deliver system distribution packages for Linux. Implemented an uninstaller. New parameters for the conf.cfg file: PublishDistributiveLocationLinux64 and PublishDistributiveLocationLinux32. The following parameters of this file are no longer supported: PublishDistributiveLocationLinuxDeb64, PublishDistributiveLocationLinuxDeb32, PublishDistributiveLocationLinuxRpm64, and PublishDistributiveLocationLinuxRpm32. New attributes for the point element of the default.vrd file: pubdstlin64 and pubdstlin32. The following attributes of this element are no longer supportred: pubdstlindeb32, pubdstlindeb64, pubdstlinrpm32, and pubdstlinrpm64. New parameters for the pubdst parameter of the http section of the standalone server configuration file: lin64 and lin32. 1C:Enterprise applications were delivered in the form of .deb and .rpm packages that could be installed only from the command line. Simplified installation of 1C:Enterprise components on Linux.
System requirements. Linux. The following Linux distribution packages are no longer supported:
  • Astra Linux Common Edition 1.11
  • Astra Linux Special Edition 1.4 and 1.5
  • ALT Linux 7.0 SPT
 1C:Enterprise supported the following Linux distribution packages:
  • Astra Linux Common Edition 1.11
  • Astra Linux Special Edition 1.4 and 1.5
  • ALT Linux 7.0 SPT
 Outdated Linux distribution packages are no longer supported.
System requirements. Linux. 1C:Enterprise distribution package for Linux now includes the WebKit1 library version 2.4.11. The WebKit1 library was not included in 1C:Enterprise distribution package for Linux. 1C:Enterprise deployed under Linux no longer depends on the webkitgtk-3.0.0 library.
System requirements. Microsoft Windows XP 64-Bit Edition is no longer supported. Microsoft Windows XP 64-Bit Edition was supported. The outdated operating system is no longer supported.
Collaboration system. You can now set the user on whose behalf the session will connect to the Collaboration System. This feature is supported only for sessions that run on behalf of the "default user" (a background job started by a scheduled job). New method: CollaborationSystemManager.SetCurrentUser(). This feature was not provided. A background job that was started by a scheduled job could not connect to the Collaboration System without explicitly specifying the user on whose behalf the scheduled job should be executed. Simplified connection to the Collaboration System from background jobs that are started using scheduled jobs.
Settings storage. When crawling the list of standard storage settings using the StandardSettingsStorageSelection.Next() method, no attempt is made to deserialize the stored settings. Deserialization is performed only when an attempt is made to access the object that stores the settings (StandardSettingsStorageSelection.Settings). In this case, an exception might be thrown. When crawling the list of standard storage settings using the StandardSettingsStorageSelection.Next() method, an attempt was made to deserialize the stored settings. If an incorrect setting object was placed in the storage, an exception was thrown when crawling the settings list. After reaching the selection end, all object properties contain values ​​matching the last selection item. If the selection is empty or the StandardSettingsStorageSelection.Next() method has not been called yet, the selection contains the following values:
  • The following properties contain an empty string: ObjectKey, SettingsKey, User, and Presentation.
  • The following properties contain the Undefined value: ChangeDate and Settings.
 Crawling the list of standard settings is more logical now. When crawling the list, the possibility of an exception caused by incorrect settings is excluded.
Client application. Administration tools. OpenID Connect protocol now supports authentication with Authorization Code Flow. New field for the OpenID provider description section of the default.vrd file (the <providers> element): client_secret. We recommend that you switch all production systems to Authorization Code Flow. We do not recommend that you use Implicit Code Flow (the current protocol implementation) for security reasons. For OpenID Connect protocol, only authentication with Implicit Code Flow was supported. It is now possible to use a more secure version of OpenID Connect protocol.
Error handling. Errors that occur when converting a spreadsheet document to external formats can now be detected. New system enumeration value: ErrorCategory.DocumentConversionError. When analyzing error categories, an application developer should note that the list of categories may expand in new system versions. They should also note that an error can change the belonging to a particular category. Errors that occurred when converting a spreadsheet document to external formats did not come into a separate category. Extended list of error categories.
Data composition system. If the data composition schema uses filter with the comparison types Contains, Begins with, Like, Does not contain, Does not begin with, or Not like for a query field that contains a join where this field is a string type in one part of the join and is not a string type in a different part of the join, a knowingly false condition will be added to the query in the part of the join where the field is a non-string type. We recommend that you analyze data composition schema filters in order to correct such conditions. This change is not implemented in 8.3.19 compatibility mode. If the data composition schema used filter with the comparison types Contains, Begins with, Like, Does not contain, Does not begin with, or Not like for a query field that contained a join where this field was a string type in one part of the join and was not a string type in a different part of the join, there were no conditions in a query in the part of the join where the field was a non-string type. Eliminated unexpected system behavior.
Standalone server. All commands that use the infobase (regardless of the execution method) are executed within a full infobase session, checking the rights of the user on whose behalf the action is being performed, and registering actions in registration. Commands related to the server as a whole (such as retrieving a session list or terminating a call) do not require creating a session, but they must also be executed on behalf of an infobase user with administrative rights. To execute administration interface commands, a session was not created, the rights of the user on whose behalf the administrative action was being performed were not checked, and the actions performed were not recorded in the infobase event log. Improved security of standalone server management.
Standalone server. All administration interface commands of a standalone server (except for commands for initializing a server configuration, creating an infobase, and restoring infobase integrity) can be managed by a running instance of a standalone server. To identify the managed server, you can use the ID of the standalone server process (on a local computer, access is performed using IPC technology) or the remote computer address (access is performed using the ssh protocol). For the ibcmd utility, the --pid, -p, --remote, and -r parameters are implemented to control the way of connecting to a standalone server for command execution. New ibsrv utility commands for the ibcmd utility: --config, -c, --system, --dbms, --db-server, --db-name, --db-user, --db-pwd, --request-db-pwd, -W, --db-path, --data, -d, --lock, --temp, -t, --session-data, --log-data, --ftext-data, and --openid-data. It was not possible to manage a running instance of a standalone server. Standalone server management on a remote computer was not supported. The ibcmd utility (in standalone server settings) could only change the configuration file content. There are two modes available for managing a standalone server:
  • Without a running server instance. In this case, the configuration file of the standalone server is generated.
  • With a running server instance. In this case, you must explicitly specify the managed server instance (on the current or remote computer) using the appropriate command-line options.
Standalone server. You can now describe several HTTP gateways that serve calls to the infobase. The gates section is implemented in the standalone server configuration file. The infobase of the client application and Internet services is accessed using the gates|http section. For a standalone server, the administration interface can now be accessed via SSH. The standalone server commands are the same as the commands of Designer in agent mode and are listed in the documentation. The gates|ssh section is implemented in the standalone server configuration file. The standalone server configuration file supported setting up only one HTTP gateway that provided access to the infobase. SSH access to the standalone server was not provided. Advanced standalone server administration features.
Standalone server. New administration interface commands for a standalone server:
  • session. Operations with a list of sessions.
  • lock. Operations with locks.
  • infobase config extension. Operations with an extension.
  • infobase config data-separation list. Getting a list of names of common attributes of the application.
  • infobase config support disable. Disables the configuration support.
  • infobase config repair. Verifies and repairs the infobase.
For the infobase config save command:
  • Implemented the --db parameter that indicates an operation with the database configuration.
  • Removed the --stage parameter that indicates an operation with the main configuration.
  • By default, the command is executed with the main configuration.
For the infobase config apply command:
  • Implemented the --dynamic parameter that allows you to dynamically update the infobase configuration.
  • Implemented the --session-terminate parameter that sets the behavior if there are sessions that block the setting of the exclusive mode of access to the infobase.
For the infobase config export command, implemented the --force parameter that allows you to force a full dump using the --sync parameter if it turns out that files of the configuration located on the hard drive are in the format that differs from the format of the current dump.		 These features were not provided. Expanded the administrative interface of the standalone server.
Charts. The following properties of the GanttChart, Dendrogram, and PivotChart objects are no longer available in 1C:Enterprise language: SplineMode, SplineStrain, SemiTransparencyMode, SemiTransparencyPercent, FunnelNeckHeight, FunnelNeckWidth, FunnelSpace, ValuesBySeriesConnection, ValuesBySeriesConnectionLines, ValuesBySeriesConnectionColor, SeriesOrderInLegend, ValuesAxis, PointsAxis, SecondaryValuesAxis, PointsAxisValuesSource, PointsAxisSeries, BubbleSizeValueSource, BubbleSizeCommonSeries, BubbleSizing, BubbleChartNegativeValuesShowMode, DefaultBubbleSize, MinBubbleSize, MaxBubbleSize, PointsConnection, BarChartPointsOrder, GradientPaletteMaxColors, GradientPaletteStartColor, GradientPaletteEndColor, ValuesReferenceLines, ValuesReferenceBands, PointsReferenceLines, PointsReferenceBands, ColorPaletteDescription, ReferenceBandsColorPaletteDescription, NonNumericValuesUse, PointsConnectionOnMissedValues, DonutChartInnerRadius, ValueTooltipRepresentation, ValuesToolTipFillType, SelectionModeShowPopUpInformationalLineOfPoints, ShowPopuUpInformationalLineOfValues, and ValuesEditMode. The following properties of the GanttChartPlotArea, DendrogramPlotArea, and PivotChartPlotArea objects are no longer available in 1C:Enterprise language: PointsScale, ValuesScale, AdditionalValuesScale, and SeriesScale. This change is not implemented in 8.3.19 compatibility mode. The specified properties were available in 1C:Enterprise language but had no effect. Excluded access to undocumented properties of chart objects.
Administration tools. Client application installation. Linux. Changed format of installation packages for Linux client applications used on updating client applications via the distr directory. The file names for client application distribution packages follow the form win-mac-clients-distr-ver.arch.run and all-clients-distr-ver.arch.run, where ver is the full version number and arch is the processor architecture for which the distribution package is intended. The .deb and .rpm packages are no longer supported. You can now install client application distribution packages and other 1C:Enterprise components at the same time. Installation packages for client application distribution packages were available in .deb and .rpm package formats. It was not possible to install a client application distribution package and other 1C:Enterprise components at the same time. Simplified installation of 1C:Enterprise components on Linux. The installation of client application distribution packages is unified with other operating systems as much as possible.
Spreadsheet documents. When exporting a spreadsheet document to Microsoft Excel format, extended line spacing is used to calculate the height of document lines with multiline text (including text with automatic line wrapping). We recommend that you check that spreadsheet documents saved in Microsoft Excel format are correct and, if necessary, make changes to the algorithm for generating these documents. This change is not implemented in 8.3.19 compatibility mode. When exporting a spreadsheet document to Microsoft Excel format, the line spacing equal to that in the spreadsheet document was used to calculate the height of document lines with multiline text. However, the line spacing in a spreadsheet document and Microsoft Excel is different, which led to a violation of the document display. The Microsoft Excel document obtained as a result of spreadsheet document export is now more correct.
Window-based interface. In Taxi interface using thin client or web client:
  • If the home page is active, the ActiveWindow() method returns an object of the ClientApplicationForm type, in which:
    • Property HomePage is set to True.
    • Property Content contains home page forms.
  • For the form located on the Home page, the Window property contains an object of the ClientApplicationForm type, in which:
    • For the active home page, the Window home page form property and the ActiveWindow() method return the same object.
This change is not implemented in 8.3.19 compatibility mode.		 In Taxi interface using thin client or web client:
  • If the home page is active, the ActiveWindow() method returned:
  • If the home page is active, the Window property of the home page form returned:
 Eliminated unexpected system behavior.
Standalone server. System requirements. The standalone server does not support 32-bit Windows operating systems. The standalone server supported 32-bit Windows operating systems. 32-bit Windows operating systems are no longer supported by the standalone server.
Table of contents

Renamed objects

Object The old name The new name
The method for checking the availability of video conferences of the Collaboration System. The former name is supported for compatibility purposes.
  • VideoConferencesAvailable().
  • VideoConferencesSupported().
Presentation of the DataCompositionSchema.NestedDataCompositionSchemas property. The former name is supported for compatibility purposes.
  • NestedDataCompositionSchema.
  • NestedDataCompositionSchemas.
Description option of the MobileClientSign property for the Configuration metadata object. The former name is supported for compatibility purposes.
  • MobileClientSign
  • MobileClientSignature
Table of contents

Mobile version of "1C:Enterprise"

Functionality After Before Result of changes
Mobile platform. The mobile platform now supports automated testing. For automated testing to work, the test manager infobase with which the mobile application will interact must be available in the network. For the /TESTCLIENT command of the mobile application command line, the -TURL parameter is implemented to specify the publication URL of the test manager. Automated testing was not available on the mobile platform. Now you can use the mobile platform for automated testing of applications.
Mobile client. When a new session starts, the server cluster automatically closes the previous session associated with this mobile client application if this session exists. If the mobile client connects to the server cluster version 8.3.19 or later, or the infobase list is displayed, the mobile client application explicitly sends a request to close the previous session if that session was not closed. New event handlers in the application module: OnClientApplicationWakeup and OnClientApplicationHibernation. When the application was minimized or the device fell asleep, the mobile client did not notify the server cluster of this. As a result, the session did not hibernate. It was also impossible to determine the application recovery after falling asleep. Reduced license consumption for standard mobile client application usage patterns when the application is not closed but minimized. It is now possible to detect when the mobile application falls asleep and wakes up.
Development tools. Implemented the Mobile application build service standard data processor that provides access to the service for building mobile applications that can run Android and iOS. The service functions only if you have Internet access. To use the service, registration on the website for Read more.developers is required.The data processor interface is available only in Russian and English. This feature is provided for beta testing purpose. This feature was not provided. The service should simplify and facilitate the build of mobile applications running Android and iOS.
Mobile client. Mobile platform. New value for the UsualGroupBehavior and FormPagesRepresentation system enumerations: Auto. When the value is set to Auto, the display of form items on a mobile device is handled in a special way. This feature was not provided. It was impossible to set the system behavior so that the system would automatically change the behavior of the group and form pages on a mobile device. Simplified development of some form types for mobile devices.
Mobile client. The mobile client now supports a specialized server application deployed on the collaboration server. When such an application is deployed on the collaboration server, the stability of video calls and the number of simultaneous video conference participants increase. The mobile client supports all acceptable methods of making video calls. The mobile client made video calls in p2p mode. That is, the mobile client exchanged video streams with computers of all video call participants. Improved stability of video calls from the mobile client. Improved display of video call participants.
Command interface. Mobile client. The LocationInCommandBar property of the form button is now supported in mobile client. This property is similar to the one from the personal computer platform, with the following exceptions:
  • The Auto value in the personal computer platform is InCommandBarAndInAdditionalSubmenu. The Auto value in the mobile client is InCommandBar.
  • If the InCommandBar display mode is selected for a command bar button, but the button does not fit the command bar, the InAdditionalSubmenu display mode will be selected.
 The LocationInCommandBar property of the form button in mobile client was supported with limitations: the OnlyInAllActions property was only emulated. Now you can manage the same way button display in the command bar of mobile client and client applications for personal computers.
Table of contents

System "1C:Analytics"

Functionality After Before Result of changes
Analytics - dashboards. Implemented mode for viewing charts and dashboards. In this mode, the edit functions that are not required for analyzing information (layout of dashboard elements, adding new elements) are disabled. The mode is enabled automatically for "foreign" charts and dashboards. This feature was not provided. Users interacted with all system objects in edit mode. Working with dashboard data is now more convenient.
Analytics - charts. Updated the selection panel. The selection panel had a different appearance. Improved chart selection panel appearance.
Analytics - desktop. You can now transfer links to your folders to other users. This feature was not provided. Users can share sets of charts and dashboards.
Analytics - dashboards. You can now configure the link transition when clicking anywhere on an element of any dashboard. This feature was not provided. Implemented more interactive features for dashboards.
Analytics - dashboards. You can now set the text style and specify links when editing text elements of the dashboard. This feature was not provided. Upgraded customization of text elements of dashboards.
Analytics - charts. In Pivot table charts, you can now pin rows and columns. This feature was not provided. The pivot table display customization is now more flexible.
Analytics - dashboards. You can now scale charts by rolling the mouse wheel while pressing the Ctrl key. Rolling the mouse wheel without pressing the Ctrl key does not scale the chart. Charts were scaled by rolling the mouse wheel, without using the keyboard. This use was unexpected and interfered with the dashboard scrolling. The scaling of charts is now more expected and does not interfere with the dashboard scrolling.
Analytics - charts. New chart type: stacked lines. This feature was not provided. Extended list of used chart types.
Analytics - other. System objects (charts, dashboards, and folders) are automatically deleted from the database if there are no users who use these objects on their desktop. This feature was not provided. Unused objects were not deleted from the database. Optimized use of 1C:Analytics database.
Analytics - charts. Upgraded indicator chart customization and appearance. The indicator appearance was determined automatically. The customization options were limited. Improved indicator appearance. Now users have more customization options for this type of chart.
Analytics - charts. Two different facts on axes can now be displayed for a bubble char. This feature was not provided. Only the following combinations were available: fact-dimension and dimension-dimension. Expanded visualization features for a bubble chart.
Analytics - other. New feature for 1C:Analytics: a notification center that stores the latest system messages for viewing. This feature was not provided. After the error notification disappeared, it could not be viewed anywhere. Reporting system issues is now easier.
Table of contents

Library updates

  • The libetpan library is updated to version 1.9.4.
  • The boost library is updated to version 1.74.
  • The OpenSSL library is updated to version 1.1.1k.
  • The libssh library is updated to version 0.9.4.
Table of contents

Demo configuration changes

  • New commands in the counterparty form: Invite To Conversations, Open Conversation, Video Call. Use the commands to work with the collaboration system external users.
  • New feature demonstrating the possibility of the planner item border linking in the Calendar form of the Meetings catalog. When the display of appointments of all users is enabled, a user can drag a calendar event only if the event initially belonged to the user.
  • New section Additional resources in the Guide. It contains hyperlinks used to:
    • Switch to demo configurations.
    • Download demo configurations.
  • In the mobile demo application, working with secure data storage is switched to asynchronous calls using promises.
  • New feature: code of the OnClientApplicationWakeup() handler, which is triggered in mobile client in the standalone mode to perform data exchange with the main server after the client application wakeup.
Table of contents

Changes made after the publication of the version

Functionality After Before Result of changes
Standalone server. Dumping configurations to files/Restoring configurations from files. Optimized several infobase operations executed using the administration utility (ibcmd) by connecting to a working instance of a standalone server. The optimized operations include but are not limited to: export of configurations to XML files, partial import of configurations from XML files. database configuration update; It took longer time to execute some infobase operations executed using the administration utility (ibcmd) by connecting to a working instance of the standalone server. Accelerated execution of some operations of the infobase managed by the standalone server.
Standalone server. Development tools. You can now start 1C:Enterprise Development Tools for the interactive launcher. If 1C:Enterprise Development Tools are not installed yet, you will be prompted to install the product. You can manage the button visibility by a check box in the interactive launcher dialog box. For an infobase that uses connection via HTTP(s) protocol, you can now specify the development control address in the connection settings. To use this feature for an infobase located on a web server, click More. This feature was not provided. The interactive launcher did not support 1C:Enterprise Development Tools. Extended interactive launcher features. Improved integration of 1C:Enterprise Development Tools with other 1C:Enterprise application components.
Standalone server. Now you can find information on a debugger in the administration interface of a standalone server via SSH protocol (infobase-tools debug-info). The parameter set returned by the command now includes the infobase-name optional parameter. It contains the name of the infobase to be debugged. This feature was not provided. Simplified connection of 1C:Enterprise Development Tools debugger to the infobase managed by a standalone server.
Development tools. Standalone server. Dumping configurations to files/Restoring configurations from files. You can now disable configuration integrity check upon importing a configuration from XML files. This check can be useful if a previously exported configuration is imported. To enable this feature, a special parameter is implemented for the following import tools:
  • Command line to start 1C:Designer. New -NoCheck parameter for the /LoadConfigFromFiles command.
  • 1C:Designer in the agent mode. New --no-check parameter for the config load-config-from-files command.
  • Standalone server management utility (ibcmd). New --no-check parameter for the infobase config import command.
 This feature was not provided. Accelerated configuration import from XML files for some scenarios.
Web client. You can now automatically open a standard function form when starting the web client. Opening standard data processor forms using 1C:Enterprise language or client application user interface (following a link) is not supported. This feature was not provided. Opening standard functions form is now available from 1C:Enterprise Development Tools.
Client application. You can now disable opening home page forms upon opening the client application. New DisableHomePageForms command for the startup command line of thin client and web client. This feature was not provided. Accelerated opening of the client application.
Development tools. Standalone server. Dumping configurations to files/Restoring configurations from files. When importing the configuration from XML files, you can now import data from a ZIP archive containing configuration XML files. The archive structure must match the import directory structure. The Import configuration from files command in 1C:Designer allows you to select not only a directory but also a ZIP archive file. To use this feature, a special parameter is now available for the following import tools:
  • Command line to start 1C:Designer. New -Archive parameter for /LoadConfigFromFiles command.
  • 1C:Designer in the agent mode. New --archive parameter for config load-config-from-files command.
  • Standalone server management utility (ibcmd). New -archive parameter for infobase config import command. For commands infobase config import and infobase config import all-extensions, a directory or a ZIP archive can be specified in the unnamed parameter. The --import parameter for the infobase create command can contain a directory path or a ZIP archive name.
 This feature was not provided. Accelerated import of configuration files, especially if files to be imported are transferred via communication channels before import.
Standalone server. The standalone server generates standard text messages into the standard output stream (stdout) in the following cases:
  • After the standalone server is ready and after the internal state update is completed: 1C:Enterprise 8.3 (x86-64) (< version number>) Stand-alone Server ready.
  • After the infobase configuration update (during the internal state update): 1C:Enterprise 8.3 (x86-64) (< version number>) Stand-alone Server refreshing.
 This feature was not provided. Now it is easier to get a standalone server status when some management commands are executed.
Development tools. Standalone server. Now you can get metadata generation ID of the infobase configuration. This ID changes every time the configuration is changed in any way. To use this feature, commands are now available for the following import tools:
  • Command line to start 1C:Designer. New /GetConfigGenerationID command.
  • 1C:Designer in the agent mode. New config generation-id command.
  • Standalone server management utility (ibcmd). New infobase config generation-id command.
 This feature was not provided. Now you can check whether the infobase configuration was changed since the latest check.
Development tools. Dumping configurations to files/Restoring configurations from files. Configuration support rules settings are ignored for full configuration import from XML files. The current configuration is completely replaced including support information. Full configuration import from XML files was impossible if support rules were set. For full configuration import from XML files, configuration support had to be disabled. The behavior of full import from XML files is now identical to the configuration import from a CF file.
Development tools. Modified format of JSON messages used in 1C:Designer in the agent mode. More than two response options can be specified in messages of the questions type. Only two response options could be specified for JSON messages of the questions type in 1C:Designer in the agent mode. Extended features of the format of JSON messages used for interaction with 1C:Designer in the agent mode.
Dumping configurations to files/Restoring configurations from files. Development tools. The standalone server no longer supports a linear format for configuration import from XML files. Only a hierarchical format is used for configuration import from XML files. The standalone server supported configuration import from XML files in linear and hierarchical formats. The standalone server no longer supports the obsolete export format.
Settings storage. A recoverable error in 1C:Enterprise language occurs when accessing properties of the StandardSettingsStorageSelection object if dataset is finished or it is empty. We recommend that you analyze the StandardSettingsStorageSelection object usages for possible errors that occur if dataset is finished or it is empty. This change is not implemented in 8.3.19 compatibility mode. An attempt to access properties of the StandardSettingsStorageSelection object showed different behavior in different cases:
  • If dataset was finished, the latest read data was left in the object properties.
  • If dataset was empty, the Undefined values were in the object properties.
 Eliminated unexpected system behavior.
Queries. Accelerated execution of the query that uses fields in temporary tables received from other temporary tables with high nesting. Execution of the query that used fields in temporary tables received from other temporary tables with high nesting took more time. Improved query execution in some scenarios.
Web client. XML and XDTO support. The XMLStringProcessing global context property is now available in web client. The XMLStringProcessing global context property was not available in web client. Web client now supports methods of search and deletion of invalid XML characters in arbitrary strings.
Print tools. If the printer used for printing by 1C:Enterprise platform is available, this information will be cached. If the same printer is used for printing within 60 seconds, its availability state is received from the cache. When using the same printer multiple times consecutively, the printer availability for each print attempt was defined by the actual state of the printer. Accelerated printing when the same printer is used to print several documents consecutively.
DBMS operations. When using PostgreSQL DBMS, the result of MIN() and MAX() query language functions for a Boolean type field does not depend on the order of Boolean and NULL type values in a dataset. When using PostgreSQL DBMS, the result of MIN() and MAX() query language functions for a Boolean type field depended on the order of Boolean and NULL type values in a dataset. Eliminated unexpected system behavior. Query language functions MIN() and MAX() now work in the same manner in all supported DBMS.
Collaboration system. Now you can re-register an infobase in the collaboration system without explicitly specifying an email after disconnecting the infobase from the collaboration system. The email address specified during initial registration will be used for re-registration. All objects created in the collaboration system will be available after re-registration. If an infobase was never connected to the collaboration system, re-registration without email address specification will be impossible. Property CollaborationSystemInfobaseRegistrationParameters.EmailAddress is not required. Now you can take advantage of re-registration for the Collaboration system management data processor. Infobase re-registration in the collaboration system was possible only with email address specification. Now you can re-register an infobase in the collaboration system if the infobase was previously disconnected from the collaboration system and the email address used for initial registration was forgotten.
Localization. Now you can use Turkmenian (tk code) in the following cases:
  • To specify in regional infobase settings dialog box.
  • To specify it as the session localization code (/VL startup command-line option).
  • To view the calendar in Turkmenian.
 These features were not provided. Limited support of Turkmenian is now available in 1C:Enterprise platform.
Data composition system. Mobile platform. Mobile client. In the tables that contain data composition system settings in mobile client and the mobile platform application, the following commands are available only in the context menu of the corresponding table row: User-defined settings item properties, Set presentation, Use as field value, Set title, Expand, Group, Group conditions, Group fields, and Ungroup. The update is applied to report settings forms, dynamic list settings, and report option editing. In the tables that contained data composition system settings in mobile client and in the mobile platform application, the following commands were available in the context menu of the corresponding table row and in the More menu: User-defined settings item properties, Set presentation, Use as field value, Set title, Expand, Group, Group conditions, Group fields, and Ungroup. A command from the More menu had no effect. Eliminated unexpected system behavior.
Collaboration System. The Mark as read setting status (in the setup dialog box of the Collaboration System) is saved on the collaboration system server. If there is no such setting on the collaboration system server, an attempt is made to read the setting from the local storage. The Mark as read setting status (in the setup dialog box of the Collaboration System) was saved to a local storage of a user computer. The same Mark as read setting value (in the setup dialog box of the Collaboration System) for any device used by a user.
Queries. Client application. New commands in Query Wizard that runs in thin client: "search" and "cancel search" for all wizard form lists. The commands are available from the context menu or the More menu. In Query Wizard that runs in thin client, the "search" and "cancel search" commands were not available in the wizard form lists. The commands were available only via hotkeys, which was not clear to users. More user-friendly search in Query Wizard in thin client.
Mobile platform. Mobile client. The file selection dialog box for the mobile application running on Android or iOS is updated. The dialog box has become more convenient and faster. You can now create a file directly from the file selection dialog box. The user can now switch the dialog box to the multiple selection mode (if this mode is available). You can now set up the sections that will be available when selecting a file. New property: FileSelectionDialogBox.Sections. New feature: filter files by MIME type. New property: FileSelectionDialogBox.EncType. The file selection dialog box for the mobile application running on Android and iOS was less convenient and slower. Improved operation of the file selection dialog box in the mobile application running on Android and iOS.
Mobile application builder. The mobile application build service now supports the mobile version 8.3.19 of 1C:Enterprise. The mobile application build service did not support the mobile version 8.3.19 of 1C:Enterprise. Extended list of supported mobile versions of 1C:Enterprise in the mobile application build service
Linux. System requirements. The following distribution packages for Linux operating system are supported now:
  • Debian 10
  • Mint 20
  • Oracle Linux 7
  • Oracle Linux 8
  • RHEL 8
  • Ubuntu 20.04 LTS
  • ALT Education 10
  • ALT Workstation 10
  • ALT Workstation K 10
  • ALT Server 10 (only 64-bit version)
  • RED OS 7.3 (only 64-bit version).
 The distribution packages were not supported. Extended list of supported Linux distribution packages.
Linux. System requirements. The following distribution packages for Linux operating system are no longer supported:
  • Centos 6
  • Debian 8
  • RHEL 6
  • Ubuntu 14.04 LTS
  • Ubuntu 16.04 LTS
  • ALT Education 8
  • ALT Workstation 8
  • ALT Workstation K 8
  • ALT Server 8.
 1C:Enterprise supported the following distribution packages for Linux operating system:
  • Centos 6
  • Debian 8
  • RHEL 6
  • Ubuntu 14.04 LTS
  • Ubuntu 16.04 LTS
  • ALT Education 8
  • ALT Workstation 8
  • ALT Workstation K 8
  • ALT Server 8.
 Outdated Linux distribution packages are no longer supported.
Table of contents

Transition from the previous version to the version 8.3.20

  • Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.20.
  • Some features that are added in version 8.3.20 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
Table of contents

1C:Enterprise Developer's Community